Terminal device, base station device, and communication method

Abstract

Provided is a terminal device which: receives an RRC message including first information indicating whether each of symbols in a certain period is a downlink, an uplink, or flexible; receives second information including a first bit field; receives third information identifying a time resource for transmission of a PUSCH for a TB; identifies the time resource on the basis of the first information and the third information; if the first bit field is a first value and upon reception on a PDCCH of fourth information indicating slot formats of a plurality of slots, does not use for transmission of the PUSCH a resource, among the time resources, that has a symbol indicating a downlink or flexible in the slot formats; and if the first bit field is a second value, uses all of the time resources for transmission of the PUSCH.

Description

[Technical field]

[0001] The present invention relates to a terminal device, a base station device, and a communication method. This application claims priority to Japanese Patent Application No. 2019-183240, filed on October 3, 2019, the contents of which are incorporated herein by reference. [Background technology]

[0002] Currently, the Third Generation Partnership Project (3GPP) is conducting technical studies and formulating standards for LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) as radio access methods and radio network technologies for the fifth generation cellular system (Non-Patent Document 1).

[0003] For the fifth generation cellular system, three expected service scenarios are required: eMBB (enhanced Mobile BroadBand) which realizes high-speed, large-capacity transmission; URLLC (Ultra-Reliable and Low Latency Communication) which realizes low-latency, highly reliable communications; and mMTC (massive Machine Type Communication) which connects a large number of machine-type devices such as IoT (Internet of Things). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016 Summary of the Invention [Problem to be solved by the invention]

[0005] An object of the present invention is to provide a terminal device, a base station device, and a communication method that enable efficient communication in the wireless communication system described above. [Means for solving the problem]

[0006] (1) In order to achieve the above object, an embodiment of the present invention takes the following measures. That is, a terminal device in one embodiment of the present invention includes a receiver that receives an RRC message including first information indicating whether each of symbols in a certain period is downlink, uplink, or flexible, receives second information including a first bit field, and receives third information for identifying a first time resource for transmitting a physical uplink shared channel for a certain transport block, and a determiner that identifies the first time resource based on the first information and the third information, and when the first bit field is a first value and the receiver receives fourth information indicating a slot format of a plurality of slots on a physical downlink control channel, the determiner does not use resources allocated to symbols indicated as downlink and symbols indicated as flexible in the slot format among the first time resources for transmitting the physical uplink shared channel, and when the first bit field is a second value, uses all of the first time resources for transmitting the physical uplink shared channel.

[0007] (2) In addition, a base station device in one embodiment of the present invention is a base station device that communicates with a terminal device, and includes a transmitter that transmits an RRC message including first information indicating whether each of symbols in a certain period is downlink, uplink, or flexible, transmits second information including a first bit field, and transmits third information for identifying a first time resource from which the terminal device transmits a physical uplink shared channel for a transport block, and a receiver that receives the physical uplink shared channel based on the first information, the second information, and the third information, wherein when the first bit field is a first value and the transmitter transmits fourth information indicating a slot format of a plurality of slots to the terminal device on a physical downlink control channel, the receiver does not use resources allocated to symbols indicated as downlink and symbols indicated as flexible in the slot format among the first time resources for receiving the physical uplink shared channel, and when the first bit field is a second value, uses all of the first time resources for receiving the physical uplink shared channel.

[0008] (3) Furthermore, a communication method according to one embodiment of the present invention is a communication method of a terminal device, which receives an RRC message including first information indicating whether each of symbols in a certain period is downlink, uplink, or flexible, receives second information including a first bit field, receives third information for identifying a first time resource for transmitting a physical uplink shared channel for a transport block, identifies the first time resource based on the first information and the third information, and when the first bit field is a first value and fourth information indicating a slot format of a plurality of slots is received on a physical downlink control channel, resources allocated to symbols indicated as downlink and symbols indicated as flexible in the slot format among the first time resources are not used for transmitting the physical uplink shared channel, and when the first bit field is a second value, all of the first time resources are used for transmitting the physical uplink shared channel.

[0009] (4) Furthermore, a communication method according to one embodiment of the present invention is a communication method of a base station device, which includes the steps of: transmitting an RRC message including first information indicating whether each of symbols in a certain period is downlink, uplink, or flexible; transmitting second information including a first bit field; transmitting third information for identifying a first time resource from which the terminal device transmits a physical uplink shared channel for a transport block; receiving the physical uplink shared channel based on the first information, the second information, and the third information; when the first bit field is a first value and fourth information indicating a slot format of a plurality of slots is transmitted to the terminal device on a physical downlink control channel, resources allocated to symbols indicated as downlink and symbols indicated as flexible in the slot format among the first time resources are not used for receiving the physical uplink shared channel; and when the first bit field is a second value, all of the first time resources are used for receiving the physical uplink shared channel. Effect of the Invention

[0010] According to one aspect of the present invention, a terminal device and a base station device can communicate efficiently. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention. [Diagram 2] A figure showing an example of an SS / PBCH block and SS burst set for an embodiment of the present invention. [Diagram 3] A figure showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. [Figure 4] FIG. 2 is a diagram showing the relationship between subframes, slots, and minislots in the time domain according to an embodiment of the present invention. [Diagram 5] A diagram showing an example of a slot or subframe according to an embodiment of the present invention. [Figure 6] FIG. 2 is a diagram showing an example of a table of slot formats according to an embodiment of the present invention. [Figure 7] FIG. 2 is a diagram illustrating an example of beamforming according to an embodiment of the present invention. [Figure 8] 1 is an example of a table showing a method of determining a resource allocation table to be applied to a PUSCH according to an embodiment of the present invention. [Figure 9] 11 is another example of a table showing a method of determining a resource allocation table to be applied to a PUSCH according to an embodiment of the present invention. [Figure 10] FIG. 4 is a diagram showing an example of a PUSCH default table A according to the present embodiment. [Figure 11] FIG. 11 is a diagram showing an example of a PUSCH default table B according to the present embodiment. [Figure 12] 1 is a diagram illustrating an example of a parameter configuration of an RRC parameter PUSCH-Time Domain Resource Allocation according to an embodiment of the present invention. [Figure 13] FIG. 1 is a diagram showing an example of calculating a SLIV according to an embodiment of the present invention. [Figure 14] 1 is a diagram illustrating an example of a parameter configuration of an RRC parameter PUSCH-Time Domain Resource Allocation 2 according to an embodiment of the present invention. [Figure 15] 1 is a diagram illustrating an example of a parameter configuration of an RRC parameter PUSCH-Time Domain Resource Allocation 3 according to an embodiment of the present invention. [Figure 16] FIG. 2 is a diagram illustrating an example of uplink symbols available for transmitting a PUSCH according to an embodiment of the present invention. [Figure 17] FIG. 11 is a diagram illustrating an example of dropping a PUSCH in repeated transmission of a PUSCH according to an embodiment of the present invention. [Figure 18] 1 is a diagram illustrating an example of time resource allocation of a PUSCH in repeated transmission of the PUSCH according to an embodiment of the present invention. [Figure 19] A figure showing an example of segmentation of a PUSCH according to an embodiment of the present invention. [Figure 20] FIG. 11 is a diagram illustrating another example of segmentation of a PUSCH according to an embodiment of the present invention. [Figure 21] FIG. 2 is a schematic diagram of a first frequency hopping according to an embodiment of the present invention; [Figure 22] FIG. 2 is a schematic diagram of a second frequency hopping according to an embodiment of the present invention. [Diagram 23] 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an embodiment of the present invention. [Figure 24] 1 is a schematic block diagram showing a configuration of a base station device 3 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described.

[0013] Fig. 1 is a conceptual diagram of a wireless communication system in this embodiment. In Fig. 1, the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3. Hereinafter, the terminal device 1A and the terminal device 1B are also referred to as terminal devices 1.

[0014] The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). The base station device 3 is also referred to as a radio base station device, a base station, a radio base station, a fixed station, a Node B (NB), an evolved Node B (eNB), a BTS (Base Transceiver Station), a BS (Base Station), a NR Node B (NR NB), an NNB, a TRP (Transmission and Reception Point), or a gNB. The base station device 3 may include a core network device. The base station device 3 may also include one or more transmission reception points 4. At least some of the functions / processing of the base station device 3 described below may be functions / processing of each transmission reception point 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 with a communication coverage area (communication area) controlled by the base station device 3 as one or more cells. Furthermore, the base station device 3 may serve the terminal device 1 as one or more cells, which are communication ranges (communication areas) controlled by one or more transmission / reception points 4. Furthermore, the base station device 3 may divide one cell into multiple partial areas (beamed areas) and serve the terminal device 1 in each partial area. Here, the partial area may be identified based on the index of the beam used in beamforming or the index of precoding.

[0015] In this embodiment, a wireless communication link from the base station device 3 to the terminal device 1 is referred to as a downlink. In this embodiment, a wireless communication link from the terminal device 1 to the base station device 3 is referred to as an uplink.

[0016] In FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), discrete Fourier transform spread OFDM (DFT-S-OFDM), or multi-carrier code division multiplexing (MC-CDM) may be used.

[0017] In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 may use Universal Filtered Multi-Carrier (UFMC), Filtered OFDM (F-OFDM), Windowed OFDM (Windowed OFDM), or Filter-Bank Multi-Carrier (FBMC).

[0018] In this embodiment, OFDM is used as a transmission method and OFDM symbols are used, but the above-mentioned cases where other transmission methods are used are also included in one aspect of the present invention.

[0019] 1, the above-mentioned transmission method may be used in which a CP is not used or zero padding is used instead of a CP in wireless communication between the terminal device 1 and the base station device 3. Also, a CP or zero padding may be added to both the front and rear.

[0020] An aspect of the present embodiment may be operated in carrier aggregation or dual connectivity with a radio access technology (RAT) such as LTE or LTE-A / LTE-A Pro. In this case, it may be used in some or all of the cells or cell groups, carriers or carrier groups (e.g., a primary cell (PCell), a secondary cell (SCell), a primary secondary cell (PSCell), a master cell group (MCG), a secondary cell group (SCG), etc.). Also, an aspect of the present embodiment may be used in a standalone manner. In dual connectivity operation, the SpCell (Special Cell) is referred to as a PCell of an MCG or a PSCell of an SCG depending on whether the MAC (Medium Access Control) entity is associated with an MCG or an SCG, respectively. If not in dual connectivity operation, the SpCell (Special Cell) is referred to as a PCell. The SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

[0021] In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured multiple serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell where an initial connection establishment procedure has been performed, a serving cell where a connection re-establishment procedure has been started, or a cell designated as a primary cell in a handover procedure. One or more secondary cells may be configured at the time when an RRC (Radio Resource Control) connection is established or after that. However, the configured multiple serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information in an uplink, among one or more secondary cells where the terminal device 1 is configured. In addition, two types of subsets of serving cells, a master cell group and a secondary cell group, may be configured for the terminal device 1. The master cell group may be configured with one primary cell and zero or more secondary cells. The secondary cell group may be configured with one primary secondary cell and zero or more secondary cells.

[0022] In the wireless communication system of the present embodiment, TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) may be applied. The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of a plurality of cells. Furthermore, cells to which the TDD method is applied and cells to which the FDD method is applied may be aggregated. The TDD method may be called an unpaired spectrum operation. The FDD method may be called a paired spectrum operation.

[0023] In the downlink of this embodiment, a carrier corresponding to a serving cell is referred to as a downlink component carrier (or downlink carrier). In the uplink of this embodiment, a carrier corresponding to a serving cell is referred to as an uplink component carrier (or uplink carrier). In the sidelink of this embodiment, a carrier corresponding to a serving cell is referred to as a sidelink component carrier (or sidelink carrier). Downlink component carrier, uplink component carrier, and / or sidelink component carrier are collectively referred to as a component carrier (or carrier).

[0024] The physical channels and physical signals of this embodiment will be described.

[0025] In FIG. 1, the following physical channels are used in wireless communication between the terminal device 1 and the base station device 3.

[0026] PBCH (Physical Broadcast CHannel) PDCCH (Physical Downlink Control CHannel) PDSCH (Physical Downlink Shared CHannel) PUCCH (Physical Uplink Control CHannel) PUSCH (Physical Uplink Shared CHannel) PRACH (Physical Random Access CHannel)

[0027] The PBCH is used to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1.

[0028] Also, the PBCH may be used to broadcast a time index within a period of a block of a synchronization signal (also referred to as an SS / PBCH block). Here, the time index is information indicating an index of a synchronization signal and a PBCH within a cell. For example, when an SS / PBCH block is transmitted using the assumption of three transmission beams (transmission filter setting, quasi co-location (QCL: Quasi Co-Location) for reception spatial parameters), a time order within a predetermined period or a set period may be indicated. Also, the terminal device may recognize a difference in the time index as a difference in the transmission beam.

[0029] The PDCCH is used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (which may be referred to as DCI formats) are defined for the transmission of the downlink control information. That is, a field for the downlink control information is defined as a DCI and mapped to information bits. The PDCCH is transmitted in PDCCH candidates. The terminal device 1 monitors a set of PDCCH candidates in the serving cell. However, monitoring may mean attempting to decode the PDCCH according to a certain DCI format.

[0030] For example, the following DCI formats may be defined: DCI Format 0_0 DCI Format 0_1 DCI Format 0_2 DCI Format 1_0 DCI Format 1_1 DCI Format 1_2 DCI Format 2_0 DCI Format 2_1 DCI Format 2_2 DCI Format 2_3

[0031] DCI format 0_0 may be used for scheduling a PUSCH in a serving cell. DCI format 0_0 may include information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of a PUSCH. DCI format 0_0 may be added with a CRC (Cyclic Redundancy Check) scrambled by any one of Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI, MCS-C-RNTI, and / or Temporary C-NRTI (TC-RNTI) among Radio Network Temporary Identifiers (RNTIs) that are identifiers. DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

[0032] DCI format 0_1 ​​may be used for scheduling PUSCH in a serving cell. DCI format 0_1 ​​may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band width part (BWP), a channel state information (CSI) request, a sounding reference signal (SRS) request, and / or information regarding an antenna port. DCI format 0_1 ​​may be added with a CRC scrambled by any of C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 0_1 ​​may be monitored in a UE-specific search space.

[0033] DCI format 0_2 may be used for scheduling a PUSCH in a serving cell. DCI format 0_2 may include information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of a PUSCH, information indicating a BWP, a CSI request, an SRS request, and / or information regarding an antenna port. DCI format 0_2 may be added with a CRC scrambled by any of C-RNTI, CSI-RNTI, SP-CSI-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 0_2 may be monitored in a UE-specific search space. DCI format 0_2 may be referred to as DCI format 0_1A, etc.

[0034] DCI format 1_0 may be used for scheduling a PDSCH in a serving cell. DCI format 1_0 may include information indicating scheduling information (frequency domain resource allocation and time domain resource allocation) of a PDSCH. DCI format 1_0 may be added with a CRC scrambled by any of the following identifiers: C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random Access (RA)-RNTI, and / or TC-RNTI. DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

[0035] DCI format 1_1 may be used for scheduling a PDSCH in a serving cell. DCI format 1_1 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP), a transmission configuration indication (TCI), and / or information regarding an antenna port. DCI format 1_1 may be added with a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_1 may be monitored in a UE-specific search space.

[0036] DCI format 1_2 may be used for scheduling a PDSCH in a serving cell. DCI format 1_2 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a BWP, a TCI, and / or information regarding an antenna port. DCI format 1_2 may be added with a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_2 may be monitored in a UE-specific search space. DCI format 1_2 may be referred to as DCI format 1_1A, etc.

[0037] DCI format 2_0 is used to notify the slot format of one or more slots. The slot format is defined as a classification of each OFDM symbol in a slot as either downlink, flexible, or uplink. For example, when the slot format is 28, DDDDDDDDDDDDFU is applied to 14 OFDM symbols in a slot in which slot format 28 is specified. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Slots will be described later.

[0038] DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks (PRBs or RBs) and OFDM symbols for which no transmission may be assumed. Note that this information may be called a preemption instruction (discontinuous transmission instruction).

[0039] DCI format 2_2 is used for transmitting the PUSCH and a transmit power control (TPC) command for the PUSCH.

[0040] DCI format 2_3 is used to transmit a group of TPC commands for sounding reference signal (SRS) transmission by one or more terminal devices 1. An SRS request may be transmitted together with the TPC command. An SRS request and a TPC command may be defined in DCI format 2_3 for an uplink without PUSCH and PUCCH, or for an uplink in which the transmission power control of SRS is not linked to the transmission power control of PUSCH.

[0041] The DCI for the downlink is also referred to as a downlink grant or a downlink assignment. Here, the DCI for the uplink is also referred to as an uplink grant or an uplink assignment. The DCI may also be referred to as a DCI format.

[0042] The CRC parity bits added to the DCI format transmitted in one PDCCH are scrambled with the SI-RNTI, P-RNTI, C-RNTI, CS-RNTI, RA-RNTI, or TC-RNTI. The SI-RNTI may be an identifier used for broadcasting system information. The P-RNTI may be an identifier used for paging and notifying of system information changes. The C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device in a cell. The TC-RNTI is an identifier for identifying the terminal device 1 that transmitted a random access preamble during a contention based random access procedure.

[0043] The C-RNTI is used to control the PDSCH or PUSCH in one or more slots. The CS-RNTI is used to periodically allocate resources for the PDSCH or PUSCH. The MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission. The TC-RNTI is used to control the PDSCH or PUSCH transmission in one or more slots. The TC-RNTI is used to schedule retransmissions of the random access message 3 and the transmission of the random access message 4. The RA-RNTI is determined according to the frequency and time location information of the physical random access channel that transmitted the random access preamble.

[0044] Different values ​​may be used for the C-RNTI and / or other RNTIs depending on the type of traffic of the PDSCH or PUSCH. Different values ​​may be used for the C-RNTI and other RNTIs depending on the service type (eMBB, URLLC, and / or mMTC) of data transmitted on the PDSCH or PUSCH. The base station device 3 may use different values ​​of RNTI depending on the service type of data to be transmitted. The terminal device 1 may identify the service type of data transmitted on the associated PDSCH or PUSCH depending on the value of the RNTI applied to the received DCI (used for scrambling).

[0045] The PUCCH is used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. The uplink control information may also include a scheduling request (SR) used to request a UL-SCH resource. The uplink control information may also include a hybrid automatic repeat request ACKnowledgement (HARQ-ACK). The HARQ-ACK may indicate a HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).

[0046] The PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the Medium Access Control (MAC) layer, and is also used to transmit system information (SI: System Information) and random access response (RAR: Random Access Response) in the downlink.

[0047] The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and / or CSI together with uplink data. The PUSCH may also be used to transmit only CSI or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI.

[0048] Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in a higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive an RRC message (also referred to as an RRC message, RRC information, or RRC signaling) in a Radio Resource Control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive a MAC control element in a Medium Access Control (MAC) layer. The RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3. Here, the RRC message, the system information, and / or the MAC control element are also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). Each of the parameters included in the higher layer signal received by the terminal device 1 may be referred to as a higher layer parameter. The upper layer here means an upper layer seen from the physical layer, and may include one or more of the MAC layer, the RRC layer, the RLC layer, the PDCP layer, the NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, the RLC layer, the PDCP layer, the NAS layer, etc. Hereinafter, the meaning of "A is given (provided) by the upper layer" or "A is given (provided) by the upper layer" may mean that the upper layer (mainly the RRC layer or the MAC layer, etc.) of the terminal device 1 receives A from the base station device 3, and the received A is given (provided) to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. For example, in the terminal device 1, "upper layer parameters are provided" may mean that the upper layer signal is received from the base station device 3, and the upper layer parameters included in the received upper layer signal are provided to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. Setting the upper layer parameters to the terminal device 1 may mean that the upper layer parameters are given (provided) to the terminal device 1.For example, setting an upper layer parameter in the terminal device 1 may mean that the terminal device 1 receives an upper layer signal from the base station device 3 and sets the received upper layer parameter in an upper layer. However, setting an upper layer parameter in the terminal device 1 may also include setting a default parameter that is given in advance to the upper layer of the terminal device 1.

[0049] The PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. The RRC signaling transmitted from the base station device 3 by the PDSCH may be common signaling for a plurality of terminal devices 1 in a cell. Furthermore, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, terminal device-specific (UE-specific) information may be transmitted using dedicated signaling for a certain terminal device 1. Furthermore, the PUSCH may be used to transmit UE capabilities in the uplink.

[0050] In Fig. 1, the following downlink physical signals are used in downlink wireless communication: Here, the downlink physical signals are not used to transmit information output from higher layers, but are used by the physical layer. ·Synchronization signal (SS) ·Reference Signal (RS)

[0051] The synchronization signal may include a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The PSS and SSS may be used to detect the cell ID.

[0052] The synchronization signal is used by the terminal device 1 to synchronize the frequency domain and the time domain of the downlink. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that the beam may be called a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

[0053] The reference signal is used by the terminal device 1 to perform propagation path compensation of the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate the downlink CSI. In addition, the reference signal may be used for fine synchronization to the extent that numerology such as radio parameters and subcarrier intervals and FFT window synchronization can be performed.

[0054] In this embodiment, one or more of the following downlink reference signals are used. ·DMRS(Demodulation Reference Signal) ·CSI-RS(Channel State Information Reference Signal) ·PTRS(Phase Tracking Reference Signal) ·TRS(Tracking Reference Signal)

[0055] The DMRS is used to demodulate a modulated signal. Two types of DMRS may be defined: a reference signal for demodulating the PBCH and a reference signal for demodulating the PDSCH, and both may be called DMRS. The CSI-RS is used for measuring channel state information (CSI) and beam management, and applies a periodic, semi-persistent, or aperiodic CSI reference signal transmission method. For CSI-RS, non-zero power (NZP) CSI-RS and zero power (ZP) CSI-RS with zero transmission power (or zero reception power) may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or no transmission. PTRS is used to track the phase on the time axis for the purpose of compensating for frequency offset caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. Note that TRS may be used as one setting of CSI-RS. For example, radio resources may be configured as a TRS for one-port CSI-RS.

[0056] In this embodiment, any one or more of the following uplink reference signals are used. ·DMRS(Demodulation Reference Signal) ·PTRS(Phase Tracking Reference Signal) ·SRS(Sounding Reference Signal)

[0057] The DMRS is used to demodulate a modulated signal. Two types of DMRS may be defined: a reference signal for demodulating the PUCCH and a reference signal for demodulating the PUSCH, and both may be called DMRS. The SRS is used for measuring uplink channel state information (CSI), channel sounding, and beam management. The PTRS is used to track the phase on the time axis in order to compensate for the frequency offset caused by phase noise.

[0058] In this embodiment, the downlink physical channel and / or the downlink physical signal are collectively referred to as a downlink signal. In this embodiment, the uplink physical channel and / or the uplink physical signal are collectively referred to as an uplink signal. In this embodiment, the downlink physical channel and / or the uplink physical channel are collectively referred to as a physical channel. In this embodiment, the downlink physical signal and / or the uplink physical signal are collectively referred to as a physical signal.

[0059] BCH, UL-SCH and DL-SCH are transport channels. A channel used in the Medium Access Control (MAC) layer is called a transport channel. A unit of a transport channel used in the MAC layer is also called a transport block (TB) and / or a MAC Protocol Data Unit (PDU). In the MAC layer, HARQ (Hybrid Automatic Repeat reQuest) control is performed for each transport block. A transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, a transport block is mapped to a codeword, and encoding processing is performed for each codeword.

[0060] Fig. 2 is a diagram showing an example of an SS / PBCH block (also referred to as a synchronization signal block, SS block, or SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to this embodiment. Fig. 2 shows an example in which two SS / PBCH blocks are included in a periodically transmitted SS burst set, and the SS / PBCH block is composed of four consecutive OFDM symbols.

[0061] An SS / PBCH block is a unit block including at least a synchronization signal (PSS, SSS) and / or a PBCH. Transmitting a signal / channel included in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When transmitting a synchronization signal and / or a PBCH using one or more SS / PBCH blocks in an SS burst set, the base station device 3 may use an independent downlink transmission beam for each SS / PBCH block.

[0062] In Fig. 2, the PSS, SSS and PBCH are time / frequency multiplexed in one SS / PBCH block, but the order in which the PSS, SSS and / or PBCH are multiplexed in the time domain may be different from the example shown in Fig. 2.

[0063] The SS burst set may be periodically transmitted by the base station device 3. For example, a period for which the SS / PBCH block is used for initial access and a period to be set for a connected (Connected or RRC_Connected) terminal device 1 may be defined. Furthermore, the period to be set for a connected (Connected or RRC_Connected) terminal device 1 may be set in the RRC layer. Furthermore, the period to be set for a connected (Connected or RRC_Connected) terminal device 1 is a period of radio resources in the time domain that may potentially be transmitted, and the base station device 3 may actually decide whether or not to transmit. Furthermore, the period for which the SS / PBCH block is used for initial access may be defined in advance in a specification or the like.

[0064] The SS burst set may be determined based on a system frame number (SFN), and the starting position (boundary) of the SS burst set may be determined based on the SFN and a period.

[0065] An SSB index (which may be referred to as an SSB / PBCH block index) is assigned to the SS / PBCH block according to its time position within the SS burst set. The terminal device 1 calculates the SSB index based on PBCH information and / or reference signal information included in the detected SS / PBCH block.

[0066] SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets are assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to average delay, Doppler shift, and spatial correlation.

[0067] Within a period of a certain SS burst set, SS / PBCH blocks that are assigned the same SSB index may be assumed to be QCLs with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. A configuration corresponding to one or more SS / PBCH blocks (or possibly reference signals) that are QCLs may be referred to as a QCL configuration.

[0068] The number of SS / PBCH blocks (which may also be referred to as the number of SS blocks or SSBs) may be defined as, for example, the number of SS / PBCH blocks in an SS burst, or an SS burst set, or a period of SS / PBCH blocks. The number of SS / PBCH blocks may also indicate the number of beam groups for cell selection in an SS burst, or an SS burst set, or a period of SS / PBCH blocks. Here, a beam group may be defined as the number of different SS / PBCH blocks or different beams included in an SS burst, or an SS burst set, or a period of SS / PBCH blocks.

[0069] Hereinafter, the reference signal described in this embodiment includes a downlink reference signal, a synchronization signal, an SS / PBCH block, a downlink DM-RS, a CSI-RS, an uplink reference signal, an SRS, and / or an uplink DM-RS. For example, in this embodiment, the downlink reference signal, the synchronization signal, and / or the SS / PBCH block may be referred to as a reference signal. The reference signal used in the downlink includes a downlink reference signal, a synchronization signal, an SS / PBCH block, a downlink DM-RS, a CSI-RS, etc. The reference signal used in the uplink includes an uplink reference signal, an SRS, and / or an uplink DM-RS, etc.

[0070] The reference signal may be used for radio resource measurement (RRM) and for beam management.

[0071] Beam management may be a procedure performed by base station device 3 and / or terminal device 1 to align the directivity of an analog and / or digital beam in a transmitting device (base station device 3 in the case of downlink and terminal device 1 in the case of uplink) with the directivity of an analog and / or digital beam in a receiving device (terminal device 1 in the case of downlink and base station device 3 in the case of uplink) to obtain beam gain.

[0072] In addition, procedures for configuring, setting up or establishing a beam pair link may include the following procedures. Beam selection Beam refinement Beam recovery

[0073] For example, beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Beam improvement may be a procedure for selecting a beam with a higher gain, or changing the beam between the base station device 3 and the terminal device 1 to an optimal one due to movement of the terminal device 1. Beam recovery may be a procedure for reselecting a beam when the quality of the communication link is degraded due to blockage caused by the passage of an obstruction or a person in communication between the base station device 3 and the terminal device 1.

[0074] Beam management may include beam selection, beam improvement. Beam recovery may include the following procedures: Beam failure detection New beam discovery · Sending a beam recovery request -Monitoring responses to beam recovery requests

[0075] For example, when selecting a transmission beam of the base station device 3 in the terminal device 1, the RSRP (Reference Signal Received Power) of the SSS included in the CSI-RS or SS / PBCH block may be used, or the CSI may be used. In addition, a CSI-RS resource index (CRI) may be used as a report to the base station device 3, or an index indicated by a sequence of the PBCH included in the SS / PBCH block and / or a demodulation reference signal (DMRS) used for demodulating the PBCH may be used.

[0076] Furthermore, the base station device 3 instructs the terminal device 1 of a time index of CRI or SS / PBCH when instructing the beam, and the terminal device 1 receives based on the time index of the instructed CRI or SS / PBCH. At this time, the terminal device 1 may set a spatial filter based on the time index of the instructed CRI or SS / PBCH and receive. Furthermore, the terminal device 1 may receive using a quasi co-location (QCL) assumption. A signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" with another signal (antenna port, synchronization signal, reference signal, etc.) or "QCL assumption is used" may be interpreted as a signal being associated with another signal.

[0077] Two antenna ports are said to be QCLs if the long-term properties of the channel over which a symbol at one antenna port is carried can be inferred from the channel over which a symbol at the other antenna port is carried. The long-term properties of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna port 1 and antenna port 2 are QCLs with respect to average delay, it means that the receive timing of antenna port 2 can be inferred from the receive timing of antenna port 1.

[0078] This QCL can also be extended to beam management. For this purpose, a spatially extended QCL may be newly defined. For example, the long term properties of a channel in the spatial domain may be the angle of arrival (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or the angle spread (e.g. ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)) in a radio link or channel, the angle of departure (AoD, ZoD, etc.) and its angle spread (e.g. ASD (Angle Spread of Departure) and ZSD (Zenith angle Spread of Departure)), spatial correlation, and reception spatial parameters.

[0079] For example, if antenna port 1 and antenna port 2 can be considered as a QCL in terms of receive spatial parameters, it means that a receive beam for receiving a signal from antenna port 2 can be inferred from a receive beam (receive spatial filter) for receiving a signal from antenna port 1.

[0080] A combination of long-range properties that may be considered to be a QCL may be defined as a QCL type. For example, the following types may be defined: Type A: Doppler shift, Doppler spread, average delay, delay spread Type B: Doppler shift, Doppler spread Type C: Average delay, Doppler shift Type D: Reception spatial parameters

[0081] The above-mentioned QCL type may be set and / or indicated as a transmission configuration indication (TCI) in the RRC and / or MAC layer and / or DCI, which indicates the assumption of QCL between one or two reference signals and PDCCH or PDSCH DMRS. For example, when the index #2 of the SS / PBCH block and the QCL type A+QCL type B are set and / or indicated as one state of the TCI when the terminal device 1 receives the PDCCH, the terminal device 1 may receive the DMRS of the PDCCH and perform synchronization and propagation path estimation by regarding the Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters, and long-range characteristics of the channel when receiving the SS / PBCH block index #2 as the long-range characteristics of the channel. At this time, the reference signal indicated by the TCI (SS / PBCH block in the above example) may be referred to as a source reference signal, and the reference signal (PDCCH DMRS in the above example) influenced by the long-range characteristics inferred from the long-range characteristics of the channel when receiving the source reference signal may be referred to as a target reference signal. Furthermore, the TCI may be configured by RRC with one or more TCI states and a combination of a source reference signal and a QCL type for each state, and may be indicated to the terminal device 1 by the MAC layer or DCI.

[0082] With this method, operations of the base station device 3 and the terminal device 1 equivalent to beam management may be defined as beam management and beam instruction / reporting, based on the assumption of QCL in the spatial domain and radio resources (time and / or frequency).

[0083] The subframe will be described below. In this embodiment, the following will be referred to as a subframe, but the subframe according to this embodiment may also be referred to as a resource unit, a radio frame, a time period, a time interval, etc.

[0084] FIG. 3 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each radio frame is 10 ms long. Each radio frame is composed of 10 subframes and W slots. One slot is composed of X OFDM symbols. That is, one subframe has a length of 1 ms. Each slot has a time length defined by a subcarrier interval. For example, when the subcarrier interval of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. When the subcarrier interval is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. When X=14, for example, when the subcarrier interval is 15 kHz, W=10, and when the subcarrier interval is 60 kHz, W=40. FIG. 3 shows a case of X=7 as an example. Note that the example of FIG. 3 can be similarly extended to a case of X=14. Also, the uplink slot is defined similarly, and the downlink slot and the uplink slot may be defined separately. Also, the bandwidth of the cell in FIG. 3 may be defined as a part of the band (BWP: BandWidth Part). Also, the slot may be defined as a transmission time interval (TTI: Transmission Time Interval). The slot may not be defined as a TTI. The TTI may be a transmission period of a transport block.

[0085] The signals or physical channels transmitted in each slot may be represented by a resource grid. The resource grid is defined by a number of subcarriers and a number of OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers constituting one slot depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is called a resource element. A resource element may be identified by a subcarrier number and an OFDM symbol number.

[0086] The resource grid is used to express the mapping of resource elements of a certain physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier spacing is 15 kHz, the number of OFDM symbols included in a subframe is X=14, and in the case of NCP, one 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 (RBs) determined by the subcarrier spacing setting μ described later. That is, the resource grid is composed of (14*12*Nmax,μ) resource elements. In the case of ECP (Extended CP), since only a subcarrier spacing of 60 kHz is supported, one physical resource block is defined by, for example, 12 (the number of OFDM symbols included in one slot)*4 (the number of slots included in one subframe)=48 consecutive OFDM symbols in the time domain and 12*Nmax,μ consecutive subcarriers in the frequency domain. That is, the resource grid consists of (48*12*Nmax,μ) resource elements.

[0087] As resource blocks (RB), reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined. One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may be a resource block with a subcarrier interval of, for example, 15 kHz, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or may simply be referred to as a "reference point"). The common resource block is a resource block numbered in ascending order from 0 at each subcarrier interval setting μ from reference point A. The above-mentioned resource grid is defined by this common resource block. The physical resource block is a resource block numbered in ascending order from 0 included in a band part (BWP) described later, and the physical resource block is a resource block numbered in ascending order from 0 included in the band part (BWP). A certain physical uplink channel is first mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. Hereinafter, the resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

[0088] Next, we will explain the subcarrier spacing setting μ. As mentioned above, NR supports one or more OFDM numerologies. For a given BWP, the subcarrier spacing setting μ (μ=0,1,...,5) and the cyclic prefix length are given by higher layers for the downlink BWP and by higher layers for the uplink BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf=2^μ·15(kHz).

[0089] For subcarrier spacing setting μ, slots are numbered from 0 to N^{subframe,μ}_{slot}-1 in ascending order within a subframe and from 0 to N^{frame,μ}_{slot}-1 in ascending order within a frame. Based on the slot setting and cyclic prefix, there are N^{slot}_{symb} consecutive OFDM symbols in a slot, where N^{slot}_{symb} is 14. The start of a slot n^{μ}_{s} in a subframe is aligned in time with the start of the n^{μ}_{s}*N^{slot}_{symb}th OFDM symbol in the same subframe.

[0090] Next, subframes, slots, and minislots will be described. FIG. 4 is a diagram showing an example of the relationship between subframes, slots, and minislots in the time domain. As shown in the diagram, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier interval, the number of OFDM symbols included in a slot is 7 or 14 (however, if the cyclic prefix (CP) added to each symbol is Extended CP, it may be 6 or 12), and the slot length differs depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, one subframe includes 14 OFDM symbols. A downlink slot may be referred to as PDSCH mapping type A. An uplink slot may be referred to as PUSCH mapping type A.

[0091] A minislot (which may be called a subslot) is a time unit consisting of a number of OFDM symbols less than the number of OFDM symbols included in one slot. The figure shows an example in which a minislot is composed of two OFDM symbols. The OFDM symbols in a minislot may coincide with the OFDM symbol timing that constitutes the slot. The minimum unit of scheduling may be a slot or a minislot. Allocating a minislot may be called non-slot based scheduling. Scheduling a minislot may be expressed as scheduling a resource in which the relative time positions of the start positions of a reference signal and data are fixed. A downlink minislot may be called PDSCH mapping type B. An uplink minislot may be called PUSCH mapping type B.

[0092] In the terminal device 1, the transmission direction (uplink, downlink, or flexible) of the symbol in each slot is set in a higher layer using an RRC message including a predetermined higher layer parameter received from the base station device 3, or is set by a PDCCH of a specific DCI format (e.g., DCI format 2_0) received from the base station device 3. In this embodiment, a slot format that sets each symbol in a slot to either uplink, downlink, or flexible is called a slot format. One slot format may include a downlink symbol, an uplink symbol, and a flexible symbol.

[0093] FIG. 5 is a diagram showing an example of a slot format. Here, an example is shown in which the subcarrier spacing is 15 kHz and the slot length is 1 ms. In the figure, D indicates the downlink and U indicates the uplink. As shown in the figure, within a certain time interval (for example, the minimum time interval that must be allocated to one UE in the system), Downlink symbol Flexible Symbols One or more of the uplink symbols may be included. The ratio of these symbols in a certain slot may be predetermined as a slot format. The ratio of these symbols in a certain slot may be defined by the number of downlink OFDM symbols included in the slot, or the start position and / or end position in the slot. The ratio of these symbols in a certain slot may be defined by the number of uplink OFDM symbols or the number of DFT-S-OFDM symbols included in the slot, or the start position and / or end position in the slot. The scheduling of a slot for the terminal device 1 may be expressed as the scheduling of a resource in which the relative time position of the reference signal and the slot boundary is fixed.

[0094] When the terminal device 1 is provided with the higher layer parameter TDD-UL-DL-ConfigurationCommon, it sets the slot format for each slot as indicated in TDD-UL-DL-ConfigurationCommon over one or more slots. TDD-UL-DL-ConfigurationCommon provides the following parameters: Reference subcarrier spacing (SCS:subcarrier spacing) setting μ ref Slot format pattern 1

[0095] Slot format pattern 1 provides the following parameters: - Slot duration P (milliseconds) The number of downlink slots (downlink slots) consisting of only downlink symbols within the slot setting period P, d slots The number of downlink symbols d excluding the symbols in the downlink slots during the slot setting period P sym The number of slots (uplink slots) consisting of only uplink symbols within the slot setting period P, u slots The number of uplink symbols u excluding the symbols in the uplink slots during the slot setting period P sym

[0096] The slot setting period P (milliseconds) is the reference SCS setting μ ref In (S=P*2^(μ ref )) slot. In the S slot, the first d slots The slot contains only downlink symbols, and the last u slots The slot contains only uplink symbols. The first d slots Next d sym The symbol is a downlink symbol, and the last u slots The u immediately before sym The symbols are uplink symbols. The remaining symbols in the S slot are flexible symbols.

[0097] In TDD-UL-DL-ConfigurationCommon, slot format pattern 2 may be provided in addition to slot format pattern 1. Slot format pattern 2 includes parameters similar to those in slot format pattern 1, and each parameter may be set to a value different from that in slot format pattern 1. Slot format pattern 2 includes an S2 slot, and provides a setting for the slot format in the S2 slot next to the S slot.

[0098] The terminal device 1 sets the slot format of each slot for every S slot (if only slot format pattern 1 is provided) or for every (S+S2) slot (if slot format pattern 1 and slot format pattern 2 are provided) based on slot format pattern 1 and / or slot format pattern 2 provided in TDD-UL-DL-ConfigurationCommon. However, parameters indicating other slot format patterns including similar parameters (e.g., slot format pattern 3 indicating the slot format of the S3 slot, etc.) may be provided, and the slot format of each slot may be set. However, the terminal device 1 sets the slot format of each slot for every S slot (if only slot format pattern 1 is provided) or for every (S+S2) slot (if slot format pattern 1 and slot format pattern 2 are provided) based on slot format pattern 1 and / or slot format pattern 2 provided in TDD-UL-DL-ConfigurationCommon. ref When the SCS setting μ of the DL BWP or UL BWP described later is different, the transmission direction of each symbol in the slot format set by TDD-UL-DL-ConfigurationCommon is set to the consecutive 2^(μ-μ ref ) symbols.

[0099] When the terminal device 1 is provided with the higher layer parameter TDD-UL-DL-ConfigurationDedicated, it may overwrite a flexible symbol among the slot formats of multiple slots set in the higher layer parameter TDD-UL-DL-ConfigurationCommon with an uplink symbol, a downlink symbol or a flexible symbol.

[0100] An RRC message including TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated may be referred to as an RRC message including higher layer slot format configuration information, and setting the slot format (uplink symbol / downlink symbol / flexible symbol) in TDD-UL-DL-ConfigurationCommon and / or TDD-UL-DL-ConfigurationDedicated may be referred to as setting the slot format (uplink symbol / downlink symbol / flexible symbol) based on the higher layer slot format configuration information.

[0101] The terminal device 1 considers that symbols (also called semi-static downlink symbols) indicated as downlink in the higher layer slot format setting information are available for reception, and does not transmit uplink signals (e.g., PUSCH, PUCCH, PRACH, and / or SRS). The terminal device 1 considers that symbols (also called semi-static uplink symbols) indicated as uplink in the higher layer slot format setting information are available for transmission, and does not receive downlink signals (e.g., PDCCH, PDSCH, or CSI-RS).

[0102] When the terminal device 1 is not configured to monitor a PDCCH for a DCI format (e.g., DCI format 2_0) that sets the slot format, it may receive a downlink signal (e.g., PDSCH or CSI-RS) specified in a specified DCI format (e.g., DCI format 1_0, 1_1 or 0_1) in a symbol (also referred to as a semi-static flexible symbol) indicated as flexible in the higher layer slot format setting information (which may include any symbol when higher layer slot format setting information is not provided), and may transmit an uplink signal (e.g., PUSCH, PUCCH, PRACH or SRS) specified in a specified DCI format (e.g., DCI format 0_0, 0_1, 1_0, 1_1 or 2_3).

[0103] When the terminal device 1 is not configured to monitor a PDCCH for a DCI format (e.g., DCI format 2_0) that sets the slot format, and is configured to receive a downlink signal (e.g., PDCCH, PDSCH or CSI-RS) in a set of symbols that is an upper layer in symbols indicated as flexible in the upper layer slot format setting information (which may include any symbol when the upper layer slot format setting information is not provided), if a specified DCI format (e.g., DCI format 0_0, 0_1, 1_0, 1_1 or 2_3) indicating that an uplink signal (e.g., PUSCH, PUCCH, PRACH or SRS) is transmitted is not detected in any one symbol of the set of symbols, the terminal device 1 receives the downlink signal, and in other cases, does not receive the downlink signal in the set of symbols.

[0104] When the terminal device 1 is not configured to monitor a PDCCH for a DCI format (e.g., DCI format 2_0) including a slot format indicator (SFI), and is configured to transmit an uplink signal (e.g., SRS, PUCCH, PUSCH or PRACH) in a set of symbols in a higher layer in symbols indicated as flexible in the higher layer slot format setting information (which may include any symbol when higher layer slot format setting information is not provided), if the terminal device 1 does not detect a specified DCI format (e.g., DCI format 1_0, 1_1 or 0_1) indicating reception of a downlink signal (e.g., CSI-RS or PDSCH) in any one symbol of the set of symbols, the terminal device 1 transmits the uplink signal.

[0105] When the upper layer parameter SlotFormatIndicator is set by the upper layer, the terminal device 1 monitors a DCI format including a slot format indicator (SFI) field (for example, DCI format 2_0). The DCI format including the SFI field may be referred to as a slot format setting DCI or slot format setting information by the PDCCH.

[0106] The value of the SFI field in the DCI format indicates a combination of slot formats (slot format combination) of each of multiple slots starting from the slot in which the DCI format is detected to the terminal device 1. The value of the SFI field indicates an index value corresponding to one of a set of slot format combinations set in a higher layer.

[0107] In the terminal device 1, the following parameters are set for each serving cell by SlotFormatIndicator. Serving cell identifier The position of the corresponding SFI field in the DCI format A set of slot format combinations (each slot format combination indicates a combination of slot format indexes corresponding to each of a number of slots from a predefined slot format table) Reference SCS configuration in FDD μ SFI · Reference SCS setting for DL ​​BWP in TDD μ SFI,DL and UL BWP reference SCS setting μ SFI,UL

[0108] FIG. 6 is a diagram showing an example of a slot format table according to the present embodiment. In the table of FIG. 6, 256 slot formats are shown, and indexes from 0 to 255 are assigned to each of them (however, slot formats with indexes from 5 to 254 are omitted in FIG. 6). In each slot format, "Symbol number in a slot" corresponds to symbols with indexes from 0 to 13 in the slot, and D indicates a downlink symbol (also called a dynamic downlink symbol), U indicates an uplink symbol (also called a dynamic uplink symbol), and F indicates a flexible symbol (also called a dynamic flexible symbol). In addition, the slot format table may include a slot format index that determines a slot format based on higher layer slot format setting information without directly indicating a slot format, such as the slot format index of 255 in FIG. 6.

[0109] In FDD, the reference SCS setting μ for each slot format of the slot format combination indicated by the value of the SFI field SFIEach downlink symbol, uplink symbol and flexible symbol of the SCS setting μ is a consecutive 2^(μ-μ SFI ) downlink symbols, uplink symbols and flexible symbols.

[0110] In TDD, μ SFI,DL >μ SFI,UL If the value of the SFI field is 2^(μ SFI,DL -μ SFI,UL )+1 slot format is the first 2^(μ SFI,DL -μ SFI,DL ) applies to the reference DL BWP and the next one applies to the reference UL BWP. SFI,DL <μ SFI,DL If the value of the SFI field is 2^(μ SFI,UL -μ SFI,DL )+1 slot formats, the first one applies to the reference DL BWP and the next 2^(μ SFI,UL -μ SFI,DL ) apply to the reference UL BWP.

[0111] In TDD, the reference SCS setting μ for each slot format of the reference DL BWP of the slot format combination indicated by the value of the SFI field SFI,DL Each downlink symbol, uplink symbol and flexible symbol of DL The active DL BWPs of consecutive 2^(μ DL -μ SFI,DL ) downlink symbols, uplink symbols and flexible symbols, and the reference SCS setting μ SFI,UL Each downlink symbol, uplink symbol and flexible symbol of UL The active UL BWP of consecutive 2^(μ UL -μ SFI,UL) downlink symbols, uplink symbols and flexible symbols.

[0112] The terminal device 1 may receive a downlink signal or a downlink channel using a downlink symbol or a flexible symbol. The terminal device 1 may transmit an uplink signal or a downlink channel using an uplink symbol or a flexible symbol.

[0113] FIG. 5(a) shows an example in which a certain time interval (for example, the minimum unit of time resource that can be assigned to one UE, or may be referred to as a time unit, etc., or a plurality of minimum units of time resource may be bundled and referred to as a time unit) is entirely used for downlink transmission, and FIG. 5(b) shows an example in which the first time resource is used for uplink scheduling, for example, via PDCCH, and an uplink signal is transmitted via a flexible symbol including a processing delay for PDCCH, a switching time from downlink to uplink, and generation of a transmission signal. FIG. 5(c) shows an example in which the first time resource is used for transmitting PDCCH and / or downlink PDSCH, and is used for transmitting PUSCH or PUCCH via a gap for processing delay, a switching time from downlink to uplink, and generation of a transmission signal. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and / or CSI, i.e., UCI. In Fig. 5(d), the first time resource is used for transmitting PDCCH and / or PDSCH, and then, via a gap for processing delay, downlink to uplink switching time, and generation of a transmission signal, is used for transmitting uplink PUSCH and / or PUCCH. Here, as an example, the uplink signal may be used for transmitting uplink data, i.e., UL-SCH. In Fig. 5(e), all the time resources are used for uplink transmission (PUSCH or PUCCH).

[0114] The above-mentioned downlink part and uplink part may be composed of multiple OFDM symbols, similar to LTE.

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

[0116] Hereinafter, the bandwidth part (BWP, Bandwidth part) will be described. The BWP is also referred to as a carrier BWP. The BWP may be set for each of the downlink and the uplink. The BWP is defined as a set of consecutive physical resources selected from a consecutive subset of common resource blocks. The terminal device 1 can be set up to 4 BWPs in which one downlink carrier BWP (DL BWP) is activated at a certain time. The terminal device 1 can be set up to 4 BWPs in which one uplink carrier BWP (UL BWP) is activated at a certain time. In the case of carrier aggregation, the BWP may be set in each serving cell. At this time, the fact that one BWP is set in a certain serving cell may be expressed as "no BWP is set". Also, the fact that two or more BWPs are set may be expressed as "BWP is set".

[0117] <MAC entity operation> In an activated serving cell, there is always one active BWP. BWP switching for a serving cell is used to activate an inactive BWP and deactivate an active BWP. BWP switching for a serving cell is controlled by a PDCCH indicating a downlink assignment or an uplink grant. BWP switching for a serving cell may also be controlled by a BWP inactivity timer, RRC signaling, or the MAC entity itself at the start of a random access procedure. Upon addition of an SpCell (PCell or PSCell) or activation of an SCell, one BWP is first active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The first active DL BWP and the first active UL BWP may be specified in an RRC message sent from the base station device 3 to the terminal device 1. The active BWP for a serving cell is specified by the RRC or PDCCH sent from the base station device 3 to the terminal device 1. Also, the first active DL BWP and the UL BWP may be included in the message 4. In an unpaired spectrum (such as a TDD band), the DL BWP and the UL BWP are paired, and BWP switching is common for the UL and DL. In the active BWP for each activated serving cell for which a BWP is configured, the MAC entity of the terminal device 1 applies normal processing. The normal processing includes transmitting a UL-SCH, transmitting a RACH, monitoring a PDCCH, transmitting a PUCCH, transmitting an SRS, and receiving a DL-SCH.For each activated serving cell with BWP configured, in an inactive BWP, 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. When a certain serving cell is deactivated, the active BWP may be made non-existent (for example, the active BWP is deactivated).

[0118] <RRC operation> The BWP information element (IE) included in the RRC message (the notified system information or the information sent in the dedicated RRC message) is used to configure the BWP. The RRC message transmitted from the base station device 3 is received by the terminal device 1. For each serving cell, the network (such as the base station device 3) configures at least an initial BWP for the terminal device 1, including at least a downlink BWP and one (such as when the serving cell is configured for uplink) or two (such as when the supplementary uplink in the appendix is used) uplink BWPs. Further, the network may configure additional uplink BWPs or downlink BWPs for a certain serving cell. The BWP configuration is divided into uplink parameters and downlink parameters. Also, the BWP configuration is divided into common parameters and dedicated parameters. The common parameters (such as the BWP uplink common IE and the BWP downlink common IE) are cell-specific. The common parameters of the initial BWP of the primary cell are also provided in the system information. For all other serving cells, the network provides the common parameters by a dedicated signal. The BWP is identified by the BWP ID. The initial BWP has a BWP ID of 0. The BWP IDs of other BWPs take values from 1 to 4.

[0119] If the higher layer parameter initialDownlinkBWP is not configured (provided) for the terminal device 1, the initial DL BWP (initial active DL BWP) may be defined by the position and number of consecutive PRBs, subcarrier spacing, and cyclic prefix for PDCCH reception in a control resource set (CORESET) for a type 0 PDCCH common search space. The position of the consecutive PRBs starts from the PRB with the smallest index and ends with the PRB with the largest index among the PRBs of the control resource set for the type 0 PDCCH common search space. If the higher layer parameter initialDownlinkBWP is configured (provided) for the terminal device 1, the initial DL BWP may be indicated by the higher layer parameter initialDownlinkBWP. The higher layer parameter initialDownlinkBWP may be included in SIB1 (systemInformationBlockType1, ServingCellConfigCommonSIB) or ServingCellConfigCommon. The information element ServingCellConfigCommonSIB is used to configure cell-specific parameters of the serving cell for terminal device 1 within SIB1.

[0120] That is, when the higher layer parameter initialDownlinkBWP is not configured (provided) for the terminal device 1, the size of the initial DL BWP may be the number of resource blocks of the control resource set (CORESET#0) for the Type 0 PDCCH common search space. When the higher layer parameter initialDownlinkBWP is configured (provided) for the terminal device 1, the size of the initial DL BWP may be given by the locationAndBandwidth included in the higher layer parameter initialDownlinkBWP. The higher layer parameter locationAndBandwidth may indicate the frequency domain location and bandwidth of the initial DL BWP.

[0121] As described above, multiple DL BWPs may be set for the terminal device 1. Then, a default DL BWP can be set by the upper layer parameter defaultDownlinkBWP-Id among the DL BWPs set for the terminal device 1. If the upper layer parameter defaultDownlinkBWP-Id is not provided for the terminal device 1, the default DL BWP is the initial DL BWP.

[0122] The terminal device 1 may be provided with an initial UL BWP by SIB1 (systemInformationBlockType1) or initialUplinkBWP. The information element initialUplinkBWP is used to configure the initial UL BWP. For operation in an SpCell or a secondary cell, the terminal device 1 may be configured (provided) with an initial UL BWP (initial active UL BWP) by the higher layer parameter initialUplinkBWP. If a supplementary uplink carrier is configured for the terminal device 1, the terminal device 1 may be configured with an initial UL BWP on the supplementary uplink carrier by the initialUplinkBWP included in the higher layer parameter supplementaryUplink.

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

[0124] A control resource set (CORESET) is a time and frequency resource for searching downlink control information. The configuration information of a CORESET includes a CORESET identifier (ControlResourceSetId, CORESET-ID) and information for identifying the frequency resource of the CORESET. The information element ControlResourceSetId (CORESET identifier) ​​is used to identify a control resource set in a serving cell. The CORESET identifier is used between BWPs in a serving cell. The CORESET identifier is unique between BWPs in a serving cell. The number of CORESETs in each BWP is limited to 3, including the initial CORESET. In a serving cell, the value of the CORESET identifier ranges from 0 to 11.

[0125] The control resource set identified by the identifier 0 (ControlResourceSetId 0) of CORESET is called CORESET#0. CORESET#0 may be configured by pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. That is, the configuration information of CORESET#0 may be pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. The configuration information of CORESET#0 may be configured by controlResourceSetZero included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. That is, the information element controlResourceSetZero is used to indicate CORESET#0 (common CORESET) of the initial DL BWP. The CORESET indicated by pdcch-ConfigSIB1 is CORESET#0. The information element pdcch-ConfigSIB1 in the MIB or the dedicated configuration is used to configure the initial DL BWP. The configuration information pdcch-ConfigSIB1 of CORESET for CORESET#0 does not include information that explicitly identifies the identifier of CORESET and the frequency resources (e.g., the number of consecutive resource blocks) and time resources (the number of consecutive symbols) of CORESET, but the frequency resources (e.g., the number of consecutive resource blocks) and time resources (the number of consecutive symbols) of CORESET for CORESET#0 can be implicitly specified by the information included in pdcch-ConfigSIB1. The information element PDCCH-ConfigCommon is used to configure cell-specific PDCCH parameters provided in the SIB. PDCCH-ConfigCommon may also be provided at the time of handover and addition of PSCell and / or SCell. The configuration information of CORESET#0 is included in the configuration of the initial BWP.That is, the configuration information of CORESET#0 does not need to be included in the configuration of BWPs other than the initial BWP. controlResourceSetZero corresponds to 4 bits (e.g., the 4 most significant bits) of pdcch-ConfigSIB1. CORESET#0 is a control resource set for the type 0 PDCCH common search space.

[0126] Configuration information of an additional common CORESET (additional common control resource set) may be configured by a commonControlResourceSet included in PDCCH-ConfigCommon. Configuration information of the additional common CORESET may also be used to specify an additional common CORESET for system information and / or paging procedures. Configuration information of the additional common CORESET may be used to specify an additional common CORESET used for a random access procedure. Configuration information of the additional common CORESET may be included in the configuration of each BWP. The identifier of the CORESET indicated in the commonControlResourceSet takes a value other than 0.

[0127] The common CORESET may be a CORESET (for example, an additional common CORESET) used in a random access procedure. In addition, in this embodiment, the common CORESET may include a CORESET set by the setting information of CORESET#0 and / or an additional common CORESET. In other words, the common CORESET may include CORESET#0 and / or an additional common CORESET. CORESET#0 may be referred to as common CORESET#0. The terminal device 1 may also refer to (obtain) the setting information of the common CORESET in a BWP other than the BWP in which the common CORESET is set.

[0128] Configuration information of one or more CORESETs may be configured by PDCCH-Config. The information element PDCCH-Config is used to configure UE-specific PDCCH parameters (e.g., CORESET, search space, etc.) for a BWP. PDCCH-Config may be included in the configuration of each BWP.

[0129] That is, in this embodiment, the configuration information of the common CORESET indicated by 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. Also, the configuration information of one or more CORESETs (UE specifically configured Control Resource Sets, UE-specific CORESETs) indicated by PDCCH-Config is controlResourceSetToAddModList.

[0130] A search space is defined to search for PDCCH candidates. A searchSpaceType included in the configuration information of a search space indicates whether the search space is a common search space (CSS) or a UE-specific search space (USS). A UE-specific search space is derived from at least the value of a C-RNTI set by a terminal device 1. That is, a UE-specific search space is derived individually for each terminal device 1. A common search space is a search space common to multiple terminal devices 1, and is composed of CCEs (Control Channel Elements) of a predetermined index. A CCE is composed of multiple resource elements. The configuration information of a search space includes information on a DCI format to be monitored in the search space.

[0131] The configuration information of the search space includes an identifier of the CORESET identified by the configuration information of the CORESET. The CORESET identified by the identifier of the CORESET included in the configuration information of the search space is associated with the search space. In other words, the CORESET associated with the search space is a CORESET identified by the identifier of the CORESET included in the search space. The DCI format indicated by the configuration information of the 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 for the random access procedure may be configured by ra-SearchSpace. That is, the DCI format to which a CRC scrambled by RA-RNTI or TC-RNTI is added is monitored in the CORESET associated with the ra-SearchSpace.

[0132] The terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs arranged in each active serving cell configured to monitor the PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. "Monitoring" may mean decoding each PDCCH candidate according to one or more DCI formats to be monitored. The set of PDCCH candidates monitored by the terminal device 1 is defined by PDCCH search space sets. One search space set is a common search space set or a UE-specific search space set. In the above, the search space set is referred to as a search space, the common search space set is referred to as a common search space, and the UE-specific search space set is referred to as a UE-specific search space. The terminal device 1 monitors PDCCH candidates in one or more of the following search space sets. - a Type0-PDCCH common search space set: This search space set is configured by the higher layer parameters pdcch-ConfigSIB1 or searchSpaceSIB1 indicated in PDCCH-ConfigCommon or searchSpaceZero included in PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRC scrambled with SI-RNRI in the primary cell. - a Type0A-PDCCH common search space set: This search space set is configured by the higher layer parameters searchSpaceOtherSystemInformation indicated in PDCCH-ConfigCommon.This search space is for monitoring the DCI format of CRC scrambled with SI-RNRI in the primary cell. - a Type1-PDCCH common search space set: This search space set is configured by the higher layer parameter search space for random access procedure (ra-SearchSpace) indicated in PDCCH-ConfigCommon. This search space is for monitoring the DCI format of CRC scrambled with RA-RNRI or TC-RNTI in the primary cell. The Type1-PDCCH common search space set is a search space set for random access procedure. - a Type2-PDCCH common search space set: This search space set is configured by the higher layer parameter search space for paging procedure (pagingSearchSpace) indicated in PDCCH-ConfigCommon. This search space is for monitoring the DCI format of the CRC scrambled with the P-RNTI in the primary cell. - a Type3-PDCCH common search space set: This search space set is configured by the higher layer parameter SearchSpace with a search space type of Common indicated in PDCCH-Config. This search space is for monitoring the DCI format of the CRC scrambled with the INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. For the primary cell, it is for monitoring the DCI format of the CRC scrambled with the C-RNTI, CS-RNTI(s), or MCS-C-RNTI.- a UE-specific search space set: This search space set is configured by the higher layer parameter PDCCH-Config with a search space type of UE specific (SearchSpace). This search space is for monitoring DCI formats of C-RNTI, CS-RNTI(s) or CRC scrambled with MCS-C-RNTI.

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

[0134] The BWP configuration information is divided into DL BWP configuration information and UL BWP configuration information. The BWP configuration information includes information element bwp-Id (BWP identifier). The BWP identifier included in the DL BWP configuration information is used to identify (reference) the DL BWP in a serving cell. The BWP identifier included in the UL BWP configuration information is used to identify (reference) the UL BWP in a serving cell. BWP identifiers are assigned to each of DL BWP and UL BWP. For example, the BWP identifier corresponding to a DL BWP may be referred to as a DL BWP index. The BWP identifier corresponding to a UL BWP may be referred to as a UL BWP index. The initial DL BWP is referenced by DL BWP identifier 0. The initial UL BWP is referenced by UL BWP identifier 0. Other DL BWPs or other UL BWPs may each be referenced by BWP identifiers 1 to maxNrofBWPs. That is, a BWP identifier 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 other BWP identifiers can have values ​​from 1 to 4. Other higher layer configuration information is associated with a specific BWP using the BWP identifier. A DL BWP and a UL BWP having the same BWP identifier may mean that the DL BWP and the UL BWP are paired.

[0135] The terminal device 1 may be configured with one primary cell and up to 15 secondary cells.

[0136] The procedure for transmitting the PUSCH will be described below.

[0137] The repetitive transmission of PUSCH to which the first repetitive transmission scheme according to this embodiment is applied will be described. The first repetitive transmission scheme is a scheme in which one PUSCH (e.g., one transport block) is continuously and repeatedly transmitted in the time domain in uplink resources available for transmitting the PUSCH. For example, multiple time resources are assigned to one transport block, and the transport block is coded and transmitted in accordance with each of the multiple time resources, so that the same transport block is repeatedly transmitted the number of times corresponding to the multiple time resources used for transmission.

[0138] The terminal device 1 may transmit a corresponding PUSCH by detecting a PDCCH including DCI format 0_0, DCI format 0_1, or DCI format 0_2. That is, the corresponding PUSCH may be scheduled (indicated) by the DCI format (DCI). For example, when transmitting a PUSCH scheduled with DCI format 0_2 in a PDCCH CRC-scrambled with a predetermined RNTI (for example, C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1), the terminal device 1 may transmit a PUSCH by applying a first repetition transmission scheme. For example, when transmitting a PUSCH scheduled with DCI format 0_2 in a PDCCH CRC-scrambled with a predetermined RNTI (for example, C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1), if a predetermined parameter (for example, pusch-Aggregation-v16) is set in an upper layer, the terminal device 1 may transmit a PUSCH by applying a first repetition transmission scheme. For example, when the terminal device 1 transmits a PUSCH scheduled in DCI format 0_1 ​​in a PDCCH CRC-scrambled with a predetermined RNTI (for example, C-RNTI, MCS-C-RNTI, or CS-RNTI with NDI=1), if a predetermined parameter (for example, pusch-Aggregation-v16) is set in the higher layer, the terminal device 1 may transmit the PUSCH by applying the first repetition transmission scheme. The PUSCH may also be scheduled by an RAR UL grant included in an RAR message. The start position (start symbol) of the scheduled PUSCH may be defined by S. The start symbol S of the PUSCH may be the symbol index of the first symbol in a certain slot where a certain PUSCH is transmitted (mapped). For example, when 14 symbols are included in a slot, the available values ​​for S may be 0 to 13. The start symbol S indicates the number of symbols from the beginning of the slot. For example, when the value of S is 2, the terminal device 1 may transmit the PUSCH from the third symbol of a certain slot.The number of consecutive symbols of the scheduled PUSCH is referred to as L. The number L of consecutive symbols is counted from the starting symbol S. The determination of S and L assigned to the PUSCH will be described later. However, when the first repetition transmission scheme is applied to transmit the PUSCH, S may be the index of the starting symbol of the first PUSCH that is repeatedly transmitted. However, when the first repetition transmission scheme is applied to transmit the PUSCH, L may be the nominal number of symbols of the PUSCH that is repeatedly transmitted. For example, when the first repetition transmission scheme is applied to transmit the PUSCH, the number of symbols used for one PUSCH that is repeatedly transmitted and the number of symbols indicated by L may be different values. For example, when the first repetition transmission scheme is applied to transmit the PUSCH, the maximum number of symbols available for one PUSCH that is repeatedly transmitted may be L. The terminal device 1 may transmit multiple corresponding PUSCHs by detecting the DCI format 0_2.

[0139] The type of PUSCH mapping may include 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. However, 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 may be limited to a value from 1 to 14. However, under a certain condition, the sum of S and L may not be limited. For example, when a certain higher layer parameter is set, the sum of S and L may not be limited, and when the parameter is not set, the sum of S and L may be limited. However, when a certain higher layer parameter is set, a different mapping type (e.g., PUSCH mapping type C) may be set instead of PUSCH mapping type B. PUSCH mapping type C may be a mapping type corresponding to allocation in minislot units like PUSCH mapping type B. For example, in PUSCH mapping type B, the sum of S and L may be limited to values ​​from 1 to 14, while in PUSCH mapping type C, the sum of S and L may not be limited. The following description of PUSCH mapping type B may also be applied to PUSCH mapping type C.

[0140] The position of the DMRS symbol for the PUSCH may depend on the type of PUSCH mapping. The position of the first DMRS symbol for the PUSCH may depend on the type of PUSCH mapping. In PUSCH mapping type A, the position of the first DMRS symbol may be indicated in the higher layer parameter dmrs-TypeA-Position. For example, 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 for the PUSCH may be the third symbol in a slot. For example, if dmrs-TypeA-Position is set to 'pos3', the position of the first DMRS symbol for the PUSCH may be the fourth symbol in a slot. In PUSCH mapping type B and PUSCH mapping type C, the position of the first DMRS symbol may be the first symbol of the assigned PUSCH.

[0141] A method for determining PUSCH time domain resource allocation will now be described.

[0142] The base station device 3 may schedule the terminal device 1 to transmit a PUSCH by detecting a DCI addressed to the terminal device 1. The terminal device 1 may transmit a PUSCH by detecting a DCI addressed to the terminal device 1. When identifying a PUSCH time domain resource allocation, the terminal device 1 determines a resource allocation table to be applied to the PUSCH. The resource allocation table includes one or more PUSCH time domain resource allocation settings. The terminal device 1 may select one PUSCH time domain resource allocation setting in the determined resource allocation table based on a value indicated in a 'Time domain resource assignment' field included in the DCI that schedules the PUSCH. That is, the base station device 3 determines a resource allocation of a PUSCH for the terminal device 1, generates a value for the 'Time domain resource assignment' field, and transmits a DCI including the 'Time domain resource assignment' field to the terminal device 1. The terminal device 1 identifies a time domain resource allocation of a PUSCH based on a value set in the 'Time domain resource assignment' field.

[0143] 8 and 9 are tables that define a selection rule for a resource allocation table to be applied to PUSCH time domain resource allocation. The terminal device 1 may determine / select whether to use the table shown in FIG. 8 or the table shown in FIG. 9 for PUSCH time domain resource allocation based on a higher layer parameter, DCI, and / or RNTI. For example, if the higher layer parameter pusch-tdra-r16 is set, the terminal device 1 may determine / select a resource allocation table to be applied to PUSCH time domain resource allocation using the table shown in FIG. 9, and if the higher layer parameter pusch-tdra-r16 is not set, the terminal device 1 may determine / select a resource allocation table to be applied to PUSCH time domain resource allocation using the table shown in FIG. 8. However, the tables in FIG. 8 and FIG. 9 may be combined into one table. The terminal device 1 may determine / select a resource allocation table to be applied to PUSCH time domain resource allocation based on the RNTI, the PDCCH search space, the presence or absence of a predetermined higher layer parameter pusch-TimeDomainAllocationList or pusch-TimeDomainAllocationList2, and / or the setting or absence of the higher layer parameter pusch-tdra-r16. The resource allocation table includes one or more PUSCH time domain resource allocation configurations. In this embodiment, the resource allocation table is classified into (I) predefined resource allocation table and (II) resource allocation table configured from higher layer RRC signaling. The predefined resource allocation table is defined as a default PUSCH time domain resource allocation A and / or a default PUDSCH time domain resource allocation B. Hereinafter, the default PUSCH time domain resource allocation A is referred to as PUSCH default table A, and the default PUSCH time domain resource allocation B is referred to as PUSCH default table B.

[0144] FIG. 10 is a diagram showing an example of a PUSCH default table A for a normal cyclic prefix (NCP). In FIG. 10, the number of rows in the PUSCH default table A is 16, and each row indicates a configuration of PUSCH time domain resource allocation. In FIG. 10, the indexed rows define a PUSCH mapping type, a slot offset K2 between a PDCCH including DCI and its PUSCH, a starting symbol S of a PUSCH in a slot, and a number of consecutively allocated symbols L. FIG. 11 is a diagram showing an example of a PUSCH default table B for an NCP. In FIG. 11, the number of rows in the PUDSCH default table B is 16, and each row indicates a configuration of PUSCH time domain resource allocation. In FIG. 11, the indexed rows define a slot offset K2 between a PDCCH including DCI and its PUSCH, a starting symbol S of a PUSCH in a slot, a number of consecutively allocated symbols L, and / or a number of repeated transmissions Rep of a PUSCH. However, the number of rows of the PUSCH default table A and / or the PUSCH default table B may not be 16. For example, the number of rows of the PUSCH default table A and the PUSCH default table B may be different values. That is, the terminal device 1 may use a PUSCH default table with a different number of rows depending on the setting of the higher layer parameter, the information included in the DCI field, and / or the RNTI. For example, the terminal device 1 may use a PUSCH default table with a different number of rows depending on the number of bits constituting the field of the time domain resource allocation indicated by the DCI. However, the columns constituting the PUSCH default table A and the columns constituting the PUSCH default table B may be different. For example, any of the indexed row, PUSCH mapping type, offset K2, start symbol S, and number of symbols L indicated in the PUSCH default table A may not be indicated in the PUSCH default table B, and conversely, the other columns may be indicated only in the PUSCH default table B.

[0145] The slot offset K2 will be explained below.

[0146] As mentioned above, for subcarrier spacing setting μ, slots are numbered from 0 to N^{subframe,μ}_{slot}-1 in ascending order within a subframe and from 0 to N^{frame,μ}_{slot}-1 in ascending order within a frame. K2 is the number of slots based on the subcarrier spacing of the PUSCH. K2 can take values ​​from 0 to 32. In a subframe or frame, slots are numbered from 0 in ascending order. Slot number n for a subcarrier spacing setting of 15 kHz corresponds to slot numbers 2n and 2n+1 for a subcarrier spacing setting of 30 kHz.

[0147] When the terminal device 1 detects DCI that schedules a PUSCH, the slot allocated to the PUSCH is floor(n*2 μPUSCH / 2 μPDCCH )+K2. The function floor(A) outputs the largest integer not greater than A. n is the slot in which the PDCCH that schedules the PUSCH is found. μ PUSCH is the subcarrier spacing setting for PUSCH. PDCCH is the subcarrier spacing setting for the PDCCH.

[0148] The resource allocation table configured from the higher layer RRC signal may be provided by the higher layer signal pusch-TimeDomainAllocationList. The information element PUSCH-TimeDomainResourceAllocation indicates the configuration of PUSCH time domain resource allocation. PUSCH-TimeDomainResourceAllocation may be used to configure 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 including one or more elements (information elements). One information element PUSCH-TimeDomainResourceAllocation may also be referred to as one entry (or one row). FIG. 12 is a diagram showing an example of a parameter configuration of PUSCH-TimeDomainResourceAllocation, i.e., each entry. Each entry may be defined by k2, mappingType, and startSymbolAndLength. k2 indicates the slot offset between the PDCCH including DCI and its scheduled PUSCH. If PUSCH-TimeDomainResourceAllocation does not indicate k2, the terminal device 1 may assume that the value of k2 is a predetermined value according to the subcarrier spacing used for transmitting the PUSCH. For example, the terminal device 1 may assume that the value of k2 is 1 when the subcarrier spacing of the PUSCH is 15 kHz or 30 kHz, assume that the value of k2 is 2 when the subcarrier spacing of the PUSCH is 60 kHz, and assume that the value of k2 is 3 when the subcarrier spacing of the PUSCH is 120 kHz. The mappingType indicates either PUSCH mapping type A or PUSCH mapping type B.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 may be referred to as a start and length indicator SLIV. That is, unlike a default table that directly defines the start symbol S and consecutive symbols L, the start symbol S and consecutive symbols L are given based on the SLIV. The base station device 3 can set the value of SLIV so that the time domain resource allocation of the PUSCH does not cross a slot boundary.

[0149] FIG. 13 is a diagram showing an example of calculating the SLIV.

[0150] In Fig. 13, 14 is the number of symbols contained in one slot. Fig. 13 shows an example of calculating SLIV in the case of NCP (Normal Cyclic Prefix). The value of SLIV is calculated based on the number of symbols contained in the 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 ECP, the values ​​7 and 14 in Fig. 13 are replaced by 6 and 12.

[0151] The resource allocation table set from the higher layer RRC signal may be provided by the higher layer signal pusch-TimeDomainAllocationList2. pusch-TimeDomainAllocationList2 may be a parameter different from pusch-TimeDomainAllocationList. The information element PUSCH-TimeDomainResourceAllocation2 indicates the setting of PUSCH time domain resource allocation. PUSCH-TimeDomainResourceAllocation2 may be used to set the time domain relationship between PDCCH including DCI and PUSCH. pusch-TimeDomainAllocationList2 includes one or more information elements PUSCH-TimeDomainResourceAllocation2. That is, pusch-TimeDomainAllocationList2 is a list including one or more elements (information elements). One information element PUSCH-TimeDomainResourceAllocation2 may also be referred to as one entry (or one row).

[0152] FIG. 14 is a diagram showing an example of a parameter configuration of PUSCH-TimeDomainResourceAllocation2, that is, each entry. Each entry may be defined by k2, mappingType, startSymbol, length, and / or repetition. However, PUSCH-TimeDomainResourceAllocation2 may include a parameter mappingType indicating a mapping type. k2 indicates a slot offset between a PDCCH including DCI and its scheduled PUSCH. If k2 is not provided in PUSCH-TimeDomainResourceAllocation2 (not present / absent), the terminal device 1 may assume that the value of k2 is a predetermined value according to the subcarrier spacing used for transmitting PUSCH. For example, when the subcarrier spacing of PUSCH is 15 kHz or 30 kHz, the value of k2 may be assumed to be 1, when the subcarrier spacing of PUSCH is 60 kHz, the value of k2 may be assumed to be 2, and when the subcarrier spacing of PUSCH is 120 kHz, the value of k2 may be assumed to be 3. mappingType indicates a PUSCH mapping type. For example, mappingType indicates either PUSCH mapping type A or PUSCH mapping type B. startSymbol indicates the start symbol S of PUSCH. For example, startSymbol indicates any integer from 0 to 13. length indicates the length of one PUSCH, that is, the number of symbols L that are continuously allocated. For example, L indicates any one of a plurality of integer values. However, L indicated by length may be a nominal length (number of symbols) to which PUSCH is virtually continuously allocated regardless of whether a symbol is available or not, and the value of L may differ from the symbol actually used for transmitting PUSCH. However, L indicated by length may be the number of symbols to which PUSCH is continuously allocated for available uplink symbols. repetition indicates the number of repeated transmissions Rep of PUSCH.For example, repetition may indicate any one of integers from 2 to 8. However, Rep indicated by repetition may be the nominal number of repetitions of PUSCH, and the actual number of repetitions of PUSCH and the value of Rep may differ. However, when repetition is not provided in PUSCH-Time Domain Resource Allocation 2 (not present / absent), the terminal device 1 may assume that the value of repetition is 1 (the number of repetitive transmissions of PUSCH is 1). However, when repetition is not provided in PUSCH-Time Domain Resource Allocation 2, the terminal device 1 may select / determine the number of repetitive transmissions based on the value of the upper layer parameter repetitionCommon. However, the upper layer parameter repetitionCommon indicates the number of repetitive transmissions of PUSCH used commonly for all entries. However, when repetition is not provided in PUSCH-TimeDomainResourceAllocation2 and the higher layer parameter repetitionCommon is not provided / set, the terminal device 1 may assume that the value of repetition is 1 (the number of repeated transmissions of PUSCH is 1). However, the values ​​of startSymbol, length and / or repetition may be given by one parameter using joint coding. For example, a parameter may be used that has as candidates values ​​excluding combinations of startSymbol, length and / or repetition that are not used.

[0153] The resource allocation table set from the higher layer RRC signal may be provided by the higher layer signal pusch-TimeDomainAllocationList3. pusch-TimeDomainAllocationList3 may be a parameter different from pusch-TimeDomainAllocationList and pusch-TimeDomainAllocationList2. The information element PUSCH-TimeDomainResourceAllocation3 indicates the setting of PUSCH time domain resource allocation. PUSCH-TimeDomainResourceAllocation3 may be used to set the time domain relationship between PDCCH including DCI and PUSCH. pusch-TimeDomainAllocationList3 includes one or more information elements PUSCH-TimeDomainResourceAllocation3. That is, pusch-TimeDomainAllocationList3 is a list including one or more elements (information elements). One information element PUSCH-TimeDomainResourceAllocation3 may also be referred to as one entry (or one row).

[0154] FIG. 15 is a diagram showing an example of a parameter configuration of PUSCH-TimeDomainResourceAllocation3, that is, each entry. Each entry is configured with a PUSCH-TDRAperRep whose number of elements is any one from 1 to maxNrofReps, and each PUSCH-TDRAperRep may be defined by k2 and / or startSymbolAndLength. k2 indicates a slot offset between a PDCCH including DCI and its scheduled PUSCH. If k2 is not provided in PUSCH-TDRAperRep (not present / absent), the terminal device 1 may assume that the value of k2 is a predetermined value according to the subcarrier spacing used for transmitting the PUSCH. For example, when the subcarrier spacing of the PUSCH is 15 kHz or 30 kHz, the value of k2 may be assumed to be 1, when the subcarrier spacing of the PUSCH is 60 kHz, the value of k2 may be assumed to be 2, and when the subcarrier spacing of the PUSCH is 120 kHz, the value of k2 may be assumed to be 3. startSymbolAndLength is an index that gives a valid combination of the start symbol S of the PUSCH and the number of consecutive symbols L that are allocated. startSymbolAndLength may be referred to as a start and length indicator SLIV. That is, unlike a default table that directly defines the start symbol S and consecutive symbols L, the start symbol S and consecutive symbols L are given based on the SLIV. The base station device 3 can set the value of the SLIV so that the time domain resource allocation of the PUSCH does not cross the slot boundary. The value of the SLIV is calculated based on the number of symbols included in the slot, the start symbol S, and the number of consecutive symbols L, as in the formula in FIG. 13.

[0155] The higher layer signals pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationList2, and / or pusch-TimeDomainAllocationList3 may be included in the cell-specific RRC parameter pusch-ConfigCommon and / or the terminal device 1 (UE)-specific RRC parameter pusch-Config. pusch-ConfigCommon is used to configure cell-specific parameters for the PUSCH for a certain BWP. pusch-Config is used to configure terminal device 1 (UE)-specific parameters for the PUSCH for a certain BWP. However, the terminal device 1 may determine / specify whether the resource allocation table used for time domain resource allocation of the PUSCH is given by pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationList2, or pusch-TimeDomainAllocationList3 based on the higher layer parameters, DCI, and / or RNTI. However, the terminal device 1 may determine / specify whether each entry in pusch-TimeDomainAllocationList, pusch-TimeDomainAllocationList2, or pusch-TimeDomainAllocationList3 is provided in PUSCH-TimeDomainResourceAllocation, PUSCH-TimeDomainResourceAllocation2, or pusch-TimeDomainAllocation3 based on higher layer parameters, DCI and / or RNTI.

[0156] The terminal device 1 detects DCI that schedules a PUSCH. The slot in which the PUSCH is transmitted is floor(n*2 μPUSCH / 2 μPDCCH )+K2, where n is the slot in which the PDCCH that schedules the PUSCH is detected. PUSCHis the subcarrier spacing setting for PUSCH. PDCCH is the subcarrier spacing setting for the PDCCH.

[0157] In Figures 10 and 11, the value of K2 is any of j, j+1, j+2, or j+3. The value of j is a value specified for the subcarrier spacing of the PUSCH. For example, when the subcarrier spacing to which the PUSCH is applied is 15 kHz or 30 kHz, the value of j may be 1 slot. For example, when the subcarrier spacing to which the PUSCH is applied is 60 kHz, the value of j may be 2 slots. For example, when the subcarrier spacing to which the PUSCH is applied is 120 kHz, the value of j may be 3 slots.

[0158] As mentioned above, the terminal device 1 may determine / specify which resource allocation table to apply to the PUSCH time domain resource allocation based on a table such as that shown in FIG.

[0159] As an example A, the terminal device 1 may determine / specify a resource allocation table to be applied to the PUSCH scheduled by the RAR UL grant. When pusch-ConfigCommon for the terminal device 1 includes pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify a resource allocation table set from an RRC signal of a higher layer. The resource allocation table is given by pusch-TimeDomainAllocationList2 included in pusch-ConfigCommon. Also, when pusch-ConfigCommon for the terminal device 1 does not include pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify a PUSCH default table B. That is, the terminal device 1 may apply the default table B indicating the setting of the PUSCH time domain resource allocation to the determination / specification of the PUSCH time domain resource allocation.

[0160] As an example B, the terminal device 1 may detect DCI in any common search space associated with CORESET#0. The detected DCI is added with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, TC-RNTI, or CS-RNTI. Then, the terminal device 1 may determine / specify a resource allocation table to be applied to the PUSCH scheduled by the DCI. If pusch-ConfigCommon includes pusch-TimeDomainAllocationList2 for the terminal device 1, the terminal device 1 may determine / specify the resource allocation table to be applied to the PUSCH time domain resource allocation to the resource allocation table provided by pusch-TimeDomainAllocationList2 provided in pusch-ConfigCommon. Also, if pusch-ConfigCommon does not include pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify the resource allocation table to be applied to the PUSCH time domain resource allocation to the PUSCH default table B.

[0161] As an example C, the terminal device 1 may detect DCI in (I) any common search space associated with CORESET#0 or (II) a UE-specific search space. The detected DCI is added with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, TC-RNTI, or CS-RNTI. Then, the terminal device 1 may determine / specify a resource allocation table to be applied to a PUSCH scheduled by the DCI. If the pusch-Config for the terminal device 1 includes pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify a resource allocation table to be applied to a PUSCH time domain resource allocation to a resource allocation table provided from the pusch-TimeDomainAllocationList2 provided in the pusch-Config. That is, when pusch-Config includes pusch-TimeDomainAllocationList2, the terminal device 1 may use pusch-TimeDomainAllocationList2 provided by pusch-Config to determine / specify PUSCH time domain resource allocation, regardless of whether pusch-ConfigCommon includes pusch-TimeDomainAllocationList2. Also, when pusch-Config does not include pusch-TimeDomainAllocationList2 and pusch-ConfigCommon includes pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify the resource allocation table to be applied to PUSCH time domain resource allocation to the resource allocation table provided by pusch-TimeDomainAllocationList2 provided by pusch-ConfigCommon. That is, the terminal device 1 uses pusch-TimeDomainAllocationList2 provided by pusch-ConfigCommon to determine / specify PUSCH time domain resource allocation.In addition, if pusch-Config does not include pusch-TimeDomainAllocationList2 and pusch-ConfigCommon does not include pusch-TimeDomainAllocationList2, the terminal device 1 may determine / specify the PUSCH default table B as the resource allocation table to be applied to PUSCH time domain resource allocation.

[0162] The terminal device 1 may select one PUSCH time domain resource allocation configuration in the determined / identified resource allocation table based on a value indicated in a 'Time domain resource assignment' field included in the DCI that schedules the PUSCH. For example, when the resource allocation table applied to the PUSCH time domain resource allocation is the PUSCH default table A (or the PUSCH default table B), the value m indicated in the 'Time domain resource assignment' field may indicate row index m+1 of the PUSCH default table A (or the PUSCH default table B). At this time, the PUSCH time domain resource allocation is the time domain resource allocation configuration indicated from row index m+1. The terminal device 1 transmits the PUSCH assuming the time domain resource allocation configuration indicated from row index m+1. For example, when the value m indicated in the 'Time domain resource assignment' field is 0, the terminal device 1 identifies the time direction resource allocation of the PUSCH scheduled by the DCI using the PUSCH time domain resource allocation configuration of row index 1 of the PUSCH default table A (or the PUSCH default table B).

[0163] Also, when the resource allocation table applied to the PUSCH time domain resource allocation is a resource allocation table given by pusch-TimeDomainAllocationList, the value m indicated in the 'Time domain resource assignment' field corresponds to the (m+1)th element (entry, row) in the list pusch-TimeDomainAllocationList. For example, when the value m indicated in the 'Time domain resource assignment' field is 0, the terminal device 1 may refer to the first element (entry) in the list pusch-TimeDomainAllocationList. For example, when the value m indicated in the 'Time domain resource assignment' field is 1, the terminal device 1 may refer to the second element (entry) in the list pusch-TimeDomainAllocationList.

[0164] Furthermore, when the resource allocation table applied to the PDSCH time domain resource allocation is a resource allocation table given by pusch-TimeDomainAllocationList2, the value m indicated in the 'Time domain resource assignment' field corresponds to the (m+1)th element (entry, row) in the list pusch-TimeDomainAllocationList2. For example, when the value m indicated in the 'Time domain resource assignment' field is 0, the terminal device 1 may refer to the first element (entry) in the list pusch-TimeDomainAllocationList2. For example, when the value m indicated in the 'Time domain resource assignment' field is 1, the terminal device 1 may refer to the second element (entry) in the list pusch-TimeDomainAllocationList2.

[0165] The number of bits (size) of the 'Time domain resource assignment' field included in the DCI will be described below.

[0166] The terminal device 1 may transmit a corresponding PUSCH by detecting a PDCCH including DCI format 0_0, DCI format 0_1, or DCI format 0_2. The number of bits of the 'Time domain resource assignment' field included in DCI format 0_0 may be a fixed number of bits. For example, this fixed number of bits may be 6. That is, the size of the 'Time domain resource assignment' field included in DCI format 0_0 is 6 bits. Also, the size of the 'Time domain resource assignment' field included in DCI format 0_1 ​​or DCI format 0_2 may be a variable number of bits. For example, the number of bits of the 'Time domain resource assignment' field included in DCI format 0_1 ​​or DCI format 0_2 may be any one of 0, 1, 2, 3, 4, 5, and 6.

[0167] The following describes how to determine / specify the number of bits in the 'Time domain resource assignment' field included in DCI format 0_1 ​​or DCI format 0_2.

[0168] The number of bits of the 'Time domain resource assignment' field may be given as ceil(log2(I)). When pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) is configured (provided) for terminal device 1, the value of I may be the number of entries contained in pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3). When pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) is not configured (provided) for terminal device 1, the value of I may be the number of rows in PUSCH default table A (or PUSCH default table B). In other words, when pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) is configured for terminal device 1, the number of bits of the 'Time domain resource assignment' field may be given based on the number of entries contained in pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3). When pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) is not configured for terminal device 1, the number of bits of the 'Time domain resource assignment' field may be given based on the number of rows of the default table (PUSCH default table A or PUSCH default table B).Specifically, when pusch-Config includes pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3), the value of I may be the number of entries included in pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) provided by pusch-Config. Also, when pusch-Config does not include pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) and pusch-ConfigCommon includes pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3), the value of I may be the number of entries included in pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) provided by pusch-ConfigCommon. In addition, if pusch-Config does not include pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3) and pusch-ConfigCommon does not include pusch-TimeDomainAllocationList (or pusch-TimeDomainAllocationList2, pusch-TimeDomainAllocationList3), the value of I may be the number of rows included in PUSCH default table A (or PUSCH default table B).

[0169] Hereinafter, the repetitive transmission (also referred to as repetition, repetition transmission, or aggregation transmission) of the PUSCH in this embodiment will be described. The repetitive transmission of the PUSCH in this embodiment is a repetitive transmission in which a plurality of PUSCHs are continuously transmitted to one or a plurality of slots by one uplink grant, and is also referred to as mini-slot level repetition or multi-segment transmission. That is, the terminal device 1 may transmit one PUSCH multiple times in the same slot. However, one PUSCH may be a PUSCH generated from one transport block. For example, the repeated transmission of one PUSCH may be a transmission of a plurality of PUSCHs generated by encoding one transport block in accordance with the size of each time resource in a plurality of time resources, in each of the plurality of time resources.

[0170] The terminal device 1 repeatedly transmits the PUSCH in a time resource determined / specified based on the start symbol S of the time domain resource for the PUSCH, the nominal duration (which may be the number of symbols) L of the PUSCH, and / or the number of repeated transmissions Rep given by the higher layer parameters (e.g., the above-mentioned pusch-TimeDomainAllocationList2) notified by the RRC message, and the field of the downlink control information using a predetermined DCI format (e.g., DCI format 0_2) received by the PDCCH (e.g., the above-mentioned Time domain resource assignment field). That is, the terminal device 1 may determine / specify the start symbol, period, and / or number of repeated transmissions of each of the PUSCHs to be repeatedly transmitted from S, L, and / or Rep given by the higher layer parameters notified by the RRC message and the field of the downlink control information received by the PDCCH. However, S, L, and / or Rep may be the nominal start symbol, the nominal duration, and / or the nominal number of repeated transmissions, respectively. For example, S, L, and / or Rep may be different from the start symbol, transmission period, and / or the number of repeated transmissions used for the actual PUSCH transmission. The terminal device 1 may determine / specify the actual start symbol, actual period, and / or actual number of repeated transmissions of each PUSCH to be repeatedly transmitted from the parameters of the time domain resource for PUSCH (start symbol S, nominal period L, and / or nominal number of repetitions Rep) given by the higher layer parameters notified by the RRC message and the field of the downlink control information received by the PDCCH, the slot boundary position, the arrangement of the symbols (uplink symbols and / or flexible symbols) available for transmitting the PUSCH, and / or the time resource arrangement of the downlink signal given by the downlink control information.For example, the arrangement of uplink symbols available for transmitting the PUSCH may be set from higher layer slot format setting information transmitted in an RRC message and / or slot format setting DCI transmitted in a PDCCH. The terminal device 1 may determine / specify the actual start symbol, actual period, and / or actual number of repeated transmissions of each of multiple PUSCHs generated from one transport block based on the resource allocation information indicated in the RRC message and / or DCI, the higher layer slot format setting information transmitted in the RRC message, the slot format setting DCI received in the PDCCH, and / or the time resource arrangement of the downlink signal.

[0171] FIG. 16 is a diagram showing an example of symbols available for transmitting a PUSCH that is set based on higher layer slot format configuration information transmitted in an RRC message according to this embodiment and slot format configuration DCI transmitted in a PDCCH.

[0172] In FIG. 16, for a slot consisting of 14 symbols, the upper layer slot format configuration information indicates that the first 6 symbols are downlink (DL by RRC: semi-static downlink symbols), the next 4 symbols are flexible (Flexible by RRC: semi-static flexible symbols), and the last 4 symbols are uplink (UL by RRC: semi-static uplink symbols). In this case, the terminal device 1 may treat the symbols indicated as downlink in the upper layer slot format configuration information as symbols that cannot be used for arranging time resources for PUSCH (PUSCH resources), and may treat the symbols indicated as flexible or uplink in the upper layer slot format configuration information as symbols that can be used for PUSCH resource arrangement. For example, the symbols indicated as downlink in the upper layer slot format configuration information may be excluded from resources available for PUSCH transmission using the first repetition transmission scheme, and multiple PUSCH resources may be allocated consecutively in time to the symbols indicated as flexible or uplink in the upper layer slot format configuration information. However, the terminal device 1 may postpone and allocate the PUSCH resource allocated to a symbol (e.g., a semi-static downlink symbol) unavailable for arranging the PUSCH resource and the subsequent PUSCH resource to a symbol (e.g., a semi-static uplink symbol or a semi-static flexible symbol) available for arranging the PUSCH resource next to the semi-static downlink symbol after allocating the PUSCH resource to all one or more symbols consecutively in time, regardless of the content of the upper layer slot format setting information. However, the terminal device 1 may drop (cancel) the PUSCH resource allocated to the symbol indicated as downlink in the upper layer slot format setting information after allocating the PUSCH resource to all one or more symbols consecutively in time, regardless of the content of the upper layer slot format setting information.However, "dropping" may mean that the terminal device 1 does not postpone the resource allocated to the symbol and does not use it for transmitting the PUSCH. However, "dropping" may also be called "cancelling" or "not transmitting". However, the terminal device 1 may switch between postponing and allocating the PUSCH resource allocated to the symbol indicated as downlink in the higher layer slot format setting information to the next available symbol (e.g., semi-static uplink symbol or semi-static flexible symbol) after the semi-static downlink symbol, or dropping (canceling) without postponing, depending on the information included in the RRC message received in the higher layer and / or the DCI included in the PDCCH received from the base station device 3.

[0173] However, among the symbols (semi-static flexible symbols) indicated as flexible by the higher layer slot format configuration information, a predetermined symbol may be made unavailable for PUSCH resource allocation. Here, the predetermined symbol may be a symbol notified by the higher layer parameters (RRC parameters) that a downlink signal and / or an uplink signal is to be allocated thereto.

[0174] For example, a symbol (which may be a semi-static flexible symbol) in which an SS / PBCH block is indicated to be arranged by a higher layer parameter (e.g., ssb-PositionsInBurst) may be treated as a symbol unavailable for PUSCH resource arrangement. When a symbol in which an SS / PBCH block indicated by a higher layer parameter is transmitted overlaps / collides with a symbol in which a time domain resource for a PUSCH is arranged, which is given in a field of downlink control information received in a PDCCH, the terminal device 1 may treat the symbol as a symbol unavailable for PUSCH resource arrangement.

[0175] For example, a symbol (which may be a semi-static flexible symbol) in which a type-0 CSS in CORESET#0 is indicated to be arranged by higher layer parameters (e.g., SearchSpace, SearchSpaceZero, ControlResourceSet, and / or ControlResourceSetZero) may be treated as an unavailable symbol for PUSCH resource arrangement. When a symbol in which a type-0 CSS in CORESET#0 indicated by higher layer parameters is arranged overlaps / collides with a symbol in which a time domain resource for PUSCH provided in a field of downlink control information received on PDCCH is arranged, the terminal device 1 may treat the symbol as an unavailable symbol for PUSCH resource arrangement.

[0176] For example, a symbol (which may be a semi-static flexible symbol) in which a higher layer parameter indicates that a PUSCH resource is not to be allocated may be set as a symbol unavailable for PUSCH resource allocation. When a symbol in which a higher layer parameter indicates that a PUSCH resource is not to be allocated and a symbol in which a time domain resource for a PUSCH is allocated, which is given in a field of downlink control information received in a PDCCH, overlap / collide, the terminal device 1 may set the symbol as a symbol unavailable for PUSCH resource allocation. However, the higher layer parameter indicating a symbol in which a PUSCH resource is not allocated may be indicated by a higher layer parameter (for example, rateMatchPatternGroup1, rateMatchPatternGroup2, and / or rateMatchPatternToAddModList) indicating that a PDSCH is not allocated. However, the higher layer parameter indicating a symbol in which a PUSCH resource is not allocated may be bitmap information or index information indicating a symbol number and / or a slot number, or may be information directly indicating a symbol number and / or a slot number.

[0177] The terminal device 1 may treat symbols (which may be semi-static flexible symbols) indicated by upper layer parameters (e.g., rateMatchPatternGroup1, rateMatchPatternGroup2 and / or rateMatchPatternToAddModList) indicating that PDSCH resources are not to be placed as symbols unavailable for PUSCH resource placement, separately from upper layer parameters indicating that PUSCH resources are not to be placed (which may be semi-static flexible symbols).

[0178] The multiple PUSCH resources allocated based on the higher layer slot format setting information may be referred to as multiple provisional PUSCH resources. The multiple provisional PUSCH resources may be determined / specified based on resource allocation information (e.g., S, L, and / or Rep) included in the DCI, the higher layer slot format setting information, and / or other higher layer parameters. The terminal device 1 may determine / specify multiple provisional PUSCH resources based on resource allocation information (e.g., S, L, and / or Rep) included in the DCI, the higher layer slot format setting information, and / or other higher layer parameters.

[0179] The time resource of the PUSCH that the terminal device 1 determines / specifies based on the resource allocation information included in the DCI may be referred to as a nominal time resource. For example, the terminal device 1 may determine L consecutive symbols from the start symbol indicated by S as a nominal time resource of one PUSCH, and may determine Rep×L consecutive symbols as a nominal time resource for repeated transmission of the PUSCH when Rep>1. The terminal device 1 may specify one or more provisional PUSCH resources based on the nominal time resource of the PUSCH, the position of the slot boundary, and / or an RRC parameter given by a higher layer. For example, when the nominal time resource of a certain PUSCH spans a slot boundary, the terminal device 1 may specify a plurality of provisional PUSCH resources obtained by dividing the nominal time resource at the slot boundary. For example, when a nominal time resource of a certain PUSCH is assigned to a symbol indicated as a downlink symbol in the higher layer slot format setting information, the terminal device 1 may identify, as a provisional PUSCH resource, the nominal time resource assigned to the symbol that is postponed to the next available uplink symbol or flexible symbol.

[0180] In FIG. 16, a time resource (temporary PUSCH resource) for PUSCH using the first repetition transmission method is arranged for a symbol indicated as a flexible symbol in the upper layer slot format setting information. When the slot format setting DCI transmitted by the PDCCH indicates that the symbol in which the temporary PUSCH resource is arranged is unavailable for PUSCH transmission, the terminal device 1 drops the allocated temporary PUSCH resource in the symbol. However, "dropping" may mean that the terminal device 1 does not use the symbol for PUSCH transmission. However, "dropping" may also be referred to as "cancelling" or "not transmitting". For example, a symbol indicated as unavailable for PUSCH transmission in the slot format setting DCI may be a symbol set as a downlink symbol in the slot format setting DCI. For example, a symbol indicated as unavailable for PUSCH transmission in the slot format setting DCI may be a symbol set as a downlink symbol or a flexible symbol in the slot format setting DCI. For example, if a certain provisional PUSCH resource includes a symbol indicated as an uplink symbol in the slot format setting DCI and a symbol indicated as a downlink symbol (or a flexible symbol), the terminal device 1 drops the time resource of the symbol indicated as a downlink symbol (or a flexible symbol) from the provisional PUSCH resource, and places and transmits the PUSCH only in the time resource of the symbol indicated as the uplink symbol.

[0181] However, since a specific slot format index (e.g., index 255) is indicated in the slot format setting DCI, when the slot format set in the higher layer slot format setting information is followed, the terminal device 1 may treat the flexible symbol as a symbol available for transmitting the PUSCH.

[0182] However, when the terminal device 1 is set to monitor the slot format configuration DCI by the RRC parameter and does not detect the slot format configuration DCI, the terminal device 1 may drop all the provisional PUSCH resources including the symbol indicated as a flexible symbol in the upper layer slot format configuration information. In other words, when the terminal device 1 cannot detect the slot format configuration DCI set to monitor and a certain provisional PUSCH resource includes both a symbol indicated as a flexible symbol and an uplink symbol in the upper layer slot format configuration information, the terminal device 1 may drop all the provisional PUSCH resources and not transmit PUSCH with the provisional PUSCH resource. In other words, when the terminal device 1 is set to monitor the slot format configuration DCI, the terminal device 1 may determine / specify a plurality of actual PUSCH resources (e.g., the first symbol and the number of symbols) based on the plurality of provisional PUSCH resources (e.g., the first symbol and the number of symbols) and the slot format configuration DCI, when the terminal device 1 does not detect the slot format configuration DCI, determining / specifying the plurality of actual PUSCH resources using information indicated in the upper layer slot format configuration information may include.

[0183] By performing such an operation, the base station apparatus 3 can perform reception processing of a plurality of PUSCHs in a predetermined PUSCH resource without knowing whether the terminal apparatus 1 has detected the slot format setting DCI.

[0184] However, if a certain provisional PUSCH resource allocated by higher layer slot format setting information includes a symbol indicated as an uplink symbol in the slot format setting DCI and a symbol indicated as a downlink symbol (or a flexible symbol), the terminal device 1 may drop all of the provisional PUSCH resources.

[0185] However, when the terminal device 1 is configured to monitor the slot format setting DCI and does not detect the slot format setting DCI, in a certain provisional PUSCH resource allocated by the higher layer slot format setting information, the terminal device 1 may drop only the resources of the symbols indicated as downlink symbols and / or flexible symbols among the provisional PUSCH resources.

[0186] In the multiple provisional PUSCH resources allocated based on the upper layer slot format configuration information, the provisional PUSCH resource that is not dropped by the slot format configuration DCI may be referred to as an actual PUSCH resource. The multiple actual PUSCH resources (e.g., the first symbol and the number of symbols of each of the multiple actual PUSCH resources) may be determined / specified based on the multiple provisional PUSCH resources (e.g., the first symbol and the number of symbols of each of the multiple provisional PUSCH resources) and the slot format configuration DCI. The terminal device 1 may determine / specify the multiple actual PUSCH resources based on the multiple provisional PUSCH resources and the slot format configuration DCI. However, when the terminal device 1 is not configured to monitor the slot format configuration DCI in the PDCCH and / or when the flexible symbol is not configured in the upper layer slot format configuration information, the multiple actual PUSCH resources may be the same as the multiple provisional PUSCH resources.

[0187] When the terminal device 1 is not configured to monitor the slot format configuration DCI on the PDCCH, the terminal device 1 may use the provisional PUSCH resource allocated to the symbol indicated as a flexible symbol by the higher layer slot format configuration information as the actual PUSCH resource.

[0188] However, when the terminal device 1 detects a DCI format that allocates a downlink signal (for example, PDSCH or CSI-RS) to a flexible symbol to which a provisional PUSCH resource is allocated, the terminal device 1 may drop a part or all of the provisional PUSCH resources including the symbol to which the downlink signal is allocated. FIG. 17 is a diagram showing an example of dropping a PUSCH in repeated transmission of a PUSCH according to an embodiment of the present invention. More specifically, it is a diagram showing an example of dropping a provisional PUSCH resource including a symbol to which a downlink signal is allocated among the provisional PUSCH resources allocated to a symbol indicated as a flexible symbol by the higher layer slot format configuration information. Each of (a), (b), and (c) of FIG. 17 shows a case in which all symbols are indicated as flexible symbols (Flexible by RRC: semi-static flexible symbols) in the higher layer slot format configuration information for two certain slots, and a downlink signal (DL signal by DCI) (which may be a downlink signal scheduled by a dynamic grant) is allocated by DCI to the 9th to 12th four symbols of the first slot. Also, in each of (a), (b), and (c) of FIG. 17, S=2, L=4, and Rep=4 are indicated in the DCI, and a 4-symbol provisional PUSCH resource is repeatedly allocated 4 times from the third symbol of the first slot. In this case, the terminal device 1 may drop (cancel) all provisional PUSCH resources (the second and third provisional PUSCH resources) that collide with the downlink signal resources as shown in FIG. 17(a). As another example, the terminal device 1 may drop the colliding symbol resources (the third and fourth symbols of the second provisional PUSCH resource and the first and second symbols of the third provisional PUSCH resource) in the provisional PUSCH resources that collide with the downlink signal resources as shown in FIG. 17(b).By using such a dropping method, flexible scheduling with high time resource utilization efficiency can be used when the transmission of PUSCH, which uses many symbols by repeated transmission, and the reception of downlink signals are mixed. As another embodiment, the terminal device 1 may drop the resource of the colliding symbol in the temporary PUSCH resource that collide with the resource of the downlink signal, as shown in FIG. 17(c), and further drop a predetermined number of symbols (one symbol (the third symbol of the third temporary PUSCH resource) in FIG. 17(c)) immediately after the resource to which the downlink signal is assigned as a guard symbol. By securing a guard symbol between the symbol for receiving the downlink signal and the symbol for transmitting the PUSCH in this way, the terminal device 1 can secure the time to switch from the downlink to the uplink, and suppress interference between the downlink and uplink signals. However, the number of guard symbols may be a fixed value. However, the number of guard symbols may be based on the subcarrier interval. However, the terminal device 1 may set / specify / determine the number of guard symbols based on a signal (for example, an RRC parameter, downlink control information, and / or a random access response) notified from the base station device 3.

[0189] The terminal device 1 detects a DCI format (e.g., DCI format 0_2) including uplink allocation information instructing to repeatedly transmit a certain transport block on multiple PUSCHs, detects a DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) including downlink allocation information instructing to receive a downlink signal, and, when at least one symbol conflicts between one or more of the multiple virtual PUSCH resources identified from the uplink allocation information and the downlink time resource identified from the downlink allocation information, drops the virtual PUSCH resource including the conflicting symbol.

[0190] The terminal device 1 detects a DCI format (e.g., DCI format 0_2) including uplink allocation information instructing to repeatedly transmit a certain transport block on multiple PUSCHs, detects a DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) including downlink allocation information instructing to receive a downlink signal, and when at least one symbol conflicts in one or more of the multiple virtual PUSCH resources identified from the uplink allocation information and the downlink time resource identified from the downlink allocation information, the terminal device 1 may drop only the resource of the colliding symbol among the virtual PUSCH resources including the colliding symbol.

[0191] The terminal device 1 detects a DCI format (e.g., DCI format 0_2) including uplink allocation information instructing to repeatedly transmit a certain transport block on multiple PUSCHs, detects a DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) including downlink allocation information instructing to receive a downlink signal, and when at least one symbol collide between one or more of a plurality of temporary PUSCH resources identified from the uplink allocation information and a downlink time resource identified from the downlink allocation information and / or when the gap in the number of symbols between one of the plurality of temporary PUSCH resources and the downlink time resource is smaller than a specified number of guard symbols, drops the resource of the colliding symbol and a predetermined number of symbols (guard symbols) immediately following it among the temporary PUSCH resources including the colliding symbol.

[0192] The terminal device 1 detects a DCI format (e.g., DCI format 0_2) including uplink allocation information instructing to repeatedly transmit a certain transport block on multiple PUSCHs, detects a DCI format (e.g., DCI format 1_0, DCI format 1_1, or DCI format 0_1) including downlink allocation information instructing to receive a downlink signal, and when at least one symbol conflicts between one or more of a plurality of temporary PUSCH resources identified from the uplink allocation information and a downlink time resource identified from the downlink allocation information and / or when the gap in the number of symbols between one of the plurality of temporary PUSCH resources and the downlink time resource is less than a specified number of guard symbols, the terminal device 1 may drop the temporary PUSCH resource including the symbol colliding with the downlink time resource and the downlink time resource and the gap in the number of symbols between the temporary PUSCH resource is less than a specified number of guard symbols.

[0193] The repeat transmission of PUSCH includes a case where the base station device 3 indicates a time resource for repeat transmission by DCI to the terminal device 1 that has transmitted a scheduling request (SR) (also referred to as PUSCH transmission scheduled by a dynamic grant or DG PUSCH transmission), and a case where the base station device 3 periodically sets a plurality of time resources for repeat transmission in advance, and the terminal device 1 performs repeat transmission of PUSCH using one of the plurality of time resources for repeat transmission without transmitting an SR (also referred to as PUSCH transmission set by a configured grant or CG PUSCH). The dropping of the temporary PUSCH resource may be applied only when the temporary PUSCH resource is set by a configured grant. However, the same dropping method may be applied both when the temporary PUSCH resource is set by a configured grant and when it is set by a dynamic grant. However, different dropping methods may be applied when the temporary PUSCH resource is set by a configured grant and when it is set by a dynamic grant.

[0194] In repeat transmission of PUSCH using the first repeat transmission scheme according to this embodiment, the total number of symbols of multiple virtual PUSCH resources may be equal to L*Rep, which is the power of L and Rep indicated in the resource allocation information included in DCI. In repeat transmission of PUSCH using the first repeat transmission scheme according to this embodiment, the total number of symbols of multiple actual PUSCH resources is equal to or less than L*Rep, which is the power of L and Rep indicated in the resource allocation information included in DCI.

[0195] Fig. 18 is a diagram showing an example of time resource allocation of PUSCH in repeated transmission of PUSCH according to this embodiment. Fig. 18 shows an example of PUSCH allocation when S=6, L=4, and Rep=4 are indicated by DCI including resource allocation (RA) information, and Fig. 18(a), (b), and (c) show three examples in which different slot formats are notified.

[0196] 18(a) is a diagram showing an example in which all symbols in two slots are set as uplink symbols (UL by RRC) by the upper layer slot format setting information. In this case, since all symbols in two slots are available for PUSCH, the terminal device 1 transmits PUSCH four times in succession, with the first PUSCH resource being a time resource whose start symbol is the seventh symbol period of the first slot and whose duration is four symbols, the second PUSCH resource being a time resource whose start symbol is the eleventh symbol of the first slot and whose duration is four symbols, the third PUSCH resource being a time resource whose start symbol is the first symbol of the second slot and whose duration is four symbols, and the fourth PUSCH resource being a time resource whose start symbol is the fifth symbol of the second slot and whose duration is four symbols.

[0197] FIG. 18(b) is a diagram showing an example in which up to the sixth symbol in both the first and second slots are set as downlink symbols (DL by RRC) by the upper layer slot format setting information, and the remaining symbols are set as uplink symbols (UL by RRC). In this case, since the last eight symbols of each slot are available for PUSCH, the terminal device 1 sets the first PUSCH resource as a time resource with a start symbol of the seventh symbol period of the first slot and a four-symbol period, the second PUSCH resource as a time resource with a start symbol of the eleventh symbol of the first slot and a four-symbol period, the third PUSCH resource as a time resource with a start symbol of the seventh symbol of the second slot and a four-symbol period, and the fourth PUSCH resource as a time resource with a start symbol of the eleventh symbol of the second slot and a four-symbol period, and transmits PUSCH four times. However, the terminal device 1 may set several symbols immediately after the symbol receiving the downlink signal as symbols that cannot be assigned as guard symbols even if they are indicated as uplink by the upper layer slot format setting information. For example, when receiving higher layer slot format configuration information similar to that of FIG. 18(b) and receiving a downlink signal from the first symbol to the sixth symbol of the first slot, the seventh symbol, which is an uplink symbol, may be used as a guard symbol and PUSCH resources may be allocated from the eighth symbol. However, for the guard symbol, the PUSCH resource may be allocated and then the PUSCH resource of the guard symbol may be dropped. However, the number of guard symbols may be a fixed value. However, the number of guard symbols may be based on the subcarrier spacing. However, the terminal device 1 may set / specify / determine the number of guard symbols based on a signal (for example, an RRC parameter, downlink control information, and / or a random access response) notified from the base station device 3.

[0198] FIG. 18(c) shows a case where all symbols in two slots are set as flexible symbols (Flexible by RRC) by the higher layer slot format setting information, and the slot format setting DCI sets up to the sixth symbol in both the first and second slots as downlink symbols (DL by DCI), and the remaining symbols as uplink symbols (UL by DCI). In this case, since all symbols in two slots are available for PUSCH arrangement, the terminal device 1 allocates PUSCH resources (temporary PUSCH resources) in the same manner as in the case of FIG. 18(a). However, since the PUSCH resources of the symbols indicated as downlink symbols in the slot format setting DCI are dropped, the terminal device 1 drops all of the third PUSCH resources and the first two symbols of the fourth PUSCH resource. Therefore, the terminal device 1 transmits PUSCH three times with three actual PUSCH resources, with the first PUSCH resource (actual PUSCH resource) being a time resource with a start symbol of the seventh symbol of the first slot and a period of four symbols, the second PUSCH resource (actual PUSCH resource) being a time resource with a start symbol of the eleventh symbol of the first slot and a period of four symbols, and the third PUSCH resource (actual PUSCH resource) being a time resource with a start symbol of the seventh symbol of the second slot and a period of two symbols. However, the terminal device 1 may drop the PUSCH resource as a guard symbol for several symbols immediately after the symbol receiving the downlink signal, even if the symbols are indicated as uplink by the upper layer slot format setting information. For example, when receiving the same upper layer slot format setting information and slot format setting DCI as in FIG. 18(c) and receiving the downlink signal with the first symbol to the sixth symbol of the first slot, the seventh symbol, which is an uplink symbol, may be used as a guard symbol and the PUSCH resource allocated to the symbol may be dropped. However, the number of guard symbols may be a fixed value. However, the number of guard symbols may be based on the subcarrier spacing.However, the terminal device 1 may set / specify / determine the number of guard symbols based on a signal notified from the base station device 3 (for example, an RRC parameter, downlink control information, and / or a random access response).

[0199] When the terminal device 1 determines / sets a certain PUSCH resource for a certain slot based on the upper layer slot format setting information and S, L and Rep given in the RA information, if the number of consecutive uplink symbols and / or flexible symbols available in the slot due to a slot boundary or downlink symbol is less than L symbols, the terminal device 1 may segment the PUSCH resource and transmit multiple PUSCHs as multiple PUSCH resources.

[0200] 19 shows an example of segmentation of PUSCH according to the present embodiment, in which all two slots are symbols to which PUSCH can be assigned (uplink symbols or flexible symbols), S=8, L=4, and Rep=4. In this case, the parameters are set to repeat a four-symbol PUSCH four times from the ninth symbol in the slot, but since the second PUSCH resource of the repeated transmission crosses a slot boundary, it is segmented into two two-symbol PUSCHs. As a result, the terminal device 1 transmits a four-symbol or two-symbol PUSCH five times without each PUSCH crossing a slot boundary.

[0201] FIG. 20 shows, as another example, a case where in a certain slot, the first to third symbols and the sixth to eighth symbols are set as symbols unavailable for PUSCH transmission (e.g., downlink symbols and / or several symbols immediately following the downlink symbols (guard symbols)) according to the upper layer slot format setting information, and the remaining symbols are set as symbols available for PUSCH transmission (e.g., uplink symbols excluding guard symbols or flexible symbols). In this case, the PUSCH resource is allocated starting from the fourth symbol. However, since the number of symbols available for PUSCH continuously from the fourth symbol is 2 (<L = 4), the first PUSCH resource is segmented. As a result, the first PUSCH resource has a start symbol of the fourth symbol and a period of 2, the second PUSCH resource has a start symbol of the ninth symbol and a period of 2, and the third PUSCH resource has a start symbol of the eleventh symbol and a period of 4. The terminal device 1 transmits PUSCH three times.

[0202] That is, Rep notified by the higher layer parameters and the number of repetitions of PUSCH that are actually transmitted may differ. That is, L notified by the higher layer parameters and the number of symbols of PUSCH that are actually transmitted may differ. For example, the terminal device 1 may determine / specify the actual number of repetitions of PUSCH from Rep and the number of segments of each PUSCH and / or the number of dropped PUSCH resources. For example, when Rep (nominal number of repetitions) indicated in the RRC message and / or DCI is 1, if the time domain resource of PUSCH determined / specified by S and L spans a slot boundary or if some of the symbols are unavailable for transmitting PUSCH, the terminal device 1 may repeatedly transmit PUSCH in a time domain resource segmented into multiple pieces. More specifically, when one slot is 14 symbols and S=8, L=14, and Rep=1 are notified, the terminal device 1 may transmit one PUSCH using 6 symbols from symbol numbers 8 to 13 in the first slot, and transmit one PUSCH using 8 symbols from symbol numbers 0 to 7 in the second slot. In this case, the terminal device 1 repeats transmission of the PUSCH twice using the time domain resource of symbols from symbol numbers 8 to 6 in the first slot and the time domain resource of symbols from symbol numbers 0 to 8 in the second slot.

[0203] However, when a time domain resource of L×Rep symbols indicated by S, L, and Rep crosses a slot boundary or is partially DL symbols, the terminal device 1 may segment the time domain resource and transmit one PUSCH for each group of consecutive available uplink symbols in the slot. In other words, when a time domain resource of L×Rep symbols indicated by S, L, and Rep crosses a slot boundary or is partially DL symbols, the terminal device 1 does not need to transmit multiple PUSCHs in consecutive available uplink symbol groups in the slot.

[0204] In this way, the terminal device 1 according to this embodiment determines / specifies the first symbol and period of multiple provisional PUSCH resources based on DCI including uplink RA information and higher layer slot format setting information. Furthermore, when the terminal device 1 is set to monitor the slot format setting DCI in the PDCCH, the terminal device 1 determines / specifies the first symbol and period of each of multiple PUSCH resources (which may be referred to as actual PUSCH resources) based on the first symbol and period of the multiple provisional PUSCH resources and the slot format setting DCI. Furthermore, when the terminal device 1 is not set to monitor the slot format setting DCI in the PDCCH, the terminal device 1 determines / specifies the first symbol and period of each of multiple actual PUSCH resources based on the first symbol and period of the multiple provisional PUSCH resources. The terminal device 1 receives DCI including downlink RA information, and when a time resource of a downlink signal indicated by the downlink RA information collides with at least one symbol of the plurality of tentative PUSCH resources, determines / specifies the leading symbol and period of each of the plurality of actual PUSCH resources based on the leading symbol and period of the plurality of tentative PUSCH resources and the downlink RA information.Furthermore, the terminal device 1 transmits PUSCH using each of the determined / specified plurality of actual PUSCH resources.

[0205] Moreover, the terminal device 1 according to the present embodiment determines / specifies a plurality of provisional PUSCH resources based on DCI including RA information and upper layer slot format configuration information. Furthermore, when the terminal device 1 is configured to monitor the slot format configuration DCI in the PDCCH and detects the slot format configuration DCI, the terminal device 1 determines / specifies a set of a plurality of consecutive symbols indicated as an uplink symbol by at least one of the upper layer slot format configuration information and the slot format configuration DCI as a plurality of actual PUSCH resources in each of the plurality of PUSCH resources. Furthermore, when the terminal device 1 is configured to monitor the slot format configuration DCI in the PDCCH and does not detect the slot format configuration DCI, the terminal device 1 determines / specifies only a provisional PUSCH resource including only a symbol indicated as an uplink symbol by the upper layer slot format configuration information as an actual PUSCH resource in each of the plurality of provisional PUSCH resources. Furthermore, when the terminal device 1 is not configured to monitor the slot format configuration DCI in the PDCCH, the terminal device 1 determines / specifies a plurality of actual PUSCH resources based on a plurality of provisional PUSCH resources. The terminal device 1 receives DCI including downlink RA information, and when a time resource of a downlink signal indicated by the downlink RA information collides with at least one symbol of the plurality of tentative PUSCH resources, the terminal device 1 determines / specifies a plurality of actual PUSCH resources based on the plurality of tentative PUSCH resources and the downlink RA information. Furthermore, the terminal device 1 transmits a PUSCH using each of the determined / specified plurality of actual PUSCH resources.

[0206] The terminal device 1 according to the embodiment of the present invention may change the symbols available for use in the actual PUSCH resource and / or the symbols that cannot be used, depending on the value of bit field b1 included in information notified from the base station device 3. For example, bit field b1 may be included in DCI (e.g., DCI of DCI format 0_2) including RA information for repeated transmission of PUSCH. For example, bit field b1 may be included in the PDCCH received from the base station device 3. For example, bit field b1 may be included in an RRC message received in a higher layer.

[0207] When the value of bit field b1 is a first value, the terminal device 1 may treat symbols indicated as uplink (semi-static uplink symbols) and symbols indicated as flexible (semi-static flexible symbols) in the upper layer slot format setting information as symbols available for use in actual PUSCH resources, and may treat symbols indicated as downlink (semi-static downlink symbols) as symbols that cannot be used in actual PUSCH resources.

[0208] When the value of bit field b1 is the second value, the terminal device 1 may treat symbols indicated as uplink in the upper layer slot format setting information (semi-static uplink symbols) as symbols available for use in actual PUSCH resources, and may treat symbols indicated as downlink (semi-static downlink symbols) and symbols indicated as flexible (semi-static flexible symbols) as symbols that cannot be used in actual PUSCH resources.

[0209] When the value of the bit field b1 is a third value, the terminal device 1 may set the symbol indicated as uplink in the upper layer slot format setting information (semi-static uplink symbol) and the symbol indicated as uplink in the slot format setting DCI (dynamic uplink symbol) as symbols available for actual PUSCH resources, and may set the symbol indicated as downlink in the upper layer slot format setting information (semi-static downlink symbol), the symbol indicated as flexible in the slot format setting DCI (dynamic flexible symbol), and the symbol indicated as downlink in the slot format setting DCI (dynamic downlink symbol) as symbols unavailable for actual PUSCH resources. However, when the terminal device 1 cannot detect the slot format setting DCI, it may set the symbol indicated as flexible in the upper layer slot format setting information (semi-static flexible symbol) as symbols unavailable for actual PUSCH resources.

[0210] When the value of the bit field b1 is the fourth value, the terminal device 1 may set the symbols indicated as uplink in the upper layer slot format setting information (semi-static uplink symbols), the symbols indicated as uplink in the slot format setting DCI (dynamic uplink symbols), and the symbols indicated as flexible in the slot format setting DCI (dynamic flexible symbols) as symbols available for actual PUSCH resources, and may set the symbols indicated as downlink in the upper layer slot format setting information (semi-static downlink symbols) and the symbols indicated as downlink in the slot format setting DCI (dynamic downlink symbols) as symbols unavailable for actual PUSCH resources. However, when the terminal device 1 cannot detect the slot format setting DCI, it may set the symbols indicated as flexible in the upper layer slot format setting information (semi-static flexible symbols) as symbols unavailable for actual PUSCH resources.

[0211] However, the bit field b1 may be a single bit that indicates one of two of the first to fourth values. For example, bit field b1=0 may be the first value, and bit field b1=1 may be the third value, and the value of bit field b1 (0 or 1) may switch between the operation for the first value and the operation for the third value.

[0212] However, the bit field b1 may be a 2-bit bit field indicating any one of the first to fourth values. For example, the bit field b1=00 is the first value, the bit field b1=01 is the second value, the bit field b1=10 is the third value, and the bit field b1=11 is the fourth value, and the operation for the first to fourth values ​​may be switched depending on the value of the bit field.

[0213] However, the number of bits in the bit field b1 may be two or more, and may be a bit field indicating any of the operations for the first to fourth values ​​or other operations.

[0214] However, the operation indicated by the bit field b1 may be indicated by a combination of the RRC message and the DCI. For example, the number of bits in the bit field b1 included in the DCI may be 1 bit, and the operation indicated by the 1 bit may be set by the RRC message.

[0215] In this embodiment, the terminal device 1 may determine / specify whether to apply repeat transmission to the PUSCH transmission scheduled in the uplink grant, or which of multiple repeat transmission types to apply, based on at least (I) a parameter of a higher layer and / or (II) a field included in the uplink grant. The repeat transmission type may include slot aggregation (hereinafter referred to as second repeat transmission) in which the PUSCH is transmitted once per slot with the same predetermined symbol between slots, in addition to the repeat transmission (hereinafter referred to as first repeat transmission) in which the PUSCH is transmitted with consecutive available uplink symbols in one or multiple consecutive available slots.

[0216] In aspect A of the present embodiment, the base station device 3 may notify the terminal device 1 of which of the first repetitive transmission and the second repetitive transmission is to be set / applied by a parameter of a higher layer. For example, pusch-AggregationFactor may be used to indicate the number of repetitive transmissions of the second repetitive transmission. For example, pusch-AggregationFactor-r16 may be used to indicate the number of repetitions of the first repetitive transmission common between indexes notified in the Time domain resource assignment field of the DCI. For example, repetition may be used to indicate the number of repetitions of the first repetitive transmission of each index notified in the Time domain resource assignment field of the DCI. When pusch-AggregationFactor, pusch-AggregationFactor-r16, and / or repetition are not set in the terminal device 1, the terminal device 1 may assume that the repetitive transmission is not applied and may transmit the PUSCH in which the uplink grant is scheduled once.

[0217] In aspect B of this embodiment, the terminal device 1 may determine / specify which of the first repeated transmission and the second repeated transmission is to be applied, based on a 'Time domain resource assignment' field included in the uplink grant transmitted from the base station device 3. As described above, the 'Time domain resource assignment' field is used to indicate PUSCH time domain resource allocation.

[0218] In aspect C of this embodiment, the base station device 3 may notify the terminal device 1 of which of the first and second repeated transmissions to set by using a parameter of a higher layer. For example, the base station device 3 may set a parameter of a higher layer indicating the number of repeated transmissions for each of the first and second repeated transmissions. For example, pusch-AggregationFactor-r16 and / or repetition may be used to indicate the number of repeated transmissions for the first repeated transmission.

[0219] In addition, in aspect A, aspect B, or aspect C of this embodiment, the terminal device 1 may determine / specify which of the first repeated transmission and the second repeated transmission is to be applied based on a PUSCH mapping type obtained based on a 'Time domain resource assignment' field included in the uplink grant.

[0220] In addition, in aspect A, aspect B, or aspect C of this embodiment, the terminal device 1 may determine / identify whether the first repeated transmission or the second repeated transmission is to be applied based on S, L and / or Rep indicated in the 'Time domain resource assignment' field included in the uplink grant.

[0221] Hereinafter, frequency hopping applied to the uplink in this embodiment will be described.

[0222] A first frequency hopping for scheduled or set PUSCH transmission is configured in the higher layer parameter frequencyHopping in the terminal device 1. In frequencyHopping, one of the following two frequency hopping modes is configured. Intra-slot frequency hopping ·Inter-slot frequency hopping

[0223] Fig. 21 is a diagram showing an example of a first frequency hopping in this embodiment. Fig. 21(a) is an example of PUSCH transmission without frequency hopping. Fig. 21(b) is an example of PUSCH transmission with intra-slot frequency hopping. Fig. 21(c) is an example of PUSCH transmission with inter-slot frequency hopping.

[0224] The second frequency hopping of the scheduled or configured PUSCH transmission is configured in the terminal device 1 by the higher layer parameter frequencyHopping-r16. One of the following three frequency hopping modes may be configured in frequencyHopping-r16. Inter-PUSCH frequency hopping Intra-PUSCH frequency hopping ·Inter-slot frequency hopping

[0225] However, the second frequency hopping configurable in frequencyHopping-r16 may be a part of the above three. For example, the second frequency hopping configurable in frequencyHopping-r16 may be inter-PUSCH frequency hopping and inter-slot frequency hopping.

[0226] Fig. 22 is a diagram showing an example of a second frequency hopping in this embodiment. Fig. 22(a) is an example of PUSCH transmission without frequency hopping. Fig. 22(b) is an example of PUSCH transmission with inter-PUSCH frequency hopping. Fig. 22(c) is an example of PUSCH transmission with intra-PUSCH frequency hopping. Fig. 22(d) is an example of PUSCH transmission with inter-slot frequency hopping.

[0227] In Fig. 21(b), Fig. 22(b), and Fig. 22(c), the PUSCH transmission with frequency hopping in a slot consists of a first hop (first frequency hop, first frequency unit) and a second hop (second frequency hop, second frequency unit) in the slot. However, the frequency hopping in the slot in this embodiment is also applicable to the case where there are three or more hops. That is, in addition to the first and second hops, there may be a third hop, a fourth hop, ... in the slot. The maximum number of hops in a slot may be set by an RRC message or the like.

[0228] However, the frequency hopping modes indicated by frequencyHopping and frequencyHopping-r16 (the frequency hopping modes included in the first frequency hopping and the frequency hopping modes included in the second frequency hopping) may be indicated by the same RRC parameter. For example, frequencyHopping-r16 (or frequencyHopping) may be a parameter that sets one of intra-slot frequency hopping, inter-slot frequency hopping, intra-PUSCH frequency hopping, and / or inter-PUSCH frequency hopping. For example, the frequency hopping mode indicated by frequencyHopping-r16 may be switched implicitly based on the type of DCI format, information of a field included in the DCI format, the RNTI, and / or other information. For example, the frequency hopping mode indicated by frequencyHopping-r16 in a PUSCH scheduled in DCI formats 0_0 and 0_1 may be any of the first frequency hopping modes, and the frequency hopping mode indicated by frequencyHopping-r16 in a PUSCH scheduled in DCI format 0_2 may be any of the second frequency hopping modes.

[0229] If the frequency hopping field included in the detected DCI format or random access response UL grant is set to 1 or if the higher layer parameter frequencyHoppingOffset is provided in the PUSCH transmission of the configured grant, the terminal device 1 performs frequency hopping of the PUSCH, and does not perform frequency hopping of the PUSCH in other cases. Note that frequencyHoppingOffset is a parameter indicating a frequency offset between hoppings when frequency hopping is performed in the PUSCH transmission of the configured grant.

[0230] For PUSCH scheduled in DCI format 0_0, 0_1 and / or 0_2, the frequency offset is set by the higher layer parameter frequencyHoppingOffsetLists.

[0231] When intra-slot frequency hopping is configured, the starting RB of each hop is given by equation (1).

number

[0232] where i=0 and i=1 are the first and second hops, respectively, and RB start is the starting RB in the UL BWP, and RB offset is the frequency offset in RB units between two frequency hops. A terminal device 1 configured for intra-slot frequency hopping may determine / identify frequency resources of the first hop and the second hop based on Equation (1).

[0233] If intra-slot frequency hopping is configured, the number of symbols in the first hop is ceil(N PUSCH,s symb ) and the number of symbols in the second hop is N PUSCH,s symb -ceil(N PUSCH,s symb ), where N PUSCH,s symb is the number of OFDM symbols for PUSCH transmission per slot. The terminal device 1 in which intra-slot frequency hopping is set calculates the number of symbols in the first hop as ceil(N PUSCH,s symb ) and the number of symbols in the second hop is determined as N PUSCH,s symb -ceil(N PUSCH,s symb ) may be determined / identified.

[0234] If inter-slot frequency hopping is configured, slot n μ sThe starting RB in is given by equation (2).

number

[0235] However, n μ s is the current slot number in a radio frame, and RB start is the starting RB in the UL BWP, and RB offset is the frequency offset in RB units between two frequency hops. A terminal device 1 in which inter-slot frequency hopping is configured may determine / specify frequency resources in each slot based on Equation (2).

[0236] When inter-PUSCH frequency hopping is configured, the start RB of each hop may be given by Equation (1). The terminal device 1 in which inter-PUSCH frequency hopping is configured may determine / specify frequency resources of the first hop and the second hop based on Equation (1).

[0237] When inter-PUSCH frequency hopping is set, the number of PUSCHs included in each hop (first hop / second hop) and / or the number of OFDM symbols in each hop may be determined based on time resource allocation information included in the DCI format or the random access response UL grant. When inter-PUSCH frequency hopping is set, the terminal device 1 may determine / specify the number of PUSCHs included in each hop and / or the number of OFDM symbols in each hop based on time resources assigned to one or more PUSCHs assigned to one or more slots. The terminal device 1 may determine whether to include each of one or more scheduled PUSCHs and / or configured PUSCHs in the first hop or the second hop based on downlink control information.

[0238] As an example, when inter-PUSCH frequency hopping is configured, μ sIn, the number of PUSCH transmissions in the first hop is ceil(N PUSCH (n μ s ) / 2), and the number of PUSCH transmissions in the second hop is N PUSCH (n μ s )-ceil(N PUSCH (n μ s ) / 2) (or floor(N PUSCH (n μ s ) / 2), where N PUSCH (n μ s ) is slot n μ s The terminal device 1 in which inter-PUSCH frequency hopping is configured calculates the number of PUSCH transmissions of the first hop as ceil(N PUSCH (n μ s ) / 2), and the number of PUSCH transmissions for the second hop is determined / specified as N PUSCH (n μ s )-ceil(N PUSCH (n μ s ) / 2) (or floor(N PUSCH (n μ s However, the formula for determining / identifying the number of PUSCH transmissions for the first hop and the second hop may be reversed, e.g., the number of PUSCH transmissions for the first hop may be determined / identified by N PUSCH (n μ s )-ceil(N PUSCH (n μ s ) / 2) (or floor(N PUSCH (n μ s ) / 2), and the number of PUSCH transmissions in the second hop is given by ceil(N PUSCH (n μ s ) / 2).

[0239] As another example, when inter-PUSCH frequency hopping is configured, μ s In the above, the number of PUSCH transmissions in the first hop and the number of PUSCH transmissions in the second hop are determined as follows: μ s The terminal device 1 in which the inter-PUSCH frequency hopping is set may be based on the total number of symbols of the PUSCH transmission scheduled and / or configured in the slot n μ s In the case of slot n, the number of PUSCH transmissions in the first hop and the number of PUSCH transmissions in the second hop are μ s The PUSCH transmission may be determined / specified based on the total number of symbols of the scheduled and / or configured PUSCH transmissions.

[0240] As another example, when inter-PUSCH frequency hopping is configured, in slot n μ s In the above, a PUSCH whose start symbol is in the first half of a slot may be included in the first hop, and a PUSCH whose start symbol is in the second half of the slot may be included in the second hop. μ s In the above, a PUSCH whose starting symbol is in the first half of a slot may be included in the first hop, and a PUSCH whose starting symbol is in the second half of a slot may be included in the second hop.

[0241] As another example, when inter-PUSCH frequency hopping is configured, μ s In the above, a PUSCH whose end symbol is in the first half of a slot may be included in the first hop, and a PUSCH whose end symbol is in the second half of a slot may be included in the second hop. μ sIn the above, a PUSCH whose end symbol is in the first half of the slot may be included in the first hop, and a PUSCH whose end symbol is in the second half of the slot may be included in the second hop.

[0242] As another example, when inter-PUSCH frequency hopping is set, the terminal device 1 μ s In the above, whether one or more PUSCHs are included in the first hop or the second hop may be determined and specified for each uplink period in a slot. However, an uplink period is a time interval in which one or more PUSCHs can be continuously allocated in a slot. For example, one or more PUSCHs in an uplink period may be included in the same hop, and the same or different hops may be used between different uplink periods. The terminal device 1 in which inter-PUSCH frequency hopping is set may determine and specify whether one or more PUSCHs are included in the first hop or the second hop for each uplink period in a slot. μ s In the step S100, it may be determined and specified for each uplink period in a slot whether one or more PUSCHs are included in the first hop or the second hop.

[0243] When inter-PUSCH frequency hopping is set, the terminal device 1 may determine the number of PUSCHs included in each hop (first hop / second hop) and / or the number of OFDM symbols in each hop based on the number of repeated transmissions of PUSCHs (or the number of PUSCHs allocated in one grant) specified by downlink control information. For example, a transmission number may be assigned to each of one or more PUSCHs assigned in one UL grant, and the terminal device 1 may determine / specify whether to include it in the first hop or the second hop based on the transmission number. For example, a transmission number may be assigned to each of one or more PUSCHs in the same slot assigned in one UL grant, and the terminal device 1 may determine / specify whether to include it in the first hop or the second hop based on the transmission number. However, when a PUSCH allocated by one UL grant is segmented into multiple PUSCHs by a slot boundary, a switch between DL and UL symbols, and / or other signals, the multiple segmented PUSCHs may be assigned the same transmission number or different transmission numbers. For example, when a PUSCH allocated by one UL grant is segmented into multiple PUSCHs by a slot boundary, a switch between DL and UL symbols, and / or other signals, the multiple segmented PUSCHs may always be included in the same hop, or may be included in the same or different hops like other PUSCHs allocated by the same grant.

[0244] As an example, if frequency hopping between PUSCHs is configured and slot n μ s The number of scheduled and / or configured PUSCH transmissions in PUSCH (n μ s ), then the threshold X PUSCH =ceil(N PUSCH (n μ s ) / 2) and the same UL grant is used for slot nμ s For PUSCHs assigned to PUSCH =1~N PUSCH (n μ s ) are numbered, and the terminal device 1 is PUSCH <=X PUSCH The PUSCH in the first hop is included, and n PUSCH >X PUSCH The PUSCH may be included in the second hop.

[0245] When inter-PUSCH frequency hopping is set, the terminal device 1 may switch whether a PUSCH is included in the first hop or the second hop for each predetermined number of PUSCHs in the time domain, in a plurality of PUSCHs allocated with the same DL format or the same UL grant. The number of PUSCHs included in the same hop consecutively may be determined by the start symbol (S), period (D), and / or number of repetitions (Rep) of the PUSCH indicated in the downlink control information. However, the terminal device 1 may regard a plurality of PUSCHs segmented by a slot boundary, a switching point between DL symbols and UL symbols, and / or other channels / signals as one PUSCH, in the number of PUSCHs included in the same hop consecutively, as one PUSCH, or may regard each of the plurality of segmented PUSCHs as one PUSCH. However, when switching between the first hop and the second hop for each predetermined number of PUSCHs in the time domain, the maximum number of switching times within a slot may be limited.

[0246] However, applying intra-PUSCH frequency hopping in the second frequency hopping may be applying intra-slot frequency hopping of the first frequency hopping.

[0247] However, applying inter-slot frequency hopping in the second frequency hopping may be applying inter-slot frequency hopping in the first frequency hopping.

[0248] However, the frequency hopping mode indicated by frequencyHopping-r16 may be one of the following two modes. Inter-PUSCH frequency hopping - Frequency hopping mode indicated by the upper layer parameter frequencyHopping

[0249] Inter-PUSCH frequency hopping and intra-PUSCH frequency hopping (or intra-slot frequency hopping) may be switched implicitly. For example, when inter-PUSCH frequency hopping is set in frequencyHopping-r16 and the number of repeated transmissions indicated in a predetermined field of the DCI format is 1, the terminal device 1 may apply intra-PUSCH frequency hopping (or intra-slot frequency hopping) to scheduled or configured PUSCH transmission. For example, when inter-PUSCH frequency hopping is set in frequencyHopping-r16 and the number of PUSCHs transmitted in a certain slot is 1, the terminal device 1 may apply intra-PUSCH frequency hopping (or intra-slot frequency hopping) to scheduled or configured PUSCH transmission in the slot. For example, when inter-PUSCH frequency hopping is set in frequencyHopping-r16, the number of PUSCHs transmitted in a certain slot is 1, and the number of symbols of the PUSCH transmitted in the slot is equal to or greater than a predetermined value, the terminal device 1 may apply intra-PUSCH frequency hopping (or intra-slot frequency hopping) to the PUSCH transmission scheduled or set in that slot.

[0250] This enables the terminal device 1 to transmit uplink data to the base station device 3.

[0251] The configuration of the device in this embodiment will be described below.

[0252] 23 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. As shown in the figure, the terminal device 1 includes a radio transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The radio transmission / reception 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 measuring unit 14, a selecting unit 14, a determining unit 14, or a control unit 14.

[0253] The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user operation or the like to the radio transmission / reception unit 10. The upper layer processing unit 14 performs some or all of the processes of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function of determining / specifying resources for transmitting one or more PUSCHs based on a higher layer signal and / or DCI received from the base station device 3. The upper layer processing unit 14 may have a function of determining / specifying the leading symbol and the number of symbols of each of multiple time resources of a PUSCH for a certain TB. The upper layer processing unit 14 may have a function of determining / specifying the leading symbol and the number of symbols of multiple provisional time resources based on higher layer slot format setting information and time resource allocation information. The upper layer processing unit 14 may be configured to monitor the slot format configuration DCI in the PDCCH, and may have a function of determining / specifying, in each of the plurality of provisional time resources, a set of consecutive symbols indicated as uplink symbols by at least one of the upper layer slot format configuration information and the slot format configuration DCI, as one of the plurality of time resources of the PUSCH, when the slot format configuration DCI is detected. The upper layer processing unit 14 may be configured to monitor the slot format configuration DCI in the PDCCH, and may have a function of determining / specifying, in each of the plurality of provisional time resources, a provisional time resource including only symbols indicated as uplink symbols by the upper layer slot format configuration information, as one of the plurality of time resources of the PUSCH, when the slot format configuration DCI is not detected.The upper layer processing unit 14 may have a function of determining / specifying each of the plurality of tentative time resources based on the plurality of time resources of the PUSCH and / or allocation information of a downlink signal when the slot format configuration DCI is not set to be monitored in the PDCCH. The upper layer processing unit 14 may have a function of canceling the transmission of the PUSCH in some or all symbols of the symbol set A when the uplink allocation information indicates that a certain PUSCH is transmitted in a certain symbol set (symbol set A), the downlink allocation information indicates that a downlink signal is transmitted in a certain symbol set (symbol set B), and at least one symbol in the symbol set A is a symbol included in the symbol set B. The upper layer processing unit 14 may have a function of determining / specifying whether or not to transmit a PUSCH in a symbol indicated as flexible in the upper layer slot format configuration information based on information of a first bit field received from the base station device 3.

[0254] The medium access control layer processing unit 15 included in the upper layer processing unit 14 performs processing of the MAC layer (medium access control layer). The medium access control layer processing unit 15 controls the transmission of a scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0255] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs processing of the RRC layer (radio resource control layer). The radio resource control layer processing unit 16 manages various setting information / parameters of its own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on an upper layer signal received from the base station device 3. That is, the radio resource control layer processing unit 16 sets various setting information / parameters based on information indicating the various setting information / parameters received from the base station device 3. The radio resource control layer processing unit 16 controls (specifies) resource allocation based on downlink control information received from the base station device 3.

[0256] The radio transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The radio transmission / reception unit 10 separates, demodulates, and decodes a signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The radio transmission / reception unit 10 generates a transmission signal by modulating and encoding data, and transmits the transmission signal to the base station device 3, etc. The radio transmission / reception unit 10 outputs an upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. The radio transmission / reception unit 10 also generates and transmits an uplink signal (including a PUCCH and / or a PUSCH) based on an instruction from the upper layer processing unit 14. The radio transmission / reception unit 10 may have a function of receiving a PDCCH and / or a PDSCH. The radio transmission / reception unit 10 may have a function of transmitting one or more PUCCHs and / or PUSCHs. The radio transmission / reception unit 10 may have a function of receiving DCI on a PDCCH. The radio transceiver 10 may have a function of outputting DCI received on the PDCCH to the higher layer processing unit 14. The radio transceiver 10 may have a function of receiving an RRC message including higher layer slot format configuration information. The radio transceiver 10 may have a function of receiving time resource allocation information of a PUSCH for a certain TB on the PDCCH. The radio transceiver 10 may have a function of monitoring the slot format configuration DCI on the PDCCH. The radio transceiver 10 may have a function of receiving a DCI and / or an RRC message including a first bit field.

[0257] The RF unit 12 converts the signal received via the antenna unit 11 into a baseband signal by quadrature demodulation (down-converts) and removes unnecessary frequency components. The RF unit 12 outputs the processed analog signal to the baseband unit.

[0258] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to a CP (Cyclic Prefix) from the converted digital signal, and performs a Fast Fourier Transform (FFT) on the signal from which the CP has been removed to extract a signal in the frequency domain.

[0259] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and converts the baseband digital signal into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

[0260] The RF unit 12 uses a low-pass filter to remove unnecessary frequency components from the analog signal input from the baseband unit 13, up-converts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies power. The RF unit 12 may also have a function of determining the transmission power of an uplink signal and / or an uplink channel to be transmitted in the serving cell. The RF unit 12 is also referred to as a transmission power control unit.

[0261] FIG. 24 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As shown in the figure, the base station device 3 includes a radio transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a media access control layer processing unit 35 and a radio resource control layer processing unit 36. The radio transmission / reception unit 30 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. A control unit that controls the operation of each unit based on various conditions may be provided separately. The upper layer processing unit 34 is also referred to as a determining unit 34 or a control unit 34.

[0262] The upper layer processing unit 34 performs part or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of generating DCI based on the upper layer signal transmitted to the terminal device 1 and the time resource for transmitting the PUSCH. The upper layer processing unit 34 may have a function of outputting the generated DCI and the like to the radio transmitting / receiving unit 30. The upper layer processing unit 34 may have a function of determining / specifying resources to be used for transmitting one or more PUSCHs based on the RRC message and the generated DCI. The upper layer processing unit 34 may have a function of determining / specifying multiple tentative time resources based on upper layer slot format setting information and time resource allocation information. The upper layer processing unit 34 may have a function of determining / specifying the leading symbol and the number of symbols of each of multiple time resources for a certain PUSCH. The upper layer processing unit 34 may have a function of determining / specifying the first symbol and the number of symbols of a plurality of provisional time resources based on the upper layer slot format setting information and the time resource allocation information. When the terminal device 1 is configured to monitor the slot format setting DCI in the PDCCH, the upper layer processing unit 34 may have a function of determining / specifying a set of consecutive symbols indicated as an uplink symbol by at least one of the upper layer slot format setting information and the slot format setting DCI in each of the plurality of provisional time resources as one of the plurality of time resources for the PUSCH. When the terminal device 1 is configured to monitor the slot format setting DCI in the PDCCH, the upper layer processing unit 34 may have a function of determining / specifying the first symbol and the number of symbols of the plurality of time resources for the PUSCH based on the first symbol and the number of symbols of each of the plurality of provisional time resources and the slot format setting DCI.The upper layer processing unit 34 may have a function of determining / specifying each of the plurality of tentative time resources as each of the plurality of time resources for the PUSCH when the terminal device 1 is not set to monitor the slot format configuration DCI in the PDCCH. The upper layer processing unit 34 may have a function of determining / specifying each of the plurality of tentative time resources based on the plurality of time resources of the PUSCH and / or allocation information of the downlink signal when the terminal device 1 is not set to monitor the slot format configuration DCI in the PDCCH. The upper layer processing unit 34 may have a function of not using some or all of the symbols of the symbol set A for receiving the PUSCH when the uplink allocation information transmitted to the terminal device 1 indicates that a certain PUSCH is transmitted in a certain symbol set (symbol set A), the downlink allocation information indicates that a downlink signal is transmitted in a certain symbol set (symbol set B), and at least one symbol of the symbol set A is a symbol included in the symbol set B. The upper layer processing unit 34 may have a function of determining / identifying whether or not to receive a PUSCH in a symbol indicated as flexible in the upper layer slot format setting information based on the information of the first bit field transmitted to the terminal device 1.

[0263] The media access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer. The media access control layer processing unit 35 performs processing related to the scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 36.

[0264] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​generates DCI (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 ​​generates DCI, downlink data (transport block (TB), random access response (RAR)) arranged in the PDSCH, system information, RRC message, MAC CE (Control Element), etc., or acquires them from an upper node, and outputs them to the radio transmitting / receiving unit 30. In addition, the radio resource control layer processing unit 36 ​​manages various setting information / parameters of each terminal device 1. The radio resource control layer processing unit 36 ​​may set various setting information / parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 ​​transmits / reports information indicating various setting information / parameters. The radio resource control layer processing unit 36 ​​may transmit / report information for identifying the setting of one or more reference signals in a certain cell.

[0265] When the base station device 3 transmits an RRC message, a MAC CE, and / or a PDCCH to the terminal device 1 and the terminal device 1 performs processing based on the reception of the message, the base station device 3 performs processing (control of the terminal device 1 and the system) assuming that the terminal device is performing the processing. That is, the base station device 3 transmits an RRC message, a MAC CE, and / or a PDCCH to the terminal device 1 to cause the terminal device to perform processing based on the reception of the message.

[0266] The radio transmission / reception unit 30 transmits higher layer signals (RRC messages), DCI, and the like to the terminal device 1. Moreover, the radio transmission / reception unit 30 receives an uplink signal transmitted from the terminal device 1 based on an instruction from the higher layer processing unit 34. The radio transmission / reception unit 30 may have a function of transmitting a PDCCH and / or a PDSCH. The radio transmission / reception unit 30 may have a function of receiving one or more PUCCHs and / or PUSCHs. The radio transmission / reception unit 30 may have a function of transmitting DCI on a PDCCH. The radio transmission / reception unit 30 may have a function of transmitting DCI output by the higher layer processing unit 34 on a PDCCH. The radio transmission / reception unit 30 may have a function of transmitting time resource allocation information of a PUSCH for a certain TB on a PDCCH. The radio transmission / reception unit 30 may have a function of transmitting an RRC message including higher layer slot format setting information. The radio transmission / reception unit 30 may have a function of transmitting a DCI and / or an RRC message including a first bit field. Other than that, some of the functions of the wireless transceiver unit 30 are similar to those of the wireless transceiver unit 10, and therefore the description thereof will be omitted. When the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless transceiver unit 30 may be included in each transmission / reception point 4.

[0267] Furthermore, the upper layer processing unit 34 transmits (transfers) or receives control messages or user data between base station devices 3 or between higher-level network devices (MME, S-GW (Serving-GW)) and the base station device 3. In Fig. 24, other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but it is clear that the base station device 3 has a plurality of blocks having other functions necessary for operating as the base station device 3 as components. For example, the upper layer processing unit 34 includes a Radio Resource Management layer processing unit and an application layer processing unit.

[0268] In addition, the "parts" in the figure are elements that realize the functions and procedures of the terminal apparatus 1 and the base station apparatus 3, and may also be expressed by terms such as section, circuit, component equipment, device, and unit.

[0269] Each of the units denoted by reference numerals 10 to 16 in the terminal device 1 may be configured as a circuit. Each of the units denoted by reference numerals 30 to 36 in the base station device 3 may be configured as a circuit.

[0270] (1) A terminal device 1 according to a first aspect of the present invention includes a receiver 1 that detects a first DCI format (which may be DCI format 0_2) including first allocation information (S, L, and / or Rep indicated in uplink RA information) for identifying a time resource and a number of repeated transmissions to be used for transmitting a physical uplink shared channel (PUSCH) corresponding to a first transport block (TB), and detects a second DCI format (which may be DCI format 1_0, DCI format 1_1, and / or DCI format 0_1) including second allocation information (downlink RA information) instructing to receive a downlink signal. 0, and a decision unit 14 that specifies a time resource (temporary PUSCH resource) for transmitting the physical uplink shared channel based on the first allocation information, wherein the decision unit 14 cancels the transmission of the first physical uplink shared channel when the first allocation information indicates that the first physical uplink shared channel, which is any one of repeated transmissions of the physical uplink shared channel, is transmitted in a first symbol set, the second allocation information indicates that the downlink signal is received in a second symbol set, and at least one symbol of the first symbol set is a symbol included in the second symbol set.

[0271] (2) A base station device 3 in a second aspect of the present invention is a base station device 3 that communicates with a terminal device 1, and transmits a signal including a first DCI format (which may be DCI format 0_2) including first allocation information (S, L and / or Rep indicated in uplink RA information) for specifying a time resource and a number of repeated transmissions to be used for transmitting a physical uplink shared channel (PUSCH) corresponding to a first transport block (TB) to the terminal device 1, and transmits a signal including a second DCI format (which may be DCI format 1_0, DCI format 1_1 and / or DCI format 2_2) including second allocation information (downlink RA information) that instructs the terminal device 1 to receive a downlink signal. a transmitter 30 configured to transmit a signal including a first physical uplink shared channel (which may be DCI format 0_1 ​​or DCI format 0_1); and a determination unit configured to determine / specify a time resource for receiving the physical uplink shared channel based on the first allocation information, wherein the determination unit determines / specifies not to receive the first physical uplink shared channel when the first allocation information indicates that a first physical uplink shared channel, which is one of the plurality of physical uplink shared channels, is received in a first symbol set, the second allocation information indicates that the downlink signal is transmitted in a second symbol set, and at least one symbol of the first symbol set is a symbol included in the second symbol set.

[0272] (3) A terminal device 1 in a third aspect of the present invention includes a receiver 10 that receives an RRC message including first information (higher layer slot format setting information) indicating whether each of symbols in a certain period is downlink, uplink, or flexible, receives second information including a first bit field, and receives third information (uplink RA information) for identifying a first time resource for transmitting a physical uplink shared channel (PUSCH) for a certain transport block (TB), and a decision unit 14 that identifies the first time resource based on the first information and the third information, wherein when the first bit field is a first value and the receiver receives fourth information (slot format setting DCI) indicating a slot format of a plurality of slots on a physical downlink control channel (PDCCH), the decision unit 14 does not use resources allocated to symbols indicated as downlink and flexible in the slot format among the first time resources for transmitting the physical uplink shared channel, and when the first bit field is a second value, uses all of the first time resources for transmitting the physical uplink shared channel.

[0273] (4) In the third aspect of the present invention, the receiver 10 may receive the second information on a physical downlink control channel (PDCCH).

[0274] (5) In the third aspect of the present invention, the receiving unit 10 may receive the second information in an RRC message.

[0275] (6) A base station device 3 in a fourth aspect of the present invention is a base station device 3 that communicates with a terminal device 1, and includes a transmitter 30 that transmits an RRC message including first information (higher layer slot format setting information) indicating whether each symbol in a certain period is downlink, uplink, or flexible, transmits second information including a first bit field, and transmits third information (uplink RA information) for identifying a first time resource in which the terminal device 1 transmits a physical uplink shared channel (PUSCH) for a certain transport block (TB), and a transmitter 31 that transmits the physical uplink shared channel (PUSCH) based on the first information, the second information, and the third information. and a receiving unit 30 for receiving a physical uplink shared channel, wherein when the first bit field is a first value and the transmitting unit transmits fourth information (slot format setting DCI) indicating a slot format of a plurality of slots to the terminal device on a physical downlink control channel (PDCCH), the receiving unit 30 does not use resources allocated to symbols indicated as downlink and flexible in the slot format among the first time resources for receiving the physical uplink shared channel, and when the first bit field is a second value, the receiving unit 30 uses all of the first time resources for receiving the physical uplink shared channel.

[0276] (7) In the fourth aspect of the present invention, the transmitter 30 may transmit the second information on a physical downlink control channel (PDCCH).

[0277] (8) In the fourth aspect of the present invention, the transmission unit 30 may transmit the second information in an RRC message.

[0278] This allows the terminal device 1 to efficiently communicate with the base station device 3. For example, in DCI that schedules data of different services (eMBB, URLLC, and / or mMTC, etc.), a notification method appropriate for each service can be used when indicating a time resource for receiving a PDSCH and / or a time resource for transmitting a PUSCH. Furthermore, the base station device 3 can efficiently communicate with the terminal device 1. For example, in DCI that schedules data of different services, a notification method appropriate for each service can be used when indicating a time resource for transmitting a PDSCH and / or a time resource for receiving a PUSCH.

[0279] A program that operates on an apparatus according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to an aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or other storage device system.

[0280] A program for implementing the functions of the embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0281] In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when a technology for integrated circuitization that replaces current integrated circuits appears due to the progress of semiconductor technology, one or more aspects of the present invention may use a new integrated circuit according to that technology.

[0282] In an embodiment relating to one aspect of the present invention, an example is described in which the present invention is applied to a communication system consisting of a base station device and a terminal device, but the present invention can also be applied to a system in which terminals communicate with each other, such as D2D (Device to Device).

[0283] The present invention is not limited to the above-described embodiment. In the embodiment, an example of a device is described, but the present invention is not limited to this, and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices of AV equipment, kitchen equipment, cleaning / washing equipment, air conditioners, office equipment, vending machines, and other household appliances.

[0284] Although the embodiments of the present invention have been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes within the scope of the gist of the present invention are also included. In addition, one aspect of the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments are replaced with elements that have the same effect are also included. [Industrial Applicability]

[0285] One aspect of the present invention can be used in, for example, a communication system, a communication device (for example, a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (for example, a communication chip), or a program. [Explanation of symbols]

[0286] 1(1A, 1B) Terminal equipment 3 Base station equipment 4 Transmit / Receive Point (TRP) 10 Radio transmitter / receiver 11 Antenna section 12 RF section 13 Baseband section 14 Upper layer processing unit 15 Media access control layer processing unit 16 Radio resource control layer processing unit 30 Radio transmitter / receiver 31 Antenna section 32 RF section 33 Baseband section 34 Upper layer processing unit 35 Media access control layer processing unit 36 Radio resource control layer processing unit 50 Transmitting Unit (TXRU) 51 Phase Shifter 52 Antenna Element

Claims

1. A terminal device, a receiving unit for receiving an RRC message including first information indicating whether each of symbols in a certain period is a downlink, an uplink, or a flexible symbol, receiving second information including a first bit field, and receiving third information for identifying a first time resource for transmitting a physical uplink shared channel for a transport block; a determination unit that identifies the first time resource based on the first information and the third information, The determination unit is when the first bit field is a first value and the receiving unit receives fourth information indicating a slot format of a plurality of slots on a physical downlink control channel, resources allocated to a symbol indicated as downlink in the slot format and a symbol indicated as flexible among the first time resources are not used for transmitting the physical uplink shared channel, and resources allocated to a symbol indicated as uplink in the slot format among the first time resources are used for transmitting the physical uplink shared channel; A terminal device that uses all of the first time resources for transmitting the physical uplink shared channel when the first bit field is a second value.

2. The terminal device according to claim 1 , wherein the receiving unit receives the second information through a physical downlink control channel.

3. The terminal device according to claim 1 , wherein the receiving unit receives the second information in an RRC message.

4. A base station device that communicates with a terminal device, a transmitter that transmits an RRC message including first information indicating whether each symbol of a certain period is a downlink, an uplink, or a flexible symbol, transmits second information including a first bit field, and transmits third information for identifying a first time resource in which the terminal device transmits a physical uplink shared channel for a certain transport block; a receiving unit that receives the physical uplink shared channel based on the first information, the second information, and the third information, The receiving unit is when the first bit field is a first value and the transmitter transmits fourth information indicating a slot format of a plurality of slots to the terminal device on a physical downlink control channel, resources allocated to a symbol indicated as downlink in the slot format and a symbol indicated as flexible among the first time resources are not used for receiving the physical uplink shared channel, and resources allocated to a symbol indicated as uplink in the slot format among the first time resources are used for receiving the physical uplink shared channel; A base station device that uses all of the first time resources for receiving the physical uplink shared channel when the first bit field is a second value.

5. The base station apparatus according to claim 4 , wherein the transmitting unit transmits the second information on a physical downlink control channel.

6. The base station apparatus according to claim 4 , wherein the transmission unit transmits the second information in an RRC message.

7. A communication method for a terminal device, comprising: receiving an RRC message including first information indicating whether each of symbols of a certain period is downlink, uplink, or flexible; receiving second information including a first bit field; and receiving third information for identifying a first time resource for transmitting a physical uplink shared channel for a transport block; identifying the first time resource based on the first information and the third information; when the first bit field is a first value and fourth information indicating a slot format of a plurality of slots is received on a physical downlink control channel, resources allocated to a symbol indicated as downlink in the slot format and a symbol indicated as flexible among the first time resources are not used for transmitting the physical uplink shared channel, and resources allocated to a symbol indicated as uplink in the slot format among the first time resources are used for transmitting the physical uplink shared channel; A communication method, comprising: when the first bit field is a second value, using all of the first time resource for transmitting the physical uplink shared channel.

Images