Terminal and communication method
The terminal and communication method address the challenge of uplink signal retransmissions in 5G and NR systems by scheduling retransmissions based on downlink control signals and utilizing advanced carrier switching and PUSCH retransmission techniques, thereby reducing latency and improving throughput for XR applications.
Patent Information
- Application Number
- PCT/JP2024/017656
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-24
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-28
AI Technical Summary
Current communication systems, particularly in the context of 5G and NR, face challenges in efficiently handling retransmissions of uplink signals due to limitations in time domain resource allocation and HARQ-ACK feedback latency, which are critical for meeting the low latency and high throughput requirements of applications like XR.
A terminal and communication method that includes a receiving unit for downlink control signals indicating start and length of uplink signals in a time domain resource allocation table, and a control unit that schedules retransmissions based on permitted configurations, enabling appropriate retransmission of uplink signals by utilizing dynamic and semi-static PUCCH carrier switching and enhanced CG PUSCH retransmission scheduling.
This approach reduces latency and improves the efficiency of uplink signal retransmissions, enhancing the system's ability to meet the low latency and high throughput demands of XR applications and supporting dynamic PUCCH carrier switching and multiple CG PUSCH transmission occasions.
Smart Images

Figure JP2024017656_28112024_PF_FP_ABST
Abstract
Description
Terminal and communication method
[0001] The present disclosure relates to a terminal and a communication method.
[0002] Long Term Evolution (LTE) has been specified for Universal Mobile Telecommunication System (UMTS) networks to achieve higher data rates and lower latency. Furthermore, successor systems to LTE are also being considered to achieve even greater bandwidth and speed than LTE. Examples of successor systems to LTE include LTE-Advanced (LTE-A), Future Radio Access (FRA), 5th generation mobile communication system (5G), 5G plus (5G+), Radio Access Technology (New-RAT), and New Radio (NR).
[0003] In 5G, various wireless technologies and network architectures are being studied to meet the requirements of achieving a throughput of 10 Gbps or more while reducing wireless section latency to 1 ms or less (for example, Non-Patent Document 1).
[0004] In NR, Release 16 specifies the configuration of a configured grant physical uplink shared channel (CG PUSCH) (see, for example, Non-Patent Document 2). The CG PUSCH includes a Type 1 CG PUSCH and a Type 2 CG PUSCH.
[0005] Release 17 examines 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 include capacity, latency, mobility, and energy saving.
[0006] 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, 20223GPP TS38.214 V17.5.0 (2023-03)3GPP TS38.331 V17.1.0 (2022-06)
[0007] However, the handling of retransmission of upstream signals has not been sufficiently studied, and further study is required.
[0008] One aspect of the present disclosure is to provide a terminal and a communication method that appropriately retransmit an uplink signal.
[0009] A terminal according to one aspect of the present disclosure includes a receiving unit that receives a downlink control signal indicating one or more pieces of information regarding the start symbol and length of an uplink signal within a row of a time domain resource allocation table, and a control unit that schedules retransmission of the uplink signal that has been permitted to be set based on the downlink control signal.
[0010] A communication method according to one aspect of the present disclosure comprises a terminal receiving a downlink control signal indicating one or more pieces of information regarding the start symbol and length of an uplink signal within a row of a time-domain resource allocation table, and scheduling retransmission of the uplink signal that has been granted permission based on the downlink control signal.
[0011] FIG. 1 is a diagram showing an example of dual connectivity (DC). FIG. 2 is a diagram showing an example of PUCCH carrier switching. FIG. 3 is a diagram explaining agreements regarding time domain resource allocation (TDRA) at the RAN1#112 meeting. FIG. 4 is a diagram explaining resource allocation in the time domain of Rel-17. FIG. 5 is a diagram explaining PUSCH transmission. FIG. 6 is a diagram showing an example of specifications. FIG. 7 is a diagram explaining Proposal 2 - Option 1. FIG. 8 is a block diagram showing an example of the configuration of a base station. FIG. 9 is a block diagram showing an example of the configuration of a terminal. FIG. 10 is a diagram showing an example of the hardware configuration of a base station and a terminal according to the present embodiment. FIG. 11 is a diagram showing an example of the configuration of a vehicle.
[0012] Hereinafter, an embodiment according to one aspect of the present disclosure will be described with reference to the drawings. In URLLC, enhancements to terminal feedback for Hybrid Automatic Repeat request-Acknowledgement (HARQ-ACK) are being considered. HARQ-ACK is an example of information regarding an acknowledgement (e.g., an acknowledgement) for data received by a terminal. In response to these URLLC considerations, it has been agreed to support dynamic and semi-static PUCCH carrier switching. Note that PUCCH carrier switching may also be called by other names, such as control information transmission carrier switching.
[0013] PUCCH carrier switching is a technique applied when a base station communicates via multiple cells. Dual connectivity, which is an example of communication via multiple cells, and PUCCH carrier switching will be described below.
[0014] <Dual Connectivity> Figure 1 is a diagram showing an example of dual connectivity (DC). In the example of Figure 1, the base station 10-1 may be a master node (MN). The base station 10-2 may be a secondary node (SN). As shown in the example of Figure 1, in DC, carriers between different base stations are aggregated.
[0015] 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.
[0016] In the case of DC, since there may be a delay in communication between the base station 10-1 and the base station 10-2, it is difficult to notify the base station 10-2 of the uplink control information (e.g., Uplink Control Information (UCI)) received by the Pcell of the base station 10-1 via a backhaul link (e.g., a wired or wireless link connecting the base station 10-1 and the base station 10-2) and reflect it in the scheduling of the Scell under the base station 10-2. Therefore, in DC, in addition to the Pcell of the base station 10-1, one carrier under the base station 10-2 may be set as the Primary Scell (PScell), and PUCCH transmission may be supported by the PScell. In this case, the terminal 20 transmits UCI to the base station 10-2 via the PScell.
[0017] In the example of FIG. 1, the terminal 20 configures an Scell in addition to a Pcell for the base station 10-1. The terminal 20 also configures an Scell in addition to a PScell for the base station 10-2. The terminal 20 transmits UCI of each carrier under the control of the base station 10-1 on the PUCCH of the Pcell. The terminal 20 also transmits UCI of each carrier under the control of the base station 10-2 on the PUCCH of the PScell. In the example of FIG. 1, the cell group (CG) under the control of the base station 10-1 may be referred to as a Master Cell-Group (MCG). The cell group under the control of the base station 10-2 may be referred to as a Secondary Cell-Group (SCG).
[0018] When DC is performed, terminal 20 may transmit PUCCH via a Pcell, a PScell, and / or a PUCCH-Scell. Generally, it is not expected that terminal 20 transmits PUCCH via an Scell other than a Pcell, a PScell, and a PUCCH-Scell.
[0019] <PUCCH Carrier Switching> PUCCH carrier switching is being studied as a method for reducing the latency of HARQ-ACK feedback in the Time Division Duplex (TDD) system.
[0020] Fig. 2 is a diagram showing an example of PUCCH carrier switching. In the example of Fig. 2, a base station and a terminal communicate via cell 1 and cell 2. In the example of Fig. 2, cell 1 is a Pcell, and cell 2 is an Scell. The example of Fig. 2 also shows downlink (DL) slots and uplink (UL) slots in each cell.
[0021] In the example of FIG. 2 , the terminal receives data at timing S101 (receives a Physical Downlink Shared Channel (PDSCH)). The terminal attempts to transmit a HARQ-ACK for the data received at timing S101 at timing S102, but at timing S102, the slot of cell 1 is a downlink (DL) slot. Therefore, when the terminal transmits a HARQ-ACK in cell 1, the transmission of the HARQ-ACK is postponed until the transmission timing of the PUCCH in the uplink (UL) slot (e.g., timing S103 in FIG. 2 ), which increases the latency of the HARQ-ACK transmission. Note that the transmission timing of the PUCCH in the uplink (UL) slot may also be referred to as a PUCCH transmission opportunity.
[0022] In the example of Fig. 2, at timing S102, the slot of cell 2 is a UL slot. In the example of Fig. 2, if the terminal can transmit a HARQ-ACK for the data received at S101 at the PUCCH transmission opportunity at timing S102 of cell 2, the latency of the HARQ-ACK transmission can be reduced. URLLC requires low latency, particularly in the wireless section. For this reason, 3GPP is considering PUCCH carrier switching, in which a terminal switches the carrier on which it transmits PUCCH, as an extension of URLLC technology.
[0023] In the following embodiments, "the same timing" may mean the exact same timing, or may mean that all or part of a time resource (for example, one or more symbols (which may be a resource with a time unit shorter than a symbol)) is the same or overlaps.
[0024] PUCCH carrier switching may refer to the case where, when a terminal attempts to transmit a PUCCH at a specific transmission timing of a Pcell (which may be a PScell or a PUCCH-Scell), the slot of the specific transmission timing of the Pcell (which may be a PScell or a PUCCH-Scell) is a DL slot, and therefore the terminal switches the cell from which the PUCCH is transmitted from the Pcell (which may be a PScell or a PUCCH-Scell) to one of one or more Scells in which the slot with the same timing as the specific transmission timing is a UL slot (in the case of a PScell, an Scell other than the PScell, and in the case of a PUCCH-Scell, an Scell other than the PUCCH-Scell). Note that, in embodiments of the present invention, the unit of the specific transmission timing is not limited to a slot. For example, the specific transmission timing may be a timing in units of a subframe or a timing in units of a symbol.
[0025] Two methods are being considered for realizing PUCCH carrier switching. The first method is a method in which a base station dynamically instructs a terminal on a carrier for transmitting the PUCCH. The second method is a method in which a base station semi-statically sets a terminal on a carrier for transmitting the PUCCH. Note that in the following embodiments, "transmitting a PUCCH" and "transmitting a PUCCH" may refer to transmitting uplink control information via a PUCCH.
[0026] The terminal may notify the base station of terminal capability information (UE capability) that defines information about the terminal's capabilities regarding PUCCH transmission.
[0027] For example, information indicating whether the terminal supports switching of settings related to transmission of control information may be defined as the terminal capability information of the terminal. Switching of settings related to transmission of control information may be, for example, switching of resources (e.g., carriers or cells) used for transmitting the control information. Switching of resources used for transmitting the control information may be referred to as "PUCCH carrier switching." Furthermore, information indicating application of dynamic PUCCH carrier switching and / or semi-static PUCCH carrier switching may be defined as the terminal capability information of the terminal.
[0028] The configuration operation of quasi-static PUCCH carrier switching may be based on the RRC setting of the PUCCH cell timing pattern of the PUCCH cell to which quasi-static PUCCH carrier switching applies, and the configuration operation of quasi-static PUCCH carrier switching may be supported between cells of different numerologies.
[0029] In PUCCH carrier switching, PUCCH resources may be configured for each UL BWP (Uplink Bandwidth Part) (for example, for each candidate cell and the UL BWP of the candidate cell).
[0030] In the case of PUCCH carrier switching based on dynamic instruction of control information, the K1 value (offset) from PDSCH to HARQ-ACK may be interpreted based on the numerology of the dynamically instructed target PUCCH cell. Note that the control information may be control information for scheduling PUCCH, such as Downlink control information (DCI). The numerology may also be considered as slot or Subcarrier Spacing (SCS).
[0031] <Configured Grant Enhancements (CG Enhancements) in Rel-18 XR> RP-223502 (Non-Patent Document 3), a Work Item Description (WID) for Rel-18, describes capacity-related enhancements. For example, one of the enhancements describes multiple CG PUSCH transmissions during a single CG PUSCH configuration period. Therefore, in Rel-18, multiple CG PUSCH transmission occasions can be supported in one CG period. A CG PUSCH transmission occasion may also be referred to as a CG PUSCH occasion or a CG occasion.
[0032] Note that 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 independent of DCI.
[0033] The transmission parameters of the Type 2 CG PUSCH are provided by "configuredGrantConfig", "pusch-Config", and "activation DCI". Activation and deactivation of the Type 2 CG PUSCH depend on the RRC-configuration and DCI. One DCI can activate one CG PUSCH and deactivate multiple CG PUSCHs. The Type 1 CG PUSCH may be referred to as Type 1 CG. The Type 2 CG PUSCH may be referred to as Type 2 CG.
[0034] <TDRA for Multi-PUSCHs CG (Agreement at RAN1#112 Meeting)> Figure 3 explains 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 PUSCHs related to multi-PUSCHs CG.
[0035] <Restrictions on CG retransmission scheduling> Fig. 4 is a diagram explaining resource allocation in the time domain in Rel-17. As shown in Fig. 4, section 6.1.2.1 of TS38.214 (Non-Patent Document 4) specifies resource allocation in the time domain.
[0036] When extendedK2 is configured in pusch-TimeDomainAllocationListForMultiPUSCH including multiple SLIVs in one or more rows for a PUSCH on the UL BWP of the serving cell, PUSCH retransmission is indicated by DCI format 0_1, and the PUSCH corresponds to CG type 1 or CG type 2, the terminal does not expect that the number of SLIVs indicated in a row of pusch-TimeDomainAllocationListForMultiPUSCH by the DCI is multiple. In other words, when DCI format 0_1 indicates multiple SLIVs, the terminal does not expect DCI format 0_1 to schedule CG PUSCH retransmission. Expectation may be rephrased as expectation or assumption.
[0037] Note that SLIV is an abbreviation for Start and Length Indicator Value. extendedK2 is a parameter that gives K2, which is information indicating the offset from the slot in which DCI is received to the slot to which PUSCH is allocated. pusch-TimeDomainAllocationListForMultiPUSCH is a parameter for setting a TDRA table for multiple PUSCHs (Non-Patent Document 5).
[0038] <PUSCH Transmission> Fig. 5 is a diagram illustrating PUSCH transmission. As shown in Fig. 5, Section 6.1 of TS38.214 (Non-Patent Document 4) specifies application of HARQ process IDs (HP IDs) to multiple PUSCHs scheduled by a single DCI.
[0039] For example, if multiple PUSCHs are scheduled for a terminal by DCI, the HP ID indicated by this DCI is applied to the first PUSCH that does not overlap with the DL symbol indicated by the next parameter (if provided). The parameter is tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. Also, if multiple PUSCHs are scheduled for a terminal by DCI, the HP ID indicated by this DCI is applied to the first PUSCH that does not overlap with the symbol of the SS / PBCH block having the index provided by ssb-PositionsInBurst. Thereafter, the HP ID is incremented by 1 for each subsequent PUSCH in the scheduled order, and the applied modulo operation varies depending on the provided parameter.
[0040] For a PUSCH that is not transmitted, the HP ID is not incremented if at least one of the symbols indicated by the indexed row of the used resource allocation table within a slot overlaps with a DL symbol indicated by the above parameter (if provided), and for a PUSCH that is not transmitted, the HP ID is not incremented if at least one of the symbols indicated by the indexed row of the used resource allocation table within a slot overlaps with a symbol of the SS / PBCH block whose index is provided by ssb-PositionsInBurst.
[0041] Section 6.1 of TS38.214 also specifies that out-of-order scheduling is not permitted. For example, except in certain cases, a terminal does not expect to be scheduled to transmit a PUSCH that starts before the end of the first PUSCH by a PDCCH that ends after symbol i of the scheduling cell.
[0042] Also, Section 6.1 of TS38.214 specifies that HP ID collisions are not permitted. For example, the terminal does not expect that another PUSCH transmission with DCI for a particular HARQ process will be scheduled with DCI received before the end of the expected transmission of the last PUSCH for that HARQ process.
[0043] Analysis: In Rel-17, CG PUSCH retransmissions are not allowed to be scheduled by DCIs indicating multiple SLIVs in a TDRA row.
[0044] In Rel-18, when multiple CG occasions are supported within one CG period, it may be useful if one DCI can schedule retransmissions for multiple transport blocks (TBs) whose initial transmissions are in the same CG period.
[0045] Therefore, it is beneficial to support retransmissions corresponding to CGs scheduled by DCIs indicating multiple SLIVs.
[0046] <Proposal 1> Proposal 1 supports retransmissions corresponding to CGs scheduled by DCIs indicating multiple SLIVs. Proposal 1 includes Option 1 and Option 2.
[0047] <Proposal 1 - Option 1> Retransmissions corresponding to any type 1 CG or type 2 CG are scheduled by DCI format 0_1 indicating one or more SLIVs in the TDRA row.
[0048] Proposal 1-Option 1 may be defined by a specification. FIG. 6 is a diagram illustrating an example of the specification. Proposal 1-Option 1 may be defined by Section 6.1.2.1 of TS38.214, as shown in FIG. 6. The terminal may expect that the number of indicated SLIVs in a row of pusch-TimeDomainAllocationListForMultiPUSCH by the DCI is one or more. In other words, if the DCI indicates one or more SLIVs, the terminal may expect the DCI to schedule a retransmission of the CG PUSCH. The DCI format may be DCI format 0_1.
[0049] <Proposal 1 - Option 2> Retransmissions corresponding to only type 1 CG or type 2 CG with multiple PUSCHs CG within one CG period are scheduled by DCI indicating one or more SLIVs in the TDRA row. For retransmissions corresponding to type 1 CG or type 2 CG with single PUSCH CG within one CG period, DCI is not expected to indicate one or more SLIVs in the TDRA row.
[0050] Proposal 1-Option 2 may be specified by a specification. FIG. 7 is a diagram showing an example of the specification. Proposal 1-Option 2 may be specified by Section 6.1.2.1 of TS38.214, as shown in FIG. 7. When extendedK2 is configured in pusch-TimeDomainAllocationListForMultiPUSCH, which includes multiple SLIVs in one or more rows, for a PUSCH on the UL BWP of the serving cell, PUSCH retransmission is indicated by DCI format 0_1, and the PUSCH corresponds to CG type 1 or CG type 2 with one single PUSCH CG in one CG period, the terminal does not expect the number of SLIVs indicated in a row of pusch-TimeDomainAllocationListForMultiPUSCH by the DCI to be multiple. If the PUSCH corresponds to CG type 1 or CG type 2, which has multiple PUSCH CGs within one CG period, the terminal may expect the number of SLIVs indicated by the DCI in a row of pusch-TimeDomainAllocationListForMultiPUSCH to be one or more.
[0051] <Proposal 2> If DCI format 0_1 configured in the multi-PUSCH TDRA table scrambled by CS-RNTI indicates a TDRA row index with multiple SLIVs in the row, the following Proposal 2-Option 1 to Proposal 2-Option 3 may be applied.
[0052] <Proposal 2 - Option 1> The NDI (New Data Indicator) bit is used to indicate whether a retransmission TB is scheduled for the corresponding SLIV or resource allocation. The NDI may be included in, for example, the DCI.
[0053] In the case of an SLIV (or PUSCH resource allocation) with an NDI bit of '1', a PUSCH is scheduled for a retransmission TB corresponding to type 1 CG or type 2 CG.
[0054] In the case of an SLIV (or PUSCH resource allocation) with an NDI bit of '0', the terminal does not transmit on the PUSCH, i.e., the terminal considers that the PUSCH allocation is not scheduled in any TB.
[0055] Figure 8 is a diagram illustrating Proposal 2 - Option 1. As shown in Figure 8, DCI scrambled by CS-RNTI schedules multiple PUSCHs #1, #2, #3, and #4 for retransmission TBs. The terminal transmits retransmission TBs on PUSCHs #1 and #4 with the NDI bit set to "1". The terminal does not transmit retransmission TBs on PUSCHs #1 and #4 with the NDI bit set to "0". The terminal considers PUSCHs #1 and #4 with the NDI bit set to "0" as not being scheduled for transmission of retransmission TBs. In the example of Figure 8, one PUSCH is allocated per slot.
[0056] Note that CS-RNTI is an abbreviation for Configured Scheduling Radio Network Temporary Identifier. The DCI format may be DCI format 0_1.
[0057] Variation: The terminal does not expect to detect DCI format 0_1 scrambled by a CS-RNTI indicating multiple SLIVs in the TDRA row, and the number of NDI bits indicating "1" is equal to one.
[0058] If the terminal detects DCI format 0_1 scrambled by CS-RNTI indicating multiple SLIVs in a TDRA row, the terminal expects the number of NDI bits indicating "1" to be greater than one.
[0059] The terminal does not expect to detect DCI format 0_1 scrambled by CS-RNTI indicating multiple SLIVs in the TDRA row, and the number of PUSCH resource allocations that do not overlap with quasi-static DL symbols or SSB symbols is equal to 1. The quasi-static DL symbols may be indicated, for example, by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. The SSB symbols may be, for example, symbols of the SS / PBCH block with an index provided by ssb-PositionsInBurst.
[0060] If the terminal detects DCI format 0_1 scrambled by CS-RNTI indicating multiple SLIVs in a TDRA row, the terminal expects the number of PUSCH resource allocations that do not overlap with quasi-static DL symbols or SSB symbols in the row to be greater than one.
[0061] The terminal does not expect to detect DCI format 0_1 scrambled by CS-RNTI indicating multiple SLIVs in a TDRA row, and the number of PUSCH resource allocations that do not overlap with quasi-static DL symbols or SSB symbols and the number of PUSCH resource allocations that do not overlap with NDI bits corresponding as "1" is greater than 1.
[0062] If the terminal detects DCI format 0_1 scrambled by CS-RNTI indicating multiple SLIVs in a TDRA row, the terminal expects that the number of PUSCH resource allocations that do not overlap with quasi-static DL symbols or SSB symbols and the number of PUSCH resource allocations that do not overlap with NDI bits corresponding as "1" are greater than 1.
[0063] <Proposal 2 - Option 2> The HP ID indication and HP ID increment only apply to PUSCHs scheduled in retransmitted TBs.
[0064] (1) The HP ID indication applies to the first PUSCH allocation scheduled with a retransmission TB (or the corresponding NDI bit is '1') that does not overlap with a quasi-static DL symbol or SSB symbol.
[0065] (2) The HP ID is not incremented for unscheduled PUSCHs. The HP ID is incremented only for PUSCH allocations that are scheduled with a retransmission TB (or the corresponding NDI bit is '1') and do not overlap with quasi-static DL or SSB symbols (A).
[0066] <Proposal 2 - Option 3> Out-of-order scheduling is not considered for PUSCHs where no TB is scheduled.
[0067] For example, a terminal may be scheduled to transmit a PUSCH that starts earlier than the end of the first PUSCH by a PDCCH that ends after symbol i of the scheduling cell if the first PUSCH is one of multiple PUSCHs scheduled by a PDCCH scrambled with CS-RNTI, indicates multiple SLIVs in the TDRA row, and the NDI bit of the first PUSCH is indicated as '0'.
[0068] No TB is considered to override the CG for a scheduled PUSCH.
[0069] For example, if DCI format 0_1 scrambled by CS-RNTI indicates multiple SLIVs in a TDRA row, and one PUSCH of multiple PUSCH allocations is indicated by a corresponding NDI bit "0", the terminal may transmit a CG PUSCH overlapping with the PUSCH.
[0070] For a PUSCH for which no TB is scheduled, if an HP ID is assigned to a PUSCH for which no TB is scheduled (i.e., if (2) in Proposal 2 - Option 2 is not adopted), the HP ID and / or applicable collisions are not taken into account.
[0071] For example, if DCI format 0_1 scrambled by CS-RNTI indicates multiple SLIVs in a TDRA row and one PUSCH of multiple PUSCH allocations is indicated by a corresponding NDI bit of "0", the terminal may transmit a PUSCH having the same HP ID as the HP ID determined for the PUSCH.
[0072] <UE capability> The terminal may report the following terminal capability information to the base station.
[0073] - Information defining whether the terminal supports DCI format 0_1 for scheduling retransmissions corresponding to type 1 CG or type 2 CG when DCI format 0_1 indicates multiple SLIVs in a TDRA row. - Information defining whether the terminal supports DCI format 0_1 for scheduling retransmissions corresponding to type 1 CG or type 2 CG with multiple CG occasions within one CG period when DCI format 0_1 indicates multiple SLIVs in a TDRA row. - Information defining whether the terminal supports DCI format 0_1 for scheduling retransmissions corresponding to type 1 CG or type 2 CG with a single CG occasion within one CG period when DCI format 0_1 indicates multiple SLIVs in a TDRA row.
[0074] <Variations> Which proposals and options are used may be configured by parameters of higher layer signaling. Which proposals and options are used may be reported by the terminal as terminal capabilities. The behavior of the proposals and options may be specified in the specification. Which proposals and options are used may be defined by a specification. Which proposals and options are used may be defined by a combination of parameters of higher layer signaling, terminal capabilities, and a specification.
[0075] The above-mentioned multiple SLIVs (multi SLIVs) may be replaced with multiple S and L values or resource allocation of multiple PUSCHs. One SLIV (single SLIV) may be replaced with one S and L value or resource allocation of a single PUSCH.
[0076] A quasi-static DL symbol, if provided, may be considered equivalent to a symbol indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated. An SSB symbol may be considered equivalent to a symbol in the SS / PBCH block with an index provided by ssb-PositionsInBurst. SS stands for Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS). PBCH stands for Physical Broadcast Channel.
[0077] Retransmissions corresponding to one or both of type 1 CG and type 2 CG may be scheduled by DCI format 0_1 indicating one or more SLIVs in the TDRA row.
[0078] Retransmissions corresponding to one or both of type 1 CG and type 2 CG with multiple PUSCHs CG within one CG period may be scheduled by DCI indicating one or more SLIVs in a TDRA row. For retransmissions corresponding to one or both of type 1 CG and type 2 CG with single PUSCH CG within one CG period, DCI may not be expected to indicate one or more SLIVs in a TDRA row.
[0079] <Configuration of Base Station> Fig. 9 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. 10) by radio.
[0080] 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.
[0081] The DL signal may include, for example, a downlink data signal and control information (e.g., Downlink Control Information (DCI)). The DL signal may also include information indicating scheduling related to signal transmission of the terminal 20 (e.g., an UL grant). The DL signal may also include control information of higher layers (e.g., control information of Radio Resource Control (RRC)). The DL signal may also include a reference signal.
[0082] The channels used for transmitting DL signals include, for example, a data channel and a control channel. For example, the data channel may include a PDSCH (Physical Downlink Shared Channel), and the control channel may include a PDCCH (Physical Downlink Control Channel). For example, the base station 10 transmits control information to the terminal 20 using the PDCCH and transmits downlink data signals using the PDSCH.
[0083] The reference signal included in the DL signal may include at least one of a demodulation reference signal (Demodulation Reference Signal (DMRS)), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information. For example, reference signals such as DMRS and PTRS are used for demodulating downlink data signals and are transmitted using the PDSCH.
[0084] 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.
[0085] 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 .
[0086] For example, the control unit 103 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 101. The control unit 103 also outputs the data, control information, etc. received from the receiving unit 102 to the upper layer.
[0087] For example, the control unit 103 allocates resources (or channels) used for transmitting and receiving DL signals and / or resources used for transmitting and receiving UL signals based on signals (e.g., data and control information, etc.) received from the terminal 20 and / or data and control information, etc. acquired from a higher layer. Information on the allocated resources may be included in control information transmitted to the terminal 20.
[0088] The control unit 103 sets PUCCH resources as an example of allocation of resources used for transmitting and receiving UL signals. Information related to PUCCH configuration such as a PUCCH cell timing pattern (PUCCH configuration information) may be notified to the terminal 20 by RRC.
[0089] 10 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.
[0090] 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.
[0091] 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.
[0092] The UL signal may include, for example, an uplink data signal and control information (e.g., UCI). For example, information related to the processing capability of the terminal 20 (e.g., UE capability) may be included. The UL signal may also include a reference signal.
[0093] Channels used for transmitting UL signals include, for example, data channels and control channels. For example, the data channels include a PUSCH (Physical Uplink Shared Channel), and the control channels include a PUCCH (Physical Uplink Control Channel). For example, the terminal 20 receives control information from the base station 10 using the PUCCH and transmits uplink data signals using the PUSCH.
[0094] The reference signals included in the UL signal may include, for example, at least one of DMRS, PTRS, CSI-RS, SRS, and PRS. For example, the reference signals such as DMRS and PTRS are used for demodulating the uplink data signal and are transmitted using an uplink channel (for example, PUSCH).
[0095] The control unit 203 controls the communication operations of the terminal 20 , including the reception processing in the receiving unit 201 and the transmission processing in the transmitting unit 202 .
[0096] For example, the control unit 203 acquires information such as data and control information from the upper layer and outputs it to the transmitting unit 202. Also, the control unit 203 outputs, for example, the data and control information received from the receiving unit 201 to the upper layer.
[0097] For example, the control unit 203 controls transmission of information to be fed back to the base station 10. The information to be fed back to the base station 10 may include, for example, HARQ-ACK, channel state information (CSI), or a scheduling request (SR). The information to be fed back to the base station 10 may be included in UCI. The UCI is transmitted in the resources of the PUCCH.
[0098] The control unit 203 sets PUCCH resources based on configuration information (for example, configuration information such as a PUCCH cell timing pattern notified by RRC and / or DCI) received from the base station 10. The control unit 203 determines the PUCCH resources to be used for transmitting information to be fed back to the base station 10. Under the control of the control unit 203, the transmission unit 202 transmits the information to be fed back to the base station 10 in the PUCCH resources determined by the control unit 203.
[0099] Note that the channel used for transmitting the DL signal and the channel used for transmitting the UL signal are not limited to the above-mentioned examples. For example, the channel used for transmitting the DL signal and the channel used for transmitting the UL signal may include a Random Access Channel (RACH) and a Physical Broadcast Channel (PBCH). The RACH may be used to transmit Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), for example.
[0100] The receiving unit 201 receives a downlink control signal indicating one or more pieces of information related to the start symbol and length of an uplink signal in a row of a time-domain resource allocation table. The time-domain resource allocation table may be a TDRA table related to a PUSCH. The information related to the start symbol and length of the uplink signal may be an SLIV. The downlink control signal may be DCI. DCI may be interpreted as a DCI format.
[0101] The control unit 203 schedules retransmission of the uplink signal for which the setting is permitted based on the downlink control signal. The uplink signal for which the setting is permitted may be a CG PUSCH. The CG PUSCH may be type 1 CG or type 2 CG.
[0102] When the control unit 203 receives a downlink control signal scrambled with a specific identifier, the control unit 203 may determine whether to retransmit the uplink signal based on a specific bit included in the downlink control signal. The specific identifier may be the CS-RNTI. The specific bit may be the NDI bit.
[0103] The control unit 203 may apply the increment of the information relating to the process of requesting retransmission of the downlink signal only to the retransmitted uplink signal. The information relating to the process of requesting retransmission may be an HP ID instruction and an HP ID.
[0104] With the above configuration, the terminal can support retransmissions corresponding to CGs scheduled by DCIs indicating multiple SLIVs. The terminal can appropriately retransmit uplink signals. Since the terminal determines whether to retransmit uplink signals based on specific bits, the amount of communication with the base station is reduced.
[0105] In the above, the Type 1 CG PUSCH may be referred to as Type 1 CG or CG Type 1. The Type 2 CG PUSCH may be referred to as Type 2 CG or CG Type 2.
[0106] The present disclosure has been described above. Note that the division of items in the above description is not essential to the present disclosure, and items described in two or more items may be used in combination as needed, and items described in one item may be applied to items described in another item (unless they are inconsistent).
[0107] <Hardware Configuration, etc.> The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.
[0108] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.
[0109] For example, a base station, a terminal, or the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to this embodiment. The above-described base station 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, and the like.
[0110] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.
[0111] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.
[0112] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 103 and control unit 203 may be realized by the processor 1001.
[0113] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 203 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.
[0114] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to an embodiment of the present disclosure.
[0115] Storage 1003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.
[0116] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the above-mentioned transmitter 101, receiver 102, receiver 201, transmitter 202, etc. may be realized by the communication device 1004.
[0117] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).
[0118] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.
[0119] 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.
[0120] <Notification of Information, Signaling> Notification of information is not limited to the embodiments described in the present disclosure and may be performed using other methods. For example, notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.
[0121] <Applicable Systems> The embodiments described in the present disclosure are applicable to LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 (WiMAX (registered trademark The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).
[0122] <Processing Procedures, etc.> The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.
[0123] <Operation of Base Station> In the present disclosure, specific operations described as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (for example, an MME or an S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.
[0124] <Direction of Input / Output> Information, etc. (see <Information, Signal>) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). It may also be input / output via multiple network nodes.
[0125] <Handling of Input / Output Information, etc.> Input / output information, etc. may be stored in a specific location (for example, memory) or may be managed using a management table. Input / output information, etc. may be overwritten, updated, or added. Output information, etc. may be deleted. Input information, etc. may be sent to another device.
[0126] <Determination method> The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a comparison of numerical values (e.g., comparison with a predetermined value).
[0127] <Variations of Aspects, etc.> Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation. In addition, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).
[0128] 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.
[0129] <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.
[0130] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.
[0131] Information, Signals, etc., described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0132] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.
[0133] <System, Network> As used in this disclosure, the terms "system" and "network" are used interchangeably.
[0134] <Parameter and Channel Names> Furthermore, the information, parameters, and the like described in the present disclosure may be expressed using absolute values, relative values from a predetermined value, or other corresponding information. For example, a radio resource may be indicated by an index.
[0135] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.
[0136] <Base Station> In the present disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.
[0137] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a remote radio head (RRH)). The terms "cell" or "sector" refer to part or the entire coverage area of a base station and / or base station subsystem that provides communication services within that coverage area.
[0138] Mobile Station In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.
[0139] 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.
[0140] <Base Station / Mobile Station> At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.
[0141] Furthermore, a base station in the present disclosure may be read as a terminal. For example, the embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.
[0142] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.
[0143] Fig. 12 shows an example configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.
[0144] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.
[0145] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0146] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.
[0147] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.
[0148] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.
[0149] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.
[0150] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.
[0151] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.
[0152] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.
[0153] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).
[0154] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.
[0155] <Meaning and Interpretation of Terms> As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), ascertaining something that is considered to be a "judging" or "determining," and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like that are considered to be a "judging" or "determining." Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.
[0156] 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.
[0157] <Reference Signal> A reference signal can also be abbreviated as RS (Reference Signal), and may also be called a pilot depending on the applicable standard.
[0158] <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."
[0159] "First," "Second" Any reference to an element using designations such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must precede the second element in some way.
[0160] <Means> The "means" in the configuration of each device above may be replaced with "section," "circuit," "device," etc.
[0161] 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.
[0162] <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.
[0163] Numerology may be a communication parameter that applies to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.
[0164] A slot may be composed of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may be a time unit based on numerology.
[0165] 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.
[0166] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.
[0167] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.
[0168] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) to each user terminal in TTI units. Note that the definition of TTI is not limited to this.
[0169] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.
[0170] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.
[0171] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.
[0172] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.
[0173] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may be determined based on numerology.
[0174] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.
[0175] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.
[0176] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.
[0177] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.
[0178] 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.
[0179] 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."
[0180] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.
[0181] <Maximum Transmit Power> The "maximum transmit power" in the present disclosure may refer to the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.
[0182] Articles In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.
[0183] <"Different"> In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." Note that the term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."
[0184] This patent application claims priority based on Japanese Patent Application No. 2023-085787 filed on May 24, 2023, the entire contents of which are incorporated herein by reference.
[0185] One aspect of the present disclosure is useful in wireless communication systems.
[0186] 10 Base station 101 Transmitter 102 Receiver 103 Controller 20 Terminal 201 Receiver 202 Transmitter 203 Controller
Claims
1. A terminal having a receiving unit that receives a downlink control signal indicating one or more pieces of information regarding the start symbol and length of an uplink signal within a row of a time domain resource allocation table; and a control unit that schedules retransmission of an uplink signal that has been permitted to be set based on the downlink control signal.
2. The terminal according to claim 1, wherein, when the control unit receives the downlink control signal scrambled with a specific identifier, the control unit determines whether or not to retransmit the uplink signal based on a specific bit contained in the downlink control signal.
3. The terminal according to claim 1, wherein the specific bit is one bit.
4. The terminal according to claim 1, wherein the control unit applies an increment of information relating to a process of a retransmission request for a downlink signal only to the retransmitted uplink signal.
5. A communication method in which a terminal receives a downlink control signal indicating one or more pieces of information regarding a starting symbol and length of an uplink signal within a row of a time domain resource allocation table, and schedules retransmission of the uplink signal that has been permitted to be set based on the downlink control signal.
