Terminal

Abstract

This terminal comprises: a reception unit that receives downlink control information used for multi-cell scheduling; and a control unit that determines that a field of the downlink control information in a dormant and / or a deactivated cell is used for the purpose of notification other than scheduling of a downlink signal.

Description

Terminal

[0001] The present disclosure relates to a terminal.

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

[0003] In 3GPP, Rel-17 (Release-17) specifies several techniques for coverage enhancement of uplink signals such as PUSCH, PUCCH, and Msg3 PUSCH of the random access procedure (see, for example, Non-Patent Documents 1 and 2). Note that PUSCH is an abbreviation for Physical Uplink Shared Channel, and PUCCH is an abbreviation for Physical Uplink Control Channel.

[0004] In 3GPP, multi-carrier enhancement of downlink and uplink signals is being discussed (see, for example, Non-Patent Document 3). For example, multi-cell PDSCH (Physical Downlink Shared Channel) scheduling using a single DCI (Downlink Control Information) is being discussed.

[0005] At the RAN1 #114-bis meeting, it was agreed that partial scheduling would be supported in multi-cell PDSCH scheduling. In partial scheduling, there are cells in which PDSCH scheduling by DCI is not performed.

[0006] 3GPP TS 38.214 V17.7.0 (2023-09)3GPP TS 38.300 V17.6.0 (2023-09)”New WID on Multi-carrier enhancements”, RP-213577, 3GPP TSG RAN Meeting #94e, Electronic Meeting, Dec. 6 - 17, 2021

[0007] At present, there is no clear definition of how terminals should control dormant and / or deactivated cells in multi-cell PDSCH scheduling. Therefore, when dormant and / or deactivated cells exist between a base station and a terminal, there is a risk that inconsistencies may occur, making it impossible to perform appropriate communication.

[0008] One aspect of the present disclosure is to provide a terminal capable of performing appropriate control regarding support for dormant and / or deactivation of a cell in multi-cell PDSCH scheduling.

[0009] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines that a field of the downlink control information in a dormant and / or deactivated cell is used for notification purposes other than scheduling of downlink signals.

[0010] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines that fields of the downlink control information in a Dormant and / or deactivated cell are not used for notification purposes other than scheduling of downlink signals.

[0011] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines not to transmit an acknowledgement response corresponding to a dormant and / or deactivated cell and / or a bandwidth part among a set of cells to be multi-cell scheduled.

[0012] A terminal according to one embodiment of the present disclosure includes a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines to transmit an acknowledgement response corresponding to a dormant and / or deactivated cell and / or a bandwidth part among a set of cells to be multi-cell scheduled.

[0013] FIG. 1 is a diagram showing an example of a wireless communication system according to an embodiment. FIG. 1 is a diagram showing example configurations of a radio frame, a subframe, and a slot used in a wireless communication system. FIG. 2 is a diagram explaining multi-carrier scheduling. FIG. 3 is a diagram explaining self-carrier scheduling. FIG. 4 is a diagram explaining cross-carrier scheduling. FIG. 5 is a diagram explaining scheduling in DCI format 1_3. FIG. 6 is a diagram explaining a reference cell. FIG. 7 is a diagram explaining an overview of Type-1 HARQ-ACK CB. FIG. 8 is a diagram explaining an overview of Type-1 HARQ-ACK CB. FIG. 9 is a diagram explaining an overview of Type-2 HARQ-ACK CB. FIG. 10 is a diagram explaining an overview of Type-2 HARQ-ACK CB. FIG. 11 is a diagram explaining an overview of Type-3 HARQ-ACK CB. FIG. 12 is a diagram explaining agreed matters of partial scheduling. FIG. 13 is a diagram explaining agreed matters of partial scheduling. FIG. 14 is a diagram showing an example of a description of the current specifications. FIG. 15 is a diagram showing an example of a description of the current specifications. FIG. 16 is a diagram showing an example of a description of the current specifications. FIG. 17 is a flow diagram showing the operation of a terminal in option 1 of proposal 1. FIG. 18 is a diagram showing a part of a list of Prerequisite FGs related to multi-carrier scheduling (DCI format 1_3). FIG. 1 is a diagram showing a part of a list of Prerequisite FGs related to multi-carrier scheduling (DCI format 1_3). FIG. 2 is a block diagram showing an example of the configuration of a base station according to an embodiment. FIG. 3 is a block diagram showing an example of the configuration of a terminal according to an embodiment. FIG. 4 is a diagram showing an example of the hardware configuration of a base station and a terminal according to the present embodiment. FIG. 5 is a diagram showing an example of the configuration of a vehicle.

[0014] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that the embodiments described below are merely examples, and embodiments to which the present disclosure can be applied are not limited to the following embodiments.

[0015] In the following description, the notation " / " may mean "and / or" unless otherwise specified.

[0016] <Wireless System Configuration> Fig. 1 is a diagram showing an example of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to New Radio (NR) and includes a Next Generation-Radio Access Network (hereinafter referred to as NG-RAN 20 and a terminal 200). The wireless communication system 10 may be a wireless communication system conforming to a scheme called 5G, Beyond 5G, 5G Evolution, or 6G. The terminal is also referred to as User Equipment (UE).

[0017] The NG-RAN 20 includes a base station 100. The base station 100 may be, for example, a gNB or an ng-eNB. The NG-RAN 20 is connected to a core network (e.g., 5GC, not shown) conforming to NR. The NG-RAN 20 and the 5GC may be simply referred to as a network.

[0018] The base station 100 is a radio base station conforming to NR, and performs NR radio communication with the terminal 200. The base station 100 and the terminal 200 are capable of supporting Massive MIMO (Multi-Input Multi-Output), which generates a more directional beam by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) by bundling them together, and Dual Connectivity (DC), which performs simultaneous communication between multiple NG-RAN nodes and the terminal.

[0019] The wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR (Frequency Range) are as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz

[0020] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and may use a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 kHz or 120 kHz (including 240 kHz), and may use a bandwidth (BW) of 50 to 400 MHz.

[0021] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0022] Furthermore, the wireless communication system 10 may also support frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 may support frequency bands above 52.6 GHz up to 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x." When using a frequency band above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0023] FIG. 2 shows an example of the configuration of a radio frame, subframe, and slot used in the wireless communication system 10. As shown in FIG. 2, one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the number of symbols constituting one slot does not necessarily have to be 14 symbols (e.g., 28 or 56 symbols). Also, the number of slots per subframe may differ depending on the SCS. Furthermore, the SCS may be wider than 240 kHz.

[0024] The time direction (t) shown in Fig. 2 may be called a time domain, a time region, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a resource block group, a subcarrier, a BWP (Bandwidth Part), a subchannel, a common frequency resource, etc.

[0025] <Multi-carrier extension> In the formulation of Rel-18, 3GPP is discussing multi-carrier extension of downlink and uplink signals.

[0026] For example, multi-cell PUSCH / PDSCH scheduling using a single DCI, which will be described in <Multi-carrier scheduling> below, has been discussed and some agreement has been reached.

[0027] Note that multi-cell PDSCH / PUSCH scheduling may also be referred to as multi-carrier PDSCH / PUSCH scheduling. Furthermore, multi-cell PDSCH / PUSCH scheduling may also be referred to as multi-cell scheduling or multi-carrier scheduling.

[0028] Multi-cell PDSCH / PUSCH scheduling may also be referred to as single DCI multi-cell PDSCH / PUSCH scheduling, single DCI multi-carrier PDSCH / PUSCH scheduling, single DCI multi-cell scheduling, or single DCI multi-carrier scheduling.

[0029] Hereinafter, multi-cell PDSCH / PUSCH scheduling may be referred to as multi-carrier scheduling.

[0030] <Multi-carrier scheduling> Fig. 3 is a diagram explaining multi-carrier scheduling. Fig. 4 is a diagram explaining self-carrier scheduling. Fig. 5 is a diagram explaining cross-carrier scheduling. CC#1 to CC#3 shown in Figs. 3 to 5 indicate CCs. A CC may also be referred to as a carrier or a cell. Figs. 4 and 5 are shown for comparison with the multi-carrier scheduling of Fig. 3.

[0031] As shown in FIG. 3, in multi-carrier scheduling, one DCI in one CC#1 schedules PDSCH / PUSCH in multiple CC#1 to CC#3.

[0032] As shown in Fig. 4, in self-carrier scheduling, one DCI in one CC#1 schedules a PDSCH / PUSCH in one CC#1 (the same CC as the CC of the DCI), one DCI in one CC#2 schedules a PDSCH / PUSCH in one CC#2, and one DCI in one CC#3 schedules a PDSCH / PUSCH in one CC#3.

[0033] As shown in FIG. 5, in cross-carrier scheduling, multiple DCIs in one CC#1 schedule PDSCHs / PUSCHs in multiple CC#1 to CC#3.

[0034] Multi-carrier scheduling can be considered as one DCI scheduling PDSCH / PUSCH in multiple CCs, whereas self-carrier scheduling and cross-carrier scheduling can be considered as multiple DCIs scheduling PDSCH / PUSCH in multiple CCs.

[0035] In multi-carrier scheduling, one DCI schedules PDSCH / PUSCH in multiple CCs, so the load of DCI monitoring (PDCCH monitoring) on ​​a terminal can be reduced compared to self-carrier scheduling and cross-carrier scheduling. For example, in multi-carrier scheduling, the number of BDs (Blind Detections) of PDCCHs on a terminal can be reduced.

[0036] Furthermore, in multi-carrier scheduling, the total overhead in DCI can be reduced compared to self-carrier scheduling and cross-carrier scheduling. For example, in a scenario where it is not necessary to notify different information to each of CC#1 to CC#3, common information can be notified in one DCI (DCI field), and the total overhead in DCI can be reduced.

[0037] <DCI format 0_3 / 1_3> The DCI format for multi-carrier scheduling of PUSCH is called DCI format 0_3. The DCI format for multi-carrier scheduling of PDSCH is called DCI format 1_3. DCI format 0_3 / 1_3 can be scheduled simultaneously for each cell included in a set of cells to be scheduled (Set of cells). Hereinafter, Set of cells may be referred to as SoCs.

[0038] Fig. 6 is a diagram illustrating scheduling in DCI format 1_3. One SoC consists of a maximum of four cells (CCs). One cell is included in only one SoC. In the example of Fig. 6, Set of cells 1 includes CCs #1 / 2 / 3 / 4, and Set of cells 2 includes CCs #5 / 6 / 7. Information about the configuration of the SoCs is reported by higher layer signaling, such as RRC signaling.

[0039] DCI formats 0_3 / 1_3 can be scheduled simultaneously for any combination of cells included in the SoCs.

[0040] For example, the PDCCH (DCI format 1_3) shown by arrow A6a in Fig. 6 can simultaneously schedule PDSCHs in four CCs #1 / 2 / 3 / 4 of Set of cells 1. For example, the PDCCH (DCI format 1_3) shown by arrow A6b in Fig. 6 can simultaneously schedule PDSCHs in three CCs #5 / 6 / 7 of Set of cells 2.

[0041] Similarly, PUSCH can be scheduled simultaneously with PUCCH (DCI format 0_3).

[0042] In addition, in Fig. 6, the PDCCH is transmitted by a cell (#0) different from the cells (CC#1 to CC#7) of Set of cells 1 and Set of cells 2, but this is not limited to this. The PDCCH may be transmitted by a cell of the SoCs. For example, in Fig. 6, the PDCCH may be transmitted by a cell of CC#1. The same applies to the PUCCH.

[0043] <Reference Cell> A cell referenced to count specific parameters such as DCI size, number of PDCCH candidates (number of BDs), number of CCEs (Control Channel Elements), etc. is called a reference cell. The reference cell is notified to the terminal by higher-level parameters such as RRC signaling (e.g., search space configuration). In multi-carrier scheduling, one reference cell is configured for each SoC.

[0044] In multi-carrier scheduling, the terminal counts the Downlink Assignment Index (DAI) in the reference cell. In self-carrier scheduling, the terminal counts the DAI in the cell monitoring the PDCCH, and in cross-carrier scheduling, the terminal counts the DAI in the scheduled cell.

[0045] 7 is a diagram illustrating reference cells. In the example of FIG. 7, the reference cell of Set of cells 1 is set to CC#1, which has the smallest index value in Set of cells 1. The reference cell of Set of cells 2 is set to CC#5, which has the smallest index value in Set of cells 2.

[0046] <HARQ-ACK CB> 3GPP is currently studying the enhancement of HARQ-ACK feedback functionality using Hybrid Automatic Repeat request - Acknowledgement Codebook (HARQ-ACK CB) as an extension of URLLC technology. 3GPP has previously specified type-1, type-2 (hereinafter sometimes abbreviated as "type-1 / 2"), and type-3 HARQ-ACK CB. Furthermore, in Rel-17, 3GPP specified enhanced type-3 HARQ-ACK CB, which is an extension of type-3 HARQ-ACK CB. A terminal may be instructed which type of HARQ-ACK CB to apply, for example, by higher layer signaling such as RRC. HARQ-ACK may be considered as an example of information (signal) related to a confirmation response (e.g., an acknowledgement) to data received by the terminal. Each type of HARQ-ACK CB is briefly described below.

[0047] (Type-1 HARQ-ACK CB) Fig. 8 is a diagram illustrating an overview of type-1 HARQ-ACK CB. "Scheduled" shown in Fig. 8 indicates, for example, a slot scheduled by DCI. CC indicates Component Carrier.

[0048] In type-1 HARQ-ACK CB, the terminal generates a HARQ-ACK bit for the PDSCH regardless of whether a scheduled slot (PDSCH) exists. For example, the terminal may set a NACK for an unscheduled PDSCH, as shown in the "HARQ-ACK codebook" in FIG. 8.

[0049] In type-1 HARQ-ACK CB, for example, as shown in FIG. 9 , the terminal checks all combinations of all candidate values ​​of k1 (PDSCH-to-HARQ feedback timing indicator) and all entries in the TDRA table for each PUCCH occasion, and prepares HARQ-ACK bits for all occasions in which a PDSCH may be allocated.

[0050] (Type-2 HARQ-ACK CB) Fig. 10 is a diagram illustrating an overview of type-2 HARQ-ACK CB. (x, y) in Fig. 10 indicates, for example, a slot scheduled by DCI. Also, in Fig. 10, x corresponds to the C-DAI value, and y corresponds to the T-DAI value. C-DAI stands for Count - Downlink Assignment Index, and T-DAI stands for Total - Downlink Assignment Index. DAI indicates, for example, the scheduled PDSCH allocation in which HARQ-ACK bits are bundled in the HARQ-ACK CB. C-DAI and T-DAI are counted for each DCI.

[0051] In type-2 HARQ-ACK CB, the terminal generates a HARQ-ACK bit for the scheduled PDSCH. For example, the terminal may configure HARQ-ACK for the scheduled PDSCH as shown in "HARQ-ACK codebook" in FIG. 10.

[0052] Note that C-DAI counts up from 1. For example, in the case of a 2-bit field, C-DAI repeats 1->2->3->0->... C-DAI is counted up for each slot at each opportunity to receive DCI for each CC, and even if the slot changes, it is counted up from the final value of the previous slot. T-DAI indicates the final value of C-DAI for each slot.

[0053] In type-2 HARQ-ACK CB, the terminal allocates HARQ-ACKs in the second sub-codebook when two or more PDSCHs can be scheduled in one DCI, and allocates HARQ-ACKs in the first sub-codebook when one PDSCH can be scheduled in one DCI. The terminal prepares HARQ-ACK bits for the maximum number of TBs that can be scheduled in one DCI for each DAI counter value as the number of HARQ-ACK bits for Multi-PDSCHs scheduling to be included in the second sub-codebook. The terminal counts the DAI separately for each sub-codebook, for example, as shown in FIG. 11 .

[0054] (Type-3 HARQ-ACK CB) In 3GPP, in Rel-16, it was agreed to support type-3 HARQ-ACK CB as a function for retransmitting HARQ-ACK bits for all HARQ process IDs.

[0055] The type-3 HARQ-ACK CB includes HARQ-ACK information for all configured HARQ processes of all configured serving cells. The terminal is assumed to provide HARQ-ACK information in response to a type-3 HARQ-ACK CB request N symbols after the last symbol of the PDCCH that provides the DCI format.

[0056] 12 is a diagram illustrating an overview of type-3 HARQ-ACK CB. As shown in FIG. 12, in type-3 HARQ-ACK CB, first, for each HARQ-ACK for the HARQ process of each CC, the HARQ-ACK bits are arranged in ascending order of HPN (HARQ Process Number). Then, the HARQ-ACKs for the HARQ processes of each CC are arranged in ascending order of CC number.

[0057] (Enhanced type-3 HARQ-ACK CB) In 3GPP Rel-17, it was agreed to support enhanced type-3 HARQ-ACK CB. In addition, the following points were agreed regarding enhanced type-3 HARQ-ACK CB:

[0058] The size of the enhanced type-3 HARQ-ACK CB is smaller than the size of the type-3 HARQ-ACK CB, which is defined by the RRC configuration.

[0059] The enhanced type-3 HARQ-ACK CB is triggered by DCI format 1_1 and DCI format 1_2. For the enhanced type-3 HARQ-ACK CB, one or more small CBs are configured by RRC. Each configured small CB may include HARQ processes of a subset of the configured CCs or a subset of the configured HARQ processes (specific to the CC). The terminal can transmit some of the subsets in the enhanced type-3 HARQ-ACK CB.

[0060] In type-3 HARQ-ACK CB, for example, as shown in FIG. 13, the terminal prepares HARQ ACK bits for all HARQ processes.

[0061] <Sub-codebook> In type-2 HARQ-ACK CB, two types of sub-codebooks, a first sub-codebook and a second sub-codebook, are generated.

[0062] The first sub-codebook is used for HARQ-ACK feedback in the following cases, for example: Reception of SPS PDSCH; Any DCI format with associated HARQ-ACK information without scheduling PDSCH reception; Reception of PDSCH scheduled by a DCI format that schedules a single PDSCH; Reception of PDSCH for TBG-based HARQ-ACK information on the serving cell.

[0063] The second sub-codebook is used when feeding back HARQ-ACK bits for PDSCHs scheduled by a DCI format that schedules multiple PDSCHs.

[0064] <Partial Scheduling> At the RAN1 #114-bis meeting for Release 18, support for partial scheduling was agreed upon in multi-cell PDSCH scheduling using DCI format 1_3, as shown in, for example, Figures 14 and 15 (see, for example, "3GPP TSG RAN WG1 #114bis," "R1-2310733," "Maintenance of multi-carrier enhancements for NR," "Xiamen, China, October 9th - 13th, 2023").

[0065] In DCI format 1_3, multiple fields for MCS (Modulation and Coding Scheme), RV (Redundancy Version), and NDI (New data indicator) are provided, and these values ​​can be notified individually for each cell.

[0066] In partial scheduling, for one cell among the SoCs, there is no DL assignment, PDSCH scheduling using DCI format 1_3 is not performed, and the MCS, RV, and NDI fields of DCI format 1_3 are used for purposes (functions) other than PDSCH scheduling. For the other cells, PDSCH scheduling is performed using DCI format 1_3, and the MCS, RV, and NDI fields of DCI format 1_3 are used for PDSCH scheduling.

[0067] For example, when partial scheduling is performed in FIG. 5, in CC#1, the MCS, RV, and NDI fields of DCI format 1_3 are used for purposes (functions) other than PDSCH scheduling, and in CC#2 and CC#3, the MCS, RV, and / or NDI fields of DCI format 1_3 are used for PDSCH scheduling.

[0068] Hereinafter, when partial scheduling is performed, a cell in which PDSCH scheduling is not performed using DCI format 1_3 and the MCS, RV, and / or NDI fields of DCI format 1_3 are used for purposes (functions) other than PDSCH scheduling may be referred to as a "specific cell."

[0069] The terminal can identify the specific cell by decoding the DCI. Specifically, a cell in which the value of the Frequency-Domain Resource Allocation (FDRA) field is an invalid value (for example, all "0") and in which no specific DCI field is set in the DCI is interpreted as a specific cell.

[0070] In the agreement on partial scheduling support, "purposes (functions) other than PDSCH scheduling" include at least the following: Cell dormancy indication case 2 Enhanced type-3 HARQ-ACK CB trigger HARQ-ACK retransmission slot offset

[0071] "Scell ​​dormancy indication case 2" is information indicating which of the Scells (Secondary-cells) is dormant.

[0072] "Enhanced type-3 HARQ-ACK CB trigger" is information that triggers the transmission of HARQ-ACK to some selected processes and cells in the enhanced type-3 HARQ-ACK CB that can notify HARQ-ACK of all cells. The terminal reads the value of the MCS field of a specific cell and determines for which HARQ-ACK process the HARQ-ACK is to be transmitted.

[0073] "HARQ-ACK retransmission slot offset" is information indicating the offset of the PUCCH resource for retransmitting the HARQ-ACK for the function of retransmitting the HARQ-ACK. The terminal interprets the value of the MCS field of a specific cell and determines how many slots back in the PUCCH the HARQ-ACK should be retransmitted.

[0074] <Analysis> As support for partial scheduling has been agreed upon in multi-cell PDSCH scheduling, PDSCH scheduling using DCI format 1-3 will not be performed in specific cells. However, at present, terminal control in partial scheduling, such as HARQ-ACK feedback in specific cells, has not been fully considered.

[0075] (Analysis 1) It is specified that the HARQ-ACK bit for an existing DCI format that does not perform PDSCH scheduling is transmitted in the first sub-codebook. On the other hand, it is specified that the HARQ-ACK bit for receiving a PDSCH scheduled in DCI format 1_3 is transmitted in the second sub-codebook. Figure 16 is a diagram showing an example of the description of the current specifications. Note that Figure 16 is an excerpt from section 9.1.3.1 of 3GPP TS38.213 v18.0.0.

[0076] However, at present, there is no specification for a sub-codebook for transmitting the HARQ-ACK bit of a specific cell for which PDSCH scheduling using DCI format 1_3 is not performed (hereinafter abbreviated as "HARQ-ACK bit of a specific cell").

[0077] This may cause a discrepancy in the recognition of the sub-codebook of the HARQ-ACK bit of a specific cell between the base station and the terminal, which may result in inappropriate communication.

[0078] (Analysis 2) For existing DCI formats that do not perform PDSCH scheduling, the C-DAI for HARQ-ACK is specified to be counted as a pair of a serving cell and a PDCCH monitoring occasion. On the other hand, for HARQ-ACK for reception of PDSCH scheduled in DCI format 1_3, the C-DAI is specified to be counted as a pair of the serving cell with the smallest index among multiple serving cells (the serving cell of the PDSCH) and the PDCCH monitoring occasion. Figure 17 is a diagram showing an example of the description of the current specifications. Note that Figure 17 is an excerpt from section 9.1.3.1 of 3GPP TS38.213 v18.0.0.

[0079] However, at present, there is no specification for a method of determining a reference cell for counting the DAI, etc., in the case where partial scheduling is used and PDSCH scheduling using DCI format 1_3 is not performed, and a specific cell exists in which the MCS, RV, and NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0080] This may result in a discrepancy in the recognition of the reference cell between the base station and the terminal, which may prevent proper communication.

[0081] (Analysis 3) Although support for partial scheduling has been agreed upon in multi-cell PDSCH scheduling, some UEs do not support partial scheduling. At present, there are no specifications for reporting UE capabilities regarding support for partial scheduling.

[0082] This may result in a discrepancy in the recognition of the terminal's capabilities between the base station and the terminal, making it impossible to carry out appropriate communication.

[0083] (Analysis 4) In the existing specifications, when an Scell ​​is dormant / deactivated, the terminal does not monitor the PDCCH scheduled to the Scell. Fig. 18 is a diagram showing an example of the description of the current specifications. Note that Fig. 18 is an excerpt from section 5.9 and section 5.15.1 of 3GPP TS38.321 v17.6.0.

[0084] On the other hand, in multi-cell PDSCH scheduling, if at least one cell included in the SoCs (ScheduledCell-ListDCI-1-3 / ScheduledCell-ListDCI-0-3) is activated, the terminal may continue to monitor the PDCCH (DCI format 0_3 / 1_3) that schedules these cells, even if other cells included in the SoCs are dormant / deactivated.

[0085] In this case, it is unclear whether the DCI field (such as the MCS field) for the dormant / deactivated Scell ​​can be used for notification purposes other than PDSCH scheduling (for example, Scell ​​dormancy indication case 2, enhanced type-3 HARQ-ACK codebook trigger, HARQ-ACK retransmission slot offset, etc.). If it is usable, the terminal needs to check the DCI field (such as the FDRA field) for the dormant / deactivated Scell. On the other hand, if it is not usable, the terminal does not need to check the DCI field (such as the FDRA field) for the dormant / deactivated Scell.

[0086] Furthermore, in this case, it is unclear whether the terminal transmits HARQ-ACK information (NACK) to the dormant / deactivated Scell.

[0087] As mentioned above, in the RAN1 #114-bis meeting for Release 18, it was agreed that when the DCI fields (MCS, RV, and NDI fields) of DCI format 1_3 are used for notification purposes other than PDSCH scheduling, the DCI fields of the cell with the smallest serving cell index among the cells in which PDSCH is not scheduled should be used for notification purposes other than PDSCH scheduling (see the bold part in Figures 14 and 15). It is unclear whether a dormant / deactivated cell is also involved in determining the "cell with the smallest serving cell index," since it is one of the cells in which PDSCH is not scheduled.

[0088] As described above, regarding multi-cell PDSCH scheduling using DCI format 1_3, there is no clear definition of terminal control for dormant / deactivated cells (whether or not DCI fields need to be decoded and HARQ-ACK feedback).

[0089] Therefore, when a dormant / deactivated cell exists between the base station and the terminal, a discrepancy may occur, and appropriate communication may not be possible.

[0090] Based on the above analysis, the present embodiment makes the following proposals 1 to 4.

[0091] <Proposal 1> Proposal 1 corresponds to the above analysis 1 and proposes the specification of a sub-codebook for transmitting a HARQ-ACK bit of DCI format 1_3 or a specific cell for which PDSCH scheduling using DCI format 1_3 is not performed and the MCS, RV, and / or NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0092] <Option 1> The sub-codebook for transmitting the HARQ-ACK bit of a specific cell may be set to one of the following alternations (hereinafter referred to as "Alt") either fixedly or semi-statically.

[0093] <Alt. 1> The sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be set as the first sub-codebook.

[0094] In this case, HARQ-ACK feedback control for terminals in cells in which PDSCH scheduling using DCI formats is not performed can be made common between the existing DCI format and DCI formats 1-3.

[0095] <Alt. 2> The sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the second sub-codebook.

[0096] In this case, it is possible to standardize HARQ-ACK feedback control for terminals in each cell where multi-cell PDSCH scheduling is performed using DCI format 1_3.

[0097] Furthermore, even if DCI format 1_3 is dropped (if the terminal fails to decode DCI format 1_3), a codebook can be generated so that the size of the HARQ-ACK CB does not deviate.

[0098] Among the Alts in Option 1 above, the one to be applied to actual communications may be defined by the specifications, or may be dynamically determined based on information contained in any of the higher layer signals, MAC CE, or DCI received from the network (base station).

[0099] <Operation of Terminal> Next, the operation of the terminal in option 1 of proposal 1 will be described with reference to the flow chart of FIG.

[0100] The terminal decodes DCI format 1_3 included in the received PDCCH (S101), and determines whether each cell is a specific cell based on the value of the FDRA field, etc. (S102).

[0101] For cells other than the specific cell (S102: No), the terminal monitors and decodes the PDSCH based on the scheduling of DCI format 1_3 (S103).

[0102] The terminal generates a HARQ-ACK bit for the reception (decoded result) of the PDSCH (S104). Specifically, if the decoding of the PDSCH is successful, the terminal generates a HARQ-ACK bit with a value (e.g., "0") that indicates "ACK", and if the decoding of the PDSCH is unsuccessful, the terminal generates a HARQ-ACK bit with a value (e.g., "1") that indicates "NACK".

[0103] Next, the terminal places the HARQ-ACK bit in the second sub-codebook and transmits the HARQ-ACK bit to the base station (S105).

[0104] On the other hand, for the specific cell (S102: Yes), the terminal decodes a specific field of DCI format 1_3 (S106).

[0105] The terminal generates a HARQ-ACK bit in response to reception (decoding result) of a specific field of DCI format 1_3 (S107).

[0106] Next, the terminal places the HARQ-ACK bit in the first sub-codebook (in the case of Alt. 1) or in the second sub-codebook (in the case of Alt. 2), and transmits the HARQ-ACK bit to the base station (S108).

[0107] There is no particular limitation on the arrangement order of the HARQ-ACK bits in the sub-codebook, and they may be arranged in the order of the serving cell index of the cell corresponding to each HARQ-ACK bit, or in some other order.

[0108] <Option 2> In practice, depending on the number of cells for which PDSCH is scheduled by DCI format 1_3, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be set to one of the following Alts.

[0109] <Alt. 1> If the number of cells for which PDSCH is scheduled by DCI format 1_3 is "1", the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the first sub-codebook, and in other cases, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell may be the second sub-codebook.

[0110] <Alt. 2> If the number of cells for which PDSCH is scheduled by DCI format 1_3 is "1", the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the second sub-codebook, and in other cases, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell may be the first sub-codebook.

[0111] Among the Alts in Option 2, the one to be applied to actual communications may be defined by the specifications, or may be dynamically determined based on information contained in any of the higher layer signals, MAC CE, or DCI received from the network (base station).

[0112] <Option 3> Depending on whether PDSCH scheduling is not notified to any of the cells included in the SoCs, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell may be set to one of the following Alts. Note that whether PDSCH scheduling is performed for each cell included in the SoCs is notified by whether the value of the FDRA field is valid or invalid, or by the cell number corresponding to the value of the scheduled cell indicator field in a table that is predefined and set by higher layer parameters. For example, if the value of the FDRA field is invalid (e.g., "0") for all cells that can be scheduled, PDSCH scheduling is not notified to any of the cells included in the SoCs.

[0113] <Alt. 1> When PDSCH scheduling is not notified to any cell included in the SoCs, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the first sub-codebook, and in other cases, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the second sub-codebook.

[0114] <Alt. 2> When PDSCH scheduling is not notified to any cell included in the SoCs, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the second sub-codebook, and in other cases, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 may be the first sub-codebook.

[0115] Among the Alts in Option 3 above, the one to be applied to actual communications may be defined by the specifications, or may be dynamically determined based on information contained in any of the higher layer signals, MAC CE, or DCI received from the network (base station).

[0116] <Effects of Proposal 1> According to the option and alternation of Proposal 1, in partial scheduling of multi-cell PDSCH scheduling, the sub-codebook for transmitting the HARQ-ACK bit of a specific cell or DCI format 1_3 can be clearly defined. This eliminates discrepancies in recognition of the sub-codebook for the HARQ-ACK bit of a specific cell or DCI format 1_3 between the base station and the terminal, enabling appropriate communication.

[0117] <Proposal 2> Proposal 2 corresponds to the above analysis 2 and proposes a method for determining a reference cell when PDSCH scheduling is not performed using DCI format 1_3 and there is a specific cell in which the MCS, RV and / or NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0118] The reference cell may be a cell that is referenced to count the DAI.

[0119] Furthermore, the reference cell may be used to determine the PUCCH resource offset. That is, since only one offset is reported in one DCI, and multiple PDSCHs exist, it is necessary to clarify from which PDSCH the number of slots is to be counted. The terminal determines the PUCCH resource offset by counting the offset from the PDSCH scheduled for the reference cell.

[0120] Furthermore, the reference cell may be a cell of the last DCI format for determining the PUCCH resource. When transmitting HARQ-ACK bits for each of PDSCHs scheduled by multiple DCIs in one HARQ-ACK CB, it is necessary to clarify in which DCI format a PRI (PUCCH Resource Indicator) notified is to be used. The terminal determines the PUCCH resource based on the PRI notified in the last DCI format of the reference cell.

[0121] <Option 1> When PDSCH scheduling is notified to any cell included in the SoC in which the specific cell exists (when the value of the FDRA field is valid for at least one cell), the terminal may determine the reference cell using one of the following Alts.

[0122] <Alt. 1> PDCCH cell (scheduling cell) is used as the reference cell. In the example of Fig. 6, CC#0, which is the PDCCH cell (scheduling cell), is used as the reference cell.

[0123] <Alt. 2> A cell (specific cell) in which the MCS, RV and / or NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling is defined as a reference cell.

[0124] <Alt. 3> The cell for counting the DCI size / number of PDCCH candidates (number of BDs) / number of CCEs (cell in which the SS set for monitoring DCI format 1_3 is configured) is used as the reference cell.

[0125] <Alt. 4a> The cell with the smallest serving cell index among the cells notified of scheduling (cells with valid FDRA field values) is set as the reference cell.

[0126] <Alt. 4b> The cell with the largest serving cell index among the cells for which scheduling has been notified (cells with valid FDRA field values) is set as the reference cell.

[0127] <Alt. 5a> The cell with the smallest serving cell index among the cells included in the SoCs is set as the reference cell. In the example of Figure 6, CC#1 is set as the reference cell for Set of Cells 1, and CC#5 is set as the reference cell for Set of Cells 1.

[0128] <Alt. 5b> The cell with the largest serving cell index among the cells included in the SoCs is set as the reference cell. In the example of Figure 6, CC#4 is set as the reference cell for Set of Cells 1, and CC#7 is set as the reference cell for Set of Cells 1.

[0129] <Alt. 6a> The reference cell is the cell with the smallest serving cell index among the cells to which scheduling has been notified and among the cells (specific cells) whose MCS, RV and NDI fields in DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0130] <Alt. 6b> The reference cell is the cell with the largest serving cell index among the cells to which scheduling has been notified and among the cells (specific cells) whose MCS, RV and NDI fields in DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0131] Among the Alts in Option 1 above, the one to be applied to actual communications may be defined by the specifications, or may be dynamically determined based on information contained in any of the higher layer signals, MAC CE, or DCI received from the network (base station).

[0132] <Option 2> If PDSCH scheduling is not notified to any of the cells included in the SoCs in which a specific cell exists (if the value of the FDRA field is invalid for all cells that can be scheduled), the reference cell may be determined using one of the following Alts.

[0133] <Alt. 1> The PDCCH cell (scheduling cell) is the reference cell.

[0134] <Alt. 2> A cell (specific cell) in which the MCS, RV and / or NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling is defined as a reference cell.

[0135] <Alt. 3> The cell for counting the DCI size / number of PDCCH candidates (number of BDs) / number of CCEs (cell in which the SS set for monitoring DCI format 1_3 is configured) is used as the reference cell.

[0136] Among the Alts in Option 2, the one to be applied to actual communications may be defined by the specifications, or may be dynamically determined based on information contained in any of the higher layer signals, MAC CE, or DCI received from the network (base station).

[0137] <Variation 1> In the above Option 1 or 2, the cell determined as the reference cell may be different depending on whether the PDCCH cell (scheduling cell) is included in the SoCs. For example, in Option 1, if the PDCCH cell is included in the SoCs, (Alt. 1) the PDCCH cell may be the reference cell, and if the PDCCH cell is not included in the SoCs, (Alt. 2) a specific cell may be the reference cell.

[0138] <Variation 2> In the above-described Option 1 and Option 2, the cell determined as the reference cell may be the same. This reduces the control load for determining the reference cell. For example, the PDCCH cell may be set as the reference cell regardless of whether PDSCH scheduling has been notified to any cell included in the SoC in which the specific cell exists (Alt. 1 of Option 1 and Alt. 1 of Option 2).

[0139] <Advantages of Proposal 2> According to the above-mentioned option and alternation of Proposal 2, the reference cell can be clearly defined in partial scheduling of multi-cell PDSCH scheduling. This eliminates discrepancies in the recognition of the reference cell between the base station and the terminal, enabling appropriate communication.

[0140] The terminal may also count the DAI in the reference cell, determine a PUCCH resource offset in the reference cell, and determine a PUCCH resource based on the PRI indicated in the last DCI format in the reference cell.

[0141] <Proposal 3> Proposal 3 corresponds to the above analysis 3 and proposes reporting of terminal capabilities (UE capability) related to support of partial scheduling in multi-cell PDSCH scheduling using DCI format 1_3.

[0142] The terminal may report terminal capability information (UE capability) that defines information about the terminal's capability regarding partial scheduling to the base station by signaling at an early stage of communication with the base station.

[0143] For example, the terminal capability information may include information indicating whether or not the terminal supports "Scell ​​dormancy indication," information indicating whether or not the terminal supports "enhanced type-3 HARQ-ACK CB trigger," and information indicating whether or not the terminal supports "notification of slot offset value "l" when triggering HARQ-ACK retransmission." Note that the information indicating whether or not the "enhanced type-3 HARQ-ACK codebook trigger" is supported may be specified as a component of FG49-5a / 5b. Furthermore, the slot offset value "l" may be defined by a specification or may be set by a higher layer parameter.

[0144] Furthermore, for example, the terminal capability information may include information indicating whether or not it is permitted for a P(S)Cell that the MCS, RV, and NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling, and information indicating whether or not it is permitted for an Scell ​​that the MCS, RV, and NDI fields of DCI format 1_3 are used for purposes other than PDSCH scheduling.

[0145] A base station receives terminal capability information from a terminal at an initial stage of communication with the terminal. The base station communicates with each terminal according to its capability. For example, the base station does not use the MCS, RV, and NDI fields of DCI format 1_3 transmitted to a terminal that does not have partial scheduling capability for any purpose other than PDSCH scheduling. Furthermore, a terminal that does not have partial scheduling capability does not assume that the MCS, RV, and NDI fields of DCI format 1_3 will be used for any purpose other than PDSCH scheduling.

[0146] The reporting granularity of the terminal capability information of the terminal may be per carrier type (FR1 / FR2-1 / FR2-2, licensed / unlicensed, TDD (Time Division Duplex) / FDD (Frequency Division Duplex)), per band, per terminal, per BC (Band Combination), per FS (Feature Set), or per FSPC (Feature Set Per Component-carrier).

[0147] The prerequisite FG may be at least one of FG49-1 / 1b / 5a / 5b. FG49-1 / 1b shown in Fig. 20 defines functions related to support of DCI formats for multi-cell PDSCH scheduling. FG49-5a / 5b shown in Fig. 21 defines functions related to support of enhanced type-3 HARQ-ACK CB and type-3 HARQ-ACK CB for PDSCH scheduled with DCI format 1_3.

[0148] Furthermore, UE capability signaling (FG49-x) for performing Scell ​​dormancy indication using DCI format 1_3 may be prerequisite, and UE capability signaling (FG49-x) for performing HARQ-ACK retransmission using DCI format 1_3 may be prerequisite.

[0149] <Effects of Proposal 3> According to Proposal 3, it is possible to clearly define terminal capability information related to partial scheduling of multi-cell PDSCH scheduling, which eliminates discrepancies in the recognition of terminal capabilities between the base station and the terminal, enabling appropriate communication.

[0150] <Proposal 4> Proposal 4 corresponds to the above analysis 4, and proposes terminal control for dormant / deactivated cells in PDSCH scheduling using DCI format 1-3.

[0151] <Proposal 4-1> Proposal 4-1 clarifies whether or not the DCI field for a dormant / deactivated Scell ​​in DCI format 1_3 can be used for notification purposes other than PDSCH scheduling.

[0152] <Option 1> In DCI format 1_3, the DCI field for a dormant / deactivated Scell ​​may be usable for notification purposes other than PDSCH scheduling. Note that in Option 1, the DCI field that can be used for notification purposes other than PDSCH scheduling may be the DCI field of the cell with the smallest serving cell index among the cells in the SoCs including the dormant / deactivated cell / BWP and in which the PDSCH is not scheduled.

[0153] <Option 2> In DCI format 1_3, the DCI field for a dormant / deactivated Scell ​​may not be used for notification purposes other than PDSCH scheduling.

[0154] In this case, the specifications may stipulate that the terminal does not decode the DCI field for the dormant / deactivated Scell.

[0155] Furthermore, the terminal does not need to assume a DCI field dedicated to a dormant / deactivated Scell.

[0156] <Option 2-1> In this case, the DCI size may be changed, for example, the DCI field dedicated to the dormant / deactivated Scell ​​may be removed.

[0157] <Option 2-2> Alternatively, the DCI size may remain unchanged, and the DCI field dedicated to the dormant / deactivated Scell ​​may be padded and used as a field for other cells. In this case, zero padding may be performed on the end of DCI format 1_3 or on each DCI field (Type-2 DCI fields such as MCS, RV, NDI, and HPN) by the number of bits padded.

[0158] In addition, in option 2, the DCI field that can be used for notification purposes other than PDSCH scheduling may be the DCI field of the cell with the smallest serving cell index among the active cells / BWPs (non-dormant BWPs) in which PDSCH is not scheduled.

[0159] <Variations> Whether to use the above option 1 or option 2 may be notified to the terminal by any of the SIB, RRC, MAC CE, or DCI.

[0160] Furthermore, the terminal may report to the base station whether it supports option 1 / option 2 depending on the terminal capability (UE capability).

[0161] In this case, the reporting granularity may be per carrier type (FR1 / FR2-1 / FR2-2, licensed / unlicensed, TDD (Time Division Duplex) / FDD (Frequency Division Duplex)), per band, per terminal, per BC (Band Combination), per FS (Feature Set), or per FSPC (Feature Set Per Component-carrier).

[0162] The prerequisite FG may be at least one of FG49-1 / 1b / 5a / 5b.

[0163] Furthermore, UE capability signaling (FG49-x) for performing Scell ​​dormancy indication using DCI format 1_3 may be prerequisite, and UE capability signaling (FG49-x) for performing HARQ-ACK retransmission using DCI format 1_3 may be prerequisite.

[0164] Whether option 1 or option 2 is applied may differ depending on the purpose of the notification (PDSCH scheduling, cell dormancy indication case 2, enhanced type-3 HARQ-ACK codebook trigger, HARQ-ACK retransmission slot offset, etc.).

[0165] (Effect of Proposal 4-1) A terminal receives DCI (DCI format 1_3) used for multi-cell PDSCH scheduling. The control unit determines (assumes) that the DCI fields in dormant and / or deactivated cells are used for notification purposes other than downlink signal scheduling. This operation enables the terminal to perform appropriate control regarding support for dormant / deactivate in multi-cell PDSCH scheduling.

[0166] The terminal receives DCI (DCI format 1-3) used for multi-cell PDSCH scheduling. The control unit determines (assumes) that the DCI fields in the dormant and / or deactivated cells are not used for notification purposes other than downlink signal scheduling. This operation enables the terminal to perform appropriate control regarding support of dormant / deactivate in multi-cell PDSCH scheduling.

[0167] <Proposal 4-2> Proposal 4-2 clarifies HARQ-ACK feedback for dormant / deactivated Scells in DCI format 1_3.

[0168] First, Proposal 4-2 proposes the following Option 1 and Option 2 for at least one HARQ-ACK codebook from among Type-1 / Type-2 / Type-3 / enhanced Type-3 codebooks.

[0169] <Option 1> The terminal does not need to transmit HARQ-ACK information corresponding to dormant / deactivated cells / BWPs among the SoCs scheduled by DCI format 1_3. In other words, the terminal may transmit HARQ-ACK information only for active cells / BWPs (non-dormant BWPs) among the SoCs scheduled by DCI format 1_3.

[0170] <Option 2> The terminal may transmit HARQ-ACK information corresponding to all cells, including dormant / deactivated cells / BWPs, among the SoCs scheduled by DCI format 1_3.

[0171] In this case, the terminal may transmit a NACK as HARQ-ACK information corresponding to the dormant / deactivated cell / BWP.

[0172] Furthermore, if the DCI field for a dormant / deactivated cell / BWP is used for a purpose other than PDSCH scheduling, the terminal may transmit an ACK or NACK as HARQ-ACK information corresponding to the cell.

[0173] <Variation 1> The terminal may report to the base station whether it supports option 1 / option 2 depending on the terminal capability (UE capability).

[0174] In this case, the reporting granularity may be per carrier type (FR1 / FR2-1 / FR2-2, licensed / unlicensed, TDD (Time Division Duplex) / FDD (Frequency Division Duplex)), per band, per terminal, per BC (Band Combination), per FS (Feature Set), or per FSPC (Feature Set Per Component-carrier).

[0175] The prerequisite FG may be at least one of FG49-1 / 1b / 5a / 5b.

[0176] The terminal may be notified of the above option 1 or option 2 by any of the SIB, RRC, MAC CE, or DCI.

[0177] Whether option 1 or option 2 is applied may differ depending on the purpose of the notification (PDSCH scheduling, cell dormancy indication case 2, enhanced type-3 HARQ-ACK codebook trigger, HARQ-ACK retransmission slot offset, etc.).

[0178] Next, Proposal 4-2 makes the following proposal for the case of Type-2 codebook.

[0179] If there is only one active cell / BWP (non-dormant BWP) among the cells included in the SoCs, the terminal may transmit the HARQ-ACK of the PDSCH scheduled in that cell / BWP using the first sub-codebook.

[0180] Alternatively, if there is only one active cell / BWP (non-dormant BWP) among the cells included in the SoCs, the terminal may transmit a HARQ-ACK in the first sub-codebook for the SCell dormancy indication case 2, enhanced type-3 HARQ-ACK codebook trigger, and HARQ-ACK retransmission slot offset notified in the DCI field for that cell / BWP.

[0181] <Variation 2> Either option 1 or option 2 may be set based on whether DCI format 1_3 can be used for purposes other than PDSCH scheduling.

[0182] For example, when a DCI field in DCI format 1_3 corresponding to a cell in dormancy / deactivation is used for purposes other than PDSCH scheduling (when configured to be usable), a setting may be made so that a HARQ-ACK corresponding to the cell in dormancy / deactivation can be transmitted (option 2 is configured), and when a DCI field of a cell in dormancy / deactivation is not used for purposes other than PDSCH scheduling (when not configured to be usable), a setting may be made so that a HARQ-ACK corresponding to the cell in dormancy / deactivation is not transmitted (option 1 is configured). Alternatively, the setting may be made the other way around.

[0183] <Variation 3> Furthermore, when DCI format 1_3 is used for purposes other than PDSCH scheduling (when DCI format 1_3 is configured to be usable), whether or not to transmit ACK / NACK may be configured based on whether DCI format 1_3 is used for PDSCH scheduling or for other purposes.

[0184] For example, when the DCI field of a dormancy / deactivated cell is set to be used for purposes other than PDSCH scheduling, the terminal may transmit a NACK in a cell included in the SoCs (1) if it is unable to receive a PDSCH corresponding to the DCI for PDSCH scheduling, and (2) if it is unable to receive (receive) DCI used for purposes other than PDSCH / PUSCH scheduling, not transmit a NACK. Alternatively, the reverse may be configured.

[0185] (Effect of Proposal 4-2) A terminal receives DCI (DCI format 1_3) used for multi-cell PDSCH scheduling. The terminal determines (assumes) not to transmit acknowledgements corresponding to dormant and / or deactivated cells and / or bandwidth parts among the set of cells for multi-cell PDSCH scheduling. This operation enables the terminal to perform appropriate control regarding support of dormant / deactivate in multi-cell PDSCH scheduling.

[0186] The terminal receives DCI (DCI format 1-3) used for multi-cell PDSCH scheduling. The terminal determines (assumes) to transmit an acknowledgement corresponding to a dormant and / or deactivated cell and / or bandwidth part among a set of cells scheduled for the multi-cell PDSCH. This operation enables the terminal to appropriately control support of dormant / deactivate in multi-cell PDSCH scheduling.

[0187] <Configuration of Base Station> Fig. 22 is a block diagram showing an example of the configuration of a base station 100 according to an embodiment. The base station 100 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 100 communicates with a terminal 200 (see Fig. 23) by radio. The base station 100 may be an intermediate node, a support node, or a terminal (a terminal in SL that communicates with the terminal 200).

[0188] The transmitter 101 transmits a downlink (DL) signal to the terminal 200. For example, the transmitter 101 transmits the DL signal under the control of the controller 103.

[0189] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of terminal 200 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.

[0190] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channels may include a PDSCH (Physical Downlink Shared Channel), and the control channels may include a PDCCH (Physical Downlink Control Channel). For example, the base station 100 transmits control information to the terminal 200 using the PDCCH and transmits downlink data signals using the PDSCH.

[0191] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.

[0192] The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 200. For example, the receiving unit 102 receives the UL signal under the control of the control unit 103.

[0193] The control unit 103 controls the communication operations of the base station 100 , including the transmission processing of the transmission unit 101 and the reception processing of the reception unit 102 .

[0194] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.

[0195] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the terminal 200 and / or data and control information, etc. acquired from a higher layer. Information related to the allocated resources may be included in control information transmitted to the terminal 200.

[0196] Control unit 103 configures PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to PUCCH configuration such as a PUCCH cell timing pattern (PUCCH configuration information) may be reported to terminal 200 by RRC.

[0197] 23 is a block diagram showing an example of the configuration of a terminal 200 according to an embodiment. The terminal 200 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 200 communicates with the base station 10 wirelessly, for example.

[0198] The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives the DL signal under the control of the control unit 203.

[0199] The transmitting unit 202 transmits the UL signal to the base station 10. For example, the transmitting unit 202 transmits the UL signal under the control of the control unit 203.

[0200] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the terminal 200 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

[0201] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels include a PUSCH (Physical Uplink Shared Channel), and the control channels include a PUCCH (Physical Uplink Control Channel). For example, the terminal 200 receives control information from the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.

[0202] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).

[0203] The control unit 203 controls the communication operations of the terminal 200 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .

[0204] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.

[0205] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or a scheduling request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted in the resources of the PUCCH.

[0206] The control unit 203 sets PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern notified by RRC and / or DCI) received from the base station 10. The control unit 203 determines the PUCCH resources to be used for transmitting information to be fed back to the base station 10. Under the control of the control unit 203, the transmission unit 202 transmits the information to be fed back to the base station 10 in the PUCCH resources determined by the control unit 203.

[0207] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.

[0208] <Summary> The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).

[0209] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless contradictory). The above suggestions and options may be combined.

[0210] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

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

[0212] For example, a base station, a terminal, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 24 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment. The above-described base station 100 and terminal 200 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

[0214] Each function in the base station 100 and the terminal 200 is realized by loading specified software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0215] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

[0216] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 200 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

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

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

[0219] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.

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

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

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

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

[0224] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0225] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

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

[0227] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.

[0228] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.

[0229] <Determination method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0230] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

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

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

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

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

[0236] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0237] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values ​​from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.

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

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

[0240] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

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

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

[0244] <Base Station / Mobile Station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0245] Furthermore, the base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 200 may be configured to have the functions of the base station 100 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0246] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 100 may be configured to have the functions of the terminal 200 described above.

[0247] Fig. 25 shows an example configuration of a vehicle 2001. As shown in Fig. 25, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0248] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

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

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

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

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

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

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

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

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

[0257] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0258] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

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

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

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

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

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

[0264] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.

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

[0266] <Time Units such as TTI, Frequency Units such as RB, and Radio Frame Configuration> A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0267] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

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

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

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

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

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

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

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

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

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

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

[0278] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

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

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

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

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

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

[0284] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

[0285] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

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

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

[0288] The disclosures of the specification, drawings and abstract contained in Japanese Patent Application No. 2023-193223, filed on November 13, 2023, are incorporated herein by reference in their entirety.

[0289] One aspect of the present disclosure is useful in wireless communication systems.

[0290] 100 Base station 200 Device 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A terminal having a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines that a field of the downlink control information in a Dormant and / or deactivated cell is used for notification purposes other than scheduling of downlink signals.

2. The terminal according to claim 1, wherein the control unit determines that the field of the downlink control information is used for at least one of secondary cell (Scell) dormancy indication case 2, enhanced type-3 HARQ-ACK codebook trigger, and HARQ-ACK retransmission slot offset.

3. A terminal having a receiving unit that receives downlink control information used for multi-cell scheduling, and a control unit that determines that a field of the downlink control information in a Dormant and / or deactivated cell is not used for notification purposes other than scheduling of downlink signals.

4. The terminal according to claim 1, wherein the control unit determines not to decode a field of the downlink control information of a Dormant and / or deactivated cell.

5. A terminal having: a receiving unit that receives downlink control information used for multi-cell scheduling; and a control unit that determines not to transmit an acknowledgement response corresponding to a Dormant and / or deactivated cell and / or a bandwidth part among a set of cells to be multi-cell scheduled.

6. A terminal having: a receiving unit that receives downlink control information used for multi-cell scheduling; and a control unit that determines to transmit an acknowledgement response corresponding to a Dormant and / or deactivated cell and / or a bandwidth part among a set of cells to be multi-cell scheduled.

Images