WO2024241926A1 - Terminal and communication method - Google Patents

Abstract

Provided are a terminal and a communication method for performing appropriate communication when Alt-A1 is applied. This terminal comprises: a reception unit for receiving a parameter for setting a transmission opportunity of an uplink signal; and a control unit for determining the transmission opportunity on the basis of the setting of the parameter and symbol information indicating a start symbol and a symbol length of the transmission opportunity included in a downlink control signal. The number of the transmission opportunities set within a specific period is determined on the basis of a time domain resource allocation of the transmission opportunity indicated/set first.

Description

Terminal and communication method

This disclosure relates to a terminal and a communication method.

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

For 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 CG PUSCH (Configured Grant Physical Uplink Shared Channel) (e.g., Non-Patent Document 2). There are Type 1 CG PUSCH and Type 2 CG PUSCH.

Release 17 examines XR (Extended Reality), including VR (virtual reality), AR (augmented reality), and MR (mixed reality), and considers XR scenarios, requirements, key performance indicators (KPIs), and evaluation methods. The target requirements for XR are to take into account capacity, latency (delay), mobility, and energy saving aspects.

3GPP TS38.213 V16.3.0 (2020-09) 3GPP TS38.331 V16.2.0 (2020-09) RP-223502 “New WID on XR Enhancements for NR”, 3GPP TSG RAN Meeting #98-e, Electronic Meeting, December 12-16, 2022 3GPP TS38.214 V17.4.0 (2022-12) 3GPP TS38.331 V17.1.0 (2022-06) 3GPP TS38.214 V17.5.0 (2023-03)

At the RAN1#112 meeting, as described below, it was agreed to conduct further study on Alt-A, Alt-B, and Alt-C with regard to determining the TDRA (time domain resource allocation) of CG PUSCH related to multi-PUSCHs CG, and it was agreed that, among each Alt, Alt-A1, Alt-B, and Alt-C2 will be prioritized for further downscoping for the TDRA design for multi-PUSCHs CG.

One aspect of the present disclosure is to provide a terminal and a communication method that perform appropriate communication when Alt-A1 is applied.

A terminal according to one embodiment of the present disclosure has a receiving unit that receives parameters for setting transmission opportunities for an uplink signal, and a control unit that determines the transmission opportunities based on the parameter settings and symbol information indicating the start symbol and symbol length of the transmission opportunities contained in a downlink control signal, and the number of transmission opportunities set within a specific period is determined based on the time domain resource allocation of the transmission opportunities initially specified/set.

FIG. 1 is a diagram illustrating an example of dual connectivity (DC). FIG. 13 is a diagram illustrating an example of PUCCH carrier switching. This diagram explains the agreements reached at the RAN1#112 meeting regarding time domain resource allocation (TDRA). This is a diagram explaining the TDRA table determination for type 1 CG. FIG. 1 is a diagram illustrating PUSCH slot counting. FIG. 1 is a diagram illustrating PUSCH slot counting. A diagram explaining multiple CG PUSCH occasions within one CG period. FIG. 2 is a block diagram showing an example of the configuration of a base station. FIG. 2 is a block diagram showing an example of a configuration of a terminal. FIG. 2 is a diagram illustrating an example of a hardware configuration of a base station and a terminal according to an embodiment. FIG. 1 is a diagram illustrating an example of a configuration of a vehicle.

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

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

<Dual connectivity>
FIG. 1 is a diagram showing an example of dual connectivity (DC). In the example of FIG. 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 FIG. 1, in DC, carriers between different base stations are bundled.

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

In the case of DC, there may be a delay in communication between base station 10-1 and base station 10-2, so it is difficult to notify uplink control information (e.g., Uplink Control Information: UCI) received by the Pcell of base station 10-1 to base station 10-2 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 a 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 FIG. 1, the terminal 20 configures an Scell in addition to a Pcell for the base station 10-1. The terminal 20 also configures an Scell in addition to a PScell for the base station 10-2. The terminal 20 transmits the UCI of each carrier under the base station 10-1 on the PUCCH of the Pcell. The terminal 20 also transmits the UCI of each carrier under the base station 10-2 on the PUCCH of the PScell. In the example of FIG. 1, the cell group (CG) under the base station 10-1 may be referred to as a Master Cell-Group (MCG). The cell group under the base station 10-2 may be referred to as a Secondary Cell-Group (SCG).

When DC is being performed, the terminal 20 may transmit PUCCH via the Pcell, PScell, and/or PUCCH-Scell. In general, it is not expected that the terminal 20 will transmit PUCCH via an Scell other than the 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 the Time Division Duplex (TDD) system.

Figure 2 shows an example of PUCCH carrier switching. In the example of Figure 2, the base station and the 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 FIG. 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 S101 at timing S102, but at timing S102, the slot of cell 1 is a downlink (DL) slot. Therefore, when the terminal transmits a HARQ-ACK in cell 1, the transmission of the HARQ-ACK is postponed until the timing of transmitting the PUCCH in the uplink (UL) slot (for example, the timing of S103 in FIG. 2), thereby increasing the latency of the HARQ-ACK transmission. The timing of transmitting the PUCCH in the uplink (UL) slot may also be referred to as a PUCCH transmission opportunity.

In the example of Figure 2, at the timing of S102, the slot of cell 2 is a UL slot. In the example of Figure 2, if the terminal can transmit a HARQ-ACK for the data received in S101 at the PUCCH transmission opportunity at the timing of 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 (registered trademark) is considering PUCCH carrier switching, which switches the carrier on which a terminal 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 a resource with a time unit shorter than a symbol) is the same or overlaps).

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

Two methods are being considered for implementing PUCCH carrier switching. The first method is for the base station to dynamically instruct the terminal on the carrier for transmitting PUCCH. The second method is for the base station to semi-statically set the carrier for transmitting PUCCH to the terminal. Note that in the following embodiments, "transmitting PUCCH" and "transmitting PUCCH" may also refer to transmitting uplink control information via PUCCH.

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

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

The configuration operation of quasi-static PUCCH carrier switching may be based on the RRC setting the PUCCH cell timing pattern of the PUCCH cell to which the quasi-static PUCCH carrier switching applies. The configuration operation of quasi-static PUCCH carrier switching may also 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 of control information, the K1 value (offset) from PDSCH to HARQ-ACK may be interpreted based on the numerology of the dynamically instructed target PUCCH cell. The control information may be control information for scheduling the PUCCH, such as Downlink control information (DCI). The numerology may also be considered as slots or Subcarrier Spacing (SCS).

<Configured Grant enhancements in Rel-18 XR>
RP-223502 (Non-Patent Document 3) of the WID (Work Item Description) in Rel-18 describes specifying capacity-related extensions. For example, multiple CG PUSCH transmissions during a period of single CG PUSCH configuration are described as one of the extensions. Thus, in Rel-18, multiple CG PUSCH transmission occasions can be supported in one CG period. Note that the CG PUSCH transmission occasion may be referred to as a transmission opportunity, a CG PUSCH transmission opportunity, a CG PUSCH opportunity, a CG PUSCH occasion, or a CG occasion.

<TDRA (Agreements made at the RAN1#112 meeting)>
Figure 3 is a diagram explaining the agreement on time domain resource allocation (TDRA) at the RAN1#112 meeting. At the RAN1#112 meeting, it was agreed to further study Alt-A, Alt-B, and Alt-C shown in Figure 3 regarding TDRA determination of CG PUSCH related to multi-PUSCHs CG.

＜Type 1 CG, Type 2 CG＞
At the RAN1#112 meeting, it was agreed that multi-PUSCHs CG is supported for both type 1 CG and type 2 CG.

Figure 4 explains the TDRA table determination for type 1 CG and type 2 CG. As shown in Figure 4, section 6.1.2.3 of TS38.214 (Non-Patent Document 4) specifies resource allocation for uplink transmission by CG.

For type 1 PUSCH transmission with CG, parameters are specified in configuredGrantConfig. For example, the following parameters are specified:

(1) In the case of PUSCH repetition type A, the selection of the TDRA table follows the rules of DCI format 0_0 on the UE specific search space. In other words, the determination of the TDRA table for type 1 CG follows the rules of DCI format 0_0.

(2) The value m of the higher layer parameter timeDomainAllocation provides the row index m+1 that points to the determined TDRA table. The starting symbol and length are determined according to the procedure defined in Section 6.1.2.1 of TS38.214.

For type 2 PUSCH transmission with CG, resource allocation follows higher layer configuration and UL grant received in DCI.

The PUSCH repetition type and time domain resource allocation table (TDRA table) are determined by the PUSCH repetition type and time domain resource allocation table associated with the UL grant received on the DCI, respectively. If a Koffset value is set, it is applied when determining the first CG PUSCH occasion.

There are two types of CG PUSCH: 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 not dependent on DCI.

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

<Alt-A1 Framework>
As explained in <TDRA (Agreement at RAN1#112 Meeting)> above, it was agreed to further study Alt-A, Alt-B, and Alt-C shown in Fig. 3 regarding the TDRA determination of CG PUSCH related to multi-PUSCHs CG. In Alt-A, the TDRA determination of CG PUSCH related to multi-PUSCHs CG is based on the repetition framework. In Alt-A1 of Alt-A, the TDRA determination of CG PUSCH related to multi-PUSCHs CG is based on the time domain resource mapping of repetition type A.

<PUSCH slot counting in Rel-17>
TS38.214 specifies whether or not to count a PUSCH slot that overlaps with a TDD DL symbol and/or a symbol of an SS/PBCH block as an available slot when multiple PUSCHs are scheduled with a single DCI.

Note that SS is an abbreviation for Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS). PBCH is an abbreviation for Physical Broadcast Channel. In the following, SS/PBCH blocks may be referred to as SSB. SSB symbols may be considered as one of the DL symbols.

Figure 5 explains PUSCH slot counting. As shown in Figure 5, section 6.1.2.1 of TS38.214 specifies the counting of available slots in DG PUSCH repetition Type A, TBoMS of DG PUSCH, PUSCH scheduled by RAR, and PUSCH scheduled by DCI scrambled by TC-RNTI.

Note that repetition type A is a form in which a PUSCH allocated within a slot is repeatedly transmitted in multiple slots. A PUSCH is 14 symbols or less and cannot be allocated across multiple slots (adjacent slots).

TBoMS stands for TB processing over multi-slot. RAR stands for Random Access Response. TC-RNTI stands for Temporary Cell Radio Network Temporary Identifier.

Figure 6 explains PUSCH slot counting. As shown in Figure 6, section 6.1.2.3.3 of TS38.214 specifies the counting of available slots in CG PUSCH repetition type A. Section 6.1.2.3.3 of TS38.214 specifies the counting of available slots in TBoMS of CG PUSCH.

Analysis
At the RAN1#112bis meeting, it was agreed that Alt-A1, Alt-B, and Alt-C2, among the Alts shown in Figure 3, would be prioritized for further downscoping for the TDRA design for multi-PUSCHs CG. However, at present, it is difficult to determine which scheme will ultimately be supported. In addition, there are some items that were not agreed upon at RAN1#112bis and are to be considered in the future.

The following issues need to be considered regarding Alt-A1:
(Problem 1) The number of CG PUSCHs in one CG period is considered to be set by RRC or indicated by activation DCI. However, details for indicating the number of CG PUSCHs by activation DCI have not yet been considered. Therefore, there is a risk of affecting activation DCI.
(Issue 2) The impact of TDD collision has not been considered or clarified. For example, it is not clear whether to perform special handling of CG PUSCH that collides with DL symbols.

If the above contents are not clarified, there is a risk that the operation of base stations or terminals may be affected, and there may also be problems in terms of resource utilization efficiency.

<Proposal>
Based on the above analysis, in this embodiment, a proposal is made to solve the above two problems regarding Alt-A1.

First, we will use Figure 7 to explain multiple CG PUSCH occasions within one CG period in Alt-A1. Figure 7 shows an example where NumberOfOccasions, a parameter indicating one CG period, is "3". The double arrow in Figure 7 indicates one slot.

When NumberOfOccasions=3, CG PUSCH occasions are allocated once per slot and across three slots by a single SLIV indicated by TDRA. SLIV stands for Start and Length Indicator Value.

<Proposal 1>
Proposal 1 is a proposal for solving the above problem 1.

Multiple CG PUSCH occasions within one CG period may be determined based on the TDRA of the first indicated/set CG PUSCH occasion and the number of CG PUSCH occasions within one CG period.

For type 1 CG PUSCH, the number of CG PUSCH occasions within one CG period may be configured in the CG configuration.

For type 2 CG PUSCH, the number of CG PUSCH occasions within one CG period may be configured in the CG configuration or may be indicated by the activation DCI. If the number of CG PUSCH occasions within one CG period is indicated by the activation DCI, the following options are applicable:

(Option 1)
A new field may be provided in the activation DCI to indicate the number of CG PUSCH occasions in one CG period.

(example)
The new field may directly indicate the number of CG PUSCH occasions in one CG period, and indicates one of several configured values.

(Option 2)
An existing field in the activation DCI may be used to indicate the number of CG PUSCH occasions in one CG period.

(example)
Any unused fields in the Activation DCI can be reused. If there are multiple NDI bits in the Activation DCI, any of the NDI bits may be used.

(Note)
If the TDRA table configured for DCI 0_1 contains at least one row with multiple SLIVs, then DCI 0_1 has multiple NDI bits. Considering that NDI bits are not used for CG activation, these bits can be reused.

(Option 3)
An extended TDRA table may be used with a column containing "number of CG PUSCH occasions in one CG period."

In this case, in addition to parameters such as slot/mapping type/start symbol/length, the number of CG PUSCH occasions within one CG period can also be derived.

(Option 4)
If there is a "number of PUSCH repetitions" in the TDRA table, it may be reinterpreted.

Whether or not to reinterpret the parameters may be determined by RRC configuration or activation DCI indication.

(Example 1)
If the parameter multi-PUSCH-CG is configured (as "ENABLED") in configuredGrantConfig or rrc-ConfiguredUplinkGrant, the "number of PUSCH repetitions" indicated by the TDRA row index is taken as the number of CG PUSCH occasions in one slot. Otherwise the conventional behavior applies.

(Example 2)
If the activation DCI explicitly indicates that multiple CG PUSCHs are applied in the CG configuration, the "number of PUSCH repetitions" indicated by the TDRA row index is taken as the number of CG PUSCH occasions in one slot. Otherwise, the conventional behavior applies.

Explicit indication of multiple CG PUSCHs by the activation DCI can be done via a new DCI field or an existing DCI field (e.g., the NDI bit).

(Variations)
In option 4 above, the "number of PUSCH repetitions" can be replaced with the "number of slots".

<Proposal 2>
Proposal 2 is a proposal for solving the above problem 2.

In case of type 1 CG PUSCH and/or type 2 CG PUSCH with multi-PUSCHs CG, i.e. when the specified or configured number of CG PUSCH occasions within one CG period is greater than one, the "counting of available CG PUSCH occasions (or counting of available slots) procedure" does not apply.

Note that the "procedure for counting available CG PUSCH occasions (or counting available slots)" for multi-PUSCHs CG may mean any of the following examples:

(Example 1)
If at least one symbol of a CG PUSCH occasion overlaps with a DL symbol indicated in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or with a symbol of an SS/PBCH block with an index provided by ssb-PositionsInBurst, the CG PUSCH occasion is not counted in the number of CG PUSCH occasions in one CG period.

(Example 2)
A slot is not counted in the number of CG PUSCH occasions within one CG period if at least one of the symbols indicated by the row index of the used resource allocation table in a slot overlaps with a DL symbol indicated in tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or with a symbol of an SS/PBCH block with an index provided by ssb-PositionsInBurst.

Whether or not the "Available CG PUSCH Occasion Counting (or Available Slot Counting) Procedure" (hereinafter simply referred to as the "Counting Procedure") is applied may be determined by one of the following alternations:

(Alt 1)
Whether or not a counting procedure is applied may be determined by the specification.

For example, if there are multiple CG PUSCH occasions within a CG period (or if the number of CG PUSCH occasions within a CG period is greater than one), the counting procedure does not always apply.

(Alt 2)
Whether the counting procedure is applied may be determined by the RRC configuration (eg, the existing parameter AvailableSlotCounting or another parameter AvailablePuschOccasionCounting).

For example, if AvailableSlotCounting (or AvailablePuschOccasionCounting) is set, the counting procedure is applied, otherwise the counting procedure is not applied.

(Alt 3)
Whether or not the counting procedure applies may be determined by the indication of the activation DCI.

For example, if the activation DCI indicates a count of available CG PUSCH occasions/slots, the counting procedure applies, otherwise the counting procedure does not apply.

(Note)
When the counting procedure does not apply, this may mean:

The terminal determines M consecutive slots for M CG PUSCH occasions within one CG period and the specified TDRA applies to each slot. CG PUSCH occasions may be canceled in accordance with Sections 11.1 and 11.1.1 of TS 38.213.

<Variations of the Overall Embodiment>
(Variation 1)
For type 1 CG PUSCH and/or type 2 CG PUSCH, the terminal does not assume that the number of CG PUSCH occasions in one CG period (or the number of slots of multiple CG PUSCHs in one CG period) is set/indicated to be greater than the period P.

(Variation 2)
In Proposal 2, when the counting procedure is applied, the following alternations may be applied:

(Alt 1)
If the counting procedure is applied, the terminal shall not assume that the duration of multiple CG PUSCH occasions within one CG period after applying the counting procedure is greater than the periodicity P.

(Alt 2)
If a counting procedure is applied, the CG PUSCH occasions in one CG period are determined until the number of CG PUSCH occasions in one CG period is reached or until the last slot in the CG period is reached.

(Variation 3)
The perspective used may be based on any of the following:
- It is set by higher layer parameters - It is reported by the terminal as UE capability - It is described in the specification - It is determined by the setting of higher layer parameters and the reported UE capability (a combination of the above decisions)

<Summary of proposal>
With the above configuration, when Alt-A1 is applied, the terminal can perform appropriate communication. In addition, the base station and the terminal can use resources efficiently.

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

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

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 regarding signal transmission from 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.

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

The receiving unit 102 receives an uplink (UL) signal transmitted from the terminal 20. For example, the receiving unit 102 receives a 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 transmission unit 101. The control unit 103 also outputs data and control information received from the reception 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 a signal (e.g., data and control information, etc.) received from the terminal 20 and/or data and control information, etc. acquired from a higher layer. Information regarding the allocated resources may be included in the control information to be 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 related to PUCCH settings such as a PUCCH cell timing pattern (PUCCH setting information) may be notified to the terminal 20 by RRC.

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

The receiving unit 201 receives a DL signal transmitted from the base station 10. For example, the receiving unit 201 receives a 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 channels include the Physical Uplink Shared Channel (PUSCH), and the control channels include the Physical Uplink Control Channel (PUCCH). For example, the terminal 20 receives control information from the base station 10 using the PUCCH, and transmits uplink data signals using the PUSCH.

The reference signal 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 process in the receiving unit 201 and the transmitting process in the transmitting unit 202.

For example, the control unit 203 acquires information such as data and control information from a higher layer and outputs it to the transmission unit 202. The control unit 203 also outputs, for example, data and control information received from the reception unit 201 to the higher 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 (Channel. State Information (CSI)), or a scheduling request (Scheduling Request (SR)). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted in the resources of the PUCCH.

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 channel used to transmit DL signals and the channel used to transmit UL signals are not limited to the above examples. For example, the channel used to transmit DL signals and the channel used to transmit 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, for example, a Random Access Radio Network Temporary Identifier (RA-RNTI).

The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as necessary, and items described in one item may be applied to items described in another item (as long as they do not contradict each other).

<Hardware configuration, etc.>
The block diagrams used in the description of the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (for example, using wires, wirelessly, etc.). The functional blocks may be realized by combining the one device or the multiple devices with software.

Functions include, but are not limited to, judgement, determination, judgment, 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 the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for either of these.

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. FIG. 10 is a diagram showing an example of the hardware configuration of a base station and a terminal in an embodiment. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

The functions of the base station 10 and the terminal 20 are realized by loading specific software (programs) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communications by the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

The processor 1001, for example, operates 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 device, an arithmetic unit, registers, etc. For example, the above-mentioned control unit 103 and control unit 203, etc. may be realized by the processor 1001.

The processor 1001 also reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. For example, the control unit 203 of the terminal 20 may be realized by a control program stored in the memory 1002 and running on the processor 1001, and similarly may be realized for other functional blocks. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may 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 a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), etc. Memory 1002 may also be called a register, a cache, a main memory, etc. Memory 1002 can store executable programs (program codes), 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, 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 (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a 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, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For example, the above-mentioned transmitting unit 101, receiving unit 102, receiving unit 201, and transmitting unit 202 may be realized by the communication device 1004.

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output 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 embodiment 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 combinations thereof. In addition, the RRC signaling may be called 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 include Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), Future Radio Access (FRA), new Radio (NR), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (WiMAX (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (WiMAX (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark)), IEEE 802.35 (WiMAX (registered The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), and other suitable systems, and next-generation systems that are expanded, modified, created, or defined based on these systems. In addition, the present invention may be applied to a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.).

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

<Base station operation>
In the present disclosure, a specific operation 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 other network nodes other than the base station (e.g., MME or 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, it may be a combination of multiple other network nodes (e.g., MME and S-GW).

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

<Handling of input/output information, etc.>
The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

<Judgment method>
The determination may be 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.>
Each aspect/embodiment described in the present disclosure may be used alone, in combination, or switched according to execution. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the predetermined information).

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

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

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then at least one of these wired and wireless technologies is included within the definition of a transmission medium.

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

Note that the terms explained in this disclosure and the terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Furthermore, the 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>
In addition, the information, parameters, etc. described in the present disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, a radio resource may be indicated by an index.

The names used for the above-mentioned parameters are not limiting in any respect. Furthermore, the 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 limiting in any respect.

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

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 provide communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head). The term "cell" or "sector" refers to a part or the entire coverage area of at least one of the base station and base station subsystems that provide communication services in this coverage.

<Mobile Station>
In this disclosure, the terms "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. 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 called 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 moving object, the moving object itself, etc. The moving object refers to an object that can move, and the moving speed is arbitrary. It also naturally includes the case where the moving object is stopped. The moving object includes, but is not limited to, for example, a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an artificial satellite, a drone (registered trademark), a multicopter, a quadcopter, a balloon, and objects mounted thereon. The moving object may also be a moving object that runs autonomously based on an operation command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving object (e.g., a drone, an automatic driving vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

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

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

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

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

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

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

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

The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that perform output to the outside.

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

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

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

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

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

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

<Terminology and interpretation>
The terms "determining" and "determining" as used in this disclosure 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 in 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 a memory), and the like. "Determining" and "determining" may also include resolving, selecting, choosing, establishing, comparing, and the like. In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Also, "judgment (decision)" may be interpreted as "assuming,""expecting,""considering," etc.

The terms "connected" and "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 at least one of one or more wires, cables, and 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">
Any reference to an element using a designation such as "first,""second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.

<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." Further, when used in this disclosure, the term "or" 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, a particular filtering process performed by the transceiver in the frequency domain, a particular windowing process performed by the transceiver in the time domain, etc.

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

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

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name that corresponds to the 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.

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

Note that when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) that constitute the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, short 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 the TTI length of a long TTI and equal to or greater than 1 ms.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers included in an RB may be determined based on the 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 be composed 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.

Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource area 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 an index of the RB relative to a common reference point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

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

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 "cell," "carrier," etc. in this disclosure may be read as "BWP."

The above-mentioned 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, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

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

＜Article＞
In this disclosure, where articles have been added due to translation, such as, for example, 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."

This patent application claims priority based on Japanese Patent Application No. 2023-084215, filed on May 22, 2023, and the entire contents of Japanese Patent Application No. 2023-084215 are incorporated herein by reference.

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

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

Claims (6)

A receiving unit for receiving a parameter for setting an upstream signal transmission opportunity;
a control unit that determines the transmission opportunity based on the parameter setting and symbol information indicating a start symbol and a symbol length of the transmission opportunity that is included in a downlink control signal;
having
the number of transmission opportunities configured within a particular time period is determined based on a time domain resource allocation of the initially indicated/configured transmission opportunity;
Terminal. The number of transmission opportunities is indicated in the downlink control signal.
The terminal according to claim 1. A new field is provided in the downlink control signal to indicate the number of transmission opportunities.
The terminal according to claim 2. an existing field of the downstream control signal is used to indicate the number of transmission opportunities;
The terminal according to claim 2. If at least one symbol of the transmission opportunity overlaps with a downlink symbol indicated by a higher layer parameter, the transmission opportunity is not counted in the number of transmission opportunities set within the specific period.
The terminal according to claim 1. The device is
receiving parameters for setting an upstream signal transmission opportunity;
determining the transmission opportunity based on the parameter setting and symbol information indicating a start symbol and a symbol length of the transmission opportunity included in a downlink control signal;
the number of transmission opportunities configured within a particular time period is determined based on a time domain resource allocation of the initially indicated/configured transmission opportunity;
Communication methods.

Images