Terminal, wireless base station, and wireless communication method

Abstract

This terminal: receives a single piece of first specific downlink control information for scheduling a channel to be transmitted by a plurality of slots, and a single piece of second specific downlink control information for scheduling a channel to be transmitted by a plurality of carriers; and controls channel transmission and reception on the basis of the first specific downlink control information and / or the second specific downlink control information. When scheduling based on both the first specific downlink control information and the second specific downlink control information is performed, the terminal assumes that a single value is set for at least one field in a format of the first specific downlink control information and the second specific downlink control information, and applies a different setting to a cell, a slot, and / or a channel scheduled by the first specific downlink control information and the second specific downlink control information.

Description

[Technical Field]

[0001] The present disclosure relates to a terminal, a radio base station, and a radio communication method that support a mechanism for scheduling data channels transmitted via a plurality of carriers by means of single downlink control information transmitted via a specific carrier. [Background Art]

[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) has standardized the 5th generation mobile communication system (5G, also referred to as New Radio (NR) or Next Generation (NG)), and is further advancing the standardization of the next generation system referred to as Beyond 5G, 5G Evolution or 6G.

[0003] For example, regarding downlink control information (DCI: Downlink Control Information), in 3GPP Release 16 and 17, a function of scheduling PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted via a plurality of slots by means of a single DCI (referred to as single DCI multi-slot PDSCH / PUSCH scheduling) is specified (Non-Patent Document 1).

[0004] Furthermore, 3GPP Release 18 is considering the introduction of a function to schedule PDSCH / PUSCH transmitted by multiple component carriers (CCs) using a single DCI (Non-Patent Document 2). Such a function is called Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling (hereinafter referred to as Single DCI Multi-carrier PDSCH / PUSCH scheduling). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.212 V17.4.0, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Multiplexing and channel coding(Release 17), 3GPP, December 2022 [Non-Patent Document 2] "New WID on Multi-carrier enhancements", RP-213577, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 [Overview of the initiative]

[0006] However, currently, Single DCI Multi-carrier PDSCH / PUSCH scheduling has a problem in that it cannot be used in conjunction with single DCI multi-slot PDSCH / PUSCH scheduling. Specifically, cells included in the same PUCCH group cannot be used simultaneously with single DCI Multi-carrier PDSCH / PUSCH scheduling. Furthermore, it is not possible to schedule multiple slots of multiple CCs using a single DCI.

[0007] In particular, for FR2 (24.25 GHz~71 GHz), the slot length is shorter compared to FR1 (410 MHz~7.125 GHz), so there are concerns that frequent PDCCH (Physical Downlink Control Channel) monitoring will increase the processing load (including power consumption) on the terminal (User Equipment, UE) when using PDSCH / PUSCH scheduling for each slot.

[0008] Furthermore, there is a trade-off between the efficiency gained by using a single DCI (which could also be called the DCI compression effect) and the flexibility of PDSCH / PUSCH scheduling for slots or CCs. However, assuming the combined use of Single DCI Multi-carrier PDSCH / PUSCH scheduling and Single DCI Multi-slot PDSCH / PUSCH scheduling, there is room for improvement in the DCI design.

[0009] Therefore, the following disclosure is made in light of these circumstances and aims to provide terminals, radio base stations, and wireless communication methods that can utilize downlink control information more suitable for the combined use of Single DCI Multi-carrier PDSCH / PUSCH scheduling and Single DCI multi-slot PDSCH / PUSCH scheduling.

[0010] One aspect of the present disclosure is a terminal (UE200) comprising: a receiving unit (control signal / reference signal processing unit 240) that receives a single first specific downlink control information for scheduling channels transmitted by multiple slots and a single second specific downlink control information for scheduling channels transmitted by multiple carriers; and a control unit (control unit 270) that controls the transmission or reception of the channels based on at least one of the first specific downlink control information and the second specific downlink control information, wherein when the control unit performs scheduling based on both the first specific downlink control information and the second specific downlink control information, it assumes that a single value is set for at least one of the fields in the format of the first specific downlink control information and the second specific downlink control information, and applies different settings to at least one of the cells, slots, or channels scheduled by the first specific downlink control information and the second specific downlink control information. [Brief explanation of the drawing]

[0011] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows the frequency band used in the wireless communication system 10. [Figure 3] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 4] Figure 4 shows the functional block diagrams of the gNB100 and UE200. [Figure 5]Figure 5 shows an example of a scheduling method that can be supported by the wireless communication system 10. [Figure 6] Figure 6 shows an example of single DCI multi-slot PDSCH / PUSCH scheduling. [Figure 7] Figure 7 shows an example of data channel (PDSCH / PUSCH) scheduling using DCI. [Figure 8] Figure 8 shows an example of the table settings (part 1) related to the operation example (Opt. 1-2). [Figure 9] Figure 9 shows an example of applying an entry related to the operation example (Opt. 1-2) (part 1). [Figure 10] Figure 10 shows an example of applying the entry related to the operation example (Opt. 1-2) (part 2). [Figure 11] Figure 11 shows an example of the table settings (part 2) related to the operation example (Opt. 1-2). [Figure 12] Figure 12 shows an example of the table settings (part 3) related to the operation example (Opt. 1-2). [Figure 13] Figure 13 shows an example of the hardware configuration of the gNB100 and UE200. [Figure 14] Figure 14 shows an example of the configuration of vehicle 2001. [Modes for carrying out the invention]

[0012] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.

[0013] (1) Overall outline of the wireless communication system FIG. 1 is an overall schematic configuration diagram of a radio communication system 10 according to the present embodiment. The radio communication system 10 is a radio communication system conforming to 5G New Radio (NR), and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

[0014] Note that the radio communication system 10 may be a radio communication system conforming to a scheme called Beyond 5G, 5G Evolution or 6G.

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

[0016] The NG-RAN 20 actually includes a plurality of NG-RAN Nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not illustrated). Note that NG-RAN 20 and 5GC may be simply expressed as a "network".

[0017] The gNB 100 is an NR-compliant radio base station, and performs NR-compliant radio communication with the UE 200. The gNB 100 and the UE 200 can support Massive MIMO that generates a beam with higher directivity by controlling radio signals transmitted from a plurality of antenna elements, carrier aggregation (CA) that uses a plurality of component carriers (CCs) in a bundled manner, and dual connectivity (DC) that simultaneously performs communication between a UE and each of a plurality of NG-RAN Nodes.

[0018] The type of DC can be Multi-RAT Dual Connectivity (MR-DC), which utilizes multiple wireless access technologies, or NR-NR Dual Connectivity (NR-DC), which utilizes only NR. Furthermore, MR-DC can be E-UTRA-NR Dual Connectivity (EN-DC), where the eNB constitutes the master node (MN) and the gNB constitutes the secondary node (SN), or vice versa, NR-E-UTRA Dual Connectivity (NE-DC).

[0019] Furthermore, the wireless communication system 10 may support multiple frequency ranges (FR). Figure 2 shows the frequency bands used in the wireless communication system 10.

[0020] • FR1: 410 MHz ~ 7.125 GHz ·FR2: FR2-1: 24.25 GHz ~ 52.6 GHz ·FR2-2: More than 52.6GHz~71GHz In FR1, a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and a 60 or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

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

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

[0023] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10.

[0024] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol duration (and slot duration). Note that the number of symbols constituting one slot does not necessarily have to be 14 (for example, 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 (for example, 480 kHz or 960 kHz, as shown in Figure 3).

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

[0026] As described above, the wireless communication system 10 may have enhanced functionality for multiple carriers (specifically CCs). Specifically, the wireless communication system 10 supports a function (single DCI multi-slot PDSCH / PUSCH scheduling) that schedules PDSCH (Physical Downlink Shared Channel) / PUSCH (Physical Uplink Shared Channel) transmitted by multiple slots using a single Downlink Control Information (DCI).

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

[0028] More specifically, the wireless communication system 10 may support a function that schedules PDSCH / PUSCH transmitted by multiple CCs using a single DCI (Single DCI Multi-carrier PDSCH / PUSCH scheduling or Single DCI Multi-Cell PDSCH / PUSCH scheduling). Hereinafter, this will be referred to as Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0029] Single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling are both available, and it is not necessary to use both simultaneously; however, the wireless communication system 10 may support the simultaneous use of both.

[0030] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configuration of UE200 will be described. Figure 4 is a functional block configuration diagram of gNB100 and UE200.

[0031] As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception unit 210, an amplifier unit 220, a modulation / demodulation unit 230, a control signal / reference signal processing unit 240, an encoding / decoding unit 250, a data transmission / reception unit 260, and a control unit 270.

[0032] Note that Figure 4 only shows the main functional blocks relevant to the description of the embodiment, and the UE200 (gNB100) has other functional blocks (e.g., a power supply unit). Also, Figure 4 shows the functional block configuration of the UE200; please refer to Figure 12 for the hardware configuration.

[0033] The wireless signal transceiver 210 transmits and receives wireless signals in accordance with NR. By controlling the radio frequency (RF) signals transmitted from multiple antenna elements, the wireless signal transceiver 210 can support Massive MIMO, which generates a more directional beam; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and each of the two NG-RAN Nodes.

[0034] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0035] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (such as gNB100). The modulation / demodulation unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0036] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0037] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

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

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

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

[0041] Furthermore, channels include control channels and data channels. Control channels may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH), among others.

[0042] Furthermore, data channels include PDSCH and PUSCH, among others. "Data" can refer to data transmitted through a data channel.

[0043] The control signal / reference signal processing unit 240 can receive downlink control information (DCI) transmitted from the network. Specifically, the control signal / reference signal processing unit 240 can receive DCI in accordance with the DCI format specified in 3GPP TS38.212. In particular, in this embodiment, it can receive UL and DL scheduling DCI. More specifically, the control signal / reference signal processing unit 240 may receive DCI in accordance with DCI format 0_0, 0_1, 0_2, 1_0, 1_1, 1_2.

[0044] DCI formats 0_0, 0_1, and 0_2 may be interpreted as scheduling grants for ULs. DCI formats 1_0, 1_1, and 1_2 may be interpreted as scheduling assignments for DLs.

[0045] Furthermore, the control signal / reference signal processing unit 240 may receive DCIs corresponding to single DCI multi-slot PDSCH / PUSCH scheduling and DCIs corresponding to Single DCI multi-carrier PDSCH / PUSCH scheduling.

[0046] Specifically, with respect to single DCI multi-slot PDSCH / PUSCH scheduling, the control signal / reference signal processing unit 240 can receive a single DCI (first specific downlink control information) that schedules channels transmitted by multiple slots. Furthermore, with respect to Single DCI multi-carrier PDSCH / PUSCH scheduling, the control signal / reference signal processing unit 240 can receive a single DCI (second specific downlink control information) that schedules channels transmitted by multiple carriers. In this embodiment, the control signal / reference signal processing unit 240 may constitute a receiving unit.

[0047] Here, "channel" may include the control channel and data channel described above, and is not necessarily limited to either the uplink or downlink direction, but typically refers to at least one of PDSCH or PUSCH. "Carrier" may refer to the component carrier (CC), but may also be interpreted simply as a carrier or subcarrier.

[0048] The DCI format applicable to single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling is not limited to any of the scheduling DCIs described above. Alternatively, a specific (novel) DCI for Single DCI multi-carrier PDSCH / PUSCH scheduling (and / or single DCI multi-slot PDSCH / PUSCH scheduling) may be used.

[0049] Furthermore, the control signal / reference signal processing unit 240 may transmit capability information of the UE200 to the network. In particular, in this embodiment, the control signal / reference signal processing unit 240 can transmit UE Capability Information (see Figure 1) related to scheduling to the gNB100.

[0050] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).

[0051] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0052] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on Hybrid ARQ (Hybrid automatic repeat request).

[0053] The control unit 270 controls each functional block that constitutes the UE200. In particular, in this embodiment, the control unit 270 controls the transmission or reception of a channel (e.g., PDSCH / PUSCH, hereinafter the same) based on DCI (first specific downlink control information, hereinafter abbreviated as single DCI multi-slot PDSCH / PUSCH scheduling) for single DCI multi-slot PDSCH / PUSCH scheduling.

[0054] Furthermore, the control unit 270 controls the transmission or reception of the channel based on the DCI (second specific downlink control information, hereinafter abbreviated as Single DCI Multi-carrier PDSCH / PUSCH scheduling) for Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0055] Thus, the control unit 270 may control the transmission or reception of a channel based on at least one of the DCI for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI for Single DCI multi-carrier PDSCH / PUSCH scheduling. Furthermore, as described above, single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling may be used simultaneously, and the control unit 270 may execute control based on both scheduling DCIs in parallel.

[0056] When the control unit 270 performs scheduling based on both single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling, it can be assumed that the scheduling functionality is more limited than when performing scheduling based on either single DCI multi-slot PDSCH / PUSCH scheduling or Single DCI multi-carrier PDSCH / PUSCH scheduling.

[0057] Scheduling features are not particularly limited, but examples include search space (SS), DCI format, and aggregation level.

[0058] SS is a set of candidate control channels formed by CCE (Control channel element) at a specific aggregation level, and UE200 may decode this set of control channels. In other words, SS may be defined in relation to the maximum number of blind decoding attempts in UE200. Furthermore, SS may be interpreted as including PDCCH CSS (Common Search Space) or CORESET (control resource sets) for the CSS set.

[0059] The aggregation level indicates the number of CCEs assigned to the PDCCH, and may be specified as 1, 2, 4, 8, or 16, but a larger value may also be used.

[0060] Furthermore, the control unit 270 may assume that at least one of the following is limited: the number of slots scheduled by single DCI multi-slot PDSCH / PUSCH scheduling, and the number of carriers (CCs) scheduled by Single DCI multi-carrier PDSCH / PUSCH scheduling.

[0061] When the control unit 270 performs scheduling based on both single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling, it may assume that a single value is set for at least one field in the DCI format for single DCI multi-slot PDSCH / PUSCH scheduling and for Single DCI multi-carrier PDSCH / PUSCH scheduling. Specifically, the control unit 270 may assume that one identical value is set for at least one field in both DCIs. The fields of the DCI are not particularly limited. Examples of specific setting values ​​will be described later.

[0062] While making such assumptions, the control unit 270 may apply different settings to at least one of the cells, slots, or channels scheduled by DCI for single DCI multi-slot PDSCH / PUSCH scheduling and DCI for single DCI multi-carrier PDSCH / PUSCH scheduling. The cell type (primary cell (PCell), primary / secondary cell (PSCell), and secondary cell (SCell)) is not particularly limited, and a cell group (master or secondary) may be the target. The channel type is also not particularly limited and may be in the UL direction or DL ​​direction, but here, PDSCH / PUSCH may be the target.

[0063] Furthermore, the control unit 270 may apply different settings to multiple channels that are scheduled simultaneously, based on multiple entries associated with a single index value notified by at least one of single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling.

[0064] Specifically, the control unit 270 can apply different settings to multiple channels (specifically PDSCH / PUSCH, hereinafter sometimes collectively referred to as PXSCH) that are simultaneously scheduled by the DCI, based on multiple entries (for example, entry #1 to 4, each entry may contain one or more setting items) associated with a single row index value communicated by the DCI. For example, the value of entry #1 may be applied to PXSCH #1, entry #2 to PXSCH #2, entry #3 to PXSCH #3, and entry #4 to PXSCH #4, which are simultaneously scheduled by the DCI.

[0065] Furthermore, the control unit 270 may apply the entry to multiple slots or multiple cells. Specifically, the control unit 270 may apply the contents of a particular entry (e.g., entry#1) to multiple slots or cells in common.

[0066] The order in which multiple entries (e.g., entry #1 to 4) are applied in the time direction (slots) and frequency direction (CC) may be either from the time direction to the frequency direction (CC index order) or from the frequency direction (CC index order) to the time direction.

[0067] Alternatively, the control unit 270 may apply the entry to each cell or cell group. Specifically, the control unit 270 may apply the contents of a particular entry (e.g., entry #1) to each cell or cell group. In this case as well, the order in which multiple entries (e.g., entry #1 to 4) are applied in the time direction (slot) and frequency direction (CC) may be from the time direction to the frequency direction (CC index order), or from the frequency direction (CC index order) to the time direction.

[0068] Furthermore, the gNB100 may be equipped with functions corresponding to the UE200 described above. Specifically, the gNB100 (control signal / reference signal processing unit 240) may constitute a transmission unit that transmits single DCI multi-slot PDSCH / PUSCH scheduling for scheduling channels transmitted by multiple slots, and Single DCI multi-carrier PDSCH / PUSCH scheduling for scheduling channels transmitted by multiple carriers.

[0069] Furthermore, the gNB100 (control unit 270) configures a control unit that performs the settings for single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI Multi-carrier PDSCH / PUSCH scheduling. When performing scheduling based on both single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI Multi-carrier PDSCH / PUSCH scheduling, a single value may be set for at least one field of the DCI format for single DCI multi-slot PDSCH / PUSCH scheduling and the DCI format for Single DCI Multi-carrier PDSCH / PUSCH scheduling. While making such a setting, the gNB100 (control unit 270) may instruct at least one of the cells, slots, or channels scheduled by single DCI multi-slot PDSCH / PUSCH scheduling to have different settings.

[0070] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation related to DCI transmission and reception when Single DCI Multi-carrier PDSCH / PUSCH scheduling and Single DCI Multi-slot PDSCH / PUSCH scheduling are used in combination will be described, in particular, while explaining the DCI design and related operations.

[0071] (3.1) Premise As described above, the wireless communication system 10 may support the function of scheduling multiple slot PDSCH / PUSCH using a single DCI (single DCI multi-slot PDSCH / PUSCH scheduling). Single DCI multi-slot PDSCH / PUSCH scheduling is specified in 3GPP Releases 16 and 17.

[0072] Furthermore, the wireless communication system 10 may support a function that schedules PDSCH / PUSCH of multiple CCs using a single DCI (Single DCI Multi-carrier PDSCH / PUSCH scheduling).

[0073] Figure 5 shows an example of a scheduling scheme that can be supported by the wireless communication system 10. Figure 6 shows an example of single DCI multi-slot PDSCH / PUSCH scheduling.

[0074] Single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling have the following characteristics compared to the conventional method of preparing a DCI for each CC and scheduling them one by one.

[0075] • (Advantages): Reduces the load (number of blind decodes (BDs)) caused by monitoring DCI (PDCCH). Also reduces the total PDCCH overhead (the smaller the size of Single DCI compared to the conventional DCI × CC count, the more effective it is). • (Disadvantages): It is not possible to change the instructions for each CC in detail (if this were possible, the size of the Single DCI would increase, and the error rate and overhead of the PDCCH would increase). If the PDCCH makes a mistake, data reception for all CCs will fail.

[0076] In this embodiment, Single DCI Multi-carrier PDSCH / PUSCH scheduling may be used in conjunction with Single DCI Multi-slot PDSCH / PUSCH scheduling. In conventional systems (up to 3GPP Release 18 may be assumed), Single DCI Multi-carrier PDSCH / PUSCH scheduling and Single DCI Multi-slot PDSCH / PUSCH scheduling cannot be used together in cells included in the same PUCCH group. Furthermore, it is not possible to schedule multiple slots of multiple CCs with a single DCI.

[0077] In particular, since the slot length in FR2 is shorter than that of FR1 (see Figure 3), there are concerns that the load and power consumption of the UE200 will increase due to frequent PDSCH monitoring when using PDSCH / PUSCH scheduling per slot. Therefore, in order to utilize Single DCI Multi-carrier PDSCH / PUSCH scheduling for FR2, it is desirable to be able to use Single DCI Multi-slot PDSCH / PUSCH scheduling in conjunction with it.

[0078] Figure 7 shows an example of scheduling data channels (PDSCH / PUSCH) using DCI. As shown in Figure 7, scheduling of multiple slots on the same CC and multiple CCs can be performed using different DCIs (upper part of Figure 7). Furthermore, scheduling of multiple slots on multiple CCs can be performed using a single DCI (lower part of Figure 7).

[0079] As mentioned above, there is a trade-off between the compression effect of DCI (efficiency achieved by using a single DCI) and the flexibility of PDSCH / PUSCH scheduling for slots or CCs. Specifically, in existing single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling, some DCI fields can have common settings applied across multiple slots / CCs, while other DCI fields can have different settings applied. Even in the case of multi-carrier and multi-slot scheduling (a combination of single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling), where one DCI schedules multiple slots of multiple CCs, it is preferable to design a DCI that is suitable for a wider range of applications and environments while taking advantage of the benefits of multi-carrier and multi-slot scheduling.

[0080] The following describes examples of how to apply common or individual settings to multiple slots / cells (CCs) based on which DCI field is targeted.

[0081] (3.2) Example of operation (3.2.1) Operation overview The following operational examples demonstrate the application of single DCI multi-slot PDSCH / PUSCH scheduling and Single DCI multi-carrier PDSCH / PUSCH scheduling (multi-carrier and multi-slot scheduling), which supports scheduling multiple slots of multiple CCs using a single DCI. This enables efficient scheduling from the perspective of reducing DCI overhead and PDCCH monitoring load.

[0082] By leveraging the benefits of multi-carrier and multi-slot scheduling, DCI designs are realized that are suitable for a wider range of applications and environments.

[0083] For at least one field of the DCI used for multi-carrier and multi-slot scheduling, one of the following options may be applied:

[0084] • Opt. 1: A single value is notified in the DCI. • Opt.2: Values ​​for each cell / cell group / slot / slot group / PDSCH / PUSCH are notified in the relevant DCI. • Opt.3: Two or more of the above options may apply. The application of such options may be applied to each field of the UL grant / DL assignment.

[0085] Furthermore, the following assumptions may be made in this example of operation.

[0086] Regarding DCI used for multi-carrier and multi-slot scheduling, it may be an extension of an existing DCI format (multi-carrier scheduling DCI, DCI format 0_1 / 1_1, or DCI format 0_2 / 1_2), or it may be defined as a new DCI format.

[0087] The number of cells / slots / PDSCHs / PUSCHs scheduled by the DCI is 1 or more, and this example of operation may also apply when the number of cells / slots / PDSCHs / PUSCHs scheduled by the DCI is 1.

[0088] (3.2.2) Examples of sub-options Next, we will explain examples of sub-options for each option. Details of each option will be discussed later.

[0089] (3.2.2.1) Option 1 • Opt. 1-1: A single value is set for the DCI format. • Opt. 1-2: A single value is set for the DCI format, but different settings are possible for each cell / cell group / slot / slot group / PDSCH / PUSCH scheduled by that DCI (joint indication / joint coding). • Opt. 1-3: Applies only to specific cells / cell groups / slots / slot groups / PDSCH / PUSCH scheduled by the DCI in question.

[0090] (3.2.2.2) Option 2 • Opt. 2-1: Common values ​​can be set between slots / slot groups / PDSCH / PUSCH within the same cell / cell group scheduled by the DCI, while different settings can be set between cells / cell groups. • Opt. 2-2: Apply different settings to each cell / cell group / slot / slot group / PDSCH / PUSCH scheduled by the DCI.

[0091] (3.2.2.3) Option 3 As mentioned above, in Opt.3, two or more of Opt1 and Opt2 (including sub-options) may be applied. In this case, which options are applied may be determined by one of the following:

[0092] • Opt.3-1: Configured from gNB100 to UE200 • Opt. 3-2: Different options apply depending on the conditions.

[0093] (3.2.3) Supplement Furthermore, the application of each option for each field of DCI may be predetermined by the 3GPP specification or notified by RRC / SIB / MAC CE (Control Element) / DCI. The application of options may be determined on a case-by-case basis.

[0094] A cell group may be intended to be a subgroup of a scheduled cell, or it may be interpreted as containing some kind of group related to cells. Furthermore, the cells included in a cell group may be set by RRC, or multiple cell groups may be set by RRC, and activation / deactivation of cell groups may be possible by MAC CE. Alternatively, it may be notified by DCI.

[0095] A slot group may be intended as a subgroup of scheduled slots, or it may be interpreted as containing any group related to slots. Furthermore, the method of grouping slots (such as the number of slots included in a slot group) may be set by RRC / MAC CE / DCI, or it may be linked to the settings of the SS set on which the DCI monitor is set (such as the monitoring period), or linked to the frame, as predetermined by the 3GPP specification.

[0096] (3.2.4) Details of each option (3.2.4.1) Opt.1-1 This option may involve the notification of multiple DCI fields in combination. The combination of DCI fields may be predetermined by the 3GPP specification or notified by RRC / SIB / MAC CE / DCI.

[0097] Examples of DCI field combinations include, but are not limited to, the Carrier indicator field (co-scheduled cell indicator) and the BWP indicator.

[0098] Additionally, the following fields may be targeted.

[0099] • Ex.1: A field where different values ​​cannot be set for each PDSCH / PUSCH scheduled by the DCI. Examples of applicable fields for DL ​​assignment / UL grant are as follows:

[0100] Identifier for DCI formats TRS (Target Emergency Response System) indication ·PDCCH monitoring adaptation indication • Ex.2: The single value notified applies to all PDSCH / PUSCH scheduled by the DCI in question. While DCI compression is achieved, the flexibility of settings for each CC / slot is limited.

[0101] (3.2.4.2) Opt.1-2 This option may apply joint indication / joint coding / joint encoding. Specifically, a table containing multiple entries for one or more configuration items may be configured. In this case, the field of the DCI may specify the row index value.

[0102] Figure 8 shows an example of table configuration (part 1) related to the operation example (Opt. 1-2). When a table is configured as shown in Figure 8, the row index is notified by the DCI. The values ​​of entry#1 may be applied to PXSCH#1, entry#2 to PXSCH#2, entry#3 to PXSCH#3, and entry#4 to PXSCH#4, which are simultaneously scheduled by the DCI.

[0103] As an interpretation of each entry (Opt. 1), it may be assumed that the settings are notified for each cell / slot according to the same table. Figure 9 shows an example of the application (1) of entries related to the operation example (Opt. 1-2). As shown in Figure 9, each entry may be interpreted as either (i) applied to each PDSCH / PUSCH in the order of time direction → CC index, or (ii) applied to each PDSCH / PUSCH in the order of CC index → ​​time direction.

[0104] Alternatively, as an interpretation of each entry (Opt. 2), a separate table may be set up for each Cell / cell group. Figure 10 shows an example (part 2) of applying entries related to the operation example (Opt. 1-2). Figure 10 shows an example for the TDRA (Time Domain Resource Allocation) field, and as shown in Figure 10, the row index of the combination table of settings for each CC may be specified by the DCI field. In addition, the row index of the combination table of settings for multiple slots of each CC may be specified by the value of each entry.

[0105] Furthermore, this option may have the following sub-options:

[0106] • Opt. 1-2-1: The RRC / SIB sets up a table containing entries for the maximum number of PDSCH / PUSCH that can be scheduled by the DCI, and applies the entries corresponding to the PDSCH / PUSCH that were actually scheduled. In this case, the cell / cell group / slot / slot group / PDSCH / PUSCH that are actually scheduled may be notified by a DCI field other than the DCI field in question.

[0107] Opt. 1-2-2: The RRC sets up a table containing entries for the number of PDSCH / PUSCH that can be scheduled by the DCI, and the DCI field notifies the DCI field of the row index containing entries for the number of PDSCH / PUSCH that are actually scheduled.

[0108] Figure 11 shows an example of the table settings (part 2) related to the operation example (Opt. 1-2). As shown in Figure 11, if row index 0 is specified by the DCI field for Config. Element, UE200 can assume that four PDSCH / PUSCH events (corresponding to entry #1 to 4) will actually be scheduled.

[0109] Alternatively, if row index 2 is specified by the DCI field, the UE200 can assume that three PDSCH / PUSCH events (corresponding to entry #1 to #3) will actually be scheduled.

[0110] Furthermore, regarding the relationship between the table described above and the table for single-cell multi-slot scheduling / single-slot multi-cell scheduling, one of the following options may be applied.

[0111] • Opt. 1: Separate tables are set up for multi-cell and multi-slot scheduling. • Opt. 2: Use a table shared with single-cell multi-slot scheduling / single-slot multi-cell scheduling. • Opt. 3: Use the table of a specific cell among the cells that can be scheduled by the DCI. Alternatively, in this option (Opt.1-2), multiple DCI fields may be combined and notified. Figure 12 shows an example of a table setting (part 3) related to the operation example (Opt.1-2). As shown in Figure 12, a table combining multiple DCI fields (A, B) may be used. The combination of DCI fields may be predetermined by the 3GPP specification or notified by RRC / SIB / MAC CE / DCI.

[0112] Examples of DCI field combinations include, for example, any two or more of the following: Carrier indicator field (co-scheduled cell indicator), BWP indicator, FDRA (Frequency Domain Resource Allocation), VRB (Virtual Resource Block)-to-PRB (Physical Resource Block) mapping, and PRB binding size indicator.

[0113] (3.2.4.3) Opt. 1-3 With this option, the number of cells / cell groups / slots / slot groups / PDSCH / PUSCH to which the settings notified by the DCI field apply may be one or more.

[0114] Furthermore, the applicable cell / cell group / slot / slot group / PDSCH / PUSCH may be explicitly notified by RRC / SIB / MAC CE / DCI, or it may be implicitly determined based on RRC settings, etc. For example, the settings of a field may be applied to the PDSCH / PUSCH of a cell for which a specific RRC parameter has been set.

[0115] (3.2.4.4) Opt.2-1 With this option, the size of the DCI field may be set to one of the following:

[0116] • The sum of the sizes of the field for each cell / cell group that can be scheduled simultaneously. The product of the maximum number of cells / cell groups that can be scheduled simultaneously and the maximum value of that field for each cell / cell group that can be scheduled simultaneously. The field may be applied to each PDSCH / PUSCH in the order of MSB (most significant bit) / LSB (least significant bit) to CC index.

[0117] Furthermore, a method for setting different values ​​for multiple cells / cell groups may be a joint indication. For example, if a table like the one shown in Figure 8 is set up, the row index will be notified by the DCI, and entry#1 may be applied to at least one PDSCH / PUSCH of CC#1 that is scheduled concurrently.

[0118] Similarly, the value of entry#2 may be applied to at least one PDSCH / PUSCH in CC#2, the value of entry#3 may be applied to at least one PDSCH / PUSCH in CC#3, and the value of entry#4 may be applied to at least one PDSCH / PUSCH in CC#4.

[0119] (3.2.4.5) Opt.2-2 With this option, the size of the DCI field may be set to one of the following:

[0120] • The sum of the sizes of the field for each cell / cell group / slot / slot group / PDSCH / PUSCH that can be scheduled simultaneously. The product of the maximum number of cells / cell groups / slots / slot groups / PDSCH / PUSCHs that can be scheduled simultaneously and the maximum value of the field for each cell / cell group that can be scheduled simultaneously. The field may be applied to each PDSCH / PUSCH in the order of MSB / LSB in the time direction → CC index, or it may be applied to each PDSCH / PUSCH in the order of CC index → ​​time direction. Furthermore, the flexibility of setting the DCI field (such as the field size) may be limited.

[0121] (3.2.4.6) Opt.3-1 In this option, settings from the gNB100 may be notified via RRC / SIB / MAC CE / DCI, or a combination of these.

[0122] Furthermore, settings from gNB100 may be notified for each field, or they may be notified to multiple fields at once. UE200 may change its assumed DCI size according to the settings from gNB100.

[0123] (3.2.4.7) Opt.3-2 In the case of this option, at least one of the following conditions may apply:

[0124] • Scheduled CC is either intra-band only, or includes inter-band as well. For intra-band only, it is acceptable to have many common fields between CCs (resulting in a smaller DCI size).

[0125] • Scheduled CC is intra-FR only, or also includes inter-FR. If only Intra-FR is used, it is acceptable to have many common fields between CCs (resulting in a smaller DCI size).

[0126] • The scheduled CC includes the specified FR • The number of scheduled CCs (the number dynamically notified or the maximum number set quasi-statically) is greater than or less than the specified value. • Scheduled CC includes only one SCS or multiple SCSs. If only a single SCS is used, it is acceptable to have many common fields between CCs (resulting in a smaller DCI size).

[0127] • Scheduled CC includes a specific SCS combination • Scheduled CCs may consist of licensed CCs only, include CCs in unlicensed frequency bands, or consist of CCs in unlicensed frequency bands only.

[0128] (3.2.5) UE capability The UE Capability Information for the above-mentioned options of the UE200 may be set as follows:

[0129] Specifically, UE capability may be defined separately for each DCI field or for multiple DCI fields. Furthermore, UE capability may be defined separately for intra-band and inter-band applications.

[0130] The granularity for reporting UE capability may be one of the following: Per-UE, Per-FR, Per-TDD / FDD, Per-band, Per-BC (Band Combination), Per-FS (Feature Set), or Per-FSPC (Feature Set Per CC).

[0131] (3.2.6) Example of application to each field of DL assignment The following describes examples of applying the above options to each field of a DL assignment. The following options may be applied to each field of a DL assignment. However, the application of options per field is illustrative and does not prevent the application of different options.

[0132] ·DCI format identifier:Opt.1-1 ·DAI (Downlink Assignment Index):Opt.1-1 • Carrier indicator: Opt.1 (may be defined as a single field for specifying multiple scheduled cells, and may be interpreted as any of Opt.1-1 / 1-2 / 1-3), or Opt.2 (may be defined to specify each of the multiple scheduled cells individually in a field) ·TPC command for PUCCH:Opt.1-1 ·PRI (PUCCH resource indicator): Opt.1-1 ·PDSCH-to-HARQ_feedback timing indicator:Opt.1-1 • TDRA: Opt.1-1 (may be defined as a single field to specify a common TDRA list setting for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify the index of a combination of TDRA settings for multiple scheduled cells / slots), or Opt.2 may be applied (may be defined to specify the row index value of the TDRA list for each of the multiple scheduled cells / slots individually in separate fields). The slots to which resources are allocated by this field may be contiguous or non-contiguous. Furthermore, the size of the TDRA field may be expanded compared to the existing DCI format. In conjunction with this expansion, the sizes of other fields may be reduced (compared to DCI for multi-carrier and multi-slot scheduling).

[0133] For TDRA, if Opt. 1-2 applies, a table containing entries for multiple PDSCHs may be set up by RRC for K0 (time difference between DCI slot and PDSCH slot), SLIV (Start and Length Indicator Value), and Mapping type, as shown in the TDRA list in Figure 10, and the row index value may be notified by the TDRA field.

[0134] • FDRA: Opt.1-1 (may be defined as a single field to specify a common FDRA setting for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify an index for a combination of FDRA settings for multiple scheduled cells / slots), or Opt.2 (may be defined to specify the FDRA setting for each of the multiple scheduled cells / slots individually in separate fields, and the same setting may be applied to multiple slots in the same cell). Regarding FDRA, if Opt. 1-2 applies, the RRC may set combinations of candidate FDRA values ​​for each of the multiple cells / slots. In this case, the interpretation of the FDRA field common to all CCs may differ from the conventional method (for example, interpreting it as a broadband FDRA including multiple intra-band CCs, or changing the interpretation for each scheduled CC). Furthermore, FDRA may be set in combination with the settings of other fields.

[0135] • BWP indicator: Opt.1-1 (may be defined as a single field to specify a common BWP index for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify an index for a combination of BWP indices for multiple scheduled cells / slots), Opt.1-3 (may be defined as a field to specify a common BWP index for a specific scheduled cell / cell group among multiple scheduled cells), or Opt.2 (may be defined to specify the BWP index value for each of the multiple scheduled cells / slots individually in separate fields).

[0136] The BWP indicator may also be set in combination with the settings of other fields.

[0137] • Rate matching indicator: Opt.1-1 (may be defined as a single field to specify a common rate matching pattern for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify an index for combinations of rate matching patterns for multiple scheduled cells / slots), Opt.1-3 (may be defined as a field to specify a common value for a specific scheduled cell / cell group among multiple scheduled cells), or Opt.2 (may be defined to specify rate matching pattern values ​​for each of multiple scheduled cells / slots individually in separate fields). Regarding the rate matching indicator, if Opt. 1-2 is applied, the RRC may set a combination of rate matching patterns for each of the multiple cells.

[0138] • ZP-CSI-RS trigger: Opt.1-1 (may be defined as a single field to specify a common aperiodic ZP-CSI-RS resource set value for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify the index of a combination of aperiodic ZP-CSI-RS resource sets for multiple scheduled cells / slots), Opt.1-3 (may be defined as a field to specify a common value for a specific scheduled cell / cell group among multiple scheduled cells), Opt.2 (may be defined to specify the aperiodic ZP-CSI-RS resource set value for each of the multiple scheduled cells / slots individually in separate fields). Alternatively, this field may not be expected in Single DCI Multi-carrier PDSCH / PUSCH scheduling.

[0139] If Opt. 1-2 is applied to the ZP (Zero Power)-CSI-RS trigger, the RRC may configure the combination of aperiodic ZP-CSI-RS resource sets for each of the multiple cells.

[0140] • MCS (Modulation and Coding Scheme): Opt.1-1 (may be defined as a single field to specify a common MCS index value for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify the index of a combination of MCS for multiple scheduled cells / slots), Opt.2 (may be defined to specify the MCS index value for each of the multiple scheduled cells / slots individually in separate fields) Regarding MCS, if Opt. 1-2 is applied, the RRC may set combinations of MCS indices for each of the multiple cells / slots. Also, if Opt. 2 is applied, the difference with the settings for other cells / slots may be notified.

[0141] ·NDI (New-Data Indicator) / RV (Redundancy Version):Opt.2 The RV size may be smaller than before, and it may be specified that only 0 or 2, or 0 or 1, can be specified in the DCI.

[0142] • 2nd TB (Transport Block): Opt.1-1 (The presence or absence of a 2nd TB may be determined commonly across CCs), Opt.1-2, Opt.1-3, or Opt.2 (Enabling / disabling may be set for each CC) • HPN (HARQ Process Number): Opt.1-1 (may be defined as a single field to specify a common HPN value for multiple scheduled cells / slots), Opt.1-2 (may be defined as a field to specify the index of HPN combinations for multiple scheduled cells / slots), Opt.2 (may be defined to specify HPN values ​​for each of the multiple scheduled cells / slots individually in separate fields) • One-shot HARQ-ACK request: Opt. 1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.) • Enhanced Type 3 codebook indicator: Opt. 1-1 (However, this field may be considered not to be intended for DCI for multi-carrier and multi-slot scheduling) • PDSCH group index: Opt.1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.) • New feedback indicator: Opt. 1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.) • Number of requested PDSCH group(s): Opt.1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.) • HARQ-ACK retransmission indicator: Opt. 1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.) • Antenna port(s): Opt.1-1 (may be defined as a single field to specify the AP for each of multiple scheduled cells), Opt.1-2 (may be defined as a field to specify the index of the AP combination for multiple scheduled cells / slots), or Opt.2 (may be defined to specify each of multiple scheduled cells individually in a separate field) Depending on specific conditions (for example, whether the scheduled cell is an intraband or not), one of the above options may be switched.

[0143] • Transmission configuration indication: Opt.1-1 (may be defined as a single field to specify the TCI for each of the multiple scheduled cells), Opt.1-2 (may be defined as a field to specify the index of the TCI combination for multiple scheduled cells / slots), or Opt.2 (may be defined to specify each of the multiple scheduled cells individually in a separate field). Depending on specific conditions (for example, whether the scheduled cell is an intraband or not), one of the above options may be switched.

[0144] • SRS request: Opt.1-1 (Assumed to be a notification for all scheduled cells), Opt.1-2 (May be defined as a field to specify an index for a combination of SRS request settings for multiple scheduled cells / slots), Opt.1-3 (Assumed to be a notification for a specific cell), or Opt.2 (May be defined to specify each of multiple scheduled cells individually in a field) Note that this field may not be expected in DCI for multi-carrier and multi-slot scheduling. The combination of SRS requests for each of the multiple cells may be set by RRC.

[0145] • SRS offset indicator: Opt.1-1 (Assumed to notify all scheduled cells), Opt.1-2 (May be defined as a field to specify the index of combinations of candidate SRS offset values ​​for multiple scheduled cells / slots), Opt.1-3 (Assumed to notify specific cells), or Opt.2 (May be defined to specify each of multiple scheduled cells individually in a field) Note that this field may not be considered in DCI for multi-carrier and multi-slot scheduling. The combination of candidate SRS offset values ​​for each of the multiple cells may be set by RRC.

[0146] ·CBG (Code Block Group) transmission information (CBGTI):Opt.1 However, the field in question may not be considered in DCI for multi-carrier and multi-slot scheduling, or it may only be considered when there is one PDSCH to be scheduled.

[0147] ·CBG flushing out information (CBGFI): Opt.1 However, the field in question may not be considered in DCI for multi-carrier and multi-slot scheduling, or it may only be considered when there is one PDSCH to be scheduled.

[0148] • DMRS sequence initialization: Opt.1-1 (May be defined as a single field to specify settings common to multiple scheduled cells / slots) • Priority indicator: Opt. 1-1 (May be defined as a single field to specify a setting common to multiple scheduled cells) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0149] • ChannelAccess-CPext: Opt.1-1 (Assumed to notify all scheduled cells), or Opt.1-3 (Assumed to notify specific cells) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0150] • Minimum applicable scheduling offset indicator: Opt. 1-1 (assuming notification for all scheduled cells), Opt. 1-3 (assuming notification for specific cells), or Opt. 2 (may be defined to specify each of multiple scheduled cells individually). However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0151] • SCell dormancy indication: Opt. 1-1 (However, this field may be considered not to be anticipated in DCI for multi-carrier and multi-slot scheduling.) • PDCCH monitoring adaptation indication: Opt. 1-1 (assumed to be a notification for all scheduled cells), Opt. 1-3 (assumed to be a notification for a specific cell), or Opt. 2 (may be defined to specify each of multiple scheduled cells individually in a field) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0152] • PUCCH Cell indicator: Opt. 1-1 (However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.)

[0153] (3.2.7) Examples of application to each field of UL grant The following describes examples of applying the above options to each field of a UL grant. The following options may be applied to each field of a UL grant. However, the application of options per field is illustrative and does not prevent the application of different options. Note that the same field settings as for DL ​​assignments are omitted.

[0154] • DFI (Downlink Feedback Information) flag: Opt.1-1 (Assumed to notify all scheduled cells), Opt.1-3 (Assumed to notify specific cells), or Opt.2 (May be defined to specify each of multiple scheduled cells individually in fields) However, it may be assumed that the field in question is not intended for DCI for multi-carrier and multi-slot scheduling. • TPC command for scheduled PUSCH: Opt.1-1 (Assumed to be a notification to all scheduled cells / slots), Opt.1-2 (May be defined as a field to specify an index for a combination of TPC command settings for multiple scheduled cells / slots), Opt.1-3 (Assumed to be a notification to a specific cell), or Opt.2 (May be defined to specify each of multiple scheduled cells / slots individually in a field) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0155] • UL / SUL (Supplementary Uplink) indicator: Opt.1-1 (Assumed to notify all scheduled cells), Opt.1-3 (Assumed to notify specific cells), or Opt.2 (May be defined to specify each of multiple scheduled cells individually in fields) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0156] • SRS resource set indicator: Opt.1-1 (may be defined as a single field to specify the AP for each of multiple scheduled cells), Opt.1-2 (may be defined as a field to specify the index of the SRS resource set combination for multiple scheduled cells / slots), or Opt.2 (may be defined to specify each of multiple scheduled cells individually in a separate field) Depending on specific conditions (for example, whether the scheduled cell is an intraband or not), one of the above options may be switched.

[0157] SRS resource indicator: Opt.1-1 (may be defined as a single field to specify the SRS resource for each of multiple scheduled cells), Opt.1-2 (may be defined as a field to specify the index of AP combinations for multiple scheduled cells / slots), or Opt.2 (may be defined to specify each of multiple scheduled cells individually in a separate field). Depending on specific conditions (for example, whether the scheduled cell is an intraband or not), one of the above options may be switched.

[0158] • PTRS-DMRS association: Opt.1-1, Opt.1-2 (may be defined as a field to specify the index of the combination of PTRS-DMRS associations for multiple scheduled cells / slots), or Opt.2 (may be defined to specify each of the multiple scheduled cells individually in a field) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0159] • beta_offset indicator: Opt.1-1 (Assumes notification for all scheduled cells / slots) or Opt.1-3 (Assumes notification for specific cells) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0160] • UL-SCH indicator: Opt.1-1 (Assumed to notify all scheduled cells / slots), Opt.1-3 (Assumed to notify specific cells) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0161] • ChannelAccess-CPext-CAPC: Opt.1-1 (Assumed to notify all scheduled cells / slots), Opt.1-3 (Assumed to notify specific cells) However, this field may be excluded from DCI for multi-carrier and multi-slot scheduling.

[0162] • TRS availability indication (PowSav.): Opt.1-1 (Assumes notification for all scheduled cell / slot), Opt.1-3 (May assume that this field is assumed only for specific cells (cells with TRS-ResourceSetConfig configured)), or Opt.2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling. • PDCCH monitoring adaptation indication (PowSav.): Opt. 1-1 (notification and assumption for all scheduled cells / slots), Opt. 1-3 may apply (the field may be assumed only for specific cells (cells with PDCCHSkippingDurationList set)), or Opt. 2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling.

[0163] • Second TPC command for scheduled PUSCH (mTRP (Transmission Reception Point) PUSCH): Opt.1-1 (Assumed to be a notification to all scheduled cell / slot), Opt.1-2 (May be defined as a field to specify the index of combinations of 2nd TPC command settings for multiple scheduled cell / slots), Opt.1-3 (May be assumed to be this field only for specific cells (cells with mTRP set)), or Opt.2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling.

[0164] • Second SRS resource indicator (mTRP PUSCH): Opt. 1-1 (Assumed to be a notification for all scheduled cells / slots), Opt. 1-2 (May be defined as a field to specify the index of combinations of 2nd SRS resources for multiple scheduled cells / slots), Opt. 1-3 (May be assumed to be this field only for specific cells (cells for which mTRP is set)), or Opt. 2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling.

[0165] • Second Precoding information (mTRP PUSCH): Opt.1-1 (Assumed to be a notification for all scheduled cells / slots), Opt.1-2 (May be defined as a field to specify the index of combinations of 2nd precoding info for multiple scheduled cells / slots), Opt.1-3 (May be assumed to be this field only for specific cells (cells with mTRP set)), or Opt.2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling.

[0166] • Second PTRS-DMRS association (mTRP PUSCH): Opt.1-1 (Assumes notification to all scheduled cells / slots), Opt.1-2 (May be defined as a field to specify the index of combinations of 2nd PTRS-DMRS association settings for multiple scheduled cells / slots), Opt.1-3 (May be assumed to apply only to specific cells (cells with mTRP set)), or Opt.2 Depending on specific conditions (e.g., whether it is FR1 / FR2-1 / FR2-2), one of the above Opts may be switched. The field in question may not be assumed in the DCI for multi-carrier and multi-slot scheduling.

[0167] (4) Action and Effects According to the embodiments described above, even when a DCI for multi-carrier and multi-slot scheduling is applied, the appropriate options described above can be applied to each field of the DCI. Therefore, it is possible to establish a DCI design that can achieve a high level of balance between the efficiency of using a single DCI (DCI compression effect) and the flexibility of PDSCH / PUSCH scheduling for slots or CCs.

[0168] Therefore, the gNB100 and UE200 can utilize DCI that is even more suitable for use in combination with Single DCI Multi-carrier PDSCH / PUSCH scheduling and Single DCI Multi-slot PDSCH / PUSCH scheduling. In other words, they can leverage the benefits of multi-carrier and multi-slot scheduling while utilizing DCI that is more suitable for a wider range of applications and environments.

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

[0170] For example, in the embodiments described above, the terms single DCI multi-slot PDSCH / PUSCH scheduling, Single DCI Multi-carrier PDSCH / PUSCH scheduling, and Multi-carrier and multi-slot scheduling were used. However, these terms may be referred to by other names as long as they mean the function of scheduling PDSCH / PUSCH on multiple slots using one DCI, the function of scheduling PDSCH / PUSCH on multiple CCs using a single DCI (Single DCI Multi-carrier PDSCH / PUSCH scheduling), and a combination of both functions. Furthermore, as mentioned above, the channels are not limited to PDSCH / PUSCH, but may include control channels and / or other data channels.

[0171] Furthermore, in the above description, configure, activate, update, indicate, enable, specify, and select may be interpreted interchangeably. Similarly, link, associate, correspond, and map may be interpreted interchangeably, as may allocate, assign, monitor, and map.

[0172] Furthermore, "specific," "dedicated," "UE specific," and "UE individual" may be interpreted interchangeably. Similarly, "common," "shared," "group-common," "UE common," and "UE shared" may be interpreted interchangeably.

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

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

[0175] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 13 shows an example of the hardware configuration of the device. As shown in Figure 13, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0176] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0177] Each functional block of the device (see Figure 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0178] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0179] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0180] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line.

[0181] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.

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

[0183] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc.

[0184] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).

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

[0186] 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 different buses may be configured for each device.

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

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

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

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

[0191] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0192] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

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

[0194] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

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

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

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

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

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

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

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

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

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

[0204] A base station can house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0205] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

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

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

[0208] 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 appropriate term.

[0209] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

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

[0211] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

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

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

[0214] A slot may consist 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 also be a time unit based on neurology.

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

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

[0217] For example, one subframe may be called a Transmit Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

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

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

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

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

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

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

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

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

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

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

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

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

[0230] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

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

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

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

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

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

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

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

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

[0239] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

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

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

[0243] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0244] Information Services Section 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).

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

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

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

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

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

[0250] The present disclosure has been described in detail above. However, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and changed aspects without departing from the spirit and scope of the present disclosure defined by the description of the claims. Therefore, the description of the present disclosure is for the purpose of illustrative explanation, and does not have any restrictive meaning with respect to the present disclosure.

[0251] (Supplementary Note) The above disclosure may be expressed as follows.

[0252] A first feature is a terminal comprising: a receiving unit that receives single first specific downlink control information that schedules a channel transmitted via a plurality of slots, and single second specific downlink control information that schedules a channel transmitted via a plurality of carriers; and a control unit that controls transmission or reception of the channel based on at least one of the first specific downlink control information and the second specific downlink control information, wherein when the control unit performs scheduling based on both the first specific downlink control information and the second specific downlink control information, the control unit assumes that a single value is set for at least one field in the formats of the first specific downlink control information and the second specific downlink control information, and applies different configurations to at least any one of a cell, a slot, or the channel scheduled by the first specific downlink control information and the second specific downlink control information.

[0253] A second feature is that in the first feature, the control unit applies different configurations to a plurality of simultaneously scheduled channels based on a plurality of entries associated with a single index value notified by at least one of the first specific downlink control information and the second specific downlink control information.

[0254] A third feature is that in the first or second feature, the control unit applies the entry to a plurality of slots or a plurality of cells.

[0255] A fourth feature is that in any one of the first to third features, the control unit applies the entry for each cell or each cell group. [Description of Reference Numerals]

[0256] 10 Wireless communication system 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitting / receiving unit 220 Amplifier unit 230 Modem / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception unit 270 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication Port

Claims

1. A receiving unit that receives a single first specific downlink control information for scheduling channels transmitted by multiple slots, and a single second specific downlink control information for scheduling channels transmitted by multiple carriers, A control unit that controls the transmission or reception of the channel based on at least one of the first specific downlink control information and the second specific downlink control information, Equipped with, The control unit, When scheduling is performed based on both the first specific downlink control information and the second specific downlink control information, it is assumed that a single value is set for at least one of the fields in the format of the first specific downlink control information and the second specific downlink control information. A terminal that applies different settings to at least one of the cells, slots, or channels scheduled by the first specific downlink control information and the second specific downlink control information.

2. The terminal according to claim 1, wherein the control unit applies different settings to multiple simultaneously scheduled channels based on a plurality of entries associated with a single index value notified by at least one of the first specific downlink control information and the second specific downlink control information.

3. The terminal according to claim 2, wherein the control unit applies the entry to a plurality of slots or a plurality of cells.

4. The terminal according to claim 2, wherein the control unit applies the entry to each cell or cell group.

5. A transmission unit that transmits a single first specific downlink control information for scheduling channels transmitted by multiple slots, and a single second specific downlink control information for scheduling channels transmitted by multiple carriers, A control unit that performs the setting of the first specific downlink control information and the second specific downlink control information, Equipped with, When the control unit performs scheduling based on both the first specific downlink control information and the second specific downlink control information, it sets a single value for at least one of the fields in the format of the first specific downlink control information and the second specific downlink control information. A radio base station that instructs at least one of the cells, slots, or channels scheduled by the first specific downlink control information and the second specific downlink control information to have different settings.

6. The steps include receiving a single first specific downlink control information that schedules channels transmitted by multiple slots, and a single second specific downlink control information that schedules channels transmitted by multiple carriers, A step of controlling the transmission or reception of the channel based on at least one of the first specific downlink control information and the second specific downlink control information. Equipped with, In the aforementioned control step, When scheduling is performed based on both the first specific downlink control information and the second specific downlink control information, it is assumed that a single value is set for at least one of the fields in the format of the first specific downlink control information and the second specific downlink control information. A wireless communication method for applying different settings to at least one of the cells, slots, or channels scheduled by the first specific downlink control information and the second specific downlink control information.

Images