Terminal, base station, wireless system, and communication method

JPWO2024150342A5Pending Publication Date: 2025-09-17
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2024569922
Authority / Receiving Office
JP · JP
Patent Type
Applications
Filing Date
2025-07-09
Publication Date
2025-09-17

AI Technical Summary

Technical Problem

Current communication systems face challenges in efficiently managing multiple uplink signal opportunities in high-capacity communications, particularly in extended reality scenarios, where capacity, latency, and energy savings are critical, and existing configurations do not effectively support dynamic and semi-static PUCCH carrier switching to reduce HARQ-ACK latency.

Method used

A terminal and communication method that dynamically determines the activation and deactivation of uplink signal transmission based on downlink control signals and upper layer signaling parameters, allowing for individual time resource allocation and supporting multiple uplink signal occasions in a single period, which includes configuring PUCCH resources for each UL BWP and enabling dynamic and semi-static PUCCH carrier switching.

Benefits of technology

This approach enhances the ability to manage multiple uplink signals efficiently, reducing latency and improving communication capacity in high-capacity scenarios like extended reality, while optimizing energy usage and supporting advanced communication requirements.

✦ Generated by Eureka AI based on patent content.
Patent Text Reader

Abstract

Provided is a terminal comprising a reception unit which receives a parameter of higher layer signaling and a control unit which determines activation or deactivation of transmission of an uplink signal on the basis of a downlink control signal and the parameter of the higher layer signaling. In this invention, the control unit determines each of a plurality of uplink signal occasions in one period on the basis of individual pieces of time resource allocation information.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal and communication method

[0001] The present disclosure relates to a terminal 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) (see, for example, Non-Patent Document 2). The CG PUSCH includes a Type 1 CG PUSCH and a Type 2 CG PUSCH.

[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. It also considers the target requirements for XR, including capacity, latency, mobility, and energy efficiency.

[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 opportunities for large-capacity communications such as XR.

[0008] One aspect of the present disclosure is to provide a terminal and a communication method that appropriately set multiple uplink signal opportunities in high-capacity communication.

[0009] A terminal according to one aspect of the present disclosure has a receiving unit that receives parameters of upper layer signaling, and a control unit that determines activation and deactivation of transmission of uplink signals based on downlink control signals and parameters of upper layer signaling, and the control unit determines each of the occasions of multiple uplink signals in one period based on individual time resource allocation information.

[0010] A terminal according to one aspect of the present disclosure has a receiving unit that receives parameters of upper layer signaling, and a control unit that determines activation and deactivation of transmission of uplink signals based on a downlink control signal and the parameters of the upper layer signaling, and the control unit determines each of the occasions of multiple uplink signals in one period based on one piece of time resource allocation information and the number of occasions of the multiple uplink signals.

[0011] A communication method according to one aspect of the present disclosure includes a terminal receiving parameters of higher layer signaling, determining activation and deactivation of transmission of uplink signals based on the downlink control signal and the parameters of the higher layer signaling, and determining each of the occasions of multiple uplink signals in one period based on individual time resource allocation information.

[0012] A communication method according to one aspect of the present disclosure includes a terminal receiving parameters of upper layer signaling, determining activation and deactivation of transmission of uplink signals based on the downlink control signal and the parameters of the upper layer signaling, and determining each of the occasions of multiple uplink signals in one period based on one piece of time resource allocation information and the number of occasions of the multiple uplink signals.

[0013] FIG. 1 is a diagram showing an example of dual connectivity (DC). FIG. 2 is a diagram showing an example of PUCCH carrier switching. FIG. 3 is a diagram showing parameters of configuredGrantConfig. FIG. 4 is a diagram showing parameters of configuredGrantConfig. FIG. 5 is a diagram showing an example of a TDRA table. FIG. 6 is a block diagram showing an example of the configuration of a base station 10. FIG. 7 is a block diagram showing an example of the configuration of a terminal 20. FIG. 8 is a diagram showing an example of the hardware configuration of a base station and a terminal according to the present embodiment. FIG. 9 is a diagram showing an example of the configuration of a vehicle 2001.

[0014] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings. In URLLC, enhancements to terminal feedback for Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK) are being considered. HARQ-ACK is an example of information regarding an acknowledgement (e.g., an acknowledgement) for data received by a terminal. In response to these URLLC considerations, it has been agreed to support dynamic and semi-static PUCCH carrier switching. Note that PUCCH carrier switching may also be called by other names, such as control information transmission carrier switching.

[0015] PUCCH carrier switching is a technique applied when a base station communicates via multiple cells. Dual connectivity, which is an example of communication via multiple cells, and PUCCH carrier switching will be described below.

[0016] <Dual Connectivity> Figure 1 is a diagram showing an example of dual connectivity (DC). In the example of Figure 1, the base station 10-1 may be a master node (MN). The base station 10-2 may be a secondary node (SN). As shown in the example of Figure 1, in DC, carriers between different base stations are aggregated.

[0017] 1, the base station 10-1 communicates with the terminal 20 via a primary cell (Pcell) and a secondary cell (Scell). In the example of Fig. 1, the terminal 20 establishes a Radio Resource Control (RRC) connection with the base station 10-1.

[0018] In the case of DC, since there may be a delay in communication between the base station 10-1 and the base station 10-2, it is difficult to notify the base station 10-2 of the uplink control information (e.g., Uplink Control Information (UCI)) received by the Pcell of the base station 10-1 via a backhaul link (e.g., a wired or wireless link connecting the base station 10-1 and the base station 10-2) and reflect it in the scheduling of the Scell ​​under the base station 10-2. Therefore, in DC, in addition to the Pcell of the base station 10-1, one carrier under the base station 10-2 may be set as the Primary Scell ​​(PScell), and PUCCH transmission may be supported by the PScell. In this case, the terminal 20 transmits UCI to the base station 10-2 via the PScell.

[0019] In the example of FIG. 1, the terminal 20 configures an Scell ​​in addition to a Pcell for the base station 10-1. The terminal 20 also configures an Scell ​​in addition to a PScell ​​for the base station 10-2. The terminal 20 transmits UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. The terminal 20 also transmits UCI of each carrier under the control of the base station 10-2 on the PUCCH of the PScell. In the example of FIG. 1, the cell group (CG) under the control of the base station 10-1 may be referred to as a Master Cell-Group (MCG). The cell group under the control of the base station 10-2 may be referred to as a Secondary Cell-Group (SCG).

[0020] When DC is performed, terminal 20 may transmit PUCCH via a Pcell, a PScell, and / or a PUCCH-Scell. Generally, it is not expected that terminal 20 transmits PUCCH via an Scell ​​other than a Pcell, a PScell, and a PUCCH-Scell.

[0021] <PUCCH Carrier Switching> PUCCH carrier switching is being studied as a method for reducing the latency of HARQ-ACK feedback in the Time Division Duplex (TDD) system.

[0022] Fig. 2 is a diagram showing an example of PUCCH carrier switching. In the example of Fig. 2, a base station and a terminal communicate via cell 1 and cell 2. In the example of Fig. 2, cell 1 is a Pcell, and cell 2 is an Scell. The example of Fig. 2 also shows downlink (DL) slots and uplink (UL) slots in each cell.

[0023] In the example of FIG. 2 , the terminal receives data at timing S101 (receives a Physical Downlink Shared Channel (PDSCH)). The terminal attempts to transmit a HARQ-ACK for the data received at timing S101 at timing S102, but at timing S102, the slot of cell 1 is a downlink (DL) slot. Therefore, when the terminal transmits a HARQ-ACK in cell 1, the transmission of the HARQ-ACK is postponed until the transmission timing of the PUCCH in the uplink (UL) slot (e.g., timing S103 in FIG. 2 ), which increases the latency of the HARQ-ACK transmission. Note that the transmission timing of the PUCCH in the uplink (UL) slot may also be referred to as a PUCCH transmission opportunity.

[0024] In the example of Fig. 2, at timing S102, the slot of cell 2 is a UL slot. In the example of Fig. 2, if the terminal can transmit a HARQ-ACK for the data received at S101 at the PUCCH transmission opportunity at timing S102 of cell 2, the latency of the HARQ-ACK transmission can be reduced. URLLC requires low latency, particularly in the wireless section. For this reason, 3GPP is considering PUCCH carrier switching, in which a terminal switches the carrier on which it transmits PUCCH, as an extension of URLLC technology.

[0025] In the following embodiments, "the same timing" may mean the exact same timing, or may mean that all or part of a time resource (for example, one or more symbols (which may be a resource with a time unit shorter than a symbol)) is the same or overlaps.

[0026] PUCCH carrier switching may refer to the case where, when a terminal attempts to transmit a PUCCH at a specific transmission timing of a Pcell (which may be a PScell ​​or a PUCCH-Scell), the slot of the specific transmission timing of the Pcell (which may be a PScell ​​or a PUCCH-Scell) is a DL slot, and therefore the terminal switches the cell from which the PUCCH is transmitted from the Pcell (which may be a PScell ​​or a PUCCH-Scell) to one of one or more Scells in which the slot with the same timing as the specific transmission timing is a UL slot (in the case of a PScell, an Scell ​​other than the PScell, and in the case of a PUCCH-Scell, an Scell ​​other than the PUCCH-Scell). Note that, in embodiments of the present invention, the unit of the specific transmission timing is not limited to a slot. For example, the specific transmission timing may be a timing in units of a subframe or a timing in units of a symbol.

[0027] Two methods are being considered for realizing PUCCH carrier switching. The first method is a method in which a base station dynamically instructs a terminal on a carrier for transmitting the PUCCH. The second method is a method in which a base station semi-statically sets a terminal on a carrier for transmitting the PUCCH. Note that in the following embodiments, "transmitting a PUCCH" and "transmitting a PUCCH" may refer to transmitting uplink control information via a PUCCH.

[0028] The terminal may notify the base station of terminal capability information (UE capability) that defines information about the terminal's capabilities regarding PUCCH transmission.

[0029] For example, information indicating whether the terminal supports switching of settings related to transmission of control information may be defined as the terminal capability information of the terminal. Switching of settings related to transmission of control information may be, for example, switching of resources (e.g., carriers or cells) used for transmitting the control information. Switching of resources used for transmitting the control information may be referred to as "PUCCH carrier switching." Furthermore, information indicating application of dynamic PUCCH carrier switching and / or semi-static PUCCH carrier switching may be defined as the terminal capability information of the terminal.

[0030] The configuration operation of quasi-static PUCCH carrier switching may be based on the RRC setting of the PUCCH cell timing pattern of the PUCCH cell to which quasi-static PUCCH carrier switching applies, and the configuration operation of quasi-static PUCCH carrier switching may be supported between cells of different numerologies.

[0031] In PUCCH carrier switching, PUCCH resources may be configured for each UL BWP (Uplink Bandwidth Part) (for example, for each candidate cell and the UL BWP of the candidate cell).

[0032] In the case of PUCCH carrier switching based on dynamic instruction of control information, the K1 value (offset) from PDSCH to HARQ-ACK may be interpreted based on the numerology of the dynamically instructed target PUCCH cell. Note that the control information may be control information for scheduling PUCCH, such as Downlink control information (DCI). The numerology may also be considered as slot or Subcarrier Spacing (SCS).

[0033] In URLLC, enhancements to the HARQ-ACK Codebook (HARQ-ACK CB) feedback function of a terminal are being considered. Below, an overview of Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB is explained (see Non-Patent Document 1 for details).

[0034] <CG enhancements in Rel-18 XR> At the RAN1 #111 meeting, it was agreed to support CG enhancements for Rel-18 XR.

[0035] Agreement: Supports dynamic indication of one or more unused CG PUSCH occasions based on Uplink Control Information (UCI) by the terminal.

[0036] For example, if there is an unused CG PUSCH occasion, the terminal may report the unused CG PUSCH occasion using UCI.

[0037] Agreement Supports multiple CG PUSCH occasions in the period of a single CG PUSCH configuration.

[0038] For example, when multiple CG PUSCHs are configured, the terminal may configure multiple CG PUSCH occasions during the period of one of the CG PUSCH configurations.

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

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

[0041] Type 1 CG PUSCH The transmission parameters of Type 1 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "rrc-ConfiguredUplinkGrant". Activation and deactivation of Type 1 CG PUSCH depend on the RRC-configuration and are independent of Downlink Control Information (DCI).

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

[0043] <CG PUSCH configurations> Figures 3 and 4 show parameters of configuredGrantConfig. The parameters shown in Figure 4 follow the parameters shown in Figure 3. The parameters of configuredGrantConfig shown in Figures 3 and 4 are used to configure the granted uplink transmission.

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

[0045] <Analysis> As mentioned in <CG Extensions in Rel-18 XR> above, it was agreed to support CG extensions for Rel-18 XR. However, in high-capacity communications such as Rel-18 XR, there is room for further consideration regarding the configuration of multiple CG PUSCH occasions in a single CG PUSCH configuration.

[0046] ・Study 1 Type 1 CG PUSCH related settings

[0047] - Study 2: Type 2 CG PUSCH-related settings and verification of activated DCI As mentioned in <Verification of activated DCI>, in the current specifications, the terminal cannot verify activated DCI if the DCI indicates multiple SLIVs using the TDRA field.

[0048] Study 3: Possibility of limiting multiple CG PUSCH occasions in one CG period

[0049] Based on the above considerations 1-3, Proposal 1-3 will be explained below.

[0050] <Proposal 1> Proposal 1 appropriately configures multiple CG PUSCH occasions in high-capacity communication by specifying the Type 1 CG PUSCH-related configuration of Study 1. Proposal 1 may include Option 1 and Option 2.

[0051] <Proposal 1 - Option 1> Option 1 of Proposal 1 does not support multiple CG PUSCH occasions in one CG period for Type 1 CG PUSCH configuration.

[0052] Example 1: The terminal does not expect "timeDomainAllocation" in "rrc-ConfiguredUplinkGrant" that indicates multiple SLIVs. "rrc-ConfiguredUplinkGrant" is an RRC parameter related to the configuration of uplink grants, and "timeDomainAllocation" is a parameter related to the allocation of time resources.

[0053] Example 2: The terminal does not expect the RRC parameter indicating the number of CG PUSCH occasions in one CG period to be configured for Type 1 CG PUSCH.

[0054] In the operations of the above examples 1 and 2, for example, the base station may control enabling and disabling of multiple CG PUSCH occasions, where it is assumed that the terminal can support multiple CG PUSCH occasions in the Type 1 CG PUSCH.

[0055] When the base station disables the function of multiple CG PUSCH occasions in Type 1 CG PUSCH, it does not include "timeDomainAllocation" that indicates multiple SLIVs in "rrc-ConfiguredUplinkGrant." Since "timeDomainAllocation" that indicates multiple SLIVs is not included in "rrc-ConfiguredUplinkGrant," the terminal does not support multiple CG PUSCH occasions.

[0056] In addition, the base station does not configure the RRC parameter indicating the number of CG PUSCH occasions for the Type 1 CG PUSCH. The terminal does not support multiple CG PUSCH occasions because the RRC parameter indicating the number of CG PUSCH occasions is not configured for the Type 1 CG PUSCH.

[0057] Note that "expectation" may be replaced with "assuming" or "determining." "Valid" and "invalid" may be replaced with "activated" and "inactivated."

[0058] <Proposal 1 - Option 2> Proposal 1 Option 2 supports multiple CG PUSCH occasions in one CG period for Type 1 CG PUSCH configuration.

[0059] Example 1: If "timeDomainAllocation" in "rrc-ConfiguredUplinkGrant" indicates multiple SLIVs, the terminal expects (supports) multiple CG PUSCH occasions in one CG period.

[0060] Example 2: The terminal expects (supports) multiple CG PUSCH occasions in one CG period if the number of CG PUSCH occasions in one CG period is configured for Type 1 CG PUSCH.

[0061] When the terminal expects multiple CG PUSCH occasions in Example 1 or Example 2, the terminal expects that one or more of the following conditions are satisfied. The conditions may also be referred to as states.

[0062] Condition 1: Dynamic indication of unused CG PUSCH occasions is enabled for Type 1 CG PUSCH configuration.

[0063] Condition 2: The physical priority of the Type 1 CG PUSCH configuration is specified as either High or Low.

[0064] For example, "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH configuration is set to Low in the terminal.

[0065] For example, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "0." Alternatively, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "1."

[0066] Condition 3: Repetition (Type A or Type B) is not configured for Type 1 CG PUSCH configuration.

[0067] For example, "rep-K" is not set in "ConfiguredGrantConfig", or "rep-K" is set to "1". Note that "rep-K" is a parameter indicating the number of repetitions of the CG PUSCH.

[0068] For example, "pusch-RepTypeIndicator" is not set in "rrc-ConfiguredUplinkGrant".

[0069] For example, "pusch-RepTypeIndicator" is not set in "rrc-ConfiguredUplinkGrant" as 'pusch-RepTypeA', or "pusch-RepTypeIndicator" is not set in "rrc-ConfiguredUplinkGrant" as 'pusch-RepTypeB'.

[0070] Note that "pusch-RepTypeIndicator" is a parameter indicating the repetition type. Repetition type A may be interpreted as a form in which the PUSCH allocated within a slot is repeatedly transmitted. In other words, the PUSCH is 14 symbols or less and cannot be allocated across multiple slots (adjacent slots).

[0071] On the other hand, Repetition type B may be interpreted as repeated transmission of a PUSCH in which a PUSCH of 15 symbols or more may be allocated. In the present embodiment, it may be permitted to allocate such a PUSCH across multiple slots.

[0072] Condition 4: Multi-TPR transmission is not configured due to Type 1 CG PUSCH configuration. TPR stands for Transmission and Reception Point.

[0073] For example, "pathlossReferenceIndex2" and / or "srs-ResourceIndicator2" and / or "precodingAndNumberOfLayers2" are not set in "rrc-ConfiguredUplinkGrant." In other words, parameters related to the second SRS are not set in the terminal. SRS is an abbreviation for Sounding Reference Signal.

[0074] Note that "pathlossReferenceIndex2" is a parameter indicating a reference signal used as a PUSCH pathloss reference for the second SRS resource set. "srs-ResourceIndicator2" is a parameter indicating an SRS resource used for the second SRS resource set. "precodingAndNumberOfLayers2" is a parameter indicating the precoding and number of layers for the second SRS resource set.

[0075] Condition 5: "cg-SDT-Configuration" is not set in "rrc-ConfiguredUplinkGrant".

[0076] "cg-SDT-Configuration" is a parameter related to the SDT configuration. SDT stands for Small Data Transmission. SDT transmits CG PUSCH in the RRC inactive state.

[0077] Condition 6: The period of the CG PUSCH is greater than X symbols. Or, the period of the CG PUSCH is greater than the number of slots of the specified multiple SLIVs. In other words, the period of the CG PUSCH is set so that the specified multiple CG PUSCH occasions are transmitted within the CG period.

[0078] Modification: If one or more of the above conditions are not met, the terminal may transmit one CG PUSCH occasion in one CG period.

[0079] <Summary of Proposal 1> A terminal determines whether to support multiple CG PUSCH occasions for Type 1 CG PUSCH in one period based on parameters of higher layer signaling. This operation allows the terminal to appropriately configure multiple CG PUSCH occasions in high-capacity communication.

[0080] <Proposal 2> Proposal 2 specifies the Type 2 CG PUSCH-related configuration and verification of activated DCI in Study 2, thereby appropriately configuring multiple CG PUSCH occasions in high-capacity communications.

[0081] In Proposal 2, multiple CG PUSCH occasions are supported in one CG period for Type 2 CG PUSCH configuration. Proposal 2 has the following Assumptions 1 and 2.

[0082] <Proposal 2 - Assumption 1> TDRAs for multiple CG PUSCH occasions in one CG period are indicated by individual SLIVs in one TDRA row.

[0083] Fig. 5 shows an example of a TDRA table. The TDRA table shown in Fig. 5 is semi-statically entered in a terminal using parameters such as RRC. As shown in Fig. 5, the TDRA table has multiple SLIVs for each row. The multiple SLIVs correspond to the SLIVs of multiple CG PUSCH occasions.

[0084] If the DCI (TDRA field) indicates a TDRA row index indicating one or more SLIVs, the UE verifies the DCI as an activated DCI for a Type 2 CG PUSCH. The UE determines multiple CG PUSCH occasions (e.g., slots) in one CG period based on the multiple SLIVs.

[0085] The terminal can verify the DCI as an activated DCI indicating a TDRA row index indicating multiple SLIVs, and when transmitting multiple CG PUSCH occasions based on multiple SLIVs in one CG period, it expects one or more of the following conditions to be met:

[0086] Condition 1: Dynamic indication of unused CG PUSCH occasions is enabled for Type 2 CG PUSCH configuration.

[0087] Condition 2: The physical priority of the Type 1 CG PUSCH setting is specified as either High or Low.

[0088] For example, "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH configuration is set to Low in the terminal.

[0089] For example, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "0." Alternatively, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "1."

[0090] Condition 3: Repetition (Type A or Type B) is not configured for Type 2 CG PUSCH configuration.

[0091] For example, "numberOfRepetitions" exists in the TDRA table, or "rep-K" is not set in "ConfiguredGrantConfig."

[0092] For example, if the activated DCI format is DCI 0_1 or DCI 0_2, "pusch-RepTypeIndicatorDCI-0-1" or "pusch-RepTypeIndicatorDCI-0-2" in "PUSCH-Config" is not set, or if the activated DCI format is DCI 0_1 or DCI 0_2, it is not set as "pusch-RepTypeA" or "pusch-RepTypeB".

[0093] "PUSCH-Config" is an information element used to configure terminal-specific PUSCH parameters applicable to a specific Band Width Part (BWP). "pusch-RepTypeIndicatorDCI-0-1" / "pusch-RepTypeIndicatorDCI-0-2" are parameters that indicate whether the terminal follows "Repetition type A" or "Repetition type B" operation for PUSCH scheduled with DCI format 0_1 / 0_2.

[0094] Condition 4: Multi-TPR transmission is not configured due to Type 2 CG PUSCH configuration.

[0095] For example, the value of the SRS resource set indicator field of the activated DCI indicates '00' or '01.' In other words, the value of the SRS resource set indicator field of the activated DCI indicates one certain TPR.

[0096] For example, "powerControlLoopToUse2" and / or "mappingPattern" are not set in "ConfiguredGrantConfig".

[0097] Note that "powerControlLoopToUse2" is a parameter related to a closed control loop applied to the second SRS resource set. "mappingPattern" is a parameter indicating whether the terminal should follow a cyclical mapping pattern or a sequential mapping pattern when two SRS resource sets are configured.

[0098] Condition 5: The period of the CG PUSCH is greater than X symbols. Alternatively, the period of the CG PUSCH is greater than the number of slots of the specified plurality of SLIVs. In other words, the period of the CG PUSCH is set so that the specified plurality of CG PUSCH occasions are transmitted within the CG period.

[0099] - Variation: The terminal may verify the DCI as an activated DCI if any one or more of the above conditions are not satisfied, and may transmit only one CG PUSCH occasion in one CG period based on the first or last SLIV.

[0100] <Proposal 2 - Assumption 2> The TDRA of multiple CG PUSCH occasions in one CG period is determined based on the TDRA of the first CG PUSCH occasion and the number of CG PUSCH occasions in one CG period. Assumption 2 of Proposal 2 is further divided into two assumptions 2-1 and 2-2.

[0101] <Proposal 2 - Assumption 2-1> The number of CG PUSCH occasions in one CG period is indicated by the activation DCI.

[0102] For example, the terminal expects the TDRA of the first CG PUSCH occasion and the number of the multiple CG PUSCH occasions based on the activated DCI, and determines the TDRA of CG PUSCH occasions after the first CG PUSCH occasion based on the TDRA of the first CG PUSCH occasion and the number of the multiple CG PUSCH occasions.

[0103] The terminal can verify the DCI as an activated DCI indicating the number of CG PUSCH occasions in one CG period, and when transmitting multiple CG PUSCH occasions based on one SLIV or the first SLIV of multiple SLIVs in one CG period, it expects that one or more of the following conditions are met:

[0104] Condition 1: Enabling multiple CG PUSCH occasions in one CG period is configured for Type 2 CG PUSCH configuration.

[0105] Condition 2: Dynamic indication of unused CG PUSCH occasions is enabled for Type 2 CG PUSCH configuration.

[0106] Condition 3: The physical priority of the Type 1 CG PUSCH setting is specified as either High or Low.

[0107] For example, "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH configuration is set to Low in the terminal.

[0108] For example, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "0." Alternatively, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "1."

[0109] Condition 4: Repetition (Type A or Type B) is not configured for Type 2 CG PUSCH configuration.

[0110] For example, "numberOfRepetitions" exists in the TDRA table, or "rep-K" is not set in "ConfiguredGrantConfig."

[0111] For example, if the activated DCI format is DCI 0_1 or DCI 0_2, "pusch-RepTypeIndicatorDCI-0-1" or "pusch-RepTypeIndicatorDCI-0-2" in "PUSCH-Config" is not set, or if the activated DCI format is DCI 0_1 or DCI 0_2, it is not set as "pusch-RepTypeA" or "pusch-RepTypeB".

[0112] Condition 5: Multi-TPR transmission is not configured due to Type 2 CG PUSCH configuration.

[0113] For example, the value of the SRS resource set indicator field of the activated DCI indicates '00' or '01.' In other words, the value of the SRS resource set indicator field of the activated DCI indicates one certain TPR.

[0114] For example, "powerControlLoopToUse2" and / or "mappingPattern" are not set in "ConfiguredGrantConfig".

[0115] Condition 6: The period of the CG PUSCH is greater than X symbols. Or, the period of the CG PUSCH is greater than the number of slots of the specified multiple SLIVs. In other words, the period of the CG PUSCH is set so that the specified multiple CG PUSCH occasions are transmitted within the CG period.

[0116] - Variation: The terminal may verify the DCI as an activated DCI if any one or more of the above conditions are not met, and may transmit only one CG PUSCH occasion in one CG period.

[0117] <Proposal 2 - Assumption 2-2> The number of CG PUSCH occasions in one CG period is indicated by the Type 2 CG PUSCH configuration. For example, the number of CG PUSCH occasions in one CG period is indicated by a parameter of higher layer signaling such as "ConfiguredGrantConfig".

[0118] When the number of CG PUSCH occasions in one CG period is set to "ConfiguredGrantConfig", the terminal expects that one or more of the following conditions are met.

[0119] Condition 1: Dynamic indication of unused CG PUSCH occasions is enabled for Type 2 CG PUSCH configuration.

[0120] Condition 2: The physical priority of the Type 1 CG PUSCH setting is specified as either High or Low.

[0121] For example, "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH configuration is set to Low in the terminal.

[0122] For example, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "0." Alternatively, the "phy-PriorityIndex" in the "ConfiguredGrantConfig" is not set as "1."

[0123] Condition 3: Repetition (Type A or Type B) is not configured for Type 2 CG PUSCH configuration.

[0124] For example, "numberOfRepetitions" exists in the TDRA table, or "rep-K" is not set in "ConfiguredGrantConfig."

[0125] For example, if the activated DCI format is DCI 0_1 or DCI 0_2, "pusch-RepTypeIndicatorDCI-0-1" or "pusch-RepTypeIndicatorDCI-0-2" in "PUSCH-Config" is not set, or if the activated DCI format is DCI 0_1 or DCI 0_2, it is not set as "pusch-RepTypeA" or "pusch-RepTypeB".

[0126] Condition 4: Multi-TPR transmission is not configured due to Type 2 CG PUSCH configuration.

[0127] For example, the value of the SRS resource set indicator field of the activated DCI indicates '00' or '01.' In other words, the value of the SRS resource set indicator field of the activated DCI indicates one certain TPR.

[0128] For example, "powerControlLoopToUse2" and / or "mappingPattern" are not set in "ConfiguredGrantConfig".

[0129] Condition 5: The period of the CG PUSCH is greater than X symbols. Alternatively, the period of the CG PUSCH is greater than the number of slots of the specified plurality of SLIVs. In other words, the period of the CG PUSCH is set so that the specified plurality of CG PUSCH occasions are transmitted within the CG period.

[0130] Modification: If one or more of the above conditions are not met, the terminal may transmit one CG PUSCH occasion in one CG period.

[0131] Summary of Proposal 2: A terminal determines each of multiple CG PUSCH occasions for a Type 2 CG PUSCH in one period based on an individual TDRA. This operation allows the terminal to appropriately configure multiple CG PUSCH occasions for high-capacity communication.

[0132] Furthermore, the terminal determines each of multiple CG PUSCH occasions for the Type 2 CG PUSCH in one period based on the TDRA of the first CG PUSCH occasion and the number of multiple CG PUSCH occasions. This operation allows the terminal to appropriately configure multiple CG PUSCH occasions for high-capacity communication.

[0133] <Proposal 3> Proposal 3 appropriately configures multiple CG PUSCH occasions in high-capacity communication by specifying restrictions on multiple CG PUSCH occasions in one CG period in Study 3. Proposal 3 may include Option 1 and Option 2.

[0134] <Proposal 3 - Option 1> If "rep-K" is set to the value K in "ConfiguredGrantConfig" and multiple PUSCH occasions are determined in one CG period for CG PUSCH configuration as described in Proposal 1 and Proposal 2, the terminal shall perform the following transmission operations of Alt. 1 to Alt. 3.

[0135] Furthermore, if "numberOfRepetitions" exists in the TDRA table and multiple PUSCH occasions are determined in one CG period for CG PUSCH configuration as described in Proposal 1 and Proposal 2, the terminal performs the following transmission operations of Alt.1 to Alt.3.

[0136] <Proposal 3 - Option 1 - Alt. 1> In Proposal 3 Alt. 1, joint operation of repetition and multiple CG PUSCH occasions is not allowed in one CG period, and multiple CG PUSCH occasions take priority over repetition.

[0137] For example, each of the multiple CG PUSCH occasions has only one repetition. For example, a terminal may transmit multiple CG PUSCH occasions in one CG period, with one repetition for each of the multiple CG PUSCH occasions.

[0138] <Proposal 3 - Option 1 - Alt. 2> Proposal 3, Option 2 allows joint operation of repetition and multiple CG PUSCH occasions within one CG period.

[0139] For example, each of the multiple CG PUSCH occasions has K repetitions. For example, a terminal transmits multiple CG PUSCH occasions in one CG period, and each of the multiple CG PUSCH occasions performs K repetitions. If the number of multiple CG PUSCH occasions is N, the terminal transmits the PUSCH N*K times in one CG period.

[0140] <Proposal 3 - Option 1 - Alt. 3> In Proposal 3 Alt. 3, joint operation of repetition and multiple CG PUSCH occasions is not allowed in one CG period, and repetition takes priority over multiple CG PUSCH occasions.

[0141] For example, one CG PUSCH occasion is transmitted in one CG period, and one CG PUSCH occasion has K repetitions. For example, a terminal transmits one CG PUSCH occasion in one CG period, and performs K repetitions for one CG PUSCH occasion.

[0142] Proposal 3 - Option 2 Proposal 3, Option 2 describes another possible variation of TDRA for multiple CG PUSCH occasions in one CG period.

[0143] Example 1: The number of CG PUSCH occasions in one slot is limited to a maximum of X.

[0144] Example 2: Multiple CG PUSCH occasions in one CG period are limited to a maximum of Y slots.

[0145] - Modifications The values ​​of X and / or Y may be defined by a specification. The values ​​of X and / or Y may be set by parameters of higher layer signaling such as RRC. The values ​​of X and / or Y may be reported by UE capability information.

[0146] The candidate values ​​of X and / or Y may depend on the frequency range (e.g., FR1, FR2-1, FR2-2) and / or the SCS (e.g., 15 / 30 / 60 / 120 / 240 / 960 kHz SCS) and / or the number of CG PUSCH configurations and / or the periodicity value of the CG PUSCH configurations.

[0147] Summary of Proposal 3: A terminal determines the CG PUSCH occasions in one period and the repetition of the CG PUSCH occasions based on parameters of higher layer signaling. This operation allows multiple CG PUSCH occasions to be appropriately configured for high-capacity communication.

[0148] Furthermore, for TDRA, the terminal limits the number of CG PUSCH occasions in one slot to a maximum of X. This operation allows multiple CG PUSCH occasions to be appropriately configured in high-capacity communications.

[0149] Furthermore, for TDRA, the terminal limits the number of CG PUSCH occasions in one CG period to a maximum of Y slots. This operation allows appropriate configuration of multiple CG PUSCH occasions in high-capacity communications.

[0150] <Modification> The terminal may dynamically update the number of CG PUSCH occasions in one CG period. The terminal may dynamically update TDRA for multiple CG PUSCH occasions in one CG period. The dynamic update may be performed by an existing DCI and / or a new DCI and / or an activated DCI and / or a MAC CE. MAC CE stands for Media Access Control Control Element.

[0151] Which proposals, options, and / or Alt. are used may be configured by parameters of higher layer signaling. Which proposals, options, and / or Alt. are used may be reported by the terminal as terminal capability information. Which proposals, options, and / or Alt. are used may be defined by a specification. Which proposals, options, and / or Alt. are used may be defined by a combination of parameters of higher layer signaling, terminal capability information, and a specification.

[0152] <Terminal Capabilities> The terminal may report the following terminal capability information to the base station: Information defining whether joint operation of PUSCH repetition and multiple CG PUSCH occasions in one CG period is supported Prerequisite features and / or capabilities for terminal capability of multiple CG PUSCH occasions in one CG period include one or more of the following: A single DCI (Rel-17 capability) to schedule multiple PUSCHs Multiple active configured grant configurations for the BWP of the serving cell Reporting of dynamic indication of unused CG PUSCH occasions via UCI

[0153] <Configuration of Base Station> Fig. 6 is a block diagram showing an example of the configuration of the base station 10. The base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. The base station 10 communicates with the terminal 20 (see Fig. 7) wirelessly.

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

[0155] 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 the terminal 20 (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.

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

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

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

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

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

[0161] 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 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the terminal 20.

[0162] The control unit 103 sets PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to PUCCH configuration such as a PUCCH cell timing pattern (PUCCH configuration information) may be notified to the terminal 20 by RRC.

[0163] 7 is a block diagram showing an example of the configuration of the terminal 20. The terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. The terminal 20 communicates with the base station 10, for example, wirelessly.

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

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

[0166] 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 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.

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

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

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

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

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

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

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

[0174] The control unit 203 determines whether to support multiple uplink signal occasions for the Type 1 CG PUSCH in one period based on parameters of higher layer signaling. For example, when "rrc-ConfiguredUplinkGrant" does not include "timeDomainAllocation" indicating multiple SLIVs, the control unit 203 determines not to support multiple uplink signal occasions for the Type 1 CG PUSCH in one period. When "rrc-ConfiguredUplinkGrant" includes "timeDomainAllocation" indicating multiple SLIVs, the control unit 203 determines to support multiple uplink signal occasions for the Type 1 CG PUSCH in one period.

[0175] When the control unit 203 decides not to support multiple uplink signal occasions for Type 1 CG PUSCH, it assumes that one or more of the conditions described in <Proposal 1 - Option 2> are met.

[0176] Furthermore, the control unit 203 determines the occasions of multiple uplink signals in one period based on the individual time resource allocation information. When the control unit 203 determines the occasions of multiple uplink signals in one period based on the individual time resource allocation information and transmits the occasions of multiple uplink signals, it is assumed that one or more of the conditions described in <Proposal 2 - Assumption 1> are satisfied.

[0177] Furthermore, the control unit 203 determines each of the multiple uplink signal occasions in one period based on one piece of time resource allocation information and the number of the multiple uplink signal occasions. The one piece of time resource allocation information may be resource allocation information for the first occasion of the multiple uplink signal occasions.

[0178] The number of CG PUSCH occasions in one CG period may be indicated by an activation DCI. In this case, the control unit 203 assumes that one or more of the conditions described in <Proposal 2 - Assumption 2-1> are satisfied. Also, the number of CG PUSCH occasions in one CG period is indicated by a Type 2 CG PUSCH configuration. In this case, the control unit 203 assumes that one or more of the conditions described in <Proposal 2 - Assumption 2-2> are satisfied.

[0179] Furthermore, the control unit 203 determines the occasion of the uplink signal in one period and the repetition of the occasion of the uplink signal based on parameters of higher layer signaling.

[0180] Furthermore, the control section 203 limits the number of CG PUSCH occasions in one slot to a maximum of X in determining the time resource allocation information.

[0181] Furthermore, in determining time resource allocation information, the control section 203 limits the number of CG PUSCH occasions in one CG period to a maximum of Y slots.

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

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

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

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

[0186] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 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.

[0187] Each function in the base station 10 and the terminal 20 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.

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

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

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

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

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

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

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

[0195] Furthermore, the base station 10 and the terminal 20 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, the processor 1001 may be implemented using at least one of these pieces of hardware.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0217] Furthermore, a 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, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 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.

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

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

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

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

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

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

[0224] The information service unit 12 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0261] 10 Base station 101 Transmitter 102 Receiver 103 Controller 20 Terminal 201 Receiver 202 Transmitter 203 Controller

Claims

1. a receiving unit for receiving information regarding a configuration of an uplink transmission; a control unit that determines not to perform repetition for an uplink transmission in the information when the information includes a parameter related to the number of slots of a transmission occasion of an uplink channel; A terminal having:

2. the receiving unit receives the information regarding a configuration of the uplink transmission of a Configured Grant (CG); The control unit determines not to perform repetition for the uplink transmission in the CG when the information includes the parameter related to the number of slots of the transmission occasion of the uplink channel within one period of the CG. The terminal according to claim 1 .

3. a transmitter for transmitting information regarding a maximum supportable number of slots of the transmission occasion; The terminal according to claim 1 .

4. a transmitter for transmitting information regarding uplink transmission configuration; a control unit that assumes that no repetition is performed on an uplink transmission in the information when the information includes a parameter related to the number of slots of a transmission occasion of an uplink channel; A base station having

5. a transmitter for transmitting information regarding uplink transmission configuration; a control unit that assumes that no repetition is performed on an uplink transmission in the information when the information includes a parameter related to the number of slots of a transmission occasion of an uplink channel; a base station having a receiving unit that receives the information; a control unit that determines not to perform repetition on uplink transmission in the information when the parameter is included in the information; a terminal having A wireless system having:

6. The device is receiving information regarding uplink transmission configuration; If the information includes a parameter relating to the number of slots of a transmission occasion of an uplink channel, determining not to perform repetition for the uplink transmission in the information; Communication method.