Base station device, terminal device, and communication method

Abstract

A terminal device of the present application is provided with: a reception section that receives a DCI format; and a transmission section that repeatedly transmits a transport block scheduled by the DCI format through a PUSCH, gives a first value of the number of times of repetition transmission, a second value of the symbol number of a starting symbol, and a third value of consecutive symbols based on the DCI format, and determines the number of slots in which the transport block is repeatedly transmitted based on the first value, the second value, the third value, and the number of symbols within a slot.

Description

Technical Field

[0001] This invention relates to base station devices, terminal devices, and communication methods. This application claims priority based on Japanese Patent Application No. 2019-2867, filed on January 10, 2019, the contents of which are incorporated herein by reference. Background Technology

[0002] Currently, as wireless access methods and wireless network technologies for fifth-generation cellular systems, the Third Generation Partnership Project (3GPP) has conducted technical research and standardization on LTE (Long Term Evolution)-Advanced Pro (LTE-A Pro, an extended standard of LTE) and NR (New Radio technology) (Non-patent literature 1).

[0003] In fifth-generation cellular systems, as a hypothetical service scenario, the following three scenarios are requested: eMBB (enhanced Mobile Broadband) for high-speed / high-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) for low-latency / high-reliability communication, and mMTC (massive Machine Type Communication) for massive connectivity of machine-type devices such as IoT (Internet of Things).

[0004] Existing technical documents

[0005] Non-patent literature

[0006] Non-Patent Literature 1: RP-161214, NTT DOCOMO, “Revision of SI: Study on New RadioAccess Technology”, June 2016 Summary of the Invention

[0007] The problem the invention aims to solve

[0008] One objective of this invention is to provide a terminal device, a base station device, a communication method, and an integrated circuit that can communicate efficiently in the wireless communication system described above.

[0009] Technical solution

[0010] (1) To achieve the above objective, the present invention employs the following solution. That is, a terminal device according to one embodiment of the present invention includes: a receiving unit that receives a DCI format; and a transmitting unit that repeatedly transmits transport blocks scheduled by the DCI format via PUSCH, provides a first value for repeated transmission, a second value for the symbol number of the starting symbol, and a third value for consecutive symbols based on the DCI format, and determines the number of time slots for repeatedly transmitting the transport blocks based on the first value, the second value, the third value, and the number of symbols in the time slot.

[0011] (2) Furthermore, a base station apparatus according to one aspect of the present invention includes: a transmitting unit that transmits a DCI format; and a receiving unit that receives repeated transmissions of a transport block scheduled by the DCI format via a PUSCH, provides a first value for repeated transmission, a second value for the symbol number of the starting symbol, and a third value for consecutive symbols based on the DCI format, and determines the number of time slots for repeatedly transmitting the transport block based on the first value, the second value, the third value, and the number of symbols in the time slot.

[0012] (3) In addition, one aspect of the communication method of the present invention is a communication method of a terminal device, wherein a DCI format is received, a transport block scheduled by the DCI format is repeatedly transmitted via PUSCH, a first value for repeated transmission, a second value for the symbol number of the starting symbol and a third value for consecutive symbols are given based on the DCI format, and the number of time slots for repeatedly transmitting the transport block is determined based on the first value, the second value, the third value and the number of symbols in the time slot.

[0013] (4) Furthermore, one aspect of the communication method of the present invention is a communication method of a base station device, wherein a DCI format is transmitted, a retransmission of a transport block scheduled by the DCI format is received via PUSCH, a first value for the retransmission, a second value for the symbol number of the starting symbol and a third value for the consecutive symbols are given based on the DCI format, and the number of time slots for retransmitting the transport block is determined based on the first value, the second value, the third value and the number of symbols in the time slot.

[0014] Beneficial effects

[0015] According to one aspect of the present invention, the base station device and the terminal device can communicate efficiently. Attached Figure Description

[0016] Figure 1 This is a diagram illustrating the concept of a wireless communication system according to an embodiment of the present invention.

[0017] Figure 2 This is a diagram illustrating an example of an SS / PBCH block and an SS burst set according to an embodiment of the present invention.

[0018] Figure 3 This is a diagram illustrating an example of the schematic configuration of uplink and downlink time slots in an embodiment of the present invention.

[0019] Figure 4 This is a diagram illustrating the temporal relationship between subframes, time slots, and mini-time slots in embodiments of the present invention.

[0020] Figure 5 This is a diagram illustrating an example of a time slot or subframe in an embodiment of the present invention.

[0021] Figure 6 This is a diagram illustrating an example of beamforming according to an embodiment of the present invention.

[0022] Figure 7 This is a diagram illustrating an example of a PDSCH mapping type in an embodiment of the present invention.

[0023] Figure 8 This is a diagram illustrating an example of frequency hopping in an embodiment of the present invention.

[0024] Figure 9 This is a diagram illustrating another example of determining the number of repeated transmissions and frequency hopping in an embodiment of the present invention.

[0025] Figure 10 This is a diagram that defines which resource allocation table of the embodiments of the present invention will be applied to the PDSCH time-domain resource allocation.

[0026] Figure 11 This is a diagram illustrating an example of a default table A representing an embodiment of the present invention.

[0027] Figure 12 This is a diagram illustrating an example of a default table B in an embodiment of the present invention.

[0028] Figure 13 This is a diagram illustrating an example of the default table C in an embodiment of the present invention.

[0029] Figure 14 This is a diagram illustrating an example of calculating the SLIV of an embodiment of the present invention.

[0030] Figure 15 This is a diagram illustrating an example of a redundant version of the transmission opportunities applied to this embodiment.

[0031] Figure 16 This is a diagram that defines which resource allocation table of this implementation will be applied to the PUSCH time-domain resource allocation.

[0032] Figure 17 This is a diagram showing an example of the PUSCH default table A in this implementation.

[0033] Figure 18 This is a diagram illustrating another example of determining the number of repeated transmissions and frequency hopping in this embodiment.

[0034] Figure 19 This is a diagram illustrating another example of determining the number of repeated transmissions and frequency hopping in an embodiment of the present invention.

[0035] Figure 20 This is a diagram illustrating another example of the number of repeated transmissions and frequency hopping in this embodiment.

[0036] Figure 21 This is a diagram illustrating an example of time-slot aggregation transmission according to an embodiment of the present invention.

[0037] Figure 22 This is a schematic block diagram illustrating the configuration of the terminal device 1 according to an embodiment of the present invention.

[0038] Figure 23 This is a schematic block diagram illustrating the configuration of a base station device 3 according to an embodiment of the present invention. Detailed Implementation

[0039] The embodiments of the present invention will be described below.

[0040] Figure 1 This is a conceptual diagram of the wireless communication system according to this embodiment. Figure 1 In this wireless communication system, there are terminal device 1A, terminal device 1B, and base station device 3. Hereinafter, terminal device 1A and terminal device 1B will also be referred to as terminal device 1.

[0041] Terminal device 1 is also referred to as a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), or MS (Mobile Station). Base station device 3 is also referred to as a wireless base station device, base station, wireless base station, fixed station, NB (NodeB), eNB (evolved NodeB), BTS (Base Transceiver Station), BS (Base Station), NRNB (NRNode B), NNB, TRP (Transmission and Reception Point), or gNB. Base station device 3 may also include core network devices. Furthermore, base station device 3 may have one or more transceiver points 4. At least some of the functions / processes of base station device 3 described below may be the functions / processes of each transceiver point 4 possessed by base station device 3. Base station device 3 can serve terminal device 1 as one or more cells within a communication range (communication area) controlled by base station device 3. Additionally, base station device 3 can also serve terminal device 1 as one or more cells within a communication range (communication area) controlled by one or more transceiver points 4. Alternatively, a small area can be divided into multiple local areas (beamed areas), with terminal device 1 serving in each local area. Here, the local areas can be identified based on the index of the beam used in beamforming or a pre-coded index.

[0042] The wireless communication link from base station device 3 to terminal device 1 is called the downlink. The wireless communication link from terminal device 1 to base station device 3 is called the uplink.

[0043] exist Figure 1 In the wireless communication between terminal device 1 and base station device 3, the following can be used: Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix, Single-Carrier Frequency Division Multiplexing (SC-FDM), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM), and Multi-Carrier Code Division Multiplexing (MC-CDM).

[0044] In addition, Figure 1 In the wireless communication between terminal device 1 and base station device 3, Universal-Filtered Multi-Carrier (UFMC), Filtered OFDM (F-OFDM), Windowed OFDM, and Filter-Bank Multi-Carrier (FBMC) can also be used.

[0045] It should be noted that in this embodiment, OFDM is used as the transmission method and is described using OFDM symbols, but the present invention also includes cases where other transmission methods are used.

[0046] In addition, Figure 1 In the wireless communication between terminal device 1 and base station device 3, CP may be omitted, or the aforementioned transmission method with zero padding may be used instead of CP. Furthermore, CP and zero padding can be added to both the front-end and rear-end devices.

[0047] One implementation scheme of this method can operate in carrier aggregation or dual connectivity using radio access technologies (RATs) such as LTE, LTE-A / LTE-A Pro. In this case, it can be used for some or all cells or cell groups, carriers or carrier groups (e.g., primary cell (PCell), secondary cell (SCell), primary-secondary cell (PSCell), master cell group (MCG), secondary cell group (SCG), etc.). Alternatively, it can be used in standalone deployments for individual operation. In dual connectivity operation, the SpCell (SpecialCell) is referred to as the PCell of the MCG or the PSCell of the SCG, depending on whether it is associated with the MAC (Medium Access Control) entity and the MCG. If it is not a dual connectivity operation, the SpCell (SpecialCell) is referred to as the PCell. The SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

[0048] In this embodiment, one or more serving cells can be configured for terminal device 1. The configured serving cells may include a primary cell and one or more secondary cells. The primary cell may be a serving cell that has undergone initial connection establishment, started connection re-establishment, or is designated as the primary cell during handover. One or more secondary cells may be configured at or after the establishment of an RRC (Radio Resource Control) connection. However, the configured serving cells may include one primary and one secondary cell. The primary and secondary cells may be secondary cells among the one or more secondary cells configured for terminal device 1 that can transmit control information on the uplink. Furthermore, a subset of serving cells, namely a primary cell group and a secondary cell group, may be configured for terminal device 1. A primary cell group may consist of one primary cell and zero or more secondary cells. A secondary cell group may consist of one primary and one secondary cell and zero or more secondary cells.

[0049] The wireless communication system of this embodiment can apply TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). TDD or FDD can be applied to all multiple cells. Furthermore, cells applying TDD can be aggregated with cells applying FDD. TDD can also be called unpaired spectrum operation. FDD can also be called paired spectrum operation.

[0050] The carrier corresponding to the serving cell in the downlink is called the downlink component carrier (or downlink carrier). The carrier corresponding to the serving cell in the uplink is called the uplink component carrier (or uplink carrier). The carrier corresponding to the serving cell in the sidelink is called the sidelink component carrier (or sidelink carrier). The downlink component carrier, uplink component carrier, and / or sidelink component carrier are collectively referred to as component carriers (or carriers).

[0051] The physical channel and physical signal of this embodiment will be described.

[0052] exist Figure 1 In the wireless communication between terminal device 1 and base station device 3, the following physical channel is used.

[0053] • PBCH (Physical Broadcast Channel)

[0054] • PDCCH (Physical Downlink Control Channel)

[0055] • PDSCH (Physical Downlink Shared Channel)

[0056] • PUCCH (Physical Uplink Control Channel)

[0057] • PUSCH (Physical Uplink Shared Channel)

[0058] • PRACH (Physical Random Access Channel)

[0059] PBCH is an important information block used to broadcast important system information required by terminal device 1 (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel).

[0060] Furthermore, the PBCH can be used as a time index within a period of a block of broadcast synchronization signals (also known as an SS / PBCH block). Here, the time index is information representing the index of the synchronization signals and the PBCH within the cell. For example, when transmitting SS / PBCH blocks using the assumption of three transmit beams (transmit filter settings, quasi-co-location (QCL) related to receive spatial parameters), the time sequence within a pre-set period or a set period can be represented. Additionally, the terminal device can recognize differences in the time index as differences in the transmit beams.

[0061] The PDCCH is used to transmit (or transport) downlink control information (DCI) in downlink wireless communication (wireless communication from base station device 3 to terminal device 1). Here, one or more DCIs (also called DCI formats) are defined for the transmission of downlink control information. That is, fields for downlink control information are defined as DCIs and mapped to information bits. The PDCCH is transmitted in PDCCH candidates. Terminal device 1 monitors the set of PDCCH candidates in the serving cell. Monitoring means attempting to decode the PDCCH according to a certain DCI format.

[0062] For example, the following DCI format can be defined.

[0063] ·DCI format 0_0

[0064] ·DCI format 0_1

[0065] ·DCI format 1_0

[0066] ·DCI format 1_1

[0067] ·DCI format 2_0

[0068] ·DCI format 2_1

[0069] ·DCI format 2_2

[0070] ·DCI format 2_3

[0071] DCI format 0_0 can be used for PUSCH scheduling within a serving cell. DCI format 0_0 can include information representing PUSCH scheduling (frequency domain resource allocation and time domain resource allocation). DCI format 0_0 can be appended with a CRC scrambled by any of C-RNTI, CS-RNTI, MCS-C-RNTI, and / or TC-RNTI. DCI format 0_0 can be monitored in the common search space or the UE-specific search space.

[0072] DCI format 0_1 ​​can be used for PUSCH scheduling within a serving cell. DCI format 0_1 ​​may include: information representing PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information representing the Bandwidth Part (BWP), a Channel State Information (CSI) request, a Sounding Reference Signal (SRS) request, and information related to the antenna port. DCI format 0_1 ​​may be appended with a CRC scrambled by any of C-RNTI, CS-RNTI, SP-CSI-RNTI, and / or MCS-C-RNTI. DCI format 0_1 ​​can be monitored in the UE-specific search space.

[0073] DCI format 1_0 can be used for PDSCH scheduling within a serving cell. DCI format 1_0 can include information representing PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation). DCI format 1_0 can be appended with a CRC scrambled by any of C-RNTI, CS-RNTI, MCS-C-RNTI, P-RNTI, SI-RNTI, RA-RNTI, and / or TC-RNTI. DCI format 1_0 can be monitored in either the common search space or the UE-specific search space.

[0074] DCI format 1_1 can be used for PDSCH scheduling in a serving cell. DCI format 1_1 may include: information representing PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information representing partial bandwidth (BWP), Transmission Configuration Indication (TCI), and information related to the antenna port. DCI format 1_1 may be appended with a CRC scrambled by any of C-RNTI, CS-RNTI, and / or MCS-C-RNTI. DCI format 1_1 can be monitored in the UE-specific search space.

[0075] DCI format 2_0 is used to notify the slot format of one or more slots. The slot format is defined as classifying each OFDM symbol within a slot as downlink, variable, or uplink. For example, in the case of slot format 28, DDDDDDDDDDDDFU is applied to the 14 OFDM symbols within the slot indicating slot format 28. Here, D represents downlink symbols, F represents variable symbols, and U represents uplink symbols. It should be noted that slots will be described in detail later.

[0076] DCI format 2_1 is used to notify terminal device 1 that physical resource blocks and OFDM symbols can be assumed to be untransmitted. It should be noted that this information can also be called a preemption indication (intermittent transmission indication).

[0077] DCI format 2_2 is used to send PUSCH and transmit power control (TPC) commands for PUSCH.

[0078] DCI format 2_3 is used to send groups of TPC commands for transmitting Sound Reference Signals (SRS) implemented by one or more terminal devices 1. Furthermore, SRS requests can be sent together with TPC commands. Additionally, in DCI format 2_3, SRS requests and TPC commands can be defined for uplinks without PUSCH and PUCCH, or for uplinks where SRS transmit power control is not associated with PUSCH transmit power control.

[0079] The DCI for the downlink is also referred to as a downlink grant or downlink assignment. Similarly, the DCI for the uplink is referred to as an uplink grant or uplink assignment. The DCI can also be referred to as the DCI format.

[0080] The parity check bits appended to the DCI-formatted CRC (Cyclic Redundancy Check) transmitted via a PDCCH can be scrambled using SI-RNTI (System Information-Radio Network Temporary Identifier), P-RNTI (Paging-Radio Network Temporary Identifier), C-RNTI (Cell-Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), RA-RNTI (Random Access-Radio Network Temporary Identity), or Temporary C-RNTI. SI-RNTI can be an identifier used for broadcasting system information. P-RNTI can be an identifier used for paging and notification of system information changes. C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers used to identify terminal devices within a cell. The temporary C-RNTI is an identifier used to identify the terminal device 1 that sent the random access preamble in a contention-based random access procedure.

[0081] The C-RNTI (Terminal Device Identifier) ​​is used to control PDSCH or PUSCH in one or more time slots. The CS-RNTI is used to periodically allocate PDSCH or PUSCH resources. The MCS-C-RNTI is used for the use of the MCS table specified in the grant-based transmission instruction. The Temporary C-RNTI (TC-RNTI) is used to control PDSCH or PUSCH transmission in one or more time slots. The Temporary C-RNTI is used to schedule the retransmission of Random Access Message 3 and the transmission of Random Access Message 4. The RA-RNTI (Random Access Response Identification Information) is determined based on the frequency and time location information of the physical random access channel that transmitted the random access preamble.

[0082] In uplink wireless communication (wireless communication from terminal device 1 to base station device 3), the PUCCH is used to transmit uplink control information (UCI). This uplink control information may include channel state information (CSI) indicating the state of the downlink channel. Furthermore, the uplink control information may include a scheduling request (SR) for requesting UL-SCH resources. Additionally, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACK knowledgement). HARQ-ACK can represent a HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit (MAC PDU), Downlink-Shared Channel (DL-SCH)).

[0083] PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the Medium Access Control (MAC) layer. In addition, in the downlink case, it is also used to transmit System Information (SI), Random Access Response (RAR), etc.

[0084] PUSCH can be used to send HARQ-ACK and / or CSI along with uplink data (UL-SCH: Uplink Shared Channel) or uplink data from the MAC layer. Alternatively, it can be used to send only CSI or only HARQ-ACK and CSI. That is, it can also be used to send only UCI.

[0085] Here, base station device 3 and terminal device 1 exchange (transmit and receive) signals at the higher layer. For example, base station device 3 and terminal device 1 can transmit and receive RRC signaling (also called RRC message or RRC information) at the Radio Resource Control (RRC) layer. Furthermore, base station device 3 and terminal device 1 can also transmit and receive MAC control elements at the MAC (Medium Access Control) layer. Additionally, the RRC layer of terminal device 1 obtains the broadcast system information from base station device 3. Here, RRC signaling, system information, and / or MAC control elements are also referred to as higher layer signaling or higher layer parameters. The term "higher layer" here refers to the layer observed from the physical layer; therefore, it can include one or more of the following: MAC layer, RRC layer, RLC layer, PDCP layer, NAS (Non-Access Stratum) layer, etc. For example, in MAC layer processing, the upper layer may include one or more of the following: RRC layer, RLC layer, PDCP layer, NAS layer, etc. Hereinafter, "A is given through the upper layer" or "A is given by the upper layer" can mean that the upper layer of terminal device 1 (mainly the RRC layer, MAC layer, etc.) receives A from base station device 3, and the upper layer of terminal device 1 provides the received A to the physical layer of terminal device 1. Setting upper layer parameters for terminal device 1 can refer to providing upper layer parameters to the terminal device.

[0086] PDSCH or PUSCH can be used to transmit RRC signaling and MAC control elements. Here, in PDSCH, the RRC signaling transmitted from base station device 3 can be signaling shared by multiple terminal devices 1 within the cell. Furthermore, the RRC signaling transmitted from base station device 3 can also be signaling dedicated to a specific terminal device 1 (also known as dedicated signaling). That is, dedicated signaling can be used to transmit terminal device-specific (UE-specific) information to a specific terminal device 1. Additionally, PUSCH can be used to transmit UE capabilities on the uplink.

[0087] exist Figure 1 In downlink wireless communication, the following downlink physical signals are used. These downlink physical signals are not used to transmit information output from the upper layer, but are used by the physical layer.

[0088] Synchronization signal (SS)

[0089] • Reference Signal (RS)

[0090] Synchronization signals can include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The PSS and SSS can be used to detect the cell ID.

[0091] The synchronization signal is used by terminal device 1 to obtain frequency and time domain synchronization of the downlink. Here, the synchronization signal can be used by terminal device 1 to select precoding or beamforming performed by base station device 3. It should be noted that beamforming can also be referred to as transmit or receive filtering, or spatial domain transmit filtering or spatial domain receive filtering.

[0092] The reference signal is used by terminal device 1 for physical channel transmission path compensation. Here, the reference signal can also be used by terminal device 1 to calculate the downlink CSI. Furthermore, the reference signal can be used for fine synchronization, which is a level of synchronization that achieves synchronization of parameters such as radio parameters, subcarrier spacing, and FFT window synchronization.

[0093] In this implementation, one or more of the following downlink reference signals are used.

[0094] ·DMRS (Demodulation Reference Signal)

[0095] • CSI-RS (Channel State Information Reference Signal)

[0096] • PTRS (Phase Tracking Reference Signal)

[0097] • TRS (Tracking Reference Signal)

[0098] DMRS is used to demodulate modulated signals. It should be noted that DMRS can define two types of reference signals: one for demodulating PBCH and the other for demodulating PDSCH; both can be referred to as DMRS. CSI-RS is used for Channel State Information (CSI) measurement and beam management, and employs periodic, semi-static, or aperiodic CSI reference signal transmission methods. For CSI-RS, non-zero power (NZP) CSI-RS and zero-power (ZP) CSI-RS can be defined. Here, ZP CSI-RS can be defined as a CSI-RS resource with zero transmission power or that has not been transmitted. PTRS is used to track phase on the time axis to compensate for frequency shifts caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. It should be noted that TRS can be used as a setting for CSI-RS. For example, a port's CSI-RS can be used as a TRS to set up a radio resource.

[0099] In this implementation, one or more of the following uplink reference signals are used.

[0100] ·DMRS (Demodulation Reference Signal)

[0101] • PTRS (Phase Tracking Reference Signal)

[0102] • SRS (Sounding Reference Signal)

[0103] DMRS is used to demodulate modulated signals. It should be noted that two reference signals can be defined in DMRS: one for demodulating PUCCH and the other for demodulating PUSCH; both can be referred to as DMRS. SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management. PTRS is used to track phase on the time axis to compensate for frequency shifts caused by phase noise.

[0104] The downlink physical channel and / or downlink physical signal are collectively referred to as downlink signals. The uplink physical channel and / or uplink physical signal are collectively referred to as uplink signals. The downlink physical channel and / or uplink physical channel are collectively referred to as physical channel. The downlink physical signal and / or uplink physical signal are collectively referred to as physical signal.

[0105] BCH, UL-SCH, and DL-SCH are transport channels. The channels used in the Medium Access Control (MAC) layer are called transport channels. The unit of the transport channel used in the MAC layer is also called a transport block (TB) and / or MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) control is performed on a per-transport-block basis in the MAC layer. A transport block is the unit of data delivered by the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords, and each codeword is encoded.

[0106] Figure 2 This is a diagram illustrating an example of the SS / PBCH block (also known as the synchronization signal block, SS block, SSB) and SS burst set (also known as the synchronization signal burst set) in this embodiment. Figure 2 An example is shown that a periodically transmitted SS burst set includes two SS / PBCH blocks, each consisting of four consecutive OFDM symbols.

[0107] An SS / PBCH block is a unit block that includes at least a synchronization signal (PSS, SSS) and / or a PBCH. Transmitting the signals / channels included in an SS / PBCH block is represented as transmitting the SS / PBCH block. When using one or more SS / PBCH blocks within an SS burst set to transmit the synchronization signal and / or PBCH, the base station device 3 can use a downlink transmission beam independent for each SS / PBCH block.

[0108] exist Figure 2 In this process, the PSS, SSS, and PBCH are time-division multiplexed / frequency-division multiplexed within an SS / PBCH block. The order in which the PSS, SSS, and / or PBCH are multiplexed in the time domain can be... Figure 2 The examples shown are different.

[0109] SS burst sets can be transmitted periodically. For example, a period can be defined for initial access and a period set for connected (Connected or RRC_Connected) terminal devices. Furthermore, the period set for connected (Connected or RRC_Connected) terminal devices can be set at the RRC layer. Additionally, the period set for connected (Connected or RRC_Connected) terminals is the period for time-domain radio resources that may potentially be transmitted, and it can be determined whether it is transmitted by base station device 3. Furthermore, the period for initial access can be predefined in specifications, etc.

[0110] SS burst sets can be determined based on the System Frame Number (SFN). Furthermore, the start position (boundary) of an SS burst set can be determined based on the SFN and the period.

[0111] For SS / PBCH blocks, the SSB index (also known as the SSB / PBCH block index) is assigned based on the temporal position within the SS burst set. Terminal device 1 calculates the SSB index based on the PBCH information and / or reference signal information included in the detected SS / PBCH block.

[0112] The same SSB index is assigned to SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets. It can be assumed that the SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets are QCLs (or use the same downlink transmit beam). Furthermore, it can also be assumed that the antenna ports of the SS / PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets are QCLs related to average delay, Doppler shift, and spatial correlation.

[0113] Alternatively, it can be assumed that within a certain SS burst set period, SS / PBCH blocks assigned the same SSB index constitute the QCL, which is related to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. The settings corresponding to one or more SS / PBCH blocks (or reference signals) that serve as QCLs can be referred to as QCL settings.

[0114] The number of SS / PBCH blocks (which may be referred to as the number of SS blocks or SSBs) can be defined, for example, as the number of SS / PBCH blocks within an SS burst or SS burst set, or within a period of an SS / PBCH block. Furthermore, the number of SS / PBCH blocks can represent the number of beamgroups used for cell selection within an SS burst, SS burst set, or the periodicity of an SS / PBCH block. Here, a beamgroup can be defined as: the number of different SS / PBCH blocks or different beams included within an SS burst, SS burst set, or the periodicity of an SS / PBCH block.

[0115] Hereinafter, the reference signals described in this embodiment include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RS, CSI-RS, uplink reference signals, SRS, and / or uplink DM-RS. For example, downlink reference signals, synchronization signals, and / or SS / PBCH blocks may be referred to as reference signals. Reference signals used in the downlink include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RS, CSI-RS, etc. Reference signals used in the uplink include uplink reference signals, SRS, and / or uplink DM-RS, etc.

[0116] In addition, the reference signal can be used for radio resource measurement (RRM). Furthermore, the reference signal can be used for beam management.

[0117] Beam management can be a process by which a base station device 3 and / or a terminal device 1 obtains beam gain by matching the directivity of analog and / or digital beams in a transmitting device (base station device 3 in the downlink case and terminal device 1 in the uplink case) with the directivity of analog and / or digital beams in a receiving device (terminal device 1 in the downlink case and base station device 3 in the uplink case).

[0118] It should be noted that the process of constructing, setting, or establishing beam pairing may include the following processes.

[0119] • Beam selection

[0120] • Beam refinement

[0121] • Beam recovery

[0122] For example, beam selection can be a process of selecting a beam during communication between base station device 3 and terminal device 1. Furthermore, beam refinement can be a process of further selecting a high-gain beam or changing the optimal beam between base station device 3 and terminal device 1 by moving terminal device 1. Beam recovery can be a process of reselecting a beam during communication between base station device 3 and terminal device 1 when the quality of the communication link deteriorates due to obstructions such as obstacles or people passing by.

[0123] Beam management can include beam selection and beam refinement. Beam recovery can include the following processes.

[0124] • Beam failure detected

[0125] • Discover new beams

[0126] • Send beam recovery request

[0127] • Monitor responses to beam recovery requests.

[0128] For example, when selecting the transmission beam from base station device 3 to terminal device 1, the RSRP (Reference Signal Received Power) of the SSS included in the CSI-RS or SS / PBCH block can be used, or CSI can be used. Furthermore, as a report to base station device 3, the CSI-RS Resource Index (CRI) can be used, or an index included in the SS / PBCH block indicating the sequence of demodulation reference signals (DMRS) used for demodulation of the PBCH can be used.

[0129] Furthermore, when indicating a beam to terminal device 1, base station device 3 indicates the time index of CRI or SS / PBCH, and terminal device 1 receives signals based on the indicated time index of CRI or SS / PBCH. At this time, terminal device 1 can set and receive spatial filtering based on the indicated time index of CRI or SS / PBCH. Additionally, terminal device 1 can use assumed quasi-co-location (QCL) for reception. The statement that a signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" with other signals (antenna port, synchronization signal, reference signal, etc.), or "using the assumption of QCL," can be interpreted as a signal establishing a correlation with other signals.

[0130] If the long-term property (LTP) of the channel transmitting a symbol at one antenna port can be inferred from the channel transmitting a symbol at the other antenna port, then the two antenna ports are considered to have a QCL (Quadrant-Like Channel). The LTP of the channel includes one or more of the following: delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna ports 1 and 2 have a QCL related to average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1.

[0131] This QCL can also be extended to beam management. Therefore, the QCL extended to space can also be redefined. For example, the long-term property of the channel assumed in the spatial domain QCL can be the angle of arrival (AoA, ZoA, etc.) and / or angle spread (e.g., ASA, ZSA), the angle of departure (AoD, ZoD, etc.) or its angle spread (e.g., ASD, ZSD), the spatial correlation, and the received spatial parameters.

[0132] For example, if the reception spatial parameter is QCL between antenna port 1 and antenna port 2, it means that the reception beam of the signal received from antenna port 2 can be inferred from the reception beam (reception spatial filtering) of the signal received from antenna port 1.

[0133] As a QCL type, a combination of long-range properties that can be considered as a QCL can be defined. For example, the following types can be defined.

[0134] Type A: Doppler frequency shift, Doppler spread, average delay, delay spread

[0135] Type B: Doppler frequency shift, Doppler spread

[0136] Type C: Average delay, Doppler shift

[0137] Type D: Receive spatial parameters

[0138] The aforementioned QCL types can be configured and / or indicated as Transmission Configuration Indication (TCI) by the assumed settings and / or indications of one or two reference signals and the QCL of the PDCCH or PDSCH DMRS through RRC and / or MAC layers and / or DCI. For example, when the index #2 of the SS / PBCH block and QCL type A + QCL type B are set and / or indicated as a state of the TCI when terminal device 1 receives the PDCCH, terminal device 1 can receive the PDCCH DMRS as if it were the Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters, and long-range characteristics of the channel in the reception of the SS / PBCH block index #2, and perform synchronization and transmission path estimation. In this case, the reference signal indicated by the TCI (SS / PBCH block in the above example) can be called the source reference signal, and the reference signal affected by the long-range characteristics inferred from the long-range characteristics of the channel when receiving the source reference signal (PDCCHDMRS in the above example) can be called the target reference signal. In addition, TCI can set one or more TCI states and the combination of source reference signals and QCL types for each state via RRC, and indicate the terminal device 1 via the MAC layer or DCI.

[0139] According to this method, as beam management and beam indication / reporting, the actions of the base station device 3 and terminal device 1, which are equivalent to beam management, can be defined based on the assumptions of QCL in the spatial domain and radio resources (time and / or frequency).

[0140] The following is a description of subframes. In this embodiment, they are referred to as subframes, but they may also be called resource units, radio frames, time intervals, time intervals, etc.

[0141] Figure 3This diagram illustrates an example of the approximate configuration of uplink and downlink time slots according to the first embodiment of the present invention. Each radio frame is 10 ms long. Furthermore, each radio frame consists of 10 subframes and W time slots. Additionally, one time slot consists of X OFDM symbols. That is, the length of one subframe is 1 ms. The duration of each time slot is defined by the subcarrier spacing. For example, when the subcarrier spacing of the OFDM symbols is 15 kHz and it is NCP (Normal Cyclic Prefix), X = 7 or X = 14, which are 0.5 ms and 1 ms respectively. Furthermore, when the subcarrier spacing is 60 kHz, X = 7 or X = 14, which are 0.125 ms and 0.25 ms respectively. Furthermore, for example, when X = 14, W = 10 when the subcarrier spacing is 15 kHz, and W = 40 when the subcarrier spacing is 60 kHz. Figure 3 The case of X=7 is shown as an example. It should be noted that the same extension is possible when X=14. Furthermore, uplink time slots can be defined in the same way, or downlink and uplink time slots can be defined separately. Figure 3 The bandwidth of a cell can be defined as a portion of the frequency band (BWP). Furthermore, a time slot can be defined as a transmission time interval (TTI). A time slot may also not be defined as a TTI. The TTI can be the transmission period of a transport block.

[0142] The signals or physical channels transmitted in each time slot can be represented by a resource grid. The resource grid defines each parameter set (subcarrier spacing and cyclic prefix length) and each carrier using multiple subcarriers and multiple OFDM symbols. The number of subcarriers constituting a time slot depends on the downlink and uplink bandwidths of the cell. Each element within the resource grid is called a resource element. Resource elements can be identified using subcarrier numbers and OFDM symbol numbers.

[0143] The resource grid is used to represent the mapping of resource elements for a physical downlink channel (PDSCH, etc.) or uplink channel (PUSCH, etc.). For example, with a subcarrier spacing of 15kHz, and with X = 14 OFDM symbols included in a subframe and NCP, a physical resource block is defined by 14 consecutive OFDM symbols in the time domain and 12 * Nmax consecutive subcarriers in the frequency domain. Nmax is the maximum number of resource blocks determined by the subcarrier spacing setting μ, which will be discussed later. That is, the resource grid consists of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended CP), only a subcarrier spacing of 60kHz is supported, so a physical resource block is defined, for example, by 12 (number of OFDM symbols included in a time slot) * 4 (number of time slots included in a subframe) = 48 consecutive OFDM symbols in the time domain and 12 * Nmax, μ consecutive subcarriers in the frequency domain. That is to say, the resource grid consists of (48*12*Nmax, μ) resource elements.

[0144] As resource blocks, there are reference resource blocks, shared resource blocks, physical resource blocks, and virtual resource blocks. A resource block is defined as 12 consecutive subcarriers in the frequency domain. Reference resource blocks are shared across all subcarriers; for example, they can be constructed with subcarrier spacing of 15 kHz and numbered in ascending order. Subcarrier index 0 of reference resource block index 0 can also be called reference point A (or simply "reference point"). Shared resource blocks are resource blocks numbered from 0 in ascending order within each subcarrier spacing setting μ, starting from reference point A. The resource grid described above is defined by this shared resource block. Physical resource blocks are resource blocks included in the partial bandwidth (BWP) described later, numbered in ascending order starting from 0. First, a physical uplink channel is mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. In the following, a resource block can be a virtual resource block, a physical resource block, a shared resource block, or a reference resource block.

[0145] Next, the subcarrier spacing setting μ will be explained. As mentioned above, NR supports one or more OFDM parameter sets. In a given BWP, the subcarrier spacing setting μ (μ = 0, 1...5) and the cyclic prefix length are given by the upper layer for the downlink BWP and by the upper layer for the uplink BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf = 2^μ·15 (kHz).

[0146] In the subcarrier spacing setting μ, time slots are counted in ascending order from 0 to N^{subframe, μ}_{slot}-1 within a subframe, and in ascending order from 0 to N^{frame, μ}_{slot}-1 within a frame. Based on the time slot setting and the cyclic prefix, consecutive OFDM symbols of N^{slot}_{symb} are located within a time slot. N^{slot}_{symb} is 14. The starting point of the time slot n^{μ}_{s} within a subframe is temporally aligned with the starting point of the n^{μ}_{s}N^{slot}_{symb} OFDM symbol within the same subframe.

[0147] Next, we will explain subframes, time slots, and mini-time slots. Figure 4 It is a graph representing the temporal relationship between subframes, time slots, and mini-time slots. For example... Figure 4 As shown, three time units are defined. Regardless of the subcarrier spacing, the subframe is 1 ms, and the number of OFDM symbols included in the time slot is either 7 or 14. The time slot length varies depending on the subcarrier spacing. Here, with a subcarrier spacing of 15 kHz, 14 OFDM symbols are included in one subframe. The downlink time slot can also be referred to as PDSCH mapping type A. The uplink time slot can also be referred to as PUSCH mapping type A.

[0148] A mini slot (also known as a subslot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols included in a slot. Figure 4 The case of a mini-slot comprising two OFDM symbols is illustrated as an example. The OFDM symbols within a mini-slot can also be timed in sync with the OFDM symbols constituting the slot. It should be noted that the smallest unit of scheduling can be a slot or a mini-slot. Furthermore, allocating mini-slots can also be referred to as non-slot-based scheduling. Additionally, scheduling mini-slots can be represented as a resource where the relative time position of the scheduling reference signal and the start position of the data is a fixed resource. Downlink mini-slots can also be referred to as PDSCH mapping type B. Uplink mini-slots can also be referred to as PUSCH mapping type B.

[0149] Figure 5 This is a diagram illustrating an example of a time slot format. Here, we illustrate an example with a time slot length of 1 ms in a subcarrier spacing of 15 kHz. Figure 5 In this context, D represents the downlink and U represents the uplink. For example... Figure 5 As shown, a certain time interval (e.g., the minimum time interval that must be allocated to a UE in the system) may include:

[0150] Downlink symbols

[0151] ·Variable symbols

[0152] Uplink symbol

[0153] One or more of these. It should be noted that these ratios can be preset as a time slot format. Alternatively, they can be defined by the number of downlink OFDM symbols included within a time slot, or by the start and end positions within the time slot. Similarly, they can be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included within a time slot, or by the start and end positions within the time slot. It should be noted that scheduling time slots can be represented as resources with fixed relative time positions between the scheduling reference signal and the time slot boundary.

[0154] Terminal device 1 can receive downlink signals or downlink channels using downlink symbols or variable symbols. Terminal device 1 can also transmit uplink signals or downlink channels using uplink symbols or variable symbols.

[0155] Figure 5 (a) is an example where all of a certain time interval (e.g., which may be referred to as the smallest unit of time resources that can be allocated to a UE or a time unit, etc. Furthermore, the smallest units of multiple time resources can also be collectively referred to as a time unit) is used entirely for downlink transmission. Figure 5 In (b), uplink scheduling is performed in the first time resource, for example via PDCCH, and uplink signals are transmitted via variable symbols, including the processing delay of PDCCH and the handover time from downlink to uplink, and the generation of transmission signals. Figure 5 In (c), the first time resource is used to transmit the PDCCH and / or the downlink PDSCH, and to transmit the PUSCH or PUCCH via the interval for handling delays and the handover time from downlink to uplink, and the interval for generating the transmission signal. Here, as an example, the uplink signal can be used to transmit HARQ-ACK and / or CSI, i.e., UCI. Figure 5 In (d), the first time resource is used to transmit PDCCH and / or PDSCH, and to transmit uplink PUSCH and / or PUCCH via the interval for handling delays and the switching time from downlink to uplink, and the interval for generating the transmission signal. Here, as an example, the uplink signal can be used to transmit uplink data, i.e., UL-SCH. Figure 5 (e) is an example of all that is used for uplink transmission (PUSCH or PUCCH).

[0156] The downlink and uplink portions mentioned above can include multiple OFDM symbols, just like LTE.

[0157] Figure 6FIG. is a diagram showing an example of beamforming. A plurality of antenna elements are connected to a transmission unit (TXRU: Transceiver unit) 50, and the phase is controlled by the phase shifter 51 of each antenna element, and the beam can be directed in an arbitrary direction with respect to the transmission signal by transmitting from the antenna element 52. Typically, the TXRU can be defined as an antenna port, and only the antenna port can be defined in the terminal device 1. By controlling the phase shifter 51, the directivity can be directed in an arbitrary direction. Therefore, the base station device 3 can communicate with the terminal device 1 using a beam with high gain.

[0158] Hereinafter, the partial bandwidth (BWP, Bandwidth part) will be described. The BWP is also referred to as a carrier BWP. The BWP can also be set separately for the downlink and the uplink. The BWP is defined as a set of consecutive physical resources selected from a consecutive subset of shared resource blocks. The terminal device 1 can set up to four BWPs that activate one downlink carrier BWP (DL BWP) at a certain time. The terminal device 1 can set up to four BWPs that activate one uplink carrier BWP (UL BWP) at a certain time. In the case of carrier aggregation, the BWP can be set in each serving cell. At this time, setting one BWP in a certain serving cell can be expressed as not setting the BWP. In addition, setting two or more BWPs can also be expressed as setting the BWP.

[0159] <MAC entity action>

[0160] In an activated serving cell, there is always an activated (already activated) BWP. BWP switching for a serving cell is used to activate a deactivated (disabled) BWP and deactivate an activated (already activated) BWP. BWP switching for a serving cell is controlled by a PDCCH indicating a downlink allocation or an uplink grant. BWP switching for a serving cell can be controlled by a BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of a random access procedure. In the addition of a SpCell (PCell or PSCell) or the activation of an SCell, a BWP is first activated without receiving a PDCCH indicating a downlink allocation or an uplink grant. The first active DL BWP (first activation DL BWP) and UL BWP (first active UL BWP) may be specified by an RRC message sent from the base station device 3 to the terminal device 1. The activated BWP for a serving cell is specified by an RRC or PDCCH sent from the base station device 3 to the terminal device 1. In addition, the first active DL BWP and UL BWP may be included in Message 4. In an unpaired spectrum (TDD band, etc.), the DL BWP and UL BWP are paired, and BWP switching is common for UL and DL. For the activated BWP of each activated serving cell with a BWP set, the MAC entity of the terminal device 1 applies normal processing. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. For the deactivated BWP of each activated serving cell with a BWP set, the MAC entity of the terminal device 1 does not transmit UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, does not transmit SRS, and does not receive DL-SCH. It is also possible that when a serving cell is disabled, there is no activated BWP (e.g., the activated BWP is deactivated).

[0161] <RRC action>

[0162] The BWP Information Element (IE) included in the RRC message (broadcast system information, information sent via dedicated RRC messages) is used to set the BWP. The RRC message sent from base station device 3 is received by terminal device 1. For each serving cell, the network (base station device 3, etc.) sets at least an initial BWP for terminal device 1, including at least a downlink BWP and one (if uplink settings are made in the serving cell, etc.) or two (if a supplementary uplink is used, etc.). Furthermore, the network may set additional uplink or downlink BWPs for a particular serving cell. BWP settings are divided into uplink parameters and downlink parameters. In addition, BWP settings are divided into common parameters and dedicated parameters. Common parameters (such as BWP uplink common IE or BWP downlink common IE) are cell-specific. The common parameters for the initial BWP of the primary cell are also provided in the system information. For all other serving cells, the network provides common parameters via dedicated signals. BWPs are identified by their BWPID. The initial BWP has a BWP ID of 0. Other BWPs have BWP IDs ranging from 1 to 4.

[0163] Without setting (providing) the upper-layer parameter initialDownlinkBWP for terminal device 1, the initial DLBWP (initial active DL BWP) can be defined by the position and number of consecutive PRBs, subcarrier spacing, and cyclic prefix, for PDCCH reception in the control resource set (CORESET) used for type 0PDCCH common search space. The position of these consecutive PRBs is between the PRBs in the control resource set used for type 0PDCCH common search space, starting from the lowest index PRB and ending at the highest index PRB. With the upper-layer parameter initialDownlinkBWP set (provided) for terminal device 1, the initial DL BWP can be indicated by the upper-layer parameter initialDownlinkBWP. The upper-layer parameter initialDownlinkBWP can be included in SIB1 (systemInformationBlockType1, ServingCellConfigCommonSIB) or ServingCellConfigCommon. The information element ServingCellConfigCommonSIB is used to set cell-specific parameters for the serving cell of terminal device 1 within SIB1.

[0164] That is, if the terminal device 1 is not configured (provided) with the upper-layer parameter `initialDownlinkBWP`, the size of the initial DL BWP can be the number of resource blocks in the control resource set (CORESET#0) used for the common search space of type 0PDCCH. If the terminal device 1 is configured (provided) with the upper-layer parameter `initialDownlinkBWP`, the size of the initial DL BWP can be given by the `locationAndBandwidth` included in the upper-layer parameter `initialDownlinkBWP`. The upper-layer parameter `locationAndBandwidth` can indicate the frequency domain location and bandwidth of the initial DL BWP.

[0165] As described above, multiple DL BWPs can be configured for terminal device 1. Furthermore, a default DL BWP can be set within the DL BWPs configured for terminal device 1 using the upper-layer parameter defaultDownlinkBWP-Id. If the upper-layer parameter defaultDownlinkBWP-Id is not provided to terminal device 1, the default DL BWP is the initial DL BWP.

[0166] The initial UL BWP can also be provided to terminal device 1 based on SIB1 (system Information Block Type 1) or initialUplinkBWP. The information element initialUplinkBWP is used to set the initial UL BWP. For operations in SpCell or secondary cell, the initial UL BWP (initial activated UL BWP) can be set (provided) to terminal device 1 based on the upper-layer parameter initialUplinkBWP. In the case of setting a supplementary uplink carrier for terminal device 1, the initial UL BWP in the supplementary uplink carrier can be set to terminal device 1 based on the initialUplinkBWP included in the upper-layer parameter supplementaryUplink.

[0167] The control resource set (CORESET) of this embodiment will be described below.

[0168] A control resource set (CORESET) is a time and frequency resource used to search for downlink control information. The CORESET configuration information includes an identifier (ControlResourceSetId, CORESET-ID) and information about the frequency resources used in the CORESET. The ControlResourceSetId (CORESET identifier) ​​is used to identify the control resource set within a serving cell. The CORESET identifier is used among BWPs within a serving cell. The CORESET identifier is unique among BWPs within a serving cell. The number of CORESETs per BWP, including the initial CORESET, is limited to three. Within a serving cell, the value of the CORESET identifier ranges from 0 to 11.

[0169] The control resource set identified by the identifier 0 of CORESET (ControlResourceSetId 0) is called CORESET#0. CORESET#0 can be set according to pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. That is, the setting information of CORESET#0 can be pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. The setting information of CORESET#0 can be set according to controlResourceSetZero included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. In other words, the information element controlResourceSetZero is used to indicate the initial DL BWP's CORESET#0 (common CORESET). The CORESET indicated by pdcch-ConfigSIB1 is CORESET#0. The information element pdcch-ConfigSIB1 within the MIB or dedicated configuration is used to set the initial DL BWP. The configuration information pdcch-ConfigSIB1 for CORESET#0 does not explicitly define the CORESET identifier, frequency resources (e.g., the number of consecutive resource blocks), and time resources (the number of consecutive symbols). However, the frequency resources (e.g., the number of consecutive resource blocks) and time resources (the number of consecutive symbols) for CORESET#0 can be implicitly determined based on the information included in pdcch-ConfigSIB1. The information element PDCCH-ConfigCommon is used to set the cell-specific PDCCH parameters provided in the SIB. Furthermore, PDCCH-ConfigCommon can also be provided during handover and the addition of PSCell and / or SCell. The configuration information for CORESET#0 is included in the initial BWP configuration. That is, the configuration information for CORESET#0 may also be excluded from the configuration of BWPs other than the initial BWP. controlResourceSetZero corresponds to 4 bits (e.g., MSB 4 bits, the most significant 4 bits) in pdcch-ConfigSIB1. CORESET#0 is a control resource set used in the public search space of type 0PDCCH.

[0170] The configuration information for the additional common control resource set (CORESET) can be set according to the commonControlResourceSet included in PDCCH-ConfigCommon. Furthermore, the configuration information for the additional common CORESET can be used to specify additional common CORESETs used for system information and / or paging procedures. The configuration information for the additional common CORESET can also be used to specify additional common CORESETs used during random access procedures. The configuration information for the additional common CORESET can be included in the settings of each BWP. The identifier of the CORESET indicated by commonControlResourceSet takes a value other than 0.

[0171] The public coreset can be a coreset used during random access (e.g., an additional public coreset). Furthermore, in this embodiment, the public coreset can include the coreset set in the setting information of coreset#0 and / or the additional public coreset. That is, the public coreset can include coreset#0 and / or the additional public coreset. coreset#0 can also be referred to as public coreset#0. Even in a BWP other than one with a public coreset set, the terminal device 1 can refer to (obtain) the setting information of the public coreset.

[0172] The configuration information for one or more CORESETs can be set according to PDCCH-Config. The information element PDCCH-Config is used to set UE-specific PDCCH parameters (such as CORESET, search space, etc.) for a specific BWP. PDCCH-Config can be included in the configuration of each BWP.

[0173] That is, in this embodiment, the configuration information of the common CORESET indicated by the MIB is pdcch-ConfigSIB1, the configuration information of the common CORESET indicated by PDCCH-ConfigCommon is controlResourceSetZero, and the configuration information of the common CORESET (additional common CORESET) indicated by PDCCH-ConfigCommon is commonControlResourceSet. Furthermore, the configuration information of one or more CORESETs (UE-specifically configured Control Resource Sets) indicated by PDCCH-Config is controlResourceSetToAddModList.

[0174] The search space is defined for searching PDCCH candidates. The searchSpaceType included in the search space configuration information indicates whether the search space is a common search space (CSS) or a UE-specific search space (USS). The UE-specific search space is derived from at least the C-RNTI value set by terminal device 1. That is, the UE-specific search space is derived separately for each terminal device 1. The common search space is a search space shared by multiple terminal devices 1, and is composed of pre-defined indexes CCE (Control Channel Element). A CCE consists of multiple resource elements. The search space configuration information includes information on the DCI format monitored within that search space.

[0175] The search space configuration information includes an identifier for the CORESET determined by the CORESET configuration information. The CORESET determined by the identifier of the CORESET included in the search space configuration information is associated with that search space. In other words, the CORESET associated with that search space is the CORESET determined by the identifier of the CORESET included in that search space. The DCI format indicated by the configuration information of that search space is monitored in the associated CORESET. Each search space is associated with one CORESET. For example, the configuration information of the search space used for a random access procedure can be set according to ra-SearchSpace. That is, the DCI format with CRC scrambled by RA-RNTI or TC-RNTI is monitored in the CORESET associated with ra-SearchSpace.

[0176] Terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs configured in each active serving cell for monitoring PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring means decoding each PDCCH candidate according to one or more monitored DCI formats. The set of PDCCH candidates monitored by terminal device 1 is defined as a PDCCH search space set. A search space set is either a common search space set or a UE-specific search space set. In the above description, a search space set is referred to as a search space, a common search space set as a common search space, and a UE-specific search space set as a UE-specific search space. Terminal device 1 monitors PDCCH candidates in one or more of the following search space sets.

[0177] - Type 0 PDCCH common search space set: This search space set is set according to the search space SIB1 (searchSpaceSIB 1) indicated by pdcch-ConfigSIB 1 or PDCCH-ConfigCommon as a parameter of the upper layer, or the search space zero included in PDCCH-ConfigCommon. This search space is used for monitoring DCI format scrambled CRC by SI-RNRI in the primary cell.

[0178] - Type 0A-PDCCH common search space set: This search space set is set according to the search space (searchSpaceOtherSystemInformation) indicated by PDCCH-ConfigCommon, which is a parameter of the upper layer. This search space is used for monitoring DCI format scrambled CRC by SI-RNRI in the primary cell.

[0179] - Type 1 PDCCH common search space set: This search space set is configured according to the search space (ra-SearchSpace) used for random access procedures, as indicated by PDCCH-ConfigCommon, a parameter of the upper layer. This search space is used for monitoring DCI format scrambled CRC by RA-RNRI or TC-RNTI in the primary cell. The Type 1 PDCCH common search space set is the search space set used for random access procedures.

[0180] - A Type 2-PDCCH common search space set: This search space set is configured according to the paging search space indicated by PDCCH-ConfigCommon, a parameter of the upper layer. This search space is used for monitoring DCI format scrambled CRC by P-RNTI in the primary cell.

[0181] - Type 3 PDCCH common search space set: This search space set is configured as a common search space according to the search space type indicated by the PDCCH-Config parameter used as the upper layer. This search space is used for monitoring the DCI format of CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. It is used for monitoring the primary cell in DCI format of CRC scrambled by C-RNTI, CS-RNTI(s), or MSC-C-RNTI.

[0182] - A UE-specific search space set: This search space set is set according to the UE-specific search space type indicated by the PDCCH-Config, which is a parameter of the upper layer. This search space is used for monitoring DCI format scrambled by C-RNTI, CS-RNTI(s), or MSC-C-RNTI.

[0183] If terminal device 1 is provided with one or more search space sets according to the corresponding upper-layer parameters (searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.), and terminal device 1 is provided with C-RNTI or CS-RNTI, terminal device 1 can monitor PDCCH candidates for DCI format 0_0 and DCI format 1_0 with C-RNTI or CS-RNTI in the one or more search space sets.

[0184] The configuration information for a BWP is divided into configuration information for a DL BWP and configuration information for a UL BWP. The configuration information for a BWP includes the information element bwp-Id (the identifier of the BWP). The BWP identifier included in the configuration information of a DL BWP is used to identify (reference) a DL BWP in a serving cell. The BWP identifier included in the configuration information of a UL BWP is used to identify (reference) a UL BWP in a serving cell. Identifiers are assigned to DL BWPs and UL BWPs respectively. For example, the identifier of a BWP corresponding to a DL BWP can also be called the DL BWP index. The identifier of a BWP corresponding to a UL BWP can also be called the UL BWP index. The initial DL BWP is referenced by the DL BWP identifier 0. The initial UL BWP is referenced by the UL BWP identifier 0. Other DL BWPs or other UL BWPs can be referenced by BWP identifiers 1 to maxNrofBWPs respectively. In other words, the identifier of a BWP set to 0 (bwp-Id = 0) is associated with the initial BWP and cannot be used for other BWPs. `maxNrofBWPs` is the maximum number of BWPs per serving cell, which is 4. That is, the identifiers of other BWPs take values ​​from 1 to 4. Other upper-layer configuration information uses the BWP identifier to associate with a specific BWP. The fact that DLBWPs and UL BWPs have the same BWP identifier can mean that the DL BWP and UL BWP are paired.

[0185] Terminal device 1 can be configured with one primary cell and up to 15 secondary cells.

[0186] The following describes the process of receiving PDSCH.

[0187] Terminal device 1 can decode (receive) the corresponding PDSCH by detecting a PDCCH including DCI format 1_0 or DCI format 1_1. The corresponding PDSCH is scheduled (indicated) according to its DCI format (DCI). The start position (start symbol) of the scheduled PDSCH is called S. The start symbol S of the PDSCH can be the first symbol of the PDSCH transmitted (mapped) in a certain time slot. The start symbol S corresponds to the start of the time slot. For example, when the value of S is 0, terminal device 1 can receive the PDSCH starting from the first symbol in a certain time slot. Furthermore, for example, when the value of S is 2, terminal device 1 can receive the PDSCH starting from the third symbol in a certain time slot. The number of consecutive symbols of the scheduled PDSCH is called L. The number of consecutive symbols L is counted starting from the start symbol S. The determination of S and L allocated to the PDSCH will be described later.

[0188] The PDSCH mapping has two types: PDSCH mapping type A and PDSCH mapping type B. In PDSCH mapping type A, S takes a value from 0 to 3. L takes a value from 3 to 14. The sum of S and L is a value from 3 to 14. In PDSCH mapping type B, S takes a value from 0 to 12. L takes a value from {2, 4, 7}. The sum of S and L is a value from 2 to 14.

[0189] The position of the DMRS symbol used by PDSCH depends on the type of PDSCH mapping. The position of the first DMRS symbol used by PDSCH also depends on the type of PDSCH mapping. In PDSCH mapping type A, the position of the first DMRS symbol is indicated by the upper-level parameter dmrs-TypeA-Position. That is, the upper-level parameter dmrs-TypeA-Position is used to indicate the position of the first DMRS used by PDSCH or PUSCH. dmrs-TypeA-Position can be set to either "pos2" or "pos3". For example, when dmrs-TypeA-Position is set to "pos2", the position of the first DMRS symbol used by PDSCH can be the third symbol in the time slot. For example, when dmrs-TypeA-Position is set to "pos3", the position of the first DMRS symbol used by PDSCH can be the fourth symbol in the time slot. Here, S can only take the value 3 when dmrs-TypeA-Position is set to "pos3". That is, when dmrs-TypeA-Position is set to "pos2", S takes a value between 0 and 2. In PDSCH mapping type B, the position of the first DMRS symbol is the first symbol of the assigned PDSCH.

[0190] Figure 7 This is a diagram illustrating an example of the PDSCH mapping type in this embodiment. Figure 7 (A) is a diagram representing an example of PDSCH mapping type A. In Figure 7 In (A), the S value of the assigned PDSCH is 3. The L value of the assigned PDSCH is 7. Figure 7 In (A), the position of the first DMRS symbol used by PDSCH is the fourth symbol in the time slot. That is, dmrs-TypeA-Position is set to "pos3". Figure 7 (B) is a diagram representing an example of PDSCH mapping type A. In Figure 7In (B), the S value of the assigned PDSCH is 4. The L value of the assigned PDSCH is 4. Figure 7 In (B), the position of the first DMRS symbol used by PDSCH is the first symbol assigned to PDSCH.

[0191] The following explains the method for determining the time-domain resource allocation of PDSCH.

[0192] Base station device 3 can schedule PDSCH reception by enabling terminal device 1 to receive it via DCI. Furthermore, terminal device 1 can receive PDSCH by detecting DCI destined for itself. When determining the time-domain resource allocation for PDSCH, terminal device 1 first determines the resource allocation table applied to that PDSCH. The resource allocation table includes one or more PDSCH time-domain resource allocation configurations. Then, terminal device 1 can select a PDSCH time-domain resource allocation configuration from the determined resource allocation table based on the value indicated by the "Time domain resource assignment" field included in the DCI scheduling the PDSCH. That is, base station device 3 determines the resource allocation for PDSCH for terminal device 1, generates the value of the "Time domain resource assignment" field, and sends the DCI including the "Time domain resource assignment" field to terminal device 1. Terminal device 1 determines the resource allocation in the time direction of the PDSCH based on the value set in the "Time domain resource assignment" field.

[0193] Figure 10 This is a diagram that defines which resource allocation table will be applied to the PDSCH time-domain resource allocation. Terminal device 1 can refer to this. Figure 10 A resource allocation table is determined for use in PDSCH time-domain resource allocation. The resource allocation table includes configurations for one or more PDSCH time-domain resource allocations. In this embodiment, the resource allocation tables are classified into (I) predefined resource allocation tables and (II) resource allocation tables set according to upper-layer RRC signals. The predefined resource allocation tables are defined as default PDSCH time-domain resource allocation A, default PDSCH time-domain resource allocation B, and default PDSCH time-domain resource allocation C. Hereinafter, default PDSCH time-domain resource allocation A will be referred to as default table A. Default PDSCH time-domain resource allocation B will be referred to as default table B. Default PDSCH time-domain resource allocation C will be referred to as default table C.

[0194] Figure 11 This is a diagram illustrating an example of the default table A in this implementation. Figure 12This is a diagram illustrating an example of the default table B in this implementation. Figure 13 This is a diagram illustrating an example of the default table C in this implementation. (Refer to...) Figure 11 The default table A contains 16 rows. Each row in the default table A represents the configuration of PDSCH time-domain resource allocation. For more details, see... Figure 11In the table, the indexed row defines the PDSCH mapping type, the slot offset K0 between the PDCCH (including DCI) and the PDSCH, the starting symbol S of the PDSCH within the slot, and the number of consecutively allocated symbols L. The resource allocation table, set according to the upper-layer RRC signal, is provided by the upper-layer signal pdsch-TimeDomainAllocationList. The information element PDSCH-TimeDomainResourceAllocation represents the configuration of PDSCH time-domain resource allocation. PDSCH-TimeDomainResourceAllocation can be used to set the time-domain relationship between the PDCCH (including DCI) and the PDSCH. pdsch-TimeDomainAllocationList includes one or more information elements PDSCH-TimeDomainResourceAllocation. That is, pdsch-TimeDomainAllocationList is a list containing one or more elements (information elements). A single information element PDSCH-TimeDomainResourceAllocation can also be referred to as an entry (or row). pdsch-TimeDomainAllocationList can contain up to 16 entries. Each entry can be defined by K0, mappingType, and startSymbolAndLength. K0 represents the slot offset between the PDCCH (including DCI) and the PDSCH. If PDSCH-TimeDomainResourceAllocation does not indicate K0, terminal device 1 can assume the value of K0 is 0. mappingType represents either PDSCH mapping type A or PDSCH mapping type A. startSymbolAndLength is an index that gives a valid combination of the starting symbol S and the number of consecutively allocated symbols L of the PDSCH. startSymbolAndLength can also be called the start and length indicator SLIV. That is, unlike the default table that directly defines the start symbol S and the consecutive symbols L, the start symbol S and the consecutive symbols L are given based on SLIV. Base station device 3 can set the value of SLIV so that the time domain resource allocation of the PDSCH does not exceed the slot boundary. The slot offset K0 and SLIV will be described later.

[0195] The upper-layer signal pdsch-TimeDomainAllocationList can be included in pdsch-ConfigCommon and / or pdsch-Config. The information element pdsch-ConfigCommon is used to set cell-specific parameters for the PDSCH of a specific BWP. The information element pdsch-Config is used to set UE-specific parameters for the PDSCH of a specific BWP.

[0196] Figure 14 This is a diagram representing an example of SLIV computation.

[0197] exist Figure 14 In this context, 14 represents the number of symbols included in the time slot. Figure 14 This illustrates an example of calculating SLIV in the case of NCP (Normal Cyclic Prefix). The SLIV value is calculated based on the number of symbols included in the time slot, the start symbol S, and the number of consecutive symbols L. Here, the value of L is equal to or greater than 1, and does not exceed (14-S). When calculating SLIV in the case of ECP, Figure 14 The numbers 7 and 14 in the original text use 6 and 12.

[0198] The following is an explanation of the time slot offset K0.

[0199] As described above, in the subcarrier spacing setting μ, the time slots are counted in ascending order from 0 to N^{subframe, μ}_{slot}-1 within a subframe, and in ascending order from 0 to N^{frame, μ}_{slot}-1 within a frame. K0 is the number of time slots based on the PDSCH subcarrier spacing. K0 can take values ​​from 0 to 32. Within a subframe or frame, the time slot numbers are counted in ascending order from 0. The time slot number n for a subcarrier spacing setting of 15kHz corresponds to the time slot numbers 2n and 2n+1 for a subcarrier spacing setting of 30kHz.

[0200] Terminal device 1 detects the DCI of the PDSCH scheduling. The time slot allocated to this PDSCH is determined by (Equation 1) Floor(n*2) μPDSCH / 2 μPDCCH Given )+K0. The function Floor(A) outputs the largest integer not higher than A. n is the time slot of the PDCCH that detects and schedules the PDSCH. μ PDSCH This refers to the subcarrier spacing setting for PDSCH. μ PDCCH This refers to the subcarrier spacing setting for the PDCCH.

[0201] Terminal device 1 can refer to Figure 10To determine which resource allocation table to apply to the PDSCH time-domain resource allocation. That is, terminal device 1 can determine the resource allocation table to apply to the PDSCH scheduled by DCI based on some or all of the following elements (A) to (F).

[0202] Element A: The type of RNTI used to scramble the CRC appended to the DCI.

[0203] Element B: Detects the type of search space for the DCI.

[0204] Element C: Whether the CORESET associated with this search space is CORESET#0

[0205] Does element D: pdsch-ConfigCommon include pdsch-TimeDomainAllocationList?

[0206] Element E: Does pdsch-Config include pdsch-TimeDomainAllocationList?

[0207] Element F: SS / PBCH and CORESET multiplexing mode

[0208] In element A, the type of RNTI used to scramble the CRC appended to the DCI is any one of SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI.

[0209] In element B, the search space type for detecting DCI is either a common search space or a UE-specific search space. Common search spaces include: Type 0 common search space, Type 1 common search space, and Type 2 common search space.

[0210] As an example A, terminal device 1 can detect DCI in any common search space associated with CORESET#0. The detected DCI is appended with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, or CS-RNTI. Furthermore, terminal device 1 can determine the resource allocation table applied to the PDSCH scheduled via this DCI. If pdsch-TimeDomainAllocationList is included in terminal device 1's pdsch-ConfigCommon, terminal device 1 can determine the resource allocation table set according to the upper-layer RRC signal. This resource allocation table is given by pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon. Furthermore, if pdsch-TimeDomainAllocationList is not included in terminal device 1's pdsch-ConfigCommon, terminal device 1 can determine a default table A. That is, terminal device 1 can use the default table A, representing the configuration of PDSCH time-domain resource allocation, to determine the PDSCH time-domain resource allocation.

[0211] Furthermore, as Example B, terminal device 1 can detect DCI in any common search space not associated with CORESET#0. The detected DCI is appended with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, or CS-RNTI. Moreover, terminal device 1 can determine the resource allocation table applied to the PDSCH scheduled via this DCI. If terminal device 1's pdsch-Config includes pdsch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to the PDSCH time-domain resource allocation as given by pdsch-TimeDomainAllocationList provided in pdsch-Config. That is, if pdsch-Config includes pdsch-TimeDomainAllocationList, terminal device 1 can use pdsch-TimeDomainAllocationList provided in pdsch-Config to determine the PDSCH time-domain resource allocation, regardless of whether pdsch-ConfigCommon includes or does not include pdsch-TimeDomainAllocationList. Furthermore, if pdsch-Config does not include pdsch-TimeDomainAllocationList but pdsch-ConfigCommon does, terminal device 1 can determine the resource allocation table applied to PDSCH time-domain resource allocation as the resource allocation table given by pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon. That is, terminal device 1 uses pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon to determine PDSCH time-domain resource allocation. Furthermore, if pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include pdsch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to PDSCH time-domain resource allocation as default table A.

[0212] Furthermore, as an example C, terminal device 1 can detect DCI in the UE-specific search space. The detected DCI is appended with a CRC scrambled by any one of C-RNTI, MCS-C-RNTI, or CS-RNTI. Moreover, terminal device 1 can determine the resource allocation table applied to the PDSCH scheduled via this DCI. If terminal device 1's pdsch-Config includes pdsch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to the PDSCH time-domain resource allocation as given by pdsch-TimeDomainAllocationList provided in pdsch-Config. That is, if pdsch-Config includes pdsch-TimeDomainAllocationList, regardless of whether pdsch-ConfigCommon includes or does not include pdsch-TimeDomainAllocationList, terminal device 1 can use pdsch-TimeDomainAllocationList provided in pdsch-Config to determine the PDSCH time-domain resource allocation. Furthermore, if pdsch-Config does not include pdsch-TimeDomainAllocationList but pdsch-ConfigCommon does, terminal device 1 can determine the resource allocation table applied to PDSCH time-domain resource allocation as the resource allocation table given by pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon. That is, terminal device 1 uses pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon to determine PDSCH time-domain resource allocation. Furthermore, if pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include pdsch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to PDSCH time-domain resource allocation as default table A.

[0213] As can be seen from Examples B and C, the method for determining the resource allocation table for PDSCHs detected in the UE-specific search space is the same as the method for determining the resource allocation table for PDSCHs detected in any public search space that is not associated with CORESET#0.

[0214] Next, terminal device 1 can select a PDSCH time domain resource assignment configuration from the determined resource assignment table based on the value indicated by the "Time domain resource assignment" field included in the DCI that schedules the PDSCH. For example, if the resource assignment table applied to the PDSCH time domain resource assignment is the default table A, the value m indicated by the "Time domain resource assignment" field can indicate the row index m+1 of the default table A. In this case, the PDSCH time domain resource assignment is the configuration of the time domain resource assignment indicated by the row index m+1. Terminal device 1 assumes that the PDSCH is received by the configuration of the time domain resource assignment indicated by the row index m+1. For example, if the value m indicated by the "Time domain resource assignment" field is 0, terminal device 1 uses the configuration of the PDSCH time domain resource assignment at row index 1 of the default table A to determine the resource allocation in the time direction of the PDSCH scheduled by the DCI.

[0215] Furthermore, when the resource allocation table used for PDSCH time-domain resource allocation is provided by pdsch-TimeDomainAllocationList, the value m indicated by the "Time domain resource assignment" field corresponds to the (m+1)th element (entry, row) in the pdsch-TimeDomainAllocationList. For example, if the value m indicated by the "Time domain resource assignment" field is 0, terminal device 1 can refer to the first element (entry) in the pdsch-TimeDomainAllocationList. For example, if the value m indicated by the "Time domain resource assignment" field is 1, terminal device 1 can refer to the second element (entry) in the pdsch-TimeDomainAllocationList.

[0216] The following explains the number of bits (size) of the "Time domain resource assignment" field included in DCI.

[0217] Terminal device 1 can decode (receive) the corresponding PDSCH by detecting a PDCCH including DCI format 1_0 or DCI format 1_1. The number of bits in the "Time domain resource assignment" field included in DCI format 1_0 can be a fixed number of bits. For example, this fixed number of bits can be 4. That is, the size of the "Time domain resource assignment" field included in DCI format 1_0 can be 4 bits. Furthermore, the size of the "Time domain resource assignment" field included in DCI format 11 can be a variable number of bits. For example, the number of bits in the "Time domain resource assignment" field included in DCI format 1_1 can be any one of 0, 1, 2, 3, or 4.

[0218] The following explains how to determine the number of bits in the "Time domain resource assignment" field included in DCI format 1_1.

[0219] The number of bits in the "Time domain resource assignment" field included in DCI format 1_1 can be given at least based on: (I) whether pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList and / or (II) whether pdsch-Config includes pdsch-TimeDomainAllocationList and / or (III) the number of rows included in a predefined default table. In this embodiment, DCI format 11 is supplemented with a CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI. DCI format 11 can be detected in the UE-specific search space. In this embodiment, "pdsch-Config includes pdsch-TimeDomainAllocationList" can mean "pdsch-Config provides pdsch-TimeDomainAllocationList". "pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList" can mean "pdsch-ConfigCommon provides pdsch-TimeDomainAllocationList".

[0220] The number of bits for the "Time domain resource assignment" field can be given as `ceiling(log2(I))`. The function `Ceiling(A)` outputs the smallest integer not less than A. When `pdsch-TimeDomainAllocationList` is set (provided) for terminal device 1, the value of I can be the number of entries included in `pdsch-TimeDomainAllocationList`. When `pdsch-TimeDomainAllocationList` is not set (provided) for terminal device 1, the value of I can be the number of rows in the default table (default table A). That is, when `pdsch-TimeDomainAllocationList` is set for terminal device 1, the number of bits for the "Time domain resource assignment" field can be given based on the number of entries included in `pdsch-TimeDomainAllocationList`. When `pdsch-TimeDomainAllocationList` is not set for terminal device 1, the number of bits for the "Time domain resource assignment" field can be given based on the number of rows in the default table (default table A). Specifically, when pdsch-Config includes pdsch-TimeDomainAllocationList, the value of I can be the number of entries included in the pdsch-TimeDomainAllocationList provided in pdsch-Config. Furthermore, when pdsch-Config does not include pdsch-TimeDomainAllocationList but pdsch-ConfigCommon does, the value of I can be the number of entries included in the pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon. Additionally, when both pdsch-Config and pdsch-ConfigCommon do not include pdsch-TimeDomainAllocationList, the value of I can be the number of rows included in the default table (e.g., default table A).

[0221] Furthermore, to put it another way, when pdsch-TimeDomainAllocationList is set (provided) for terminal device 1, the number of bits in the "Time domain resource assignment" field can be given as ceiling(log2(I)). When pdsch-TimeDomainAllocationList is not set (provided) for terminal device 1, the number of bits in the "Time domain resource assignment" field can be a fixed number of bits. For example, the fixed number of bits can be 4 bits.

[0222] Here, I can be the number of entries included in pdsch-TimeDomainAllocationList. Specifically, if pdsch-Config includes pdsch-TimeDomainAllocationList, the value of I can be the number of entries included in the pdsch-TimeDomainAllocationList provided in pdsch-Config. Furthermore, if pdsch-Config does not include pdsch-TimeDomainAllocationList but pdsch-ConfigCommon does, the value of I can be the number of entries included in the pdsch-TimeDomainAllocationList provided in pdsch-ConfigCommon.

[0223] Therefore, terminal device 1 can determine the number of bits in the "Time domain resource assignment" field generated by base station device 3. That is, terminal device 1 can accurately receive the PDSCH scheduled by base station device 3 with terminal device 1 as the destination.

[0224] The following describes the process of receiving PUSCH.

[0225] Terminal device 1 can transmit the corresponding PUSCH by detecting a PDCCH including DCI format 0_0 or DCI format 0_1. That is, the corresponding PUSCH can be scheduled (indicated) by its DCI format (DCI). Furthermore, the PUSCH can be scheduled by the RAR UL authorization included in the RAR message. The starting position (start symbol) of the scheduled PUSCH is called S. The start symbol S of the PUSCH can be the first symbol of the PUSCH transmitted (mapped) within a certain time slot. The start symbol S corresponds to the start of the time slot. For example, when the value of S is 0, terminal device 1 can start transmitting the PUSCH from the first symbol in a certain time slot. Furthermore, for example, when the value of S is 2, terminal device 1 can start transmitting the PUSCH from the third symbol in a certain time slot. The number of consecutive symbols of the scheduled PUSCH is called L. The number of consecutive symbols L is counted from the start symbol S. The determination of S and L allocated to the PUSCH will be described later.

[0226] The PUSCH mapping types are PUSCH mapping type A and PUSCH mapping type B. In PUSCH mapping type A, the value of S is 0. L takes a value from 4 to 14. The sum of S and L takes a value from 4 to 14. In PUSCH mapping type B, S takes a value from 0 to 13. L takes a value from 1 to 14. The sum of S and L takes a value from 1 to 14.

[0227] The position of the DMRS symbol used by the PUSCH depends on the type of PUSCH mapping. The position of the first DMRS symbol used by the PUSCH also depends on the PUSCH mapping type. In PUSCH mapping type A, the position of the first DMRS symbol is indicated by the upper-level parameter dmrs-TypeA-Position. dmrs-TypeA-Position is set to either "pos2" or "pos3". For example, if dmrs-TypeA-Position is set to "pos2", the position of the first DMRS symbol used by the PUSCH could be the third symbol within the time slot. Similarly, if dmrs-TypeA-Position is set to "pos3", the position of the first DMRS symbol used by the PUSCH could be the fourth symbol within the time slot. In PUSCH mapping type B, the position of the first DMRS symbol could be the first symbol of the assigned PUSCH.

[0228] The following explains the method for determining the time-domain resource allocation for PUSCH.

[0229] Base station device 3 can schedule PUSCH transmission by enabling terminal device 1 to send it via DCI. Furthermore, terminal device 1 can transmit PUSCH by detecting DCI destined for itself. When determining the time-domain resource allocation for a PUSCH, terminal device 1 first determines the resource allocation table applied to that PUSCH. The resource allocation table includes one or more PUSCH time-domain resource allocation configurations. Then, terminal device 1 can select a PUSCH time-domain resource allocation configuration from the determined resource allocation table based on the value indicated by the "Time domain resource assignment" field included in the DCI that schedules the PUSCH. That is, base station device 3 determines the PUSCH resource allocation for terminal device 1, generates the value of the "Time domain resource assignment" field, and sends the DCI including the "Time domain resource assignment" field to terminal device 1. Terminal device 1 determines the resource allocation for the PUSCH in the time direction based on the value set in the "Time domain resource assignment" field.

[0230] Figure 16 This is a graph that defines which resource allocation table will be applied to the PUSCH time-domain resource allocation. Terminal device 1 can refer to this. Figure 16 To determine the resource allocation table applied to PUSCH time-domain resource allocation. The resource allocation table includes the configuration of one or more PUSCH time-domain resource allocations. In this embodiment, the resource allocation table is classified into (I) a predefined resource allocation table and (II) a resource allocation table set according to the upper-layer RRC signal. The predefined resource allocation table is defined as the default PUSCH time-domain resource allocation A. Hereinafter, the default PUSCH time-domain resource allocation A will be referred to as the PUSCH default table A.

[0231] Figure 17 This is a diagram showing an example of the PUSCH default table A for NCP (Normal Cyclic Prefix). (Refer to...) Figure 17 The PUSCH default table A consists of 16 rows. Each row in the PUSCH default table A represents the configuration of PUSCH time-domain resource allocation. For more details, see... Figure 17In the table, the indexed row defines the PUSCH mapping type, the slot offset K2 between the PUSCH including DCI, the starting symbol S of the PUSCH within the slot, and the number L of consecutively allocated symbols. The resource allocation table, set according to the upper-layer RRC signal, is provided by the upper-layer signal pusch-TimeDomainAllocationList. The information element PUSCH-TimeDomainResourceAllocation represents the configuration of PUSCH time-domain resource allocation. PUSCH-TimeDomainResourceAllocation can be used to set the time-domain relationship between the PDCCH including DCI and the PUSCH. pusch-TimeDomainAllocationList includes one or more information elements PUSCH-TimeDomainResourceAllocation. That is, pusch-TimeDomainAllocationList is a list containing one or more elements (information elements). An information element PDSCH-TimeDomainResourceAllocation can also be referred to as an entry (or row). pusch-TimeDomainAllocationList can include up to 16 entries. Each entry can be defined by K2, mappingType, and startSymbolAndLength. K2 represents the slot offset between the PDCCH including DCI and the scheduled PUSCH. If PUSCH-TimeDomainResourceAllocation does not indicate K2, then terminal device 1 may assume a value of 1 for a PUSCH subcarrier spacing of 15kHz or 30kHz, a value of 2 for a PUSCH subcarrier spacing of 60kHz, and a value of 3 for a PUSCH subcarrier spacing of 120kHz. mappingType represents either PUSCH mapping type A or PUSCH mapping type A. startSymbolAndLength is an index that gives a valid combination of the start symbol S of the PUSCH and the number of consecutively allocated symbols L. startSymbolAndLength can also be called the start and length indicator SLIV. That is, unlike the default table that directly defines the start symbol S and the consecutive symbols L, the start symbol S and the consecutive symbols L are given based on SLIV. Base station device 3 can set the SLIV value to ensure that the time-domain resource allocation of PUSCH does not exceed the time slot boundary. For example... Figure 14As shown in the formula, the value of SLIV is calculated based on the number of symbols included in the time slot, the start symbol S, and the number of consecutive symbols L.

[0232] The upper-layer signal `pusch-TimeDomainAllocationList` can be included in `pusch-ConfigCommon` and / or `pusch-Config`. The `pusch-ConfigCommon` information element is used to set cell-specific parameters for PUSCH of a specific BWP. The `pusch-Config` information element is used to set UE-specific parameters for PUSCH of a specific BWP.

[0233] Terminal device 1 detects and schedules the DCI for the PUSCH. The time slot for sending this PUSCH is determined by (Equation 4) Floor(n*2). μPUSCH / 2 μPDCCH Given )+K2. n is the time slot of the PDCCH used to detect and schedule the PUSCH. μ PUSCH This refers to the subcarrier spacing setting for PUSCH. μ PDCCH This refers to the subcarrier spacing setting for the PDCCH.

[0234] exist Figure 17 In this context, K2 is any one of j, j+1, j+2, or j+3. The value of j is determined based on the subcarrier spacing of the PUSCH. For example, when the subcarrier spacing of the PUSCH is 15kHz or 30kHz, j can be one time slot. For example, when the subcarrier spacing of the PUSCH is 60kHz, j can be two time slots. For example, when the subcarrier spacing of the PUSCH is 120kHz, j can be three time slots.

[0235] As described above, terminal device 1 can refer to Figure 16 This determines which resource allocation table to apply to the PUSCH time-domain resource allocation.

[0236] As an example D, terminal device 1 can determine the resource allocation table applied to PUSCH scheduled via RAR UL authorization. If the terminal device 1's `pusch-ConfigCommon` includes `pusch-TimeDomainAllocationList`, terminal device 1 can determine the resource allocation table set according to the upper-layer RRC signal. This resource allocation table is given by `pusch-TimeDomainAllocationList` included in `pusch-ConfigCommon`. Furthermore, if the terminal device 1's `pusch-ConfigCommon` does not include `pusch-TimeDomainAllocationList`, terminal device 1 can determine the PUSCH default table A. That is, terminal device 1 can use the default table A, which represents the configuration of PUSCH time-domain resource allocation, to determine the PUSCH time-domain resource allocation.

[0237] Furthermore, as an example E, terminal device 1 can detect DCI in any common search space associated with CORESET#0. The detected DCI is appended with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, TC-RNTI, or CS-RNTI. Moreover, terminal device 1 can determine the resource allocation table applied to the PUSCH scheduled via this DCI. If the pusch-ConfigCommon for terminal device 1 includes pusch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to the PUSCH time-domain resource allocation as the one given by pusch-TimeDomainAllocationList provided in pusch-ConfigCommon. Furthermore, if pusch-ConfigCommon does not include pusch-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to the PUSCH time-domain resource allocation as the PUSCH default table A.

[0238] Furthermore, as an example F, terminal device 1 can detect DCI in (I) any common search space associated with CORESET#0 or (II) a UE-specific search space. The detected DCI is appended with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, TC-RNTI, or CS-RNTI. Moreover, terminal device 1 can determine the resource allocation table applied to the PUSCH scheduled via this DCI. If the terminal device 1 push-Config includes push-TimeDomainAllocationList, terminal device 1 can determine the resource allocation table applied to the PUSCH time-domain resource allocation as given by the push-TimeDomainAllocationList provided in the push-Config. That is, if the push-Config includes push-TimeDomainAllocationList, regardless of whether push-ConfigCommon includes or does not include push-TimeDomainAllocationList, terminal device 1 can use the push-TimeDomainAllocationList provided in the push-Config to determine the PUSCH time-domain resource allocation. Furthermore, if `pusch-Config` does not include `pusch-TimeDomainAllocationList` but `pusch-ConfigCommon` does, terminal device 1 can determine the resource allocation table applied to PUSCH time-domain resource allocation as the resource allocation table given by `pusch-TimeDomainAllocationList` provided in `pusch-ConfigCommon`. That is, terminal device 1 uses `pusch-TimeDomainAllocationList` provided in `pusch-ConfigCommon` to determine PUSCH time-domain resource allocation. Furthermore, if neither `pusch-Config` nor `pusch-TimeDomainAllocationList` is included, terminal device 1 can determine the resource allocation table applied to PUSCH time-domain resource allocation as the PUSCH default table A.

[0239] Next, terminal device 1 can select a PUSCH time domain resource allocation configuration from the determined resource allocation table based on the value indicated by the "Time domain resource assignment" field included in the DCI that schedules the PUSCH. For example, if the resource allocation table applied to the PUSCH time domain resource allocation is the PUSCH default table A, the value m indicated by the "Time domain resource assignment" field can indicate the row index m+1 of the default table A. In this case, the PUSCH time domain resource allocation is the configuration of the time domain resource allocation indicated by row index m+1. Terminal device 1 assumes that the PUSCH is sent using the configuration of the time domain resource allocation indicated by row index m+1. For example, if the value m indicated by the "Time domain resource assignment" field is 0, terminal device 1 uses the PUSCH time domain resource allocation configuration of row index 1 of the PUSCH default table A to determine the resource allocation in the time direction of the PUSCH scheduled by the DCI.

[0240] Furthermore, when the resource allocation table applied to PUSCH time-domain resource allocation is a resource allocation table provided by pusch-TimeDomainAllocationList, the value m indicated by the "Time domain resource assignment" field corresponds to the (m+1)th element (entry, row) in the pusch-TimeDomainAllocationList. For example, if the value m indicated by the "Time domain resource assignment" field is 0, terminal device 1 can refer to the first element (entry) in the pusch-TimeDomainAllocationList. For example, if the value m indicated by the "Time domain resource assignment" field is 1, terminal device 1 can refer to the second element (entry) in the pusch-TimeDomainAllocationList.

[0241] The following explains the number of bits (size) of the "Time domain resource assignment" field included in DCI.

[0242] Terminal device 1 can transmit the corresponding PUSCH by detecting a PDCCH including DCI format 0_0 or DCI format 0_1. The number of bits in the "Time domain resource assignment" field included in DCI format 0_0 can be a fixed number of bits. For example, this fixed number of bits can be 4. That is, the size of the "Time domain resource assignment" field included in DCI format 0_0 can be 4 bits. Furthermore, the size of the "Time domain resource assignment" field included in DCI format 0_1 ​​can be a variable number of bits. For example, the number of bits in the "Time domain resource assignment" field included in DCI format 0_1 ​​can be any one of 0, 1, 2, 3, or 4.

[0243] The following explains how to determine the number of bits in the "Time domain resource assignment" field included in DCI format 0_1.

[0244] The number of bits in the "Time domain resource assignment" field can be given as ceiling(log2(I)). When a push-TimeDomainAllocationList is set (provided) for terminal device 1, the value of I can be the number of entries included in the push-TimeDomainAllocationList. When a push-TimeDomainAllocationList is not set (provided) for terminal device 1, the value of I can be the number of rows in the default PUSCH table A. That is, when a push-TimeDomainAllocationList is set for terminal device 1, the number of bits in the "Time domain resource assignment" field can be given based on the number of entries included in the push-TimeDomainAllocationList. When a push-TimeDomainAllocationList is not set for terminal device 1, the number of bits in the "Time domain resource assignment" field can be given based on the number of rows in the default table (default table A). Specifically, when push-Config includes a push-TimeDomainAllocationList, the value of I can be the number of entries included in the push-TimeDomainAllocationList provided in push-Config. Furthermore, if pusch-Config does not include pusch-TimeDomainAllocationList but pusch-ConfigCommon does, the value of I can be the number of entries included in the pusch-TimeDomainAllocationList provided in pusch-ConfigCommon. Additionally, if pusch-Config does not include pusch-TimeDomainAllocationList and pusch-ConfigCommon does not include pusch-TimeDomainAllocationList, the value of I can be the number of rows included in the PUSCH default table A.

[0245] The following describes the slot aggregation transmission (multi-slot transmission) of this embodiment.

[0246] The upper-layer parameter `pusch-AggregationFactor` indicates the number of times data (transmission block) is repetitively transmitted. The upper-layer parameter `pusch-AggregationFactor` indicates any of values ​​2, 4, and 8. The base station device 3 can send the upper-layer parameter `pusch-AggregationFactor`, representing the number of repetitions of data transmission, to the terminal device 1. The base station device 3 can use `pusch-AggregationFactor` to cause the terminal device 1 to repetitively transmit the transmission block a specified number of times. The terminal device 1 can receive the upper-layer parameter `pusch-AggregationFactor` from the base station device 3 and repetitively transmit the transmission block using the number of repetitions indicated by `pusch-AggregationFactor`. However, the terminal device 1 can treat the number of repetitions of the transmission block as 1 if it does not receive `pusch-AggregationFactor` from the base station device. That is, in this case, the terminal device 1 can transmit the transmission block scheduled by the PDCCH once. In other words, terminal device 1 can skip time-slot aggregation transmission (multi-slot transmission) of the transport block scheduled by PDCCH without receiving the pusch-AggregationFactor from the base station device.

[0247] Specifically, terminal device 1 can receive a PDCCH in DCI format, including a CRC scrambled by C-RNTI and MCS-C-RNTI, and send PUSCHs scheduled through this PDCCH. With a pusch-AggregationFactor set for terminal device 1, terminal device 1 can send N PUSCHs in N consecutive time slots starting from the time slot where the initial PUSCH is sent. One PUSCH transmission (transmission of a transport block) can be performed in each time slot. That is, the transmission of the same transport block (repeated transmission) occurs only once in a time slot. The value of N is indicated by the pusch-AggregationFactor. If the pusch-AggregationFactor is not set for terminal device 1, the value of N can be 1. The time slot for the initial PUSCH transmission can be given as described above (Equation 4). The PUSCH time-domain resource allocation based on the PDCCH used for scheduling PUSCHs can be applied to N consecutive time slots. In other words, the same symbol allocation (the same starting symbol S and the same number of consecutively allocated symbols L) can be applied to N consecutive time slots. Terminal device 1 can repeatedly transmit the transport block in N consecutive time slots starting from the time slot where the PUSCH was initially transmitted. Terminal device 1 can use the same symbol allocation to repeatedly transmit the transport block in each time slot. When the upper-layer parameter pusch-AggregationFactor is set, the time slot aggregation transmission performed by terminal device 1 can also be called the first aggregation transmission. That is, the upper-layer parameter pusch-AggregationFactor is used to indicate the number of repetition transmissions used for the first aggregation transmission. The upper-layer parameter pusch-AggregationFactor is also called the first aggregation transmission parameter.

[0248] In the first aggregate transmission, the 0th transmission occasion can be located in the time slot where the initial PUSCH is transmitted. The 1st transmission occasion can be located in the time slot following the initial PUSCH transmission. The Nth transmission occasion can be located in the Nth time slot from the initial PUSCH transmission. The redundancy version applied to the transmission of a transport block can be based on the rv indicated by the nth transmission occasion (n-1)th transmission occasion of that transport block and the DCI scheduling PUSCH. idTo determine this, the redundant version of the sequence is {0, 2, 3, 1}. The variable rv... id This is the index to the sequence of redundancy versions. This variable is updated modulo 4. Redundancy versions are used for encoding (rate matching) transport blocks sent via PUSCH. Redundancy versions can increment in the order of 0, 2, 3, 1. Repeated transmission of transport blocks can be performed in the order of redundancy versions.

[0249] Figure 15 This is a diagram illustrating an example of a redundant version applied to a transmission opportunity.

[0250] like Figure 15 As shown, the redundant version rv applied to the first transmission opportunity id This is the value indicated by the DCI that schedules the PUSCH (transmission block). For example, terminal device 1 will set the DCI that schedules the PUSCH to rv. id When the value indicates 0, refer to Figure 15 The first line determines the redundant version rv provided for the transmission opportunity. id The redundant versions applied to the transmission opportunity can be incremented in the order of 0, 2, 3, 1. For example, terminal device 1 will use rv in the DCI that schedules PUSCH. id When the value indicates 2, refer to Figure 15 The second line determines the redundant version rv provided for transmission opportunities. id The redundant versions applied to the transmission opportunity can be incremented in the order of 2, 3, 1, 0.

[0251] If at least one symbol in the symbol allocation for a given transmission opportunity is indicated by upper-layer parameters as a downlink symbol, the terminal device 1 may not transmit a transport block in the time slot of that transmission opportunity.

[0252] In this embodiment, the base station device 3 can send the upper-layer parameter pusch-AggregationFactor-r16 to the terminal device 1. The upper-layer parameter pusch-AggregationFactor-r16 can be used to indicate the number of repetition transmissions of data (transmission blocks). The upper-layer parameter pusch-AggregationFactor-r16 can also be used to indicate the number of repetition transmissions for slot aggregation transmission and / or mini-slot aggregation transmission. Slot aggregation transmission and mini-slot aggregation transmission will be described later.

[0253] In this embodiment, pusch-AggregationFactor-r16 is set to any value among n1, n2, and n3. The values ​​of n1, n2, and n3 can be 2, 4, 8, or other values. n1, n2, and n3 represent the number of times the transport block is retransmitted. That is, pusch-AggregationFactor-r16 can indicate a value for the number of retransmissions. The number of retransmissions of the transport block may be the number of retransmissions within a time slot (N...). rep (etc.), which may include the number of repeated transmissions within and between time slots (N) total (etc.), which may be the number of repeated transmissions between time slots (N) total (etc.). Alternatively, the base station device 3 can send a pusch-AggregationFactor-r16 containing more than one element to the terminal device 1, so as to more flexibly set the number of repetitions for the terminal device 1. Each element (information element, entry) can be used to indicate the number of repetitions of a transport block. That is, the pusch-AggregationFactor-r16 can indicate the value of the number of repetitions for more than one. In this embodiment, the slot aggregation transmission performed by the terminal device 1 when the upper-layer parameter pusch-AggregationFactor-r16 is set can also be called the second aggregation transmission. That is, the upper-layer parameter pusch-AggregationFactor-r16 can at least be used to indicate the number of repetitions for the second aggregation transmission. The upper-layer parameter pusch-AggregationFactor-r16 is also called the second aggregation transmission parameter. Moreover, the base station device 3 can indicate any element through the fields included in the DCI of the scheduled transport block and notify the terminal device 1 of the number of repetitions of that transport block. The specific process will be described later. Furthermore, the base station device 3 can indicate any element via MAC CE (MAC Control Element) and notify the terminal device 1 of the number of times the transport block is retransmitted. That is, the base station device 3 can indicate any element via the fields included in the DCI and / or MAC CE, and dynamically notify the terminal device 1 of the number of times it is retransmitted. Applying the function of dynamic retransmission count to the terminal device 1 means that the base station device 3 dynamically notifies the terminal device 1 of the number of retransmissions.

[0254] As a first example, base station device 3 may not send push-AggregationFactor and push-AggregationFactor-r16 to terminal device 1. That is, push-AggregationFactor and push-AggregationFactor-r16 may not be set for terminal device 1. In other words, terminal device 1 may receive RRC messages from base station device 3 that do not include (do not set) push-AggregationFactor and push-AggregationFactor-r16. In this case, terminal device 1 may send PUSCH in the time slots given by (Equation 4) as described above. In other words, the number of times the transport block is retransmitted may be 1. That is, terminal device 1 may not perform time slot aggregation transmission and / or mini time slot aggregation transmission.

[0255] Furthermore, as a second example, base station device 3 can send push-AggregationFactor to terminal device 1 but not push-AggregationFactor-r16. That is, push-AggregationFactor can be set for terminal device 1, but not push-AggregationFactor-r16. In other words, terminal device 1 can receive an RRC message from base station device 3 that includes (sets) push-AggregationFactor but does not include (does not set) push-AggregationFactor-r16. In this case, terminal device 1 can send N PUSCHs in N consecutive time slots starting from the time slot given by (Equation 4) as described above. That is, the number of times the transport block is repeatedly sent can be N, as indicated by push-AggregationFactor. Terminal device 1 can perform a first aggregation transmission of the PUSCH scheduled by the DCI. The PDCCH of the DCI that schedules the PUSCH can be sent in the CSS or in the USS. The same symbol assignment can be applied to N consecutive time slots.

[0256] Furthermore, as a third example, base station device 3 may not send push-AggregationFactor to terminal device 1, but may send push-AggregationFactor-r16 to terminal device 1. That is, push-AggregationFactor may not be set for terminal device 1, but push-AggregationFactor-r16 may be set for terminal device 1. In other words, terminal device 1 may receive RRC messages from base station device 3 that do not include (do not set) push-AggregationFactor, but include (set) push-AggregationFactor-r16. In this case, terminal device 1 may send M PUSCHs in one or more time slots starting from the time slot given by (Equation 4) as described above. Unlike the first aggregation transmission, the multiple time slots may be consecutive or discontinuous. That is, the number of times the transport block is repeatedly transmitted, M, may be indicated by push-AggregationFactor-r16. The PDCCH of the DCI that schedules the PUSCH may be sent in the CSS or in the USS. The same symbol allocation may not apply to multiple time slots. That is, the PUSCH time-domain resource allocation (symbol allocation) for the retransmission of the first transport block can be given based on the DCI that schedules that transport block. However, the PUSCH symbol allocation for the retransmission of subsequent transport blocks can differ from the symbol allocation given based on the PDCCH (DCI, etc.) that schedules the PUSCH. This is called symbol allocation extension. Specifically, the starting symbol S for the retransmission of subsequent transport blocks can differ from the starting symbol S given based on that PDCCH (starting symbol extension). For example, the starting symbol S for the retransmission of subsequent transport blocks can be the 0th symbol, which is the start of the time slot. Furthermore, the starting symbol S for the retransmission of subsequent transport blocks can be the same as the starting symbol S given based on the PDCCH. For example, the starting symbol S for the retransmission of subsequent transport blocks can be the first available symbol from the start of the time slot. Furthermore, the number L of consecutively allocated symbols in the PUSCH for repeated transmissions of transport blocks starting from the second transmission can differ from the number L of consecutively allocated symbols given based on the PDCCH (symbol number extension). Alternatively, the number L of consecutively allocated symbols in the PUSCH for repeated transmissions of transport blocks starting from the second transmission can be the same as the number L of consecutively allocated symbols given based on the PDCCH. The starting symbol and / or the number of symbols in each repeated transmission can be determined based on the available symbols.The number of symbols L for the Xth PUSCH can be determined based on one, more, or all of the following: the starting symbol S given by the PDCCH, the number of symbols L given by the PDCCH, the number of symbols in the time slot, the number of available symbols in the time slot, and N. total N rep and N slots .

[0257] Furthermore, in the third example, when pusch-AggregationFactor-r16 includes one and / or more elements, terminal device 1 can select one element from multiple elements (dynamic repetition count) using the "Repetition Number" field included in the DCI. It can be set such that the "Repetition Number" field included in the DCI exists when pusch-AggregationFactor-r16 includes one and / or more elements; otherwise, the "Repetition Number" field does not exist. Alternatively, it can be set such that the "Repetition Number" field does not exist when pusch-AggregationFactor-r16 is not set. Moreover, the value indicated by the selected element is the number of times the transport block scheduled by the DCI is repeatedly transmitted. Furthermore, terminal device 1 can repeatedly transmit the number of times the transport block is notified. The number of bits in the "Repetition Number" field can be given as ceiling(log2(X+1)) or ceiling(log2(X)). X is the number of elements included in pusch-AggregationFactor-r16. When the number of bits in the "Repetition Number" field is given as ceiling(log2(X)), the value m indicated by the "Repetition Number" field can correspond to the (m+1)th element included in pusch-AggregationFactor-r16. Furthermore, the number of times the transport block is retransmitted can be determined by the value indicated by the (m+1)th element. For example, when the value m indicated by the "Repetition Number" field is 0, terminal device 1 can refer to the first element included in pusch-AggregationFactor-r16. The value indicated by the element can be greater than 1. The value indicated by the element can also be equal to 1. Furthermore, when the number of bits in the "Repetition Number" field is given as ceiling(log2(X+1)), the value m indicated by the "Repetition Number" field can correspond to the mth element included in pusch-AggregationFactor-r16. Here, the value of m is a non-zero value. When the value m indicated by the “Repetition Number” field is 0, terminal device 1 can consider the number of repeated transmissions as 1. The values ​​indicated by each element can be greater than 1.When pusch-AggregationFactor-r16 is configured, the functions of applying symbol allocation extension (start symbol extension and / or symbol number extension), dynamic repetition count and / or mini-slot aggregation transmission are applied to aggregate transmission (second aggregate transmission).

[0258] Furthermore, as a fourth example, base station device 3 can send push-AggregationFactor and push-AggregationFactor-r16 to terminal device 1. That is, push-AggregationFactor and push-AggregationFactor-r16 can be set for terminal device 1. In other words, terminal device 1 can receive an RRC message from base station device 3 including (setting) push-AggregationFactor and push-AggregationFactor-r16. Basically, the symbol allocation extension (start symbol extension and / or symbol number extension), dynamic repetition count, and / or mini-slot aggregation transmission functions described as the actions when push-AggregationFactor-r16 is set are applied, as described in the third example.

[0259] Hereinafter, a terminal device 1 equipped with pusch-AggregationFactor-r16 can determine whether the “RepetitionNumber” field exists in a certain DCI based on at least some or all of the following elements (A) to (D).

[0260] Element A: The type of RNTI used to scramble the CRC appended to the DCI.

[0261] Element B: Detects the type of search space for the DCI.

[0262] Element C: Type of DCI format

[0263] Element D: Information indicated by the fields of DCI

[0264] In element A, it can be set such that: when the type of the RNTI used to scramble the CRC appended to the DCI is any one of SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI, the "Repetition Number" field does not exist in the DCI. Alternatively, it can be set such that: when the type of the RNTI used to scramble the CRC appended to the DCI is NEW-RNTI, the "Repetition Number" field included in the DCI exists.

[0265] In element B, the type of search space monitored by terminal device 1 for DCI is either a common search space or a UE-specific search space. Common search spaces include: Type 0 common search space, Type 1 common search space, and Type 2 common search space. It can be configured such that if the monitored DCI search space is a common search space, the "Repetition Number" field does not exist in that DCI. Alternatively, if the monitored DCI search space is a UE-specific search space, the "Repetition Number" field exists in that DCI.

[0266] In element C, the DCI format type is DCI format 0_0, DCI format 0_1, or DCI format 0_2. It can be set so that the "Repetition Number" field does not exist in the DCI format when it is DCI format 0_0 or DCI format 0_1. Alternatively, it can be set so that the "Repetition Number" field exists in the DCI format when it is DCI format 0_2. Or, it can be set so that the "Repetition Number" field does not exist in the DCI format when it is DCI format 0_0. It can also be set so that the "Repetition Number" field exists in the DCI format when it is DCI format 0_1 ​​or DCI format 0_2.

[0267] Furthermore, for example, it can be configured such that when monitoring DCI format 0_0 in a common search space, the "Repetition Number" field does not exist in that DCI. Alternatively, it can be configured such that when monitoring DCI format 0_0 in a UE-specific search space, the "Repetition Number" field exists in that DCI. Furthermore, for example, it can be configured such that when DCI format 0_1 ​​is scrambled by NEW-RNTI, the "Repetition Number" field exists in that DCI. Alternatively, it can be configured such that when DCI format 0_1 ​​is scrambled by an RNTI other than NEW-RNTI, the "Repetition Number" field does not exist in that DCI.

[0268] Hereinafter, the terminal device 1 equipped with pusch-AggregationFactor-r16 can determine whether to apply the functions described above for pusch-AggregationFactor-r16 to the PUSCH transmission scheduled by the DCI based at least on one or all of the following elements (A) to (C).

[0269] Element A: The type of RNTI used to scramble the CRC appended to the DCI.

[0270] Element B: Detects the type of search space for the DCI.

[0271] Element C: Type of DCI format

[0272] In element A, the function can be configured such that, when the type of the RNTI used to scramble the CRC appended to the DCI is any one of SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI, the pusch-AggregationFactor-r16 function is not configured for the PUSCH transmission application scheduled by the DCI. Alternatively, the function can be configured such that, when the type of the RNTI used to scramble the CRC appended to the DCI is NEW-RNTI, the pusch-AggregationFactor-r16 function is configured for the PUSCH transmission application scheduled by the DCI.

[0273] In element B, the type of search space monitored by terminal device 1 for DCI is either a common search space or a UE-specific search space. Common search spaces include: Type 0 common search space, Type 1 common search space, and Type 2 common search space. Alternatively, if the monitored DCI search space is a common search space, the function of pusch-AggregationFactor-r16 is not configured for the PUSCH transmission application scheduled by that DCI. Or, if the monitored DCI search space is a UE-specific search space, the function of pusch-AggregationFactor-r16 is configured for the PUSCH transmission application scheduled by that DCI.

[0274] In element C, the DCI format type is DCI format 0_0, DCI format 0_1, or DCI format 0_2. It can be that, when the DCI is DCI format 0_0 or DCI format 0_1, the function of `pusch-AggregationFactor-r16` is not configured for the PUSCH sending application scheduled by that DCI. Alternatively, when the DCI is DCI format 0_2, the function of `pusch-AggregationFactor-r16` is configured for the PUSCH sending application scheduled by that DCI. Or, when the DCI is DCI format 0_0, the function of `pusch-AggregationFactor-r16` is not configured for the PUSCH sending application scheduled by that DCI. It can also be that, when the DCI is DCI format 0_1 ​​or DCI format 0_2, the function of `pusch-AggregationFactor-r16` is configured for the PUSCH sending application scheduled by that DCI.

[0275] Furthermore, for example, it could be that when monitoring DCI format 0_0 in the common search space, the function is not configured with pusch-AggregationFactor-r16 for the PUSCH transmission application scheduled by that DCI. Alternatively, it could be that when monitoring DCI format 0_0 in the UE-specific search space, the function is configured with pusch-AggregationFactor-r16 for the PUSCH transmission application scheduled by that DCI.

[0276] As described above, without the function of setting pusch-AggregationFactor-r16, if pusch-AggregationFactor is set, a first aggregation transmission can be performed during PUSCH transmissions scheduled by this DCI. That is, terminal device 1 can repeatedly transmit transport blocks N times in N consecutive time slots. The value of N can be given by pusch-AggregationFactor. The same symbol allocation can be applied in the N time slots. Furthermore, without the function of setting pusch-AggregationFactor-r16, if pusch-AggregationFactor is not set, a single PUSCH transmission scheduled by this DCI can be performed. That is, terminal device 1 can transmit a transport block once.

[0277] The following describes the mini-slot aggregation transmission (mini-slot aggregation transmission, subslot aggregation transmission, multi-subslot transmission, intra-slot aggregation transmission) of this embodiment.

[0278] As described above, in slot aggregation transmission (slot aggregation transmission in the first and second aggregation transmissions), an uplink grant can schedule two or more PUSCH retransmissions. Each retransmission takes place in a consecutive time slot (or in each available time slot). That is, in slot aggregation, the same transport block is retransmitted at most once within a time slot (an available time slot). The available time slot can be the time slot in which the transport block retransmission actually takes place.

[0279] In mini-slot aggregation transmission, an uplink grant can schedule two or more PUSCH retransmissions. Retransmissions can occur within the same time slot or in consecutive available time slots. In this scheduled PUSCH retransmission, the number of retransmissions in each time slot can differ based on the available symbols in the PUSCH retransmission within that time slot (available time slot). That is, in mini-slot aggregation transmission, the same transport block can be retransmitted once or more than once within a single time slot (available time slot). In other words, in mini-slot aggregation transmission, terminal device 1 can transmit more than one retransmission of the same transport block to base station device 3 within a single time slot. In other words, mini-slot aggregation transmission can also be described as supporting a mode of aggregation within time slots. The symbol allocation extension (starting symbol extension and / or symbol number extension) and / or dynamic retransmission count described above can be applied to mini-slot aggregation transmission.

[0280] In this embodiment, the terminal device 1 can determine whether to apply aggregated transmission or any aggregated transmission type to the PUSCH transmission scheduling the uplink authorization based at least on (I) upper-layer parameters and / or (II) fields included in the uplink grant. The aggregated transmission type may include a first aggregated transmission and a second aggregated transmission. As another example, the second aggregated transmission type may also be divided into slotted aggregated transmission and mini-slotted aggregated transmission. That is, the aggregated transmission type may include a first slotted aggregated transmission (first aggregated transmission), a second slotted aggregated transmission (slot aggregation in the second aggregated transmission), and a mini-slotted aggregated transmission.

[0281] In Scheme A of this embodiment, the base station device 3 can notify the terminal device 1, through upper-layer parameters, which of the two is to be configured for slot aggregation transmission and mini-slot aggregation transmission. The configuration of which is configured for slot aggregation transmission and mini-slot aggregation transmission can refer to the application of slot aggregation transmission and mini-slot aggregation transmission. For example, `pusch-AggregationFactor` can be used to indicate the number of repetitions of the first aggregation transmission (first slot aggregation transmission). `pusch-AggregationFactor-r16` can be used to indicate the number of repetitions of the second slot aggregation transmission and / or mini-slot aggregation transmission. `pusch-AggregationFactor-r16` can be a parameter common to both the second slot aggregation transmission and / or mini-slot aggregation transmission. The upper-layer parameter `repTxWithinSlot-r16` can be used to indicate mini-slot aggregation transmission. When the upper-layer parameter `repTxWithinSlot-r16` is set to valid, the terminal device 1 can be considered to be performing mini-slot aggregation transmission by applying mini-slot aggregation transmission to the transport block transmission. In other words, when terminal device 1 is configured with both `pusch-AggregationFactor-r16` and `repTxWithinSlot-r16` (set to active), terminal device 1 can be considered to be applying mini-slot aggregation transmission. The number of repetitions for mini-slot aggregation transmission can be indicated by `pusch-AggregationFactor-r16`. Furthermore, when terminal device 1 is configured with `pusch-AggregationFactor-r16` but not with `repTxWithinSlot-r16`, terminal device 1 can be considered to be applying second-slot aggregation transmission. The number of repetitions for second-slot aggregation transmission can be indicated by `pusch-AggregationFactor-r16`. Additionally, when terminal device 1 is configured with `pusch-AggregationFactor` but not with `pusch-AggregationFactor-r16`, terminal device 1 can be considered to be applying first-slot aggregation transmission. Furthermore, if the pusch-AggregationFactor and pusch-AggregationFactor-r16 are not set for terminal device 1, terminal device 1 can be considered as not applying aggregation transmission and sending a PUSCH with a single uplink grant. In this embodiment, setting the upper-layer parameter (e.g., repTxWithinSlot-r16) can mean making the upper-layer parameter (e.g., repTxWithinSlot-r16) valid, or it can mean sending the upper-layer parameter (e.g., repTxWithinSlot-r16) from base station device 3.In this embodiment, not setting the upper-layer parameter (e.g., repTxWithinSlot-r16) can mean that the upper-layer parameter (e.g., repTxWithinSlot-r16) is set to invalid, or it can mean that the upper-layer parameter (e.g., repTxWithinSlot-r16) is not sent from the base station device 3.

[0282] In Scheme B of this embodiment, the base station device 3 can notify the terminal device 1, through upper-layer parameters, which of the two methods—split-area aggregation transmission and mini-split-area aggregation transmission—is being used. `pusch-AggregationFactor` can be used to indicate the number of repetitions for the first split-area aggregation transmission. `pusch-AggregationFactor-r16` can be used to indicate the number of repetitions for the second split-area aggregation transmission and / or mini-split-area aggregation transmission. `pusch-AggregationFactor-r16` can be a parameter common to both the second split-area aggregation transmission and / or mini-split-area aggregation transmission. With `pusch-AggregationFactor-r16` set for the terminal device 1, the second split-area aggregation transmission and / or mini-split-area aggregation transmission can be applied to the terminal device 1.

[0283] Next, terminal device 1 can further determine whether to apply slot aggregation transmission or mini-slot aggregation transmission based on fields included in the uplink grant for scheduling PUSCH transmission (PUSCH repetitive transmission). As an example, a field included in the uplink grant can be used to indicate whether to apply slot aggregation transmission or mini-slot aggregation transmission. This field can be 1 bit. Furthermore, terminal device 1 can determine whether to apply slot aggregation transmission or mini-slot aggregation transmission based on this field included in the uplink grant sent from base station device 3. Terminal device 1 can determine whether to apply slot aggregation transmission or mini-slot aggregation transmission when the field indicates 0, and apply mini-slot aggregation transmission when the field indicates 1.

[0284] Furthermore, as an example, terminal device 1 can determine whether to perform application slot aggregation transmission or mini slot aggregation transmission based on the "Time domain resource assignment" field included in the uplink grant sent from base station device 3. As described above, the "Time domain resource assignment" field is used to indicate the PUSCH time domain resource allocation. Terminal device 1 can determine whether to perform application slot aggregation transmission or mini slot aggregation transmission based on whether the number of symbols L exceeds a predetermined value, wherein the number of symbols L is the number of consecutively allocated symbols obtained based on the "Time domain resource assignment" field. Terminal device 1 can determine application slot aggregation transmission if the number of symbols L exceeds the predetermined value. Alternatively, terminal device 1 can determine application mini slot aggregation transmission if the number of symbols L does not exceed the predetermined value. The predetermined value can be a value indicated by parameters from the upper layer. The predetermined value can also be a value predefined in the specification. Furthermore, for example, the predetermined value can also be 7 symbols.

[0285] In Scheme C of this embodiment, the base station device 3 can notify the terminal device 1, through upper-layer parameters, which of the two methods—second time-slot aggregation transmission and mini time-slot aggregation transmission—is being used. For example, the base station device 3 can separately set upper-layer parameters indicating the number of repetitions for second time-slot aggregation transmission and mini time-slot aggregation transmission. For example, pusch-AggregationFactor-r16 can be used to indicate the number of repetitions for second time-slot aggregation transmission. pusch-MiniAggregationFactor-r16 can be used to indicate the number of repetitions for mini time-slot aggregation transmission. The base station device 3 can send the corresponding upper-layer parameters when it wants to set either second time-slot aggregation transmission or mini time-slot aggregation transmission for the terminal device 1. That is, when the base station device 3 sends pusch-AggregationFactor-r16 to the terminal device 1, the terminal device 1 can be considered to be applying first time-slot aggregation transmission. When the base station device 3 sends pusch-MiniAggregationFactor-r16 to the terminal device 1, the terminal device 1 can be considered to be applying mini time-slot aggregation transmission.

[0286] Furthermore, in schemes A, B, or C of this embodiment, terminal device 1 can determine whether to apply slot aggregation transmission or mini-slot aggregation transmission based on the PUSCH mapping type, which is obtained based on the "Time domain resource assignment" field included in the uplink grant. Specifically, in the case of applying second slot aggregation transmission and / or mini-slot aggregation transmission, terminal device 1 can consider that second slot aggregation transmission and / or mini-slot aggregation transmission are not applied if the PUSCH mapping type obtained based on the "Time domain resource assignment" field is PUSCH mapping type A. Moreover, if a pusch-AggregationFactor is sent from base station device 3, terminal device 1 can determine that first slot aggregation transmission is applied to the PUSCH transmission scheduled for uplink grant. The number of times this slot aggregation transmission is repeated is indicated by the pusch-AggregationFactor. If no pusch-AggregationFactor is sent from base station device 3, terminal device 1 can send the PUSCH scheduled for uplink grant once. In other words, if the first condition is met and the pusch-AggregationFactor is set, terminal device 1 and base station device 3 apply the same symbol assignment in each time slot, repeatedly transmitting the transport block N times in N consecutive time slots. If the pusch-AggregationFactor is not set, the transport block is transmitted once. If the second condition is met, the transport block is transmitted using the second aggregation transmission as described above. Here, the first condition at least includes that the PUSCH mapping type is indicated as type A in the DCI that schedules PUSCH transmission. The second condition at least includes that the PUSCH mapping type is indicated as type B in the DCI that schedules PUSCH transmission. The value of N is given by the pusch-AggregationFactor. That is, the mapping type of the PUSCH using the second time slot aggregation transmission and / or mini time slot aggregation transmission can be type B. The mapping type of the PUSCH using the first time slot aggregation transmission can be either type A or type B.

[0287] The following describes the process of determining the number of repeated transmissions and the frequency hopping process in this embodiment.

[0288] Terminal device 1 can determine N total N total It is the total number of times the same transport block is repeatedly sent through an uplink grant schedule (the total number of repeated PUSCHs). In other words, Ntotal This refers to one or more PUSCH numbers scheduled through an uplink grant. Terminal device 1 can determine N. rep N rep It is the number of times the same transport block is repeatedly sent within a time slot (the number of repeated PUSCHs). In other words, N rep This is the number of one or more PUSCHs configured within a time slot for one or more PUSCHs scheduled via an uplink grant. Terminal device 1 can determine N. slots N slots It is the number of time slots for repeatedly sending the same transport block scheduled through an uplink grant. In other words, N slots This refers to the number of time slots used by one or more PUSCHs authorized for scheduling via an uplink. Terminal device 1 can access N from N. rep and N slots Derive N total Terminal device 1 can also be accessed from N. total and N slots Derive N rep Terminal device 1 can also access N rep and N total Derive N slots N slots It could be 1 or 2. N rep The value N may differ between time slots. repThe values ​​may also be the same between time slots. The upper-layer parameter `frequencyHopping` can be set (provided) for terminal device 1. The upper-layer parameter `frequencyHopping` can be set to either "intraSlot" or "interSlot". When `frequencyHopping` is set to "intraSlot", terminal device 1 can perform PUSCH transmission with intra-slot frequency hopping. That is, setting intra-slot frequency hopping for terminal device 1 means setting `frequencyHopping` to "intraSlot" and setting the value of the "Frequency hopping flag" field included in the DCI scheduling the PUSCH to 1. When `frequencyHopping` is set to "interSlot", terminal device 1 can perform PUSCH transmission with inter-slot frequency hopping. That is, setting inter-slot frequency hopping for terminal device 1 means setting `frequencyHopping` to "interSlot" and setting the value of the "Frequencyhopping flag" field included in the DCI scheduling the PUSCH to 1. Furthermore, if the base station device 3 does not send frequencyHopping to the terminal device 1, the terminal device 1 can perform PUSCH transmission without frequency hopping. That is, not setting frequency hopping for the terminal device 1 may include not sending frequencyHopping. Additionally, not setting frequency hopping for the terminal device 1 may also include setting the value of the "Frequency hopping flag" field included in the DCI that schedules the PUSCH to 0 even if frequencyHopping is sent.

[0289] Figure 8 This is a diagram illustrating an example of frequency hopping in this embodiment. Figure 8 (a) is an example of PUSCH transmission without frequency hopping. Figure 8 (b) is an example of PUSCH transmission with intra-slot frequency hopping. Figure 8 (c) is an example of PUSCH transmission with inter-slot frequency hopping. Figure 8 It can be applied to time-slot aggregation transmission. Figure 8 It can be applied to mini-slot aggregation transmission where the number of repetitions within a time slot is 1.

[0290] exist Figure 8In (b), the PUSCH transmission with in-slot frequency hopping consists of a first frequency hop (first hop, first frequency unit) and a second frequency hop (second frequency hop, first hop, second frequency unit). The number of symbols in the first frequency hop can be determined by Floor(N) PUsCH，s symb / 2) is given. The number of symbols in the second frequency hopping can be given by N. PUSCH，s symb -Floor(N PUsCH，s symb / 2) is given. N PUSCH，s symb It is the length of a PUSCH transmitted in an OFDM symbol within a time slot. That is, N PUSCH，s symb This can be the number of OFDM symbols used in a scheduled PUSCH within a time slot. N PUSCH，s symb The value can be indicated by a field included in the DCI format or the RAR UL license. PUSCH ，s symb It can be the number of consecutively allocated symbols obtained based on the "Time domain resource assignment" field included in the uplink grant that schedules the transmission of this transport block. Alternatively, it can be the difference RB between the starting RB and the resource blocks of the first frequency hopping. offset This is called the frequency offset of a resource block. That is, RB offset It refers to the frequency offset of the RB between the two frequency hopping frequencies. Alternatively, the RB can also be... offset This is called the frequency offset used for the second frequency hopping. For example, the starting RB of the first frequency hopping is called RB. start The starting frequency hopping RB can be determined by (Equation 5) (RB) start+ RB offset )modN size BwP Given. RB start This can be given by the frequency resource allocation field included in the DCI that schedules the PUSCH. size BwP This is the size of the activated BWP (the number of physical resource blocks). The function (A)mod(B) divides A by B and outputs the remainder if the division is not exact. Frequency offset RB offsetThe value is set according to the higher-level parameter `frequencyHoppingOffsetLists` included in `PUSCH-Config`. The higher-level parameter `frequencyHoppingOffsetLists` is used to indicate the frequency offset (frequency hopping offset) value when frequency hopping is applied. Figure 8 In (b), intra-slot frequency hopping can be applied to single-slot PUSCH transmission and / or multi-slot (slot aggregation) PUSCH transmission.

[0291] exist Figure 8 In (c), inter-slot frequency hopping can be applied to multi-slot PUSCH transmission. RB offset It is the frequency offset of the RB between two frequency hopping frequencies. The starting RB of a PUSCH transmitted in a certain time slot can be based on the time slot number n. u s To determine. In n u s When mod2 is 0, the starting RB of the PUSCH in this time slot is RB. start In n u s When mod2 is 1, the starting RB of PUSCH in this time slot can be determined by (Equation 5) (RB) start+ RB offset )mod N size BwP Given. RB start This can be given by the frequency resource allocation field included in the DCI that schedules the PUSCH. Figure 8 In (c), terminal device 1 repeatedly transmits the same transport block in two consecutive time slots.

[0292] Intra-slot frequency hopping can be applied to single-slot transmission or time-slot aggregation transmission. Inter-slot frequency hopping can be applied to time-slot aggregation transmission.

[0293] Figure 9 This is a diagram illustrating another example of determining the number of repeated transmissions and frequency hopping in this embodiment. Figure 9 (a) is an example of PUSCH transmission without frequency hopping. Figure 9 (b) is an example of PUSCH transmission with intra-slotfrequency hopping. Figure 9 (c) is another example of PUSCH transmission with intra-slotfrequency hopping. Figure 9(d) is an example of PUSCH transmission with inter-slot frequency hopping. Figure 9 It can be applied to time-slot aggregation transmission. For example... Figure 9 The frequency hopping shown can be applied to mini-slot aggregation transmission. Or, as... Figure 9 The frequency hopping shown can be applied to mini-slot aggregation transmissions that are repeated more than once within a single time slot. Figure 9 (a) indicates the case where frequency hopping is not set, time slot aggregation is not set, or the number of times slot aggregation is 1, and the number of times mini time slot aggregation is 4. In this case, N rep =4, N total =1, N slots =1.

[0294] When frequencyHopping is set to "intraSlot", mini-slot aggregation transmission within a time slot consists of a first frequency hopping and a second frequency hopping within that time slot. The number of repeated transmissions included in the first frequency hopping can be determined by Floor(N). rep / 2) is given. The number of repeated transmissions included in the second frequency hopping can be given by N. rep -Floor(N rep / 2) is given. N rep This refers to the number of times the same transport block is repeatedly transmitted within that time slot. Furthermore, the difference RB between the starting RB and the resource block between the starting RB of the first frequency hopping can also be used. offset This is called the frequency offset of a resource block. That is, RB offset It refers to the frequency offset of the RB between the two frequency hopping frequencies. Alternatively, the RB can also be... offset This is called the frequency offset used for the second frequency hopping. For example, the starting RB of the first frequency hopping is called RB. start The starting frequency hopping RB can be determined by (Equation 5) (RB) start+ RB offset )modN size BwP Given. RB start This can be given by the frequency resource allocation field. The function (A)mod(B) divides A by B and outputs the remainder if the division is not exact. In N rep When the value is 1, the number of frequency hopping operations can be 1. That is, when frequencyHopping is set to "intraSlot", terminal device 1 can perform PUSCH transmission without intra-slot frequency hopping. The starting RB for intra-slot frequency hopping PUSCH transmission can be determined by (Equation 5) (RB) start+ RB offset )mod N sizeBwP Given. Furthermore, even in N rep If the value is 1, it can also be considered that the number of frequency hoppings is 2. That is, the number of symbols for the first frequency hopping can be 0, and the number of symbols for the second frequency hopping can be N. rep *N PUsCH，s symb .

[0295] exist Figure 9 In (b), the total number of times the transport block is repeatedly transmitted, N total The total number of repeated transmissions, N, is 4. total Notification can be made via parameters from the upper layer and / or fields within the DCI that are scheduled to be sent in the transport block. Figure 9 In (b), N tota1 The next transport block is sent repeatedly (N) total The PUSCH transmission occurs within a single time slot. Figure 9 In (b), N is within a time slot rep =4, PUSCH transmission can include N rep = 4 retransmissions of the same transport block. The first frequency hopping includes the initial (Floor(N)) rep / 2) = 2) repeated transmissions. The second frequency hopping includes (N rep -Floor(N rep / 2) = 2) repeated transmissions. The first frequency hopping includes the symbols corresponding to the first two repeated transmissions. The second frequency hopping includes the symbols corresponding to the last two repeated transmissions. At this time, N rep =4, N total =1, N slots =1.

[0296] exist Figure 9 In (c), the total number of times the transport block is repeatedly transmitted is N. total It is 7. N total Notification can be made via parameters from the upper layer and / or fields within the DCI that are scheduled to be sent in the transport block. Figure 9 In (c), N total The transmission block is repeatedly transmitted within a single time slot. Furthermore, terminal device 1 can perform intra-slot frequency hopping for each time slot in which the transmission block is repeatedly transmitted. Figure 9 In (c), within the initial time slot, PUSCH transmission may include N rep = 4 retransmissions of the same transport block. The first frequency hopping includes the initial (Floor(N)) rep / 2) = 2) repeated transmissions. The second frequency hopping includes (N rep -Floor(N rep / 2) = 2) repeated transmissions. The first frequency hopping includes the symbols corresponding to the first two repeated transmissions within the time slot. The second frequency hopping includes the symbols corresponding to the last two repeated transmissions within the time slot. In the next time slot, PUSCH transmission may include N rep = 3 retransmissions of the same transport block. The first frequency hopping includes the initial (Floor(N)) rep / 2) = 1) repeated transmissions. The second frequency hopping includes (N) rep -Floor(N rep / 2) = 2) repeated transmissions. The first frequency hopping includes the symbols corresponding to the first repeated transmission within the time slot. The second frequency hopping includes the symbols corresponding to the last two repeated transmissions within the time slot. The symbol corresponding to one repeated transmission in time slot A can be the same as or different from the symbol corresponding to one repeated transmission in time slot B. The symbols corresponding to repeated transmissions in time slot A or time slot B can be the same or different. At this time, N in time slot A rep =4, N in time slot B rep =3, N total =7, N slots =2.

[0297] exist Figure 9 In (d), the total number of times the transport block is repeatedly transmitted is N. total It is 7. N total The transmission block is repeatedly transmitted within a single time slot. Furthermore, terminal device 1 performs inter-slot frequency hopping to repeatedly transmit the transmission block. RB offset It is the frequency offset of the RB between two frequency hopping frequencies. The starting RB of a PUSCH transmitted in a certain time slot can be based on the time slot number n. u s To determine. In n u s When mod2 is 0, the starting RB of the PUSCH in this time slot is RB. start In n u s When mod2 is 1, the starting RB of PUSCH in this time slot can be determined by (Equation 5) (RB) start+ RB offset )modN size BWP Given. RB start This can be given by the frequency resource allocation field included in the DCI of the PUSCH scheduling. At this time, N in slot A... rep =4, N in time slot B rep =3, N total =7, N slots =2.

[0298] exist Figure 9 In (d), for example, in the notified N total In the case of 4, terminal device 1 performs all repetitive transmissions within one time slot (time slot A). That is, in time slot B, terminal device 1 may not repetitively transmit the same transport block. In this case, terminal device 1 can be considered as not applying inter-slot frequency hopping. That is, terminal device 1 can be considered as not setting frequency hopping and performing non-frequency hopping PUSCH transmission. That is, the RB transmitted within this time slot... start It can be given not based on the slot number, but by the frequency resource allocation field included in the DCI. Furthermore, in this case, it can be considered as applying frequency hopping within the slot, performing actions such as... Figure 9 Frequency hopping within the time slot shown in (b). At this time, N in time slot A... rep =4, N in time slot B rep =0, N total =4, N slots =1.

[0299] Hereinafter, another example of intra-slot frequency hopping in this embodiment will be described.

[0300] The terminal device 1 that sets the frequency hopping within a time slot can determine the first frequency hopping and the second frequency hopping based on the number of times the same transmission block is repeatedly transmitted within a time slot.

[0301] Terminal device 1 can determine the number of symbols for the first frequency hopping as Floor(N) if the number of retransmissions of the same transport block within a time slot is 1. PUSCH，s symb / 2), the number of symbols in the second frequency hopping is determined to be N. PUSCH，s symb -Floor(N PUSCH，s symb / 2). That is, it can be that, when the number of repeated transmissions of the same transport block within a time slot is 1, the number of symbols in the first frequency hopping is determined by Floor(N). PUSCH，s symb / 2) is given, the number of symbols in the second frequency hopping is given by N PUSCH，s symb -Floor(N PUSCH ，s symb / 2) is given. Here, N is... PUSCH，s symb It can be the length of the PUSCH transmission within an OFDM symbol in a time slot. N PUSCH ，s symbIt can be the number of consecutively allocated symbols obtained based on the "Time domain resource assignment" field included in the uplink grant that schedules the transmission of this transport block. That is, N PUSCH，s symb It can be the number of symbols corresponding to one repeated transmission of a transport block within a time slot.

[0302] Furthermore, terminal device 1 can determine the number of retransmissions included in the first frequency hopping as Floor(N) if the number of retransmissions of the same transmission block within a time slot is more than 1. rep / 2), the number of repeated transmissions included in the second frequency hopping is determined as N. rep -Floor(N rep / 2). N rep This can be the number of times the same transport block is repeatedly transmitted within that time slot. That is, if the number of times the same transport block is repeatedly transmitted within a time slot is greater than 1, the number of retransmissions included in the first frequency hopping is determined by Floor(N). rep / 2) gives the number of repeated transmissions included in the second frequency hopping, which is given by N. rep -Floor(N rep / 2) is given. The number of symbols for the first frequency hopping can be the symbols corresponding to the repeated transmissions included in the first frequency hopping. The number of symbols for the second frequency hopping can be the symbols corresponding to the repeated transmissions included in the second frequency hopping. For example, the number of symbols for the first frequency hopping can be given by Floor(N) rep / 2)*L is given. The number of symbols in the second frequency hopping can be given by (N) rep -Floor(N rep / 2))*L is given. Here, L can be the number of consecutively allocated symbols obtained based on the "Time domain resource assignment" field included in the uplink grant for retransmission of the scheduled transport block. That is, L can be the number of symbols corresponding to one retransmission of the transport block within a time slot. That is, L can be N as described above. PUSCH，s symb That is, if the same transport block is retransmitted 1 time within a time slot, the number of frequency hopping events in that time slot can be 2.

[0303] Furthermore, the terminal device 1 that sets the frequency hopping within a time slot can determine the number of frequency hoppings within that time slot as N if the number of repeated transmissions of the same transmission block within a time slot is more than 1. rep N repThe number of frequency hopping operations can be the number of times the same transport block is repeatedly transmitted within a time slot. That is, if the same transport block is repeatedly transmitted more than once within a time slot, the number of frequency hopping operations within that time slot can be the value Nrep. The first frequency hopping corresponds to the first repeated transmission of the transport block. The second frequency hopping corresponds to the second repeated transmission of the transport block. The i-th frequency hopping corresponds to the i-th repeated transmission of the transport block. The Nth frequency hopping... rep Frequency hopping corresponds to the repetition of the Nrep-th transport block. That is, i takes values ​​from 1 to Nrep. The starting RB for the ((i-1)mod2=0)-th frequency hopping can be RBstart. The starting RB for the ((i-1)mod2=1)-th frequency hopping can be (Equation 5))(RBstart+RBoffset)mod N. size BwP As mentioned above, RBstart can be given by the frequency resource allocation field included in the DCI that schedules the PUSCH. RB offset It is the frequency offset of the RB between two frequency hopping frequencies indicated by the parameters of the upper layer. That is, RBoffset is the frequency offset of the RB between the first frequency hopping frequency and the second frequency hopping frequency. That is, RBoffset is the frequency offset of the RB between the i-th frequency hopping frequency and the (i+1)-th frequency hopping frequency. Figure 20 This is a diagram illustrating another example of the number of repeated transmissions and frequency hopping in this embodiment. For example... Figure 20 The frequency hopping shown can be applied to mini-slot aggregation transmission. Figure 20 This is an example of PUSCH transmission using in-slot mini-slot transmission with in-slot frequency hopping. Or, as... Figure 20 The frequency hopping shown can be applied to mini-slot aggregation transmissions that are repeated more than once within a single time slot.

[0304] exist Figure 20 In, N total =4, N rep =4, N slots =1. In Figure 20 In this configuration, terminal device 1 can perform intra-slot frequency hopping, which involves repeatedly transmitting a transmission block. The first frequency hopping corresponds to the first repeated transmission of a transmission block. The second frequency hopping corresponds to the second repeated transmission of a transmission block. The third frequency hopping corresponds to the third repeated transmission of a transmission block. The fourth frequency hopping corresponds to the fourth repeated transmission of a transmission block. The starting RB for the first and third frequency hopping can be RBstart. The starting RBs for the second and fourth frequency hopping can be given by the formula (Equation 5) as described above.

[0305] Figure 18 This diagram illustrates another example of determining the number of repeated transmissions and frequency hopping in this embodiment. Figure 18 Assuming N total=2. Figure 18 (a) is an example of PUSCH transmission using frequency-hopping-free intra-slot mini-slot transmission. Figure 18 (b) is an example of PUSCH transmission using frequency-hopping-free inter-slot mini-slot transmission. Figure 18 (c) is an example of PUSCH transmission that employs intra-slot frequency hopping with mini-slot transmission. Figure 18 (d) is an example of PUSCH transmission that employs inter-slot mini-slot transmission with inter-slot frequencyhopping. Figure 18 This can be applied to situations where a second aggregation transmission is configured. For example... Figure 18 The frequency hopping shown can be applied to mini-slot aggregation transmission. Or, as... Figure 18 The frequency hopping shown can be applied to mini-slot aggregation transmissions that are repeated more than once within a single time slot.

[0306] exist Figure 18 In (a), N rep =2, N total =2, N slots =1. For example, terminal device 1 can receive N by using parameters from the upper layer and / or fields within the DCI sent by the scheduler of the transport block. total Terminal device 1 can receive N by using parameters from the upper layer and / or fields within the DCI sent by the scheduler in the transport block. repThe starting symbol S of the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The number L of consecutively allocated symbols in the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The starting symbol S of the second PUSCH can be the first available symbol after the first PUSCH. The starting symbol S of the second PUSCH can also be the first symbol consecutive to the first PUSCH. The number L of consecutively allocated symbols in the second PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. However, the number of consecutively allocated symbols in the second PUSCH is the number of symbols from the starting symbol S of the second PUSCH to the last symbol of the time slot, and does not cross over to the next time slot. Thus, if L symbols from the starting symbol S of the second PUSCH exceed the last symbol number of the time slot, L is the number of symbols from the starting symbol S of the second PUSCH to the last symbol number of the time slot. That is, terminal device 1 and base station device 3 can determine the number of symbols L of the second PUSCH based on one, more, or all of the following: the start symbol S given by the PDCCH, the number of symbols L given by the PDCCH, and the number of symbols in the time slot. In other words, it can be said that mini-time slot aggregation, start symbol extension, and symbol number extension are applied to the second PUSCH. Terminal device 1 and base station device 3 can determine N based on one, more, or all of the following. slots =1:N rep N total The starting symbol S, the number of symbols L, and the number of symbols in the time slot are given based on the PDCCH. Alternatively, terminal device 1 can receive a representation N from base station device 3. slots =1 information. In Figure 18 In (b), N in time slot A rep =1, N in time slot B rep =1, N total =2, N slots =2. For example, terminal device 1 can receive N by using upper-layer parameters and / or scheduling fields within the DCI sent by the transport block. total Terminal device 1 can receive N by using parameters from the upper layer and / or fields within the DCI sent by the scheduler in the transport block. repThe starting symbol S of the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The number L of consecutively allocated symbols in the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. However, the number of consecutively allocated symbols in the first PUSCH is the number of symbols from the starting symbol S of the first PUSCH given based on the PDCCH to the last symbol of the time slot, without crossing into the next time slot. Thus, if L symbols from the starting symbol S of the first PUSCH exceed the last symbol number of the time slot, L is the number of symbols from the starting symbol S of the first PUSCH to the last symbol number of the time slot. That is, terminal device 1 and base station device 3 can determine the number L of symbols in the first PUSCH based on one, more, or all of the following: the starting symbol S given based on the PDCCH, the number L of symbols given based on the PDCCH, and the number of symbols in the time slot. In the absence of mini-time slot aggregation, generally, if the base station device is notified in advance of the number L of symbols that do not cross time slots, no special processing is required; however, in Figure 18 In case (b), the L given based on the PDCCH may be a value taking into account two time slots, thus the processing described above becomes effective. The starting symbol S of the second PUSCH may be the first available symbol in time slot B. The starting symbol S of the second PUSCH may also be the first symbol consecutive to the first PUSCH. The number L of consecutively allocated symbols for the second PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. However, the number of consecutively allocated symbols for the second PUSCH may be the remaining number of symbols used for the transmission of the first PUSCH. That is, the number L of symbols for the second PUSCH can be the number obtained by subtracting the number L of symbols for the first PUSCH from the L given based on the PDCCH. That is, terminal device 1 and base station device 3 may determine the number L of symbols for the second PUSCH based on one, more, or all of the following: the starting symbol S given based on the PDCCH, the number L of symbols given based on the PDCCH, the number of symbols in the time slot, and the number of symbols used in the first PUSCH. That is, it can be said that a start symbol extension and a symbol number extension are applied to the second PUSCH. Terminal device 1 and base station device 3 may determine N based on one, more or all of the following: slots =2:N rep N tota1 The starting symbol S, the number of symbols L, and the number of symbols in the time slot are given based on the PDCCH. Alternatively, terminal device 1 can receive a representation N from base station device 3. slots =2.

[0307] exist Figure 18 In (b), N in time slot A rep =1, N in time slot Brep =1, therefore it is also considered as time slot aggregation. That is, Figure 18 (b) can be a symbol assignment extension (starting symbol extension and / or symbol number extension) in the second aggregation.

[0308] exist Figure 18 In (c), for Figure 18 (a) applies in-slot frequency hopping. N rep =2, N total =2, N slots =1, therefore, the first frequency hopping includes the initial (Floor(N)) rep / 2) = 1) repeated transmissions. The second frequency hopping includes (N) rep -Floor(N rep / 2) = 1) repeated transmissions.

[0309] exist Figure 18 In (d), for Figure 18 (b) applies inter-slot frequency hopping. Terminal device 1 and base station device 3 can be based on N slots This determines whether to apply inter-slot frequency hopping or intra-slot frequency hopping. For example, in N slot When N = 1, frequency hopping within a time slot is applied. slots In the case of 2, frequency hopping within the time slot is applied.

[0310] Figure 19 This diagram illustrates another example of determining the number of repeated transmissions and frequency hopping in this embodiment. Figure 19 Assuming N total =4. Figure 19 (a) is an example of PUSCH transmission using frequency-hopping-free intra-slot mini-slot transmission. Figure 19 (b) is an example of PUSCH transmission using frequency-hopping-free inter-slot mini-slot transmission. Figure 19 (c) is an example of PUSCH transmission that employs intra-slot frequency hopping with mini-slot transmission. Figure 19 (d) is an example of PUSCH transmission that employs inter-slot mini-slot transmission with inter-slot frequencyhopping. Figure 19 This can be applied to situations where a second aggregation transmission is configured. For example... Figure 19 The frequency hopping shown can be applied to mini-slot aggregation transmission. Or, as... Figure 19 The frequency hopping shown can be applied to mini-slot aggregation transmissions that are repeated more than once within a single time slot.

[0311] exist Figure 19In (a), N rep =4, N total =4, N slots =1. For example, terminal device 1 can receive N by using parameters from the upper layer and / or fields within the DCI sent by the scheduler of the transport block. total Terminal device 1 can receive N by using parameters from the upper layer and / or fields within the DCI sent by the scheduler in the transport block. rep The starting symbol S of the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The number L of consecutively allocated symbols for the first PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The starting symbol S of the second PUSCH can be the first available symbol after the first PUSCH. The starting symbol S of the second PUSCH can also be the first symbol consecutive to the first PUSCH. The number L of consecutively allocated symbols for the second PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1. Similarly, the starting symbol S of the Xth PUSCH can be the first available symbol after the (X-1)th PUSCH. The starting symbol S of the Xth PUSCH can also be the first symbol consecutive to the (X-1)th PUSCH. The number L of consecutively allocated symbols for the Xth PUSCH is given based on the PDCCH transmitted from base station device 3 to terminal device 1.

[0312] However, the number of consecutively allocated symbols for the Xth PUSCH is from the starting symbol S of the Xth PUSCH to the last symbol of the time slot, without crossing over to the next time slot. Therefore, if L symbols from the starting symbol S of the Xth PUSCH exceed the last symbol number of the time slot, L is the number of symbols from the starting symbol S of the second PUSCH to the last symbol number of that time slot. Furthermore, the (X+1)th PUSCH transmission takes place in the next time slot. Alternatively, the (X+1)th PUSCH transmission may not take place in the next time slot. This can be based on N. slots This determines whether to send the (X+1)th PUSCH. For example, in N... slots If the value is 1, the (X+1)th PUSCH will not be sent. In N... slots When N = 2, the (X+1)th PUSCH is performed in the next time slot. Alternatively, it can be based on N... rep This determines whether to send the (X+1)th PUSCH. That is, not sending the Nth PUSCH. rep +1 PUSCH sent. Alternatively, it can be based on N. total This determines whether to send the (X+1)th PUSCH. That is, not sending the Nth PUSCH. total+1 PUSCH transmission. That is, terminal device 1 and base station device 3 can determine the symbol number L of the Xth PUSCH based on one, more or all of the following: the start symbol S given based on PDCCH, the symbol number L given based on PDCCH, the symbol number of the time slot, N total N rep and N slots Furthermore, it can be based on N total N rep and N slots The decision to send the (X+1)th PUSCH can be made using one, more, or all of these factors. That is, it can be said that for... Figure 19 (a) The PUSCH transmission applies mini-slot aggregation, start symbol extension, and symbol number extension. Terminal device 1 and base station device 3 can determine N based on one, more, or all of the following: slots =1:N rep N total The starting symbol S, the number of symbols L, and the number of symbols in the time slot are given based on the PDCCH. Alternatively, terminal device 1 can receive a representation N from base station device 3. slots =1.

[0313] In addition, Figure 19 In (a), the starting symbol S of the first transmission opportunity is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The number L of consecutively allocated symbols in the first transmission opportunity is given based on the PDCCH transmitted from base station device 3 to terminal device 1. That is, the first transmission opportunity is used for the transmission of the first PUSCH. Terminal device 1 may transmit the first PUSCH to base station device 3 in the first transmission opportunity. The first PUSCH is the first repetition of the transport block. If a PUSCH is transmitted once, the number of repetitions of the transport block can be incremented by one. That is, the Xth PUSCH (the Xth PUSCH) is the Xth repetition of the repetition of the transport block. The starting symbol S of the second transmission opportunity may be the first available symbol after the first transmission opportunity. The starting symbol S of the second transmission opportunity may be the first symbol consecutive to the first transmission opportunity. The starting symbol S of the second transmission opportunity may be the first available symbol after the most recently transmitted PUSCH. The starting symbol S of the second transmission opportunity may be the first symbol consecutive to the most recently transmitted PUSCH. In the second transmission opportunity, the most recently transmitted PUSCH is the first PUSCH. The number L of consecutively allocated symbols in the second transmission opportunity is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The second PUSCH transmitted in the second transmission opportunity is the second retransmission of the transport block.

[0314] Similarly, the starting symbol S of the Xth transmission opportunity can be the first available symbol after the (X-1)th transmission opportunity. The starting symbol S of the Xth transmission opportunity can be the first symbol consecutive to the (X-1)th transmission opportunity. The starting symbol S of the Xth transmission opportunity can be the first available symbol after the most recently transmitted PUSCH. The starting symbol S of the Xth transmission opportunity can be the first symbol consecutive to the most recently transmitted PUSCH. The number L of consecutively allocated symbols in the Xth transmission opportunity is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The symbols in the Xth transmission opportunity can be available symbols. Furthermore, some or all of the symbols in the Xth transmission opportunity may not be available symbols. That is, all the symbols included in this transmission opportunity cannot be used for PUSCH transmission. In this case, if the number of consecutive available symbols (maximum number) in this transmission opportunity is equal to or greater than the first value, terminal device 1 can transmit the PUSCH to base station device 3 using these consecutive available symbols. If the number of consecutive available symbols (maximum number) in a transmission opportunity is less than a first value, terminal device 1 may not transmit the PUSCH to base station device 3 in that transmission opportunity. Here, the first value may be indicated by upper-layer parameters. The first value may be determined at least based on symbol L, which is given based on PDCCH. For example, the first value may be given by ceiling(L*F). F may be a value less than 1. Alternatively, the first value may be given by (LT). T may be a value equal to or greater than 1. The value of F or T may be indicated by upper-layer parameters. The value of F or T may correspond to different values ​​for different L values.

[0315] However, the consecutively allocated symbols for the Xth transmission opportunity are the symbols from the starting symbol S of the Xth transmission opportunity to the last symbol of the time slot, without crossing into the next time slot. Therefore, the number of symbols L from the starting symbol S of the Xth transmission opportunity to the last symbol number of the time slot is the total number of symbols. Furthermore, the (X+1)th transmission opportunity can be located in the next time slot. In this case, the starting symbol S of the (X+1)th transmission opportunity can be the first available symbol in that time slot. The number L of consecutively allocated symbols for the (X+1)th transmission opportunity is given based on the PDCCH transmitted from base station device 3 to terminal device 1.

[0316] The methods for determining the starting symbol and the number of symbols for each PUSCH described above can also be used in slot aggregation. Figure 21 This diagram illustrates an example of slot aggregation transmission (second aggregation transmission) in this embodiment. For example, Figure 21 The N shown rep =1, N total =3, N slotIn the case of 3, the starting symbol S of the first transmission opportunity is given based on the PDCCH sent from base station device 3 to terminal device 1. The number L of consecutively allocated symbols in the first transmission opportunity (time slot) is given based on the PDCCH sent from base station device 3 to terminal device 1. That is, the first transmission opportunity (time slot) is used for the transmission of the first PUSCH. Terminal device 1 can send the first PUSCH to base station device 3 in the first transmission opportunity (time slot). The first PUSCH is the first repetition of the transport block. If a PUSCH is sent once, the number of repetitions of the transport block can be incremented by one. That is, the Xth PUSCH is the Xth repetition of the repetition of the transport block. The starting symbol S of the second transmission opportunity (time slot) can be the first available symbol in the next time slot of the first transmission opportunity (time slot). The number L of consecutively allocated symbols in the second transmission opportunity (time slot) is given based on the PDCCH sent from base station device 3 to terminal device 1. The second PUSCH sent in the second transmission opportunity is the second repetition of the transport block. Similarly, the starting symbol S of the Xth transmission opportunity (time slot) can be the first available symbol in the next time slot of the (X-1)th transmission opportunity (time slot). The number L of consecutively allocated symbols in the Xth transmission opportunity (time slot) is given based on the PDCCH transmitted from base station device 3 to terminal device 1. The symbols in the Xth transmission opportunity (time slot) can be available symbols. Furthermore, some or all of the symbols in the Xth transmission opportunity (time slot) may not be available symbols. That is, all the symbols included in this transmission opportunity (time slot) cannot be used for PUSCH transmission. In this case, if the number of consecutive available symbols (maximum) in this transmission opportunity (time slot) is equal to or greater than a first value, terminal device 1 can transmit PUSCH to base station device 3 using these consecutive available symbols. If the number of consecutive available symbols (maximum) in this transmission opportunity (time slot) is less than the first value, terminal device 1 may not transmit PUSCH to base station device 3 in this transmission opportunity (time slot). Here, the first value can be indicated by a parameter from a higher level. The first value can be determined at least based on the symbol L, which is given based on PDCCH. For example, the first value can be given by ceiling(L*F). F can be a value less than 1. Alternatively, the first value can be given by (LT). T can be a value equal to or greater than 1. The value of F or T can be indicated by a parameter from a higher level. The value of F or T can correspond to different values ​​for different L values.

[0317] Furthermore, a burst of two or more available symbols can be included in the time slots used for time slot aggregation transmission. For example, in Figure 21In (B), time slot B has a burst 201 of available symbols and a burst 202 of available symbols. A burst of available symbols consists of consecutive available symbols within the time slot. Available symbols exist between burst 201 and burst 202. Terminal device 1 can use either burst 201 or burst 202 to send PUSCH (second) to base station device 3 in time slot B. The number of symbols included in burst 202 is greater than the number of symbols included in burst 201. Terminal device 1 can use the burst with the largest length (the largest number of available symbols) among the multiple bursts to send PUSCH to base station device 3. That is, terminal device 1 can send PUSCH to base station device 3 in burst 202. Furthermore, terminal device 1 can use the earliest burst among the multiple bursts to send PUSCH to base station device 3. That is, terminal device 1 can send PUSCH to base station device 3 in burst 201. Furthermore, terminal device 1 can use the earliest of multiple bursts of the same length to send PUSCH to base station device 3. That is, if the number of symbols included in burst 201 is the same as the number of symbols included in burst 202, terminal device 1 can send PUSCH to base station device 3 in burst 201. Additionally, terminal device 1 can use the earliest of multiple bursts equal to or greater than the first value described above to send PUSCH to base station device 3. Specifically, the starting symbol S of the PUSCH sent in time slot B can be the first symbol (the first available symbol) of the burst used for transmission. The number of consecutively allocated symbols of the PUSCH sent in time slot B can be the number L of consecutively allocated symbols given based on the PDCCH sent from base station device 3 to terminal device 1.

[0318] Therefore, when L symbols from the first symbol of the burst used for transmission exceed the last symbol number of the burst, L is the number of symbols from the first symbol of the burst used for transmission to the last symbol number of the burst. Alternatively, the number of consecutively allocated symbols for the PUSCH transmitted in time slot B can be the length of the burst used for transmission. That is, the number of consecutively allocated symbols for the PUSCH transmitted in time slot B is the number of symbols from the first symbol of the burst used for transmission to the last symbol of the burst, without crossing the burst. Terminal device 1 and base station device 3 can determine the number of symbols L of the transmitted PUSCH based on one, more, or all of the following: the starting symbol S given based on the PDCCH, the number of symbols L given based on the PDCCH, the number of symbols in the time slot, the number of bursts, the number of symbols within a burst, N total N rep and N slots This method can generally be used for time slot A, time slot B, and / or time slot C.

[0319] exist Figure 19 In (b), N in time slot A rep =2, N in time slot B rep =2, N total =4, N slots =2. and Figure 19 Similarly, terminal device 1 and base station device 3 may determine the number of symbols L of the Xth PUSCH based on one, more, or all of the following: the start symbol S given by the PDCCH, the number of symbols L given by the PDCCH, the number of symbols in the time slot, and N. total N rep and N slots Furthermore, it can be based on N total N rep and N slots The X+1th PUSCH can be sent by selecting one, multiple, or all of the options.

[0320] exist Figure 19 In (c), for Figure 19 (a) applies in-slot frequency hopping. N rep =4, N total =4, N slots =1, therefore, the first frequency hopping includes the initial (Floor(N)) rep / 2) = 2) repeated transmissions. The second frequency hopping includes (N rep -Floor(N rep / 2) = 2) repeated transmissions.

[0321] exist Figure 19 In (d), for Figure 19 (b) applies inter-slot frequency hopping. Terminal device 1 and base station device 3 can be based on N slots This determines whether to apply inter-slot frequency hopping or intra-slot frequency hopping. For example, in N slot When N = 1, frequency hopping within a time slot is applied. slots In the case of 2, frequency hopping within the time slot is applied.

[0322] In this embodiment, the ceiling function can be used instead of the floor function in the calculation formula related to frequency hopping within the time slot. As an example, the formula Floor(N) can be used instead of the floor function. rep / 2) uses the ceiling function to replace the floor function, and floor(N) rep / 2) changed to ceiling(N) rep / 2).

[0323] In the uplink transmission of this embodiment, the available symbols can be those that are at least indicated as variable and / or uplink symbols by the upper-layer parameters TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated. That is, the available symbols are not those that are indicated as downlink symbols by the upper-layer parameters TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated. The upper-layer parameters TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigDedicated are used to determine the uplink / downlink TDD configuration.

[0324] However, the usable symbols are at least not those indicated by the upper-layer parameter ssb-PositionsInBurst. ssb-PositionsInBurst is used to indicate the time-domain position of the SS / PBCH block transmitted to base station device 3. That is, terminal device 1 learns the position of the symbol for transmitting the SS / PBCH block through ssb-PositionsInBurst. The symbol for transmitting the SS / PBCH block can also be called the SS / PBCH block symbol. In other words, the usable symbols are not SS / PBCH block symbols.

[0325] However, the available symbols are at least not those indicated by pdcch-ConfigSIB1. That is, the available symbols are not those indicated by pdcch-ConfigSIB1 for the CORESET of the type 0PDCCH common search space set. pdcch-ConfigSIB1 can be included in the MIB or ServingCellConfigCommon.

[0326] Therefore, terminal device 1 can transmit uplink data to base station device 3.

[0327] The configuration of the apparatus in this embodiment will be described below.

[0328] Figure 22 This is a schematic block diagram showing the configuration of the terminal device 1 in this embodiment. (As shown) Figure 22As shown, the terminal device 1 is configured to include a wireless transceiver unit 10 and an upper-layer processing unit 14. The wireless transceiver unit 10 is configured to include an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper-layer processing unit 14 is configured to include a media access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transceiver unit 10 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. The upper-layer processing unit 14 is also referred to as a measurement unit, a selection unit, or a control unit 14.

[0329] The upper-layer processing unit 14 outputs uplink data (also referred to as transport blocks) generated through user operations to the wireless transceiver unit 10. The upper-layer processing unit 14 performs processing at some or all of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Radio Resource Control (RRC) layer. The upper-layer processing unit 14 has the function of determining whether to perform transport block retransmission based on upper-layer signals received from the base station device 3. The upper-layer processing unit 14 determines whether to perform either first aggregation transmission or second aggregation transmission based on upper-layer signals received from the base station device 3. The upper-layer processing unit 14 has the function of controlling symbol allocation extension (start symbol extension and / or symbol number extension), dynamic repetition count, and / or mini-slot aggregation transmission for aggregation transmission (second aggregation transmission) based on upper-layer signals received from the base station device 3. The upper-layer processing unit 14 determines whether to perform frequency hopping transmission of a transport block based on the upper-layer signal received from the base station device 3. The upper-layer processing unit 14 has the function of controlling the setting of the first and second frequency hopping based on the number of times the same transport block is repeatedly transmitted within a time slot. The upper-layer processing unit 14 outputs frequency hopping information, aggregation transmission information, etc., to the wireless transceiver unit 10.

[0330] The upper-layer processing unit 14 has the function of controlling a second number based on upper-layer signals including a first number of retransmissions and / or a DCI field including the first number. The first number may include the number of retransmissions of the same transport block within and between time slots. The second number may be the number of retransmissions of the same transport block within a time slot.

[0331] The Media Access Control (MAC) layer processing unit 15, which is included in the upper-layer processing unit 14, performs MAC layer (Media Access Control) processing. The MAC layer processing unit 15 controls the transmission of scheduling requests based on various setting information / parameters managed by the Radio Resource Control (RRC) layer processing unit 16.

[0332] The upper-layer processing unit 14 includes a radio resource control (RRC) layer processing unit 16, which performs RRC layer (Radio Resource Control) processing. The RRC layer processing unit 16 manages various setting information / parameters for the device itself. The RRC layer processing unit 16 sets various setting information / parameters based on signals received from the upper layer from the base station device 3. That is, the RRC layer processing unit 16 sets various setting information / parameters based on information representing various setting information / parameters received from the base station device 3. The RRC layer processing unit 16 controls (determines) resource allocation based on downlink control information received from the base station device 3.

[0333] The wireless transceiver unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver unit 10 separates, demodulates, and decodes signals received from the base station device 3, and outputs the decoded information to the upper-layer processing unit 14. The wireless transceiver unit 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3. The wireless transceiver unit 10 outputs upper-layer signals (RRC messages), DCI, etc., received from the base station device 3 to the upper-layer processing unit 14. Furthermore, the wireless transceiver unit 10 generates and transmits uplink signals based on instructions from the upper-layer processing unit 14. The wireless transceiver unit 10 can repeatedly transmit transport blocks to the base station device 3 based on instructions from the upper-layer processing unit 14. When repeat transmission of transport blocks is enabled, the wireless transceiver unit 10 repeatedly transmits the same transport block. The number of retransmissions is given based on instructions from the upper-layer processing unit 14. The wireless transceiver unit 10 is characterized in that it transmits PUSCH in aggregate transmission based on information related to the first repetition count, a first number, and a second number indicated by the upper-layer processing unit 14. The wireless transceiver unit 10 can control aggregate transmission based on predetermined conditions. Specifically, the wireless transceiver unit 10 has the following functions: when a first condition is met and a second aggregate transmission parameter is set, it applies the same symbol allocation in each time slot and repeatedly transmits the transport block N times in N consecutive time slots; when the second aggregate transmission parameter is not set, it transmits the transport block once. Here, the value of N is indicated by the second aggregate transmission parameter. Furthermore, the wireless transceiver unit 10 has the function of transmitting the transport block by applying mini-time slot aggregate transmission when a second condition is met. The first condition at least includes that the PUSCH mapping type is indicated as type A in the DCI received from the base station device 3. The second condition at least includes that the PUSCH mapping type is indicated as type B in the DCI received from the base station device 3.

[0334] The RF unit 12 converts the signal received by the antenna unit 11 into a baseband signal through quadrature demodulation (down-conversion), removing unwanted frequency components. The RF unit 12 then outputs the processed analog signal to the baseband unit.

[0335] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes the part equivalent to the CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal after removing the CP, and extracts the signal in the frequency domain.

[0336] The baseband unit 13 performs an inverse fast fourier transform (IFFT) on the data to generate OFDM symbols, appends a CP to the generated OFDM symbols to generate a digital baseband signal, and converts the digital baseband signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

[0337] The RF unit 12 uses a low-pass filter to remove unwanted frequency components from the analog signal input from the baseband unit 13, upconverts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. Furthermore, the RF unit 12 amplifies the power. Additionally, the RF unit 12 may also have the function of determining the transmission power of the uplink signal and / or uplink channel transmitted within the cell. The RF unit 12 is also referred to as the transmission power control unit.

[0338] Figure 23 This is a schematic block diagram showing the configuration of the base station device 3 in this embodiment. (See diagram below.) Figure 23 As shown, the base station device 3 is configured to include a wireless transceiver unit 30 and an upper-layer processing unit 34. The wireless transceiver unit 30 is configured to include an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper-layer processing unit 34 is configured to include a media access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver unit 30 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. In addition, a control unit is provided to control the operation of each unit based on various conditions. The upper-layer processing unit 34 is also referred to as the control unit 34.

[0339] The upper-layer processing unit 34 performs processing on some or all of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Radio Resource Control (RRC) layer. The upper-layer processing unit 34 has the function of determining whether to perform repeated transmission of a transport block based on signals transmitted to the upper layer of the terminal device 1. The upper-layer processing unit 34 determines whether to perform either first aggregation transmission or second aggregation transmission based on signals transmitted to the upper layer of the terminal device 1. The upper-layer processing unit 34 has the function of controlling symbol allocation extension (start symbol extension and / or symbol number extension), dynamic repetition count, and / or mini-slot aggregation transmission for aggregation transmission (second aggregation transmission) based on signals transmitted to the upper layer of the terminal device 1. The upper-layer processing unit 34 determines whether to perform frequency hopping transmission of a transport block based on signals transmitted to the upper layer of the terminal device 1. The upper-layer processing unit 34 has the function of controlling the setting of the first frequency hopping and the second frequency hopping based on the number of times the same transmission block is repeatedly transmitted within a time slot. The upper-layer processing unit 34 outputs frequency hopping information, aggregation transmission information, etc. to the wireless transceiver unit 30.

[0340] The upper-layer processing unit 34 has the function of controlling a second number based on upper-layer signals including a first number of retransmissions and / or a DCI field including the first number. The first number may include the number of retransmissions of the same transport block within and between time slots. The second number may be the number of retransmissions of the same transport block within a time slot.

[0341] The Media Access Control (MAC) layer processing unit 35, which is included in the upper-layer processing unit 34, performs MAC layer processing. The MAC layer processing unit 35 performs processing related to scheduling requests based on various configuration information / parameters managed by the Radio Resource Control (RRC) layer processing unit 36.

[0342] The Radio Resource Control (RRC) layer processing unit 36, included in the upper-layer processing unit 34, performs RRC layer processing. The RRC layer processing unit 36 ​​generates downlink control information (uplink grant, downlink grant) including resource allocation information at the terminal device 1. The RRC layer processing unit 36 ​​generates or obtains downlink control information, downlink data (transmission blocks, random access responses) configured on the physical downlink shared channel, system information, RRC messages, MAC CE (Control Element), etc., from the upper-level node, and outputs them to the radio transceiver unit 30. Furthermore, the RRC layer processing unit 36 ​​manages various configuration information / parameters for each terminal device 1. The RRC layer processing unit 36 ​​can configure various configuration information / parameters for each terminal device 1 via signals from the upper layer. That is, the RRC layer processing unit 36 ​​transmits / broadcasts information indicating various configuration information / parameters. The RRC layer processing unit 36 ​​can transmit / broadcast information for determining the configuration of one or more reference signals in a cell.

[0343] When base station device 3 sends RRC messages, MAC CE, and / or PDCCH to terminal device 1, and terminal device 1 performs processing based on the received information, base station device 3 assumes that the terminal device is performing such processing and performs the processing (control of terminal device 1 and system). That is, base station device 3 sends RRC messages, MAC CE, and / or PDCCH to terminal device 1 so that terminal device performs processing based on the received information.

[0344] The wireless transceiver unit 30 transmits upper-layer signals (RRC messages), DCI, etc., to the terminal device 1. Furthermore, the wireless transceiver unit 30 receives uplink signals transmitted from the terminal device 1 based on instructions from the upper-layer processing unit 34. The wireless transceiver unit 30 can receive repeated transmissions of transport blocks from the terminal device 1 based on instructions from the upper-layer processing unit 34. When repeat transmission of transport blocks is enabled, the wireless transceiver unit 30 receives repeated transmissions of the same transport block. The number of repetitions is given based on instructions from the upper-layer processing unit 34. The wireless transceiver unit 30 is characterized in that it receives PUSCH in aggregate transmission based on information related to a first repetition count, a first number, and a second number, as instructed by the upper-layer processing unit 34. The wireless transceiver unit 30 can control aggregate transmission based on predetermined conditions. Specifically, the wireless transceiver unit 30 has the following functions: when a first condition is met and a second aggregation transmission parameter is set, it applies the same symbol allocation in each time slot and repeatedly receives transmission blocks N times in N consecutive time slots; when the second aggregation transmission parameter is not set, it receives a transmission block once. Here, the value of N is indicated by the second aggregation transmission parameter. Furthermore, the wireless transceiver unit 30 has the function of receiving transmission blocks by applying mini-time slot aggregation transmission when a second condition is met. The first condition at least includes that the PUSCH mapping type is indicated as type A in the DCI transmitted to the terminal device 1. The second condition at least includes that the PUSCH mapping type is indicated as type B in the DCI transmitted to the terminal device 1. Furthermore, some functions of the wireless transceiver unit 30 are the same as those of the wireless transceiver unit 10, and therefore are omitted from the description. It should be noted that when the base station device 3 is connected to one or more transceiver points 4, some or all of the functions of the wireless transceiver unit 30 may also be included in each transceiver point 4.

[0345] In addition, the upper-layer processing unit 34 performs the transmission (forwarding) or reception of control messages or user data between base station devices 3 or between upper-layer network devices (MME, SGW (Serving-GW)) and base station devices 3. Figure 23 The components of other base station devices 3 and the data (control information) propagation paths between these components are omitted, but it is obvious that each component has multiple blocks that have other functions required for the operation of the base station device 3. For example, the upper-layer processing unit 34 includes a radio resource management layer processing unit and an application layer processing unit.

[0346] It should be noted that the “part” in the figure refers to the elements that realize the functions and processes of the terminal device 1 and the base station device 3, expressed by terms such as components, circuits, constituent devices, equipment, and units.

[0347] The components of terminal device 1 marked with reference numerals 10 to 16 can also be configured as circuits. The components of base station device 3 marked with reference numerals 30 to 36 can also be configured as circuits.

[0348] (1) More specifically, the terminal device 1 of the first embodiment of the present invention includes: a receiving unit 10, which receives an RRC message including a first aggregation transmission parameter; and a transmitting unit 10, which transmits a PUSCH scheduled by the DCI, and when a first condition is met and a second aggregation transmission parameter is set, applies the same symbol allocation in each time slot, and repeatedly transmits a transport block N times in N consecutive time slots, the value of N being indicated by the second aggregation transmission parameter; when the second aggregation transmission parameter is not set, transmits a transport block once; and when a second condition is met, transmits a transport block by applying mini time slot aggregation transmission.

[0349] (2) The base station apparatus 3 of the second aspect of the present invention includes: a transmitting unit 30, which transmits an RRC message including a first aggregation transmission parameter and transmits a DCI; and a receiving unit 30, which receives a PUSCH scheduled by the DCI, and when a first condition is met and a second aggregation transmission parameter is set, applies the same symbol allocation in each time slot, repeatedly receives N transmission blocks in N consecutive time slots, the value of N being indicated by the second aggregation transmission parameter, receives a transmission block once when the second aggregation transmission parameter is not set, and applies mini-time slot aggregation to transmit and receive transmission blocks when a second condition is met.

[0350] (3) In the first or second aspect of the present invention, in the mini time slot aggregation transmission, the same transmission block is repeatedly transmitted once or more times in one time slot.

[0351] (4) In the first or second embodiment of the present invention, the first condition includes at least that the PUSCH mapping type in the DCI is indicated as type A.

[0352] (5) In the first or second embodiment of the present invention, the second condition includes at least that the PUSCH mapping type in the DCI is indicated as type B.

[0353] (6) The terminal device 1 of the third aspect of the present invention includes: a receiving unit 10 for receiving uplink grants; and a transmitting unit 10 for transmitting a frequency-hopping PUSCH that schedules the uplink grants, wherein the PUSCH includes N in one time slot. rep The same transmission block is repeatedly transmitted, and the PUSCH is composed of a first frequency hopping and a second frequency hopping within a time slot, in the N... repWhen N is 1, the first frequency hopping has Floor(L / 2) symbols, and the second frequency hopping has L-Floor(L / 2) symbols, where L is the number of symbols corresponding to one repeated transmission, and in the N rep In the case of more than 1, the first frequency hopping has the same characteristics as the initial Floor(N). rep / 2) times the symbols corresponding to the repeated transmission, the second frequency hopping has N rep -Floor(N rep / 2) The corresponding symbols are sent repeatedly.

[0354] (7) The base station apparatus 3 of the fourth aspect of the present invention comprises: a transmitting unit 30 for transmitting uplink grants; and a receiving unit 30 for receiving a frequency-hopping PUSCH accompanied by scheduling the uplink grants, wherein the PUSCH includes N in one time slot. rep The same transmission block is repeatedly transmitted, and the PUSCH is composed of a first frequency hopping and a second frequency hopping within a time slot, in the N... rep When N is 1, the first frequency hopping has Floor(L / 2) symbols, and the second frequency hopping has L-Floor(L / 2) symbols, where L is the number of symbols corresponding to one repeated transmission, and in the N rep In the case of more than 1, the first frequency hopping has the same characteristics as the initial Floor(N). rep / 2) times the symbols corresponding to the repeated transmission, the second frequency hopping has N rep -Floor(N rep / 2) The corresponding symbols are sent repeatedly.

[0355] (8) In the third or fourth embodiment of the present invention, the number of symbols corresponding to the repeated transmission of the same transmission block in a time slot may be the same or different.

[0356] (9) In the third or fourth embodiment of the present invention, the N rep The repeated transmission described herein refers to continuous transmission within a time slot, or non-continuous transmission.

[0357] (10) The terminal device 1 of the fifth aspect of the present invention is characterized by comprising: a receiving unit 10, which receives an RRC message including a first aggregation transmission parameter and receives a DCI; and a sending unit 10, which sends a PUSCH scheduled by the DCI, wherein the first aggregation transmission parameter includes information related to a first repetition number, the DCI field includes a first number, a second number is calculated based on the first number, and the sending unit sends the PUSCH by aggregation transmission based on the information related to the first repetition number, the first number, and the second number.

[0358] (11) The base station apparatus 3 of the sixth aspect of the present invention is characterized by comprising: a transmitting unit 30 for transmitting an RRC message including a first aggregation transmission parameter and transmitting a DCI; and a receiving unit 30 for receiving a PUSCH scheduled by the DCI, wherein the first aggregation transmission parameter includes information related to a first repetition number, the DCI field includes a first number, a second number is calculated based on the first number, and the receiving unit receives the PUSCH by aggregation transmission based on the information related to the first repetition number, the first number, and the second number.

[0359] (12) In the fifth or sixth aspect of the present invention, the first number is the number of times the same transmission block is repeatedly transmitted within and between time slots, and the second number is the number of times the same transmission block is repeatedly transmitted within a time slot.

[0360] (13) In the fifth or sixth aspect of the present invention, the first number is the number of times the same transmission block is repeatedly transmitted within a time slot, and the second number is the number of times the same transmission block is repeatedly transmitted both within and between time slots.

[0361] (14) In the fifth or sixth aspect of the present invention, the number of times the same transmission block is repeatedly transmitted within a time slot, the second number being the number of time slots used in repeatedly transmitting the same transmission block.

[0362] Therefore, terminal device 1 can communicate efficiently with base station device 3.

[0363] The program operating in the apparatus of this invention can be a program that controls a central processing unit (CPU) or other computer to perform its functions in order to achieve the functions of the embodiments of this invention. The program or the information processed by the program is temporarily stored in volatile memory such as random access memory (RAM) or non-volatile memory such as flash memory, hard disk drive (HDD), or other storage device systems.

[0364] It should be noted that the program used to implement the functions of the embodiments of the present invention can also be recorded on a computer-readable recording medium. This can be achieved by reading the program recorded on the recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into the device, including hardware such as an operating system and peripherals. Furthermore, "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium for short-term dynamic storage of programs, or other computer-readable recording media.

[0365] Furthermore, the functional blocks or features of the apparatus used in the above embodiments can be installed or executed by electronic circuits such as integrated circuits or multiple integrated circuits. Circuits designed to perform the functions described in this specification may include: general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic elements, discrete gate or transistor logic, discrete hardware components, or combinations thereof. General-purpose processors may be microprocessors, or existing types of processors, controllers, microcontrollers, or state machines. The aforementioned electronic circuits may be constructed from digital circuits or analog circuits. Furthermore, with the emergence of integrated circuit technologies that replace existing integrated circuits due to advancements in semiconductor technology, one or more embodiments of the present invention may also use new integrated circuits based on this technology.

[0366] It should be noted that, in the embodiments of the present invention, examples applicable to communication systems consisting of base station devices and terminal devices are described, but they can also be applied to systems where terminals communicate with each other, such as D2D (Device to Device).

[0367] It should be noted that the invention described in this application is not limited to the embodiments described above. While one example of the device is described in the embodiments, the invention is not limited thereto and can be applied to fixed or non-movable electronic devices installed indoors or outdoors, such as AV equipment, kitchen equipment, cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other terminal devices or communication devices in daily life.

[0368] The embodiments of the present invention have been described in detail above with reference to the accompanying drawings. However, the specific configuration is not limited to these embodiments, and design changes that do not depart from the spirit of the present invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the technical solutions shown, and embodiments obtained by appropriately combining technical solutions disclosed in different embodiments are also included within the technical scope of the present invention. In addition, it also includes configurations obtained by replacing elements that have the same effect as those described in the above embodiments with each other.

Claims

1. A user equipment (UE), the UE comprising: The receiving unit receives from the base station device radio resource control (RRC) parameters instructing the UE to apply a repetition type between a first repetition type and a second repetition type, and a physical downlink control channel in DCI format, wherein... The first repetition type indicates one repetition in a time slot, and the second repetition type allows more than one repetition of a transport block to be sent in a time slot; The transmitting unit performs physical uplink shared channel (PUSCH) retransmission of transport blocks scheduled via the DCI format by applying the indicated retransmission type; and The control unit determines, at least based on the DCI format, a first number representing the number of repetitions, a second number representing the start symbol, and a third number representing consecutive symbols. The control unit performs the following operations: In the case of indicating the first repetition type, determine the consecutive time slots for performing the first number of PUSCH repetitions, and When the second repetition type is indicated, one or more time slots for performing the PUSCH repetition are determined based at least on the first number, the second number, the third number, and the number of symbols in the time slot.

2. The UE according to claim 1, wherein, In the case of indicating the second repeat type The first repeated transmission of the transport block begins with a symbol represented by the second number. The starting symbol of the Xth repetition of the transport block is the first symbol consecutive to the (X-1)th repetition.

3. A base station apparatus, the base station apparatus comprising: The control unit generates downlink control information (DCI) format, which includes DCI fields for indicating to the user equipment (UE) a first number representing the number of repetitions, a second number representing the start symbol, and a third number representing consecutive symbols. The transmitting unit sends to the UE radio resource control (RRC) parameters instructing the UE to apply a repetition type between a first repetition type and a second repetition type, as well as a physical downlink control channel having the DCI format, wherein... The first repetition type indicates one repetition in a time slot, and the second repetition type allows more than one repetition of a transport block to be sent in a time slot; and The receiving unit receives, from the UE, repeated transmissions of the Physical Uplink Shared Channel (PUSCH) of the transport blocks scheduled via the DCI format, according to the repetition type indicated by the application. The control unit performs the following operations: In the case of indicating the first repetition type, determine the consecutive time slots for performing the first number of PUSCH repetitions, and When the second repetition type is indicated, one or more time slots for the UE to perform the PUSCH repetition are determined based at least on the first number, the second number, the third number, and the number of symbols in the time slot.

4. The base station apparatus according to claim 3, wherein, In the case of indicating the second repeat type The first repeated transmission of the transport block begins with a symbol represented by the second number. The starting symbol of the Xth repetition of the transport block is the first symbol consecutive to the (X-1)th repetition.

5. A communication method for a user equipment (UE), the communication method comprising the following steps: The UE receives Radio Resource Control (RRC) parameters instructing it to apply a repeating type between a first repeating type and a second repeating type, as well as a Physical Downlink Control Channel in DCI format, from the base station device, wherein the first repeating type indicates one repeating in a time slot, and the second repeating type allows more than one repeating of a transport block to be transmitted in a time slot; Physical uplink shared channel (PUSCH) retransmission of transport blocks scheduled via the DCI format is performed by applying the indicated retransmission type. The first number representing the number of repetitions, the second number representing the start symbol, and the third number representing consecutive symbols are determined based at least on the DCI format. Wherein, in the case of indicating the first repetition type, the consecutive time slots for performing the first number of PUSCH repetitions are also determined, and In the case of indicating the second repetition type, one or more time slots for performing the PUSCH repetition are also determined based at least on the first number, the second number, the third number, and the number of symbols in the time slot.

6. A communication method for a base station device, the communication method comprising the following steps: A downlink control information (DCI) format is generated, the DCI format including a DCI field for indicating to the user equipment (UE) a first number representing the number of repetitions, a second number representing the start symbol, and a third number representing consecutive symbols; Send to the UE Radio Resource Control (RRC) parameters instructing the UE to apply a repetition type between a first repetition type and a second repetition type, and a Physical Downlink Control Channel having the DCI format, wherein the first repetition type indicates one repetition in a time slot, and the second repetition type allows more than one repetition of a transport block to be transmitted in a time slot; and Physical uplink shared channel (PUSCH) retransmissions are received from the UE via the retransmission type indicated by the application, using the transport blocks scheduled through the DCI format. Wherein, in the case of indicating the first repetition type, the consecutive time slots for performing the first number of PUSCH repetitions are also determined, and In the case of indicating the second repetition type, one or more time slots for the UE to perform the PUSCH repetition are also determined based at least on the first number, the second number, the third number, and the number of symbols in the time slot.

Images