JP7733117B2 - Terminal and wireless communication method - Google Patents

Description

The present disclosure relates to a terminal and a wireless communication method.

Long Term Evolution (LTE) has been specified for Universal Mobile Telecommunication System (UMTS) networks, aiming to achieve even higher data rates and lower latency. Successor systems to LTE are also being considered, aiming to achieve even wider bandwidth and faster speeds 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).

In 5G, various wireless technologies and network architectures are being considered to meet the requirements of achieving a throughput of 10 Gbps or more while keeping wireless section latency to 1 ms or less (for example, non-patent document 1).

In NR, Release 16 specifies the configuration of the Configured Grant Physical Uplink Scheduling Channel (CG PUSCH) (see, for example, Non-Patent Document 2). CG PUSCH is divided into Type 1 CG PUSCH and Type 2 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).

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

In addition, Release 16 of NR specifies the configuration of the Semi-Persistent Scheduling Downlink Shared Channel (SPS PDSCH) (see, for example, Non-Patent Document 2). The transmission parameters of the SPS PDSCH are provided by "sps-Config" and "Activation DCI." Activation and deactivation of the SPS PDSCH depend on the DCI.

In NR Release 17, various technologies are being considered for systems known as Ultra-Reliable and Low Latency Communications (URLLC) and the Industrial Internet of Things (IIoT).

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

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

There is room for consideration regarding SPS PDSCH communication in high-volume communications such as XR.

One aspect of the present disclosure is to provide a terminal and a wireless communication method for performing SPS PDSCH communication, which is suitable for high-capacity communications.

A terminal according to one aspect of the present disclosure has a control unit that sets a receiving period for a downlink signal based on period setting information, and a receiving unit that receives the downlink signal for each receiving period using multiple downlink channels.

A wireless communication method according to one aspect of the present disclosure sets a reception period for a downlink signal based on period setting information, and receives the downlink signal for each reception period using multiple downlink channels.

FIG. 1 is a diagram illustrating an example of dual connectivity (DC). FIG. 10 is a diagram illustrating an example of PUCCH carrier switching. FIG. 1 is a diagram illustrating an overview of Type 1 HARQ-ACK CB. FIG. 1 is a diagram illustrating an overview of Type 2 HARQ-ACK CB. FIG. 10 is a diagram illustrating an example of generating a Type 1 HARQ-ACK CB. FIG. 10 is a diagram illustrating an example of generating a Type 1 HARQ-ACK CB. FIG. 10 is a diagram illustrating an example of generating a Type 1 HARQ-ACK CB. FIG. 10 is a diagram illustrating an example of determining candidate PDSCH reception opportunities in Step A-2. FIG. 10 is a diagram illustrating an example of HARQ-ACK ordering in Type 1 HARQ-ACK CB of SPS PDSCH. FIG. 10 is a diagram illustrating an example of a CG PUSCH. FIG. 10 is a diagram illustrating an example of an SPS PDSCH. FIG. 10 is a diagram illustrating an example of TDRA settings. FIG. 10 is a diagram showing an example of multiple SLIVs in a TDRA table. FIG. 10 is a diagram illustrating an example of Alt.1-1. FIG. 10 is a diagram illustrating an example of Alt.1-2A. FIG. 10 is a diagram illustrating an example of Alt.1-2B-1. FIG. 10 is a diagram illustrating an example of Alt.1-2B-2. FIG. 10 is a diagram illustrating an example of Alt.1-2B-3. FIG. 10 is a diagram illustrating an example of Alt.2-1. FIG. 10 is a diagram illustrating an example of Alt.2-2. 10 is a diagram illustrating an example of HARQ-ACK ordering in Type 1 HARQ-ACK CB for multiple PDSCHs. FIG. 10 is a diagram illustrating an example of a candidate PDSCH reception opportunity. FIG. 10 is a diagram illustrating an example of an extended PDSCH slot set. FIG. 10 is a diagram illustrating an example of an extension of SLIV. FIG. 10 is a diagram illustrating an example of an extension of SLIV. FIG. 2 is a block diagram showing an example of the configuration of a base station according to the present embodiment. FIG. 2 is a block diagram showing an example of the configuration of a terminal according to the present embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment of the present disclosure.

An embodiment according to one aspect of the present disclosure will be described below 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 acknowledgment (e.g., an acknowledgement) for data received by a terminal. In response to these URLLC considerations, it has been agreed that dynamic and semi-static PUCCH carrier switching will be supported. Note that PUCCH carrier switching may also be referred to by other names, such as carrier switching for transmitting control information.

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

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

In the example of Figure 1, base station 10-1 communicates with terminal 20 via a primary cell (Pcell) and a secondary cell (Scell). In the example of Figure 1, terminal 20 establishes an RRC connection with base station 10-1.

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

In the example of Figure 1, the terminal 20 configures an Scell in addition to a Pcell for the base station 10-1. Also, the terminal 20 configures an Scell in addition to a PScell for the base station 10-2. The terminal 20 transmits the UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. Also, the terminal 20 transmits the UCI of each carrier under the control of the base station 10-2 on the PUCCH of the PScell. In the example of Figure 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).

When DC is being performed, terminal 20 may transmit PUCCH via Pcell, PScell, and/or PUCCH-Scell. Generally, it is not expected that terminal 20 will transmit PUCCH via Scell other than Pcell, PScell, and PUCCH-Scell.

<PUCCH carrier switching>
PUCCH carrier switching is being considered as a method to reduce the latency of HARQ-ACK feedback in Time Division Duplex (TDD) systems.

Figure 2 shows 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 an Scell. The example of Figure 2 also shows the downlink (DL) slots and uplink (UL) slots in each cell.

In the example of Figure 2, the terminal receives data at timing S101 (receives the 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 for 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 Figure 2), thereby increasing the latency of the HARQ-ACK transmission. The transmission timing of the PUCCH in the uplink (UL) slot may also be referred to as a PUCCH transmission opportunity.

In the example of Figure 2, at timing S102, the slot for cell 2 is the UL slot. In the example of Figure 2, if the terminal can transmit a HARQ-ACK for the data received in S101 during the PUCCH transmission opportunity at timing S102 for 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.

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

PUCCH carrier switching may refer to the terminal switching 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 the case of a PScell, an Scell other than the PScell; in the case of a PUCCH-Scell, an Scell other than the PUCCH-Scell) in which the slot with the same timing as the specific transmission timing is an UL slot, when the terminal attempts to transmit the PUCCH at a specific transmission timing of the Pcell (which may be a PScell or a PUCCH-Scell), because the slot with the specific transmission timing of the Pcell (which may be a PScell or a PUCCH-Scell) is a DL slot. Note that in 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 in units of subframes or symbols.

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

The terminal may notify the base station of terminal capability information (UE capability), which specifies information regarding the terminal's capabilities regarding PUCCH transmission.

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

The configuration operation for quasi-static PUCCH carrier switching may be based on the RRC that configured the PUCCH cell timing pattern of the PUCCH cell to which quasi-static PUCCH carrier switching applies. Furthermore, the configuration operation for quasi-static PUCCH carrier switching may be supported between cells of different numerologies.

When switching PUCCH carriers, PUCCH resources may be configured per UL BWP (Uplink Bandwidth Part) (e.g., per candidate cell and the UL BWP of that candidate cell).

In the case of PUCCH carrier switching based on dynamic instruction in 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). Numerology may also be considered as slots or Subcarrier Spacing (SCS).

In URLLC, enhancements to the terminal's HARQ-ACK Codebook (HARQ-ACK CB) feedback functionality are being considered. Below, we provide an overview of Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB (see Non-Patent Document 1 for details).

Note that Type 1 HARQ-ACK CB may also be referred to as semi-static HARQ-ACK CB. Type 2 HARQ-ACK CB may also be referred to as dynamic HARQ-ACK CB. The terminal may be instructed by higher layer signaling, such as RRC, which of Type 1 HARQ-ACK CB or Type 2 HARQ-ACK CB to apply.

<Type 1 HARQ-ACK CB>
3 is a diagram illustrating an overview of Type 1 HARQ-ACK CB. "Scheduled" in FIG. 3 indicates, for example, a slot scheduled by DCI. CC indicates Component Carrier.

In Type 1 HARQ-ACK CB, the terminal generates a HARQ-ACK bit for the PDSCH regardless of whether a scheduled slot (PDSCH) exists. For example, the terminal may set a NACK for an unscheduled PDSCH, as shown in the "HARQ-ACK codebook" in Figure 3.

<Type 2 HARQ-ACK CB>
Figure 4 is a diagram illustrating an overview of Type 2 HARQ-ACK CB. (x, y) in Figure 4 indicates, for example, a slot scheduled by DCI. x corresponds to the C-DAI value, and y corresponds to the T-DAI value. DAI stands for Downlink Assignment Index. DAI indicates, for example, the allocation of a scheduled PDSCH in which HARQ-ACK is bundled in the HARQ-ACK CB.

In Type 2 HARQ-ACK CB, the terminal generates a HARQ-ACK bit for the scheduled PDSCH. For example, the terminal may configure HARQ-ACK for the scheduled PDSCH as shown in the "HARQ-ACK codebook" in Figure 4.

Note that C-DAI counts up from 1. For example, in the case of a 2-bit field, C-DAI repeats 1->2->3->0->... C-DAI is counted up for each slot at each opportunity to receive DCI for each CC, and even if the slot changes, it counts up from the final value of the previous slot. T-DAI indicates the final value of C-DAI for each slot.

Next, we will explain an example of generating a Type 1 HARQ-ACK CB.

<Type 1 HARQ-ACK CB generation>
Figures 5, 6, and 7 are diagrams illustrating an example of generating a Type 1 HARQ-ACK CB. In Figure 5, it is assumed that the numerology of the serving cell and the numerology of the PUCCH cell are the same. In Figure 5, the set of K1 (offset from PDSCH to HARQ-ACK) is {1, 2, 3, 4}.

In Figure 6, it is assumed that the numerology of the serving cell and the numerology of the PUCCH cell are different. In Figure 6, the set of K1 is {1, 2, 3, 4, 5}.

The terminal may generate a HARQ-ACK CB based on Step A, Step A-1, Step A-2, and Step B below.

・Step A
The terminal determines a HARQ-ACK occasion for a candidate PDSCH reception. For example, the terminal determines slot n+4 of the PUCCH cell in FIG. 5. For example, the terminal determines slot n+5 of the PUCCH cell in FIG. 6.

・Step A-1
The terminal determines the PDSCH slot window based on the K1 set. For example, the terminal interprets the K1 set in the numerology of the PUCCH cell and determines the PDSCH slot window shown in the dotted frame in FIG. 5 or FIG. 6.

・Step A-2
For each K1, the terminal determines candidate PDSCH reception occasions in each slot. For example, the terminal determines candidate PDSCH reception occasions in each slot as shown in _FIG .

Note that candidate PDSCH reception opportunities, as explained in Figure 8, are associated with a set RI (Row index) in the Time Domain Resource Allocation (TDRA) table. Candidate PDSCH reception opportunities in the TDRA table that overlap with the UL configured by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated are excluded. For candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on specific rules.

・Step B
The terminal may determine (generate) a HARQ-ACK (HARQ-ACK information bit, HARQ-ACK CB) for each element of the determined candidate PDSCH reception opportunity. For example, the terminal may generate the following Type 1 HARQ-ACK CB for a total number of HARQ-ACK information bits of 0 ^ACK :

Figure 8 is a diagram explaining an example of determining candidate PDSCH reception opportunities in Step A-2. The table shown in the upper left of Figure 8 shows an example of TDRA. K0 indicates the offset between the DCI slot and the PDSCH slot. Start indicates the start symbol within the slot, and Length indicates the length from Start (the number of symbols allocated to the PDSCH). Mapping Type relates to the mapping type, which includes information about the symbol that can be set as the start symbol of the PDSCH within the slot.

The slot format is shown in the upper right corner of Figure 8. In the example slot format shown in Figure 8, the last two symbols are quasi-statically configured as UL.

The candidate PDSCH reception opportunities based on RI 0-8 of the TDRA shown in the upper left of Figure 8 are as shown in the upper right of Figure 8. However, candidate PDSCH reception opportunities in the TDRA table that overlap with the UL are excluded.

Therefore, candidate PDSCH reception opportunities for RI2, RI3, and RI8 that overlap with the UL are excluded, and the candidate PDSCH reception opportunities in a certain slot are as shown in the lower right of Figure 8. In other words, HARQ-ACKs for RI2, RI3, and RI8 are excluded from the generation set of HARQ-ACK CB.

For candidate PDSCH reception opportunities that overlap in the time domain, the candidate PDSCH reception opportunities are determined based on a specific rule. Therefore, the final candidate PDSCH reception opportunities are as shown in the lower left of Figure 8, and M _A,c in a certain slot is M _A,c = {0, 1, 2, 3}.

Next, an example of generating an SPS HARQ-ACK CB will be described. Note that the SPS HARQ-ACK CB may be considered as the CB of the HARQ-ACK in the SPS PDSCH. For example, the transmission period of the SPS PDSCH is set by RRC. Also, the transmission timing (K1) of the HARQ-ACK for the SPS PDSCH is set by RRC, for example. The SPS PDSCH is activated and deactivated, for example, by DCI. Below, DCI that deactivates the SPS PDSCH may be referred to as deactivation DCI. The terminal also transmits a HARQ-ACK in response to a deactivation DCI.

<HARQ-ACK order>
In Type 1 HARQ-ACK CB with SPS PDSCH reception only, HARQ-ACK may be ordered as follows:

Figure 9 illustrates an example of HARQ-ACK ordering in Type 1 HARQ-ACK CB for SPS PDSCH. HARQ-ACKs for SPS PDSCH are sorted in ascending order of DL slot number for each SPS configuration index for each serving cell index. Then, HARQ-ACKs for SPS PDSCH are sorted in ascending order of SPS configuration index for each serving cell index. Then, HARQ-ACKs for SPS PDSCH are sorted in ascending order of serving cell index.

In Type 2 HARQ-ACK CB for SPS PDSCH reception, HARQ-ACKs may be ordered in the same way as in the Type 1 HARQ-ACK CB described above. Note that in Type 2 HARQ-ACK CB, when the HARQ-ACK for SPS PDSCH reception is multiplexed with the HARQ-ACK for dynamically scheduled PDSCH reception and/or the HARQ-ACK for deactivation DCI, the HARQ-ACK (bit) for SPS PDSCH reception is added following (contiguous in time) the HARQ-ACK (bit) for dynamically scheduled PDSCH reception and/or the HARQ-ACK (bit) for deactivation DCI.

<Analysis>
As described above, Release 17 considers XR and specifies that the target requirements for XR are to take into account capacity, latency, mobility, and energy saving. Therefore, it is assumed that SPS PDSCH and/or CG PUSCH will be applied to XR services, and that multiple SPSs and/or multiple CGs will be used for one XR packet transmission.

However, the current SPS PDSCH and CG PUSCH may not be able to adequately support XR services. For example, they may not be able to adequately support XR services with larger payload sizes.

For example, it is specified that one SPS PDSCH is transmitted in a set SPS transmission cycle (reception cycle in the terminal, hereinafter simply referred to as the SPS cycle). Therefore, the current SPS PDSCH may not be able to adequately support XR services. In this embodiment, the terminal receives multiple SPS PDSCHs in an SPS cycle (for each SPS cycle). In this embodiment, the terminal appropriately processes HARQ-ACK CB when receiving multiple SPS PDSCHs in an SPS cycle.

In addition, for CG PUSCH, multiple PUSCH transmissions are specified in each CG period (grant period). However, the current CG PUSCH lacks flexibility and may not be able to adequately support XR services.

Figure 10 is a diagram illustrating an example of CG PUSCH. The parameters cg-nrofSlots and cg-nrofPUSCH-InSlot are provided to the terminal by a higher layer. cg-nrofSlots indicates the number of consecutive slots allocated in the configured CG cycle. cg-nrofPUSCH-InSlot indicates the number of consecutive PUSCH allocations within a slot. Figure 10 shows an example where cg-nrofSlots = 3 and cg-nrofSlots = 2. The CG period (the period in which the CG PUSCH is transmitted, for example, the 3 slots shown in Figure 10) is repeated in the configured CG cycle.

The first PUSCH allocation is based on higher layer configuration per TDRA or TS38.321 for Type 1 CG PUSCH. Alternatively, the first PUSCH allocation is based on the UL grant received in the DCI for Type 2 CG PUSCH. The remaining PUSCH allocations have the same length and mapping type as the first PUSCH. Each PUSCH is added without gaps after the previous PUSCH.

However, the current CG PUSCH lacks flexibility. For example, the current CG PUSCH does not allow PUSCH to be transmitted in the gaps between slots (e.g., the area indicated by the double-headed arrow A1 in Figure 10). As a result, there is a possibility that it will not be able to fully support XR services. In this embodiment, the terminal flexibly responds to the gaps between slots in the CG PUSCH. Furthermore, the terminal flexibly responds to the gaps between slots in the SPS PDSCH.

<Proposal 1>
The terminal may receive multiple SPS PDSCHs in the SPS cycle of the configured SPS PDSCH. The terminal may receive one or more SPS PDSCHs in slots allocated in the SPS cycle. The slots allocated in the SPS cycle may be consecutive.

Figure 11 is a diagram illustrating an example of an SPS PDSCH. For example, the parameters sps-nrofSlots and sps-nrofPDSCH-InSlot may be provided to a terminal by a higher layer such as RRC. The parameters sps-nrofSlots and sps-nrofPDSCH-InSlot may be included in, for example, the SPS-Config information element of RRC.

sps-nrofSlots may indicate the number of consecutive slots for SPS PDSCH transmission allocated in the configured SPS cycle. sps-nrofPDSCH-InSlot may indicate the number of consecutive SPS PDSCH allocations within a slot. Figure 11 shows an example where sps-nrofSlots = 3 and sps-nrofPDSCHSlot = 2. The SPS period (the period for receiving the SPS PDSCH, for example, the three slots shown in Figure 11) is repeated in the configured SPS cycle.

Hereinafter, reception of multiple SPS PDSCHs in (each) SPS period may be referred to as multiple PDSCHs. Transmission of multiple CG PUSCHs in (each) CG period may be referred to as multiple PUSCHs. Multiple PDSCHs and/or multiple PUSCHs may be applied to a terminal.

<Proposal 2>
Multiple PDSCHs may be supported for one SPS periodicity. Multiple PUSCHs may be supported for one CG periodicity.

<Option 1>
A separate (different) TDRA may be indicated or configured for each of a plurality of SPS PDSCHs in one SPS cycle. A separate TDRA may be indicated or configured for each of a plurality of CG PUSCHs in one CG cycle.

・About Type 1 CG PUSCH
In the case of Type 1 CG PUSCH, multiple TDRAs may be configured for one configuration of multiple PUSCHs.

Figure 12 is a diagram illustrating an example of TDRA configuration. In the case of Type 1 CG PUSCH, multiple TDRAs may be configured based on RRC parameters for one multiple PUSCH configuration, as shown in the underlined part of Figure 12.

・Type 2 CG PUSCH and SPS PDSCH
In the case of Type 2 CG PUSCH, multiple TDRAs may be indicated by the activation DCI of the CG PUSCH for one configuration of multiple PUSCHs. In the case of SPS PDSCH, multiple TDRAs may be indicated by the activation DCI of the SPS PDSCH for one configuration of multiple PDSCHs.

<Alt.1>
One TDRA field of the activation DCI may indicate the RI of a TDRA table having multiple Start and Length Indicator Values (SLIVs) and at least one RI.

Figure 13 shows an example of multiple SLIVs in a TDRA table. In Figure 13, the mapping type is omitted. As shown in Figure 13, one RI in the TDRA table may have multiple SLIVs. For example, RI #k may have two SLIVs: {S=2, L=5} and {S=7, L=5}.

Based on the RI notified by the activation DCI, the terminal may refer to the TDRA table and determine (obtain) the SLIVs of multiple CG PUSCHs of multiple PUSCHs.

The terminal may refer to the TDRA table based on the RI notified by the activation DCI and determine the SLIVs of multiple SPS PDSCHs of multiple PDSCHs.

Alt.1 does not affect (change) the activation DCI of CG PUSCH. Also, Alt.1 allows the reuse of the TDRA table (enhanced in Rel-17) for scheduling multiple PUSCHs.

Alt.1 does not affect the activation DCI of SPS PDSCH. Also, Alt.1 allows the reuse of the TDRA table (enhanced in Rel-17) for scheduling multiple PDSCHs.

<Alt.2>
The activation DCI of the CG PUSCH may include multiple TDRA fields, each of which may indicate an RI of a TDRA table having only one SLIV in each row.

For example, one SLVI indicated by each RI of multiple TDRA fields may indicate the SLIV of each CG PUSCH during the CG period.

The activation DCI for the SPS PDSCH may include multiple TDRA fields, each of which may indicate the RI of a TDRA table with only one SLIV in each row.

For example, one SLVI indicated by each RI of multiple TDRA fields may indicate the SLIV of each SPS PDSCH in the SPS period.

In Alt.2, the TDRA table can be reused for scheduling a single multiple PUSCHs.

Alt.2 allows the reuse of a single TDRA table for scheduling multiple PDSCHs.

<Option 2>
In one SPS period, TDRA may be indicated and/or configured for the first SPS PDSCH, and in one CG period, TDRA may be indicated and/or configured for the first CG PUSCH.

The TDRA of a subsequent SPS PDSCH may be determined based on the TDRA of the first SPS PDSCH and the number of SPS PDSCHs in one period. The TDRA of a subsequent CG PUSCH may be determined based on the TDRA of the first CG PUSCH and the number of CG PUSCHs in one period.

<Alt.1>
TDRA for multiple PDSCHs may be assigned on a slot basis. TDRA for multiple PUSCHs may be assigned on a slot basis.

For example, the SPS PDSCH resource allocation may be the same in each slot. The number of SPS PDSCH slots in one period may be indicated by the activation DCI (if present) or configured by RRC. If configured by RRC, the number of SPS PDSCHs may be configured for each configured SPS or commonly for all configured SPSs.

For example, the CG PUSCH resource allocation may be the same in each slot. The number of CG PUSCH slots in one period may be indicated by the activation DCI (if present) or configured by RRC. If configured by RRC, the number of CG PUSCHs may be configured for each configured CG or commonly for all configured CGs.

<Alt.1-1>
One SPS PDSCH may be allocated in one slot. One CG PUSCH may be allocated in one slot.

Figure 14 is a diagram illustrating an example of Alt.1-1. In the example of Figure 14, the terminal receives three SPS PDSCHs in the set SPS period. In the example of Figure 14, the terminal receives one SPS PDSCH in one slot.

TDRA may be indicated or configured for the SPS PDSCH in the first slot (e.g., the leftmost slot in Figure 14). The TDRA for the SPS PDSCH in the first slot may be applied to the SPS PDSCHs in the remaining slots.

Figure 14 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.1-2>
Multiple SPS PDSCHs may be allocated in one slot. Multiple CG PUSCHs may be allocated in one slot.

<Alt.1-2A>
The number of SPS PDSCHs in one slot may be explicitly indicated and/or configured. The number of CG PUSCHs in one slot may be explicitly indicated and/or configured.

The length of each SPS PDSCH may be the same as the length of the first SPS PDSCH. The length of each CG PUSCH may be the same as the length of the first CG PUSCH.

Figure 15 is a diagram illustrating an example of Alt. 1-2A. In the example of Figure 15, the number of slots allocated for consecutive SPS PDSCH transmissions in the set SPS period is three. The terminal receives two SPS PDSCHs in each slot.

The number of SPS PDSCHs in one slot may be explicitly indicated and/or configured. For example, the number of SPS PDSCHs in one slot, "2," shown in FIG. 15, may be explicitly indicated and/or configured by a parameter of a higher layer, such as DCI or RRC. Furthermore, the length of the SPS PDSCHs shown in FIG. 15 may be the same as the length of the first SPS PDSCH.

Figure 15 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.1-2B>
The number of SPS PDSCHs in one slot may be implicitly determined as the maximum number of PDSCHs allowed in a slot, assuming that the length of the PDSCH is equal to the length of the first PDSCH. The number of CG PUSCHs in one slot may be implicitly determined as the maximum number of PUSCHs allowed in a slot, assuming that the length of the PUSCH is equal to the length of the first PUSCH.

<Alt.1-2B-1>
The length of the last SPS PDSCH in a slot may be shorter than the length of the first SPS PDSCH, and the length of the last CG PUSCH in a slot may be shorter than the length of the first CG PUSCH.

Figure 16 is a diagram illustrating an example of Alt.1-2B-1. In the example of Figure 16, the number of slots allocated for consecutive SPS PDSCH transmissions in the set SPS period is three.

The terminal may implicitly determine the maximum allowable number of SPS PDSCHs in the time domain within a slot based on the length of the SPS PDSCHs and the length of the slot, assuming that the length of the PDSCHs is equal to the length of the first PDSCH. In the example of Figure 16, the maximum allowable number of SPS PDSCHs within a slot is 3. The lengths of the first and second SPS PDSCHs within a slot are the same, but the length of the last SPS PDSCH within a slot may be shorter than the lengths of the other SPS PDSCHs.

For example, the terminal may allocate the first SPS PDSCH to a slot based on TDRA. The terminal may allocate consecutive SPS PDSCHs of the same length as the first SPS PDSCH so that they fit in the slot. The terminal may allocate SPS PDSCHs of a shorter length than the first SPS PDSCH in resources (symbols) where consecutive SPS PDSCHs in the slot do not fit (e.g., the portion indicated by the double-headed arrow A11 in FIG. 16).

Figure 16 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.1-2B-2>
The last SPS PDSCH in a slot may be longer than the first SPS PDSCH, and the last CG PUSCH in a slot may be longer than the first CG PUSCH.

Figure 17 is a diagram illustrating an example of Alt.1-2B-2. In the example of Figure 17, the number of slots allocated for consecutive SPS PDSCH transmissions in the set SPS period is 2.

The terminal may implicitly determine the maximum allowable number of SPS PDSCHs in the time domain within one slot based on the length of the SPS PDSCHs and the length of the slot, assuming that the length of the PDSCHs is equal to the length of the first PDSCH. In the example of Figure 17, the maximum allowable number of SPS PDSCHs within a slot is 2. The length of the second SPS PDSCH within a slot (the last SPS PDSCH within a slot) may be longer than the lengths of the other SPS PDSCHs.

For example, the terminal may allocate the first SPS PDSCH to a slot based on TDRA. The terminal may allocate consecutive SPS PDSCHs of the same length as the first SPS PDSCH so that they fit in the slot. In resources (symbols) where consecutive SPS PDSCHs in the slot do not fit (e.g., the portion indicated by the double-headed arrow A21 in FIG. 17), the terminal may make the length of the last SPS PDSCH (the second SPS PDSCH in the example of FIG. 17) longer than the other SPS PDSCHs.

Figure 17 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.1-2B-3>
The last remaining symbols in a slot that are shorter than the length of the first SPS PDSCH may be dropped. The last remaining symbols in a slot that are shorter than the length of the first CG PUSCH may be dropped.

Figure 18 is a diagram illustrating an example of Alt.1-2B-3. In the example of Figure 18, the number of slots allocated for consecutive SPS PDSCH transmissions in the set SPS period is 3.

The terminal may implicitly determine the maximum number of SPS PDSCHs allowed in the time domain within one slot based on the length of the SPS PDSCH and the length of the slot, assuming that the length of the PDSCH is equal to the length of the first PDSCH. In the example of Figure 18, the maximum number of SPS PDSCHs allowed within a slot is 2. The terminal may drop SPS PDSCHs in resources shorter than the SPS PDSCH within one slot.

For example, the terminal may allocate the first SPS PDSCH to a slot based on TDRA. The terminal may allocate consecutive SPS PDSCHs of the same length as the first SPS PDSCH so that they fit in the slot. The terminal may not drop (allocate) SPS PDSCHs in resources (symbols) where consecutive SPS PDSCHs in the slot do not fit (e.g., the portion indicated by the double-headed arrow A31 in FIG. 18).

Figure 18 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.2>
In one period, multiple SPS PDSCHs may be allocated consecutively based on TDRA, and multiple CG PUSCHs may be allocated consecutively based on TDRA.

For example, multiple SPS PDSCHs may be allocated consecutively across slots, as in PUSCH-repetition type B. For example, multiple CG PUSCHs may be allocated consecutively across slots, as in PUSCH-repetition type B. This enables low-latency communications.

When the SPS PDSCH allocated by TDRA spans slots, the nominal SPS PDSCH may be split into two actual PDSCHs, similar to PUSCH-repetition type B. When the CG PUSCH allocated by TDRA spans slots, the nominal CG PUSCH may be split into two actual PUSCHs, similar to PUSCH-repetition type B.

The number of SPS PDSCHs and CG PUSCHs may be counted based on Alt.2-1 or Alt.2-2 below.

<Alt.2-1>
The number of SPS PDSCHs may be counted based on the nominal SPS PDSCH, and the number of CG PUSCHs may be counted based on the nominal SPS PDSCH.

Figure 19 is a diagram illustrating an example of Alt.2-1. Line A31a in Figure 19 indicates a slot boundary. In Figure 19, the number of SPS PDSCHs in an SPS period is set to 4 (sps-nrofSlots = 4).

In Alt.2-1, the number of SPS PDSCHs is counted based on the nominal SPS PDSCH. That is, the number of SPS PDSCHs is counted before an SPS PDSCH is divided by slots. For example, an SPS PDSCH that is divided at a slot boundary is counted as one.

Therefore, if the number of SPS PDSCHs in an SPS cycle is four and one SPS PDSCH spans multiple slots, the nominal SPS PDSCH is assigned to resources as shown in Figure 19. The terminal decodes the nominal SPS PDSCH assigned to the resource.

Figure 19 explains SPS PDSCH, but the same applies to CG PUSCH.

<Alt.2-2>
The number of SPS PDSCHs may be counted based on the actual SPS PDSCHs, and the number of CG PUSCHs may be counted based on the actual SPS PDSCHs.

Figure 20 is a diagram illustrating an example of Alt.2-2. Line A31b in Figure 20 indicates a slot boundary. In Figure 20, the number of SPS PDSCHs in an SPS period is set to 4 (sps-nrofSlots = 4).

In Alt.2-2, the number of SPS PDSCHs is counted based on the actual SPS PDSCH. That is, the number of SPS PDSCHs is counted after one SPS PDSCH is divided by a slot. For example, an SPS PDSCH divided by a slot boundary is counted as two.
Therefore, when the number of SPS PDSCHs in an SPS cycle is four and one SPS PDSCH spans multiple slots, the actual SPS PDSCHs are allocated to resources as shown in Figure 20. The terminal decodes the actual SPS PDSCH allocated to the resources.

Figure 20 explains SPS PDSCH, but the same applies to CG PUSCH.

In addition, in Alt. 2 of Proposal 1, the number of SPS PDSCHs transmitted in an SPS cycle may be indicated by the activation DCI (if present) or may be configured by RRC. If the number of SPS PDSCHs is configured by RRC, the number of SPS PDSCHs may be configured for each configured SPS or commonly for all configured SPSs.

Also, in Alt. 2 of Proposal 1, the number of CG PUSCHs transmitted in a CG cycle may be indicated by the activation DCI (if present) or configured by RRC. If the number of CG PUSCHs is configured by RRC, the number of CG PUSCHs may be configured for each configured CG or commonly for all configured CGs.

<Proposal 3>
Parameters other than TDRA, such as Frequency Domain Resource Allocation (FDRA), Modulation Coding Scheme (MCS), Redundancy Version (RV), Transmission Configuration Indication (TCI) state, or SRS resource indicator (SRI), may be applied to multiple PDSCHs. Parameters other than TDRA, such as FDRA, MCS, RV, TCI state, or SRI, may be applied to multiple PUSCHs.

<Option 1>
The above parameters may be commonly indicated and/or commonly configured for all SPS PDSCHs in one SPS cycle, and the above parameters may be commonly indicated and/or commonly configured for all CG PUSCHs in one CG cycle.

<Option 2>
The above parameters may be individually indicated and/or individually configured for all SPS PDSCHs in one SPS cycle, and the above parameters may be individually indicated and/or individually configured for all CG PUSCHs in one CG cycle.

For Type 1 CG PUSCH, rrc-ConfiguredUplinkGrant may be used to individually configure the above parameters. For Type 1 CG PUSCH and SPS PDSCH, individual fields for the above parameters may be included in the CG activation DCI and SPS activation DCI.

<Proposal 4>
Actual transmission of PDSCH (reception in the terminal) may occur in all SPS PDSCHs or in some SPS PDSCHs in one SPS cycle, and actual transmission of PUSCH may occur in all CG PUSCHs or in some CG PUSCHs in one CG cycle.

<Option 1>
Actual reception may occur on all SPS PDSCHs in an SPS period, or on a specific SPS PDSCH at the beginning of the SPS period. Actual transmission may occur on all CG PUSCHs in a CG period, or on a specific CG PUSCH at the beginning of the CG period.

For example, the terminal may receive a PDSCH in one of the six SPS PDSCHs of the multiple PDSCHs shown in Figure 15, or may receive a PDSCH in the SPS PDSCH shown on the left side of the six SPS PDSCHs shown in Figure 15.

The number of actual receptions in one SPS cycle and the number of actual transmissions in one CG cycle may be determined according to Alt. 1 or Alt. 2 below.

<Alt.1>
The number of actual receptions in one SPS period may be determined by blind detection. The number of actual transmissions in one CG period may be determined by blind detection.

If blind detection determines that there is no actual reception on a certain SPS PDSCH, the terminal may not perform blind detection on the SPS PDSCH that follows the certain SPS PDSCH. If blind detection determines that there is no actual transmission on a certain CG PUSCH, the base station may not perform blind detection on the CG PUSCH that follows the certain CG PUSCH.

For example, if a terminal determines that there is no actual reception in the second SPS PDSCH from the left of the nine SPS PDSCHs of the multiple PDSCHs shown in Figure 16, it does not need to perform brand detection of the number of actual receptions in the third and subsequent SPS PDSCHs.

<Alt.2>
The number of actual receptions in one SPS cycle may be indicated by control information included in the first SPS PDSCH in the SPS cycle, and the number of actual transmissions in one CG cycle may be indicated by control information included in the first CG PUSCH in the CG cycle.

The control information included in the first SPS PDSCH in an SPS cycle may indicate that there are N actual PDSCHs received in this SPS cycle. N may be a number less than or equal to the maximum number of SPS PDSCHs included in one SPS cycle. If N is less than the maximum number of SPS PDSCHs, the terminal may not perform blind detection on the (N+1)th SPS PDSCH included in one SPS cycle.

The control information included in the first CG PUSCH in a CG period may indicate that there are N actual PUSCH transmissions in this CG period. N may be a number less than or equal to the maximum number of CG PUSCHs included in one CG period. If N is less than the maximum number of CG PUSCHs, the base station may not perform blind detection on the (N+1)th PUSCH included in one CG period.

<Option 2>
Actual reception may not occur in all SPS PDSCHs in one SPS cycle. For example, although many SPS PDSCH candidates are configured in one slot in response to a request for an XR service (see, for example, FIG. 16), it is assumed that actual reception may not occur at a certain timing.

Therefore, the terminal may blindly detect the SPS PDSCH at all SPS PDSCH reception opportunities. Note that even if the terminal determines that there is no actual reception for a certain SPS PDSCH in one SPS period, it still blindly detects the remaining SPS PDSCHs.

There may be cases where actual transmission does not occur for all CG PUSCHs in one CG cycle. For example, in response to an XR service request, many CG PUSCH candidates may be configured within one slot, but actual reception may not occur at a certain timing.

Therefore, the base station may blindly detect the CG PUSCH at all CG PUSCH reception opportunities. Note that even if the base station determines that there is no actual transmission for a certain CG PUSCH in one CG period, it will blindly detect the remaining CG PUSCHs.

<Proposal 5>
Proposal 5 describes HARQ-ACK feedback in one SPS period for multiple PDSCHs.

・HARQ-ACK timing <Alt.1>
The timing of reporting the HARQ-ACK may be determined individually for each SPS PDSCH. Therefore, there may be as many HARQ-ACKs as there are SPS PDSCHs, and there may also be multiple K1s.

K1 may be indicated to the terminal by the activation DCI for each configured SPS PDSCH. Alternatively, one K1 may be indicated to the terminal by the activation DCI and applied commonly to each configured SPS PDSCH.

<Alt.2>
HARQ-ACK feedback for multiple SPS PDSCHs in one SPS period may be reported in one PUCCH. For example, HARQ-ACKs for the nine SPS PDSCHs shown in Figure 16 may be reported in one PUCCH. The transmission timing of the PUCCH may be determined based on K1 indicated by the activation DCI and the first or last SPS PDSCH slot of the SPS period.

Regarding Type 1 HARQ-ACK CB and Type 2 HARQ-ACK CB with only SPS PDSCHs of multiple PDSCHs: Figure 21 illustrates an example of HARQ-ACK ordering in Type 1 HARQ-ACK CB of multiple PDSCHs. HARQ-ACKs of SPS PDSCHs of multiple PDSCHs are sorted in ascending order of the starting symbol (number) of the SPS PDSCH for each DL slot number of each SPS configuration index of each serving cell index. Then, HARQ-ACKs of SPS PDSCHs are sorted in ascending order of the DL slot number of each SPS configuration index of each serving cell index. Then, HARQ-ACKs of SPS PDSCHs are sorted in ascending order of the SPS configuration index of each serving cell index. Then, HARQ-ACKs of SPS PDSCHs are sorted in ascending order of the serving cell index.

In Type 2 HARQ-ACK CB for SPS PDSCH reception, HARQ-ACKs may be ordered in the same way as in the Type 1 HARQ-ACK CB described above. Note that in Type 2 HARQ-ACK CB, when the HARQ-ACK for SPS PDSCH reception is multiplexed with the HARQ-ACK for dynamically scheduled PDSCH reception and/or the HARQ-ACK for deactivation DCI, the HARQ-ACK (bit) for SPS PDSCH reception is added following (contiguous in time) the HARQ-ACK (bit) for dynamically scheduled PDSCH reception and/or the HARQ-ACK (bit) for deactivation DCI.

Type 1 HARQ-ACK feedback for SPS PDSCH and dynamic PDSCH of multiple PDSCHs
When an individual TDRA is indicated and/or configured for each SPS PDSCH (see, for example, Opt. 1 of Proposal 2), the generation procedure of Type 1 HARQ-ACK CB may follow the generation procedure in Rel.-15 or Rel.-16. Also, the generation procedure of Type 1 HARQ-ACK CB may follow the generation procedure of HARQ-ACK CB for multi-PDSCH scheduling currently under discussion in Rel.-17.

If only TDRA of the first SPS PDSCH is indicated and/or configured (see, for example, Opt. 2 of Proposal 2), the following Opt. 1 or Opt. 2 may apply.

<Option 1>
Multiple candidate PDSCH reception opportunities in one SLIV may be determined as follows.

Figure 22 is a diagram illustrating an example of a candidate PDSCH reception opportunity.

(1) When the timing of HARQ-ACK reporting is determined individually for each SPS PDSCH, the number N of multiple candidate PDSCH reception opportunities for one SLIV may be determined by the maximum number of SPS PDSCHs in one slot.

For example, in the example of Figure 16, if the timing of HARQ-ACK reporting is determined individually for each SPS PDSCH, the number N of candidate PDSCH reception opportunities may be 3.

(2) When HARQ-ACKs for multiple SPS PDSCHs in one SPS period are reported in one PUCCH, the number of multiple candidate PDSCH reception opportunities for one SLIV may be determined by the maximum number of SPS PDSCHs in one SPS period.

For example, in the example of Figure 16, if HARQ-ACKs for multiple SPS PDSCHs in one SPS period are reported in one PUCCH, the number of candidate PDSCH reception opportunities may be 9.

<Option 2>
One candidate PDSCH reception opportunity in one SLIV may be determined as follows.

<Opt.2-1>
The PDSCH slot set (PDSCH slot window) may be expanded or the K1 set may be expanded.

・Step 1
If multiple PDSCH scheduling is not enabled or configured, the PDSCH slot set or K1 set may be expanded based on the maximum number of PDSCH slots in one SPS period.

When multiple PDSCH scheduling is enabled or configured, the PDSCH slot set or K1 set may be expanded based on the maximum value between the "maximum number of PDSCH slots in one SPS period" and the "maximum number of PDSCH slots for multiple PDSCH scheduling by one DCI".

Figure 23 is a diagram illustrating an example of an extended PDSCH slot set. One SPS cycle includes multiple SPS PDSCHs. If K1 is set (extended) for each of the multiple SPS PDSCHs, the PDSCH slot set may be extended as shown in dotted frame A41a in Figure 23. Note that dotted frame A41b in Figure 23 indicates, for example, a PDSCH slot set determined from the K1 value of the first SPS PDSCH in one SPS cycle.

・Step 2
The candidate PDSCH reception opportunity in each candidate PDSCH slot after K1 extension may be determined based on the set of SLIVs in each row of the TDRA table.

Note that Opt.2-1 of Proposal 5 applies to the case of slot-based multiple PDSCHs where one PDSCH is included in one slot, and HARQ-ACKs for multiple SPS PDSCHs in one SPS period are reported in one PUCCH. For example, Opt.2-1 of Proposal 5 applies to the case of Alt.1-1 of Opt.2 of Proposal 2 (see, for example, Figure 14).

<Opt.2-2>
The PDSCH slot set may be expanded, and each row of the TDRA table may be expanded.

・Step 1
The PDSCH slot set or K1 set is expanded in the same manner as in Step 1 of Opt.2-1 above.

・Step 2
For each row in the TDRA table, the SLIV in the original TDRA table may be extended assuming that it is the first PDSCH in a slot (SPS PDSCH). The SLIVs of the PDSCHs following the first PDSCH in the same slot may be added to the row in the TDRA table.

Figure 24 is a diagram explaining an example of an SLIV extension. The table shown in the lower left of Figure 24 shows the original TDRA table. The original TDRA table includes the SILV of the first PDSCH in one slot.

The table shown in the lower right of Figure 24 shows an extended TDRA table. In the extended TDRA table, in addition to the SILV of the first PDSCH in one slot, the SILV of the PDSCH following the first PDSCH is included.

For example, SLIV {S=2, L=5} in RI #k of the extended TDRA table indicates the SLIV of the SPS PDSCH shown by arrow A42a in Figure 24. SLIV {S=7, L=5} indicates the SLIV of the SPS PDSCH shown by arrow A42b in Figure 24. SLIV {S=12, L=2} indicates the SLIV of the SPS PDSCH shown by arrow A42c in Figure 24.

・Step 3
The candidate PDSCH reception opportunity in each candidate PDSCH slot after K1 extension may be determined based on the SLIV set in each row of the extended TDRA table.

Note that Opt.2-2 of Proposal 5 is applied to the case of slot-based multiple PDSCH, where multiple PDSCHs are included in one slot, and when HARQ-ACKs for multiple SPS PDSCHs in one SPS period are reported in one PUCCH. For example, Opt.2-2 of Proposal 5 is applied to the case of Alt.1-2 of Opt.2 of Proposal 2 (see, for example, Figure 15).

<Option 2-3>
In each row of the TDRA table, the SLIV may be expanded.

・Step 1
For each row in the TDRA table, the SLIV may be extended assuming that the SLIV is the first PDSCH in one SPS period. The SLIVs of the PDSCHs following the first PDSCH in one SPS period may be added to the row in the TDRA table assuming the maximum number of SPS PDSCHs in one SPS period.

Figure 25 is a diagram explaining an example of an SLIV extension. The table shown in the lower left of Figure 25 shows the original TDRA table. The original TDRA table includes the SILV of the first PDSCH in one slot.

The table shown in the lower right of Figure 25 shows an extended TDRA table. The extended TDRA table includes the SILV of the first PDSCH in one SPS period as well as the SILV of the PDSCH following the first PDSCH.

For example, SLIV {K0=2, S=2, L=5} in RI #k of the extended TDRA table indicates the SLIV of the SPS PDSCH shown by arrow A43a in FIG. 25. SLIV {K0=2, S=7, L=5} indicates the SLIV of the SPS PDSCH shown by arrow A43b in FIG. 25. SLIV {K0=2, S=12, L=2} indicates the SLIV of the SPS PDSCH shown by arrow A43c in FIG. 25. SLIV {K0=3, S=0, L=3} indicates the SLIV of the SPS PDSCH shown by arrow A43d in FIG. 25. SLIV {K0=3, S=3, L=5} indicates the SLIV of the SPS PDSCH shown by arrow A43e in FIG. 25.

・Step 2
The determination of the candidate PDSCH slots and the candidate PDSCH receiving opportunities may follow the determination of multiple PDSCH scheduling in Rel.-17.

Note that Opt. 2-3 of Proposal 5 are applied to the case of slot-based multiple PDSCHs where one PDSCH is included in one slot, and to the case of slot-based multiple PDSCHs where multiple PDSCHs are included in one slot. For example, Opt. 2-3 of Proposal 5 are applied to Alt. 1 and Alt. 2 of Opt. 2 of Proposal 2 (see, for example, Figures 14-18).

<Variations>
Which of the multiple proposals applies, which of the multiple options applies, and/or which of the multiple alternatives applies may be determined in the following manner.

- Set by upper layer parameters.
- Reported by the UE as UE capability(ies).
- It is stated in the specifications.
- Determined based on the settings of higher layer parameters and the reported UE capability.
- Determined by a combination of two or more of the above decisions.
- Slots may be replaced with sub-slots.

<UE capability>
The UE capability indicating the capability of the UE may include the following information indicating the capability of the UE: Note that the information indicating the capability of the UE may correspond to information defining the capability of the UE.

Information defining whether the UE supports multiple consecutive CG PUSCHs in one CG period. Information defining whether the UE supports multiple slot-based SPS PDSCHs in one SPS period. Information defining whether the UE supports multiple consecutive SPS PDSCHs in one SPS period. Information defining whether the UE supports multiple PUSCHs with individual TDRA indications/settings for each CG PUSCH in one CG period. Information defining whether the UE supports multiple PDSCHs with individual TDRA indications/settings for each SPS PDSCH in one CG period. Information defining whether the UE supports reception of actual transmissions on which PDSCH opportunities of multiple SPS PDSCHs in one SPS period. Information defining whether the UE supports actual transmissions on which PUSCH opportunities of multiple CG PUSCHs in one CG period. Information defining whether the UE supports individual HARQ-ACK feedback decisions for different SPS PDSCHs in one SPS period. Information defining whether the UE supports the function of reporting HARQ-ACK for different SPS PDSCHs in one SPS period using one PUCCH

<Example of a wireless communication system>
The wireless communication system according to the present embodiment includes a base station 10 shown in FIG. 26 and a terminal 20 shown in FIG. 27. The number of base stations 10 and the number of terminals 20 are not particularly limited. For example, as shown in FIG. 1, the system may be one in which two base stations 10 (base station 10-1 and base station 10-2) communicate with one terminal 20. The wireless communication system may be a wireless communication system conforming to New Radio (NR). For example, the wireless communication system may be a wireless communication system conforming to a method called URLLC and/or IIoT.

The wireless communication system may also be a wireless communication system conforming to a method called 5G, Beyond 5G, 5G Evolution or 6G.

The base station 10 may be referred to as an NG-RAN Node, ng-eNB, eNodeB (eNB), or gNodeB (gNB). The terminal 20 may be referred to as User Equipment (UE). The base station 10 may also be considered as a device included in the network to which the terminal 20 connects.

The wireless communication system may include a Next Generation-Radio Access Network (hereinafter referred to as NG-RAN). The NG-RAN includes multiple NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that the NG-RAN and 5GC may also be simply referred to as the "network."

The base station 10 performs wireless communication with the terminal 20. For example, the wireless communication performed complies with NR. At least one of the base station 10 and the terminal 20 may support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements. At least one of the base station 10 and the terminal 20 may also support Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CC). At least one of the base station 10 and the terminal 20 may also support Dual Connectivity (DC), which performs communication between the terminal 20 and each of multiple base stations 10.

The wireless communication system may support multiple frequency bands. For example, the wireless communication system supports Frequency Range (FR) 1 and FR2. The frequency bands of each FR are, for example, as follows:
・FR1: 410MHz to 7.125GHz
・FR2: 24.25GHz to 52.6GHz

FR1 may use a Sub-Carrier Spacing (SCS) of 15 kHz, 30 kHz, or 60 kHz, and a bandwidth (BW) of 5 MHz to 100 MHz. FR2, for example, is a higher frequency than FR1. FR2 may use an SCS of 60 kHz or 120 kHz, and a bandwidth (BW) of 50 MHz to 400 MHz. FR2 may also include an SCS of 240 kHz.

The wireless communication system in this embodiment may support frequency bands higher than the FR2 frequency band. For example, the wireless communication system in this embodiment may support frequency bands above 52.6 GHz and up to 114.25 GHz. Such high frequency bands may be referred to as "FR2x."

In addition, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread - Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) than the above-mentioned examples may be applied. Furthermore, DFT-S-OFDM may be applied to both the uplink and downlink, or to either one.

In a wireless communication system, a slot configuration pattern for time division duplexing (TDD) may be set. For example, the slot configuration pattern may specify a pattern indicating the order of two or more slots among slots for transmitting downlink (DL) signals, slots for transmitting uplink (UL) signals, slots containing a mixture of DL signals, UL signals, and guard symbols, and slots in which the transmitted signals are changed to flexible.

In addition, in wireless communication systems, channel estimation of PUSCH (or PUCCH (Physical Uplink Control Channel)) can be performed using a demodulation reference signal (DMRS) for each slot, but channel estimation of PUSCH (or PUCCH) can also be performed using DMRS assigned to multiple slots. Such channel estimation may be called joint channel estimation, or may be called by another name such as cross-slot channel estimation.

The terminal 20 may transmit DMRS allocated to each of the multiple slots in multiple slots so that the base station 10 can perform joint channel estimation using DMRS.

Furthermore, in the wireless communication system, an enhanced function may be added to the feedback function from the terminal 20 to the base station 10. For example, an enhanced function may be added to the terminal's feedback regarding HARQ-ACK.

Next, the configuration of the base station 10 and terminal 20 will be described. Note that the configuration of the base station 10 and terminal 20 described below is an example of functions related to this embodiment. The base station 10 and terminal 20 may have functions not shown. Furthermore, the functional divisions and/or names of the functional units are not limited as long as they are functions that perform operations related to this embodiment.

<Base station configuration>
Fig. 26 is a block diagram showing an example of the configuration of base station 10 according to this embodiment. Base station 10 includes, for example, a transmitting unit 101, a receiving unit 102, and a control unit 103. Base station 10 communicates with terminal 20 (see Fig. 27) by radio.

The transmitting unit 101 transmits a downlink (DL) signal to the terminal 20. For example, the transmitting unit 101 transmits the DL signal under the control of the control unit 103.

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 by the terminal 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., Radio Resource Control (RRC) control information). The DL signal may also include a reference signal.

Channels used to transmit DL signals include, for example, data channels and control channels. 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.

Reference signals included in DL signals 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 position information. For example, reference signals such as DMRS and PTRS are used to demodulate downlink data signals and are transmitted using PDSCH.

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.

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.

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 data, control information, etc. received from the receiving unit 102 to the upper layer.

For example, the control unit 103 allocates resources (or channels) to be used for transmitting and receiving DL signals and/or resources to be 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. obtained from a higher layer. Information regarding the allocated resources may be included in the control information transmitted to the terminal 20.

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

<Device configuration>
27 is a block diagram showing an example of the configuration of terminal 20 according to this embodiment. Terminal 20 includes, for example, a receiving unit 201, a transmitting unit 202, and a control unit 203. Terminal 20 communicates with base station 10, for example, wirelessly.

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.

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.

The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, it may include information related to the processing capabilities of the terminal 20 (e.g., UE capability). The UL signal may also include a reference signal.

Channels used to transmit UL signals include, for example, data channels and control channels. For example, the data channel includes the PUSCH (Physical Uplink Shared Channel), and the control channel includes the 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.

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 uplink data signals and are transmitted using an uplink channel (e.g., PUSCH).

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

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. The control unit 203 also outputs, for example, data and control information received from the receiving unit 201 to the upper layer.

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, 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 PUCCH resources.

The control unit 203 sets 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 RRC and/or DCI). The control unit 203 determines the PUCCH resource 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 resource determined by the control unit 203.

Note that the channels used to transmit DL signals and UL signals are not limited to the above examples. For example, the channels used to transmit DL signals and UL signals 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.

The control unit 203 may set a DL signal reception period based on the period setting information. The receiving unit 201 may receive the DL signal using multiple SPS PDSCHs for each set reception period. The period setting information may be, for example, an RRC parameter.

The receiving unit 201 may receive DL signals using multiple SPS PDSCHs in multiple consecutive slots, for example, as shown in Figures 14 to 18. The receiving unit 201 may receive DL signals using one SPS PDSCH included in each of multiple slots, for example, as shown in Figure 14. The receiving unit 201 may receive DL signals using multiple SPS PDSCHs included in each of multiple slots, for example, as shown in Figures 15 to 18.

With the above configuration, terminal 20 can perform SPS PDSCH communication, which is suitable for high-capacity communications.

The receiving unit 201 may receive configuration information for the transmission period of the UL signal and individual TDRAs for multiple CG PUSCHs transmitting the UL signal. The control unit 203 may allocate the CG PUSCH to resources based on the individual TDRAs for each transmission period of the received configuration information. The configuration information may be, for example, an RRC parameter.

The receiving unit 201 may receive the TDRA using higher layer signaling, such as RRC signaling. The RRC signaling may also be referred to as an RRC message or an RRC information element.

With the above configuration, terminal 20 can perform CG PUSCH communication, which is suitable for high-capacity communications.

For each transmission period of the received configuration information, the control unit 203 may determine the first CG PUSCH in a slot based on the TDRA, and may determine the last CG PUSCH in a slot so that it fits within the rear boundary of the slot. For example, as shown in Figures 16 and 17, the control unit 203 may determine the first CG PUSCH in a slot based on the TDRA, and may determine the last CG PUSCH in a slot so that it fits within the rear boundary of the slot. The control unit 203 may allocate multiple CG PUSCHs to resources consecutively within one slot.

With the above configuration, terminal 20 can perform CG PUSCH communication, which is suitable for high-capacity communications.

The receiving unit 201 may receive DL signals using multiple SPS PDSCHs for each set reception period, and the transmitting unit 202 may transmit a response signal for the DL signals. The transmitting unit 202 may transmit the response signal using one PUCCH. The response signal may be, for example, a HARQ-ACK. The receiving unit 201 and the transmitting unit 202 may be referred to as a communication unit.

The control unit 203 may determine the number of candidate reception opportunities for multiple SPS PDSCHs based on the maximum number of SPS PDSCHs in one slot. The control unit 203 may determine the number of candidate reception opportunities for multiple SPS PDSCHs based on the maximum number of SPS PDSCHs in each reception cycle. The control unit 203 may determine a slot set for multiple SPS PDSCHs to which a response signal is to be transmitted based on the maximum number of SPS PDSCHs in each reception cycle.

With the above configuration, terminal 20 can appropriately report HARQ-ACK for SPS PDSCH, which is suitable for high-capacity communications.

This disclosure has been described above.

<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 hardware and/or 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., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

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

For example, a base station, a terminal, etc. in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 28 is a diagram showing an example of the hardware configuration of a base station and a terminal in one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

In the following description, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the base station 10 and terminal 20 may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

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 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 storage 1003.

The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.

The processor 1001 also 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 in accordance with these. The program used is a program that causes 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 program may also be transmitted from a network via a telecommunications line.

Memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. Memory 1002 may also be referred to as a register, cache, main memory (primary storage device), etc. Memory 1002 can store executable programs (program code), software modules, etc. for implementing a wireless communication method relating to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium and may be composed of, for example, at least one of 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 suitable medium including at least one of memory 1002 and storage 1003.

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, network controller, network card, or communication module. 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, and transmitter 202 may be realized by the communication device 1004.

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

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 may be configured using different buses between each device.

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.

<Information notification, signaling>
The notification of information is not limited to the embodiments described in the present disclosure, and may be performed using other methods. For example, the 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, the 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.

<Applicable systems>
The embodiments described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), 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.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

<Processing procedures, etc.>
The order of the procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed unless it is consistent. 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.

<Base station operation>
In the present disclosure, a specific operation described as being performed by a base station may 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.

<Input/output direction>
Information, etc. (see the section on information and signals) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Information may be input or output via multiple network nodes.

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

<Judgment 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 numerical comparison (e.g., comparison with a predetermined value).

<Variations in form, etc.>
The aspects/embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

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 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.

<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.

Software, instructions, information, etc. may also be transmitted and received via 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), these wired and/or wireless technologies are included within the definition of transmission media.

<Information, Signals>
The 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. that 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.

Note that terms explained 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.

<Systems, Networks>
As used in this disclosure, the terms "system" and "network" are used interchangeably.

<Parameter and channel names>
Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical formulas, etc. 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.

<Base station>
In the present disclosure, terms such as "base station (BS),""radio base station,""fixedstation,""NodeB,""eNodeB(eNB),""gNodeB(gNB),""accesspoint,""transmissionpoint,""receptionpoint,""transmission/receptionpoint,""cell,""sector,""cellgroup,""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.

A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of a base station and/or base station subsystem that provides communication services within this coverage area.

<Mobile Station>
In this disclosure, the terms "Mobile Station (MS),""userterminal,""User Equipment (UE),""terminal," and the like may be used interchangeably.

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.

<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 body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also 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.

Furthermore, the base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions possessed by 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 uplink channel and downlink channel may be read as side channel.

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

<Terminology and interpretation>
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, 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, all of which are considered to be "determining.""Determining" and "determining" may also include resolving, selecting, choosing, establishing, comparing, and the like, all of which are considered to be "determining." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Also, "judgment (decision)" can be interpreted as "assuming,""expecting,""considering," etc.

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.

<Reference signal>
The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

<The 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."

<"First" and "Second">
As used in this disclosure, any reference to an element using a designation such as "first,""second," etc. 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 in some way precede the second element.

<Means>
The "means" in the configuration of each of the above devices may be replaced with "part,""circuit,""device," etc.

<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.

<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.

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

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

A slot may include multiple minislots. Each minislot may consist of one or more 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.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Other names may also be used for radio frame, subframe, slot, minislot, and symbol.

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

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

A TTI may be a transmission time unit for a channel-coded data packet (transport block), code block, code word, etc., or may be a processing unit for scheduling, link adaptation, etc. Note that when a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, code block, code word, etc. is actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the smallest time unit for scheduling. Furthermore, the number of slots (minislots) that constitute the smallest time unit for scheduling may be controlled.

A TTI with a time length of 1 ms may be referred to as 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 referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that 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 that of a long TTI and greater than or equal to 1 ms.

A resource block (RB) is a resource allocation unit in the time and frequency domains, 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 also be determined based on numerology.

Furthermore, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each consist of one or more resource blocks.

In addition, one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

A resource block may also 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.

A Bandwidth Part (BWP) (which may also be referred to as a partial 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 that BWP.

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

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."

The above-described structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, 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, as well as the number of symbols in a TTI, symbol length, and cyclic prefix (CP) length can be varied in various ways.

<Maximum transmission power>
The "maximum transmit power" in this disclosure may mean the maximum value of the transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

＜Article＞
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.

"Different"
In the present 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 "coupled" may also be interpreted in the same way as "different."

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

10 Base station 20 Terminal 101, 202 Transmitter 102, 201 Receiver 103, 203 Controller

Claims (5)

a control unit that sets a semi-permanent reception period of a downstream signal based on the period setting information;
a receiving unit that receives the downlink signals using a plurality of downlink channels for each reception period ,
the receiving unit receives an index for determining resource allocation in the time domain of the plurality of downlink channels via downlink control information;
the control unit refers to a table in which indexes are associated with a plurality of resource allocations in the time domain based on the received index, and determines resource allocations in the time domain for the plurality of downlink channels.
Terminal. the receiving unit receives the downlink signal in a plurality of consecutive slots using the plurality of downlink channels.
The terminal according to claim 1 . the receiving unit receives the downlink signal using one downlink channel included in each of the plurality of slots.
The terminal according to claim 2. the receiving unit receives the downlink signal using a plurality of downlink channels included in each of the plurality of slots.
The terminal according to claim 2. The device is
Based on the cycle setting information, a semi-permanent reception cycle of the downstream signal is set,
receiving the downlink signals using a plurality of downlink channels for each reception period;
receiving an index for determining resource allocation in the time domain of the plurality of downlink channels via downlink control information;
determining a time-domain resource allocation for the plurality of downlink channels by referring to a table in which indexes are associated with a plurality of time-domain resource allocations based on the received index;
Wireless communication method.