Communication device and communication method

Abstract

The present invention improves the efficiency of wireless communications. This communication device comprises: a control circuit that determines, on the basis of downlink control information in a first format, a first time domain resource allocation used for scheduling a plurality of cells and scheduling a plurality of data channels in each of the plurality of cells, with the setting of the first time domain resource allocation being different from the setting of a second time domain resource allocation used for scheduling the plurality of data channels in a second format different from the first format; and a communication circuit that transmits or receives a signal on the basis of the first time domain resource allocation.

Description

Communication equipment and communication methods

[0001] This disclosure relates to communication devices and communication methods.

[0002] In recent years, driven by the expansion and diversification of wireless services, the Internet of Things (IoT) is expected to develop dramatically. The use of mobile communication is expanding beyond information terminals such as smartphones to encompass all fields, including automobiles, homes, home appliances, and industrial equipment. To support this service diversification, significant improvements in the performance and functionality of mobile communication systems are required, in addition to increased system capacity, as well as various requirements such as an increase in the number of connected devices and low latency. Fifth-generation mobile communication systems (5G) have features such as large capacity and ultra-high speed (eMBB: enhanced Mobile Broadband), massive machine-type communication (mMTC: massive Machine Type Communication), and ultra-reliable and low-latency communication (URLLC: Ultra Reliable and Low Latency Communication). Leveraging these features, they provide flexible wireless communication to meet a wide variety of needs.

[0003] 3GPP TS38.211, “NR Physical channels and modulation (Release 18),” December 2024. 3GPP TS38.212, “NR Multiplexing and channel coding (Release 18),” December 2024. 3GPP TS38.213, “NR Physical layer procedures for control (Release 18),” December 2024. 3GPP TS38.214, “NR Physical layer procedures for data (Release 18),” December 2024. RP-242408, “New WID: Multi-carrier enhancements for NR Phase 2,” Lenovo, RAN#105, September 2024.

[0004] However, there is room for consideration regarding methods for improving the efficiency of wireless communication.

[0005] Non-limiting examples of the present disclosure contribute to providing a communication device and a communication method capable of improving the efficiency of wireless communication.

[0006] A communication device according to an embodiment of the present disclosure determines a first time-domain resource allocation used for scheduling a plurality of cells and scheduling a plurality of data channels in each of the plurality of cells based on downlink control information of a first format, and the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and includes a control circuit and a communication circuit that transmits or receives a signal based on the first time-domain resource allocation.

[0007] These general or specific aspects may be implemented in a system, apparatus, method, integrated circuit, computer program, or recording medium, or may be implemented by any combination of a system, apparatus, method, integrated circuit, computer program, and recording medium.

[0008] According to one embodiment of the present disclosure, the efficiency of wireless communication can be improved.

[0009] Further advantages and effects of one embodiment of this disclosure will be made apparent from the specification and drawings. Such advantages and / or effects are provided by several embodiments and features described in the specification and drawings, but not all of them are necessarily provided in order to obtain one or more identical features.

[0010] Figures illustrating multiple Transport Block (TB) scheduling, multiple cell scheduling, time domain resource allocation, multiple cell scheduling, multiple TB scheduling combinations, time domain resource allocation, block diagrams showing some base station configurations, block diagrams showing some terminal configurations, time domain resource allocation, time domain resource allocation, time domain resource allocation, time domain resource allocation, time domain resource allocation, time domain resource allocation, time domain resource allocation, time domain resource allocation, flowcharts showing terminal operation, block diagrams showing base station configurations, block diagrams showing terminal configurations, 3. Diagram of exemplary architecture of a GPP NR system, 5. Diagram of exemplary functional partitioning in G O-RAN

[0011] Embodiments of this disclosure will be described in detail below with reference to the drawings.

[0012] The 3rd Generation Partnership Project (3GPP), an international standardization organization, is working on the specification of New Radio (NR) as one of the 5G radio interfaces. The basic functions of eMBB and URLLC were specified in Release 15, and from Release 16 onwards, URLLC will be extended for industrial IoT, Vehicle-to-Everything (V2X), or non-terrestrial networks (NTN) including satellites. 3GPP's extended specifications are also called "5G-Advanced" from Release 18 onwards. Furthermore, 3GPP began considering 6th generation mobile communication systems (6G) in Release 20 and plans to specify them in Release 21.

[0013] [Multiple Transport Block (TB) Scheduling] In NR, for example, "multiple transport block (TB) scheduling" is employed as one way to reduce power consumption of terminals (also called user equipment (UE)) by reducing the frequency of receiving downlink control channels (e.g., PDCCH: Physical Downlink Control Channel) while maintaining high transmission efficiency.

[0014] Figure 1 shows an example of multiple TB scheduling. As shown in Figure 1, downlink control information (e.g., DCI) containing scheduling information such as resource allocation from a base station (e.g., also called a gNB) is transmitted, for example, by a PDCCH. The terminal receives downlink data channels (e.g., PDSCH: Physical Downlink Shared Channel) or transmits uplink data channels (e.g., PUSCH: Physical Uplink Shared Channel) according to the resource allocation indicated by the DCI on the PDCCH.

[0015] For example, one DCI can instruct the scheduling of one PUSCH or PDSCH (also referred to as "PUSCH / PDSCH" or "PxSCH"), and the number of TBs included in one PUSCH / PDSCH is one, or two when transmitted via spatial multiplexing on the same time and frequency resource. On the other hand, in multiple TB scheduling, as shown in Figure 1, one DCI can allocate (schedule) multiple PUSCH / PDSCHs (e.g., TB#1 and TB#2).

[0016] In Release 18, the DCI format that can be used for multiple TB scheduling is DCI format 0-1 for PUSCH scheduling and DCI format 1-1 for PDSCH scheduling. Below, DCI format 0-1 and DCI format 1-1 will be collectively referred to as "DCI format 0-1 / 1-1".

[0017] [Multi-Cell Scheduling] In 5G, with the expansion of the 5G network and the reduction of 3G or 4G operations, it is anticipated that there will be an increased opportunity to repurpose frequency bands used by 3G or 4G (e.g., Frequency range 1 (FR1) bands) for 5G. In such scenarios, the different frequencies used for 5G may often be, for example, fragmented and narrowband bands. Therefore, multi-carrier operation combining these multiple bands is expected.

[0018] Furthermore, in the Frequency Range 2 (FR2) band, or in some FR1 bands, sufficient bandwidth can be secured within the same band, so multi-carrier operation combining multiple bands within the same band may be effective. In Release 18, a function was introduced to improve the efficiency of multi-carrier operation by scheduling multiple cells using a single DCI (for example, called "multi-cell scheduling").

[0019] In multi-cell scheduling, as shown in Figure 2, a single DCI can assign multiple PUSCH / PDSCH signals to receive or transmit in different cells (in the example in Figure 2, cells (CC: component carrier) #2, #3, and #4).

[0020] In Release 18, multi-cell scheduling allows multiple cells scheduled by a single DCI to have the same subcarrier spacing (e.g., SCS) and carrier type (e.g., the subcarrier spacing and carrier type are limited). Additionally, when scheduling multiple cells with a single DCI, each scheduled cell can be assigned one data channel (e.g., a shared channel, PUSCH / PDSCH).

[0021] In Release 18, the DCI formats that can be used for multi-cell scheduling are DCI format 0-3 for PUSCH scheduling and DCI format 1-3 for PDSCH scheduling. Below, DCI format 0-3 and DCI format 1-3 will be collectively referred to as "DCI format 0-3 / 1-3".

[0022] [Example of Time Domain Resource Allocation] PUSCH / PDSCH time domain resources are controlled, for example, by the DCI Time Domain Resource Assignment (TDRA) field. For example, in scheduling using DCI format 0-1 / 1-1, multiple time domain resource assignment patterns (e.g., candidate combinations of multiple settings) are pre-configured on the terminal by signaling from a higher layer (e.g., Radio Resource Control (RRC)), and one of the configured assignment patterns is notified by the DCI TDRA field, enabling the allocation of time domain resources (see, for example, Non-Patent Documents 2 and 4).

[0023] The parameters included in the information regarding time-domain resource allocation pre-configured on the terminal (e.g., allocation pattern, also called the "TDRA table") include, for example, an offset relative to the slot or symbol from which the terminal received the DCI (e.g., K0 or K1 (hereinafter also referred to as "K0 / K1")), information regarding the starting symbol position and number of symbols within the slot (e.g., Start and Length Indicator Value (SLIV)), and a mapping type. In the case of single TB scheduling, the parameters included in the TDRA table may also include the number of repetitions and the number of Transport Block over Multiple Slot (TBoMS) slots.

[0024] For example, in the case of multiple TB scheduling, Repetition and TBoMS do not need to be applied. Therefore, in the case of multiple TB scheduling, parameters such as the number of Repetitions and the number of TBoMS slots are not included in the TDRA table. Also, in the case of multiple TB scheduling, the parameters included in the TDRA table may include time domain allocation resources corresponding to each of the multiple PUSCH / PDSCH (or multiple TB) (e.g., offset relative to the slot or symbol in which the terminal received the DCI, the position of the first symbol in the slot, and the number of symbols).

[0025] Furthermore, in multi-cell scheduling using DCI format 0-3 / 1-3, for example, the time-domain resources for PUSCH / PDSCH for each of the multiple cells indicated by DCI or RRC are controlled by the DCI's TDRA field. For example, the DCI's TDRA field allows for the allocation of individual time-domain resources (e.g., an offset relative to the slot or symbol where the terminal received the DCI, the position and number of symbols of the first symbol in the slot, and the mapping type) to each of the multiple cells' PUSCH / PDSCHs.

[0026] For example, RRC signaling sets up a "joint TDRA table" for multiple cells (also called a "cell set"). Each row in the joint TDRA table contains TDRA indexes for multiple cells included in the cell set (e.g., all cells, or all cells and all BandWidth Parts (BWPs)). The TDRA field in DCI format 0-3 / 1-3 notifies, for example, one of several TDRA index patterns (TDRA indexes for each cell) set up in the joint TDRA table, thereby determining the TDRA index for each cell. The TDRA index for each cell is, for example, the corresponding index in the TDRA table applied to DCI format 0-1 / 1-1 (e.g., a pointer to the allocation of time-domain resources), and the allocation of time-domain resources becomes possible when one of several TDRA patterns set up in DCI format 0-1 / 1-1 is notified.

[0027] Figure 3 shows an example of time-domain resource allocation in multi-cell scheduling using DCI format 0-3 / 1-3. Each row in the joint TDRA table shown in Figure 3 contains multiple entries, each entry corresponding to a cell. For example, entry 1 in each row of the joint TDRA table shown in Figure 3 contains the TDRA index for cell #0 (and BWP #0). Similarly, other entries in the joint TDRA table shown in Figure 3 also contain TDRA indexes for each cell. For example, entry 4 in each row of the joint TDRA table shown in Figure 3 contains the TDRA index for cell #Y (and BWP #X).

[0028] For example, as shown in Figure 3, if TDRA index #0 is notified in entry 1 of the first row (joint TDRA index #0) of the joint TDRA table, a time domain resource corresponding to index #0 of the TDRA table (TDRA table for BWP#0 of CC#0) set in cell #0 (and BWP#0) is allocated. Similarly, as shown in Figure 3, if TDRA index #1 is notified in entry 4 of the first row (joint TDRA index #0) of the joint TDRA table, a time domain resource corresponding to index #1 of the TDRA table set in cell #Y (and BWP#X) is allocated.

[0029] The above explains an example of time domain resource allocation.

[0030] Release 19 explores the introduction of a multi-cell scheduling function for cases where the subcarrier spacing (SCS) or carrier type differs between multiple cells scheduled by a single DCI (for example, cell #2 (CC#2) and cell #3 (CC#3) in the example in Figure 4). Multi-cell scheduling for cells with different SCSs or different carrier types is of high commercial value to operators, such as multi-cell scheduling using FR1 and FR2 carrier cells. Furthermore, multi-cell scheduling from cells with small subcarrier spacings to cells with large subcarrier spacings is beneficial in terms of terminal power consumption or the reliability of PDCCH monitoring.

[0031] Furthermore, in Release 19, for example, as shown in Figure 5, when scheduling multiple cells with a single DCI, the application of multiple TB scheduling is permitted for each scheduled cell (in the example in Figure 5, cell #3 (CC#3)). For example, it is being considered to introduce a function that assigns multiple data channels (e.g., PUSCH / PDSCH) to each scheduled cell. By combining multiple cell scheduling with multiple TB scheduling in each scheduled cell, it is possible to improve scheduling efficiency for cells with large subcarrier intervals.

[0032] However, there is room for consideration regarding the allocation of time domain resources when applying multiple TB scheduling to each scheduled cell in a multi-cell scheduling system.

[0033] Release 19 explores combining the single-cell multi-TB scheduling supported in Release 18's DCI format 0-1 / 1-1 with the multi-cell scheduling supported in Release 18's DCI format 0-3 / 1-3. Furthermore, it is being considered to implement multi-cell scheduling and multi-TB scheduling within each scheduled cell, for example, through an extension of DCI format 0-3 / 1-3.

[0034] Here, there are features that are not commonly supported in both DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 (features that are supported in one or the other). For example, Repetition and TBoMS are such features. Repetition and TBoMS are not supported in multi-TB scheduling using DCI format 0-1 / 1-1. On the other hand, Repetition and TBoMS are supported in multi-cell scheduling using DCI format 0-3 / 1-3. However, in Release 18, TBoMS is applicable to PUSCH but not to PDSCH.

[0035] In this case, in order to ensure proper operation of multi-cell scheduling using DCI format 0-3 / 1-3, and multi-TB scheduling in each scheduled cell, it is expected that consideration will be given to whether or not to support features not supported in both DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 (features supported in one of them) in the extended DCI format 0-3 / 1-3.

[0036] Thus, for example, in multi-cell scheduling using DCI format 0-3 / 1-3 and multi-TB scheduling within each scheduled cell, there is room for consideration regarding time-domain resource allocation that may include the allocation of Repetition or TBoMS.

[0037] The following describes how to reuse existing TDRA notifications and existing RRC parameters (operational example) in multi-cell scheduling using DCI format 0-3 / 1-3 and multi-TB scheduling in each scheduled cell.

[0038] [Operation Example 0A] Operation Example 0A describes a method for directly reusing existing TDRA notifications and existing RRC parameters in multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell.

[0039] Here, existing TDRA notifications can refer to a notification method that determines the TDRA index for each cell by notifying one of several TDRA index patterns set in the joint TDRA table in the TDRA field of the DCI format 0-3 / 1-3 described above. In this TDRA notification, the TDRA index for each cell is a pointer to the corresponding index (e.g., time domain resource allocation) in the TDRA table applied to DCI format 0-1 / 1-1, and time domain resources are allocated by notifying one of several TDRA patterns set in DCI format 0-1 / 1-1.

[0040] Furthermore, existing RRC parameters may include, for example, the TDRA tables used for single TB scheduling supported in DCI format 0-1 / 1-1 of Release 18 (e.g., "pxsch-TimeDomainAllocationList") and the TDRA tables used for multi-TB scheduling (e.g., "pxsch-TimeDomainAllocationListForMultPxSCH"). Here, "pxsch" means a data channel such as "pusch" or "pdsch".

[0041] In this case, multiple TB scheduling is applied to cells within a cell set that has a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCH) set for DCI format 0-1 / 1-1 used for multiple TB scheduling. Repetition or TBoMS is not applied to these cells.

[0042] On the other hand, single TB scheduling is applied to cells within a cell set that has a TDRA table (pxsch-TimeDomainAllocationList) set for single TB scheduling for DCI format 0-1 / 1-1. For these cells, if Repetition or TBoMS is set in the TDRA table (e.g., pxsch-TimeDomainAllocationList) used for single TB scheduling, then Repetition or TBoMS may be applied. For example, if the TDRA table includes an element (or column, e.g., "numberOfRepetitions") related to the number of Repetitions, or if an RRC parameter (e.g., "pxsch-AggregationFactor") related to the number of Repetitions is set in the terminal, then Repetition may be applied. Also, if the TDRA table includes an element (or column, e.g., "numberOfSlotsTBoMS") related to the number of TBoMS slots, then TBoMS may be applied. Alternatively, if the TDRA table contains both elements relating to the number of Repetitions and elements relating to the number of TBoMS slots, then Repetition and TBoMS (for example, TBoMS with Repetition) may be applied.

[0043] Figure 6 shows an example of time domain resource allocation when applying multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell in operation example 0A.

[0044] As shown in FIG. 6, the joint TDRA table is composed (defined) of a plurality of entries corresponding to each of a plurality of cells, and each entry includes a TDRA table for a plurality of cells and a plurality of TB schedulings by DCI format 0-3 / 1-3, or a TDRA index for identifying any one of the patterns of time domain resources included in the TDRA table set to DCI format 0-1 / 1-1. Further, information (joint TDRA index) for identifying any one of the patterns of TDRA indexes set for each of the plurality of entries in the joint TDRA table is set.

[0045] As shown in FIG. 6, each of the TDRA table (multi-PxSCH table) for a plurality of cells and a plurality of TB schedulings by DCI format 0-3 / 1-3, and the TDRA table (single PxSCH table) set to DCI format 0-1 / 1-1 includes a pattern of a plurality of parameters (for example, K0 / K1, SLIV, mapping type, repetition number, etc.) related to time domain resources.

[0046] In entry 1 in each row of the joint TDRA table shown in FIG. 6, for example, a TDRA index for cell #0 (and BWP #0) is included. For example, in the first row (joint TDRA index #0) of the joint TDRA table shown in FIG. 6, TDRA index #0 is notified by entry 1. In this case, the time domain resources corresponding to index #0 of the TDRA table set for cell #0 (and BWP #0) are allocated. Here, in the example of FIG. 6, for cell #0 (and BWP #0), a TDRA table (for example, pxsch-TimeDomainAllocationList) used for single TB scheduling for DCI format 0-1 / 1-1 is set, and the TDRA table includes an element (or column, for example, numberOfRepetitions) related to the repetition number.

[0047] Also, in entry 4 of each row of the joint TDRA table shown in FIG. 6, a TDRA index for cell #Y (and BWP #X) is included. For example, in the first row (joint TDRA index #0) of the joint TDRA table shown in FIG. 6, TDRA index #1 is notified by entry 4. In this case, a time domain resource corresponding to index #1 of the TDRA table set for cell #Y (and BWP #X) is allocated. Here, in the example of FIG. 6, for cell #Y (and BWP #X), a TDRA table (for example, pxsch-TimeDomainAllocationListForMultPxSCH) used for multiple TB scheduling for DCI format 0-1 / 1-1 is set, and the TDRA table includes parameters of time domain resources for each cell (for example, K0 / K1, and SLIV1, SLIV 2, SLIV3, SLIV4,...). [[ID=<<MASK_BEGIN>>1]] [[ID=<<MASK_BEGIN>>2]]

[0048] [[ID=<<MASK_BEGIN>>3]] Here, in multiple TB scheduling by DCI format 0-1 / 1-1, there is no individual RRC setting for enabling multiple TB scheduling. By setting a TDRA table (for example, pxsch-TimeDomainAllocationListForMultPxSCH) used for multiple TB scheduling for DCI format 0-1 / 1-1, the multiple TB scheduling function becomes effective. Therefore, in the method of operation example 0A described above, setting of a TDRA table (for example, pxsch-TimeDomainAllocationListForMultPxSCH) used for multiple TB scheduling for DCI format 0-1 / 1-1 is required. [[ID=<<MASK_BEGIN>>4]] [[ID=<<MASK_BEGIN>>5]]

[0049] However, one of the design guidelines for Release 19 is to design the system so that it is not possible to simultaneously enable single-cell and multiple-TB scheduling using DCI format 0-1 / 1-1 for multiple-cell scheduling and multiple-TB scheduling in each scheduled cell (see, for example, Non-Patent Document 5). For example, a terminal is not intended to have both single-cell and multiple-TB scheduling and multiple-cell and multiple-TB scheduling enabled in the same or different cells within the same PUCCH group. This is because if both single-cell and multiple-TB scheduling and multiple-cell and multiple-TB scheduling are enabled, the DCI overhead and the number of DCI size monitors will increase, resulting in overlapping functionality. Therefore, the method in Operation Example 0A described above may not be consistent with the design guidelines in Release 19 because, in order to enable multiple-cell and multiple-TB scheduling using DCI format 0-3 / 1-3, single-cell and multiple-TB scheduling for DCI format 0-1 / 1-1 must be enabled.

[0050] Furthermore, depending on the TDRA table set up by RRC for each cell, it is determined whether the resource allocation (or scheduling) for the corresponding cell will be a single TB scheduling that can apply Repetition or TBoMS, or a multi-TB scheduling that does not apply Repetition or TBoMS. For this reason, it is difficult to dynamically switch between single TB scheduling that applies Repetition or TBoMS and multi-TB scheduling.

[0051] [Operation Example 0B] Operation Example 0B describes how to set up a TDRA table (for example, "pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3") used for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, which is different from the TDRA table set up for DCI format 0-1 / 1-1.

[0052] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0053] For example, the TDRA index for each cell may be determined by notifying one of several TDRA index patterns (combinations of TDRA indices for each cell) set in the joint TDRA table via the TDRA field in DCI format 0-3 / 1-3 (e.g., the joint TDRA index). The TDRA index for each cell notified by the TDRA field is either the corresponding index in the TDRA table applied to DCI format 0-1 / 1-1 (e.g., time domain resource allocation), or a pointer to the corresponding index in the TDRA table set for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3. Time domain resources are allocated by notifying one of several TDRA patterns included in the joint TDRA table via the TDRA field.

[0054] Multiple TB scheduling is applied to cells within a cell set that has a TDRA table for multiple cells and multiple TB scheduling set up in DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3). Repetition or TBoMS is not applied to these cells.

[0055] On the other hand, for cells in a cell set where a TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is not set, a TDRA table used for single TB scheduling (e.g., pxsch-TimeDomainAllocationList) is set for DCI format 0-1 / 1-1, and single TB scheduling is applied. For these cells, if Repetition or TBoMS is set in the TDRA table used for single TB scheduling (e.g., pxsch-TimeDomainAllocationList), Repetition or TBoMS may be applied. For example, if the TDRA table includes an element (or column, e.g., numberOfRepetitions) related to the number of repetitions, or if an RRC parameter related to the number of repetitions (e.g., pxsch-AggregationFactor) is set in the terminal, Repetition may be applied. Furthermore, if the TDRA table contains an element (or column, e.g., numberOfSlotsTBoMS) relating to the number of TBoMS slots, TBoMS may be applied. Alternatively, if the TDRA table contains both an element relating to the number of repetitions and an element relating to the number of TBoMS slots, Repetition and TBoMS (e.g., TBoMS with Repetition) may be applied.

[0056] Furthermore, the terminal does not assume that both a TDRA table used for existing multi-TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCH) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) will be set simultaneously in the same cell or different cells within the same PUCCH group.

[0057] Figure 7 shows an example of time domain resource allocation when applying multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell in Operation Example 0B.

[0058] In the joint TDRA table shown in Figure 7, entry 1 in each row contains, for example, the TDRA index for cell #0 (and BWP #0). For example, in the first row of the joint TDRA table shown in Figure 7 (joint TDRA index #0), entry 1 notifies TDRA index #0. In this case, a time domain resource corresponding to index #0 of the TDRA table set in cell #0 (and BWP #0) is allocated. Here, in the example in Figure 7, cell #0 (and BWP #0) is set to a TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList), and the TDRA table contains an element (or column, e.g., numberOfRepetitions) related to the number of repetitions.

[0059] Furthermore, entry 4 in each row of the joint TDRA table shown in Figure 7 contains the TDRA index for cell #Y (and BWP#X). For example, in the first row of the joint TDRA table shown in Figure 7 (joint TDRA index #0), entry 4 notifies TDRA index #1. In this case, a time domain resource corresponding to index #1 of the TDRA table set for cell #Y (and BWP#X) is allocated. Here, in the example in Figure 7, a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set for cell #Y (and BWP#X), and the TDRA table contains time domain resource parameters for each cell (e.g., K0 / K1, and SLIV1, SLIV2, SLIV3, SLIV4, ...).

[0060] Thus, by using a TDRA table for multi-cell and multi-TB scheduling in DCI format 0-3 / 1-3, it is not necessary to enable single-cell and multi-TB scheduling for DCI format 0-1 / 1-1 in order to enable multi-cell and multi-TB scheduling in DCI format 0-3 / 1-3. For this reason, the method in Operation Example 0B is consistent with the design guidelines in Release 19.

[0061] However, depending on the TDRA table set up by RRC for each cell, it is determined whether the resource allocation (or scheduling) for the corresponding cell will be a single TB scheduling that can apply Repetition or TBoMS, or a multi-TB scheduling that does not apply Repetition or TBoMS. Therefore, it is difficult to dynamically switch between single TB scheduling that applies Repetition or TBoMS and multi-TB scheduling.

[0062] In one non-limiting embodiment of this disclosure, a method for allocating time domain resources when applying multiple TB scheduling to each scheduled cell in multiple cell scheduling is described.

[0063] For example, in a non-limiting embodiment of this disclosure, a method is described for preventing simultaneous activation of multiple-cell and multiple-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multiple-TB scheduling using DCI format 0-1 / 1-1 when applying multiple-TB scheduling to each scheduled cell in multiple-cell scheduling. Also, in a non-limiting embodiment of this disclosure, a method is described for dynamically switching between single-TB scheduling and multiple-TB scheduling to which Repetition or TBoMS is applied.

[0064] For example, for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, a TDRA table used for multi-TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) may be set, separate from the TDRA table set for DCI format 0-1 / 1-1. In this case, in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., Repetition or TBoMS can be applied) (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3. In one non-limiting embodiment of the present disclosure, the base station can dynamically switch between single TB scheduling and multiple TB scheduling, to which Repetition or TBoMS can be applied, by dynamically notifying the terminal which of multiple TDRA tables to use.

[0065] Furthermore, in one non-limiting embodiment of this disclosure, for example, a quasi-static switching between single TB scheduling and multiple TB scheduling to which Repetition or TBoMS can be applied, which differs from the operation example 0B described above, and a method for setting up a TDRA table in which single TB scheduling and multiple TB scheduling coexist for DCI format 0-3 / 1-3 will also be described.

[0066] The following describes non-limiting embodiments of this disclosure.

[0067] [Overview of the communication system] A communication system according to one aspect of the present disclosure comprises, for example, at least one base station (e.g., corresponding to a communication device) and at least one terminal (e.g., corresponding to a communication device).

[0068] Figure 8 is a block diagram showing a partial configuration example of a base station 100 according to one embodiment of the present disclosure, and Figure 9 is a block diagram showing a partial configuration example of a terminal 200 according to one embodiment of the present disclosure.

[0069] In the base station 100 shown in Figure 8, the control unit (for example, corresponding to a control circuit) determines a first time-domain resource allocation used for multiple cell scheduling and scheduling of multiple data channels in each of the multiple cells (multiple TB scheduling) based on downlink control information (DCI) in a first format (for example, DCI format 0-3 / 1-3). The communication unit (for example, corresponding to a communication circuit) transmits (for example, PDSCH transmission) or receives (for example, PUSCH reception) a signal based on the above first time-domain resource allocation.

[0070] In the terminal 200 shown in Figure 9, the control unit (for example, corresponding to a control circuit) determines a first time-domain resource allocation used for multiple cell scheduling and scheduling of multiple data channels in each of the multiple cells (multiple TB scheduling) based on downlink control information (DCI) in a first format (for example, DCI format 0-3 / 1-3). The communication unit (for example, corresponding to a communication circuit) transmits (for example, PUSCH transmission) or receives (for example, PDSCH reception) a signal based on the first time-domain resource allocation.

[0071] Here, the first time-domain resource allocation setting described above (for example, a TDRA table used for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3) differs from the second time-domain resource allocation setting used for scheduling multiple data channels (multiple TB scheduling) in a second format different from the first format (for example, DCI format 0-1 / 1-1) (for example, a TDRA table used for a single cell using DCI format 0-1 / 1-1).

[0072] (Embodiment 1) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0073] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0074] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0075] In this embodiment, the base station 100 may dynamically notify the terminal 200 which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on dynamic notification or settings.

[0076] In this embodiment, for example, a bit field for TDRA table selection may be added to DCI (e.g., DCI format 0-3 / 1-3), and the bit field may indicate which TDRA table to use. For example, the bit field for TDRA table selection may indicate one table selected from among the TDRA tables for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and the TDRA tables set in DCI format 0-1 / 1-1. The bit field for TDRA table selection may be added as a separate field from the TDRA field, or the TDRA field may be extended (e.g., by adding bits) to include both the bit field for TDRA table selection and the bit field for TDRA index notification within the TDRA field.

[0077] Furthermore, the size of the bit field for TDRA table selection may be determined, for example, based on the maximum number of cells that can be allocated in multi-cell scheduling, or it may be determined based on the number of cells that have actually been allocated.

[0078] For example, if the number of assignable cells is {1, 2, or 4} cells, and the size of the bit field for TDRA table selection is determined based on the maximum number of assignable cells, the bit field for TDRA table selection may be 4 bits. In this case, each bit in the bit field for TDRA table selection may correspond to a notification of TDRA table selection in each cell (for example, information in bitmap format). For example, a value of "0" in the bit field for TDRA table selection corresponds to the use of a TDRA table used for single TB scheduling for DCI format 0-1 / 1-1, and "1" corresponds to the use of a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (or vice versa).

[0079] Furthermore, for example, if the number of assignable cells is {1, 2, 4} cells, and the size of the bit field for TDRA table selection is determined based on the number of cells actually assigned, the bit field for TDRA table selection may be determined to have 1, 2, or 4 bits depending on the number of cells actually assigned. Similarly, in this case, each bit of the bit field for TDRA table selection may correspond to the notification of TDRA table selection in each cell (for example, information in bitmap format).

[0080] Furthermore, the bit for TDRA table selection is present (set) for cells where a TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 is configured, and does not need to be present (does not need to be set) for cells where a TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 is not configured.

[0081] The size of the bit field for TDRA table selection is not limited to being determined based on the maximum number of assignable cells or the number of cells actually assigned. For example, the size of the bit field for TDRA table selection may be determined based on the number of cell groups formed by grouping assigned cells in order to reduce the bit field size. Cell groups may be set on terminal 200 by the RRC, or cells with the same subcarrier interval may be implicitly set as the same cell group.

[0082] Furthermore, the TDRA table selection may be communicated in combination with other fields, in addition to the bit field for TDRA table selection.

[0083] In the TDRA field of DCI format 0-3 / 1-3, the TDRA index for each cell is determined by notifying one of several TDRA index patterns (the TDRA index patterns set for the entry corresponding to each cell) that are set in the joint TDRA table. The TDRA index for each cell notified by the TDRA field is a pointer to the corresponding index (e.g., time domain resource allocation) in the TDRA table determined by the TDRA table selection described above. Time domain resources are allocated by notifying one of several TDRA patterns included in the joint TDRA table via the TDRA field.

[0084] Figure 10 shows an example of time domain resource allocation in this embodiment.

[0085] In the joint TDRA table shown in Figure 10, entry 1 in each row contains, for example, the TDRA index for cell #0 (and BWP #0). For example, in the first row of the joint TDRA table shown in Figure 10 (joint TDRA index #0), entry 1 notifies that TDRA index #0 is being referred to.

[0086] Furthermore, in Figure 10, cell #0 (and BWP#0) is configured with a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 (multi-PxSCH table for DCI format z-3; for example, pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) and a TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 (single PxSCH table; for example, pxsch-TimeDomainAllocationList). As shown in Figure 10, the terminal 200 is notified which TDRA table to select by a bit field for TDRA table selection (for example, the X bit).

[0087] For example, as shown in Figure 10, when a TDRA table is selected for single TB scheduling for DCI format 0-1 / 1-1, a time-domain resource corresponding to index #0 of the corresponding TDRA table is allocated. Here, as shown in Figure 10, the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 may include an element (or column, e.g., numberOfRepetitions) relating to the number of repetitions.

[0088] Furthermore, as shown in Figure 10, when a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 is selected, a time domain resource corresponding to index #0 of the corresponding TDRA table is allocated.

[0089] In this way, terminal 200 dynamically switches between a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1, based on a bit field for selecting a TDRA table included in DCI.

[0090] According to this embodiment, by using a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3), it is not necessary to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0091] Furthermore, according to this embodiment, it is possible to dynamically switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling by using a bit field for TDRA table selection.

[0092] Furthermore, according to this embodiment, since the selection of a TDRA table and the selection of a TDRA index can be notified separately, there is an advantage in that the flexibility of notifying combinations thereof can be improved.

[0093] (Embodiment 2) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0094] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0095] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0096] In this embodiment, the base station 100 may dynamically notify the terminal 200 which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on dynamic notification or settings.

[0097] In this embodiment, for example, in each row of the joint TDRA table, the entry corresponding to each cell may include an element that notifies one of the following tables to be selected from among the TDRA tables for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and the TDRA tables set in DCI format 0-1 / 1-1, in addition to the TDRA index for each cell. The element for TDRA table selection may exist (be set) for cells to which a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set, but may not exist (may not be set) for cells to which a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is not set.

[0098] In the TDRA field of DCI format 0-3 / 1-3, the combination of TDRA table and TDRA index for each cell is determined by notifying one of several TDRA table selection and TDRA index patterns (patterns of elements for TDRA index and TDRA table selection set for each of the multiple entries in the joint TDRA table) that are configured in the joint TDRA table. The TDRA index for each cell notified by the TDRA field is a pointer to the corresponding index of the TDRA table determined by the TDRA table selection (for example, the allocation of time-domain resources). Time-domain resources are allocated by notifying one of several TDRA patterns included in the joint TDRA table via the TDRA field.

[0099] Figure 11 shows an example of time domain resource allocation in this embodiment.

[0100] In Figure 11, as an example, cell #0 (and BWP#0) is configured with a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (multi-PxSCH table for DCI format z-3; for example, pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (single PxSCH table; for example, pxsch-TimeDomainAllocationList).

[0101] In the joint TDRA table shown in Figure 11, entry 1 in each row includes, for example, a TDRA table selection and a TDRA index for cell #0 (and BWP #0).

[0102] For example, in the first row of the joint TDRA table shown in Figure 11 (joint TDRA index #0), the TDRA table selection notifies the TDRA table to be used for single TB scheduling for DCI format 0-1 / 1-1, and also notifies the TDRA index #0. In this case, as shown in Figure 11, the TDRA table to be used for single TB scheduling for DCI format 0-1 / 1-1 is selected, and the time domain resource corresponding to index #0 of the corresponding TDRA table is allocated. Here, as shown in Figure 11, the TDRA table to be used for single TB scheduling for DCI format 0-1 / 1-1 may include an element (or column, numberOfRepetitions) related to the number of repetitions.

[0103] Furthermore, for example, in the third row (Joint TDRA Index #2) of the Joint TDRA Table shown in Figure 11, the TDRA table selection notifies a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and TDRA Index #1 is also notified. In this case, as shown in Figure 11, a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is selected, and a time domain resource corresponding to Index #1 of the corresponding TDRA table is allocated.

[0104] In this way, terminal 200 dynamically switches between a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1, based on the TDRA field included in the DCI.

[0105] According to this embodiment, by using a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3), it is not necessary to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0106] Furthermore, according to this embodiment, by selecting a TDRA table in the joint TDRA table, it is possible to dynamically switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling.

[0107] Furthermore, in this embodiment, the joint TDRA table includes information for TDRA table selection, and dynamic switching of TDRA tables is possible by the joint TDRA index notified by the TDRA field. Therefore, since it is not necessary to add a bit field to the DCI for TDRA table selection, the increase in DCI overhead can be suppressed. In addition, since the configuration (setting) of the TDRA table to be set in each cell and the TDRA table selection can be set separately, the setting of the TDRA table to be set in each cell can be simplified.

[0108] (Embodiment 3) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0109] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0110] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0111] In this embodiment, the base station 100 may dynamically notify the terminal 200 which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on dynamic notification or settings.

[0112] In this embodiment, for example, a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 may include a pointer to a TDRA table configured in DCI format 0-1 / 1-1. For example, a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 may include a pattern of multiple parameters (e.g., K0 / K1, multiple SLIVs) relating to time-domain resources in multi-cell and multi-TB scheduling, and a pointer to a TDRA table configured in DCI format 0-1 / 1-1 (e.g., a TDRA index in a TDRA table configured in DCI format 0-1 / 1-1).

[0113] In the TDRA field of DCI format 0-3 / 1-3, the TDRA index for each cell is determined by notifying one of several TDRA index patterns (the patterns of TDRA indices set for each of the multiple entries in the joint TDRA table) that are set in the joint TDRA table. For example, in a cell where a TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set, the TDRA index of each cell notified by the TDRA field is a pointer to the corresponding index in the TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 (e.g., time domain resource allocation, or a pointer to the TDRA table set in DCI format 0-1 / 1-1). For example, the TDRA index of each cell notified by the TDRA field allocates time domain resources by notifying one of several TDRA patterns or a pointer to the TDRA table set in DCI format 0-1 / 1-1. For example, if the TDRA index of each cell notified by the TDRA field points to a TDRA table configured in DCI format 0-1 / 1-1, the terminal 200 may determine the allocation of time-domain resources based on the corresponding TDRA index in the TDRA table configured in DCI format 0-1 / 1-1.

[0114] Figure 12 shows an example of time domain resource allocation in this embodiment.

[0115] In Figure 12, as an example, cell #0 (and BWP#0) is configured with a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (multi-PxSCH table for DCI format z-3; for example, pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (single PxSCH table; for example, pxsch-TimeDomainAllocationList).

[0116] In the joint TDRA table shown in Figure 12, entry 1 in each row contains, for example, the TDRA index for cell #0 (and BWP #0). For example, in the first row of the joint TDRA table shown in Figure 12 (joint TDRA index #0), entry 1 notifies TDRA index #1. In this case, a time domain resource corresponding to index #1 of the corresponding TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is allocated.

[0117] Here, if the corresponding TDRA table for a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 contains a pointer to a TDRA table configured in DCI format 0-1 / 1-1 (index #1 (or #0) in Figure 12), then the time domain resource corresponding to index #1 of the corresponding TDRA table configured in DCI format 0-1 / 1-1 is allocated. For example, in the example in Figure 12, the time domain resource corresponding to index #1 of the TDRA table configured in DCI format 0-1 / 1-1 is allocated to cell #0 (and BWP #0).

[0118] In this way, terminal 200 dynamically switches between a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1, based on the TDRA field included in the DCI.

[0119] According to this embodiment, by using a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3), it is not necessary to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0120] Furthermore, according to this embodiment, by setting a pointer to a TDRA table set in DCI format 0-1 / 1-1 within a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, it becomes possible to dynamically switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling.

[0121] Furthermore, in this embodiment, the TDRA field (joint TDRA index) notifies the user of one of the TDRA tables for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (for example, including time-domain resource patterns in multi-cell and multi-TB scheduling, and pointers to TDRA tables set in DCI format 0-1 / 1-1). Therefore, since it is not necessary to add a bit field to DCI for TDRA table selection, the increase in DCI overhead can be suppressed. In addition, since the configuration (settings) of the joint TDRA table and the TDRA table selection can be set separately, the configuration of the joint TDRA table can be simplified.

[0122] (Embodiment 4) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0123] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0124] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0125] In this embodiment, the base station 100 may dynamically notify the terminal 200 which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on dynamic notification or settings.

[0126] In this embodiment, for example, a TDRA table configured in DCI format 0-1 / 1-1 is linked to a TDRA table for multi-cell and multi-TB scheduling in DCI format 0-3 / 1-3. For example, the linked TDRA table may contain patterns for time-domain resources configured in DCI format 0-1 / 1-1 and patterns for time-domain resources for multi-cell and multi-TB scheduling in DCI format 0-3 / 1-3. Also, for example, each row of the joint TDRA table may contain a TDRA index in the entry corresponding to each cell that identifies one of the patterns included in the linked table.

[0127] In the TDRA field of DCI format 0-3 / 1-3, the TDRA index for each cell is determined by notifying one of several TDRA index patterns (the patterns of TDRA indexes set for each of the multiple entries in the joint TDRA table) that are configured in the joint TDRA table. For example, in a cell where a TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3 (pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is configured, the TDRA index for each cell is a pointer to the corresponding index (e.g., time domain resource) in the TDRA table that is a concatenation of the TDRA table configured in DCI format 0-1 / 1-1 and the TDRA table for multiple cells and multiple TB scheduling using DCI format 0-3 / 1-3. Time domain resources are allocated by notifying one of several TDRA patterns included in the joint TDRA table via the TDRA field.

[0128] Figure 13 shows an example of time domain resource allocation in this embodiment.

[0129] As shown in Figure 13, if a TDRA table configured in DCI format 0-1 / 1-1 has N rows of elements (e.g., TDRA index #0 to #N-1), the leading TDRA index of a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 may correspond to the (N+1)th element of the concatenated TDRA table (e.g., TDRA index #N).

[0130] Note that the order of concatenation of TDRA tables is not limited to the example shown in Figure 13. For example, if a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 has N rows of elements, the TDRA index at the beginning of the TDRA table set to DCI format 0-1 / 1-1 may correspond to the N+1th element of the concatenated TDRA table (e.g., TDRA index #N).

[0131] In Figure 13, as an example, cell #0 (and BWP#0) is configured with a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (multi-PxSCH table for DCI format z-3; for example, pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (single PxSCH table; for example, pxsch-TimeDomainAllocationList).

[0132] In the joint TDRA table shown in Figure 13, entry 1 in each row contains, for example, the TDRA index for cell #0 (and BWP #0). For example, in the first row of the joint TDRA table shown in Figure 13 (joint TDRA index #0), entry 1 notifies TDRA index #N+1. In this case, a time-domain resource corresponding to index #N+1 of the corresponding TDRA table in the concatenated TDRA table is allocated.

[0133] In the example in Figure 13, for example, if each entry notifies a TDRA index #0 to #N-1, time domain resources are allocated to the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1. On the other hand, in the example in Figure 13, for example, if each entry notifies a TDRA index #N or higher, time domain resources are allocated to the TDRA table used for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0134] In this way, terminal 200 dynamically switches between a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1, based on the TDRA field included in the DCI.

[0135] In this embodiment, one of several TDRA indexes included in the concatenated TDRA table is notified. The concatenated TDRA table also includes a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3). This eliminates the need to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each scheduled cell in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0136] Furthermore, according to this embodiment, by notifying each cell of the TDRA index via the TDRA field, it becomes possible to dynamically switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling.

[0137] Furthermore, in this embodiment, the TDRA field (joint TDRA index) notifies the TDRA index of a TDRA table that is a link between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set in DCI format 0-1 / 1-1. Therefore, since it is not necessary to add a bit field to DCI for TDRA table selection, the increase in DCI overhead can be suppressed. In addition, the configuration (setting) of the joint TDRA table and the configuration (setting) of the TDRA table to be set for each cell can be simplified.

[0138] (Embodiment 5) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0139] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0140] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0141] In this embodiment, the base station 100 may implicitly notify the terminal 200 which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on the implicit notification or setting.

[0142] For example, an implicit notification may be provided by at least one of the following: a cell set (a set of multiple cells), the combination of multiple cells actually allocated, the actual number of cells allocated, or the subcarrier interval of the allocated cells. Note that the implicit notification is not limited to these parameters and may be other parameters different from those related to the allocation of time-domain resources.

[0143] For example, the choice of which TDRA table to use may be predetermined for each cell set. In this case, the TDRA table associated with a cell set may be implicitly selected (determined) by notification from the cell set performing multi-cell scheduling.

[0144] Furthermore, for example, which TDRA table to use may be predetermined for each combination of cells that are actually allocated. In this case, the TDRA table associated with the combination of cells that will be scheduled for multiple cells may be implicitly selected (determined) by notification of the combination of cells that will be scheduled for multiple cells.

[0145] Furthermore, for example, the choice of which TDRA table to use may be predetermined for each number of cells actually allocated. In this case, the TDRA table associated with the number of cells to be scheduled may be implicitly selected (determined) based on the notification of the number of cells to be scheduled. For example, if the number of notified cells is less than or equal to threshold C, the use of the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 may be determined, and if the number of notified cells is greater than threshold C, the use of the TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 may be determined (and vice versa).

[0146] Furthermore, for example, which TDRA table to use may be predetermined for each subcarrier interval of the assigned cell. In this case, the TDRA table associated with the subcarrier interval may be implicitly selected (determined) by notification of the subcarrier interval of the assigned cell.

[0147] Furthermore, the mapping (association) between the selection of a TDRA table and the corresponding implicit notification or setting may be predefined in the standard, or it may be set quasi-statically by RRC or the like.

[0148] In the TDRA field of DCI format 0-3 / 1-3, the TDRA index for each cell is determined by notifying one of several TDRA index patterns (the patterns of TDRA indexes set for each of the multiple entries in the joint TDRA table) that are configured in the joint TDRA table. The TDRA index for each cell is a pointer to the corresponding index (e.g., time domain resource allocation) in the TDRA table determined by the TDRA table selection described above. Time domain resources are allocated by notifying one of the several TDRA patterns included in the joint TDRA table via the TDRA field.

[0149] According to this embodiment, by using a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3), it is not necessary to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0150] Furthermore, according to this embodiment, implicit notification of TDRA table selection makes it possible to dynamically or quasi-statically switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling.

[0151] Furthermore, in this embodiment, TDRA table selection is implicitly notified by parameters different from those related to the allocation of time-domain resources (e.g., TDRA fields), so it is not necessary to add bit fields to the DCI for TDRA table selection, thereby suppressing the increase in DCI overhead.

[0152] (Embodiment 6) In this embodiment, for multiple cell scheduling using DCI format 0-3 / 1-3 and multiple TB scheduling in each scheduled cell, a TDRA table used for multiple TB scheduling (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3, separate from the TDRA table set up in DCI format 0-1 / 1-1.

[0153] Here, "pxsch" refers to a data channel such as "pusch" or "pdsch". Also, "DCI-z-3" refers to a DCI format such as "0-3" or "1-3".

[0154] For example, if a TDRA table (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3) is set up for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and is separate from the TDRA table set up for DCI format 0-1 / 1-1, then in a cell where the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 is set up, there may be both a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1 (e.g., pxsch-TimeDomainAllocationList) and a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0155] In this embodiment, the base station 100 may quasi-statically notify the terminal 200 of which TDRA table to use. The terminal 200 may, for example, switch between a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 and a TDRA table set to DCI format 0-1 / 1-1 based on the quasi-static notification or setting.

[0156] For example, the base station 100 and terminal 200 may decide which TDRA table to use (they may switch TDRA tables) based on whether or not Repetition or TBoMS is set in the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1.

[0157] A TDRA table may be selected if the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 includes an element (or column, e.g., numberOfRepetitions) relating to the number of repetitions, or if an RRC parameter (e.g., pxsch-AggregationFactor) relating to the number of repetitions is set on terminal 200. Alternatively, a TDRA table may be selected if the TDRA table includes an element (or column, e.g., numberOfSlotsTBoMS) relating to the number of TBoMS slots. Furthermore, a TDRA table may be selected if the TDRA table includes both an element (or column, e.g., numberOfRepetitions) relating to the number of repetitions and an element (or column, e.g., numberOfSlotsTBoMS) relating to the number of TBoMS slots.

[0158] On the other hand, if the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 does not include elements related to the number of repetitions or the number of TBoMS slots, a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 may be selected.

[0159] Thus, terminal 200 quasi-statically switches between a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and a TDRA table used for single-TB scheduling for DCI format 0-1 / 1-1, depending on whether Repetition or TBoMS is set in the TDRA table.

[0160] According to this embodiment, by using a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., pxsch-TimeDomainAllocationListForMultPxSCHForDCI-z-3), it is not necessary to simultaneously enable multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0161] Furthermore, according to this embodiment, it is possible to switch between single TB scheduling to which Repetition or TBoMS can be applied and multiple TB scheduling without explicit notification, depending on whether or not Repetition or TBoMS is set in the TDRA table.

[0162] (Embodiment 7) For example, the ASN.1 (Abstract Syntax Notation One) signaling of NR can be quite flexible. Therefore, the number of elements in each row of the TDRA table and the information notified by the elements do not necessarily have to be the same.

[0163] Therefore, in this embodiment, a single TDRA table is newly defined and set as a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, which includes each row of the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 and each row of the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3.

[0164] For example, terminal 200 may determine the allocation of time domain resources using a TDRA table that includes at least a portion of the settings (e.g., a TDRA table) for time domain resource allocation used for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, and at least a portion of the settings (e.g., a TDRA table) for time domain resource allocation used for single-TB scheduling for DCI format 0-1 / 1-1.

[0165] In the TDRA field of DCI format 0-3 / 1-3, the TDRA index for each cell is determined by notifying one of several TDRA index patterns (the patterns of TDRA indexes set for each of the multiple entries in the joint TDRA table) that are configured in the joint TDRA table. The TDRA index for each cell is a pointer to the corresponding index (e.g., time domain resource allocation) in the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3. Time domain resources are allocated by notifying one of the multiple TDRA patterns included in the joint TDRA table via the TDRA field.

[0166] Figures 14 and 15 show examples of TDRA tables in this embodiment.

[0167] The TDRA tables shown in Figures 14 and 15 include each row of the TDRA table used for single TB scheduling for DCI format 0-1 / 1-1 (e.g., indices #0 to #N-1 in Figure 14; indices #0, #2 to #N-1 in Figure 15) and each row of the TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., indices #N and above in Figure 14; index #1 in Figure 15).

[0168] According to this embodiment, by defining a TDRA table for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3, when applying multi-TB scheduling to each cell scheduled in multi-cell scheduling, it is not necessary to enable both multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multi-TB scheduling using DCI format 0-1 / 1-1 simultaneously. Therefore, the method according to this embodiment is consistent with the design guidelines in Release 19.

[0169] Furthermore, the TDRA table defined in this embodiment makes it possible to dynamically or quasi-statically switch between single TB scheduling to which Repetition or TBoMS can be applied, and multiple TB scheduling.

[0170] Furthermore, in this embodiment, dynamic switching of TDRA tables is possible using the TDRA field (joint TDRA index). Therefore, since it is not necessary to add a bit field to DCI for TDRA table selection, the increase in DCI overhead can be suppressed.

[0171] The embodiments of this disclosure have been described above.

[0172] Furthermore, the embodiments described above may be applied in combination.

[0173] Furthermore, the embodiments described above may be applied to either Repetition or TBoMS, or not to the other, or they may be applied to both Repetition and TBoMS. For example, different embodiments may be applied when applied to Repetition, when applied to TBoMS, and when applied to both Repetition and TBoMS (for example, TBoMS with Repetition).

[0174] [Example of operation of base station 100 and terminal 200] Figure 16 is a flowchart showing an example of operation of terminal 200.

[0175] Terminal 200 obtains information about the TDRA table from base station 100 (S101).

[0176] Terminal 200 receives DCI transmitted from base station 100 and obtains information about TDRA based on the information contained in DCI (S102).

[0177] Terminal 200 may perform the following processing (processing S103 to S108) for each scheduled cell (for example, cell #n).

[0178] For example, terminal 200 determines whether a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 has been set up (S103).

[0179] If a TDRA table for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 is configured (S103: Yes), the terminal 200 determines (or selects) the TDRA table to use, for example, based on one of the embodiments described above (S104). The terminal 200 determines the allocation of time domain resources corresponding to the notified TDRA index in the determined TDRA table (S105). Then, the terminal 200 receives a PDSCH or sends a PUSCH based on the determined allocation of time domain resources (S106).

[0180] On the other hand, if the TDRA table is not configured for multiple cell and multiple TB scheduling using DCI format 0-3 / 1-3 (S103: No), the terminal 200 determines, for example, the allocation of time domain resources corresponding to the notified TDRA index in the configured TDRA table (S107). Then, based on the determined allocation of time domain resources, the terminal 200 receives a PDSCH or sends a PUSCH (S108).

[0181] The above describes examples of the operation of the base station 100 and the terminal 200.

[0182] Thus, in non-limiting embodiments of this disclosure, the base station 100 determines the allocation of time-domain resources used for multi-cell and multi-TB scheduling according to DCI format 0-3 / 1-3, and transmits a signal (e.g., PDSCH transmission) or receives a signal (e.g., PUSCH reception) based on the determined allocation of time-domain resources. The terminal 200 also determines the allocation of time-domain resources used for multi-cell and multi-TB scheduling based on DCI format 0-3 / 1-3, and transmits a signal (e.g., PUSCH transmission) or receives a signal (e.g., PDSCH reception) based on the determined allocation of time-domain resources.

[0183] Here, the configuration of time domain resources used for multi-cell and multi-TB scheduling using DCI format 0-3 / 1-3 (e.g., TDRA table) differs from the configuration of time domain resource allocation used for multi-TD scheduling in DCI format 0-1 / 1-1 (e.g., TDRA table).

[0184] This prevents the simultaneous activation of multiple-cell and multiple-TB scheduling using DCI format 0-3 / 1-3 and single-cell and multiple-TB scheduling using DCI format 0-1 / 1-1 when applying multiple-TB scheduling to each scheduled cell in multiple-cell scheduling. Therefore, according to non-limiting embodiments of this disclosure, the efficiency of wireless communication can be improved.

[0185] [Base Station Configuration] Figure 17 is a block diagram showing an example configuration of a base station 100. In Figure 17, the base station 100 includes a control unit 101, a higher-level control signal generation unit 102, a downlink control information generation unit 103, an encoding unit 104, a modulation unit 105, a signal allocation unit 106, a transmission unit 107, a reception unit 108, an extraction unit 109, a demodulation unit 110, and a decoding unit 111.

[0186] At least one of the transmitting unit 107 and receiving unit 108 shown in Figure 17 may be included in the communication unit shown in Figure 8. Also, at least one of the control unit 101, higher-level control signal generation unit 102, downlink control information generation unit 103, encoding unit 104, modulation unit 105, signal allocation unit 106, receiving unit 108, extraction unit 109, demodulation unit 110, and decoding unit 111 shown in Figure 17 may be included in the control unit shown in Figure 8.

[0187] The control unit 101 determines at least one of the following: information regarding multiple cell scheduling and multiple TB scheduling in each cell, and information regarding the allocation of time domain resources. The determined information is then output to at least one of the higher-level control signal generation unit 102 and the downlink control information generation unit 103. The information regarding multiple cell scheduling and multiple TB scheduling in each cell may include, for example, information regarding the number of cells that can be allocated and the number of TBs that can be allocated. The information regarding the allocation of time domain resources may include, for example, the information regarding the TDRA table described above.

[0188] Furthermore, the control unit 101 determines, for example, information regarding downlink reception (e.g., PDSCH reception) or uplink transmission (e.g., PUSCH transmission) to the terminal 200, and outputs the determined information to at least one of the higher-level control signal generation unit 102 and the downlink control information generation unit 103. The information regarding PDSCH reception and PUSCH transmission may include, for example, information regarding the TDRA table, information regarding frequency domain resources, information regarding MCS (Modulation and Coding Scheme), or information regarding retransmission control (e.g., NDI (New Data Indicator), RV (Redundancy Version), HARQ process number, etc.).

[0189] Furthermore, the control unit 101 determines, for example, information related to the downlink signal for transmitting downlink data signals, upper-layer control signals, or downlink control information (for example, coding and modulation scheme (MCS) and radio resource allocation), and outputs the determined information to the coding unit 104, the modulation unit 105, and the signal allocation unit 106. In addition, the control unit 101 outputs, for example, information related to the downlink signal (for example, data signals or upper-layer control signals) to the downlink control information generation unit 103.

[0190] Furthermore, the control unit 101 determines information related to the uplink signal transmitted by the terminal 200 (for example, MCS and wireless resource allocation), and outputs the determined information to the downlink control information generation unit 103, extraction unit 109, demodulation unit 110, and decoding unit 111.

[0191] The higher-level control signal generation unit 102 generates a higher-level control signal bit sequence based on information input from the control unit 101, for example, and outputs the higher-level control signal bit sequence to the encoding unit 104.

[0192] The downlink control information generation unit 103 generates a downlink control information (e.g., DCI) bit sequence based on information input from the control unit 101, according to the method described above, and outputs the generated DCI bit sequence to the encoding unit 104. Note that the control information may also be transmitted to multiple terminals.

[0193] The encoding unit 104 encodes, for example, the downlink data signal, the bit sequence input from the higher-level control signal generation unit 102, or the DCI bit sequence input from the downlink control information generation unit 103, based on the information input from the control unit 101. The encoding unit 104 outputs the encoded bit sequence to the modulation unit 105.

[0194] The modulation unit 105 modulates the encoded bit sequence input from the encoding unit 104 based on information input from the control unit 101, and outputs the modulated signal (for example, a symbol sequence) to the signal assignment unit 106.

[0195] The signal assignment unit 106 maps a sequence of symbols (including, for example, a downlink data signal or a control signal) input from the modulation unit 105 to a radio resource, based on information indicating the radio resource input from the control unit 101, for example. The signal assignment unit 106 outputs the signal of the downlink to which the signal has been mapped to the transmission unit 107.

[0196] The transmitting unit 107 performs, for example, a transmission waveform generation process such as orthogonal frequency division multiplexing (OFDM) on the signal input from the signal assignment unit 106. Furthermore, in the case of OFDM transmission that adds a cyclic prefix (CP), the transmitting unit 107 performs an inverse fast Fourier transform (IFFT) on the signal and adds the CP to the signal after the IFFT. The transmitting unit 107 also performs RF processing on the signal, such as D / A conversion or upconversion, and transmits the wireless signal to the terminal 200 via the antenna.

[0197] The receiving unit 108 performs RF processing, such as downconverting or A / D conversion, on the uplink signal from the terminal 200 received via the antenna. In the case of OFDM transmission, the receiving unit 108 also performs Fast Fourier Transform (FFT) processing on the received signal and outputs the resulting frequency domain signal to the extraction unit 109.

[0198] The extraction unit 109, for example, based on information input from the control unit 101, extracts the portion of the radio resource from the received signal input from the receiving unit 108 in which an uplink signal (e.g., PUSC) has been transmitted, and outputs the extracted portion of the radio resource to the demodulation unit 110.

[0199] The demodulation unit 110 demodulates the uplink signal (e.g., PUSCH) input from the extraction unit 109 based on information input from the control unit 101, for example. The demodulation unit 110 outputs the demodulation result to the decoding unit 111, for example.

[0200] The decoding unit 111 performs error-correcting decoding of the uplink signal (e.g., PUSCH) based on information input from the control unit 101 and the demodulation result input from the demodulation unit 110, and obtains the decoded received bit sequence (e.g., UL data signal).

[0201] [Terminal Configuration] Figure 18 is a block diagram showing an example configuration of a terminal 200 according to one embodiment of the present disclosure. For example, in Figure 18, the terminal 200 includes a receiving unit 201, an extraction unit 202, a demodulation unit 203, a decoding unit 204, a control unit 205, an encoding unit 206, a modulation unit 207, a signal assignment unit 208, and a transmission unit 209.

[0202] Note that at least one of the receiving unit 201 and transmitting unit 209 shown in Figure 18 may be included in the communication unit shown in Figure 9. Also, at least one of the extraction unit 202, demodulation unit 203, decoding unit 204, control unit 205, encoding unit 206, modulation unit 207, signal allocation unit 208, and transmitting unit 209 shown in Figure 18 may be included in the control unit shown in Figure 9.

[0203] The receiving unit 201 receives, for example, a downlink signal (e.g., downlink data signal or downlink control information) from the base station 100 via an antenna, and performs RF processing such as downconverting or A / D conversion on the wirelessly received signal to obtain a received signal (baseband signal). In addition, when the receiving unit 201 receives an OFDM signal, it performs FFT processing on the received signal to convert the received signal into the frequency domain. The receiving unit 201 outputs the received signal to the extraction unit 202.

[0204] The extraction unit 202, for example, based on information about the wireless resource of the downlink control information input from the control unit 205, extracts the portion of the wireless resource that may contain downlink control information from the received signal input from the receiving unit 201 and outputs it to the demodulation unit 203. The extraction unit 202 also extracts the portion of the wireless resource that contains the downlink data signal from the received signal based on information about the wireless resource of the data signal input from the control unit 205 and outputs it to the demodulation unit 203.

[0205] The demodulation unit 203 demodulates the signal (e.g., PDCCH or PDSCH) input from the extraction unit 202 based on information input from the control unit 205, and outputs the demodulation result to the decoding unit 204.

[0206] The decoding unit 204 uses, for example, the information input from the control unit 205 and the demodulation result input from the demodulation unit 203 to perform error-corrected decoding of PDCCH or PDSCH, and obtains, for example, downlink received data, upper-layer control signals, or downlink control information. The decoding unit 204 outputs the upper-layer control signals and downlink control information to the control unit 205. The decoding unit 204 may also generate an ACK / NACK signal based on the decoding result of the downlink received data.

[0207] The control unit 205 identifies radio resources (e.g., time-domain resources) for PDSCH reception and PUSCH transmission according to the method described above, based on information regarding multiple cell scheduling and multiple TB scheduling in each cell, and radio resource allocation information (e.g., information regarding the allocation of time-domain resources), obtained from signals input from the decoding unit 204 (e.g., upper-layer control signals or downlink control information). The control unit 205 outputs the identified information to, for example, the encoding unit 206, the signal allocation unit 208, the extraction unit 202, the demodulation unit 203, and the decoding unit 204.

[0208] The encoding unit 206 encodes the uplink signal (for example, the uplink data signal (UL data signal)) based on information input from the control unit 205. The encoding unit 206 outputs the encoded bit sequence to the modulation unit 207.

[0209] The modulation unit 207 modulates, for example, the encoded bit sequence input from the encoding unit 206, and outputs the modulated signal (symbol sequence) to the signal assignment unit 208.

[0210] The signal assignment unit 208 maps the signal (e.g., a sequence) input from the modulation unit 207 to a wireless resource, for example, based on information input from the control unit 205. The signal assignment unit 208 outputs the uplink signal to the transmission unit 209, for example, the signal to which the signal has been mapped.

[0211] The transmitting unit 209 generates a transmission signal waveform, such as OFDM, from the signal input from the signal assignment unit 208. Furthermore, in the case of OFDM transmission using CP, for example, the transmitting unit 209 performs IFFT processing on the signal and adds CP to the signal after IFFT. Alternatively, when the transmitting unit 209 generates a single-carrier waveform, a DFT unit may be added, for example, after the modulation unit 207 or before the signal assignment unit 208 (not shown). The transmitting unit 209 also performs RF processing, such as D / A conversion and upconversion, on the transmission signal and transmits the radio signal to the base station 100 via the antenna.

[0212] The above describes various embodiments relating to one non-limiting embodiment of the present disclosure.

[0213] In this disclosure, the signals / messages / signaling used for notification may be control plane messages (e.g., UCI or MAC-CE), RRC signals, or physical layer signaling such as DCI notification.

[0214] Furthermore, the values ​​of parameters used in the above embodiment, such as the number of bits (field size), number of cells, number of TBs, subcarrier interval, number of cell groups, and time-domain resources (e.g., K0 / K1, SLIV, mapping type, number of repetitions), are merely examples and may be other values. Also, the DCI format used in the above embodiment is merely an example and may be other formats or names.

[0215] (Supplement) Information indicating whether the terminal 200 supports each of the embodiments described above and each supplement may be transmitted (or notified) from the terminal 200 to the base station 100 as, for example, capability information or capability parameters of the terminal 200.

[0216] The capability information may include an information element (IE) that individually indicates whether the terminal 200 supports at least one of the functions, operations, or processes described in each of the embodiments, modifications, and supplements described above. Alternatively, the capability information may include an information element that indicates whether the terminal 200 supports any two or more combinations of the functions, operations, or processes described in each of the embodiments, modifications, and supplements described above.

[0217] The base station 100 may, for example, determine (or decide or assume) which functions, operations, or processes the source terminal 200 supports (or does not support) based on capability information received from the terminal 200. The base station 100 may perform operations, processes, or controls in accordance with the determination result based on the capability information. For example, the base station 100 may control the process related to the allocation of time-domain resources based on capability information received from the terminal 200.

[0218] Furthermore, the fact that terminal 200 does not support some of the functions, operations, or processes described in each embodiment, each modification, and each supplement described above may be interpreted as the terminal 200 having restrictions on such some functions, operations, or processes. For example, information or requests regarding such restrictions may be notified to base station 100.

[0219] Information regarding the capabilities or limitations of terminal 200 may be defined, for example, in a standard, or it may be implicitly communicated to base station 100 in association with information known at base station 100 or information transmitted to base station 100.

[0220] The embodiments, modifications, and supplementary information relating to one non-limiting embodiment of this disclosure have been described above.

[0221] (Control Signals) In this disclosure, the downlink control signals (or downlink control information) relating to one embodiment of this disclosure may be, for example, signals (or information) transmitted in a Physical Downlink Control Channel (PDCCH) at the physical layer, or signals (or information) transmitted in a Medium Access Control Control Element (MAC CE) or Radio Resource Control (RRC) at a higher layer. Furthermore, the signals (or information) are not limited to being notified by downlink control signals, but may be predetermined in a specification (or standard), or may be pre-configured in base stations and terminals.

[0222] In this disclosure, the uplink control signal (or uplink control information) related to one embodiment of this disclosure may be, for example, a signal (or information) transmitted in the physical layer PUCCH, or a signal (or information) transmitted in the upper layer MAC CE or RRC. Furthermore, the signal (or information) is not limited to being notified by the uplink control signal, but may be predetermined in the specification (or standard), or may be pre-configured in the base station and terminal. In addition, the uplink control signal may be replaced with, for example, uplink control information (UCI), 1st stage sidelink control information (SCI), or 2nd stage SCI.

[0223] (Base Station) In one embodiment of the present disclosure, the base station may be a Transmission Reception Point (TRP), cluster head, access point, Remote Radio Head (RRH), eNodeB (eNB), gNodeB (gNB), Base Station (BS), Base Transceiver Station (BTS), master unit, gateway, etc. Also, in side-link communication, the terminal may assume the role of a base station. Alternatively, instead of a base station, there may be a relay device that relays communication between the upper node and the terminal. There may also be a roadside unit.

[0224] (Uplink / Downlink / Sidelink) An embodiment of the present disclosure may be applied to, for example, an uplink, a downlink, or a sidelink. For example, an embodiment of the present disclosure may be applied to a Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), Physical Random Access Channel (PRACH) of an uplink, a Physical Downlink Shared Channel (PDSCH), PDCCH, Physical Broadcast Channel (PBCH) of a downlink, or a Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Broadcast Channel (PSBCH) of a sidelink.

[0225] PDCCH, PDSCH, PUSCH, and PUCCH are examples of downlink control channels, downlink data channels, uplink data channels, and uplink control channels, respectively. PSCCH and PSSCH are examples of sidelink control channels and sidelink data channels. PBCH and PSBCH are examples of broadcast channels, and PRACH is an example of a random access channel.

[0226] (Data Channel / Control Channel) One embodiment of the present disclosure may be applied to either a data channel or a control channel, for example. For example, the channel in one embodiment of the present disclosure may be replaced with any of the data channels PDSCH, PUSCH, PSSCH, or the control channels PDCCH, PUCCH, PBCH, PSCCH, PSBCH.

[0227] (Reference Signal) In one embodiment of the present disclosure, the reference signal is, for example, a signal known to both the base station and the mobile station, and may be called a Reference Signal (RS) or pilot signal. The reference signal may be any of the following: Demodulation Reference Signal (DMRS), Channel State Information - Reference Signal (CSI-RS), Tracking Reference Signal (TRS), Phase Tracking Reference Signal (PTRS), Cell-specific Reference Signal (CRS), or Sounding Reference Signal (SRS).

[0228] (Time Interval) In one embodiment of the present disclosure, the unit of time resource is not limited to one or a combination of slots and symbols, but may be a time resource unit such as a frame, superframe, subframe, slot, time slot, subslot, minislot, or symbol, Orthogonal Frequency Division Multiplexing (OFDM) symbol, Single Carrier - Frequency Division Multiplexing Access (SC-FDMA) symbol, or any other time resource unit. Furthermore, the number of symbols contained in one slot is not limited to the number of symbols exemplified in the above embodiment, but may be any other number of symbols.

[0229] (Frequency Band) One embodiment of the present disclosure may be applied to either a licensed band or an unlicensed band.

[0230] (Communication) One embodiment of the present disclosure may be applied to any of the following: communication between a base station and a terminal (Uu-link communication), communication between terminals (Sidelink communication), V2X (Vehicle to Everything) communication, or communication between an Ambient IoT Reader and an Ambient IoT Device. For example, the channels of the present disclosure may be replaced with PSCCH, PSSCH, PSFCH (Physical Sidelink Feedback Channel), PSBCH, PRDCH (Physical Reader-to-Device Channel), PDRCH (Physical Device-to-Reader Channel), PDCCH, PUCCH, PDSCH, PUSCH, or PBCH. For example, the control information in one embodiment of the present disclosure may be replaced with any of DCI, UCI, SCI (Sidelink Control Information), R2D Control Information, or D2R Control Information.

[0231] Furthermore, one embodiment of this disclosure may be applied to any of the following: a terrestrial network, a satellite, or a non-terrestrial network (NTN) using a high-altitude pseudo-satellite (HAPS). Also, one embodiment of this disclosure may be applied to terrestrial networks with large cell sizes, ultra-wideband transmission networks, and other networks where transmission delay is large relative to symbol length or slot length.

[0232] (SBFD) In ​​one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may also be applied to symbols (e.g., SBFD symbols) on which SBFD (Subband non-overlapping full duplex, Subband full duplex) operation or control is performed. In an SBFD symbol, a frequency domain (or frequency resource, frequency band) is divided into multiple frequency domains (e.g., also called subbands, RB sets, subbands, or sub-BWPs (Bandwidth parts)). A terminal transmits and receives in different directions (e.g., downlink or uplink) on a subband basis. In an SBFD symbol, a terminal may transmit and receive in either the uplink or downlink direction only, and not in the other direction. On the other hand, a base station may be able to transmit and receive both uplink and downlink simultaneously. An SBFD symbol may have a smaller frequency domain available for downlink transmission compared to a symbol that transmits and receives only downlink. Similarly, an SBFD symbol may have a smaller frequency domain available for uplink transmission compared to a symbol that transmits and receives only uplink.

[0233] Furthermore, in the SBFD symbol, a terminal may transmit and receive both uplink and downlink simultaneously. In this case, the frequency domains in which the terminal transmits and the frequency domains in which it receives may not be adjacent, and a frequency gap (also called a frequency interval) may be maintained between them.

[0234] Furthermore, sidelink transmission and reception may be included as different transmission and reception directions for each subband unit, which is a divided region.

[0235] (XDD: cross division duplex) In one embodiment of the present disclosure, the operation for uplink, downlink, and sidelink symbols may be applied to symbols (e.g., full duplex symbols) on which full duplex operation or control is performed. In full duplex symbols, both the terminal and the base station can transmit and receive uplink and downlink simultaneously. In full duplex symbols, the terminal and base station may transmit and receive simultaneously in the available frequency domain (or frequency resource, frequency band), or they may transmit and receive simultaneously in some frequency domains (i.e., they may transmit or receive in other frequency domains). In this case, the frequency domain on which the base station or terminal transmits and the frequency domain on which it receives may not be adjacent, and a frequency gap (also called a frequency gap) may be maintained between them. Alternatively, for example, to reduce interference, either the terminal or the base station may transmit and receive simultaneously (i.e., the other may transmit or receive).

[0236] Furthermore, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks. Also, full duplex operation may be applied to operations where the terminal can simultaneously transmit and receive sidelinks and uplinks or downlinks.

[0237] (Antenna Port) In one embodiment of the present disclosure, an antenna port refers to a logical antenna (antenna group) composed of one or more physical antennas. For example, an antenna port does not necessarily refer to a single physical antenna, but may refer to an array antenna composed of multiple antennas. For example, the number of physical antennas that make up an antenna port is not specified, and it may be defined as the smallest unit on which a terminal station can transmit a reference signal. An antenna port may also be defined as the smallest unit on which the weighting of a precoding vector is multiplied.

[0238] (Ambient IoT) In one embodiment of this disclosure, the terminal and base station may be replaced with either an Ambient IoT Device or an Ambient IoT Reader. The Ambient IoT Device may be a wireless communication device that has backscattering capabilities or a transmit / receive bandwidth of a few resource blocks or less. The Ambient IoT Reader may be a wireless communication device that has the capability to communicate with the Ambient IoT Device. The Ambient IoT Device may also be called an Ambient IoT terminal, IoT terminal, LPWA terminal, or tag.

[0239] <5G NR System Architecture and Protocol Stack> The 5G NR system architecture as a whole assumes an NG-RAN (Next Generation - Radio Access Network) with gNBs. The gNBs provide the UE-side termination for the user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocols of NG radio access. The gNBs are connected to each other by Xn interfaces. Furthermore, the gNBs are connected to the NGC (Next Generation Core) by Next Generation (NG) interfaces, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity performing the AMF) by NG-C interfaces, and to the UPF (User Plane Function) (e.g., a specific core entity performing the UPF) by NG-U interfaces. The NG-RAN architecture is shown in Figure 19 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0240] <RRC Connection Setup and Reconfiguration Procedure> This describes the communication between the UE, gNB, and AMF (5GC entity) when the UE transitions from RRC_IDLE to RRC_CONNECTED in the NAS section (see TS 38.300 v15.6.0).

[0241] RRC is a higher-layer signaling (protocol) used for configuring the UE and gNB. The AMF prepares the UE context data (which includes, for example, the PDU session context, security key, UE Radio Capability, UE Security Capabilities, etc.) and sends it to the gNB along with an Initial Context Setup Request. The gNB then activates AS security together with the UE. This is done by the gNB sending a SecurityModeCommand message to the UE, and the UE responding to the gNB with a SecurityModeComplete message. Subsequently, the gNB sends an RRCReconfiguration message to the UE, and upon receiving an RRCReconfigurationComplete from the UE, the gNB reconfigures itself to set up the Signaling Radio Bearer 2 (SRB2) and Data Radio Bearer (DRB). For signaling-only connections, the SRB2 and DRB are not set up, so the RRCReconfiguration step is omitted. Finally, the gNB notifies the AMF that the setup procedure is complete with an Initial Context Setup Response.

[0242] Accordingly, this disclosure provides a 5th Generation Core (5GC) entity (e.g., AMF, SMF, etc.) comprising a control circuit that establishes a Next Generation (NG) connection with gNodeB during operation, and a transmission unit that sends an initial context setup message to gNodeB via the NG connection during operation so that a signaling radio bearer between gNodeB and User Equipment (UE) is set up. Specifically, gNodeB transmits Radio Resource Control (RRC) signaling, including a Resource Allocation Setting Information Element (IE), to the UE via the signaling radio bearer. The UE then transmits on the uplink or receives on the downlink based on the resource allocation setting.

[0243] <QoS Control> The 5G QoS (Quality of Service) model is based on QoS flows and supports both QoS flows where a guaranteed flow bit rate is required (GBR: Guaranteed Bit Rate QoS flows) and QoS flows where a guaranteed flow bit rate is not required (non-GBR QoS flows). Therefore, at the NAS level, a QoS flow is the finest granularity of QoS within a PDU session. QoS flows are identified within a PDU session by a QoS Flow ID (QFI: QoS Flow ID) carried in the encapsulation header via the NG-U interface.

[0244] For each UE, the 5GC establishes one or more PDU sessions. For each UE, the NG-RAN establishes, for example, at least one Data Radio Bearers (DRB) in accordance with the PDU session. Additional DRBs for the QoS flow of that PDU session can be configured later (when this is done is up to the NG-RAN). The NG-RAN maps packets belonging to various PDU sessions to various DRBs. NAS-level packet filters in the UE and 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.

[0245] (Open-RAN) The base station described in each embodiment (for example, a 5G NR base station called a gNB) may consist of three functional modules: a Centralized Unit (CU), a Distributed Unit (DU), and a Radio Unit (RU).

[0246] CU may be referred to as, for example, a central node, aggregation node, central station, aggregation station, or central unit. DU may be referred to as, for example, an O-DU (O-RAN Distributed Unit), a distributed node, a distributed station, or a distributed unit. RU may be referred to as, for example, an O-RU (O-RAN Radio Unit), a radio device, a radio node, a radio station, an antenna unit, or a radio unit.

[0247] The functional division configuration (or functional division point) between CU, DU, and RU has multiple division options defined. The term "functional division point" is sometimes referred to as "split," "option," or "split option."

[0248] Examples of "splitting options" include the following splitting options 1 to 8. The functions of the base station described in each embodiment may be split into CU, DU, and RU functions according to any of the following splitting options 1 to 8. For example, CU, DU, and RU may be functionally split individually, or functional split may occur only between CU and DU, or only between DU and RU. (1) Splitting option 1: Between RRC (radio resource control) and PDCP (2) Splitting option 2: Between PDCP and RLC (High-RLC) (3) Splitting option 3: Between High-RLC and Low-RLC (4) Splitting option 4: Between RLC (Low-RLC) and MAC (High-MAC) (5) Splitting option 5: Between High-MAC and Low-MAC (6) Splitting option 6: Between MAC (Low-MAC) and PHY (High-PHY) (7) Splitting option 7: Between High-PHY and Low-PHY (8) Splitting option 8: Between PHY (Low-PHY) and RF

[0249] The functional division point between the CU and O-DU may be Split Option 2. The section between the CU and O-DU is called the midhaul, and the F1 interface is defined by 3GPP. The section between the O-DU and O-RU is called the fronthaul, and its functional division point may be Split Option 7-2x, which has been adopted as the O-RAN fronthaul specification.

[0250] Figure 20 shows an example of splitting the base station functions of a gNB into CU, O-DU, and O-RU using Split Option 2 and Split Option 7-2x.

[0251] The CU may, for example, include RRC (radio resource control) functionality, SDAP (service data adaptation protocol) functionality, and PDCP (packet data convergence protocol) functionality.

[0252] The O-DU may include, for example, RLC (radio link control) functionality, MAC functionality, and high-level physical layer (HIGH-PHY) functionality. The HIGH-PHY functionality may also include encoding functionality, scrambling functionality, modulation functionality, layer mapping functionality, precoding functionality, and RE (resource element) mapping functionality for downlink (DL) transmission. The HIGH-PHY functionality may also include decoding functionality, descrambling functionality, demodulation functionality, layer demapping functionality, and RE (resource element) demapping functionality for uplink (UL) reception.

[0253] The O-RU may, for example, be equipped with a LOW-PHY function and an RF function. The LOW-PHY function may also be equipped with a beamforming function, an IFFT (Inverse First Fourier Transform) + CP (Cyclic Prefix) application function, and a D / A (Digital to Analog) conversion function for downlink transmission. The LOW-PHY function may also be equipped with an A / D (Analog to Digital) conversion function, a CP removal + FFT (First Fourier Transform) function, and a beamforming function for uplink reception.

[0254] If the O-DU does not have a precoding function, the O-RU may have a precoding function.

[0255] O-RU may also include functions related to LBT (listen before talk).

[0256] In Split Option 7-2x, eCPRI (Evolved Common Public Radio Interface) is specified as the communication method between the O-DU and O-RU. In Split Option 7-2x, eCPRI transmits and receives not only the sampling sequence of the in-phase (I) and quadrature (Q) components of the OFDM signal in the frequency domain, but also information used for beamforming in the antenna and time synchronization signals.

[0257] The information transmitted by the signals described in each embodiment (PDCCH, PUCCH, PDSCH, PUSCH, MAC CE, RRC, etc.) may be transmitted between the O-DU and O-RU via the eCPRI's User Plane (U-Plan) or Control Plane (C-Plane).

[0258] If the functions described in each embodiment are executed in the O-RU by functional partitioning, the O-DU may control the O-RU by transmitting information for controlling the functions via a control signal (e.g., eCPRI) between the O-DU and the O-RU.

[0259] If the functions described in each embodiment are executed in the O-DU by functional partitioning, the O-RU may receive the result of the execution of the function in the O-DU via a control signal (e.g., eCPRI) and control the O-RU based on the received result.

[0260] The CU, O-DU, and O-RU may be deployed in physically different devices connected by optical fibers or the like, or some or all of their functions may be deployed in the same physical device.

[0261] CU and O-DU may be logical entities implemented as software running on a server such as a cloud, as a virtualized RAN (virtual Radio Access Network: vRAN). Furthermore, some or all of the functions of CU and O-DU may be provided as a service of virtualized network functions (NFV).

[0262] The transceiver does not have to be a wireless transceiver; for example, it may be a network transceiver, an optical transceiver, etc. The wireless resources allocated by the O-DU may be resources for wireless communication between the O-RU and the UE.

[0263] This disclosure can be implemented using software, hardware, or software integrated with hardware.

[0264] Each functional block used in the description of the above embodiments may be implemented partially or entirely as an integrated circuit (LSI), and each process described in the above embodiments may be controlled partially or entirely by a single LSI or a combination of LSIs. An LSI may consist of individual chips, or it may consist of a single chip that includes some or all of the functional blocks. An LSI may have data inputs and outputs. Depending on the degree of integration, LSIs may also be referred to as ICs, system LSIs, super LSIs, or ultra LSIs.

[0265] The integrated circuit implementation method is not limited to LSIs; it may also be implemented using dedicated circuits, general-purpose processors, or dedicated processors. Furthermore, a Field Programmable Gate Array (FPGA) that can be programmed after LSI manufacturing, or a reconfigurable processor that allows for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used. This disclosure may be implemented as digital or analog processing.

[0266] Furthermore, if advancements in semiconductor technology or other derived technologies lead to the emergence of integrated circuit technologies that can replace LSIs, then naturally, it would be possible to use those technologies to integrate functional blocks. The application of biotechnology, for example, is a possibility.

[0267] This disclosure is applicable to all types of devices, systems, and equipment having communication capabilities (collectively referred to as communication equipment). Communication equipment may include a radio transceiver and a processing / control circuit. The radio transceiver may include a receiver and a transmitter, or both as functions. The radio transceiver (transmitter, receiver) may include an RF (Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator, or similar. Non-exclusive examples of communication devices include telephones (mobile phones, smartphones, etc.), tablets, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still / video cameras, etc.), digital players (digital audio / video players, etc.), wearable devices (wearable cameras, smartwatches, tracking devices, etc.), game consoles, digital book readers, telehealth / telemedicine devices, vehicles or mobile transport with communication capabilities (cars, airplanes, ships, etc.), and combinations of the above-mentioned devices.

[0268] Communication devices are not limited to portable or movable devices, but also include all kinds of non-portable or fixed devices, devices, and systems, such as smart home devices (appliances, lighting fixtures, smart meters or measuring instruments, control panels, etc.), vending machines, and any other "things" that may exist on an IoT (Internet of Things) network.

[0269] Communication includes data communication via cellular systems, wireless LAN systems, and communication satellite systems, as well as data communication using combinations of these.

[0270] Furthermore, the communication device also includes devices such as controllers and sensors that are connected to or linked to a communication device that performs the communication functions described in this disclosure. For example, this includes controllers and sensors that generate control signals and data signals used by the communication device that performs the communication functions of the communication device.

[0271] Furthermore, communication equipment includes infrastructure facilities such as base stations, access points, and any other devices, devices, and systems that communicate with or control the aforementioned non-limited types of equipment.

[0272] A communication device according to one embodiment of the present disclosure comprises a control circuit that determines a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and a communication circuit that transmits or receives signals based on the first time-domain resource allocation.

[0273] In one embodiment of the present disclosure, the settings for the first time-domain resource allocation and the settings for the second time-domain resource allocation are tables containing patterns of multiple parameters relating to time-domain resources, and the control circuit switches between a first table relating to the first time-domain resource allocation used for scheduling the multiple cells and the multiple data channels in the first format and a second table relating to the second time-domain resource allocation used for scheduling a single data channel in the second format.

[0274] In one embodiment of the present disclosure, the control circuit switches between the first table and the second table based on dynamic notifications or settings.

[0275] In one embodiment of the present disclosure, the downlink control information in the first format includes a bit field indicating one of the first table and the second table selected.

[0276] In one embodiment of the present disclosure, a third table is defined, comprising a plurality of entries corresponding to each of the plurality of cells, wherein each entry includes identification information that identifies either the pattern included in the first table or the second table, and an element that indicates the table selected from the first table and the second table, and the downlink control information of the first format includes information that identifies either the identification information and the pattern of the element set for each of the plurality of entries in the third table.

[0277] In one embodiment of the present disclosure, the first table includes the pattern relating to the scheduling of the plurality of cells and the plurality of data channels, and a pointer to the second table.

[0278] In one embodiment of the present disclosure, a third table is defined, comprising a plurality of entries corresponding to each of the plurality of cells, wherein each entry includes identification information that identifies any of the patterns included in a table formed by linking the first table and the second table, and the downlink control information in the first format includes information that identifies any of the patterns of the identification information set for each of the plurality of entries in the third table.

[0279] In one embodiment of the present disclosure, the control circuit switches between the first table and the second table based on a second parameter different from a first parameter relating to the allocation of time-domain resources.

[0280] In one embodiment of the present disclosure, the second parameter is at least one of the set of the plurality of cells, the combination of the plurality of cells, the number of the plurality of cells, and the subcarrier interval of the plurality of cells.

[0281] In one embodiment of the present disclosure, the control circuit switches between the first table and the second table based on a quasi-static notification or setting.

[0282] In one embodiment of the present disclosure, the control circuit switches between the first table and the second table based on whether or not a Repetition or Transport Block over Multiple Slot (TBoMS) is set in the second table used in scheduling a single data channel for the second format.

[0283] In one embodiment of the present disclosure, the control circuit determines the first time-domain resource allocation using a table that includes at least a portion of the settings for the first time-domain resource allocation used for scheduling the plurality of cells and the plurality of data channels in the first format, and at least a portion of the settings for the second time-domain resource allocation used for scheduling a single data channel in the second format.

[0284] A communication device according to one embodiment of the present disclosure comprises one or more processors and one or more memories coupled to the one or more processors for storing instructions, wherein the instructions cause the communication device to determine a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation is executable by the one or more processors in order to transmit or receive signals based on the first time-domain resource allocation, unlike the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format.

[0285] In a communication method according to one embodiment of the present disclosure, the communication device determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format, and transmits or receives signals based on the first time-domain resource allocation.

[0286] In one embodiment of the present disclosure, the method is controlled by an integrated circuit.

[0287] In one embodiment of the present disclosure, a communication method controlled by an integrated circuit, wherein the communication device determines a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and transmits or receives signals based on the first time-domain resource allocation.

[0288] In one embodiment of the present disclosure, an integrated circuit comprises a circuit that controls the determination of a first time-domain resource allocation used for scheduling a plurality of cells and scheduling a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and controls the transmission or reception of a signal based on the first time-domain resource allocation.

[0289] In one embodiment of the present disclosure, the integrated circuit comprises at least one input coupled to the circuit for inputting data, and at least one output coupled to the circuit for outputting data.

[0290] In one embodiment of the present disclosure, the circuit comprises a control circuit that determines a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and a communication circuit that transmits or receives a signal based on the first time-domain resource allocation.

[0291] In one embodiment of the present disclosure, a non-temporary computer-readable recording medium having content that causes a processing circuit to execute a method, wherein the method involves a communication device determining a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and the device transmits or receives signals based on the first time-domain resource allocation.

[0292] In the non-temporary computer-readable recording medium according to one embodiment of the present disclosure, the contents include configuration settings.

[0293] A communication device according to one embodiment of the present disclosure comprises a control circuit that determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format, and a communication circuit that transmits or receives signals based on the first time-domain resource allocation.

[0294] A communication device according to one embodiment of the present disclosure is a communication device comprising one or more processors and one or more memories coupled to the one or more processors for storing instructions, wherein the instructions cause the communication device to determine a first time-domain resource allocation used for scheduling a plurality of cells and scheduling a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation is executable by the one or more processors in order to transmit or receive a signal based on the first time-domain resource allocation, unlike the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format.

[0295] In a communication method according to one embodiment of the present disclosure, the communication device determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells, based on downlink control information in a first format. The setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format, and the device transmits or receives signals based on the first time-domain resource allocation.

[0296] In one embodiment of the present disclosure, the method is controlled by an integrated circuit.

[0297] In one embodiment of the present disclosure, a communication method controlled by an integrated circuit, wherein the communication device determines a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and transmits or receives signals based on the first time-domain resource allocation.

[0298] In one embodiment of the present disclosure, an integrated circuit comprises a circuit that controls the determination of a first time-domain resource allocation used for scheduling a plurality of cells and scheduling a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and controls the transmission or reception of a signal based on the first time-domain resource allocation.

[0299] In one embodiment of the present disclosure, the integrated circuit comprises at least one input coupled to the circuit for inputting data, and at least one output coupled to the circuit for outputting data.

[0300] In one embodiment of the present disclosure, the circuit comprises a control circuit that determines a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and a communication circuit that transmits or receives a signal based on the first time-domain resource allocation.

[0301] In one embodiment of the present disclosure, a non-temporary computer-readable recording medium having content that causes a processing circuit to execute a method, wherein the method involves a communication device determining a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format, and the transmission or reception of a signal is performed based on the first time-domain resource allocation.

[0302] In the non-temporary computer-readable recording medium according to one embodiment of the present disclosure, the contents include configuration settings.

[0303] All disclosures in the specification, drawings, and abstract contained in the Japanese application No. 2025-004627, filed on January 14, 2025, are incorporated herein by reference.

[0304] One embodiment of this disclosure is useful for wireless communication systems.

[0305] 100 Base station 101, 205 Control unit 102 Higher-level control signal generation unit 103 Downlink control information generation unit 104, 206 Encoding unit 105, 207 Modulation unit 106, 208 Signal allocation unit 107, 209 Transmitting unit 108, 201 Receiving unit 109, 202 Extraction unit 110, 203 Demodulation unit 111, 204 Decoding unit 200 Terminal

Claims

1. A communication device comprising: a control circuit that determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format; and a communication circuit that transmits or receives signals based on the first time-domain resource allocation.

2. The communication device according to claim 1, wherein the settings for the first time-domain resource allocation and the settings for the second time-domain resource allocation are tables containing patterns of multiple parameters relating to time-domain resources, and the control circuit switches between a first table relating to the first time-domain resource allocation used for scheduling the multiple cells and the multiple data channels according to the first format and a second table relating to the second time-domain resource allocation used for scheduling a single data channel according to the second format.

3. The communication device according to claim 2, wherein the control circuit switches between the first table and the second table based on dynamic notifications or settings.

4. The communication device according to claim 3, wherein the downlink control information in the first format includes a bit field indicating one of the first table and the second table.

5. A third table is defined, comprising a plurality of entries corresponding to each of the plurality of cells, wherein each entry includes identification information that identifies either the pattern included in the first table or the second table, and an element that indicates the table selected from the first table and the second table, and the downlink control information of the first format includes information that identifies either the identification information and the pattern of the element set for each of the plurality of entries in the third table, the communication device according to claim 3.

6. The communication device according to claim 3, wherein the first table includes the pattern relating to the scheduling of the plurality of cells and the plurality of data channels, and a pointer to the second table.

7. A third table is defined comprising a plurality of entries corresponding to each of the plurality of cells, wherein each entry includes identification information that identifies any of the patterns included in a table formed by linking the first table and the second table, and the downlink control information in the first format includes information that identifies any of the patterns of the identification information set for each of the plurality of entries in the third table, the communication device according to claim 3.

8. The communication device according to claim 3, wherein the control circuit switches the first table and the second table based on a second parameter different from a first parameter relating to the allocation of time-domain resources.

9. The communication device according to claim 8, wherein the second parameter is at least one of the set of the plurality of cells, the combination of the plurality of cells, the number of the plurality of cells, and the subcarrier spacing of the plurality of cells.

10. The communication device according to claim 2, wherein the control circuit switches between the first table and the second table based on a quasi-static notification or setting.

11. The communication device according to claim 10, wherein the control circuit switches between the first table and the second table based on whether or not a Repetition or Transport Block over Multiple Slot (TBoMS) is set in the second table used in scheduling a single data channel for the second format.

12. The communication device according to claim 1, wherein the control circuit determines the first time-domain resource allocation using a table that includes at least a portion of the settings for the first time-domain resource allocation used for scheduling the plurality of cells and the plurality of data channels in the first format, and at least a portion of the settings for the second time-domain resource allocation used for scheduling a single data channel in the second format.

13. A communication device comprising: one or more processors; and one or more memories coupled to the one or more processors for storing instructions, wherein the instructions cause the communication device to determine a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells based on downlink control information in a first format; the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format; and the setting of the first time-domain resource allocation is executable by the one or more processors to cause the communication device to transmit or receive signals based on the first time-domain resource allocation.

14. A communication method comprising: a communication device that determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format, and transmits or receives signals based on the first time-domain resource allocation.

15. A communication device comprising: a control circuit that determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells based on downlink control information in a first format, wherein the setting of the first time-domain resource allocation is different from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format; and a communication circuit that transmits or receives signals based on the first time-domain resource allocation.

16. A communication device comprising: one or more processors; and one or more memories coupled to the one or more processors for storing instructions, wherein the instructions cause the communication device to determine a first time-domain resource allocation used for scheduling a plurality of cells and a plurality of data channels in each of the plurality of cells, based on downlink control information in a first format; the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling a plurality of data channels in a second format different from the first format; and the setting of the first time-domain resource allocation is executable by the one or more processors to cause the communication device to transmit or receive signals based on the first time-domain resource allocation.

17. A communication device determines a first time-domain resource allocation used for scheduling multiple cells and multiple data channels in each of the multiple cells, based on downlink control information in a first format, and the setting of the first time-domain resource allocation differs from the setting of a second time-domain resource allocation used for scheduling multiple data channels in a second format different from the first format, and transmits or receives signals based on the first time-domain resource allocation.

Images