Terminal and communication method

Abstract

This terminal comprises: a reception unit that receives a parameter for radio resource control related to setting of coverage extension; and a control unit that applies the coverage extension to an uplink signal on the basis of the parameter. The control unit applies the coverage extension to an uplink signal scheduled for a plurality of carriers, on the basis of one piece of downlink control information.

Description

Terminal and communication method

[0001] The present disclosure relates to a terminal and a communication method.

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

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

[0004] In 3GPP, multi-carrier enhancement of downlink and uplink signals is being discussed (see, for example, Non-Patent Document 3). For example, scheduling of downlink and uplink signals of multiple cells using a single DCI is being discussed.

[0005] 3GPP TS 38.214 V17.7.0 (2023-09)3GPP TS 38.300 V17.6.0 (2023-09)”New WID on Multi-carrier enhancements”, RP-213577, 3GPP TSG RAN Meeting #94e, Electronic Meeting, Dec. 6 - 17, 20213GPP TR 38.822 V17.1.0 (2023-06)”Updated RAN1 UE features list for Rel-18 NR after RAN1#114bis”, R1-2310635, 3GPP TSG RAN WG1 #114bis, Xiamen China, October 9th - 13th, 2023

[0006] However, there has been insufficient research into the application of coverage extension to uplink signals that are scheduled on multiple carriers based on a single piece of downlink control information, and further research is needed.

[0007] One aspect of the present disclosure is to provide a terminal and a communication method that appropriately configure coverage extension for uplink signals scheduled on multiple carriers based on one piece of downlink control information.

[0008] A terminal according to one aspect of the present disclosure includes a receiving unit that receives radio resource control parameters related to coverage extension settings, and a control unit that applies the coverage extension to an uplink signal based on the parameters, and the control unit applies the coverage extension to an uplink signal that is scheduled on multiple carriers based on one downlink control information.

[0009] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment. FIG. 1 is a diagram illustrating an example of the configuration of a radio frame, a subframe, and a slot used in the wireless communication system. FIG. 2 is a diagram illustrating multi-carrier scheduling. FIG. 3 is a diagram illustrating self-carrier scheduling. FIG. 4 is a diagram illustrating cross-carrier scheduling. FIG. 5 is a diagram illustrating scheduling in DCI format 1_3. FIG. 6 is a diagram illustrating a reference cell. FIG. 7 is a diagram illustrating counting of PUSCH repetitions based on a physical slot. FIG. 8 is a diagram illustrating counting of PUSCH repetitions based on an available slot basis. FIG. 9 is a diagram illustrating TBoMS. FIG. 10 is a diagram illustrating time domain resource allocation for TBoMS. FIG. 11 is a diagram illustrating repetitions for TBoMS. FIG. 12 is a diagram illustrating DMRS bundling. FIG. 13 is a diagram illustrating a portion of a list of UE features related to NR coverage extension. FIG. 14 is a diagram illustrating a portion of a list of UE features related to Scheduling / HARQ operation. FIG. 15 is a diagram illustrating a portion of a list of UE features related to NR_L1enh_URLLC. FIG. 16 is a diagram illustrating a portion of a list of UE features related to multi-carrier scheduling (DCI format 0_3). FIG. 17 is a block diagram illustrating an example of the configuration of a base station according to an embodiment. FIG. 18 is a block diagram illustrating an example of the configuration of a terminal according to an embodiment. FIG. 19 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to the present embodiment. FIG. 20 is a diagram illustrating an example of the configuration of a vehicle.

[0010] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings.

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

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

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

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

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

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

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

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

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

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

[0021] For example, multi-cell PUSCH / PDSCH scheduling using a single DCI, which will be described in the following section <Multi-carrier scheduling>, has been discussed and several agreements have been reached.

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

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

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

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

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

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

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

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

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

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

[0032] <DCI Format 0_3 / 1_3> It has been agreed that the DCI format for multi-carrier scheduling of PUSCH is called DCI format 0_3. It has been agreed that the DCI format for multi-carrier scheduling of PDSCH is called DCI format 1_3. DCI formats 0_3 / 1_3 can be simultaneously scheduled for combinations of cells included in a set of cells to be scheduled (Set of cells). Hereinafter, Set of cells may be referred to as SoCs.

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

[0034] DCI formats 0_3 / 1_3 can be scheduled simultaneously for combinations of cells included in SoCs.

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

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

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

[0038] <Reference Cell> The cell that counts the DCI size, the number of PDCCH candidates (BDs), and the number of CCEs is called the reference cell. In multi-carrier scheduling, one reference cell is configured for each SoC. The reference cell is notified by higher layer signaling, such as RRC signaling.

[0039] Fig. 7 is a diagram illustrating a reference cell. For example, in Fig. 7, the reference cell for Set of cells 1 is set to CC#1. In this case, the DCI size / number of PDCCH candidates (BDs) / number of CCEs of the PDCCH (DCI for Set of cells 1) indicated by arrow A7a are counted in CC#1.

[0040] For example, in Fig. 7, the reference cell for Set of cells 2 is set to CC#5. In this case, the DCI size / number of PDCCH candidates (BDs) / number of CCEs of the PDCCH (DCI for Set of cells 2) indicated by arrow A7b are counted in CC#5.

[0041] <Coverage Extension> Rel-17 specifies several techniques for coverage extension of uplink signals. For example, available slot counting (available slot basis) for PUSCH repetition, TB processing over multi-slot (TBoMS), and Demodulation Reference Signal (DMRS) bundling are specified. Available slot basis, TBoMS, and DMRS bundling are explained below.

[0042] <Coverage Extension: Available Slot Basis> Figure 8 is a diagram explaining counting of PUSCH repetitions based on physical slots. The count for PUSCH repetitions in Rel-15 / 16 is based on physical slots. Therefore, as shown in Figure 8, when the number of PUSCH repetitions is 16, up to four actual PUSCH repetitions are configured for the TDD (Time Division Duplex) pattern "DDDDU."

[0043] To increase the actual PUSCH repetition, Rel-17 introduced the available slot basis (available slot counting).

[0044] 9 is a diagram illustrating counting of PUSCH repetitions on an available slot basis. On an available slot basis, PUSCH repetitions are determined based on the following two steps.

[0045] Step 1: The terminal determines available slots based on RRC configurations such as tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and ssb-PositionsInBurst and TDRA in DCI scheduling.

[0046] Step 2: The terminal determines whether to drop the PUSCH repetition according to a predetermined dropping rule, for example, the PUSCH dropping rule in Rel-15 / 16.

[0047] In the available slot basis, the number of repetitions is counted based on the number of available slots. Therefore, as shown in Fig. 9, when the number of PUSCH repetitions is 4, four actual PUSCH repetitions are set for the TDD pattern "DDDDU".

[0048] Coverage Extension: TBoMS TBoMS transmits one TB over multiple slots, where the TB size decision is performed based on PUSCH resource elements over N slots.

[0049] TBoMS can have the following advantages: Improved channel coding gain due to longer code sequences - Code block segmentation is not supported when TBoMS is enabled High power spectral density at low code rates - 1TB can be allocated to multiple slots in the time domain, reducing the number of Resource Blocks (RBs) required to transmit a particular TB

[0050] Fig. 10 is a diagram for explaining TBoMS, showing an example in which one TB is transmitted over three slots.

[0051] Figure 10 shows the relationship between the bits transmitted in each slot and the bit positions in the circular buffer. The circular buffer stores, for example, an encoded bit sequence corresponding to one TB. In the example of Figure 10, bit selection is performed as indicated by arrows A10a, A10b, and A10c, and one TB is transmitted over three slots (three PUSCHs).

[0052] The number of slots (N) allocated to one TB is indicated by numberOfSlotsTBoMS, which is notified by higher layer signaling such as RRC signaling.

[0053] Figure 11 is a diagram illustrating time domain resource allocation for TBoMS. Figure 11 shows an example where numberOfSlotsTBoMS=4. The same symbols are allocated to each slot (PUSCH).

[0054] In TBoMS, TBoMS with repetition is introduced to reduce the burden on the terminal since the terminal saves the position of the circular buffer. The number of slots allocated to single TBoMS(N) and repetition TBoMS(K) are indicated by numberOfSlotsTBoMS and numberOfRepetitions, respectively. numberOfSlotsTBoMS and numberOfRepetitions are notified by higher layer signaling such as RRC signaling.

[0055] The RV (Redundancy Version) determination for each repetition is the same as for Rel-15 / 16. The RV index cycles from [0, 2, 3, 1] in the PUSCH scheduled by DCI. The RV index also cycles from [0, 0, 0, 0], [0, 3, 0, 3], or [0, 2, 3, 1] according to the RRC parameter (repK-RV) of the configured grant PUSCH (CG-PUSCH).

[0056] Fig. 12 is a diagram for explaining the repetition of TBoMS, showing an example in which the number of slots of single TBoMS is 2, the number of repetitions is 3, and the RV sequence is [0, 2, 3, 1].

[0057] <Coverage Extension: DMRS Bundling> DMRS bundling improves channel estimation accuracy by bundling DMRSs of multiple PUSCHs / PUCCHs. For example, a base station estimates DMRSs of PUSCHs / PUCCHs across multiple slots to improve channel estimation accuracy. DMRS bundling may also be referred to as joint channel estimation.

[0058] 13 is a diagram illustrating DMRS bundling. To enable DMRS bundling across multiple slots at a base station, a terminal transmits DMRS on a PUSCH / PUCCH while maintaining power consistency and phase continuity within an actual time domain window (TDW). The actual TDW is determined based on a nominal TDW and an event.

[0059] An event disrupts power consistency and phase continuity. The UE terminates the actual TDW when an event occurs. Examples of events include frequency hopping, timing advance (TA) adjustment, DL slots in unpaired spectrum, and dropping (cancelling) PUSCH / PUCCH transmissions.

[0060] Events are classified into dynamic events and semi-static events. Dynamic events are events triggered by MAC CE or DCI (e.g., TA adjustment) except for frequency hopping and UL beam switching for multi-TRP operation. Semi-static events are frequency hopping, UL beam switching for multi-TRP operation, and events triggered by RRC parameters (e.g., DL slots configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated).

[0061] <UE Features> In 3GPP, UE features are listed (grouped) in a TR (Technical Report) (Non-Patent Document 4). A terminal reports, for example, a UE feature in an FG as a terminal capability.

[0062] Figure 14 shows a part of a list of UE features related to NR coverage extension. As shown in Figure 14, UE features related to NR coverage extension (30. NR_cov_enh) are grouped by feature group. An index is assigned to each feature group.

[0063] For example, FG30-1 specifies that the maximum number of repetitions is 32. FG30-2 specifies that the repetitions of PUSCH repetition Type A are on an available slot basis.

[0064] Note that PUSCH repetition Type A is a form in which a PUSCH allocated in a slot is transmitted in a repetitive manner. PUSCH repetition Type A can be considered as repetition at the slot level. PUSCH repetition Type A may also be referred to as repetition Type A.

[0065] The FG30-3 series, such as FG30-3 and FG30-3a, specify UE features related to TBoMS. The FG30-4 series, such as FG-4, 30-4a, 30-4c, 30-4e, 30-4g, and 30-4h, specify UE features related to DMRS bundling.

[0066] 15 is a diagram showing a part of a list of UE features related to scheduling / HARQ operation. As shown in FIG. 15, UE features related to scheduling / HARQ operation (5. Scheduling / HARQ operation) are grouped by feature group.

[0067] For example, FG5-14 specifies the repetition of a Type 1 configured PUSCH across multiple slots, FG5-16 specifies the repetition of a Type 2 configured PUSCH across multiple slots, and FG5-17 specifies the repetition of a PUSCH across multiple slots.

[0068] In addition, in the Type 1 configured PUSCH, activation and deactivation of the PUSCH depend on the RRC-configuration and do not depend on the DCI. In the Type 2 configured PUSCH, activation and deactivation of the PUSCH depend on the RRC-configuration and the DCI. The configured PUSCH may also be referred to as a configured grant PUSCH.

[0069] Figure 16 shows a partial list of UE features related to NR_L1enh_URLLC. As shown in Figure 16, UE features related to NR URLLC (11. NR_L1enh_URLLC) are grouped by feature group. For example, FG11-6 specifies PUSCH of repetition type A. URLLC stands for ultra-reliable and low latency communications.

[0070] Updates to UE features in Rel-18 are being discussed (Non-Patent Document 5). UE features in Rel-18 include UE features related to multi-carrier scheduling introduced in Rel-18.

[0071] Figure 17 shows a partial list of UE features related to multi-carrier scheduling (DCI formats 0-3). As shown in Figure 17, UE features related to multi-carrier enhancement (49.NR_MC_enh) are grouped by feature group.

[0072] For example, FG49-2 specifies multi-cell PUSCH scheduling using DCI format 0_3 for scheduling cells that have the same SCS between the scheduling cell and the cells in the set. For example, FG49-2b specifies multi-cell PUSCH scheduling using DCI format 0_3 for scheduling cells that are not included in the set of cells that have different SCS / carrier types between the scheduling cell and the cells in the set.

[0073] <Analysis> It is expected that coverage extensions defined in Rel-17, such as available slot basis, TBoMS, and DMRS bundling, will also be applied to PUSCH scheduled by DCI format 0_3 (multi-carrier scheduling of PUSCH), which will be newly introduced in Rel-18.

[0074] Therefore, when a terminal supports both the PUSCH coverage extension function defined in Rel-17 and the multi-carrier scheduling function defined in Rel-18, it is desirable for the terminal to report to the network whether it supports the coverage extension function only for PUSCHs scheduled by the existing DCI format or whether it also supports the coverage extension function for PUSCHs scheduled by DCI format 0_3.

[0075] For example, a case may be assumed in which a terminal supports both the PUSCH coverage extension function defined in Rel-17 and the multi-carrier scheduling function of Rel-18, but does not support the coverage extension function for PUSCHs scheduled by DCI format 0_3. In this case, the network may configure coverage extension for a terminal that does not support the coverage extension function for PUSCHs scheduled by DCI format 0_3. Therefore, it is desirable to report to the network whether the terminal supports the coverage extension function only for PUSCHs scheduled by an existing DCI format, or whether the terminal also supports the coverage extension function for PUSCHs scheduled by DCI format 0_3.

[0076] Therefore, reports regarding support for coverage extension for PUSCH scheduled by DCI formats 0-3 are reported independently (separately) from reports regarding support for coverage extension for PUSCH scheduled by existing DCI formats (Proposal 1).

[0077] In addition, the PUSCH coverage extension function defined in Rel-17 is applied to PUSCH scheduled by the existing DCI format.

[0078] Therefore, when a terminal supports both the PUSCH coverage extension function defined in Rel-17 and the multi-carrier scheduling function defined in Rel-18, it is desirable to clarify whether or not the coverage extension function is also configured for PUSCH scheduled by DCI format 0_3 when the coverage extension function is configured for PUSCH scheduled by an existing DCI format.

[0079] For example, in a terminal that supports both the PUSCH coverage extension function defined in Rel-17 and the multi-carrier scheduling function of Rel-18, the coverage extension function is configured for the PUSCH scheduled by an existing DCI format. In this case, if it is unclear whether coverage extension is configured for the PUSCH scheduled by DCI format 0_3, it is expected that the terminal will not be able to appropriately perform coverage extension for the PUSCH scheduled by DCI format 0_3.

[0080] Therefore, the coverage extension function for PUSCH scheduled by DCI formats 0-3 is configured independently (separately) or dependently (subordinately) from the coverage extension function setting for PUSCH scheduled by existing DCI formats (Proposal 2).

[0081] <Proposal 1> Proposal 1 relates to terminal capabilities when applying the Rel-17 coverage extension feature to a PUSCH scheduled by DCI format 0_3.

[0082] The following options 1 and 2 are proposed for terminal capabilities when applying the Rel-17 coverage extension feature to a PUSCH scheduled by DCI format 0_3.

[0083] <Proposal 1: Option 1> The terminal reports information (terminal capabilities) regarding application of the Rel-17 coverage extension feature to PUSCHs scheduled by DCI formats 0-3 by UE capability signaling, independently of application to PUSCHs scheduled by existing DCI formats.

[0084] In other words, a new terminal capability (terminal capability signaling) is defined to apply a coverage extension function to a PUSCH scheduled by multi-carrier scheduling of a single DCI. The new terminal capability may mean, for example, that the new terminal capability is different from the terminal capability related to applying a coverage extension function to a PUSCH scheduled by an existing DCI format. The existing DCI format may be a DCI format defined before Rel-17. For example, the existing DCI format may be DCI format 0_0 / 0_1 / 0_2.

[0085] Regarding terminal capability signaling for option 1, the following options 1-1 to 1-11 and variations are proposed.

[0086] <Proposal 1: Option 1: Option 1-1> For a PUSCH scheduled by DCI format 0_3, terminal capability signaling is specified to report the maximum repetition number of PUSCH repetition Type A. For example, for a PUSCH scheduled by DCI format 0_3, the terminal reports the maximum repetition number of PUSCH repetition Type A as terminal capability.

[0087] The maximum number of repetitions may be 32 or a value less than 32.

[0088] The maximum repetition number may be applied only to the repetition of a dynamic grant PUSCH (DG PUSCH). The terminal may report, as terminal capability, that the PUSCH to which the maximum repetition number is applied is a CG PUSCH. The DG PUSCH may be considered as a PUSCH that is dynamically scheduled by physical layer signaling such as DCI.

[0089] <Proposal 1: Option 1: Option 1-2> Terminal capability signaling is specified to report that transmission occasion counting on an available slot basis is applicable to the repetition of a PUSCH scheduled by DCI format 0_3. For example, the terminal reports, as terminal capability, that it supports transmission occasion counting on an available slot basis for the repetition of a PUSCH scheduled by DCI format 0_3.

[0090] <Proposal 1: Option 1: Option 1-3> Terminal capability signaling is specified to report that TBoMS is applicable to the PUSCH scheduled by DCI format 0_3. For example, the terminal reports that it supports TBoMS as its terminal capability for the PUSCH scheduled by DCI format 0_3.

[0091] <Proposal 1: Option 1: Option 1-4> A terminal capability signaling is specified to report that TBoMS repetition can be applied to a PUSCH scheduled by DCI format 0_3. For example, a terminal reports as its terminal capability that it supports TBoMS repetition for a PUSCH scheduled by DCI format 0_3.

[0092] The repetition of TBoMS may be applied only to the repetition of DG PUSCH. For example, the terminal may report, as terminal capability, that the repetition of TBoMS is the repetition of DG PUSCH for PUSCH scheduled by DCI format 0_3.

[0093] <Proposal 1: Option 1: Option 1-5> For a PUSCH scheduled by DCI format 0_3, terminal capability signaling is specified to report the maximum duration of power consistency and phase continuity in DMRS bundling. For example, for a PUSCH scheduled by DCI format 0_3, the terminal reports the maximum duration of power consistency and phase continuity in DMRS bundling as terminal capability.

[0094] <Proposal 1: Option 1: Option 1-6> Terminal capability signaling is specified to report that DMRS bundling is applicable to repetition Type A of PUSCH scheduled by DCI format 0_3. For example, the terminal reports, as terminal capability, that DMRS bundling is applicable to repetition Type A of PUSCH scheduled by DCI format 0_3.

[0095] <Proposal 1: Option 1: Option 1-7> When TBoMS is applied to a PUSCH scheduled by DCI format 0_3, terminal capability signaling is specified to report that DMRS bundling is applicable. For example, when TBoMS is applied to a PUSCH scheduled by DCI format 0_3, the terminal reports that DMRS bundling is applicable as terminal capability.

[0096] <Proposal 1: Option 1: Option 1-8> When inter-slot bundling is applied to a PUSCH scheduled by DCI format 0_3, terminal capability signaling is specified to report that inter-slot FH is applicable. For example, when inter-slot bundling is applied to a PUSCH scheduled by DCI format 0_3, the terminal reports that inter-slot FH is applicable as terminal capability.

[0097] <Proposal 1: Option 1: Option 1-9> Terminal capability signaling is defined to report that a terminal supports resumption of DMRS bundling for a PUSCH scheduled by DCI format 0_3 after an event that breaks power consistency and / or phase continuity is triggered by DCI or MAC CE. For example, the terminal reports as terminal capability that a terminal supports resumption of DMRS bundling for a PUSCH scheduled by DCI format 0_3 after an event that breaks power consistency and / or phase continuity is triggered by DCI or MAC CE.

[0098] <Proposal 1: Option 1: Option 1-10> Terminal capability signaling is specified to report support of DMRS bundling for non-back-to-back transmission in non-consecutive slots of PUSCH scheduled by DCI format 0_3. For example, the terminal reports, as terminal capability, support of DMRS bundling for non-back-to-back transmission in non-consecutive slots of PUSCH scheduled by DCI format 0_3.

[0099] <Proposal 1: Option 1: Variation> The prerequisite feature of the terminal capability may be at least one of FG49-2 / 49-2b / 5-14 / 5-16 / 5-17 / 11-6.

[0100] The reporting granularity of terminal capabilities may be per carrier type (FR1 / FR2-1 / FR2-2, licensed / unlicensed, TDD / FDD), per band, per BC (Band Combination), per terminal, per FS (Feature Set), or per FSPC (Feature Set Per Component-carrier).

[0101] The terminal capabilities may be specified separately for the cases where the number of cells scheduled by DCI format 0_3 is one and two or more.

[0102] The reporting of terminal capabilities related to coverage extension of a PUSCH scheduled by DCI format 0_3 may be applied to (or used as) the reporting of terminal capabilities related to coverage extension of a PUSCH scheduled by an existing DCI format. For example, the reporting of terminal capabilities described in the above Option 1-1 to Option 1-10 may also serve as the reporting of terminal capabilities related to coverage extension of a PUSCH scheduled by an existing DCI format. In this case, the reporting of terminal capabilities related to coverage extension of a PUSCH scheduled by an existing DCI format may be omitted in favor of the reporting of terminal capabilities related to coverage extension of a PUSCH scheduled by DCI format 0_3.

[0103] <Proposal 1: Option 2> A terminal that reports support for coverage extension and multi-carrier scheduling as its terminal capabilities can support the coverage extension function for PUSCH scheduled by DCI format 0_3. For example, a terminal that reports FG30-x (x is an alphanumeric character such as 3 or 3a) and FG49-2 / 2b can support coverage extension functions such as available slot basis, TBoMS, and DMRS bundling corresponding to the reported FG30-x for PUSCH scheduled by DCI format 0_3. Note that "can support" may be read as "support."

[0104] For example, a terminal reporting FG30-1 and FG49-2 / 2b can support a maximum repetition number of 32 for PUSCH repetition Type A scheduled by DCI format 0_3.

[0105] For example, a terminal reporting FG30-2 and FG49-2 / 2b can support transmission occasion counting on an available slot basis for PUSCH repetition Type A scheduled by DCI format 0_3.

[0106] For example, a terminal reporting FG30-3 / 3a and FG49-2 / 2b can support TBoMS for a PUSCH scheduled by DCI format 0_3.

[0107] For example, a terminal reporting FG30-4 / 4a / 4c / 4e / 4g / 4h and FG49-2 / 2b can support DM-RS bundling for PUSCH scheduled by DCI format 0_3.

[0108] <Proposal 1: Summary> A terminal determines whether to report support for coverage extension for a PUSCH scheduled by DCI format 0_3. This operation allows, for example, the network to configure coverage extension for a multi-carrier scheduled PUSCH for a terminal that has the PUSCH coverage extension feature specified in Rel-17 and the multi-carrier scheduling capability of Rel-18 and supports coverage extension for a multi-carrier scheduled PUSCH. For example, the network does not need to configure coverage extension for a multi-carrier scheduled PUSCH for a terminal that has the PUSCH coverage extension feature specified in Rel-17 and the multi-carrier scheduling capability of Rel-18 but does not support coverage extension for a multi-carrier scheduled PUSCH.

[0109] <Proposal 2> Proposal 2 relates to RRC signaling when applying the coverage extension feature of Rel-17 to a PUSCH scheduled by DCI format 0_3.

[0110] The following options 1 and 2 are proposed for RRC signaling when applying the Rel-17 coverage extension feature to a PUSCH scheduled by DCI format 0_3.

[0111] <Proposal 2: Option 1> Regarding the coverage extension feature of Rel-17, new RRC parameters, different from the RRC parameters applied to PUSCHs scheduled by existing DCI formats, will be specified for PUSCHs scheduled by DCI formats 0-3.

[0112] In other words, new RRC parameters are defined for applying the coverage extension function to the PUSCH scheduled by multi-carrier scheduling of a single DCI. The new RRC parameters may mean, for example, that the RRC parameters are different from the RRC parameters for applying the coverage extension function to the PUSCH scheduled by an existing DCI format. The RRC parameters may be simply referred to as RRC.

[0113] Regarding the RRC parameters of Option 1, the following Option 1-1 to Option 1-3 and variations are proposed.

[0114] <Proposal 2: Option 1: Option 1-1> For PUSCH repetition Type A, at least one of the following RRC parameters is specified for DCI format 0_3: "numberOfRepetitionsDCI-0-3" indicating the number of PUSCH repetitions; "pusch-AggregationFactorDCI-0-3" indicating the number of data repetitions; "AvailableSlotCountingDCI-0-3" enabling available slot counting on an available slot basis.

[0115] For example, when numberOfRepetitionsDCI-0-3 is configured (notified), the terminal applies the number of repetitions indicated by numberOfRepetitionsDCI-0-3 to the repetition of the PUSCH scheduled according to DCI format 0_3. For example, when pusch-AggregationFactorDCI-0-3 is configured, the terminal applies the number of repetitions indicated by pusch-AggregationFactorDCI-0-3 to the repetition of data scheduled according to DCI format 0_3. For example, when AvailableSlotCountingDCI-0-3 is configured, the terminal performs available slot counting on an available slot basis in slots of the PUSCH scheduled according to DCI format 0_3.

[0116] <Proposal 2: Option 1: Option 1-2> For TBoMS, the following RRC parameters are specified for DCI format 0_3: "numberOfSlotsTBoMSDCI-0-3" indicating the number of slots to which TBoMS is applied For example, when numberOfSlotsTBoMSDCI-0-3 is configured, the terminal applies TBoMS to the PUSCH scheduled by DCI format 0_3 for the number of slots indicated by numberOfSlotsTBoMSDCI-0-3.

[0117] <Proposal 2: Option 1: Option 1-3> For DMRS bundling, at least one of the following RRC parameters is specified for DCI format 0-3: "pusch-DMRSBundlingDCI-0-3" to enable DMRS bundling and time domain window for PUSCH; "pusch-TimeDomainWindowLengthDCI-0-3" to indicate the length of the nominal time domain window.

[0118] For example, when pusch-DMRSBundlingDCI-0-3 is configured, the terminal performs DMRS bundling based on the time domain window for the PUSCH scheduled in DCI format 0_3. For example, when pusch-TimeDomainWindowLengthDCI-0-3 is configured, the terminal sets the nominal time domain window indicated by pusch-TimeDomainWindowLengthDCI-0-3 for the PUSCH scheduled in DCI format 0_3.

[0119] <Proposal 2: Option 1: Modifications> The following modifications 1 to 3 are proposed for the above options. "The above parameters" described below refer to at least one of the RRC parameters described in <Proposal 2: Option 1: Option 1-1> to <Proposal 2: Option 1: Option 1-3>.

[0120] <Proposal 2: Option 1: Variation 1> Coverage extension functions such as available slot basis, TBoMS, and DMRS bundling may be applied only to cells included in the SoCs for which the above RRC parameters are set.

[0121] For example, among the four CCs #1 / 2 / 3 / 4 included in the SoCs, the above RRC parameters are configured in CC #1. In this case, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are applied to the PUSCH of DCI format 0_3 of CC #1.

[0122] <Proposal 2: Option 1: Variant 2> Coverage extension features such as available slot basis, TBoMS, and DMRS bundling may be applied only if the above parameters are set for all cells simultaneously scheduled by DCI format 0_3.

[0123] For example, of the four CCs #1 / 2 / 3 / 4 included in the SoCs, a PUSCH of DCI format 0_3 is scheduled in three CCs #1 / 2 / 3. If the above RRC parameters are configured in all three CCs #1 / 2 / 3, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are applied to the PUSCH of DCI format 0_3 of the three CCs #1 / 2 / 3.

[0124] In contrast, if the above RRC parameters are set in, for example, two CC#1 / 2 out of the three CC#1 / 2 / 3 in which a PUSCH of DCI format 0_3 is scheduled, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are not applied to the PUSCH of DCI format 0_3 of the two CC#1 / 2.

[0125] <Proposal 2: Option 1: Variation 3> It may be assumed that the above parameters are set for all cells included in a scheduled cell set (SoC). In this case, the above parameters may be set individually for each cell. Alternatively, when the above parameters are set for a cell / scheduling cell included in the SoC, the parameters may be applied to all cells included in the SoC.

[0126] For example, if the SoCs includes four CCs #1 / 2 / 3 / 4, the terminal assumes that the above parameters are individually set in each of the four CCs #1 / 2 / 3 / 4. Alternatively, for example, if the above parameters are set in CC #1 of the four CCs #1 / 2 / 3 / 4 included in the SoCs, the terminal assumes that the above parameters are also set in the remaining CCs #2 / 3 / 4.

[0127] <Proposal 2: Option 2> For the coverage extension feature of Rel-17, the RRC parameters that apply to PUSCHs scheduled by existing DCI formats will also be applied to PUSCHs scheduled by DCI formats 0-3.

[0128] In other words, existing RRC parameters are used to apply the coverage extension feature to the PUSCH scheduled by multi-carrier scheduling of a single DCI, such as the RRC parameters of the Rel-17 coverage extension feature applied to the PUSCH scheduled by the existing DCI format.

[0129] Regarding the RRC parameters of Option 2, the following Option 2-1 to Option 2-3 and variations are proposed.

[0130] <Proposal 2: Option 2: Option 2-1> For PUSCH repetition Type A, if at least one of the following RRC parameters is configured for an existing DCI format, that RRC parameter will be applied to the PUSCH scheduled by DCI format 0_3: - "numberOfRepetitions" indicating the number of repetitions of the PUSCH - "pusch-AggregationFactor" indicating the number of repetitions of data - "AvailableSlotCounting" enabling available slot counting on an available slot basis

[0131] For example, when numberOfRepetitions is configured for a PUSCH of an existing DCI format, the terminal applies the number of repetitions indicated by numberOfRepetitions to the repetitions of a PUSCH scheduled by DCI format 0_3. For example, when pusch-AggregationFactor is configured for data of an existing DCI format, the terminal applies the number of repetitions indicated by pusch-AggregationFactor to the repetitions of data scheduled by DCI format 0_3. For example, when AvailableSlotCounting is configured for a slot of a PUSCH of an existing DCI format, the terminal performs available slot counting on an available slot basis in the slot of a PUSCH scheduled by DCI format 0_3.

[0132] <Proposal 2: Option 2: Option 2-2> When the following RRC parameters for TBoMS are configured for an existing DCI format, the RRC parameters are applied to the PUSCH scheduled by DCI format 0_3. "numberOfSlotsTBoMS" indicates the number of slots to which TBoMS is applied.

[0133] For example, if numberOfSlotsTBoMS is configured for an existing DCI format, the terminal performs TBoMS for the number of slots indicated by numberOfSlotsTBoMS for a PUSCH scheduled by DCI format 0_3.

[0134] <Proposal 2: Option 2: Option 2-3> If at least one of the following RRC parameters for DMRS bundling is configured for an existing DCI format, that RRC parameter applies to the PUSCH scheduled by DCI formats 0-3: "pusch-DMRSBundling" enables DMRS bundling and the time domain window for the PUSCH; "pusch-TimeDomainWindowLength" indicates the length of the nominal time domain window.

[0135] For example, when enable pusch-DMRSBundling is configured for an existing DCI format, the terminal performs DMRS bundling based on the time domain window for the PUSCH scheduled by DCI format 0_3. For example, when pusch-TimeDomainWindowLength is configured for an existing DCI format, the terminal sets the nominal time domain window indicated by pusch-TimeDomainWindowLength for the PUSCH scheduled by DCI format 0_3.

[0136] <Proposal 2: Option 2: Modifications> The following modifications 1 to 3 are proposed for the above options. "The above parameters" described below refer to at least one of the RRC parameters described in <Proposal 2: Option 2: Option 2-1> to <Proposal 2: Option 2: Option 2-3>.

[0137] <Proposal 2: Option 2: Variation 1> Coverage extension functions such as available slot basis, TBoMS, and DMRS bundling may be applied only to cells included in the SoCs for which the above RRC parameters are set.

[0138] For example, among the four CCs #1 / 2 / 3 / 4 included in the SoCs, the above RRC parameters are configured in CC #1. In this case, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are applied to the PUSCH of DCI format 0_3 of CC #1.

[0139] <Proposal 2: Option 2: Variant 2> Coverage extension features such as available slot basis, TBoMS, and DMRS bundling may be applied only if the above parameters are set for all cells simultaneously scheduled by DCI format 0_3.

[0140] For example, of the four CCs #1 / 2 / 3 / 4 included in the SoCs, a PUSCH of DCI format 0_3 is scheduled in three CCs #1 / 2 / 3. If the above RRC parameters are configured in all three CCs #1 / 2 / 3, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are applied to the PUSCH of DCI format 0_3 of the three CCs #1 / 2 / 3.

[0141] In contrast, if the above RRC parameters are set in, for example, two CC#1 / 2 out of the three CC#1 / 2 / 3 in which a PUSCH of DCI format 0_3 is scheduled, coverage extension functions such as available slot basis, TBoMS, and DMRS bundling are not applied to the PUSCH of DCI format 0_3 of the two CC#1 / 2.

[0142] <Proposal 2: Option 2: Variation 3> It may be assumed that the above parameters are set for all cells included in a scheduled cell set (SoC). In this case, the above parameters may be set individually for each cell. Alternatively, when the above parameters are set for a cell / scheduling cell included in the SoC, the parameters may be applied to all cells included in the SoC.

[0143] For example, if the SoCs includes four CCs #1 / 2 / 3 / 4, the terminal assumes that the above parameters are individually set in each of the four CCs #1 / 2 / 3 / 4. Alternatively, for example, if the above parameters are set in CC #1 of the four CCs #1 / 2 / 3 / 4 included in the SoCs, the terminal assumes that the above parameters are also set in the remaining CCs #2 / 3 / 4.

[0144] <Proposal 2: Option 2: Variation 4> For the available slot basis, TBoMS, and DMRS bundling enable, new RRC parameters are specified for DCI formats 0-3, and for other RRC parameters, the same parameters as in existing DCI formats may be applied.

[0145] <Proposal 2: Summary> The terminal applies coverage extension to the PUSCH scheduled by DCI format 0_3 based on the RRC parameters related to coverage extension in Rel-17. This operation enables the terminal to appropriately apply coverage extension to the PUSCH scheduled by DCI format 0_3.

[0146] Furthermore, the terminal applies coverage extension to the PUSCH scheduled in accordance with DCI format 0_3 based on existing RRC parameters related to coverage extension in Rel-17. This operation enables the terminal to appropriately apply coverage extension to the PUSCH scheduled in accordance with DCI format 0_3.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0168] Here, the transmitter 202 may transmit uplink signals scheduled on multiple carriers based on one downlink control information. The downlink control information may be in DCI format 0-3, and the transmitter 202 may transmit uplink signals scheduled by multi-carrier scheduling using a single DCI. The uplink signals may be PUSCH.

[0169] The control unit 203 may determine whether to report support for coverage extension for uplink signals scheduled by multi-carrier scheduling with single DCI. For example, the control unit 203 may determine whether to report the terminal capabilities described in Proposal 1.

[0170] The control unit 203 may determine a report regarding support for at least one of available slot basis, TBoMS, and DMRS bundling for an uplink signal scheduled by multi-carrier scheduling with single DCI.

[0171] The control unit 203 may determine whether to report support for coverage extension defined in a release earlier than the release in which the downlink control information is defined. The release in which the downlink control information is defined may be Rel-18, and the release in which the coverage extension is defined may be Rel-17.

[0172] The control unit 203 may report support for the function of multi-carrier scheduling using single DCI and the function of coverage extension, and may perform coverage extension processing on uplink signals using multi-carrier scheduling using single DCI.

[0173] Here, the receiver 201 may receive radio resource control parameters related to the configuration of coverage extension. For example, the receiver 201 may receive the RRC parameters described in Options 1 and 2 of Proposal 2.

[0174] The control unit 203 may apply coverage extension to the uplink signal based on the received parameters. The control unit 203 may apply coverage extension to the uplink signal scheduled to multiple carriers based on one piece of downlink control information.

[0175] The control unit 203 may apply coverage extension to an uplink signal scheduled on multiple carriers based on newly defined radio resource control parameters related to the configuration of coverage extension. For example, the control unit 203 may apply coverage extension to a PUSCH scheduled on multiple carriers using a single DCI based on the RRC parameters described in Option 1 of Proposal 2.

[0176] The control unit 203 may apply coverage extension to an uplink signal scheduled on multiple carriers based on existing radio resource control parameters related to the configuration of coverage extension. For example, the control unit 203 may apply coverage extension to a PUSCH scheduled on multiple carriers using a single DCI based on the RRC parameters described in Option 2 of Proposal 2.

[0177] The control unit 203 may apply at least one of available slot basis, TBoMS, and DMRS bundling to uplink signals scheduled on multiple carriers.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A terminal comprising: a receiving unit that receives radio resource control parameters related to coverage extension settings; and a control unit that applies the coverage extension to an uplink signal based on the parameters, wherein the control unit applies the coverage extension to an uplink signal scheduled on multiple carriers based on one downlink control information.

2. The terminal according to claim 1, wherein the control unit applies the coverage extension to uplink signals scheduled on the multiple carriers based on newly defined radio resource control parameters related to the setting of the coverage extension.

3. The terminal according to claim 1, wherein the control unit applies the coverage extension to an uplink signal scheduled on the multiple carriers based on existing radio resource control parameters related to the setting of the coverage extension.

4. The terminal according to claim 1, wherein the control unit applies at least one of available slot basis, TB processing over multi-slot (TBoMS), and Demodulation Reference Signal (DMRS) bundling to uplink signals scheduled on the multiple carriers.

5. A communication method in which a terminal receives radio resource control parameters related to coverage extension settings, applies the coverage extension to an uplink signal based on the parameters, and applies the coverage extension to uplink signals scheduled on multiple carriers based on one downlink control information.

Images