Communication device, communication method, and integrated circuit

Abstract

The present invention improves the efficiency of radio communication. According to the present invention, a terminal is equipped with: a control circuit that determines the size of one piece of downlink control information that instructs scheduling of a plurality of cells and a plurality of transport blocks in each of the plurality of cells on the basis of a second value different from a first value that is determined on the basis of the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks; and a receiving circuit that receives the downlink control information on the basis of the size.

Description

Communication devices, communication methods, and integrated circuits

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

[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),” September 2024.3GPP TS38.212, “NR Multiplexing and channel coding (Release 18),” September 2024.3GPP TS38.213, “NR Physical layer procedures for control (Release 18),” September 2024.3GPP TS38.214, “NR Physical layer procedures for data (Release 18),” September 2024.RP-242408, “New WID: Multi-carrier enhancements for NR Phase 2,” Lenovo, RAN#105, September 2024.R1-2408282, “Discussion on multi-cell scheduling with a single DCI,” Lenovo, RAN1#118bis, October 2024.

[0004] However, there is room for further consideration regarding ways to improve the efficiency of wireless communication.

[0005] Non-limiting embodiments of this disclosure contribute to the provision of communication devices, communication methods, and integrated circuits that can improve the efficiency of wireless communication.

[0006] A terminal according to one embodiment of the present disclosure comprises a control circuit that determines the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels; and a receiving circuit that receives the downlink control information based on the size.

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

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

[0009] Further advantages and effects in an embodiment of the present disclosure will be clarified from the specification and drawings. Such advantages and / or effects are provided by some embodiments and the features described in the specification and drawings respectively, but not all necessarily need to be provided in order to obtain one or more identical features.

[0010] Figures showing an example of multiple Transport Block (TB) scheduling, Figures showing an example of multi-cell scheduling, Figures showing an example of multi-cell scheduling, Figures showing an example of a combination of multi-cell scheduling and multiple TB scheduling, Figures showing an example of a Downlink Control Information (DCI) format in multiple TB scheduling, Figures showing an example of a DCI format in multi-cell scheduling, Figures showing an example of a DCI format when applying multiple TB scheduling to each cell scheduled in multi-cell scheduling, Block diagram showing a partial configuration example of a base station, Block diagram showing a partial configuration example of a terminal, Figures showing an example of setting an information field of a DCI format, Figures showing an example of setting an information field of a DCI format, Figures showing an example of setting an information field of a DCI format, Figures showing an example of setting an information field of a DCI format, Sequence diagram showing an operation example of a base station and a terminal, Sequence diagram showing an operation example of a base station and a terminal, Block diagram showing a configuration example of a base station, Block diagram showing a configuration example of a terminal, Diagram of an exemplary architecture of a 3GPP NR system, Diagram of an exemplary functional split in 5G O-RAN

[0011] Hereinafter, embodiments of the present disclosure will be described in detail 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 multi-TB scheduling. As shown in Figure 1, a downlink control signal (e.g., DCI: Downlink Control Information) including scheduling information such as resource allocation from a base station (also referred to as a gNB, for example) is transmitted by, for example, PDCCH. A terminal receives a downlink data channel (e.g., PDSCH: Physical Downlink Shared Channel) or transmits an uplink data channel (e.g., PUSCH: Physical Uplink Shared Channel) according to the resource allocation indicated by DCI on the PDCCH.

[0015] For example, one PUSCH or PDSCH (also represented as PUSCH / PDSCH, for example) scheduled by one DCI is one, and the number of TBs included in one PUSCH / PDSCH is one or two when transmitted by spatial multiplexing in the same time-frequency resource. On the other hand, in multi-TB scheduling, as shown in Figure 1, it is possible to allocate (schedule) a plurality of PUSCH / PDSCHs (e.g., TB#1 and TB#2) by one DCI.

[0016] [Multi-cell scheduling] In 5G, with the expansion of the 5G network and the reduction of 3G or 4G operations, an increase in the opportunity to divert the frequency bands used by 3G or 4G (e.g., Frequency range 1 (FR1) band) to 5G is expected. In such an assumption, different frequencies used in 5G may often be, for example, fragmented and narrow-band bands. Therefore, multi-carrier operation combining these multiple bands is expected.

[0017] 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 to multiple cells using a single DCI (for example, called "multi-cell scheduling").

[0018] 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).

[0019] This concludes our explanation of multiple cell scheduling.

[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] 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 3). 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.

[0022] Furthermore, in Release 19, for example, as shown in Figure 4, 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 4, 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.

[0023] However, the DCI design when applying multiple TB scheduling to each scheduled cell in a multi-cell scheduling scenario warrants further consideration.

[0024] [Relationship between multiple TB scheduling and DCI field size] For example, in multiple TB scheduling in single-cell scheduling, it is possible to assign multiple PUSCH / PDSCH using "DCI format 0-1" or "DCI format 1-1" (see, for example, Non-Patent Documents 2 or 4). When assigning multiple PUSCH / PDSCH in DCI format 0-1 or DCI format 1-1 (also expressed as, for example, "DCI format 0-1 / 1-1"), the correspondence between the settings of some information fields in DCI format 0-1 / 1-1 and the multiple PUSCH / PDSCH is as follows.

[0025] <Frequency Domain Resource Allocation (FDRA) field> The size of the FDRA field is determined by the size of the bandwidth used by the terminal (e.g., Active Bandwidth Part (BWP)) or the resource allocation method. Furthermore, a common value is applied to multiple PUSCH / PDSCH devices in the FDRA field.

[0026] In other words, the size of the FDRA field does not depend on the number of PUSCH / PDSCH allocated by multi-TB scheduling.

[0027] <Modulation and Coding Scheme (MCS) Field> The size of the MCS field is 5 bits if there is one TB in a single PUSCH / PDSCH. If there are two TBs in a single PUSCH / PDSCH that are spatially multiplexed onto the same time and frequency resource, an MCS field is set individually for each TB, and the size of the MCS field for each TB is 5 bits.

[0028] In other words, the size of the MCS field does not depend on the number of PUSCH / PDSCH allocated by multiple TB scheduling.

[0029] <New Data Indicator(NDI)フィールド>The size of the NDI field may depend on the maximum number of PUSCH / PDSCH that can be scheduled in the Time Domain Resource Allocation (TDRA) field.

[0030] For example, if the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 2, 3, 4, 5, 6, 7, or 8 bits, the size of the NDI field is 2, 3, 4, 5, 6, 7, or 8 bits, respectively, with each bit corresponding to the NDI of one PUSCH / PDSCH. If the number of PUSCH / PDSCHs scheduled in the TDRA field is 1, the size of the NDI field is 1 bit. Also, similar to the MCS field, if a single PUSCH / PDSCH contains two TBs spatially multiplexed onto the same time and frequency resource, an NDI field is set individually for each TB, and the size of the NDI field for each TB is one of 1 to 8 bits, as described above.

[0031] <Redundancy Version(RV)フィールド> The size of the RV field may depend on the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field.

[0032] For example, when the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 2, 3, 4, 5, 6, 7, or 8, the size of the RV field is 2, 3, 4, 5, 6, 7, or 8 bits, respectively. When the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 2 or more, each bit corresponds to the RV of one PUSCH / PDSCH. Note that when the number of PUSCH / PDSCHs scheduled in the TDRA field is 1, the size of the RV field is 1 or 2 bits. Also, similar to the MCS field, when the number of TBs included in one PUSCH / PDSCH is two multiplexed in space in the same time-frequency resource, the RV field is set individually for each TB, and the size of the RV field for each TB is any of 2 to 8 bits by the method described above.

[0033] Note that the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is not limited to 1 to 8.

[0034] <Hybrid Automatic ReQuest (HARQ) process number field> The size of the HARQ process number field is, for example, 4 bits or 5 bits. The HARQ process number indicated by the HARQ process number field is applied to the first PUSCH / PDSCH among a plurality of channels to be allocated (e.g., PUSCH / PDSCH), and for the second and subsequent PUSCH / PDSCHs, a process number incremented by 1 with respect to the indicated HARQ process number is applied.

[0035] That is, the size of the HARQ process number field does not depend on the number of PUSCH / PDSCHs allocated by multi-TB scheduling.

[0036] Figure 5 shows examples of DCI format 0-1 / 1-1 information field settings when scheduling one TB in single-cell scheduling, and examples of DCI format 0-1 / 1-1 information field settings when applying multiple TB scheduling in single-cell scheduling. In the example in Figure 5, the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field when applying multiple TB scheduling is 4 (for example, the 1st to 4th PUSCH / PDSCH). As shown in Figure 5, the DCI format 0-1 / 1-1 information fields (for example, the NDI field and RV field) when applying multiple TB scheduling in single-cell scheduling have a larger field size compared to the DCI format 0-1 / 1-1 information fields when scheduling one TB in single-cell scheduling.

[0037] [Relationship between Multiple Cell Scheduling and DCI Field Size] In Release 18, multiple cell scheduling allows for the assignment of PUSCH / PDSCH to multiple cells using "DCI format 0-3" or "DCI format 1-3" (see, for example, Non-Patent Documents 2 or 4). When assigning PUSCH / PDSCH to multiple cells using DCI format 0-3 or DCI format 1-3 (also expressed as, for example, "DCI format 0-3 / 1-3"), the correspondence between the settings of some information fields in DCI format 0-3 / 1-3 and the PUSCH / PDSCH of the multiple cells is as follows.

[0038] <FDRAフィールド> The size of the FDRA field depends on the maximum number of cells that can be scheduled.

[0039] For example, the FDRA field is <block number 1、 block number 2、…、block number N cell > may be composed of the following: Here, N cellThis indicates the maximum number of cells that can be scheduled. Each block corresponds to a PUSCH / PDSCH of one cell, and the field size of each block is determined depending on, for example, the size of the bandwidth used by the terminal in each cell (e.g., Active BWP) or the resource allocation method.

[0040] <MCSフィールド> The size of the MCS field depends on the maximum number of cells that can be scheduled.

[0041] For example, the MCS field is <block number 1、 block number 2、…、block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled. Each block corresponds to a PUSCH / PDSCH of one cell, and the field size of each block is, for example, 5 bits.

[0042] <NDIフィールド> The size of the NDI field depends on the maximum number of cells that can be scheduled.

[0043] For example, the NDI field is, <block number 1、 block number 2、…、block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled. Each block corresponds to a PUSCH / PDSCH of one cell, and the field size of each block is, for example, 1 bit.

[0044] <RVフィールド> The size of the RV field depends on the maximum number of cells that can be scheduled.

[0045] For example, RV fields are <block number 1、 block number 2、…、block number N cell > may be composed of the following: Here, N cellindicates the maximum number of cells that can be scheduled. Each block corresponds to the PUSCH / PDSCH of one cell, and the field size of each block may be set by, for example, a higher layer parameter (e.g., Radio Resource Control (RRC) parameter) and is 0, 1, or 2 bits.

[0046] <HARQ process number field> The size of the HARQ process number field depends on the maximum number of cells that can be scheduled.

[0047] For example, the HARQ process number field may be composed of <block number 1, block number 2,..., block number N cell >. Here, N cell indicates the maximum number of cells that can be scheduled. Each block corresponds to the PUSCH / PDSCH of one cell, and the field size of each block is set by, for example, an RRC parameter and is 0, 1, 2, 3, 4, or 5 bits.

[0048] FIG. 6 shows a setting example of the information field of DCI format 0-1 / 1-1 when scheduling one TB in single cell scheduling, and a setting example of the information field of DCI format 0-3 / 1-3 when applying multi-cell scheduling in Release 18. In the example of FIG. 6, the maximum number of cells that can be scheduled when applying multi-cell scheduling is two (e.g., the first cell and the second cell). As shown in FIG. 6, the information fields (e.g., FDRA, MCS, NDI, RV, and HARQ process number field) of DCI format 0-3 / 1-3 when applying multi-cell scheduling have a larger field size compared to the information field of DCI format 0-1 / 1-1 when scheduling one TB in single cell scheduling.

[0049] Above, the relationship between multi-cell scheduling and the field size of DCI has been described.

[0050] As described above, in single-cell scheduling with multiple TB scheduling, the sizes of the NDI and RV fields depend on the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field. Also, in multiple-cell scheduling, the sizes of the FDRA, MCS, NDI, RV, and HARQ process number fields depend on the maximum number of cells that can be scheduled.

[0051] For example, when applying multiple TB scheduling to each scheduled cell in multi-cell scheduling, applying the existing DCI field design standards for DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 may increase DCI overhead because the size of some DCI information fields (e.g., NDI field and RV field) depends on the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field and the maximum number of cells that can be scheduled.

[0052] For example, Figure 7 shows an example of setting the information field in DCI format 0-3 / 1-3 when applying the DCI field design standards for DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3, and applying multiple TB scheduling to each cell scheduled in multiple cell scheduling. Figure 7 is an example where the maximum number of PUSCH / PDSCH that can be scheduled for each cell set in the TDRA field is 4, and the maximum number of cells that can be scheduled is 2.

[0053] As shown in Figure 7, when applying multiple TB scheduling in multi-cell scheduling, the information fields in DCI format 0-3 / 1-3 are larger in size compared to the information fields in DCI format 0-1 or DCI format 1-1 when scheduling one TB in single-cell scheduling.

[0054] In one non-limiting embodiment of this disclosure, a method for suppressing the increase in DCI overhead when applying multiple TB scheduling to each scheduled cell in multiple cell scheduling is described.

[0055] For example, when applying multiple TB scheduling to each scheduled cell in multi-cell scheduling, a DCI size different from that which can be set by the DCI field design standards of DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 described above (for example, a DCI size based on the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field, and the maximum number of cells that can be scheduled) may be set (for example, a smaller DCI size). For example, by sharing some DCI fields with multiple PUSCH / PDSCHs and multiple cells, the DCI size can be compressed, or the DCI size can be determined based on a fixed number of bits, thereby suppressing the increase in DCI overhead.

[0056] According to one non-limiting embodiment of this disclosure, it is expected that multiple TB scheduling can be applied to each scheduled cell in multiple cell scheduling while suppressing the increase in DCI overhead.

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

[0058] [Overview of the communication system] A communication system according to one aspect of this disclosure comprises, for example, at least one base station and at least one terminal.

[0059] Figure 8 is a block diagram showing a partial configuration example of a base station 100 (corresponding to, for example, a communication device) according to one embodiment of the present disclosure, and Figure 9 is a block diagram showing a partial configuration example of a terminal 200 (corresponding to, for example, a communication device) according to one embodiment of the present disclosure.

[0060] In the base station 100 shown in Figure 8, the control unit (corresponding to, for example, a control circuit) determines the size of one downlink control information (e.g., DCI) that instructs the scheduling of multiple cells and the scheduling of multiple data channels (e.g., PUSCH / PDSCH) in each of the multiple cells, based on a second value different from a first value determined based on the maximum number of multiple cells and the maximum number of multiple data channels. The communication unit (corresponding to, for example, a receiving circuit) transmits the downlink control information based on the above size.

[0061] In the terminal 200 shown in Figure 9, the control unit (corresponding to, for example, a control circuit) determines the size of one downlink control information (e.g., DCI) that instructs the scheduling of multiple cells and the scheduling of multiple data channels (e.g., PUSCH / PDSCH) in each of the multiple cells, based on a second value different from a first value determined based on the maximum number of multiple cells and the maximum number of multiple data channels. The communication unit (corresponding to, for example, a receiving circuit) receives the downlink control information based on the above size.

[0062] (Embodiment 1) In this embodiment, of the multiple information fields included in the DCI (also referred to as, for example, "DCI fields"), at least one DCI field is shared by multiple PUSCH / PDSCHs, multiple cells, or both. This compresses the DCI size.

[0063] For example, a "group" is set up that shares a DCI field with multiple cells that can be scheduled by a single DCI, and with multiple PUSCH / PDSCHs that can be scheduled for each cell. For example, a group that includes at least some of the multiple PUSCH / PDSCHs may share at least one DCI field included in the DCI.

[0064] In this case, the DCI field size is the number of groups N set. group It depends on.

[0065] For example, the DCI field size is, <block number 1、 block number 2、…、block number N group > can be composed of the following. Each block corresponds to one group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same group and to multiple PUSCH / PDSCH that can be scheduled for each cell.

[0066] Figure 10 shows an example of setting the DCI field in DCI format 0-3 / 1-3 in this embodiment. In the example in Figure 10, the maximum number of PUSCH / PDSCH that can be scheduled for each cell set in the TDRA field is 2, and the maximum number of cells that can be scheduled is 4.

[0067] As shown in Figure 10, if there is no grouping of fields, each DCI field (for example, the FDRA field and the MCS field) will have up to four cells, each corresponding to a field.

[0068] In contrast, when there is a setting for groups that share fields (grouping), each DCI field (for example, the FDRA field and the MCS field) has fields set corresponding to two groups (Group 1 and Group 2). The field values ​​set for each group are applied in common to the cells belonging to each group and to the multiple PUSCH / PDSCH that can be scheduled for each cell. As shown in Figure 10, when grouping is present, the field size can be reduced compared to when grouping is not present.

[0069] [Example of setting up a group that shares DCI fields] A group that shares fields may be set up for some (one or more) DCI fields or all DCI fields.

[0070] Examples of DCI fields applicable to this embodiment may include the FDRA field, MCS field, NDI field, RV field, and HARQ process number field. Groups that share a common DCI field may be established for all or some of these fields.

[0071] For example, some DCI fields may be compressed by setting up a group that shares a common DCI field, while other DCI fields may not be compressed if no such group is set up. For example, the FDRA field, MCS field, NDI field, and RV field may be set up to share a common DCI field, while the HARQ process number field may not be set up to share a common DCI field. The size of DCI fields for which no group sharing a common DCI field is set may be determined by the DCI field design guidelines of the existing DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 described above.

[0072] The fields that may be applied to this embodiment are not limited to the FDRA, MCS, NDI, RV, and HARQ process number fields mentioned above, but may include other fields as well.

[0073] Furthermore, the settings for groups that share DCI fields may differ for each field or for multiple fields, as shown in Figure 11.

[0074] For example, as shown in Figure 11, a group (e.g., a first group) that shares a common DCI field may be set for the NDI field and RV field related to retransmission instructions. In addition, a group (e.g., a second group) that shares a different common DCI field from the group for the NDI field and RV field (e.g., a first group) may be set for the FDRA field and MCS field related to resource allocation. Note that the combinations of DCI fields to which a group sharing a common DCI field may be set are not limited to the above example. For example, a group that shares a common DCI field may be set for the MCS field containing instructions for some retransmissions and for the NDI field (or RV field), and a group that shares a different DCI field may be set for the FDRA field, or other combinations may also be possible.

[0075] Furthermore, whether or not to enable groups that share DCI fields, or to configure groups that share DCI fields, or both, may be set quasi-statically by RRC or dynamically by Medium Access Control - Control Element (MAC-CE). Alternatively, whether or not to enable groups that share DCI fields, or to configure groups that share DCI fields, or both, may be set dynamically within the same DCI as the DCI field in which the group is configured.

[0076] [Information Field Settings and Correspondence with Multiple Cells and Each Cell's PUSCH / PDSCH] The following explains the information field settings and their correspondence with multiple cells and each cell's PUSCH / PDSCH.

[0077] <FDRAフィールド> The size of the FDRA field is determined by the number of groups N set. group It depends on.

[0078] For example, the FDRA field is <block number 1、 block number 2、…、block number N group> may be composed of the following. Each block corresponds to one group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same group and multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs included in one group, and the field size of each block may be determined depending on, for example, the size of the Active BWP or the resource allocation method.

[0079] Furthermore, if a group contains multiple cells, the resource allocation method applied to the PUSCH / PDSCH of multiple cells within the same group may be set to be the same. Also, if a group contains multiple cells, the size of the Active BWP for each cell may be set to be the same. In this case, the correspondence between the value of the FDRA field and the frequency domain resource allocation can be unified for all cells within the group.

[0080] Furthermore, if a group contains multiple cells with different Active BWP sizes, the FDRA field size may be determined based on the largest Active BWP among the multiple cells in the same group. In this case, the flexibility of the FDRA for the largest Active BWP can be maintained. Alternatively, if a group contains multiple cells with different Active BWP sizes, the FDRA field size may be determined based on the smallest Active BWP among the multiple cells in the same group. In this case, the DCI size can be reduced. Note that if a group contains multiple cells with different Active BWP sizes, the FDRA field size may be determined not only based on the largest or smallest Active BWP among the multiple cells in the same group, but also on Active BWPs of other sizes.

[0081] Furthermore, if a group contains multiple cells and each cell has a different Active BWP size, the correspondence between the FDRA field value and the frequency domain resource allocation may differ depending on the Active BWP size. For example, if the FDRA field size is determined based on the largest Active BWP among the Active BWPs of multiple cells in the same group, and the resource allocation type is 0, then N RBG,c The frequency domain resource for the c-th cell may be determined by the LSB. Also, if the FDRA field size is determined based on the smallest Active BWP among multiple cells in the same group, the granularity K of the frequency domain resource allocation may be set as follows for frequency domain resources for cells different from the cell with the smallest Active BWP.

[0082] Here, N BWP,c This is the BWP size of the c-th cell, N BWP,min This indicates the smallest BWP size among the Active BWPs of multiple cells included in the same group.

[0083] Furthermore, if no group sharing a DCI field is defined for an FDRA field, the size of the FDRA field may depend on the maximum number of cells that can be scheduled. For example, the FDRA field may be: <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled. Each block corresponds to one or more PUSCH / PDSCH of a single cell, and the field size of each block may be determined depending on the size of the Active BWP or the resource allocation method, etc.

[0084] <MCSフィールド> The size of the MCS field is determined by the number of groups N set. group It depends on.

[0085] For example, the MCS field is <block number 1、 block number 2、…、block number N group > may be composed of the following. Each block corresponds to one group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same group and multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs included in one group, and the field size of each block may be, for example, 5 bits.

[0086] Furthermore, the field size of each block may be set, for example, by the RRC parameter, or a size of 5 bits or less may be set.

[0087] Furthermore, if no group sharing a DCI field is defined for an MCS field, the size of the MCS field may depend on the maximum number of cells that can be scheduled. For example, the MCS field may be: <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled. Each block corresponds to one or more PUSCH / PDSCH of a single cell, and the field size of each block may be, for example, 5 bits, or a size of 5 bits or less as set by the RRC parameter.

[0088] <NDIフィールド> The size of the NDI field is determined by the number of groups set, N. group It depends on.

[0089] For example, the NDI field is, <block number 1、 block number 2、…、block number N group> can be composed of the following. Each block corresponds to one group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same group and to multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs included in one group, and the field size of each block may be, for example, 1 bit.

[0090] Furthermore, if no group sharing a DCI field is defined for the NDI field, the size of the NDI field may depend on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field. For example, the NDI field may be: <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled. Each block corresponds to one or more PUSCH / PDSCHs in a single cell. For example, if the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 1, 2, 3, 4, 5, 6, 7, or 8, the field size of each block may be 1, 2, 3, 4, 5, 6, 7, or 8 bits, respectively, with each bit corresponding to an NDI for a single PUSCH / PDSCH. The size of the NDI field may also depend on the maximum number of PUSCH / PDSCHs that can be scheduled in multi-cell scheduling.

[0091] <RVフィールド> The size of the RV field is determined by the number of groups N set. group It depends on.

[0092] For example, RV fields are <block number 1、 block number 2、…、block number N group> can be composed of the following. Each block corresponds to one group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same group and to multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs included in one group, and the field size of each block may be specified in the standard as, for example, one or two bits, set by the RRC parameter, and may be 0, 1 or 2 bits.

[0093] Furthermore, if no group sharing a DCI field is defined for the RV field, the size of the RV field may depend on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field. For example, the RV field may be: <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell is the maximum number of cells that can be scheduled. Each block corresponds to one or more PUSCH / PDSCHs in a single cell, and if the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 1, 2, 3, 4, 5, 6, 7, or 8, the field size of each block may be 2, 2, 3, 4, 5, 6, 7, or 8 bits, respectively, and if the maximum number of PUSCH / PDSCHs that can be scheduled in the TDRA field is 2 or more, each bit corresponds to the RV of one PUSCH / PDSCH. The size of the RV field may also depend on the maximum number of PUSCH / PDSCHs that can be scheduled in multi-cell scheduling.

[0094] The above explains how to set up information fields and the correspondence between multiple cells and each cell's PUSCH / PDSCH.

[0095] In this embodiment, in a DCI field where groups sharing a common DCI field are configured, the DCI field size is determined to depend on the number of configured groups. This allows the DCI field size in a DCI field where groups sharing a common DCI field are configured to be set to a size different from (e.g., smaller than) the size determined based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field. Therefore, according to this embodiment, the increase in DCI size when scheduling multiple cells and multiple PUSCH / PDSCH for each cell using a single DCI can be suppressed.

[0096] (Embodiment 2) In Release 19, it is being considered to apply time-domain HARQ-ACK bundling when scheduling multiple cells and multiple PDSCHs for each cell using a single DCI.

[0097] In HARQ-ACK bundling, HARQ-ACKs (response signals) for PDSCHs within the same bundling group are bundled (compressed). For example, if at least one of the HARQ-ACKs in the same bundling group is a NACK, the feedback for the bundling group will be a NACK. In this case, it is common for base station 100 to retransmit all PDSCHs within the same bundling group. Therefore, the NDI and RV associated with retransmission can be common within the bundling group, which is sufficient for the retransmission operation.

[0098] Therefore, in this embodiment, among the multiple DCI fields included in the DCI, NDI, RV, or both DCI fields are shared among multiple PDSCHs, multiple cells, or both. This compresses the DCI size.

[0099] For example, among multiple cells that can be scheduled by a single DCI, and among multiple PDSCHs that can be scheduled for each cell, the DCI field is shared among PDSCHs within the same bundling group. For example, among PDSCHs (multiple data channels on a downlink), at least one DCI field included in the DCI may be shared by the bundling group to which HARQ-ACKs for the PDSCH are bundled.

[0100] In this case, the DCI field size is equal to the number of bundling groups N. TBG It depends on.

[0101] For example, the DCI field size is, <block number 1、 block number 2、…、block number N TBG > can be composed of the following. Each block corresponds to one bundling group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same bundling group and to multiple PDSCHs that can be scheduled for each cell.

[0102] Figure 12 shows an example of setting the DCI field in DCI format 1-3 in this embodiment. In the example in Figure 12, the maximum number of PDSCHs that can be scheduled for each cell set in the TDRA field is 2, and the maximum number of cells that can be scheduled is 4.

[0103] As shown in Figure 12, HARQ-ACKs for the two PDSCHs scheduled in cell #3 (CC#3) are bundled, and HARQ-ACKs for the two PDSCHs scheduled in cell #4 (CC#4) are bundled.

[0104] As shown in Figure 12, if there is no setting of groups that share fields (grouping), each DCI field (e.g., NDI field and RV field) will have fields corresponding to multiple cells and multiple PDSCHs scheduled for each cell (a total of six PDSCHs). In contrast, if there is a setting of bundling groups that share fields (grouping), each DCI field (e.g., NDI field and RV field) will have four fields corresponding to the PDSCH of cell 1 (CC#1), the PDSCH of cell 2 (CC#2), the bundling group of cell 3 (CC#3), and the bundling group of cell 4 (CC#4). As shown in Figure 12, when grouping is present, the field size can be reduced compared to when there is no grouping.

[0105] [Information Field Settings and Correspondence with Multiple Cells and Each Cell's PDSCH] The following explains the information field settings and their correspondence with multiple cells and each cell's PDSCH.

[0106] <NDIフィールド> The size of the NDI field is determined by the number of bundled groups N. TBG It depends on.

[0107] For example, the NDI field is, <block number 1、 block number 2、…、block number N TBG > may be composed of the following. Each block corresponds to one bundling group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same bundling group and multiple PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PDSCHs included in one bundling group, and the field size of each block may be, for example, 1 bit.

[0108] Furthermore, as mentioned above, a bundling group may be applied to multiple cells and multiple PDSCHs for each cell, or it may be set for each cell. When a bundling group is set for each cell, the size of the NDI field is the maximum number of cells that can be scheduled and the number of bundling groups set, N. TBG,c It depends on the NDI field. For example, the NDI field is <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled, N TBG,c This indicates the number of bundling groups in the c-th cell. Each block corresponds to one or more PDSCHs in a single cell, and the field size of each block is such that the number of bundling groups is N. TBG,c In the case of N TBG,c It can also be a bit, where each bit corresponds to one bundled group of NDI.

[0109] <RVフィールド> The size of the RV field is determined by the number of bundled groups N set. TBG It depends on.

[0110] For example, RV fields are <block number 1、 block number 2、…、block number N TBG > can be composed of. Each block corresponds to one bundling group, and the field values ​​of the corresponding block are commonly applied to multiple cells included in the same bundling group and multiple PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PDSCHs included in one bundling group, and the field size of each block may be specified in the standard as, for example, 1 or 2 bits, set by the RRC parameter, and may be 0, 1 or 2 bits.

[0111] Furthermore, as described above, a bundling group may be applied to multiple cells and multiple PDSCHs for each cell, or it may be set for each cell. When a bundling group is set for each cell, the size of the RV field is the maximum number of cells that can be scheduled and the number of bundling groups set N. TBG,c It depends on the RV field. <block number 1、 block number 2、…、 block number N cell > may be composed of the following: Here, N cell This indicates the maximum number of cells that can be scheduled, N TBG,c This indicates the number of bundling groups in the c-th cell. Each block corresponds to one or more PDSCHs in a single cell, and the field size of each block is such that the number of bundling groups is N. TBG,c In the case of N TBG,c It may also be ×X bits, where each bit corresponds to the RV of one bundling group. The value of X may be defined by the standard as 1 or 2 bits, set by the RRC parameter, and may be 0, 1, or 2 bits.

[0112] The above explains the settings of the information field and the correspondence between multiple cells and each cell's PDSCH.

[0113] In this embodiment, when applying HARQ-ACK bundling, the DCI field size (e.g., the size of the NDI field and RV field) is determined to a size that depends on the set number of bundling groups. This allows the DCI field size to be set to a size different from (e.g., smaller than) the size determined based on the maximum number of cells that can be scheduled and the maximum number of PDSCHs that can be scheduled in the TDRA field. Therefore, according to this embodiment, when scheduling multiple cells and multiple PDSCHs for each cell with a single DCI, it is possible to suppress the increase in DCI size while minimizing the impact on retransmission operations.

[0114] The DCI field to which this embodiment is applied may be the NDI field and the RV field, or it may include other fields.

[0115] Furthermore, whether or not to enable this embodiment (for example, sharing of the DCI field by bundling groups) may be determined in conjunction with the HARQ-ACK bundling settings. For example, if HARQ-ACK bundling is applied, this embodiment may also be enabled at the same time. In this case, terminal 200 can identify groups of PUSCH / PDSCH that share the DCI field based on the HARQ-ACK bundling settings. Therefore, since the groups of PUSCH / PDSCH are implicitly notified (configured) by the HARQ-ACK bundling settings, the amount of signaling can be reduced.

[0116] Furthermore, the application (enablement) of this embodiment may be set separately from the HARQ-ACK bundling settings. For example, the application (enablement) of this embodiment may be set quasi-statically by RRC or dynamically indicated by MAC-CE. Alternatively, the application (enablement) of this embodiment may be set dynamically within the same DCI as the DCI field shared by the bundling group.

[0117] (Embodiment 3) In Release 19, as described above, it is being considered to introduce a multi-cell scheduling function for cases where the subcarrier intervals (SCS) or carrier types differ between multiple cells scheduled by a single DCI. Furthermore, in consideration of reducing the complexity of the system and terminal processing, it is also being considered to impose restrictions such as scheduling a maximum of two different subcarrier intervals.

[0118] Between cells with different subcarrier intervals, it is desirable to be able to configure resource allocation and MCS settings individually from the perspective of scheduling flexibility or complexity. On the other hand, between cells with the same subcarrier interval, it may not significantly impair flexibility or complexity to share settings such as frequency domain resource allocation or MCS.

[0119] Therefore, in this embodiment, among the multiple DCI fields included in the DCI, the FDRA, MCS, or both DCI fields are shared among multiple cells with the same subcarrier spacing. This compresses the DCI size.

[0120] For example, a DCI field may be shared among multiple PUSCH / PDSCHs that can be scheduled for each cell of multiple cells having the same subcarrier interval, which can be scheduled by a single DCI. For example, a group of cells that include PUSCH / PDSCHs (data channels) scheduled in cells having the same subcarrier interval may share at least one DCI field included in the DCI.

[0121] In this case, the DCI field size is, for example, the number N of subcarrier intervals set for cells that can be scheduled by one DCI. SCS (For example, if you are scheduling up to two different subcarrier intervals, it depends on 2.)

[0122] For example, the DCI field size is, <block number 1、 block number 2、…、block number N SCS > can be composed of the following. Each block corresponds to a group of one subcarrier interval, and the field values ​​of the corresponding block are commonly applied to cells of the same subcarrier interval and to multiple PUSCH / PDSCH that can be scheduled for each cell.

[0123] Figure 13 shows an example of setting the DCI field in DCI format 0-3 / 1-3 in this embodiment. In the example in Figure 13, the maximum number of PUSCH / PDSCH that can be scheduled for each cell set in the TDRA field is 2, and the maximum number of cells that can be scheduled is 4.

[0124] As shown in Figure 13, cells #1 (CC#1) and #2 (CC#2) with a subcarrier spacing of 30 kHz are grouped together (Group 1), and cells #3 (CC#3) and #4 (CC#4) with a subcarrier spacing of 60 kHz are grouped together (Group 2).

[0125] As shown in Figure 13, if there is no setting of groups that share fields (grouping), each information field (for example, the FDRA field and the MCS field) may have fields corresponding to multiple cells. In contrast, if there is a setting of groups of cells with the same subcarrier interval (grouping), each information field (for example, the FDRA field and the MCS field) will have fields corresponding to the group of cells with a subcarrier interval of 30 kHz (cell 1 (CC#1) and cell 2 (CC#2)) and the group of cells with a subcarrier interval of 60 kHz (cell 3 (CC#3) and cell 4 (CC#4)). As shown in Figure 13, when grouping is present, the field size can be reduced compared to when there is no grouping.

[0126] [Information Field Settings and Correspondence with Multiple Cells and Each Cell's PUSCH / PDSCH] The following explains the information field settings and their correspondence with multiple cells and each cell's PUSCH / PDSCH.

[0127] <FDRAフィールド> The size of the FDRA field is the number of subcarrier intervals N. SCS It depends on.

[0128] For example, the FDRA field is <block number 1、 block number 2、…、block number N SCS> may be composed of the following. Each block corresponds to one subcarrier interval (e.g., a group), and the field values ​​of the corresponding block are commonly applied to multiple cells in the same subcarrier interval and multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs contained within one subcarrier interval, and the field size of each block may be determined depending on, for example, the size of the Active BWP or the resource allocation method.

[0129] Furthermore, if a group (a group with the same subcarrier interval) contains multiple cells, the resource allocation method applied to the PUSCH / PDSCH of multiple cells in the same group may be set to be the same. Also, if a group contains multiple cells, the size of the Active BWP for each cell may be set to be the same. In this case, the correspondence between the value of the FDRA field and the frequency domain resource allocation can be unified for all cells in the group.

[0130] Furthermore, if a group (a group with the same subcarrier interval) contains multiple cells with different Active BWP sizes for each cell, the FDRA field size may be determined based on the largest Active BWP among the multiple cells in the same group. In this case, the flexibility of the FDRA for the largest Active BWP can be maintained. Alternatively, if a group contains multiple cells with different Active BWP sizes for each cell, the FDRA field size may be determined based on the smallest Active BWP among the multiple cells in the same group. In this case, the DCI size can be reduced.

[0131] Furthermore, if a group (a group with the same subcarrier interval) contains multiple cells and each cell has a different Active BWP size, the correspondence between the FDRA field value and the frequency domain resource allocation may differ depending on the Active BWP size. For example, if the FDRA field size is determined based on the largest Active BWP among the Active BWPs of multiple cells in the same group, and the resource allocation type is 0, then N RBG,c The frequency domain resource for the c-th cell may be determined by the LSB. Also, if the FDRA field size is determined based on the smallest Active BWP among multiple cells in the same group, the granularity k of the frequency domain resource allocation may be set as follows for frequency domain resources for cells different from the cell with the smallest Active BWP.

[0132] Here, N BWP,c This is the BWP size of the c-th cell, N BWP,min This indicates the smallest BWP size among the Active BWPs of multiple cells included in the same group.

[0133] <MCSフィールド> The size of the MCS field is determined by the number of subcarrier intervals N. SCS It depends on.

[0134] For example, the MCS field is <block number 1、 block number 2、…、block number N SCS > may be composed of the following. Each block corresponds to one subcarrier interval, and the field values ​​of the corresponding block are commonly applied to multiple cells in the same subcarrier interval and multiple PUSCH / PDSCHs that can be scheduled for each cell. Each block corresponds to one or more PUSCH / PDSCHs contained in one subcarrier interval, and the field size of each block may be, for example, 5 bits.

[0135] Furthermore, the field size of each block may be set, for example, by the RRC parameter, or a size of 5 bits or less may be set.

[0136] The above explains how to set up information fields and the correspondence between multiple cells and each cell's PUSCH / PDSCH.

[0137] In this embodiment, when the subcarrier intervals between multiple cells scheduled by a single DCI are different, the DCI field size (e.g., the size of the FDRA field and the MCS field) is determined to depend on the number of subcarrier intervals. This allows the DCI field size to be set to a size different from (e.g., smaller than) the size determined based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH that can be scheduled in the TDRA field. Therefore, according to this embodiment, the increase in DCI size when scheduling multiple cells and multiple PUSCH / PDSCH for each cell by a single DCI can be suppressed.

[0138] The DCI field to which this embodiment is applied may be the FDRA field and the MCS field, or it may include other fields.

[0139] Furthermore, whether or not this embodiment (sharing of DCI fields by subcarrier interval groups) is applied (enabled) may be set quasi-statically by RRC, for example, or dynamically indicated by MAC-CE. Also, whether or not this embodiment is applied (enabled) may be set dynamically within the same DCI as the DCI field shared by the subcarrier interval groups. In addition, this embodiment may be applied (enabled) to some subcarrier intervals among multiple subcarrier intervals, while not being applied to the others.

[0140] Furthermore, in this embodiment, the terminal 200 can identify groups of PUSCH / PDSCH that share a DCI field based on the setting of the subcarrier interval (SCS). Therefore, since the groups of PUSCH / PDSCH are implicitly notified (set) by the setting of the subcarrier interval, the amount of signaling can be reduced.

[0141] (Variations of Embodiments 1, 2, and 3) Whether or not to apply Embodiments 1, 2, and 3 described above (enable them or not) may depend, for example, on the maximum number of cells that can be scheduled, the maximum number of PUSCH / PDSCH in each cell that can be scheduled in the TDRA field, and combinations thereof.

[0142] For example, any of the embodiments described above may be applied if the following conditions are met.

[0143] (1) When the maximum number of cells that can be scheduled is greater than threshold X. (2) When the maximum number of PUSCH / PDSCH in each cell that can be scheduled in the TDRA field is greater than threshold Y. (3) When the maximum number of cells that can be scheduled is greater than threshold X, AND the maximum number of PUSCH / PDSCH in each cell that can be scheduled in the TDRA field is greater than threshold Y. (4) When the value given by the maximum number of PUSCH / PDSCH that can be scheduled by a single DCI is greater than threshold Z. For example, when the maximum number of cells that can be scheduled is X, and the maximum number of PUSCH / PDSCH in each cell that can be scheduled in the TDRA field is Y, then Z > X × Y.

[0144] Applying the above-described variations allows the above-described embodiments to be applied when the impact of increased DCI size is significant, thereby mitigating the impact of reduced scheduling or retransmission flexibility due to DCI size compression. By not applying the above-described embodiments when the impact of increased DCI size is small, the processing load on the terminal can be reduced.

[0145] (Embodiment 4) In Release 18, multiple cell scheduling is possible with a single DCI, up to a maximum of four cells. In addition, in multiple TB scheduling in single cell scheduling, up to eight PUSCH / PDSCH units can be assigned.

[0146] As described above, when applying multiple TB scheduling to each scheduled cell in multi-cell scheduling, applying the existing DCI field design standards for DCI format 0-1 / 1-1 and DCI format 0-3 / 1-3 results in the DCI size of some fields depending on the maximum number of PUSCH / PDSCHs and the maximum number of cells that can be scheduled in each cell within the TDRA field. Consequently, the total DCI size is also calculated based on the maximum number of PUSCH / PDSCHs and the maximum number of cells that can be scheduled in the TDRA field.

[0147] Existing NR standards specify (e.g., limit) the maximum DCI size (e.g., DCI payload size) excluding Cyclic Redundancy Check (CRC) to 140 bits. Therefore, when applying multiple TB scheduling to each scheduled cell in multi-cell scheduling and calculating the DCI size using existing NR standards, the base station may set the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field to limit the DCI size to 140 bits. In this case, the number of cells that the base station can schedule or the number of PUSCH / PDSCHs in each cell may be limited. Alternatively, the number of cells that the base station can schedule or the number of PUSCH / PDSCHs in each cell can be increased by, for example, increasing the granularity of the FDRA or setting the BWP for each cell to narrowband, but this may reduce the flexibility of resource allocation.

[0148] One way to make the DCI size independent of the maximum number of PUSCH / PDSCHs per cell that can be scheduled in the TDRA field and the maximum number of cells that can be scheduled is to calculate the size of some DCI fields (e.g., FDRA, MCS, NDI, RV, or HARQ process number fields) based on the actual number of cells that are scheduled and the number of PUSCH / PDSCHs per cell that are actually scheduled in the TDRA field. In this case, even if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCHs per cell that can be scheduled in the TDRA field exceeds 140 bits, flexibility in the number of cells, the number of PUSCH / PDSCHs per cell, or resource allocation can be ensured as long as the DCI size calculated based on the actual number of cells that are scheduled and the number of PUSCH / PDSCHs per cell that are actually scheduled in the TDRA field does not exceed 140 bits. This allows for a dynamic reduction in the DCI size.

[0149] Furthermore, in the above-described embodiment, the DCI size can also be dynamically reduced even when the application of DCI field size compression is dynamically set within the same DCI.

[0150] However, if the DCI size changes dynamically, the terminal performs DCI decoding (e.g., blind decoding, monitoring) for multiple DCI size candidates. Therefore, when applying multiple TB scheduling to each scheduled cell in multi-cell scheduling, the number of DCI size candidates increases, and DCI decoding can become complex. For example, if the maximum number of cells that can be scheduled is 4, and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is 2, then the number of DCI size candidates can be up to 2 4 It could be 16.

[0151] Therefore, in this embodiment, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is greater than a specified number (for example, 140 bits, which is the maximum DCI size excluding CRC in the current specification), the DCI size is set to that specified number (for example, 140 bits).

[0152] For example, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is greater than 140 bits, the base station 100 either does not schedule the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field, or dynamically applies compression of the DCI field size in Embodiments 1, 2, or 3 to set the DCI size so as not to exceed 140 bits (for example, to 140 bits).

[0153] On the other hand, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is 140 bits or less (for example, if the specified number (e.g., 140 bits) is greater than the calculated DCI size), the base station 100 applies the calculated DCI size.

[0154] The size of the DCI that terminal 200 decodes may be determined, for example, based on a semi-static setting. For example, the DCI size is calculated using the minimum values ​​of "DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field" and "140 bits".

[0155] The size of each DCI field that constitutes the DCI calculated using the sizes described above may be dynamically variable and determined by explicit or implicit notifications within the DCI. For example, the implicit notification may include information about the number of cells actually scheduled or information about the number of PUSCH / PDSCH for each cell actually scheduled in the TDRA field.

[0156] For example, the size of the FDRA, MCS, NDI, RV, and HARQ process number fields may be determined based on the actual number of cells scheduled or the number of PUSCH / PDSCH actually scheduled for each cell.

[0157] Also, the size of the NDI field is, <block number 1、 block number 2、…、 block number N cell > may be composed of the following: where N cell This indicates the maximum number of cells that can be scheduled. Each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless one bit is applied if the number of scheduled PUSCH / PDSCHs is 1, or based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field. Alternatively, each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless the number of PUSCH / PDSCHs that are actually scheduled is 1 for all scheduled cells, or based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field.

[0158] The size of the RV field is the same as that of the NDI field. <block number 1、 block number 2、…、 block number N cell > may be composed of the following: where N cellThis indicates the maximum number of cells that can be scheduled. Each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless the number of scheduled PUSCH / PDSCHs is 1, and the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field is otherwise determined.

[0159] Furthermore, the sizes of the FDRA, MCS, NDI, RV, and HARQ process number fields may be set quasi-statically by RRC using, for example, one of the methods in Embodiment 1, 2, or 3, or they may be dynamically instructed by MAC-CE, or they may be dynamically set within the same DCI as these DCI fields.

[0160] In this embodiment, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH units that can be scheduled for each cell in the TDRA field is greater than the maximum DCI size excluding the CRC (e.g., the maximum payload size that can be set in the DCI, e.g., 140 bits), the DCI size is set to the maximum DCI size excluding the CRC. This allows the DCI field size to be set to a size different from (e.g., a smaller size) than the size determined based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH units that can be scheduled for each cell in the TDRA field.

[0161] According to this embodiment, the DCI size itself is determined by a semi-static setting, which helps to suppress the increase in the complexity of DCI decoding at the terminal 200. Furthermore, by dynamically reducing the DCI field size, flexibility in the number of cells, the number of PUSCH / PDSCHs in each cell, or resource allocation can be ensured, as long as the DCI size calculated based on the actual number of cells scheduled at the base station 100 and the number of PUSCH / PDSCHs in each cell actually scheduled in the TDRA field does not exceed 140 bits.

[0162] (Embodiment 5) In this embodiment, the base station 100 sets a semi-static size (e.g., a size limit) of the DCI that the terminal 200 decodes, rather than a fixed value (e.g., 140 bits) DCI size for the terminal 200.

[0163] If the DCI size, calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field, is greater than the set size (number of bits), the DCI size is set to the set number of bits. Here, the number of bits set is set to no more than or equal to a specified number (e.g., 140 bits).

[0164] If the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is greater than the set number of bits, the base station 100 sets the DCI size so as not to exceed the set number of bits. For example, the base station 100 may set the DCI size to the set number of bits by not scheduling the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field, or by dynamically applying the DCI field size compression in Embodiments 1, 2, or 3.

[0165] On the other hand, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field is less than or equal to the set number of bits (for example, if the set number of bits is greater than the calculated DCI size), the base station 100 applies the calculated DCI size.

[0166] The size of the DCI that terminal 200 decodes may be determined, for example, based on a semi-static setting. For example, the DCI size is calculated as the minimum of "the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCH for each cell that can be scheduled in the TDRA field" and "the set number of bits".

[0167] The size of each DCI field that constitutes the DCI calculated using the sizes described above may be set dynamically, for example, or determined by explicit or implicit notifications within the DCI. For example, the implicit notification may include information about the number of cells actually scheduled or information about the number of PUSCH / PDSCH for each cell actually scheduled in the TDRA field.

[0168] For example, the size of the FDRA, MCS, NDI, RV, and HARQ process number fields may be determined based on the actual number of cells scheduled or the number of PUSCH / PDSCH actually scheduled for each cell.

[0169] Also, the size of the NDI field is, <block number 1、 block number 2、…、 block number N cell > may be composed of the following: where N cellThis indicates the maximum number of cells that can be scheduled. Each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless one bit is applied if the number of scheduled PUSCH / PDSCHs is 1, or based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field. Alternatively, each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless the number of PUSCH / PDSCHs that are actually scheduled is 1 for all scheduled cells, or based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field.

[0170] The size of the RV field is the same as that of the NDI field. <block number 1、 block number 2、…、 block number N cell > may be composed of the following: where N cell This indicates the maximum number of cells that can be scheduled. Each block may be determined based on the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field, unless the number of scheduled PUSCH / PDSCHs is 1, and the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field is otherwise determined.

[0171] Furthermore, the sizes of the FDRA, MCS, NDI, RV, and HARQ process number fields may be set quasi-statically by RRC using, for example, one of the methods in Embodiment 1, 2, or 3, or they may be dynamically instructed by MAC-CE, or they may be dynamically set within the same DCI as these DCI fields.

[0172] In this embodiment, if the DCI size calculated based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field is greater than the set DCI size (e.g., a size of 140 bits or less), the DCI size is set to the set DCI size. This allows the DCI field size to be set to a size different from (e.g., a smaller size) the size determined based on the maximum number of cells that can be scheduled and the maximum number of PUSCH / PDSCHs that can be scheduled for each cell in the TDRA field.

[0173] According to this embodiment, the DCI size itself is determined by a semi-static setting, thereby suppressing an increase in the complexity of DCI decoding at the terminal 200. Furthermore, by enabling a reduction in the semi-static DCI size and the ability to dynamically reduce the DCI field size, it is possible to ensure a flexible number of cells, a flexible number of PUSCH / PDSCHs in each cell, or flexibility in resource allocation, as long as the DCI size calculated based on the actual number of cells scheduled at the base station 100 and the number of PUSCH / PDSCHs in each cell scheduled in the TDRA field does not exceed the set number of bits.

[0174] In Embodiments 4 and 5, we described the case where the DCI size is set to a single value (one type) from a predetermined value (e.g., 140 bits) or a semi-static setting value (e.g., a value of 140 bits or less). However, the DCI size may take on multiple values.

[0175] Furthermore, the maximum DCI size excluding the CRC (for example, the maximum DCI payload size) is not limited to 140 bits and may be any other value.

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

[0177] Furthermore, the embodiments described above may be applied in combination. For example, one or more embodiments of embodiments 1, 2, and 3 may be applied in combination with embodiment 4 or 5. Also, for example, embodiment 2 and embodiment 3 may be applied in combination. The combinations of embodiments are not limited to the examples described above, and other combinations are also possible.

[0178] [Example of operation of base station 100 and terminal 200] Figures 14 and 15 are sequence diagrams showing an example of operation of base station 100 and terminal 200.

[0179] Figure 14 shows an example of the operation of the base station 100 and terminal 200 when the DCI field size is determined before the DCI is received.

[0180] The base station 100 notifies the terminal 200 of the settings for multiple cell scheduling and multiple TB scheduling in each cell (for example, multiple PUSCH / PDSCH scheduling), and the terminal 200 receives the settings (S101).

[0181] Terminal 200 determines the DCI size (S102). Terminal 200 may, for example, determine the DCI size and DCI field size based on the settings notified from base station 100, according to the embodiment described above.

[0182] The base station 100 transmits a DCI (for example, DCI format 0-3 / 1-3) to the terminal 200 instructing it to assign (schedule) PUSCH / PDSCH, and the terminal 200 receives the DCI from the base station 100 (S103).

[0183] If the DCI transmitted from base station 100 to terminal 200 is in DCI format 1-3, base station 100 transmits a PDSCH and terminal 200 receives a PDSCH (S104). Also, if the DCI transmitted from base station 100 to terminal 200 is in DCI format 0-3, terminal 200 transmits a PUSCH and base station 100 receives a PUSCH (S105).

[0184] Figure 15 shows an example of the operation of the base station 100 and terminal 200 when the DCI field size is dynamically determined when the DCI is received.

[0185] The base station 100 notifies the terminal 200 of the settings for multiple cell scheduling and multiple TB scheduling in each cell (for example, multiple PUSCH / PDSCH scheduling), and the terminal 200 receives these settings (S201).

[0186] Terminal 200 determines the DCI size (S202). Terminal 200 may determine the DCI size based on the settings notified by base station 100, for example, according to the embodiment described above.

[0187] The base station 100 transmits a DCI (for example, DCI format 0-3 / 1-3) to the terminal 200 instructing it to assign PUSCH / PDSCH, and the terminal 200 receives the DCI from the base station 100 (S203).

[0188] Terminal 200 determines the DCI field size (S204). Terminal 200 may determine the DCI field size based on the settings notified from base station 100 and the received DCI instructions, for example, according to the embodiment described above.

[0189] If the DCI transmitted from base station 100 to terminal 200 is in DCI format 1-3, base station 100 transmits a PDSCH and terminal 200 receives a PDSCH (S205). Also, if the DCI transmitted from base station 100 to terminal 200 is in DCI format 0-3, terminal 200 transmits a PUSCH and base station 100 receives a PUSCH (S206).

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

[0191] Thus, in non-limiting embodiments of the present disclosure, the base station 100 and the terminal 200 determine a DCI size that instructs multiple cell scheduling and multiple TB scheduling in each of the multiple cells, based on a value smaller than a value (dependent value) determined based on the maximum number of multiple cells and the maximum number of multiple TBs, and transmit and receive DCIs based on the determined DCI size.

[0192] This makes it possible to suppress the increase in DCI overhead 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.

[0193] [Base Station Configuration] Figure 16 is a block diagram showing an example configuration of a base station 100. In Figure 16, 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.

[0194] At least one of the transmitting unit 107 and receiving unit 108 shown in Figure 16 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 16 may be included in the control unit shown in Figure 8.

[0195] The control unit 101 determines information regarding multiple cell scheduling and multiple TB scheduling in each cell, or information regarding the method for determining the DCI size or DCI field size, 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 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 method for determining the DCI size or DCI field size may include, for example, the information regarding the compression of the DCI size or DCI field size as described above.

[0196] Furthermore, the control unit 101 determines information regarding downlink reception (e.g., PDSCH reception) or uplink transmission (e.g., PUSCH transmission or PUCCH 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, or information regarding retransmission control (e.g., NDI, RV, HARQ process number, etc.). The information regarding PUCCH transmission may include, for example, information regarding HARQ-ACK bundling. The control unit 101 also outputs the determined information regarding uplink transmission to the extraction unit 109, the demodulation unit 110, and the decoding unit 111.

[0197] 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.

[0198] 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.

[0199] 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, and outputs the generated DCI bit sequence to the encoding unit 104. Note that the control information may also be transmitted to multiple terminals.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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., PUSCH or PUCCH) has been transmitted, and outputs the extracted portion of the radio resource to the demodulation unit 110.

[0206] The demodulation unit 110 demodulates the uplink signal (e.g., PUSCH or PUCCH) 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.

[0207] The decoding unit 111 performs error-correcting decoding of the uplink signal (e.g., PUSCH or PUCCH) 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., UCI or UL data signal).

[0208] [Terminal Configuration] Figure 17 is a block diagram showing an example configuration of a terminal 200 according to one embodiment of the present disclosure. For example, in Figure 17, 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.

[0209] At least one of the receiving unit 201 and transmitting unit 209 shown in Figure 17 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 17 may be included in the control unit shown in Figure 9.

[0210] 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.

[0211] 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.

[0212] 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.

[0213] The decoding unit 204 performs error-corrected decoding of PDCCH or PDSCH using the demodulation result input from the demodulation unit 203, for example, to obtain, 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.

[0214] The control unit 205 identifies information related to uplink transmission (e.g., PUSCH transmission) based on information 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 the encoding unit 206 and the signal allocation unit 208, for example. The control unit 205 also identifies information related to downlink reception (e.g., PDSCH reception) based on information 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 the extraction unit 202 and the demodulation unit 203, for example. For example, the information obtained from signals input from the decoding unit 204 may include information related to multiple cell scheduling and multiple TB scheduling in each cell, and radio resource allocation information.

[0215] The encoding unit 206 encodes an uplink signal (for example, an uplink data signal (UL data signal) or an uplink control signal (for example, UCI: Uplink Control Information)) based on information input from the control unit 205. The encoding unit 206 outputs the encoded bit sequence to the modulation unit 207.

[0216] 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.

[0217] 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.

[0218] 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.

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

[0220] 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.

[0221] Furthermore, the values ​​of the parameters used in the above embodiment (for example, the number of bits (field size), the number of cells, the number of TBs, the subcarrier interval, the number of groups, etc.) are examples only, and other values ​​may be used. Also, the DCI format used in the above embodiment is an example only, and other formats or names may be used.

[0222] (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.

[0223] 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.

[0224] 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 transmission and reception of downlink control information based on capability information received from the terminal 200.

[0225] 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.

[0226] Information regarding the capabilities or limitations of terminal 200 may, for example, be defined 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.

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

[0228] (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.

[0229] 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.

[0230] (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.

[0231] (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.

[0232] 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.

[0233] (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.

[0234] (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).

[0235] (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.

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

[0237] (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.

[0238] 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.

[0239] (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.

[0240] 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.

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

[0242] (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).

[0243] 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.

[0244] (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.

[0245] (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.

[0246] <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 18 (see, for example, 3GPP TS 38.300 v15.6.0, section 4).

[0247] <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).

[0248] 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.

[0249] 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.

[0250] <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.

[0251] 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.

[0252] (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).

[0253] 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.

[0254] 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."

[0255] 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

[0256] 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.

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

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

[0259] 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.

[0260] 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.

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

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

[0263] 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.

[0264] 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).

[0265] 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.

[0266] 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.

[0267] 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.

[0268] 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).

[0269] 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.

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

[0271] 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.

[0272] 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.

[0273] 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.

[0274] 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.

[0275] 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.

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

[0277] 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.

[0278] 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.

[0279] A communication device according to one embodiment of the present disclosure comprises a control circuit that determines the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and a receiving circuit that receives the downlink control information based on the size.

[0280] In one embodiment of the present disclosure, at least one of the multiple information fields included in the downlink control information is shared by at least a portion of the multiple cells and the multiple data channels.

[0281] In one embodiment of the present disclosure, the at least one information field is shared by a group that includes at least some of the plurality of data channels.

[0282] In one embodiment of the present disclosure, at least one information field is shared by a group of data channels among the plurality of data channels of the downlink, the data channels to which the response signals are bundled.

[0283] In one embodiment of the present disclosure, at least one information field is shared by a group of cells, including the data channel scheduled in cells having the same subcarrier interval.

[0284] In one embodiment of the present disclosure, the second value is the maximum payload size that can be set in the downlink control information, and the control circuit sets the size of the downlink control information to the second value if the first value is greater than the second value.

[0285] In one embodiment of the present disclosure, the second value is 140 bits.

[0286] In one embodiment of the present disclosure, the second value is a value that is set quasi-statically, and the control circuit sets the size of the downlink control information to the second value if the first value is greater than the second value.

[0287] In one embodiment of the present disclosure, the second value is a value of 140 bits or less.

[0288] 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 are executable by the one or more processors to cause the communication device to determine the size of one downlink control information that instructs the communication device to schedule a plurality of cells and to schedule a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and to receive the downlink control information based on the size.

[0289] In a communication method according to one embodiment of the present disclosure, the communication device determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and receives the downlink control information based on the size.

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

[0291] In one embodiment of the present disclosure, a communication method controlled by an integrated circuit, wherein the communication device determines the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and receives the downlink control information based on the size.

[0292] In one embodiment of the present disclosure, an integrated circuit comprises a circuit which determines the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and receives the downlink control information based on the size.

[0293] 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.

[0294] In one embodiment of the present disclosure, the circuit comprises a control circuit that determines the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and a receiving circuit that receives the downlink control information based on the size.

[0295] 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 the size of one downlink control information that instructs the scheduling of a plurality of cells and the scheduling of a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels, and receiving the downlink control information based on the size.

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

[0297] A communication device according to one embodiment of the present disclosure comprises a control circuit that determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and a transmission circuit that transmits the downlink control information based on the size.

[0298] 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 are executable by the one or more processors to cause the communication device to determine the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and to transmit the downlink control information based on the size.

[0299] In a communication method according to one embodiment of the present disclosure, the communication device determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and transmits the downlink control information based on the size.

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

[0301] In one embodiment of the present disclosure, a communication method controlled by an integrated circuit, wherein the communication device determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and transmits the downlink control information based on the size.

[0302] In one embodiment of the present disclosure, an integrated circuit comprises a circuit which determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and transmits the downlink control information based on the size.

[0303] 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.

[0304] In one embodiment of the present disclosure, the circuit comprises a control circuit that determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and a transmission circuit that transmits the downlink control information based on the size.

[0305] 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 the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and transmitting the downlink control information based on the size.

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

[0307] All disclosures in the specification, drawings, and abstract contained in the Japanese application 2024-195071, filed on November 7, 2024, are incorporated herein by reference.

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

[0309] 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 the size of one downlink control information that instructs the scheduling of multiple cells and the scheduling of multiple data channels in each of the multiple cells, based on a second value different from a first value determined based on the maximum number of the multiple cells and the maximum number of the multiple data channels; and a receiving circuit that receives the downlink control information based on the size.

2. The communication device according to claim 1, wherein at least one of the multiple information fields included in the downlink control information is shared by at least a portion of the multiple cells and the multiple data channels.

3. The communication device according to claim 2, wherein at least one information field is shared by a group including at least a portion of the plurality of data channels.

4. The communication device according to claim 2, wherein at least one information field is shared by a group of data channels among the plurality of data channels of the downlink, the data channels to which the response signals are bundled.

5. The communication device according to claim 2, wherein at least one information field is shared by a group of cells, among the plurality of cells, that include the data channel scheduled in cells having the same subcarrier interval.

6. The communication device according to claim 2, wherein the second value is the maximum payload size that can be set in the downlink control information, and the control circuit sets the size of the downlink control information to the second value if the first value is greater than the second value.

7. The communication device according to claim 6, wherein the second value is 140 bits.

8. The communication device according to claim 2, wherein the second value is a value set quasi-statically, and the control circuit sets the size of the downlink control information to the second value if the first value is greater than the second value.

9. The communication device according to claim 8, wherein the second value is a value of 140 bits or less.

10. 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 are executable by the one or more processors to cause the communication device to determine the size of one downlink control information that instructs the communication device to schedule a plurality of cells and to schedule a plurality of data channels in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of data channels; and to receive the downlink control information based on the size.

11. A communication device comprising: a control circuit that determines the size of one downlink control information that instructs scheduling for a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks; and a transmission circuit that transmits the downlink control information based on the size.

12. 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 are executable by the one or more processors to cause the communication device to determine the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and to transmit the downlink control information based on the size.

13. A communication method comprising: a communication device that determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and receiving the downlink control information based on the size.

14. A communication method comprising: a communication device that determines the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks, and transmits the downlink control information based on the size.

15. An integrated circuit for controlling the processing of a communication device, wherein the processing includes: determining the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks; and receiving the downlink control information based on the size.

16. An integrated circuit for controlling the processing of a communication device, wherein the processing includes: determining the size of one downlink control information that instructs scheduling in a plurality of cells and a plurality of transport blocks in each of the plurality of cells, based on a second value different from a first value determined based on the maximum number of the plurality of cells and the maximum number of the plurality of transport blocks; and transmitting the downlink control information based on the size.

Images