Terminals, base stations, wireless systems, and communication methods

Abstract

Provided is a terminal comprising a reception unit which receives a parameter of higher layer signaling and a control unit which determines, on the basis of the parameter of the higher layer signaling, an occasion of an uplink signal in one period and repetition in the occasion of the uplink signal.

Description

[Technical Field]

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

[0002] In Universal Mobile Telecommunication System (UMTS) networks, Long Term Evolution (LTE) has been standardized for the purposes of achieving higher data rates and lower latency. Furthermore, successor systems to LTE have been studied for the purpose of achieving wider bandwidth and higher speed than LTE. Successor systems to LTE include, for example, systems called 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 radio technologies and network architectures are being studied to satisfy the requirement of achieving a throughput of 10 Gbps or higher while reducing the latency of a radio section to 1 ms or less (for example, Non-Patent Document 1).

[0004] In NR, in Release 16, the configuration of CG PUSCH (Configured Grant Physical Uplink Shared Channel) is specified (for example, Non-Patent Document 2). CG PUSCH includes Type 1 CG PUSCH and Type 2 CG PUSCH.

[0005] Release 17 examines augmented reality (XR), including virtual reality (VR) and mixed reality (MX), and discusses XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. The target requirements for XR include considering aspects such as capacity, latency, mobility, and energy efficiency. [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS38.213 V16.3.0 (2020-09) [Non-Patent Document 2] 3GPP TS38.331 V16.2.0 (2020-09) [Overview of the project]

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

[0008] One aspect of this disclosure is to provide a terminal and a communication method for appropriately setting up multiple uplink signaling opportunities in high-capacity communication. [Means for solving the problem]

[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives parameters of higher layer signaling, and a control unit that determines the occasions of an uplink signal in a given period and the repetitions in the uplink signal occasions based on the parameters of the higher layer signaling.

[0010] A communication method according to one aspect of the present disclosure involves a terminal receiving parameters of higher layer signaling and determining the uplink signaling occasions and repetitions in the uplink signaling occasions during a given period, based on the parameters of the higher layer signaling. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of dual connectivity (DC). [Figure 2] This figure shows an example of PUCCH carrier switching. [Figure 3] This diagram shows the parameters for configurationGrantConfig. [Figure 4] This diagram shows the parameters for configurationGrantConfig. [Figure 5] This figure shows an example of a TDRA table. [Figure 6] This block diagram shows an example of the configuration of base station 10. [Figure 7] This is a block diagram showing an example of the configuration of terminal 20. [Figure 8] This figure shows an example of the hardware configuration of a base station and terminal according to this embodiment. [Figure 9] This is a diagram showing an example configuration of vehicle 2001. [Modes for carrying out the invention]

[0012] Hereinafter, an embodiment relating to one aspect of this disclosure will be described with reference to the drawings. In URLLC, enhancements to the terminal's feedback function for Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) are considered. HARQ-ACK is an example of information regarding acknowledgment (e.g., acknowledgment) for data received by the terminal. In response to these considerations for URLLC, it was agreed to support dynamic and semistatic PUCCH carrier switching. Note that PUCCH carrier switching may also be referred to by other names, such as carrier switching for transmitting control information.

[0013] PUCCH carrier switching is a technique applied when a base station communicates through multiple cells. Below, we will explain dual connectivity, which is an example of communication through multiple cells, and PUCCH carrier switching.

[0014] Dual connectivity Figure 1 shows an example of dual connectivity (DC). In the example in Figure 1, base station 10-1 may be a Master Node (MN), and base station 10-2 may be a Secondary Node (SN). As shown in the example in Figure 1, DC bundles carriers between different base stations.

[0015] In the example shown in Figure 1, base station 10-1 communicates with terminal 20 via primary cell (Pcell) and secondary cell (Scell). In the example shown in Figure 1, terminal 20 has established a Radio Resource Control (RRC) connection with base station 10-1.

[0016] In the case of DC, there may be a communication delay between the base station 10-1 and the base station 10-2. Therefore, it is difficult to notify the base station 10-2 of the uplink control information (e.g., Uplink Control Information: UCI) received on 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 the information in the scheduling of Scells under the control of the base station 10-2. Therefore, in DC, in addition to the Pcell of the base station 10-1, one carrier under the control of the base station 10-2 may be configured as a Primary Scell (PScell), and PUCCH transmission may be supported on the PScell. In this case, the terminal 20 transmits UCI to the base station 10-2 via the PScell.

[0017] In the example of Fig. 1, the terminal 20 configures a Scell in addition to a Pcell for the base station 10-1. Further, the terminal 20 configures a 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 via the PUCCH of the Pcell. Further, the terminal 20 transmits UCI of each carrier under the control of the base station 10-2 via 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).

[0018] When DC is performed, the terminal 20 may perform PUCCH transmission via the Pcell, the PScell, and / or a PUCCH-Scell. Generally, it is not assumed that the terminal 20 performs PUCCH transmission via a Scell other than the Pcell, the PScell, and the PUCCH-Scell.

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

[0020] Figure 2 is a diagram illustrating an example of PUCCH carrier switching. In the example of Figure 2, a base station and a terminal communicate via cell 1 and cell 2. In the example of Figure 2, cell 1 is a Pcell, and cell 2 is a Scell. Also, in the example of Figure 2, downlink (DL) slots and uplink (UL) slots in each cell are illustrated.

[0021] In the example of Figure 2, the terminal receives data at the timing of S101 (performs reception of a Physical Downlink Shared Channel (PDSCH)). The terminal attempts to transmit HARQ-ACK for the data received at S101 at the timing of S102, but at the timing of S102, the slot of cell 1 is a downlink (DL) slot. For this reason, when the terminal transmits HARQ-ACK on cell 1, the transmission of HARQ-ACK is suspended until the PUCCH transmission timing in an uplink (UL) slot (for example, the timing of S103 in Figure 2), so the latency of HARQ-ACK transmission increases. Note that the PUCCH transmission timing in an uplink (UL) slot may also be referred to as a PUCCH transmission opportunity.

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

[0023] In the following embodiments, "same timing" may mean exactly the same timing, or it may mean that all or part of the time resources (for example, one or more symbols (which may be resources with shorter time units than symbols) are the same or overlap) are the same.

[0024] PUCCH carrier switching refers to a situation where a terminal attempts to transmit a PUCCH at a specific transmission timing of a Pcell (which may be a PScell ​​or a PUCCH-Scell). Since the slot for that specific transmission timing of the Pcell (which may be a PScell ​​or a PUCCH-Scell) is a DL slot, the terminal may switch the cell that transmits the PUCCH from the Pcell (which may be a PScell ​​or a PUCCH-Scell) to one or more Scells whose slot for the same timing as the specific transmission timing is a UL slot (in the case of a PScell, it is an Scell ​​other than a PScell; in the case of a PUCCH-Scell, it is an Scell ​​other than a PUCCH-Scell). In the embodiments of the present invention, the unit of the specific transmission timing is not limited to slots. For example, the specific transmission timing may be a timing based on subframes, or a timing based on symbols.

[0025] Two methods are being considered to implement PUCCH carrier switching. The first method involves the base station dynamically instructing the terminal on the carrier for transmitting PUCCH. The second method involves the base station semi-statically setting the carrier for transmitting PUCCH for the terminal. In the following embodiment, "transmitting PUCCH" and "transmitting PUCCH" may also refer to transmitting uplink control information via PUCCH.

[0026] The terminal may notify the base station of terminal capability information (UE capability), which specifies information about the terminal's ability to transmit PUCCH signals.

[0027] For example, the terminal capability information of a terminal may include information indicating whether or not the terminal supports switching settings related to the transmission of control information. Switching settings related to the transmission of control information may, for example, involve switching the resources (e.g., carrier or cell) used to transmit the control information. Switching the resources used to transmit the control information may be referred to as "PUCCH carrier switching". Furthermore, the terminal capability information of a terminal may include information indicating the application of dynamic PUCCH carrier switching and / or semi-static PUCCH carrier switching.

[0028] The configuration operation for quasi-static PUCCH carrier switching may be based on the RRC (Rapid Relay Control) that sets the PUCCH cell timing pattern for the PUCCH cell to which quasi-static PUCCH carrier switching is applied. Furthermore, the configuration operation for quasi-static PUCCH carrier switching may be supported between cells of different neural networks.

[0029] In PUCCH carrier switching, PUCCH resource settings may be configured per UL BWP (Uplink Bandwidth Part) (for example, per candidate cell and per UL BWP of that candidate cell).

[0030] In the case of PUCCH carrier switching based on dynamic indication of control information, the K1 value (offset) from PDSCH to HARQ-ACK may be interpreted based on the numerology of the dynamically indicated target PUCCH cell. Note that the control information may be control information for scheduling PUCCH, such as Downlink control information (DCI). Further, numerology may be understood as a slot or Subcarrier Spacing (SCS).

[0031] In URLLC, enhancement of the HARQ-ACK Codebook (HARQ-ACK CB) feedback function of a terminal is under discussion. Hereinafter, an overview of Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB is described (refer to Non-Patent Document 1 for details).

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

[0033] ·Agreement Support dynamic indication of one or more unused CG PUSCH occasions by a terminal based on Uplink Control Information (UCI).

[0034] For example, when there is an unused CG PUSCH occasion, the terminal may use UCI to notify the unused CG PUSCH occasion.

[0035] ·Agreement Support multiple CG PUSCH occasions within a period of a single CG PUSCH configuration.

[0036] For example, if a terminal has multiple CG PUSCH settings, it may set multiple CG PUSCH occasions during the period of one of those CG PUSCH settings.

[0037] Note that "unused" may include "not used". CG PUSCH occasions may also be referred to as CG PUSCH transmission occasions. The period of CG PUSCH settings may be referred to as CG PUSCH period or CG period. The period may be periodic.

[0038] <CG PUSCH> As mentioned above, the NR (National Regulation) specifies the configuration of the CG PUSCH in Rel-16 (for example, Non-Patent Document 2). There are two types of CG PUSCH: Type 1 CG PUSCH and Type 2 CG PUSCH.

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

[0040] Type 2 CG PUSCH The transmission parameters for Type 2 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "activation DCI". Activation and deactivation of Type 2 CG PUSCH depend on RRC-configuration and DCI. One DCI can activate one CG PUSCH and deactivate multiple CG PUSCHs.

[0041] <CG PUSCH configurations> Figures 3 and 4 are diagrams showing parameters of configuredGrantConfig. The parameters shown in Figure 4 follow the parameters shown in Figure 3. The configuredGrantConfig parameters shown in Figures 3 and 4 are used to configure configured grant uplink transmissions.

[0042] <Activation DCI validation> In Rel-17, when the TDRA (time domain resource assignment or allocation) field of a 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, when the DCI indicates a plurality of SLIVs via the TDRA field, the terminal cannot validate the activation DCI. Note that the SLIV defines a starting symbol and the number of consecutive symbols.

[0043] <Analysis> As described above in <CG Enhancement for Rel-18 XR>, it has been agreed to support CG enhancement for Rel-18 XR. However, in high-capacity communication such as Rel-18 XR, there is room for the following consideration on the configuration of a plurality of CG PUSCH occasions in a single CG PUSCH configuration.

[0044] · Issue 1 Configurations related to Type 1 CG PUSCH

[0045] · Issue 2 Configurations related to Type 2 CG PUSCH and activation DCI validation As mentioned in <Verification of Activated DCI>, under the current specifications, the terminal cannot verify the activated DCI if the DCI indicates multiple SLIVs via the TDRA field.

[0046] • Consideration 3 Potential limitations on multiple CG PUSCH occasions within a single CG period.

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

[0048] <Proposal 1> Proposal 1 appropriately configures multiple CG PUSCH occasions in high-capacity communication by defining the settings related to Type 1 CG PUSCH in Study 1. Proposal 1 may have Option 1 and Option 2.

[0049] <Proposal 1 - Option 1> Option 1 of Proposal 1 does not support multiple CG PUSCH occasions within a single CG period for Type 1 CG PUSCH configuration.

[0050] Example 1 The terminal does not expect "timeDomainAllocation" within "rrc-ConfiguredUplinkGrant" to point to multiple SLIVs. "rrc-ConfiguredUplinkGrant" is an RRC parameter related to uplink permission settings, and "timeDomainAllocation" is a parameter related to the allocation of time resources.

[0051] Example 2 The terminal does not expect the RRC parameter, which indicates the number of CG PUSCH occasions in a single CG period, to be set for Type 1 CG PUSCH.

[0052] In the operation of Examples 1 and 2 described above, for example, the base station may control the enabling and disabling of multiple CG PUSCH occasions. Here, it is assumed that the terminal can handle multiple CG PUSCH occasions in Type 1 CG PUSCH.

[0053] When a base station disables the functionality of multiple CG push occasions in Type 1 CG push, it does not include "timeDomainAllocation" which directs multiple SLIVs in "rrc-ConfiguredUplinkGrant". Because the terminal does not include "timeDomainAllocation" which directs multiple SLIVs in "rrc-ConfiguredUplinkGrant", it does not support multiple CG push occasions.

[0054] Furthermore, the base station does not set the RRC parameter indicating the number of CG PUSCH occasions to 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 set for Type 1 CG PUSCH.

[0055] Furthermore, "expectation" may be reinterpreted as "assumption" or "decision." "Effective" and "ineffective" may be reinterpreted as "activation" and "deactivation."

[0056] <Proposal 1 - Option 2> Option 2 of Proposal 1 supports multiple CG PUSCH occasions within a single CG period for Type 1 CG PUSCH configuration.

[0057] Example 1 The terminal expects (supports) multiple CG PUSCH occasions within a single CG period if "timeDomainAllocation" in "rrc-ConfiguredUplinkGrant" indicates multiple SLIVs.

[0058] Example 2 The terminal expects (supports) multiple CG PUSCH occasions in a single CG period if the number of CG PUSCH occasions in a single CG period is set for Type 1 CG PUSCH.

[0059] In Example 1 or Example 2, if the terminal expects multiple CG PUSCH occasions, it expects one or more of the following conditions to be met. These conditions may also be described as states.

[0060] ·Condition 1 Dynamic instruction for unused CG PUSCH occasions is enabled for Type 1 CG PUSCH settings.

[0061] ·Condition 2 The physical priority of the Type 1 CG PUSCH setting is set to either High or Low.

[0062] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH setting on the device will be set to Low.

[0063] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "0", or the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "1".

[0064] ·Condition 3 Reputation (Type A or Type B) is not set for Type 1 CG PUSCH settings.

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

[0066] For example, "pusch-RepTypeIndicator" is not set to "rrc-ConfiguredUplinkGrant".

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

[0068] The "pusch-RepTypeIndicator" parameter indicates the type of repetition. Repetition type A can be interpreted as a form in which PUSCH assigned within a slot is repeatedly transmitted. In other words, PUSCH consists of 14 symbols or less and cannot be assigned across multiple slots (adjacent slots).

[0069] On the other hand, Repetition type B may be interpreted as repeated transmission of a PUSCH that may be assigned 15 or more PUSCH symbols. In this embodiment, it may be permitted to assign such a PUSCH across multiple slots.

[0070] ·Condition 4 Multi-TPR transmission is not configured for Type 1 CG PUSCH settings. TPR stands for Transmission and Reception Point.

[0071] For example, "pathlossReferenceIndex2" and / or "srs-ResourceIndicator2" and / or "precodingAndNumberOfLayers2" are not set in "rrc-ConfiguredUplinkGrant". In other words, the second SRS-related parameter is not set on the terminal. SRS stands for Sounding Reference Signal.

[0072] "pathlossReferenceIndex2" is a parameter that indicates the reference signal used as the PUSCH path loss reference for the second SRS resource set. "srs-ResourceIndicator2" is a parameter that indicates the SRS resource used for the second SRS resource set. "precodingAndNumberOfLayers2" is a parameter that indicates the precoding and number of layers for the second SRS resource set.

[0073] ·Condition 5 "cg-SDT-Configuration" is not configured in "rrc-ConfiguredUplinkGrant".

[0074] "cg-SDT-Configuration" is a parameter related to the SDT configuration. SDT stands for Small Data Transmission. SDT sends a CG PUSCH when RRC is inactive.

[0075] ·Condition 6 The CG PUSCH period is greater than the X symbol, or the CG PUSCH period is greater than the number of slots for the specified multiple SLIVs. In other words, the CG PUSCH period is set so that the configured multiple CG PUSCH occasions are sent within the CG period.

[0076] · Modification If one or more of the above conditions are not met, the terminal may send one CG PUSCH occasion during a single CG period.

[0077] <Summary of Proposal 1> The terminal determines, based on parameters of upper-layer signaling, whether to support multiple CG PUSCH occasions for Type 1 CG PUSCH within a single period. This operation allows the terminal to properly configure multiple CG PUSCH occasions in high-capacity communications.

[0078] <Proposal 2> Proposal 2 appropriately configures multiple CG PUSCH occasions in high-capacity communication by defining the settings related to Type 2 CG PUSCH and the verification of activated DCI as described in Consideration 2.

[0079] Proposal 2 supports multiple CG push occasions within a single CG period for a Type 2 CG push configuration. Proposal 2 has the following assumptions 1 and 2.

[0080] <Proposal 2 - Assumption 1> TDRAs for multiple CG PUSCH occasions within a single CG period are indicated by separate SLIVs in a single TDRA row.

[0081] Figure 5 shows an example of a TDRA table. The terminal quasi-statically enters the TDRA table shown in Figure 5 using parameters such as RRC. As shown in Figure 5, the TDRA table has multiple SLIVs for each row. These multiple SLIVs correspond to multiple CG PUSCH occasions.

[0082] The terminal validates a DCI (TDRA field) as an activated DCI for a Type 2 CG push if it indicates a TDRA row index that shows one or more SLIVs. Based on the multiple SLIVs, the terminal determines multiple CG push occasions (e.g., slots) within a single CG period.

[0083] The terminal can validate the DCI as an activated DCI that indicates a TDRA row index that indicates multiple SLIVs, and when sending multiple CG PUSCH occasions based on multiple SLIVs in a single CG period, it expects that one or more of the following conditions are met:

[0084] ·Condition 1 Dynamic instruction for unused CG PUSCH occasions is enabled for Type 2 CG PUSCH settings.

[0085] ·Condition 2 The physical priority of the Type 1 CG PUSCH setting is set to either High or Low.

[0086] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH setting on the device will be set to Low.

[0087] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "0", or the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "1".

[0088] ·Condition 3 Reputation (Type A or Type B) is not set for Type 2 CG PUSCH settings.

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

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

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

[0092] ·Condition 4 Multi-TPR transmission is not configured for Type 2 CG PUSCH settings.

[0093] 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 a certain TPR.

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

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

[0096] ·Condition 5 The CG PUSCH period is greater than the X symbol, or the CG PUSCH period is greater than the number of slots for the specified multiple SLIVs. In other words, the CG PUSCH period is set so that the configured multiple CG PUSCH occasions are sent within the CG period.

[0097] · Modification The terminal may verify the DCI as an activated DCI if any one or more of the above conditions are not met. The terminal may then send only one CG PUSCH occasion per CG period, based on the first or last SLIV.

[0098] <Proposal 2 - Assumption 2> The TDRA for multiple CG PUSCH occasions in a single CG period is determined based on the TDRA of the first CG PUSCH occasion and the number of CG PUSCH occasions in that CG period. Assumption 2 of Proposal 2 can be further divided into two assumptions 2-1 and 2-1.

[0099] <Proposal 2-Assumption 2-1> The number of CG PUSCH occasions in a single CG period is indicated by the activated DCI.

[0100] For example, the terminal expects the TDRA of the first CG PUSCH occasion and the number of subsequent CG PUSCH occasions based on the activated DCI. The terminal then determines the TDRA of subsequent CG PUSCH occasions based on the TDRA of the first CG PUSCH occasion and the number of subsequent CG PUSCH occasions.

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

[0102] ·Condition 1 Enabling multiple CG push occasions within a single CG period is configured for Type 2 CG push settings.

[0103] ·Condition 2 Dynamic instruction for unused CG PUSCH occasions is enabled for Type 2 CG PUSCH settings.

[0104] ·Condition 3 The physical priority of the Type 1 CG PUSCH setting is set to either High or Low.

[0105] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH setting on the device will be set to Low.

[0106] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "0", or the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "1".

[0107] ·Condition 4 Reputation (Type A or Type B) is not set for Type 2 CG PUSCH settings.

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

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

[0110] ·Condition 5 Multi-TPR transmission is not configured for Type 2 CG PUSCH settings.

[0111] 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 a certain TPR.

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

[0113] ·Condition 6 The CG PUSCH period is greater than the X symbol, or the CG PUSCH period is greater than the number of slots for the specified multiple SLIVs. In other words, the CG PUSCH period is set so that the configured multiple CG PUSCH occasions are sent within the CG period.

[0114] · Modification The terminal may verify a DCI as an activated DCI if any one or more of the above conditions are not met. The terminal may also transmit only one CG PUSCH occasion during a single CG period.

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

[0116] If the number of CG PUSCH occasions in a single CG period is set to "ConfiguredGrantConfig", the terminal expects one or more of the following conditions to be met:

[0117] ·Condition 1 Dynamic instruction for unused CG PUSCH occasions is enabled for Type 2 CG PUSCH settings.

[0118] ·Condition 2 The physical priority of the Type 1 CG PUSCH setting is set to either High or Low.

[0119] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set. In this case, the physical priority of the Type 1 CG PUSCH setting on the device will be set to Low.

[0120] For example, the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "0", or the "phy-PriorityIndex" in "ConfiguredGrantConfig" is not set to "1".

[0121] ·Condition 3 Reputation (Type A or Type B) is not set for Type 2 CG PUSCH settings.

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

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

[0124] ·Condition 4 Multi-TPR transmission is not configured for Type 2 CG PUSCH settings.

[0125] 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 a certain TPR.

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

[0127] ·Condition 5 The CG PUSCH period is greater than the X symbol, or the CG PUSCH period is greater than the number of slots for the specified multiple SLIVs. In other words, the CG PUSCH period is set so that the configured multiple CG PUSCH occasions are sent within the CG period.

[0128] · Modification If one or more of the above conditions are not met, the terminal may send one CG PUSCH occasion during a single CG period.

[0129] <Summary of Proposal 2> The terminal determines each of the multiple CG PUSCH occasions for Type 2 CG PUSCH within a single period based on individual TDRAs. This operation allows the terminal to properly configure multiple CG PUSCH occasions in high-capacity communication.

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

[0131] <Proposal 3> Proposal 3 appropriately configures multiple CG PUSCH occasions in high-capacity communication by defining restrictions on multiple CG PUSCH occasions within a single CG period as in Consideration 3. Proposal 3 may have Option 1 and Option 2.

[0132] <Proposal 3 - Option 1> If the terminal has "rep-K" set to value K in "ConfiguredGrantConfig" and determines multiple PUSCH occasions in one CG period for CG PUSCH configuration as described in Proposal 1 and Proposal 2, it performs the following Alt.1-Alt.3 transmission operations.

[0133] Furthermore, if the terminal has "numberOfRepetitions" in the TDRA table and determines multiple push occasions within a single CG period for CG push setting, as described in Proposal 1 and Proposal 2, it performs the following Alt.1-Alt.3 transmission operations.

[0134] <Proposal 3 - Option 1 - Alt.1> In Proposal 3, Alt.1, joint operation between a repetition and multiple CG push occasions is not permitted within a single CG period, and multiple CG push occasions take precedence over repetition.

[0135] For example, each of multiple CG PUSCH occasions has only one repetition. For example, a terminal sends multiple CG PUSCH occasions during a single CG period, and each of the multiple CG PUSCH occasions performs one repetition.

[0136] <Proposal 3 - Option 1 - Alt.2> In Proposal 3, Alt.2 allows for joint operation between repetition and multiple CG push occasions within a single CG period.

[0137] For example, each of the multiple CG PUSCH occasions has K repetitions. For example, a terminal sends 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 sends N*K PUSCH messages in one CG period.

[0138] <Proposal 3 - Option 1 - Alt.3> In Proposal 3, Alt.3, joint operation between a repetition and multiple CG push occasions is not permitted within a single CG period, and the repetition takes precedence over multiple CG push occasions.

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

[0140] <Proposal 3 - Option 2> Option 2 of Proposal 3 describes other possible variations of TDRA for multiple CG PUSCH occasions within a single CG period.

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

[0142] Example 2 The number of CG PUSCH occasions within a single CG period is limited to a maximum of Y slots.

[0143] · Modification The values ​​of X and / or Y may be defined by the 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.

[0144] Candidate values ​​for 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 / 960kHz SCS) and / or the number of CG PUSCH settings and / or the periodicity value of the CG PUSCH settings.

[0145] <Summary of Proposal 3> The terminal determines the CG PUSCH occasions and repetitions within each CG PUSCH occasion based on parameters from higher-layer signaling. This operation appropriately configures multiple CG PUSCH occasions in high-capacity communication.

[0146] Furthermore, with respect to TDRA, the terminal limits the number of CG PUSCH occasions in a single slot to a maximum of X. This operation allows for the proper configuration of multiple CG PUSCH occasions in high-capacity communication.

[0147] Furthermore, with respect to TDRA, the terminal limits the number of CG PUSCH occasions within a single CG period to a maximum of Y slots. This operation allows for the proper configuration of multiple CG PUSCH occasions in high-capacity communication.

[0148] <Variation> The terminal may dynamically update the number of CG PUSCH occasions in a single CG period. The terminal may dynamically update the TDRA for multiple CG PUSCH occasions in a single CG period. Dynamic updates may be performed by existing DCIs and / or new DCIs and / or activated DCIs and / or MAC CEs. MAC CE stands for Media Access Control Control Element.

[0149] Which proposals, options, and / or Alts are used may be determined by parameters in the higher-layer signaling. Which proposals, options, and / or Alts are used may be reported by the terminal as terminal capability information. Which proposals, options, and / or Alts are used may be defined by the specification. Which proposals, options, and / or Alts are used may be defined by a combination of parameters in the higher-layer signaling, terminal capability information, and the specification.

[0150] <Terminal Capabilities> The terminal may report the following terminal capability information to the base station. • Information defining whether joint operation between a PUSCH repetition and multiple CG PUSCH occasions is supported within a single CG period. • The prerequisite functions and / or capabilities for terminal capabilities of multiple CG PUSCH occasions in a single CG period include one or more of the following: A single DCI (Rel-17 capability) that schedules multiple pushes. Multiple active configured grant configurations for the Serving Cell's BWP. • Report by the UCI on the dynamic display of unused CG PUSCH occasions

[0151] <Base station configuration> Figure 6 is a block diagram showing an example of the configuration of a 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 Figure 7) wirelessly.

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

[0153] The DL signal may include, for example, data signals for the downlink and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating the scheduling of signal transmission by terminal 20 (e.g., UL grant). Furthermore, the DL signal may include control information from higher layers (e.g., Radio Resource Control (RRC) control information). Finally, the DL signal may include a reference signal.

[0154] The channels used to transmit 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, base station 10 transmits control information to terminal 20 using the PDCCH and transmits downlink data signals using the PDSCH.

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

[0156] The receiving unit 102 receives the 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.

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

[0158] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 101. The control unit 103 also outputs the data and control information received from the reception unit 102 to the upper layer.

[0159] 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 received from terminal 20 (e.g., data and control information, etc.) and / or data and control information, etc. acquired from higher layers. Information regarding the allocated resources may be included in the control information transmitted to terminal 20.

[0160] The control unit 103 sets the PUCCH resource as an example of resource allocation for sending and receiving UL signals. Information regarding PUCCH settings, such as the PUCCH cell timing pattern (PUCCH setting information), may be notified to the terminal 20 by RRC.

[0161] <Device Configuration> Figure 7 is a block diagram showing an example configuration of terminal 20. Terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. Terminal 20 communicates with, for example, a base station 10 wirelessly.

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

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

[0164] The UL signal may include, for example, data signals for the uplink and control information (e.g., UCI). It may also include, for example, information regarding the processing capability of terminal 20 (e.g., UE capability). Furthermore, the UL signal may include reference signals.

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

[0166] 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, reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (e.g., PUSCH).

[0167] The control unit 203 controls the communication operation of the terminal 20, including the receiving process in the receiving unit 201 and the transmission process in the transmitting unit 202.

[0168] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmission unit 202. The control unit 203 also outputs data and control information received from the receiving unit 201 to the upper layer.

[0169] For example, the control unit 203 controls the 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, a 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 the UCI. The UCI is transmitted using the PUCCH resource.

[0170] The control unit 203 configures the PUCCH resource based on the configuration information received from the base station 10 (for example, configuration information such as the PUCCH cell timing pattern notified by the RRC and / or DCI). The control unit 203 determines the PUCCH resource to be used to transmit the information to be fed back to the base station 10. The transmission unit 202, under the control of the control unit 203, transmits the information to be fed back to the base station 10 using the PUCCH resource determined by the control unit 203.

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

[0172] The control unit 203 determines whether to support multiple uplink occasions for Type 1 CG PUSCH in a single period based on the parameters of the upper-layer signaling. For example, if "rrc-ConfiguredUplinkGrant" does not include "timeDomainAllocation" which indicates multiple SLIVs, the control unit 203 decides not to support multiple uplink occasions for Type 1 CG PUSCH in a single period. If "rrc-ConfiguredUplinkGrant" includes "timeDomainAllocation" which indicates multiple SLIVs, the control unit 203 decides to support multiple uplink occasions for Type 1 CG PUSCH in a single period.

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

[0174] Furthermore, the control unit 203 determines each of the multiple uplink signal occasions in a single period based on individual time resource allocation information. The control unit 203 determines each of the multiple uplink signal occasions in a single period based on individual time resource allocation information, and when transmitting multiple uplink signal occasions, it assumes that one or more of the conditions described in <Proposal 2-Assumption 1> are met.

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

[0176] The number of CG PUSCH occasions in a single CG period may be indicated by the activated DCI. In this case, the control unit 203 assumes that one or more of the conditions described in <Proposal 2-Assumption 2-1> are met. Alternatively, the number of CG PUSCH occasions in a single CG period may be indicated by the Type 2 CG PUSCH setting. In this case, the control unit 203 assumes that one or more of the conditions described in <Proposal 2-Assumption 2-2> are met.

[0177] Furthermore, the control unit 203 determines the occasions for the uplink signal during a given period and the repetitions for those occasions based on the parameters of the higher-layer signaling.

[0178] Furthermore, regarding the determination of time resource allocation information, the control unit 203 limits the number of CG PUSCH occasions in one slot to a maximum of X.

[0179] Furthermore, regarding the determination of time resource allocation information, the control unit 203 limits the number of CG PUSCH occasions in a single CG period to a maximum of Y slots.

[0180] This concludes the explanation of this disclosure. The division of items in the above explanation is not essential to this disclosure, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other).

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

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

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

[0184] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0185] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or control at least one of reading and writing data to the memory 1002 and storage 1003.

[0186] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 103 and control unit 203 described above may be implemented by the processor 1001.

[0187] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. 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 other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

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

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

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

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

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

[0193] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

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

[0195] <Applicable Systems> The embodiments described herein may apply to systems utilizing LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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 (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as to at least one of the next-generation systems that are extended, modified, created, or defined based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

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

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

[0198] <Input / Output Direction> Information, etc. (see the section on <Information, Signals>) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

[0199] <Handling of input / output information, etc.> Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

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

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

[0202] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

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

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

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

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

[0207] <Systems, Networks> The terms “system” and “network” as used in this disclosure are interchangeable.

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

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

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

[0211] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may 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 all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

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

[0213] 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 several other appropriate terms.

[0214] <Base station / mobile station> At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do 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.

[0215] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the embodiments of this 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), V2X (Vehicle-to-Everything), etc.). In this case, the terminal 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0216] Similarly, the term "terminal" in this disclosure may be replaced with "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0217] Figure 9 shows an example of the configuration of vehicle 2001. As shown in Figure 9, vehicle 2001 comprises 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-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

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

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

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

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

[0222] The information service unit 12 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) or output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0223] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, 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. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

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

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

[0227] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, it outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013).

[0228] Furthermore, the communication module 2013 stores various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in 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, axles 2009, sensors 2021-2029, etc., which are provided in the vehicle 2001.

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

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

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

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

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

[0234] <Means> In the configuration of each of the above devices, "means" may be replaced with "unit", "circuit", "device", or the like.

[0235] <Open format> In the present disclosure, when "include", "including", and variations thereof are used, these terms are intended to be inclusive in the same manner as the term "comprising". Further, the term "or" as used in the present disclosure is not intended to be an exclusive OR.

[0236] <Time units such as TTI, frequency units such as RB, radio frame configuration> A radio frame may be configured by one or more frames in the time domain. Each of one or more frames in the time domain may be referred to as a subframe. A subframe may further be configured by one or more slots in the time domain. A subframe may have a fixed time length that does not depend on numerology (e.g., 1 ms).

[0237] Numerology may be a communication parameter applied to at least one of transmission and / or reception of a certain signal or channel. Numerology may indicate at least one of, for example: subcarrier spacing (SCS: SubCarrier Spacing), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI: Transmission Time Interval), the number of symbols per TTI, radio frame configuration, a specific filtering process performed by a transmitter / receiver in the frequency domain, and a specific windowing process performed by a transmitter / receiver in the time domain.

[0238] A slot may consist of one or more symbols in the time domain (such as OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A slot may also be a time unit based on neurology.

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

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

[0241] 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 mini-slot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, mini-slot, etc., instead of a subframe.

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

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

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

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

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

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

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

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

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

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

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

[0253] At least one of the configured BWPs may be active, and the UE need not assume that it transmits and receives a predetermined signal / channel outside the active BWP. Note that terms such as "cell" and "carrier" in the present disclosure may be replaced with "BWP".

[0254] The structures of the above-described radio frames, subframes, slots, minislots, symbols and the like are merely examples. For example, configurations including 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 length of a cyclic prefix (CP: Cyclic Prefix), and the like can be variously changed.

[0255] <Maximum Transmission Power> The "maximum transmit power" described in the present disclosure may mean a maximum value of transmit power, may mean the nominal UE maximum transmit power, or may mean the rated UE maximum transmit power.

[0256] <Articles> In the present disclosure, when articles are added through translation, such as a, an and the in English, the present disclosure may encompass that the nouns following these articles are in plural form.

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

[0258] One aspect of this disclosure is useful for wireless communication systems. [Explanation of Symbols]

[0259] 10 base station 101 Transmitter 102 Receiving Unit 103 Control Unit 20 devices 201 Receiving Unit 202 Transmitter 203 Control Unit

Claims

1. A transmitter unit that transmits information about the maximum number of supportable slots for transmission occasions on the upchannel, A receiving unit that receives parameters relating to the number of transmission occasion slots in the uplink channel, A terminal.

2. The transmitting unit transmits information regarding the maximum number of supported slots for transmission occasions on the upchannel of the Configured Grant (CG), The receiving unit receives parameters relating to the number of transmission occasion slots in the upchannel of the CG. The terminal according to claim 1.

3. The aforementioned parameters are included in the information regarding the uplink transmission settings for Configured Grant (CG), The receiving unit receives the parameters via the information. The terminal according to claim 1.

4. A receiver that receives information about the maximum number of supported slots for transmission occasions on the uplink channel, A transmission unit that transmits parameters relating to the number of transmission occasion slots in the uplink channel, A base station having

5. A transmitter unit that transmits information about the maximum number of supportable slots for transmission occasions on the upchannel, A receiving unit that receives parameters relating to the number of transmission occasion slots in the uplink channel, A terminal having, A receiving unit that receives the aforementioned information, A transmission unit that transmits the aforementioned parameters, A base station having, A wireless system having

6. The device, It transmits information about the maximum number of supportable slots for transmit occasions on the uplink channel. The parameters relating to the number of transmission occasion slots in the uplink channel are received. Communication method.

Images