Terminal, base station, and communication method

Abstract

This terminal is provided with: a reception unit that receives control information; and a control unit that controls the transmission operation of an uplink signal on the basis of the control information without needing to anticipate that the control information includes both first information for setting the transmission operation of a plurality of uplink signals in one period and second information indicating the number of repetitions of two or more repetitive transmissions.

Description

Terminal, base station, and communication method

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

[0002] Long Term Evolution (LTE) has been specified for Universal Mobile Telecommunication System (UMTS) networks to achieve higher data rates and lower latency. Furthermore, successor systems to LTE are also being considered to achieve even greater bandwidth and speed than LTE. Examples of successor systems to LTE include LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), and New Radio (NR).

[0003] In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while reducing wireless section latency to 1 ms or less (for example, Non-Patent Document 1).

[0004] In NR, Release 16 specifies the configuration of a Configured Grant Physical Uplink Shared Channel (CG PUSCH) (for example, see Non-Patent Document 2).

[0005] Release 17 examines Extended Reality (XR), including virtual reality (VR) and mixed reality (MX), and examines XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. The target requirements for XR include capacity, latency, mobility, and power saving.

[0006] 3GPP TS38.213 V16.3.0 (2020-09)3GPP TS38.331 V16.2.0 (2020-09)

[0007] There is room for consideration regarding the setting of multiple upstream signal transmission opportunities in high-capacity communications such as XR.

[0008] One aspect of the present disclosure is to provide a terminal, a base station, and a communication method that appropriately set transmission opportunities for multiple uplink signals.

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives control information, and a control unit that controls the transmission operation of an uplink signal based on the control information without anticipating that the control information includes both first information that sets the transmission operation of multiple uplink signals in one period and second information that indicates a number of repetitions of repeated transmission that is two or more.

[0010] 1 is a diagram illustrating an example of a wireless communication system according to an embodiment of the present disclosure. FIG. 1 is a diagram illustrating an example of FR used in the wireless communication system. FIG. 2 is a diagram illustrating an example of the configuration of a radio frame (system frame), subframes, and slots used in the wireless communication system 10. FIG. 3 is a diagram illustrating an example of a description of the current specifications. FIG. 4 is a diagram illustrating an example of TDRA. FIG. 5 is a diagram illustrating an example of a description of the current specifications regarding multi-PUSCH CG. FIG. 6 is a diagram illustrating a first example of TP for Example 2 of Option 2 of Proposal 1. FIG. 7 is a diagram illustrating a second example of TP for Example 2 of Option 2 of Proposal 1. FIG. 8 is a diagram illustrating an example of TP for Example 1 of Option 1 of Proposal 2. FIG. 9 is a diagram illustrating an example of TP for Example 2 of Option 1 of Proposal 2. FIG. 10 is a diagram illustrating an example of TP for Example 3 of Option 2 of Proposal 2. FIG. 11 is a block diagram illustrating an example of the configuration of a base station. FIG. 12 is a block diagram illustrating an example of the configuration of a terminal. FIG. 13 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to the present embodiment. FIG. 14 is a diagram illustrating an example of the configuration of a vehicle.

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

[0012] In the operation of the wireless communication system according to the embodiment of the present disclosure, existing technologies are used as appropriate. However, the existing technologies are, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0013] In addition, in the embodiments of the present disclosure described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE or NR are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. Furthermore, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even signals used in NR are not necessarily designated as "NR-".

[0014] Furthermore, in the embodiments of the present disclosure, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0015] Furthermore, in the embodiments of the present disclosure, "configuring" radio parameters and the like may mean that predetermined values ​​are pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0016] 1 is a diagram illustrating an example of a wireless communication system 10 according to an embodiment of the present disclosure. The wireless communication system 10 is a wireless communication system conforming to 5G NR, and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, also referred to as UE (User Equipment) 200).

[0017] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0018] The NG-RAN 20 includes a base station 100A (hereinafter also referred to as gNB 100A) and a base station 100B (hereinafter also referred to as gNB 100B). When there is no need to distinguish between the gNB 100A, the gNB 100B, etc., they are collectively referred to as gNB or base station 100. Furthermore, the number of gNBs and UEs is not limited to the example shown in FIG. 1.

[0019] The NG-RAN 20 actually includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). The NG-RAN 20 and 5GC may simply be referred to as "networks." In the following, the term "gNB" may be replaced with "network (NW)."

[0020] As an example, the gNB 100A and the gNB 100B are base stations conforming to 5G, and perform 5G wireless communication with the UE 200. The gNB 100A, the gNB 100B, and the UE 200 may support MIMO (Multiple-Input Multiple-Output), which generates a more directional beam BM by controlling radio signals transmitted from multiple antenna elements, carrier aggregation (CA), which uses a bundle of multiple component carriers (CC), and dual connectivity (DC), which performs communication between the UE and each of two NG-RAN nodes.

[0021] The wireless communication system 10 may also support multiple frequency ranges (FR). Fig. 2 is a diagram showing an example of FRs used in the wireless communication system 10. As shown in Fig. 2, the wireless communication system 10 may support FR1 and FR2. The frequency bands of each FR are, for example, as follows: FR1: 410 MHz to 7.125 GHz FR2: 24.25 GHz to 52.6 GHz

[0022] FR1 may use a sub-carrier spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and 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 a bandwidth (BW) of 50 to 400 MHz.

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

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

[0025] 3 is a diagram showing an example of the configuration of a radio frame (system frame), subframe, and slot used in the radio communication system 10. As shown in FIG. 3, one slot is composed of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). However, the SCS is not limited to the interval (frequency) shown in FIG. 3. For example, 480 kHz, 960 kHz, etc. may be used as the SCS.

[0026] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, it may be 28 or 56 symbols, etc.) Furthermore, the number of slots per subframe may differ depending on the SCS.

[0027] 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0028] The gNB100 transmits control information, setting information, etc. to the UE200 as a downlink (DL) signal.

[0029] Furthermore, for example, gNB100 receives control information, data signals, information regarding the processing capabilities of UE200 (terminal capabilities (information); for example, UE capability), etc. from UE200 as uplink (UL) signals.

[0030] Channels used for transmitting DL signals include, for example, data channels and control channels. For example, the data channel may include a physical downlink shared channel (PDSCH), and the control channel may include a physical downlink control channel (PDCCH). For example, the gNB 100 transmits control information to the UE 200 using the PDCCH, and transmits DL data signals using the PDSCH. Note that the PDSCH is an example of a downlink shared channel, and the PDCCH is an example of a downlink control channel. Note that the PDCCH may be interpreted as downlink control information (DCI), control information, etc. transmitted in the PDCCH.

[0031] Furthermore, for example, information (for example, parameters) set by higher layer signaling such as RRC signaling may be considered as an example of control information included in a DL signal.

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

[0033] The UE 200 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, or an M2M (Machine-to-Machine) communication module.

[0034] UE200 receives control signals or data signals from gNB100 in DL and transmits control signals or data signals to gNB100 in UL, thereby utilizing various communication services provided by wireless communication system 10. UE200 also receives various reference signals transmitted from gNB100 and performs measurement of propagation path quality based on the reception results of the reference signals.

[0035] For example, UE200 receives control information, configuration information, etc. from gNB100 as a DL signal.

[0036] Also, for example, UE200 transmits control information, data signals, terminal capability information of UE200, etc. to gNB100 as UL signals.

[0037] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channel may include a Physical Uplink Shared Channel (PUSCH), and the control channel may include a Physical Uplink Control Channel (PUCCH). For example, the UE 200 transmits control information using the PUCCH and transmits UL data signals using the PUSCH. Note that the PUSCH is an example of an uplink shared channel, and the PUCCH is an example of an uplink control channel. Note that the PUSCH or the PUCCH may be interpreted as uplink control information (UCI), control information, etc. transmitted in the PUSCH or the PUCCH.

[0038] The reference signal included in the UL signal may include, for example, at least one of a DMRS, a PTRS, a CSI-RS, an SRSRS, and a PRS for location information. For example, the reference signal such as the DMRS or the PTRS is used for demodulating the UL data signal and is transmitted using the PUSCH.

[0039] It should be noted that signals transmitted using PUSCH are not limited to data signals. Signals transmitted using PUSCH may include signals other than data signals (for example, control signals, reference signals, etc.). Hereinafter, transmitting a signal using PUSCH may be referred to as transmitting PUSCH or PUSCH transmission. Also, an opportunity to transmit PUSCH may be referred to as a PUSCH transmission opportunity or simply as a transmission opportunity. Also, as with PUSCH, some of the descriptions of channels other than the above-mentioned PUSCH may be omitted as appropriate.

[0040] In addition, the PUSCH may include a DG (dynamic grant) PUSCH and a CG PUSCH. The DG PUSCH is a PUSCH scheduled by DCI, and the CG (configured grant) PUSCH may correspond to a PUSCH configured by a configured grant. Next, the CG PUSCH will be described.

[0041] <CG PUSCH> As described above, in NR, the configuration of the CG PUSCH is specified in Rel-16 (for example, Non-Patent Document 2). The CG PUSCH includes Type 1 CG PUSCH and Type 2 CG PUSCH.

[0042] Type 1 CG PUSCH The transmission parameters of the Type 1 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". Activation and deactivation of the Type 1 CG PUSCH depend on the RRC-configuration and are not dependent on Downlink Control Information (DCI). Note that activation may also be referred to as activation.

[0043] Type 2 CG PUSCH The transmission parameters of the Type 2 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "activation DCI". Activation and deactivation of the Type 2 CG PUSCH depend on the RRC-configuration and DCI. One DCI can activate one CG PUSCH and deactivate multiple CG PUSCHs. Note that the activation DCI may also be referred to as an activation DCI.

[0044] <CG PUSCH configurations> The configuredGrantConfig parameter is used to configure uplink transmission without a dynamic grant. For example, the actual uplink grant is configured via RRC in the above-mentioned Type 1 case. Alternatively, the actual uplink grant may be provided via PDCCH (e.g., DCI) in the above-mentioned Type 2 case.

[0045] <Validation of Activated DCI> In Rel-17, if the TDRA (time domain resource assignment or allocation) field of the DCI format indicates a row including a single SLIV (Start and length Indicator Value), the terminal validates the configured UL grant Type 2 PDCCH for scheduling activation or scheduling release (see, for example, Section 10.2 of 3GPP TS38.213 V17.3.0). In other words, if the DCI indicates multiple SLIVs via the TDRA field, the terminal cannot validate the activated DCI. Note that the SLIV defines the start symbol and the number of consecutive symbols.

[0046] <CG Enhancements in Rel-18 XR> Enhancements related to power saving, enhancements related to capacity, and enhancements to XR awareness are being considered as items for consideration in Rel-18.

[0047] The following capacity-related enhancements are being considered: Multiple CG PUSCH transmission occasions in a single CG PUSCH configuration period Dynamic indication of unused CG PUSCH opportunities by the UE based on UCI BSR enhancements including at least a new BS table Reporting of delays for buffered data in the uplink Providing XR traffic assistance information (e.g. periodicity) for DL ​​and UL Discarding of PDU sets operations

[0048] When multiple CG PUSCHs are configured, the UE may configure multiple CG PUSCH transmission opportunities during one CG PUSCH configuration period.

[0049] Note that "unused" may include "unused." A CG PUSCH transmission opportunity may be referred to as a CG PUSCH opportunity. A CG PUSCH configuration period may be referred to as a CG PUSCH period or a CG period. The period may be periodic.

[0050] As described above, Rel-18 is considering supporting an extended function that provides transmission opportunities for multiple CG PUSCHs during a period in which a single CG PUSCH is configured. Hereinafter, the extended function that provides transmission opportunities for multiple CG PUSCHs during a period in which a single CG PUSCH is configured and the transmission operation based on this function may be referred to as "multi-PUSCH CG" or "multiple CG PUSCHs."

[0051] Fig. 4 is a diagram showing an example of a description of the current specification, which is an excerpt from section 6.1.2.3 of TS (technical specification) 38.214 v.18.0.0.

[0052] 4 shows that the higher layer parameter "nrofSlots_InCGperiod" provides the number of consecutive slots allocated within one configured CG period, and that when "nrofSlots_InCGperiod" is configured, PUSCH allocation in each slot follows the higher layer parameter "timeDomainAllocation" in Type 1 PUSCH transmission, and follows the higher layer configuration and the UL grant received in DCI in Type 2 PUSCH transmission. Configuring this "nrofSlots_InCGperiod" may correspond to configuring multi-PUSCH CG.

[0053] <Repetition and TBoMS> To achieve coverage extension and the like in the same way as the above-described multi-PUSCH CG, a transmission operation called repetition transmission and a transmission operation called TBoMS (Transport Block Processing over multi-slot PUSCH) have been studied.

[0054] Repeat transmission is an operation of repeatedly transmitting an information block of a specific processing unit according to a repetition coefficient. For example, in repeat transmission, an information block of a specific processing unit is repeatedly transmitted the number of times indicated by the repetition coefficient.

[0055] TBoMS may be interpreted as an operation of transmitting one transport block (TB) using multiple slots, for example, a transport block (TB) is transmitted over a physical uplink shared channel (PUSCH) allocated to multiple slots.

[0056] Here, an example of parameters for repetitive transmission and TBoMS will be described.

[0057] Fig. 5 is a diagram illustrating an example of a TDRA, which is illustratively shown as a TDRA included in an information element (IE) of "PUSCH-TimeDomainResourceAllocationList."

[0058] The PUSCH-TimeDomainResourceAllocationList information element (IE) is used to configure the time domain relationship between the PDCCH and the PUSCH. For example, the PUSCH-TimeDomainResourceAllocationList includes one or more PUSCH-TimeDomainResourceAllocations. The NW (e.g., a base station) indicates one of the configured time domain allocations in an UL grant, and the UE applies the UL grant.

[0059] As shown in Fig. 5, the TDRA table optionally includes a parameter "numberOfRepetitions" related to the repetition factor and a parameter "numberOfSlotsTBoMS" related to TBoMS. Here, the inclusion of these parameters as options indicates that the presence of these parameters is optional and not essential.

[0060] <Determining the Repetition Factor of the CG PUSCH> If the parameter "numberOfRepetitions" related to the repetition factor exists in the TDRA table (e.g., FIG. 5), the repetition factor of the CG PUSCH follows the numberOfRepetitions existing in the TDRA. If the parameter related to the repetition factor (e.g., numberOfRepetitions) does not exist in the TDRA table, the repetition factor of the CG PUSCH follows the parameter "repK" configured by a higher layer. Here, repK is a parameter included in ConfiguredGrantConfig and indicates the number of repetitions.

[0061] For example, if numberOfRepetitions is present in the TDRA table, the number of repetitions K applied to the transmitted transport block is provided by the indicated row in the TDRA table. For example, if numberOfRepetitions is present in the TDRA table, the number of repetitions K applied to the transmitted transport block is provided by repK.

[0062] <Determining TBoMS of CG PUSCH> If the TBoMS-related parameter "numberOfSlotsTBoMS" exists in the TDRA table, the TBoMS of the CG PUSCH follows numberOfSlotsTBoMS existing in the TDRA. Here, numberOfSlotsTBoMS indicates the number of slots allocated to processing transport blocks on a multi-slot PUSCH of DCI format 0_1 / 0_2. In other words, when a PUSCH scheduled according to DCI format 0_1 / 0_2 is transmitted, the number of slots N used for determining the transport block size (TBS) is indicated by numberOfSlotsTBoMS.

[0063] As described above, there are transmission operations called repetition transmission and TBoMS for coverage extension, but it is possible that repetition transmission is not supported for multi-PUSCH CG, and it is also possible that TBoMS is not supported for multi-PUSCH CG.

[0064] <Restrictions on CG PUSCH Transmission in One CG Period> Restrictions are placed on the transmission time (for example, time duration) of each of the above-described repeated transmission and transmission by TBoMS.

[0065] The UE is not expected to set the time duration of the K repeated transmissions to a time longer than the duration derived by the period P. Note that the period P may be configured by RRC signaling (e.g., a parameter included in ConfiguredGrantConfig). For example, the period P may depend on the configured subcarrier spacing (SCS).

[0066] Here, "expecting" something may be replaced with "assuming" the something or "assuming" the something. Furthermore, "not expecting" something may be replaced with "not assuming" the something or "not assuming" the something. For example, "not expecting" something may be replaced with "not occurring" the something. For example, "not expecting" a setting may be replaced with "not receiving information (e.g., parameters) for the setting" or "not transmitting information (e.g., parameters) for the setting."

[0067] The UE is not expected to set the duration of the K nominal repetitions of the transmission to a time longer than the duration derived by the period P.

[0068] The UE is not expected to set the duration of N×K transmissions to a time longer than the duration derived by the period P, where K denotes the number of repetitions in repetition and N denotes the number of slots used for transmission in TBoMS.

[0069] <Study on repetition of multi-PUSCH CG> Repetition is not supported for multi-PUSCH CG in Rel-18. The specifications based on the most recent discussions are described as shown in Figure 6.

[0070] Fig. 6 is a diagram showing an example of a description of the current specifications regarding multi-PUSCH CG, excerpted from section 6.1.2.3 of TS 38.214 v.18.0.0.

[0071] That is, the latest specification states as shown in Figure 6 that "in the 'configuredGrantConfig', if the UE is configured with the higher layer parameter [nrofSlots_InCGperiod], neither repetition of transmitted transport blocks nor TB processing across multiple slots (e.g., TBoMS) is supported for the configuredGrantConfig (see the underlined part in Figure 6)."

[0072] Regarding the above statement that "repetition is not supported," there are two possible options:

[0073] Option 1: No restrictions are placed on the gNB's instruction and / or configuration of the repetition factor, and the UE assumes that the repetition factor is 1. Option 2: Restrictions are placed on the gNB's instruction and / or configuration of the repetition factor.

[0074] As two options are assumed, it is desirable to clarify the UE behavior in this case and to consider the impact on RRC parameter settings in this case.

[0075] For example, even if the specification specifies that "repetition is not supported" in the multi-PUSCH CG, if the UE's behavior with respect to this specification is unclear, the UE cannot properly perform operations based on the specification. For example, if it is not clear whether the UE should operate based on the RRC configuration or whether the UE should operate based on the UE's assumptions rather than the RRC configuration, the UE cannot properly perform operations based on the specification. For example, even if "repetition is not supported" in the multi-PUSCH CG, if the RRC parameters are configured for repetition, the UE may perform repetition in the multi-PUSCH CG.

[0076] Furthermore, although the above description has been given of the matter that "repetition is not supported" in the multi-PUSCH CG, the same can be considered for TBoMS in the multi-PUSCH CG. For example, the following two options are possible for the matter that "TBoMS is not supported" in the multi-PUSCH CG.

[0077] Option 1: No restrictions are placed on gNB indications and / or configurations for TBoMS. The UE assumes a specific configuration for TBoMS (e.g., N=1). Option 2: Restrictions are placed on gNB indications and / or configurations for TBoMS.

[0078] As two options are assumed, it is desirable to clarify the UE behavior in this case and to consider the impact on RRC parameter settings in this case.

[0079] For example, even if the specifications specify that "TBoMS is not supported" in the multi-PUSCH CG, if the UE's behavior in response to this specification is unclear, the UE cannot appropriately perform operations based on the specification. For example, if it is not clear whether the UE should operate based on the RRC configuration or whether the UE should operate based on the UE's assumptions rather than the RRC configuration, the UE cannot appropriately perform operations based on the specification. For example, even if "TBoMS is not supported" in the multi-PUSCH CG, if the RRC parameters specify settings related to TBoMS, the UE may perform TBoMS in the multi-PUSCH CG.

[0080] Furthermore, as described in <Restrictions on CG PUSCH Transmission in One CG Period>, there are explicit restrictions on the specifications for CG transmission in one CG period (cycle). For example, there are explicit restrictions on CG PUSCH transmission using repeated transmission and / or TBoMS. On the other hand, the latest specifications do not explicitly restrict multi-PUSCH CG in one CG period.

[0081] Therefore, as described above, in the present embodiment, a proposal will be described regarding UE behavior and UE settings (for example, settings of higher layer parameters (for example, RRC parameters)) in response to the issue that "repetition is not supported" in multi-PUSCH CG. Also, in the present embodiment, a proposal will be described regarding UE behavior and UE settings (for example, settings of higher layer parameters (for example, RRC parameters)) in response to the issue that "TBoMS is not supported" in multi-PUSCH CG. Also, in the present embodiment, restrictions on transmission of multi-PUSCH CG will be described.

[0082] Proposal 1 describes an example of UE behavior and RRC parameter settings for the issue that "repetition is not supported" in multi-PUSCH CG.

[0083] Proposal 2 describes an example of UE behavior and RRC parameter settings for the issue that "TBoMS is not supported" in multi-PUSCH CG.

[0084] Proposal 3 describes an example of a restriction on multiple PUSCH CGs in one CG period.

[0085] <Proposal 1> In proposal 1, UE behavior or RRC configuration is performed such that either multi-PUSCH CG operation or repetition operation is set. For example, in proposal 1, the repetition factor is set to 1 for multi-PUSCH CG.

[0086] <Option 1 of Proposal 1> In Option 1 of Proposal 1, for multi-PUSCH CG, the UE assumes that the repetition factor is 1. In this case, no restriction may be placed on the NW (for example, a base station).

[0087] <Option 2 of Proposal 1> In Option 2 of Proposal 1, the repetition factor for multi-PUSCH CG is set to 1. In this case, the UE may transmit a signal (for example, a CG PUSCH) based on control information from a network (for example, a base station).

[0088] <Example 1 of Option 2 of Proposal 1> In Example 1, restrictions are placed on the configuration of RRC parameters.

[0089] <Example 1-1 of Option 2 of Proposal 1> In Example 1-1, the UE does not expect that nrofSlots_InCGperiod is configured in ConfiguredGrantConfig and, at the same time, repK is configured with a value greater than 1. Since nrofSlots_InCGperiod is a parameter for configuring multi-PUSCH CG and repK with a value greater than 1 is a parameter for configuring two or more repeated transmissions, in Example 1-1 the UE does not expect that multi-PUSCH CG and two or more repeated transmissions are configured at the same time.

[0090] A NW (e.g., a base station) does not simultaneously set both nrofSlots_InCGperiod and repK with a value greater than 1 in ConfiguredGrantConfig. A NW (e.g., a base station) transmits, by RRC signaling, ConfiguredGrantConfig that includes either nrofSlots_InCGperiod or repK with a value greater than 1. In this case, ConfiguredGrantConfig does not include both nrofSlots_InCGperiod and repK.

[0091] For example, in ConfiguredGrantConfig, if nrofSlots_InCGperiod is set, it may be assumed that repK is set to 1. Also, if repK is set to a value greater than 1, it may be assumed that nrofSlots_InCGperiod is not set.

[0092] <Example 1-2 of Option 2 of Proposal 1> In Example 1-2, the UE does not expect that nrofSlots_InCGperiod and repK-17 (or repK-v1710) are configured simultaneously in ConfiguredGrantConfig. Since repK-17 is a parameter that configures repeated transmission, in Example 1-2 the UE does not expect that multi-PUSCH CG and repeated transmission are configured simultaneously.

[0093] A network (e.g., a base station) does not simultaneously configure both nrofSlots_InCGperiod and repK-17 in ConfiguredGrantConfig. A network (e.g., a base station) transmits ConfiguredGrantConfig that includes either nrofSlots_InCGperiod or repK-17 by RRC signaling. In this case, ConfiguredGrantConfig does not include both nrofSlots_InCGperiod and repK-17.

[0094] For example, if nrofSlots_InCGperiod is set in ConfiguredGrantConfig, it is assumed that repK-17 is not set. Also, for example, if repK-17 is set in ConfiguredGrantConfig, it is assumed that nrofSlots_InCGperiod is not set.

[0095] Example 1 of Option 2 of Proposal 1 may be applied to multi-PUSCH CG for both Type 1 CG PUSCH and Type 2 CG PUSCH.

[0096] Note that, in Example 1 of Option 2 of Proposal 1 described above, nrofSlots_InCGperiod and repK or repK-17 are subject to restrictions, but the present disclosure is not limited to this. Restrictions may be placed on parameters for setting multi-PUSCH CG other than nrofSlots_InCGperiod, or on parameters for setting repetitions other than repK or repK-17. For example, the UE does not expect that a parameter for setting multi-PUSCH CG other than nrofSlots_InCGperiod and a parameter for setting repetitions other than repK or repK-17 will be set at the same time. In this case, it is assumed that when a parameter for setting multi-PUSCH CG other than nrofSlots_InCGperiod is set, a parameter for setting repetitions including repK or repK-17 will not be set. Alternatively, for example, the UE does not expect that a parameter for setting multi-PUSCH CG including nrofSlots_InCGperiod and a parameter for setting repetitions including repK or repK-17 will be set at the same time.

[0097] <Example 2 of Option 2 of Proposal 1> In Example 2, a limit is placed on the number of repetitions indicated by the TDRA.

[0098] For example, if nrofSlots_InCGperiod is configured for a UE and numberOfRepetitions is present in the resource allocation table (e.g., TDRA table) configured for a DCI format that activates the CG configuration, the UE does not expect the value of numberOfRepetitions in the row of the TDRA indicated by the activation DCI to be greater than 1.

[0099] Note that Example 2 of Option 2 in Proposal 1 may be applied to the multi-PUSCH CG of the Type 2 CG PUSCH. Note that both Example 1 and Example 2 of Option 2 in Proposal 1 may be applied to the multi-PUSCH CG of the Type 2 CG PUSCH.

[0100] <First Example of TP (Text Proposal) for Example 2 of Option 2 of Proposal 1> Figure 7 is a diagram showing a first example of a TP for Example 2 of Option 2 of Proposal 1. Figure 7 shows an example of adding description items to the description of the specification shown in Figure 6. In the example of Figure 7, the following items are added: - If a UE is configured with nrofSlots_InCGperiod for PUSCH transmission of Type 2 CG and numberOfRepetitions exists in the resource allocation table configured for a DCI format that activates the CG configuration, the UE does not expect the value of numberOfRepetitions in the row of the TDRA indicated by the activation DCI to be greater than 1 (see the underlined part in Figure 7).

[0101] <Second Example of TP for Example 2 of Option 2 of Proposal 1> Figure 8 is a diagram showing a second example of TP for Example 2 of Option 2 of Proposal 1. Figure 8 shows an example of adding description items to the description of the specification shown in Figure 6. In the example of Figure 8, the following items are added: - When a UE is configured with nrofSlots_InCGperiod for PUSCH transmission of Type 2 CG, the UE does not expect the row of the TDRA indicated by the activation DCI to indicate a numberOfRepetitions value greater than 1 (see the underlined part in Figure 8).

[0102] In the above-described Proposal 1 (e.g., Option 2), a UE (an example of a terminal) receives control information (e.g., ConfiguredGrantConfig) and controls transmission operations of uplink signals based on the control information without anticipating that the received control information includes both first information (e.g., nrofSlots_InCGperiod) for configuring transmission operations of multiple uplink signals in one period (e.g., multi-PUSCH CG) and second information (e.g., numberOfRepetitions) indicating a repetition number of two or more for repeated transmission. Furthermore, a base station generates control information that includes either the first information for configuring transmission operations of multiple uplink signals in one period or the second information indicating a repetition number of two or more for repeated transmission, but not both, and transmits the control information.

[0103] According to the above-described Proposal 1, the UE behavior and / or RRC configuration regarding the issue that "repetition is not supported" in the multi-PUSCH CG becomes clear, so that it is possible to configure a multi-PUSCH CG that does not take into account (anticipates) the repetition operation, and to appropriately configure transmission opportunities for multiple uplink signals.

[0104] <Proposal 2> In Proposal 2, UE behavior or RRC configuration is performed such that either multi-PUSCH CG operation or TBoMS operation is configured. For example, in Proposal 2, TBoMS is not supported for multi-PUSCH CG.

[0105] <Option 1 of Proposal 2> When multi-PUSCH CG is configured, N>1 is not expected for Type 2 CG. Note that N indicates the number of slots used for TBS determination in TBoMS. In other words, N indicates the number of slots that can be used for transmission in TBoMS. In this case, the UE may transmit a signal (e.g., CG PUSCH) based on control information from the network (e.g., base station).

[0106] <Example 1 of Option 1 of Proposal 2> In the case of Type 2 CG, if nrofSlots_InCGperiod is configured in ConfiguredGrantConfig, the UE does not expect numberOfSlotsTBoMS to be present in the row of the TDRA indicated by the activation DCI.

[0107] For example, in this case, it is expected that the numberOfSlotsTBoMS does not exist in the row of the TDRA indicated by the activation DCI. Also, for example, in this case, it is expected that the activation DCI does not indicate a row of the TDRA in which the numberOfSlotsTBoMS exists. Also, for example, in this case, it is expected that the activation DCI indicates a row of the TDRA in which the numberOfSlotsTBoMS does not exist.

[0108] <Example of TP for Example 1 of Option 1 of Proposal 2> Figure 9 is a diagram showing an example of TP for Example 1 of Option 1 of Proposal 2. Figure 9 shows an example of adding description items to the description of the specification shown in Figure 6. In the example of Figure 9, the following items are added: - When the UE is configured with nrofSlots_InCGperiod for PUSCH transmission of Type 2 CG, the UE does not expect numberOfSlotsTBoMS to be present in the row of the TDRA indicated by the activation DCI (see the underlined part in Figure 9).

[0109] <Example 2 of Option 1 of Proposal 2> In the case of Type 2 CG, if nrofSlots_InCGperiod is configured in ConfiguredGrantConfig, the UE does not expect numberOfSlotsTBoMS with a value greater than 1 to be present in the rows of the TDRA indicated by the activation DCI.

[0110] In this case, the UE may assume that the row of the TDRA indicated by the activation DCI has a numberOfSlotsTBoMS equal to 1.

[0111] <Example of TP for Example 2 of Option 1 of Proposal 2> Figure 10 is a diagram showing an example of TP for Example 2 of Option 1 of Proposal 2. Figure 10 shows an example of adding description items to the description of the specification shown in Figure 6. In the example of Figure 10, the following items are added: - When a UE is configured with nrofSlots_InCGperiod for PUSCH transmission of Type 2 CG, the UE does not expect the row of the TDRA indicated by the activation DCI to indicate a numberOfSlotsTBoMS value greater than 1 (see the underlined part in Figure 10).

[0112] Note that, in Option 1 of Proposal 2 described above, nrofSlots_InCGperiod and numberOfSlotsTBoMS are subject to restrictions, but the present disclosure is not limited to this. Restrictions may be placed on parameters for configuring multi-PUSCH CG other than nrofSlots_InCGperiod, or on parameters for configuring TBoMS other than numberOfSlotsTBoMS. For example, the UE does not expect that a parameter for configuring multi-PUSCH CG other than nrofSlots_InCGperiod and a parameter for configuring TBoMS other than numberOfSlotsTBoMS will be configured simultaneously. In this case, it is assumed that when a parameter for configuring multi-PUSCH CG other than nrofSlots_InCGperiod is configured, a parameter for configuring repetition including numberOfSlotsTBoMS will not be configured. Alternatively, for example, the UE does not expect that a parameter for configuring multi-PUSCH CG including nrofSlots_InCGperiod and a parameter for configuring repetition including numberOfSlotsTBoMS will be configured simultaneously.

[0113] <Option 2 of Proposal 2> In Option 2, when multi-PUSCH CG is configured, the UE assumes that N is 1 for Type 2 CG. Here, N=1 corresponds to TBoMS not being applied. In other words, assuming N=1 corresponds to assuming TBoMS not being applied.

[0114] <Example 3 of Option 2 of Proposal 2> For example, if nrofSlots_InCGperiod is configured in ConfiguredGrantConfig for a UE, the UE assumes that N is a specific value (e.g., 1) regardless of the numberOfSlotsTBoMS of the TDRA rows indicated by the activation DCI.

[0115] <Example of TP for Example 3 of Option 2 of Proposal 2> Figure 11 is a diagram showing an example of TP for Example 3 of Option 2 of Proposal 2. Figure 11 shows an example of adding description items to the description of the specification shown in Figure 6. In the example of Figure 11, the following items are added: - When a UE is configured with nrofSlots_InCGperiod for PUSCH transmission of Type 2 CG, the UE assumes that numberOfSlotsTBoMS is not present or that numberOfSlotsTBoMS is equal to 1.

[0116] In the above-described Proposal 2, a UE (an example of a terminal) receives control information (e.g., ConfiguredGrantConfig) and, if the received control information includes first information (e.g., nrofSlots_InCGperiod) for configuring a first transmission operation of a plurality of uplink signals in one period (e.g., multi-PUSCH CG), controls the first transmission operation of the uplink signals based on the first information, without anticipating that the number of transmission units in a second transmission operation (e.g., TBoMS) for transmitting an information block of a specific processing unit (e.g., TB) in multiple transmission units (e.g., multiple slots) is greater than 1. Furthermore, a base station generates control information that includes the first information for configuring the first transmission operation of a plurality of uplink signals in one period but does not include information indicating that a second transmission operation for transmitting an information block of a specific processing unit in multiple transmission units will be performed, and transmits the control information.

[0117] According to the above-described Proposal 2, the UE behavior and / or RRC configuration for the issue of "TBoMS not supported" in the multi-PUSCH CG becomes clear, so that it is possible to configure a multi-PUSCH CG that does not take into account (anticipates) the operation of TBoMS, and to appropriately configure transmission opportunities for multiple uplink signals.

[0118] <Proposal 3> When nrofSlots_InCGperiod is configured, the UE does not expect the duration for K PUSCH transmission allocations to be configured longer than the duration derived by the period P, where K may be in the range of 1 < K ≦ nrofSlots_InCGperiod. Here, the period P may be configured by RRC signaling (e.g., a parameter included in ConfiguredGrantConfig). For example, the period P may depend on the configured subcarrier spacing (SCS).

[0119] In other words, when nrofSlots_InCGperiod is configured, the UE does not expect the duration for the K PUSCH transmission allocations to be longer than the duration derived by the periodicity P. In this case, the duration derived by the periodicity P may be configured (e.g., K may be configured) to be equal to or greater than the duration for the K PUSCH transmission allocations.

[0120] <Example of TP for Proposal 3> Figure 12 is a diagram showing an example of TP for Proposal 3. Figure 12 shows an example of adding description items to the description of the specification shown in Figure 4. In the example of Figure 12, the following items are added: When nrofSlots_InCGperiod is configured, the UE does not expect the duration for transmission of K (1 < K ≤ nrofSlots_InCGperiod) CG PUSCH opportunities to be configured to be longer than the duration derived by the period P.

[0121] In the above-described Proposal 3, a UE (an example of a terminal) receives control information, and when the control information (e.g., ConfiguredGrantConfig) configures a specific number (e.g., nrofSlots_InCGperiod) related to the number of multiple uplink signals in a first transmission operation (e.g., multi-PUSCH CG) for transmitting multiple uplink signals in one period, the UE performs control such that the second duration for the allocation of the transmission of the multiple uplink signals (allocation of the multi-PUSCH CG) is not expected to be longer than the first duration derived from the specific periodicity P. A base station generates control information that configures a specific number related to the number of multiple uplink signals in a first transmission operation for transmitting multiple uplink signals in one period, transmits the control information, and when the specific number is configured by the control information, the second duration for the allocation of the transmission of the multiple uplink signals is not expected to be longer than the first duration derived from the specific periodicity P.

[0122] According to Proposal 3 described above, the relationship between the time duration in the multi-PUSCH CG and the period P becomes clear, so that the multi-PUSCH CG performed within the period P can be set, and transmission opportunities for multiple uplink signals can be appropriately set.

[0123] Note that the TPs shown in the above proposals are merely examples, and the present disclosure is not limited thereto. For example, the additional items of each TP shown in the drawings may be partially changed, added, or moved. Furthermore, the location of the additional items of each TP does not have to be limited to the location shown in the drawings.

[0124] Next, the configurations of the base station 100 and the terminal 200 will be described. Note that the configurations of the base station 100 and the terminal 200 described below are examples of functions related to this embodiment. The base station 100 and the terminal 200 may have functions not shown. Furthermore, the functional divisions and / or names of the functional units are not limited as long as the functions perform the operations related to this embodiment.

[0125] <Configuration of Base Station> Fig. 13 is a block diagram showing an example of the configuration of the base station 100. 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 the terminal 200 (see Fig. 14) by radio.

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

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

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

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

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

[0131] The transmitting unit 101 and the receiving unit 102 may be collectively referred to as a communication unit.

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

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

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

[0135] For example, in Proposal 1, the control unit 103 of the base station 100 generates control information (e.g., ConfiguredGrantConfig) that includes either first information (e.g., nrofSlots_InCGperiod) that configures transmission operations of multiple uplink signals in one period (e.g., multi-PUSCH CG) or second information (e.g., numberOfRepetitions) that indicates the number of repetitions of repeated transmission, which is two or more, but does not include both. The transmitting unit 101 transmits the control information.

[0136] For example, in Proposal 2, the control unit 103 of the base station 100 generates control information (e.g., ConfiguredGrantConfig) that includes first information (e.g., nrofSlots_InCGperiod) that sets a first transmission operation (e.g., multi-PUSCH CG) of multiple uplink signals in one period, but does not include information indicating that a second transmission operation (e.g., TBoMS) is to be performed that transmits an information block of a specific processing unit (e.g., TB) in multiple transmission units (e.g., multiple slots), and transmits the control information. The transmitting unit 101 transmits the control information.

[0137] For example, in Proposal 3, the control unit 103 of the base station 100 generates control information (e.g., ConfiguredGrantConfig) that sets a specific number (e.g., nrofSlots_InCGperiod) related to the number of multiple uplink signals in a first transmission operation (e.g., multi-PUSCH CG) that transmits multiple uplink signals in one period. The transmission unit 101 transmits the control information. In this case, when the specific number is set by the control information, it is not expected that the second duration for allocating the transmission of the multiple uplink signals will be longer than the first duration derived by the specific period.

[0138] 14 is a block diagram showing an example of the configuration of the terminal 200. 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 100, for example, wirelessly.

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

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

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

[0142] 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, terminal 200 receives control information from base station 100 using the PUCCH and transmits uplink data signals using the PUSCH.

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

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

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

[0146] For example, the control unit 203 controls transmission of information to be fed back to the base station 100. The information to be fed back to the base station 100 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 100 may be included in UCI. The UCI is transmitted in the resources of the PUCCH.

[0147] Control unit 203 configures 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 base station 100. Control unit 203 determines PUCCH resources to be used for transmitting information to be fed back to base station 100. Under the control of control unit 203, transmission unit 202 transmits the information to be fed back to base station 100 in the PUCCH resources determined by control unit 203.

[0148] For example, in Proposal 1, receiving unit 201 of terminal 200 receives control information (e.g., ConfiguredGrantConfig). Control unit 203 controls the transmission operation of the uplink signal based on the control information without anticipating that the received control information includes both first information (e.g., nrofSlots_InCGperiod) that configures the transmission operation of multiple uplink signals in one period (e.g., multi-PUSCH CG) and second information (e.g., numberOfRepetitions) that indicates two or more repetitions of repeated transmission.

[0149] For example, in Proposal 2, receiving unit 201 of terminal 200 receives control information (e.g., ConfiguredGrantConfig). When the received control information includes first information (e.g., nrofSlots_InCGperiod) that configures a first transmission operation of a plurality of uplink signals in one period (e.g., multi-PUSCH CG), control unit 203 controls the first transmission operation of the uplink signals based on the first information, without anticipating that the number of transmission units in a second transmission operation (e.g., TBoMS) that transmits an information block of a specific processing unit (e.g., TB) in multiple transmission units (e.g., multiple slots) is greater than one.

[0150] For example, in Proposal 3, receiving unit 201 of terminal 200 receives control information (e.g., ConfiguredGrantConfig). When a specific number (e.g., nrofSlots_InCGperiod) related to the number of multiple uplink signals in a first transmission operation (e.g., multi-PUSCH CG) that transmits multiple uplink signals in one period is configured by the control information, control unit 203 performs unexpected control such that a second duration for allocating transmission of the multiple uplink signals (allocation of multi-PUSCH CG) becomes longer than a first duration derived by a specific period P.

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

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

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

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

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

[0156] 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. 15 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to this 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0190] Fig. 16 shows an example configuration of a vehicle 2001. As shown in Fig. 16, 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.

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

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

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

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

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

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

[0197] The communication module 2013 can communicate, via the communication port, with the microprocessor 2031 and the components of the vehicle 2001. 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 2029, which are provided in the vehicle 2001.

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

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

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

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

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

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

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

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

[0206] "First," "Second" Any reference to an element using designations 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0232] 10 Wireless communication system 20 NG-RAN 100 Base station (gNB) 200 Terminal (UE) 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims

1. A terminal comprising: a receiving unit that receives control information; and a control unit that controls the transmission operation of an uplink signal based on the control information, without anticipating that the control information includes both first information that sets the transmission operation of multiple uplink signals in one period and second information that indicates a repetition number of two or more for repeated transmission.

2. The terminal according to claim 1, wherein the control unit controls the transmission operation of the plurality of uplink signals based on the first information when the control information includes the first information, without expecting that the control information includes the second information.

3. The terminal according to claim 1, wherein the second information is provided by higher layer signaling, and the second information indicates that the number of repetitions is 1.

4. A base station comprising: a control unit that generates control information including either first information that sets the transmission operation of multiple uplink signals in one period or second information that indicates a number of repetitions of repeated transmission that is two or more, but does not include both; and a transmission unit that transmits the control information.

5. A communications method in which a terminal receives control information and controls the transmission operation of an uplink signal based on the control information, without anticipating that the control information includes both first information that sets the transmission operation of multiple uplink signals in one period and second information that indicates a repetition number of two or more for repeated transmission.

Images