WO2020170972A1 - Base station device, terminal device, communication method, and integrated circuit - Google Patents

Abstract

According to the present invention, a terminal device and a base station device communicate efficiently. A terminal device for performing a random access procedure, the terminal device being such that: a first parameter and a second parameter of an upper layer are received; a PDCCH including a DCI is received; a PUSCH scheduled by the DCI is transmitted; a third parameter is defined in advance by a default table; the first parameter, the second parameter, and the third parameter indicate information regarding PUSCH time domain resource allocation; and when a CRC scrambled by a TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected irrespective of whether or not the second parameter has been received, and the PUSCH time domain resource allocation is performed on the basis of the selected parameter.

Description

Base station device, terminal device, communication method, and integrated circuit

The present invention relates to a base station device, a terminal device, a communication method, and an integrated circuit. The present application claims priority based on Japanese Patent Application No. 2019-30647 filed in Japan on February 22, 2019, the content of which is incorporated herein by reference.

Currently, LTE (Long Term Evolution)-Advanced Pro and NR (New Radio) are being used in the 3rd Generation Partnership Project (3GPP) as a wireless access method and wireless network technology for the 5th generation cellular system. technology) and standard development are being conducted (Non-Patent Document 1).

In the 5th generation cellular system, eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-delay and high-reliability communication, IoT (Internet of Things), etc. There are three required scenario scenarios for services: Mass Machine Machine Type Communication (mMTC), which connects many machine type devices.

An object of one aspect of the present invention is to provide a terminal device, a base station device, a communication method, and an integrated circuit that enable efficient communication in the above wireless communication system.

(1) In order to achieve the above object, the embodiments of the present invention take the following means. That is, a terminal device performing a random access procedure according to an aspect of the present invention receives a first parameter and a second parameter of an upper layer, receives a PDCCH including DCI, and is scheduled by the DCI. A transmission unit for transmitting PUSCH, the third parameter is predefined by a default table, and the first parameter, the second parameter and the third parameter are in the PUSCH time domain. In the case where a CRC scrambled by TC-RNTI is added to the DCI indicating resource allocation information, the first parameter and the third parameter can be recognized regardless of whether the second parameter is received. One of them is selected, and the PUSCH time domain resource allocation is given based on the selected parameters.

(2) Further, the base station apparatus that communicates with the terminal apparatus that performs the random access procedure according to an aspect of the present invention transmits the upper layer first parameter and the second parameter, and transmits the PDCCH including the DCI. And a receiver for receiving a PUSCH scheduled by the DCI, the third parameter being predefined by a default table, the first parameter, the second parameter, and the The third parameter indicates information of PUSCH time domain resource allocation, and when the CRC scrambled by TC-RNTI is added to the DCI, the first parameter is irrespective of whether the second parameter is received or not. , And the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.

(3) Further, a communication method according to an aspect of the present invention is a communication method for a terminal device that performs a random access procedure, and receives a first parameter and a second parameter of an upper layer and obtains a PDCCH including DCI. Receiving, and transmitting a PUSCH scheduled by the DCI, wherein a third parameter is predefined by a default table, the first parameter, the second parameter, and The third parameter indicates information of PUSCH time domain resource allocation, and when a CRC scrambled by TC-RNTI is added to the DCI, the second parameter is received regardless of whether the second parameter is received. One of the one parameter and the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.

(4) Further, a communication method according to an aspect of the present invention is a communication method of a base station device that communicates with a terminal device that performs a random access procedure, and transmits a first parameter and a second parameter of an upper layer. , Transmitting a PDCCH containing the DCI and receiving a PUSCH scheduled by the DCI, the third parameter being predefined by a default table, the first parameter, the first parameter The second parameter and the third parameter indicate information of PUSCH time domain resource allocation, and whether or not the second parameter is received when a CRC scrambled by TC-RNTI is added to the DCI. Regardless, one is selected from the first parameter and the third parameter, and the PUSCH time domain resource allocation is given based on the selected parameter.

(5) Further, the integrated circuit according to one aspect of the present invention is an integrated circuit that is mounted on a terminal device that performs a random access procedure, receives the first parameter and the second parameter of the upper layer, and outputs the DCI. The terminal device is caused to exert the function of receiving the PDCCH including the function of transmitting the PUSCH scheduled by the DCI, and the third parameter is defined in advance by a default table, and the first parameter, the The second parameter and the third parameter indicate information of the PUSCH time domain resource allocation, and when the CRC scrambled by TC-RNTI is added to the DCI, reception of the second parameter is performed. Regardless of the presence or absence, one is selected from the first parameter and the third parameter, and the PUSCH time domain resource allocation is given based on the selected parameter.

(6) Further, an integrated circuit according to an aspect of the present invention is an integrated circuit mounted on a base station device that communicates with a terminal device that performs a random access procedure, and includes a first parameter and a second parameter of an upper layer And the function of transmitting a PDCCH including DCI and the function of receiving a PUSCH scheduled by the DCI are exerted on the base station device, and a third parameter is defined in advance by a default table, The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation, and when a CRC scrambled by TC-RNTI is added to the DCI, One of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received, and the PUSCH time domain resource allocation is given based on the selected parameter.

According to one aspect of the present invention, the base station device and the terminal device can efficiently communicate with each other.

It is a figure which shows the concept of the wireless communication system which concerns on embodiment of this invention. It is a figure which shows the example of the SS/PBCH block and SS burst set which concern on embodiment of this invention. It is a figure which shows an example of schematic structure of the uplink and the downlink slot which concerns on embodiment of this invention. FIG. 6 is a diagram showing a relationship in the time domain of subframes, slots, and minislots according to the embodiment of the present invention. It is a figure which shows an example of the slot or sub-frame which concerns on embodiment of this invention. It is a figure showing an example of beamforming concerning an embodiment of the present invention. It is a figure which shows an example of the PDSCH mapping type which concerns on embodiment of this invention. It is a figure which shows an example of the random access procedure of the terminal device 1 which concerns on embodiment of this invention. It is a figure which shows an example of the field contained in RAR UL grant which concerns on embodiment of this invention. It is a figure which defines the resource allocation table applied to PDSCH time domain resource allocation which concerns on embodiment of this invention. It is a figure which shows an example of the default table A which concerns on embodiment of this invention. It is a figure which shows an example of the default table B which concerns on embodiment of this invention. It is a figure which shows an example of the default table C which concerns on embodiment of this invention. It is a figure which shows an example which calculates SLIV which concerns on embodiment of this invention. It is a figure which shows an example which DCI which concerns on this embodiment schedules PDSCH. It is a figure which defines the resource allocation table applied to PUSCH time domain resource allocation which concerns on this embodiment. It is a figure which shows an example of PUSCH default table A which concerns on this embodiment. It is a figure which shows an example which transmits PUSCH scheduled by the RAR UL grant which concerns on this embodiment. It is a flowchart which shows an example of the random access procedure of the MAC entity which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the terminal device 1 which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the base station apparatus 3 which concerns on embodiment of this invention.

An embodiment of the present invention will be described below.

FIG. 1 is a conceptual diagram of a wireless communication system according to 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 the terminal device 1.

The terminal device 1 is also called a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), MS (Mobile Station). The base station device 3 includes a radio base station device, a base station, a radio base station, a fixed station, an NB (Node B), an eNB (evolved Node B), a BTS (Base Transceiver Station), a BS (Base Station), and an NR NB ( Also referred to as NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. The base station device 3 may include a core network device. In addition, the base station device 3 may include one or more transmission/reception points 4 (transmission reception point). At least a part of the functions/processes of the base station device 3 described below may be functions/processes at each transmission/reception point 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 with the communicable range (communication area) controlled by the base station device 3 as one or a plurality of cells. In addition, the base station device 3 may serve the terminal device 1 with the communicable range (communication area) controlled by the one or more transmission/reception points 4 as one or more cells. Further, one cell may be divided into a plurality of partial areas (Beamed area), and the terminal device 1 may be served in each partial area. Here, the partial region may be identified based on a beam index used in beam forming or a precoding index.

A wireless communication link from the base station device 3 to the terminal device 1 is called a downlink. A wireless communication link from the terminal device 1 to the base station device 3 is called an uplink.

In FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, orthogonal frequency division multiplexing (OFDM: Orthogonal Frequency Division Multiplexing) including a cyclic prefix (CP: Cyclic Prefix), single carrier frequency multiplexing (SC- FDM: Single-Carrier Frequency Division Multiplexing), discrete Fourier transform spreading OFDM (DFT-S-OFDM: Discrete Fourier Transform Spread OFDM), multi-carrier code division multiplexing (MC-CDM: Multi-Carrier Code Division Division Multiplexing) are used. Good.

Further, in FIG. 1, in wireless communication between the terminal device 1 and the base station device 3, a universal filter multi-carrier (UFMC), a filter OFDM (F-OFDM: Filtered OFDM), and a window function are used. Multiplied OFDM (Windowed OFDM) and filter bank multi-carrier (FBMC: Filter-Bank Multi-Carrier) may be used.

In this embodiment, the OFDM symbol is used as the transmission method for explanation, but the case of using the above-mentioned other transmission method is also included in the present invention.

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

One aspect of this embodiment may be operated in carrier aggregation or dual connectivity with a radio access technology (RAT: Radio Access Technology) such as LTE or LTE-A/LTE-A Pro. At this time, some or all cells or cell groups, carriers or carrier groups (for example, primary cell (PCell: Primary Cell), secondary cell (SCell: Secondary Cell), primary secondary cell (PSCell), MCG (Master Cell Group) ), SCG (Secondary Cell Group), etc.). It may also be used as a stand-alone that operates independently. In the dual connectivity operation, the SpCell (Special Cell) is the PCell of the MCG or the PSCell of the SCG depending on whether the MAC (MAC: Medium Access Control) entity is associated with the MCG or the SCG, respectively. Called. Unless it is a dual connectivity operation, SpCell (Special Cell) is called PCell. SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

In the present embodiment, one or more serving cells may be set for the terminal device 1. The plurality of configured serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell that has undergone the initial connection establishment procedure, a serving cell that has initiated the connection re-establishment procedure, or a cell designated as the primary cell in the handover procedure. Good. One or a plurality of secondary cells may be set when or after the RRC (Radio Resource Control) connection is established. However, the plurality of configured serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information in the uplink among one or a plurality of secondary cells in which the terminal device 1 is set. In addition, a subset of two types of serving cells of a master cell group and a secondary cell group may be set for the terminal device 1. The master cell group may include one primary cell and zero or more secondary cells. The secondary cell group may include one primary secondary cell and zero or more secondary cells.

The TDD (Time Division Duplex) and/or the FDD (Frequency Division Duplex) may be applied to the wireless communication system of the present embodiment. The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of the plurality of cells. Further, cells to which the TDD scheme is applied and cells to which the FDD scheme is applied may be aggregated. The TDD method may be referred to as an unpaired spectrum operation. The FDD method may be referred to as a paired spectrum operation.

In the downlink, the carrier corresponding to the serving cell is called the downlink component carrier (or downlink carrier). In the uplink, a carrier corresponding to a serving cell is called an uplink component carrier (or an uplink carrier). In the side link, the carrier corresponding to the serving cell is called a side link component carrier (or side link carrier). The downlink component carrier, the uplink component carrier, and/or the side link component carrier are collectively referred to as a component carrier (or carrier).

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

In FIG. 1, the following physical channels are used in the wireless communication between the terminal device 1 and the base station device 3.
・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)
The PBCH is used to notify an important information block (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1.

Also, the PBCH may be used to broadcast a time index within a cycle of a block of a synchronization signal (also referred to as an SS/PBCH block). Here, the time index is information indicating the index of the synchronization signal and PBCH in the cell. For example, when the SS/PBCH block is transmitted using the assumption of three transmission beams (transmission filter setting, pseudo co-location (QCL: Quasi Co-Location) regarding reception spatial parameter), it is set within a predetermined cycle or set It may indicate the time order within the cycle. Further, the terminal device may recognize the difference in time index as the difference in transmission beam.

The PDCCH is used to transmit (or carry) downlink control information (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 transmission of downlink control information. That is, a field for downlink control information is defined as DCI and is mapped to information bits. The PDCCH is transmitted in PDCCH candidates. The terminal device 1 monitors a set of PDCCH candidates (candidate) in the serving cell. Monitoring means trying to decode the PDCCH according to a certain DCI format.

For example, the following DCI format may be defined.

・DCI format 0_0
・DCI format 0_1
・DCI format 1_0
・DCI format 1_1
・DCI format 2_0
・DCI format 2_1
・DCI format 2_2
・DCI format 2_3
The DCI format 0_0 may be used for PUSCH scheduling in a serving cell. The DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation). In the DCI format 0_0, a CRC scrambled by any of C-RNTI, CS-RNTI, MCS-C-RNTI, and/or TC-RNTI may be added. DCI format 0_0 may be monitored in the common search space or the UE-specific search space.

DCI format 0_1 may be used for PUSCH scheduling in a serving cell. The DCI format 0_1 refers to information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP: BandWidth Part), channel state information (CSI: Channel State Information) request, and sounding reference. A signal (SRS: Sounding Reference Signal) request and information about the antenna port may be included. In the DCI format 0_1, a CRC scrambled by any of C-RNTI, CS-RNTI, SP (Semi Persistent)-CSI-RNTI, and/or MCS-C-RNTI of RNTI may be added. .. DCI format 0_1 may be monitored in the UE-specific search space.

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

DCI format 1_1 may be used for PDSCH scheduling in a serving cell. DCI format 1_1 is information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), band portion (BWP) information, transmission configuration indication (TCI: Transmission Configuration Indication), and/or antenna port. Information may be included. In the DCI format 1_1, a CRC scrambled by any of C-RNTI, CS-RNTI, and/or MCS-C-RNTI of RNTI may be added. DCI format 1_1 may be monitored in the UE-specific search space.

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

The DCI format 2_1 is used to notify the terminal device 1 of a physical resource block and an OFDM symbol that may be assumed not to be transmitted. This information may be referred to as a preemption instruction (intermittent transmission instruction).

DCI format 2_2 is used for transmitting the transmission power control (TPC: Transmit Power Control) command for PUSCH and PUSCH.

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

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

The CRC (Cyclic Redundancy Check) parity bit added to the DCI format transmitted by one PDCCH is SI-RNTI (System Information-Radio Network Temporary Identifier), P-RNTI (Paging-Radio Network Temporary Identifier), C- It is scrambled by RNTI (Cell-Radio Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), RA-RNTI (Random Access-Radio Network Temporary Identity), or Temporary C-RNTI. SI-RNTI may be an identifier used for broadcasting system information. The P-RNTI may be an identifier used for notification of paging and system information change. C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device in a cell. The Temporary C-RNTI is an identifier for identifying the terminal device 1 that has transmitted the random access preamble during the contention based random access procedure.

C-RNTI (terminal device identifier (identification information)) is used to control PDSCH or PUSCH in one or more slots. CS-RNTI is used to periodically allocate PDSCH or PUSCH resources. MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission. Temporary C-RNTI (TC-RNTI) is used to control PDSCH transmission or PUSCH transmission in one or more slots. The Temporary C-RNTI is used to schedule the retransmission of the random access message 3 and the transmission of the random access message 4. RA-RNTI (random access response identification information) is determined according to frequency and time position information of the physical random access channel that transmitted the random access preamble.

PUCCH is used to transmit uplink control information (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: Channel State Information) used to indicate the state of the downlink channel. Further, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request the UL-SCH resource. Further, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). HARQ-ACK may indicate HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).

PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the medium access (MAC: Medium Access Control) layer. In the case of downlink, it is also used for transmitting system information (SI: System Information) and random access response (RAR: Random Access Response).

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

Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in an upper layer (upper layer: higher layer). For example, the base station device 3 and the terminal device 1 transmit/receive RRC signaling (RRC message: Radio Resource Control message, also called RRC information: Radio Resource Control information) in the radio resource control (RRC: Radio Resource Control) layer. You may. In addition, the base station device 3 and the terminal device 1 may transmit and receive a MAC control element in a MAC (Medium Access Control) layer. In addition, the RRC layer of the terminal device 1 acquires the system information reported from the base station device 3. Here, the RRC signaling, the system information, and/or the MAC control element are also referred to as an upper layer signal (upper layer signalling) or an upper layer parameter. The upper layer here means an upper layer viewed from the physical layer, and thus may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like. For example, in the processing of the MAC layer, the upper layer may include one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer and the like. Hereinafter, the meaning of “A is given by the upper layer” or “A is given by the upper layer” means that the upper layer (mainly the RRC layer, the MAC layer, etc.) of the terminal device 1 is transmitted from the base station device 3. It may mean that A is received and the received A is given from the upper layer of the terminal device 1 to the physical layer of the terminal device 1. For example, the base station device 3 transmits an RRC message including an information element of A, the terminal device 1 receives an RRC message including an information element of A, and the terminal device 1 is a terminal from the upper layer of the terminal device 1. Apply to the physical layer of device 1. Information elements are included in the RRC message.

PDSCH or PUSCH may be used for transmitting RRC signaling and MAC control elements. Here, in PDSCH, the RRC signaling transmitted from the base station apparatus 3 may be common signaling to the plurality of terminal apparatuses 1 in the cell. Further, 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, the terminal device-specific (UE-specific) information may be transmitted to a certain terminal device 1 using dedicated signaling. Moreover, PUSCH may be used for transmission of UE capability (UE Capability) in the uplink.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used for transmitting the information output from the upper layer, but is used by the physical layer.
・Synchronization signal (SS)
・Reference Signal (RS)
The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The cell ID may be detected using PSS and SSS.

The synchronization signal is used for the terminal device 1 to synchronize the downlink frequency domain and time domain. Here, the synchronization signal may be used by the terminal apparatus 1 for precoding by the base station apparatus 3 or for precoding or beam selection in beamforming. It should be noted that the beam may be called a transmission or reception filter setting, or a spatial domain transmission filter or a spatial domain reception filter.

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

In the present embodiment, any 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)
DMRS is used to demodulate the modulated signal. Two types of reference signals for demodulating PBCH and PDSCH may be defined for DMRS, or both may be referred to as DMRS. The CSI-RS is used for measuring channel state information (CSI) and beam management, and a transmission method of a periodic or semi-persistent or aperiodic CSI reference signal is applied. The CSI-RS may be defined as a non-zero power (NZP) CSI-RS and a zero-power (ZP: Zero Power) CSI-RS having zero transmission power (or reception power). Here, the ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or no transmission power, and the PTRS is for tracking the phase on the time axis in order to guarantee the frequency offset due to the phase noise. The TRS is used to guarantee the Doppler shift when moving at a high speed, and the TRS may be used as one setting of the CSI-RS, for example, one-port CSI-RS is used as the TRS. Radio resources may be configured.

In the present 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)
DMRS is used to demodulate the modulated signal. Two types of reference signals for demodulating PUCCH and PUSCH may be defined in DMRS, or both may be referred to as DMRS. SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management. The PTRS is used to track the phase on the time axis in order to guarantee the frequency offset due to the phase noise.

The downlink physical channel and/or the downlink physical signal are collectively referred to as the downlink signal. The uplink physical channel and/or the uplink physical signal are collectively referred to as an uplink signal. The downlink physical channel and/or the uplink physical channel are generically called a physical channel. The downlink physical signal and/or the uplink physical signal are collectively referred to as a physical signal.

BCH, UL-SCH and DL-SCH are transport channels. A channel used in the medium access control (MAC) layer is called a transport channel. The unit of the transport channel used in the MAC layer is also called a transport block (TB: transport block) and/or a MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) is controlled for each transport block in the MAC layer. The transport block is a unit of data delivered by the MAC layer to the physical layer. In the physical layer, transport blocks are mapped to codewords, and an encoding process is performed for each codeword.

FIG. 2 is a diagram showing an example of an SS/PBCH block (also referred to as a synchronization signal block, an SS block, and an SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to the present embodiment. FIG. 2 shows an example in which two SS/PBCH blocks are included in an SS burst set that is periodically transmitted, and the SS/PBCH block is composed of 4 consecutive OFDM symbols.

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

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

SS burst set may be sent periodically. For example, a cycle to be used for initial access and a cycle set for a connected (Connected or RRC_Connected) terminal device may be defined. Further, the cycle set for the connected (Connected or RRC_Connected) terminal device may be set in the RRC layer. In addition, the period set for the connected (Connected or RRC_Connected) terminal is the period of the radio resources in the time domain that may potentially be transmitted, and whether the base station device 3 actually transmits You may decide. Also, the cycle used for initial access may be defined in advance in a specification or the like.

∙ The SS burst set may be determined based on the system frame number (SFN: System Frame Number). Further, the start position (boundary) of the SS burst set may be determined based on the SFN and the cycle.

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

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

Within a cycle of an SS burst set, SS/PBCH blocks assigned the same SSB index may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation. The setting corresponding to one or more SS/PBCH blocks that may be QCL (or may be reference signals) may be referred to as QCL setting.

The number of SS/PBCH blocks (which may be referred to as the number of SS blocks or the number of SSBs) is, for example, the number of SS/PBCH blocks in the SS burst or SS burst set, or in the cycle of SS/PBCH blocks. May be defined. In addition, the number of SS/PBCH blocks may indicate the number of beam groups for cell selection within the SS burst, within the SS burst set, or within the period of the SS/PBCH block. Here, the beam group may be defined as the number of different SS/PBCH blocks or the number of different beams included in the SS burst, or the set of SS bursts, or the period of the SS/PBCH block.

Hereinafter, the reference signals described in this embodiment are downlink reference signals, synchronization signals, SS/PBCH blocks, downlink DM-RSs, CSI-RSs, uplink reference signals, SRSs, and/or uplink DM-. Including RS. For example, the downlink reference signal, the synchronization signal and/or the SS/PBCH block may be referred to as a reference signal. Reference signals used in the downlink include downlink reference signals, synchronization signals, SS/PBCH blocks, downlink DM-RSs, CSI-RSs, and the like. The reference signal used in the uplink includes an uplink reference signal, SRS, and/or uplink DM-RS.

Also, the reference signal may be used for radio resource measurement (RRM). Further, the reference signal may be used for beam management.

Beam management includes analog and/or digital beams in a transmitting device (the base station device 3 in the case of downlink and the terminal device 1 in the case of uplink) and a receiving device (the terminal device 1 in the case of downlink). , And in the case of the uplink, it is the procedure of the base station apparatus 3 and/or the terminal apparatus 1 for matching the directivity of the analog and/or digital beams in the base station apparatus 3 and obtaining the beam gain.

The procedure for configuring, setting or establishing the beam pair link may include the following procedure.
・Beam selection
・Beam refinement
・Beam recovery
For example, the beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Further, the beam improvement may be a procedure of selecting a beam with a higher gain or changing the beam between the base station apparatus 3 and the terminal apparatus 1 optimally by moving the terminal apparatus 1. The beam recovery may be a procedure for reselecting the beam when the quality of the communication link is deteriorated due to the blockage caused by the passage of a shield or a person in the communication between the base station device 3 and the terminal device 1.

Beam management may include beam selection and beam refinement. Beam recovery may include the following procedures.
-Detection of beam failure-Discoverment of new beam-Transmission of beam recovery request-Monitoring response to beam recovery request For example, when selecting the transmission beam of the base station device 3 in the terminal device 1, CSI-RS or RSRP (Reference Signal Received Power) of SSS included in the SS/PBCH block may be used, or CSI may be used. Also, a CSI-RS resource index (CRI: CSI-RS Resource Index) may be used as a report to the base station apparatus 3, or PBCH included in the SS/PBCH block and/or for demodulation used for demodulating PBCH An index designated by a reference signal (DMRS) sequence may be used.

Also, the base station apparatus 3 instructs the CRI or SS/PBCH time index when instructing the beam to the terminal apparatus 1, and the terminal apparatus 1 receives based on the instructed CRI or SS/PBCH time index. To do. At this time, the terminal device 1 may set and receive the spatial filter based on the instructed CRI or the time index of the SS/PBCH. In addition, the terminal device 1 may receive using the assumption of a pseudo co-location (QCL). A signal (antenna port, sync signal, reference signal, etc.) is "QCL" with another signal (antenna port, sync signal, reference signal, etc.), or "the assumption of QCL is used" means that a signal is Can be interpreted as being associated with another signal.

Two antenna ports are said to be QCL if the Long Term Property of the channel on which one symbol on one antenna port is carried can be inferred from the channel on which one symbol on the other antenna port is carried. .. The long term characteristics of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, when the antenna port 1 and the antenna port 2 are QCL with respect to the average delay, it means that the reception timing of the antenna port 2 can be inferred from the reception timing of the antenna port 1.

-This QCL can be extended to beam management. Therefore, the QCL extended to the space may be newly defined. For example, as the long-term property of the channel in the assumption of QCL in the spatial domain, the arrival angle (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) in the wireless link or the channel and/or the angular spread (Angle Spread, for example ASA (Angle Spread Arrival) and ZSA (Zenith angle Spread of Arrival)), transmission angle (AoD, ZoD, etc.) and its angular spread (Angle Spread, for example ASD (Angle ZenithangleSpreadofDeparture)), spatial correlation (SpatialCorrelation), and reception spatial parameters.

For example, when it can be considered that the reception spatial parameter is QCL between the antenna port 1 and the antenna port 2, the reception beam (reception spatial filter) that receives the signal from the antenna port 1 receives the signal from the antenna port 2 from the reception beam. It means that the beam can be inferred.

-As the QCL type, a combination of long-term characteristics that may be regarded as QCL may be defined. 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 parameter The above QCL type is RRC and/or The assumption of QCL between one or two reference signals and PDCCH or PDSCH DMRS may be set and/or indicated as a transmission configuration indication (TCI) in the MAC layer and/or DCI. For example, when the index #2 of the SS/PBCH block and the QCL type A+QCL type B are set and/or instructed as one state of the TCI when the terminal device 1 receives the PDCCH, the terminal device 1 determines that the PDCCH DMRS When receiving the SS/PBCH block index #2, the Doppler shift, the Doppler spread, the average delay, the delay spread, the reception space parameter and the long-term characteristics of the channel are regarded as the DMRS of the PDCCH to receive the synchronization and the propagation path. You may make an estimate. At this time, the reference signal (SS/PBCH block in the above example) designated by the TCI is the source reference signal, and the reference is influenced by the long-term characteristic inferred from the long-term characteristic of the channel when the source reference signal is received. The signal (PDCCH DMRS in the above example) may be referred to as the target reference signal. Further, the TCI may have one or more TCI states in RRC and a combination of a source reference signal and a QCL type for each state, and may be instructed to the terminal device 1 by the MAC layer or DCI.

By this method, even if the operation of the base station apparatus 3 and the terminal apparatus 1 equivalent to the beam management is defined by the assumption of the QCL in the spatial domain and the radio resource (time and/or frequency) as the beam management and the beam instruction/report. Good.

The following describes the subframe. Although referred to as a subframe in this embodiment, it may be referred to as a resource unit, a radio frame, a time section, a time interval, or the like.

FIG. 3 is a diagram showing an example of a schematic configuration of an uplink and a downlink slot 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. Further, one slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms. The time length of each slot is defined by the 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 spacing is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. Further, for example, when X=14, W=10 when the subcarrier spacing is 15 kHz, and W=40 when the subcarrier spacing is 60 kHz. FIG. 3 shows the case where X=7 as an example. It should be noted that the same can be extended when X=14. In addition, the uplink slot is defined similarly, and the downlink slot and the uplink slot may be defined separately. Further, the bandwidth of the cell in FIG. 3 may be defined as a part of the band (BWP: BandWidth Part). Further, the slot may be defined as a transmission time interval (TTI: Transmission Time Interval). Slots may not be defined as TTIs. The TTI may be a transport block transmission period.

The signal or physical channel transmitted in each of the slots may be represented by a resource grid. The resource grid is defined by a plurality of subcarriers and a plurality of OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers forming one slot depends on the downlink and uplink bandwidths of the cell. Each of the elements in the resource grid is called a resource element. Resource elements may be identified using subcarrier numbers and OFDM symbol numbers.

A resource grid is used to represent mapping of resource elements of a certain physical downlink channel (PDSCH etc.) or uplink channel (PUSCH etc.). For example, when the subcarrier interval 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 has 14 consecutive OFDM symbols in the time domain and in the frequency domain. It is defined by 12*Nmax consecutive subcarriers. Nmax is the maximum number of resource blocks determined by the subcarrier interval setting μ described later. That is, the resource grid is composed of (14*12*Nmax, μ) resource elements. In the case of ECP (Extended CP), since it is supported only in the subcarrier interval of 60 kHz, one physical resource block is, for example, 12 (the number of OFDM symbols included in one slot)*4 (included in one subframe in the time domain. Number of slots)=48 consecutive OFDM symbols and 12*Nmax, μ consecutive subcarriers in the frequency domain. That is, the resource grid is composed of (48*12*Nmax, μ) resource elements.

Reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined as resource blocks. One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may constitute a resource block with a subcarrier interval of 15 kHz, for example, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (point A) (may be simply referred to as “reference point”). The common resource block is a resource block numbered in ascending order from 0 in each subcarrier interval setting μ from the reference point A. The resource grid described above is defined by this common resource block. The physical resource blocks are resource blocks numbered in ascending order from 0 included in the band part (BWP) described later, and the physical resource blocks are in ascending order from 0 included in the band part (BWP). It is a numbered resource block. A physical uplink channel is first mapped to a virtual resource block. The virtual resource block is then mapped to the 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.

Next, the subcarrier interval setting μ will be described. As mentioned above, NR supports one or more OFDM numerologies. In a certain BWP, the subcarrier interval setting μ (μ=0, 1,..., 5) and the cyclic prefix length are given to the downlink BWP in the upper layer (upper layer), and are set in the uplink. It is given in the upper layers in BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf=2^μ·15 (kHz).

At the subcarrier spacing setting μ, slots are counted in ascending order from 0 to N^{subframe,μ}_{slot}-1 in the subframe, and 0 to N^{frame,μ}_{slot in the frame. }-1 are counted in ascending order. There are N^{slot}_{symb} consecutive OFDM symbols in the slot based on the slot settings and the cyclic prefix. N^{slot}_{symb} is 14. The start of slot n^{μ}_{s} in a subframe is the start and time of the n^{μ}_{s} N^{slot}_{symb}th OFDM symbol in the same subframe. It is aligned.

Next, I will explain subframes, slots, and minislots. FIG. 4 is a diagram showing the relationship between subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. The subframe is 1 ms regardless of the subcarrier interval, the number of OFDM symbols included in the slot is 7 or 14, and the slot length differs depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, one subframe includes 14 OFDM symbols. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot may be referred to as PUSCH mapping type A.

A minislot (may be referred to as a subslot) is a time unit composed of fewer OFDM symbols than the number of OFDM symbols included in the slot. The figure shows the case where the minislot is composed of two OFDM symbols as an example. The OFDM symbols in a minislot may match the OFDM symbol timing that makes up the slot. The minimum unit of scheduling may be a slot or a minislot. Also, assigning minislots may be referred to as non-slot based scheduling. Further, scheduling a minislot may be expressed as scheduling a resource having a fixed relative time position between a reference signal and a data start position. The downlink minislot may be referred to as PDSCH mapping type B. The uplink minislot may be referred to as PUSCH mapping type B.

FIG. 5 is a diagram showing an example of the slot format. Here, the case where the slot length is 1 ms at a subcarrier interval of 15 kHz is shown as an example. In the figure, D indicates the downlink and U indicates the uplink. As shown in the figure, within a certain time period (for example, the minimum time period that must be assigned to one UE in the system),
It may include one or more of a downlink symbol, a flexible symbol, and an uplink symbol. Note that these ratios may be predetermined as a slot format. Further, it may be defined by the number of downlink OFDM symbols included in the slot or the start position and end position in the slot. Further, it may be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included in the slot or the start position and end position in the slot. Note that scheduling a slot may be expressed as scheduling a resource in which the relative time position between the reference signal and the slot boundary is fixed.

The terminal device 1 may receive a downlink signal or a downlink channel with a downlink symbol or a flexible symbol. The terminal device 1 may transmit an uplink signal or a downlink channel with an uplink symbol or a flexible symbol.

5A may also be referred to as a certain time section (for example, a minimum unit of time resources that can be assigned to one UE, a time unit, or the like. Further, a plurality of minimum units of time resources are bundled and referred to as a time unit. 5B), all of them are used for downlink transmission. In FIG. 5B, uplink scheduling is performed via the PDCCH in the first time resource, and the processing delay of the PDCCH and the downlink are performed. The uplink signal is transmitted via the flexible symbol including the uplink switching time and the generation of the transmission signal. FIG. 5(c) is used for transmitting the PDCCH and/or the downlink PDSCH in the first time resource, and the PUSCH or the PUCCH is used through the processing delay, the switching time from the downlink to the uplink, and the gap for generating the transmission signal. It is used to send. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and/or CSI, that is, UCI. FIG. 5(d) is used for transmission of PDCCH and/or PDSCH in the first time resource, and has processing delay, downlink to uplink switching time, and uplink PUSCH and/or via a gap for generation of a transmission signal. Alternatively, it is used for PUCCH transmission. Here, as an example, the uplink signal may be used for transmission of uplink data, that is, UL-SCH. FIG. 5E is an example in which all are used for uplink transmission (PUSCH or PUCCH).

The downlink part and the uplink part described above may be composed of a plurality of OFDM symbols as in LTE.

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

Hereinafter, the band part (BWP, Bandwidth part) will be described. BWP is also referred to as carrier BWP. BWP may be set for each of the downlink and the uplink. BWP is defined as a set of contiguous physical resources selected from a contiguous subset of common resource blocks. The terminal device 1 can set up to four BWPs in which one downlink carrier BWP (DL BWP) is activated at a certain time. The terminal device 1 can set up to four BWPs in which one uplink carrier BWP (UL BWP) is activated at a certain time. In the case of carrier aggregation, 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 the case where no BWP is set. Further, the setting of two or more BWPs may be expressed as the BWP being set.
<MAC entity operation>
There is always one active (activated) BWP in an activated serving cell. BWP switching for a serving cell is used to activate an inactive (deactivated) BWP and deactivate an active (activated) BWP. To be done. BWP switching for a serving cell is controlled by PDCCH indicating downlink allocation or uplink grant. BWP switching for a serving cell may also be controlled by the BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of the random access procedure. Upon addition of SpCell (PCell or PSCell) or activation of SCell, one BWP is first active without receiving PDCCH indicating downlink allocation or uplink grant. The first active DL BWP (first active DL BWP) and the UL BWP (first active UL BWP) may be specified in the RRC message sent from the base station device 3 to the terminal device 1. The active BWP for a certain serving cell is designated by the RRC or PDCCH sent from the base station device 3 to the terminal device 1. Also, the first active DL BWP (first active DL BWP) and the UL BWP (first active UL BWP) may be included in the message 4. In an unpaired spectrum (TDD band, etc.), DL BWP and UL BWP are paired, and BWP switching is common to UL and DL. In the active BWP for each of the activated serving cells for which the BWP is set, the MAC entity of the terminal device 1 applies the normal process. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. In the inactive BWP for each of the activated serving cells in which the BWP is set, the MAC entity of the terminal device 1 does not transmit the UL-SCH, does not transmit the RACH, does not monitor the PDCCH, does not transmit the PUCCH, Does not send SRS and does not receive DL-SCH. If a serving cell is deactivated, no active BWP may be present (eg, active BWP is deactivated).
<RRC operation>
The BWP information element (IE) included in the RRC message (system information notified or information sent by the dedicated RRC message) is used to set 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) has at least one downlink BWP and one (if the serving cell is configured for uplink) or two (supplementary uplink in the Appendix). Is set), at least an initial BWP (initial BWP) including an uplink BWP (for example, is used) is set for the terminal device 1. In addition, the network may configure additional uplink BWP or downlink BWP for certain serving cells. The BWP setting is divided into an uplink parameter and a downlink parameter. In addition, the BWP setting is divided into a common parameter and a dedicated parameter. Common parameters (such as BWP uplink common IE and 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 common parameters on dedicated signals. 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.

If the upper layer parameter initialDownlinkBWP is not set (provided) for the terminal device 1, the initial DL BWP (initial active DL BWP, initial active DL BWP) is the control resource set (CORESET) for the type 0 PDCCH common search space. It may be defined by the position and number of consecutive PRBs, subcarrier spacing, and cyclic prefix for PDCCH reception in. The positions of the consecutive PRBs start from the PRB with the smallest index and end with the PRB with the largest index among the PRBs of the control resource set for the type 0 PDCCH common search space. When the upper layer parameter initialDownlinkBWP is set (provided) for the terminal device 1, the initial DL BWP may be indicated by the upper layer parameter initialDownlinkBWP. The upper layer parameter initialDownlinkBWP may be included in SIB1 (systemInformationBlockType1, ServingCellConfigCommonSIB) or ServingCellCongfigCommon. The information element ServingCellCongfigureCommon SIB is used to set the cell-specific parameter of the serving cell for the terminal device 1 in the SIB1.

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

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

An initial UL BWP may be provided to the terminal device 1 by SIB1 (systemInformationBlockType1) or initialUplinkBWP. The information element initialUplinkBWP is used to set the initial UL BWP. For the operation in the SpCell or the secondary cell, the terminal device 1 may be set (provided) with an initial UL BWP (initial active UL BWP) by the upper layer parameter initialUplinkBWP. When a supplementary uplink carrier (supplementary UL carrier) is set for the terminal device 1, the terminal device 1 uses the initialUplinkBWP included in the upper layer parameter supplementaryUplink to set the initial UL on the supplementary uplink carrier. BWP may be set.

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

Control resource set (CORESET, Control resource set) is a time and frequency resource for searching downlink control information. The setting information of CORESET includes information for identifying the CORESET identifier (ControlResourceSetId, CORESET-ID) and the frequency resource of CORESET. The information element ControlResourceSetId (identifier of CORESET) is used to specify the control resource set in a certain serving cell. The CORESET identifier is used between BWPs in a serving cell. The CORESET identifier is unique between BWPs in the serving cell. The number of CORESETs for each BWP is limited to 3, including the initial CORESET. In a certain serving cell, the value of the identifier of CORESET takes a value from 0 to 11.

The control resource set specified by the CORESET identifier 0 (ControlResourceSetId 0) is called CORESET#0. CORESET#0 may be set by pdchch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellCongfigCommon. That is, the setting information of CORESET#0 may be pdcch-ConfigSIB1 included in the MIB, or PDCCH-ConfigCommon included in the ServingCellCongfigCommon. The setting information of CORESET#0 may be set 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. CORESET indicated by pdcch-ConfigSIB1 is CORESET#0. The information element pdcch-ConfigSIB1 in the MIB or the dedicated configuration is used to set the initial DL BWP. In the CORESET setting information pdcch-ConfigSIB1 for CORESET#0, the CORESET identifier, the CORESET frequency resource (for example, the number of consecutive resource blocks), and the time resource (the number of consecutive symbols) are explicitly specified. Although the information is not included, the frequency resource (for example, the number of consecutive resource blocks) and the time resource (the number of consecutive symbols) of CORESET for CORESET#0 are implicitly indicated by the information included in pdcch-ConfigSIB1. Can be specified. The information element PDCCH-ConfigCommon is used to set cell-specific PDCCH parameters provided in SIB. Further, PDCCH-ConfigCommon may be provided at the time of handover and addition of PSCell and/or SCell. The setting information of CORESET#0 is included in the setting of the initial BWP. That is, the setting information of CORESET#0 does not need to be included in the setting of BWP other than the initial BWP. The controlResourceSetZero corresponds to 4 bits (for example, 4 bits of MSB and 4 bits of most significant bit) of pdcch-ConfigSIB1. CORESET#0 is a control resource set for the type 0 PDCCH common search space.

The setting information of the additional common CORESET (additional common control resource set) may be set by the commonControlResourceSet included in the PDCCH-ConfigCommon. Also, the additional common CORESET configuration information may be used to specify additional common CORESET for system information and/or paging procedures. The setting information of the additional common CORESET may be used to specify the additional common CORESET used in the random access procedure. The setting information of the additional common CORESET may be included in the setting of each BWP. The identifier of CORESET shown in commonControlResourceSet takes a value other than 0.

The common CORESET may be a CORESET used for the random access procedure (for example, an additional common CORESET). Further, in the present embodiment, the common CORESET may include CORESET#0 and/or CORESET set by the additional common CORESET setting information. That is, common CORESET may include CORESET#0 and/or additional common CORESET. CORESET#0 may be referred to as common CORESET#0. The terminal device 1 and the BWP other than the BWP in which the common CORESET is set may also refer to (acquire) the setting information of the common CORESET.

The setting information of one or more CORESETs may be set by PDCCH-Config. The information element PDCCH-Config is used to set UE-specific PDCCH parameters (eg, CORSET, search space, etc.) for a certain BWP. PDCCH-Config may be included in the settings of each BWP.

That is, in the present embodiment, the common CORESET setting information indicated by MIB is pdcch-ConfigSIB1, the common CORESET setting information indicated by PDCCH-ConfigCommon is controlResourceSetZero, and the common CORESET (additional common RESET indicated by PDCCH-ConfigCommon. The setting information of the common CORESET) is commonControlResourceSet. Also, the setting information of one or more CORESETs (UE-specifically configured Control Resource Sets, UE-specific CORESET) indicated by PDCCH-Config is controlResourceSetToAddModList.

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

The search space setting information includes the CORESET identifier specified by the CORESET setting information. The CORESET specified by the CORESET identifier included in the search space setting information is associated with the search space. In other words, CORESET associated with the search space is CORESET specified by the identifier of CORESET included in the search space. The DCI format indicated by the setting information of the search space is monitored by the associated CORESET. Each search space is associated with one CORESET. For example, the search space setting information for the random access procedure may be set by ra-SearchSpace. That is, the DCI format to which the CRC scrambled by RA-RNTI or TC-RNTI is added in CORESET associated with ra-SearchSpace is monitored.

As described above, the setting information of CORESET#0 is included in the setting of the initial DL BWP. The setting information of CORESET#0 may not be included in the setting of BWP (additional BWP) other than the initial DLBWP. When a BWP other than the initial DL BWP (additional BWP) refers to the setting information of CORESET#0 (refer, acquire, etc.), CORESET#0 and the SS block are included in the additional BWP in the frequency domain, and It may be necessary to at least satisfy using the same subcarrier spacing. In other words, when a BWP other than the initial BWP (additional BWP) refers to the setting information of CORESET#0 (refer, acquire, etc.), the bandwidth of the initial DL BWP and the SS block are It may be necessary to at least meet the requirements of being included in the additional BWP and using the same subcarrier spacing. At this time, the search space (for example, ra-SearchSpace) set for the additional BWP refers to the setting information of CORESET#0 by indicating the identifier 0 of CORESET#0 (refer, acquire, etc.). be able to. That is, at this time, CORESET#0 is set only for the initial DL BWP, but the terminal device 1 operating with another BWP (additional BWP) refers to the setting information of CORESET#0. You can In addition, when the bandwidth of the initial DL BWP is included in the additional DL BWP in the frequency domain, the SS block is included in the additional DL BWP, and one of the conditions using the same subcarrier spacing is not satisfied. The terminal device 1 does not have to expect that the additional DL BWP refers to the setting information of CORESET#0. That is, in this case, the base station apparatus 3 does not have to set the terminal apparatus 1 so that the additional DL BWP refers to the setting information of CORESET#0. Here, the initial DL BWP may be a size N ^size _BWP, an initial DL BWP of ₀ .

When a (additional) DL BWP refers to (SET, acquire, etc.) the setting information of the CORESET of another BWP, the CORESET (or the bandwidth of the BWP) and/or the BWP is included in the frequency domain ( It may be necessary to at least satisfy that the (related) SS blocks are included in the additional BWP and use the same subcarrier spacing. That is, in the frequency domain, the CORESET (or the bandwidth of the BWP) is included in the additional DL BWP, and the SS block included (related) in the BWP is included in the additional DL BWP, and the same sub If any of the conditions using the carrier interval is not satisfied, the terminal device 1 does not have to expect that the additional DL BWP refers to the setting information of CORESET set for the BWP.

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 refers to decoding each PDCCH candidate depending on the DCI format or formats being monitored. A set of PDCCH candidates monitored by the terminal device 1 is defined by a PDCCH search space set). 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 called a search space, the common search space set is called a common search space, and the UE-specific search space set is called a UE-specific search space. The terminal device 1 monitors PDCCH candidates with one or more of the following search space sets.
-Type 0 PDCCH common search space set: This search space set is indicated by pdcch-ConfigSIB1 or PDCCH-ConfigCommon indicated by MIB, which is an upper layer parameter. The search space SIB1 (searchSpaceSIB1) or search space zero (searchSpaceZero) included in PDCCH-ConfigCommon is set. This search space is for monitoring the SI-RNRI scrambled CRC DCI format in the primary cell.
-Type 0A PDCCH common search space set (a Type0A-PDCCH common search space set): This search space set is set by the search space (searchSpaceOtherSystemInformation) indicated by PDCCH-ConfigCommon, which is a parameter of the upper layer. To be done. This search space is for monitoring the SI-RNRI scrambled CRC DCI format in the primary cell.
-Type 1 PDCCH common search space set (a Type1-PDCCH common search space set): This search space set is a search for a random access procedure indicated by PDCCH-ConfigCommon, which is an upper layer parameter. Set by space (ra-SearchSpace ). This search space is for monitoring the DCI format of the CRC scrambled with RA-RNRI or TC-RNTI in the primary cell. The Type 1 PDCCH common search space set is a search space set for a random access procedure.
-A Type2-PDCCH common search space set: This search space set is a search space for a paging procedure indicated by PDCCH-ConfigCommon, which is an upper layer parameter. Set by (pagingSearchSpace). This search space is for monitoring the DCI format of the P-RNTI scrambled CRC in the primary cell.
-Type 3 PDCCH common search space set (a Type3-PDCCH common search space set): This search space set is a search space whose search space type indicated by PDCCH-Config, which is an upper layer parameter, is common. Set by (SearchSpace). This search space is for monitoring the DCI format of the CRC scrambled with 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 C-RNTI, CS-RNTI(s), or MSC-C-RNTI scrambled CRC.

-UE-specific search space set (aUE-specific search space set): In this search space set, the search space type indicated by PDCCH-Config, which is an upper layer parameter, is set by the UE-specific search space (SearchSpace) .. This search space is for monitoring DCI format of C-RNTI, CS-RNTI(s) or CRC scrambled with MSC-C-RNTI.

If the terminal device 1 is provided with one or a plurality of search space sets by the corresponding upper layer parameters (searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.), the terminal device 1 will receive the C-RNTI or When CS-RNTI is provided, the terminal device 1 monitors PDCCH candidates for DCI format0_0 and DCI format1_0 having C-RNTI or CS-RNTI in the one or more search space sets. May be.

BWP setting information is divided into DL BWP setting information and UL BWP setting information. The BWP setting information includes an information element bwp-Id (BWP identifier). The BWP identifier included in the DL BWP setting information is used to identify (reference) the DL BWP in a certain serving cell. The BWP identifier included in the UL BWP setting information is used to identify (reference) the UL BWP in a certain serving cell. The BWP identifier is assigned to each of the DL BWP and UL BWP. For example, the identifier of the BWP corresponding to the DL BWP may be referred to as the DL BWP index. The BWP identifier corresponding to the UL BWP may be referred to as the UL BWP index (ULBWP index). The initial DL BWP is referenced by the DL BWP identifier 0. The initial UL BWP is referenced by the UL BWP identifier 0. Each of the other DL BWPs or the other UL BWPs may be referred to from the BWP identifier 1 to maxNrofBWPs. That is, the BWP identifier (bwp-Id=0) set to 0 is associated with the initial BWP and cannot be used for another BWP. maxNrofBWPs is the maximum number of BWPs per serving cell and is 4. That is, the value of the other BWP identifier takes a value from 1 to 4. The setting information of the other upper layer is associated with a specific BWP by using the BWP identifier. Having DL BWP and UL BWP having the same BWP identifier may mean that DL BWP and UL BWP are paired.

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

The following explains the procedure for receiving PDSCH.

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

The types of PDSCH mapping have PDSCH mapping type A and PDSCH mapping type B. In PDSCH mapping type A, S takes values from 0 to 3. L takes a value from 3 to 14. However, the sum of S and L takes values from 3 to 14. In PDSCH mapping type B, S takes values from 0 to 12. L takes one value from {2, 4, 7}. However, the sum of S and L takes a value from 2 to 14.

The location of the DMRS symbol for PDSCH depends on the type of PDSCH mapping. The position of the first DMRS symbol for PDSCH depends on the type of PDSCH mapping. In PDSCH mapping type A, the position of the first DMRS symbol may be indicated in the upper layer parameter dmrs-TypeA-Position. That is, the upper layer parameter dmrs-TypeA-Position is used to indicate the position of the first DMRS for PDSCH or PUSCH. dmrs-TypeA-Position is set to either'pos2' or'pos3'. For example, when dmrs-TypeA-Position is set to'pos2', the position of the first DMRS symbol for PDSCH may be the third symbol in the slot. For example, when dmrs-TypeA-Position is set to'pos3', the position of the first DMRS symbol for PDSCH may be the fourth symbol in the slot. Here, S can take the value of 3 only when dmrs-TypeA-Position is set to'pos3'. That is, if dmrs-TypeA-Position is set to'pos2', S takes a value from 0 to 2. In PDSCH mapping type B, the position of the first DMRS symbol is the first symbol of the PDSCH assigned.

FIG. 7 is a diagram showing an example of the PDSCH mapping type according to the present embodiment. FIG. 7A is a diagram showing an example of PUSCH mapping type A. In FIG. 7A, the S of PDSCH to be assigned is 3. The L of PDSCH allocated is 7. In FIG. 7(A), the position of the first DMRS symbol for PDSCH is the fourth symbol in the slot. That is, dmrs-TypeA-Position is set to "pos3". FIG. 7B is a diagram showing an example of DPSCH mapping type A. In FIG. 7B, the S of PDSCH to be assigned is 4. The L of PDSCH allocated is 4. In FIG. 7B, the position of the first DMRS symbol for PDSCH is the first symbol to which PDSCH is assigned.

The method for identifying PDSCH time domain resource allocation will be described below.

The base station device 3 may schedule the terminal device 1 to receive PDSCH by DCI. The terminal device 1 may receive the PDSCH by detecting the DCI addressed to the terminal device 1. When identifying the PDSCH time domain resource allocation, the terminal device 1 first determines the resource allocation table to be applied to the PDSCH. The resource allocation table includes one or more PDSCH time domain resource allocation configurations. The terminal device 1 may select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource assignment' field included in the DCI that schedules the PDSCH. That is, the base station device 3 determines the resource allocation of the PDSCH to the terminal device 1, generates the'Time domain resource assignment' field of the value based on the determined resource allocation, and the DCI including the'Time domain resource assignment' field. Is transmitted to the terminal device 1. The terminal device 1 identifies the resource allocation in the time direction of PDSCH based on the value of the'Time domain resource assignment' field.

FIG. 10 is a diagram defining a resource allocation table applied to PDSCH time domain resource allocation. The terminal device 1 may determine the resource allocation table to be applied to PDSCH time domain resource allocation based on the table shown in FIG. The resource allocation table includes one or more PDSCH time domain resource allocation configurations. In the present embodiment, the resource allocation table is classified into (I) a resource allocation table defined in advance and (II) a resource allocation table configured from an RRC signal of an upper layer. The resource allocation table defined in advance is defined as, for example, a default PDSCH time domain resource allocation A, a default PDSCH time domain resource allocation B, and a default PDSCH time domain resource allocation C. Hereinafter, the default PDSCH time domain resource allocation A will be referred to as the default table A. The default PDSCH time domain resource allocation B is called default table B. The default PDSCH time domain resource allocation C is called default table C.

FIG. 11 is a diagram showing an example of the default table A according to this embodiment. FIG. 12 is a diagram showing an example of the default table B according to this embodiment. FIG. 13 is a diagram showing an example of the default table C according to this embodiment. In the example of FIG. 11, the number of rows of the default table A is 16, and each row shows the configuration of PDSCH time domain resource allocation. In FIG. 11, each row (indexed row) is a PDSCH mapping type, a slot offset K ₀ between the PDCCH including the DCI and the PDSCH, a start symbol S of the PDSCH in the slot, and continuous allocation. The number of symbols L to be defined is defined.

The resource allocation table set by the RRC signal of the upper layer is given by the signal pdsch-TimeDomainAllocationList of the upper layer. The pdsch-TimeDomainAllocationList includes one or more information elements PDSCH-TimeDomainResourceAllocation. PDSCH-TimeDomainResourceAllocation indicates the setting of PDSCH time domain resource allocation. PDSCH-TimeDomainResourceAllocation may be used to set a time domain relationship between the PDCCH including the DCI and the PDSCH. That is, pdsch-TimeDomainAllocationList is a list containing one or more information elements. One PDSCH-TimeDomainResourceAllocation may be referred to as one entry (or one row). For example, pdsch-TimeDomainAllocationList includes a maximum of 16 entries, and any one entry may be used depending on a 4-bit field included in DCI. However, the number of entries included in the pdsch-TimeDomainAllocationList may be different, and the number of bits of the fields included in the DCI associated therewith may be different values. In each entry of pdsch-TimeDomainAllocationList, K ₀ , mappingType, and/or startSymbolAndLength may be indicated. K ₀ indicates the slot offset between the PDCCH containing the DCI and its PDSCH. When K ₀ is not indicated by PDSCH-TimeDomainResourceAllocation, the terminal device 1 may assume that the value of K ₀ is a predetermined value (for example, 0). The mappingType indicates whether the corresponding PDSCH mapping type is the PDSCH mapping type A or the PDSCH mapping type B. The startSymbolAndLength is an index that gives a valid combination of the start symbol S of the corresponding PDSCH and the number L of consecutively allocated symbols. The startSymbolAndLength may be referred to as a start position and length indicator (SLIV). When SLIV is applied, unlike the case where the default table is used, the start symbol S of the corresponding PDSCH and the number of consecutive symbols L are given based on SLIV. The base station apparatus 3 may set the value of SLIV so that the time domain resource allocation of PDSCH does not exceed the slot boundary. The slot offset K ₀ and SLIV will be described later.

The upper layer signal pdsch-TimeDomainAllocationList may be included in pdsch-ConfigCommon and/or pdsch-Config. The information element pdsch-ConfigCommon is used to set the cell-specific parameters for PDSCH for a certain BWP. Information element pdsch-Config is used to set UE specific parameters for PDSCH for a certain BWP.

FIG. 14 is a diagram showing an example of calculating SLIV.

In FIG. 14, 14 is the number of symbols included in one slot. FIG. 14 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 included in the slot, the start symbol S, and the number L of consecutive symbols. Here, the value of L is equal to or greater than 1 and does not exceed (14-S). When calculating SLIV by ECP, 6 and 12 are used instead of the values 7 and 14 in FIG.

The slot offset K ₀ will be described below.

As described above, at the subcarrier spacing setting μ, slots are counted in ascending order from 0 to N^{subframe, μ}_{slot}-1 in the subframe, and 0 to N^{frame, in the frame. Counted in ascending order to μ}_{slot}-1. K ₀ is the number of slots based on the PDSCH subcarrier spacing. K ₀ can take values from 0 to 32. FIG. 15 is a diagram illustrating an example in which the DCI schedules PDSCH. The slot length depends on the subcarrier interval setting μ. FIG. 15A shows slot numbers corresponding to a subcarrier spacing of 30 kHz (μ=1). FIG. 15B shows slot numbers corresponding to a subcarrier interval of 15 kHz (μ=0). In a certain subframe or frame, slot numbers are counted in ascending order from 0. The slot number n of the subcarrier interval setting of 15 kHz corresponds to the slot numbers 2n and 2n+1 of the subcarrier interval setting of 30 kHz.

The terminal device 1 detects the DCI that schedules the PDSCH. The slot assigned to the PDSCH is given by (Equation 1) Floor(n*2 ^μPDSCH /2 ^μPDCCH )+K ₀ . The function Floor(A) outputs the largest integer that does not exceed A. n is a slot in which the PDCCH that schedules the PDSCH is detected. μ _PDSCH is a subcarrier interval setting for _PDSCH . μ _PDCCH is a subcarrier interval setting for _PDCCH .

For example, the subcarrier interval for PDCCH including DCI is 15 kHz (μ _PDCCH =0). The subcarrier interval for PDSCH scheduled by the DCI is 15 kHz (μ _PDSCH =0). The terminal device 1 detects the PDCCH (701) including DCI in the slot n. If K ₀ is 0, the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot n based on (Equation 1). In this case, the PDSCH scheduled by the DCI (701) may be the PDSCH (702) in slot n corresponding to the subcarrier interval of 15 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot n+1 based on (Equation 1). In this case, the PDSCH scheduled by that DCI (701) is the PDSCH (703) in slot n+1 corresponding to the subcarrier interval of 15 kHz.

Further, for example, the subcarrier interval for the PDCCH including DCI is 15 kHz (μ _PDCCH =0). The subcarrier interval for PDSCH scheduled by the DCI is 30 kHz (μ _PDSCH =1). The terminal device 1 detects the PDCCH (701) including DCI in the slot n. If K ₀ is 0, the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot 2n based on (Equation 1). In this case, the PDSCH scheduled by the DCI (701) is the PDSCH (705) in the slot 2n corresponding to the subcarrier interval of 30 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by that DCI (701) is given as slot 2n+1 based on (Equation 1). In this case, the PDSCH scheduled by the DCI (701) is the PDSCH (706) in slot 2n+1 corresponding to the subcarrier interval of 30 kHz.

Further, for example, the subcarrier interval for the PDCCH including DCI is 30 kHz (μ _PDCCH =1). The subcarrier interval for PDSCH scheduled by the DCI is 15 kHz (μ _PDSCH =0). The terminal device 1 detects the PDCCH (704) including DCI in the slot 2n corresponding to the subcarrier interval of 30 kHz. If K ₀ is 0, the slot assigned to the PDSCH scheduled by that DCI (704) is given as slot n based on (Equation 1). In this case, the PDSCH scheduled by the DCI (704) may be the PDSCH (702) in slot n corresponding to the subcarrier interval of 15 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by that DCI (704) is given as slot n+1 based on (Equation 1). In this case, the PDSCH scheduled by that DCI (704) is the PDSCH (703) in slot n+1 corresponding to the subcarrier interval of 15 kHz.

As described above, the terminal device 1 may determine which one of the resource allocation tables is applied to PDSCH time domain resource allocation with reference to FIG. 10. That is, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by DCI based on at least some or all of the following elements (A) to (F).

Element A: RNTI type that scrambles CRC attached to DCI Element B: Type of search space in which DCI is detected Element C: Whether CORESET associated with that search space is CORESET#0 Element D: pdsch- Whether ConfigCommon contains pdsch-TimeDomainAllocationList Element E: Whether pdsch-Config contains pdsch-TimeDomainAllocationList Element F: SS/PBCH and CORESET multiple pattern In element A, the type of RNTI that scrambles the CRC attached to DCI is , SI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, C-RNTI, MCS-C-RNTI, or CS-RNTI.

In element B, the type of search space in which DCI is detected is a common search space or a UE-specific search space. The common search space includes a type 0 common search space, a type 1 common search space, and a type 2 common search space.

As an example A, the terminal device 1 may detect the DCI in an arbitrary common search space associated with CORESET#0. A CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI is added to the detected DCI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by the DCI. When pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the resource allocation table configured from the RRC signal of the upper layer. The resource allocation table is given by pdsch-TimeDomainAllocationList included in pdsch-ConfigCommon. Further, when pdsch-ConfigCommon does not include pdsch-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the default table A. That is, the terminal device 1 may apply the determination of PDSCH time domain resource allocation using the default table A indicating the configuration of PDSCH time domain resource allocation.

Further, as an example B, the terminal device 1 may detect DCI in an arbitrary common search space that is not associated with CORESET#0. A CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI is added to the detected DCI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by the DCI. When pdsch-Config includes pdsch-TimeDomainAllocationList for the terminal device 1, the terminal device 1 assigns the resource allocation table applied to the PDSCH time domain resource allocation to the resource allocation given from the pdsch-TimeDomainAllocationList provided in pdsch-Config. You may decide on the table. That is, when pdsch-Config includes pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-Config regardless of whether or not pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList. It may be applied to the determination of area resource allocation. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-ConfigCommon resource allocation table to apply PDSCH time domain resource allocation. It may be decided in the resource allocation table given from the provided pdsch-TimeDomainAllocationList. That is, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon to apply the PDSCH time domain resource allocation determination. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table applied to PDSCH time domain resource allocation in the default table A. You may decide.

Further, as an example C, the terminal device 1 may detect the DCI in the UE-specific search space. A CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI is added to the detected DCI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by the DCI. When pdsch-Config includes pdsch-TimeDomainAllocationList for the terminal device 1, the terminal device 1 assigns the resource allocation table applied to the PDSCH time domain resource allocation to the resource allocation given from the pdsch-TimeDomainAllocationList provided in pdsch-Config. You may decide on the table. That is, when pdsch-Config includes pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-Config regardless of whether or not pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList. It may be applied to the determination of area resource allocation. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-ConfigCommon resource allocation table to apply PDSCH time domain resource allocation. It may be decided in the resource allocation table given from the provided pdsch-TimeDomainAllocationList. That is, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon to apply the PDSCH time domain resource allocation determination. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table applied to PDSCH time domain resource allocation in the default table A. You may decide.

From Example B and Example C, the method of determining the resource allocation table applied to the PDSCH detected in the UE-specific search space is as follows: This is similar to the method of determining the allocation table.

Subsequently, the terminal device 1 selects one PDSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource allocation' field included in the DCI that schedules the PDSCH. Good. For example, when the resource allocation table applied to PDSCH time domain resource allocation is the default table A, the value m shown in the'Time domain resource assignment' field may be the row index m+1 of the default table A. Good. At this time, PDSCH time domain resource allocation is a configuration of time domain resource allocation indicated by the row index m+1. The terminal device 1 receives the PDSCH, assuming the configuration of time domain resource allocation indicated by the row index m+1. For example, when the value m shown in the'Time domain resource assignment' field is 0, the terminal device 1 is scheduled by its DCI using the PDSCH time domain resource allocation configuration of the row index 1 of the default table A. The resource allocation of the PDSCH in the time direction is specified.

When the resource allocation table applied to PDSCH time domain resource allocation is the resource allocation table given by pdsch-TimeDomainAllocationList, the value m indicated in the'Time domain resource allocation' field is (m+1)th in the list pdsch-TimeDomainAllocationList. Element (entry, line) of. For example, when the value m shown in the'Time domain resource assignment' field is 0, the terminal device 1 may refer to the first element (entry) in the list pdsch-TimeDomainAllocationList. For example, when the value m shown in the'Time domain resource assignment' field is 1, the terminal device 1 may refer to the second element (entry) in the list pdsch-TimeDomainAllocationList.

Below, the number of bits (size) of the'Time domain resource assignment' field included in DCI will be explained.

The terminal device 1 may decode (receive) the corresponding PDSCH by detecting the PDCCH including the DCI format 1_0 or the DCI format 1_1. The number of bits of the'Time domain resource assignment' field included in the DCI format 1_0 may be a fixed number of bits. For example, this fixed number of bits may be four. That is, the size of the'Time domain resource assignment' field included in the DCI format 1_0 is 4 bits. Also, the size of the'Time domain resource assignment' field included in the DCI format 1_1 may be a variable number of bits. For example, the number of bits of the'Time domain resource assignment' field included in the DCI format 1_1 may be any one of 0, 1, 2, 3, 4.

The following describes the determination of the number of bits in the'Time domain resource assignment' field included in DCI format 1_1.

The number of bits of the'Time domain resource assignment' field included in DCI format 1_1 is (I) whether pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList and/or (II) whether pdsch-Config includes pdsch-TimeDomainAllocationList And/or (III) may be provided based at least on the number of rows included in the predefined default table. In the present embodiment, the DCI format 1_1 is added with a CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI. DCI format 1_1 may be detected in the UE-specific search space. In the present embodiment, the meaning of “pdsch-Config includes pdsch-TimeDomainAllocationList” may mean that “pdsch-Config provides pdsch-TimeDomainAllocationList”. The meaning of'pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList' may mean'provided by pdsch-TimeCommonAllocationList in pdsch-ConfigCommon'.

The number of bits in the'Time domain resource assignment' field may be given as ceiling(log ₂ (I)). The function Ceiling(A) outputs the smallest integer not less than A. When pdsch-TimeDomainAllocationList is set (provided) for the terminal device 1, the value of I may be the number of entries included in the pdsch-TimeDomainAllocationList. When pdsch-TimeDomainAllocationList is not set (provided) for the terminal device 1, the value of I may be the number of rows in the default table (default table A). That is, when pdsch-TimeDomainAllocationList is set for the terminal device 1, the number of bits of the Time domain resource assignment' field may be given based on the number of entries included in pdsch-TimeDomainAllocationList. When pdsch-TimeDomainAllocationList is not set for the 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 (default table A). Specifically, when pdsch-Config includes pdsch-TimeDomainAllocationList, the value of I may be the number of entries included in pdsch-TimeDomainAllocationList provided in pdsch-Config. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. May be. If pdsch-Config does not contain pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not contain pdsch-TimeDomainAllocationList, the value of I is the number of rows contained in the default table (eg default table A). May be.

In other words, when pdsch-TimeDomainAllocationList is set (provided) for the terminal device 1, the number of bits of the'Time domain resource assignment' field is given as ceiling(log ₂ (I)). May be. When pdsch-TimeDomainAllocationList is not set (provided) for the terminal device 1, the number of bits of the'Time domain resource assignment' field may be a fixed number of bits. For example, the fixed number of bits may be 4 bits. Here, I may be the number of entries included in the pdsch-TimeDomainAllocationList. Specifically, when pdsch-Config includes pdsch-TimeDomainAllocationList, the value of I may be the number of entries included in pdsch-TimeDomainAllocationList provided in pdsch-Config. When pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. May be.

With this, the terminal device 1 can specify the number of bits of the'Time domain resource assignment' field generated by the base station device 3. That is, the terminal device 1 can correctly receive the PDSCH destined for the terminal device 1 scheduled by the base station device 3.

The following describes the procedure for receiving PUSCH.

The terminal device 1 may transmit the corresponding PUSCH by detecting the DCI format 0_0 or the PDCCH including the DCI format 0_1. That is, the corresponding PUSCH may be scheduled (shown) by its DCI format (DCI). Further, the PUSCH may be scheduled by the RAR UL grant included in the RAR message. The start position (start symbol) of the scheduled PUSCH is called S. The starting symbol S of the PUSCH may be the first symbol in which the PUSCH is transmitted (mapped) in a certain slot. The start symbol S corresponds to the start of the slot. For example, when the value of S is 0, the terminal device 1 may transmit the PUSCH from the first symbol in a certain slot. Further, 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 called L. The number L of consecutive symbols is counted from the start symbol S. The determination of S and L assigned to PUSCH will be described later.

PUSCH mapping types have 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 values from 4 to 14. In PUSCH mapping type B, S takes values from 0 to 13. L takes a value from 1 to 14. However, the sum of S and L takes values from 1 to 14.

The location of the DMRS symbol for PUSCH depends on the type of PUSCH mapping. The position of the first DMRS symbol for PUSCH depends on the type of PUSCH mapping. In PUSCH mapping type A, the position of the first DMRS symbol may be indicated in the upper layer parameter dmrs-TypeA-Position. dmrs-TypeA-Position is set to either'pos2' or'pos3'. For example, if dmrs-TypeA-Position is set to'pos2', the position of the first DMRS symbol for PUSCH may be the third symbol in the slot. For example, if dmrs-TypeA-Position is set to'pos3', the position of the first DMRS symbol for PUSCH may be the fourth symbol in the slot. In PUSCH mapping type B, the position of the first DMRS symbol may be the first symbol of the assigned PUSCH.

The following explains the method of identifying PUSCH time domain resource allocation.

The base station device 3 may schedule the terminal device 1 to transmit the PUSCH by DCI. Then, the terminal device 1 may transmit the PUSCH by detecting the DCI addressed to itself. When identifying the PUSCH time domain resource allocation, the terminal device 1 first determines the resource allocation table to be applied to the PUSCH. The resource allocation table includes one or more PUSCH time domain resource allocation configurations. Next, the terminal device 1 may select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource assignment' field included in the DCI that schedules the PUSCH. Good. That is, the base station device 3 determines the PUSCH resource allocation to the terminal device 1, generates the value of the'Time domain resource assignment' field, and transmits the DCI including the'Time domain resource assignment' field to the terminal device 1. To do. The terminal device 1 identifies the resource allocation in the PUSCH time direction based on the value set in the'Time domain resource assignment' field.

FIG. 16 is a diagram defining a resource allocation table applied to PUSCH time domain resource allocation. The terminal device 1 may determine the resource allocation table applied to PUSCH time domain resource allocation based on the table shown in FIG. The resource allocation table includes configurations of one or more PUSCH time domain resource allocations. In the present embodiment, the resource allocation table is classified into (I) a resource allocation table defined in advance and (II) a resource allocation table configured from an RRC signal of an upper layer. The predefined resource allocation table is defined as the default PUSCH time domain resource allocation A. Hereinafter, the default PUSCH time domain resource allocation A will be referred to as the PUSCH default table A.

FIG. 17 is a diagram showing an example of the PUSCH default table A for NCP (Normal Cyclic Prefix). Referring to FIG. 17, PUSCH default table A includes 16 rows. Each row in the PUSCH default table A shows a PUSCH time domain resource allocation configuration. Specifically, in FIG. 17, the indexed row is a PUSCH mapping type, a slot offset K ₂ between the PDCCH including DCI and the PUSCH, a start symbol S of the PUSCH in the slot, and The number of consecutively allocated symbols L is defined.

The resource allocation table set by the RRC signal of the upper layer is given by the signal push-TimeDomainAllocationList of the upper layer. The information element PUSCH-TimeDomainResourceAllocation indicates the configuration of PUSCH time domain resource allocation. PUSCH-TimeDomainResourceAllocation may be used to set the time domain relationship between the PDCCH including the DCI and the PUSCH. The pusch-TimeDomainAllocationList contains one or more information elements PUSCH-TimeDomainResourceAllocation. That is, push-TimeDomainAllocationList is a list including one or more elements (information elements). One information element PDSCH-TimeDomainResourceAllocation may also be referred to as one entry (or one row). The pusch-TimeDomainAllocationList may contain up to 16 entries. Each entry may be defined by K ₂ , mappingType, and startSymbolAndLength. K ₂ indicates the slot offset between the PDCCH containing the DCI and its scheduled PUSCH. If PUSCH-TimeDomainResourceAllocation does not indicate K ₂ , the terminal device 1 assumes that the value of K ₂ is 1 when the PUSCH subcarrier interval is 15 kHz or 30 kHz, and the PUSCH subcarrier interval is If it is 60 kHz, it assumes that the value of _{K 2} is 2, when the sub-carrier interval of the PUSCH is 120 kHz, may be assumed that the value of _{K 2} is 3. mappingType indicates either PUSCH mapping type A or PUSCH mapping type A. startSymbolAndLength is an index that gives a valid combination of the start symbol S of PUSCH and the number of consecutively allocated symbols L. The startSymbolAndLength may be referred to as a start and length indicator (SLIV). That is, unlike the default table that directly defines the start symbol S and the continuous symbol L, the start symbol S and the continuous symbol L are given based on SLIV. The base station device 3 can set the value of SLIV so that the PUSCH time domain resource allocation does not exceed the slot boundary. The value of SLIV is calculated based on the number of symbols included in the slot, the start symbol S, and the number L of consecutive symbols, as in the formula in FIG.

-The upper layer signal push-TimeDomainAllocationList may be included in push-ConfigCommon and/or push-Config. The information element push-ConfigCommon is used to set the cell-specific parameters for PUSCH for a certain BWP. The information element push-Config is used to set UE specific parameters for PUSCH for a certain BWP.

The terminal device 1 detects DCI which schedules PUSCH. The slot in which the PUSCH is transmitted is given by (Equation 4) Floor(n*2 ^μPUSCH /2 ^μPDCCH )+K ₂ . n is a slot in which the PDCCH that schedules the PUSCH is detected. μ _PUSCH is a subcarrier interval setting for _PUSCH . μ _PDCCH is a subcarrier interval setting for _PDCCH .

In FIG. 17, the value of K ₂ is one of j, j+1, j+2, or j+3. The value of j is a value specified for the PUSCH subcarrier spacing. For example, if the subcarrier spacing to which PUSCH is applied is 15 kHz or 30 kHz, the value of j may be 1 slot. For example, if the subcarrier spacing to which PUSCH is applied is 60 kHz, the value of j may be 2 slots. For example, if the subcarrier spacing to which PUSCH is applied is 120 kHz, the value of j may be 3 slots.

As described above, the terminal device 1 may determine which resource allocation table to apply to PUSCH time domain resource allocation based on the table shown in FIG.

As an example D, the terminal device 1 may determine the resource allocation table to be applied to the PUSCH scheduled by the RAR UL grant (MAC RAR). When push-ConfigCommon includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the resource allocation table set by the RRC signal of the upper layer. The resource allocation table is given by push-TimeDomainAllocationList included in push-ConfigCommon. Further, when push-ConfigCommon does not include push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the PUSCH default table A. That is, the terminal device 1 may use the default table A indicating the configuration of PUSCH time domain resource allocation and apply it to the determination of PUSCH time domain resource allocation.

As an example E, the terminal device 1 may detect a DCI (for example, DCI format 0_0) to which a CRC scrambled by TC-RNTI is added in the common search space (for example, type 1 common search space). The terminal device 1 may determine the resource allocation table applied to the PUSCH scheduled by the DCI. That is, the terminal device 1 determines the resource allocation table applied to the PUSCH scheduled by the DCI, and based on the (m+1)th element (entry, row) in the determined resource allocation table, the time of the PUSCH Region resource allocation may be determined. That is, when the terminal device 1 determines the resource allocation table to be applied to the PUSCH time domain resource allocation scheduled by DCI, if the CRC scrambled by TC-RNTI is added to the DCI, push- Regardless of whether or not the push-TimeDomainAllocationList included in Config is received (set), one may be selected from (I) push-TimeDomainAllocationList included in push-ConfigCommon and (II) PUSCH default table A. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table. As described above, the value of m may be indicated in the'Time domain resource assignment' field included in the DCI. Whether or not the push-TimeDomainAllocationList included in the push-Config is received (set) may mean whether or not the push-Config includes the push-TimeDomainAllocationList. The fact that push-TimeDomainAllocationList included in push-Config is not received may mean that push-Config is not received. The fact that the push-TimeDomainAllocationList included in the push-Config is not received may mean that the push-Config is received, but the push-Config does not include the push-TimeDomainAllocationList. The reception of the push-TimeDomainAllocationList included in the push-Config may mean that the push-Config is received and the received push-Config includes the push-TimeDomainAllocationList.

Specifically, when push-ConfigCommon includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses a push-ConfigCommon provided resource-assignment table that is applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. When push-ConfigCommon does not include push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the resource allocation table applied to the PUSCH time domain resource allocation as the PUSCH default table A.

That is, as an example E, when the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, when the DCI is detected in the type 1 common search space b, Regardless of whether or not the push-TimeDomainAllocationList included in push-Config is received (set), even if one is selected from (I) push-TimeDomainAllocationList included in push-ConfigCommon and (II) PUSCH default table A Good. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table.

Further, as an example F, the terminal device 1 may detect the DCI in an arbitrary common search space associated with CORESET#0. A CRC scrambled by the first RNTI is added to the detected DCI. In the present invention, the first RNTI may be any one of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, and CS-RNTI. That is, when the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, the CRC scrambled by the first RNTI is added to the DCI, and When the DCI is detected in an arbitrary common search space associated with CORESET#0, it is included in (I) push-ConfigCommon regardless of whether the push-TimeDomainAllocationList included in push-Config is received (set). One may be selected from pusch-TimeDomainAllocationList and (II) PUSCH default table A. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table. Specifically, when push-ConfigCommon includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses a push-ConfigCommon provided resource-assignment table that is applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. If push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 may determine the PUSCH default table A as the resource allocation table to be applied to PUSCH time domain resource allocation.

Further, as an example G, the terminal device 1 may detect the DCI in (i) an arbitrary common search space not associated with CORESET#0 or (ii) a UE-specific search space. A CRC scrambled by the first RNTI is added to the detected DCI. In the present invention, the first RNTI may be any one of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, and CS-RNTI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PUSCH scheduled by the DCI. That is, when the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, the CRC scrambled by the first RNTI is added to the DCI, and If the DCI is detected in either (i) any common search space not associated with CORESET#0 or (ii) UE-specific search space, (I) push-TimeDomainAllocationList included in push-ConfigCommon, One may be selected from (II) PUSCH default table A and (III) push-TimeDomainAllocationList included in push-Config. The terminal device 1 may determine the time domain resource allocation of the PUSCH based on the (m+1)th element (entry, row) in the selected resource allocation table. Specifically, when push-Config includes push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 uses the push-Config provided in push-Config as a resource allocation table applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from TimeDomainAllocationList. That is, when push-Config includes push-TimeDomainAllocationList, the terminal device 1 uses the push-TimeDomainAllocationList provided in push-Config regardless of whether push-ConfigCommon includes push-TimeDomainAllocationList. It may be applied to the determination of area resource allocation. When push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList, the terminal device 1 uses the push-ConfigCommon to assign the resource allocation table applied to PUSCH time domain resource allocation. It may be determined in the resource allocation table given from the provided push-TimeDomainAllocationList. That is, the terminal device 1 uses the push-TimeDomainAllocationList provided by push-ConfigCommon to apply the PUSCH time domain resource allocation determination. If push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 uses the PUSCH default table A as the resource allocation table applied to PUSCH time domain resource allocation. May be determined.

Subsequently, the terminal device 1 may select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value indicated in the'Time domain resource assignment' field included in the DCI that schedules the PUSCH. Good. For example, when the resource allocation table applied to PUSCH time domain resource allocation is the PUSCH default table A, the value m shown in the'Time domain resource allocation' field indicates the row index m+1 of the default table A. Good. At this time, the PUSCH time domain resource allocation is a configuration of the time domain resource allocation indicated by the row index m+1. The terminal device 1 transmits the PUSCH assuming a configuration of time domain resource allocation indicated by the row index m+1. For example, when the value m shown in the'Time domain resource assignment' field is 0, the terminal device 1 uses the PUSCH time domain resource allocation configuration of the row index 1 of the PUSCH default table A and schedules it according to its DCI. The resource allocation in the time direction of the PUSCH to be specified is specified.

If the resource allocation table applied to PUSCH time domain resource allocation is the resource allocation table given by push-TimeDomainAllocationList, the value m shown in the'Time domain resource assignment' field is the (m+1)th position in the list pushch-TimeDomainAllocationList. Corresponds to the element (entry, line) of. For example, when the value m shown in the'Time domain resource assignment' field is 0, the terminal device 1 may refer to the first element (entry) in the list push-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 push-TimeDomainAllocationList.

Thereby, the terminal device 1 can determine the time domain resource allocation of the PUSCH scheduled by the DCI based on the upper layer parameters transmitted by the base station device 3 and the transmitted DCI. That is, the terminal device 1 can correctly transmit the PUSCH by using the time domain resource allocation of the PUSCH addressed to the terminal device 1 scheduled by the base station device 3.

Below, the number of bits (size) of the'Time domain resource assignment' field included in DCI will be explained.

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

The following describes the determination of the number of bits in the'Time domain resource assignment' field included in DCI format 0_1.

The number of bits of the'Time domain resource assignment' field included in DCI format 0_1 is (I) whether pushch-ConfigCommon includes pushch-TimeDomainAllocationList and/or (II) whether pushch-Config includes pushch-TimeDomainAllocationList And/or (III) may be provided based at least on the number of rows included in the predefined default table. In this embodiment, the DCI format 0_1 is added with a CRC scrambled by any one of C-RNTI, MCS-C-RNTI, and CS-RNTI. DCI format 0_1 may be detected in the UE-specific search space. In the present embodiment, the meaning of “pusch-Config includes push-TimeDomainAllocationList” may mean “pusch-TimeDomainAllocationList is provided by push-Config”. The meaning of'pusch-ConfigCommon includes pushch-TimeDomainAllocationList' may mean'pusch-ConfigCommon provides pushch-TimeDomainAllocationList'.

The number of bits in the'Time domain resource assignment' field may be given as ceiling(log ₂ (I)). When push-TimeDomainAllocationList is set (provided) for the terminal device 1, the value of I may be the number of entries included in push-TimeDomainAllocationList. When push-TimeDomainAllocationList is not set (provided) for the terminal device 1, the value of I may be the number of rows of the PUSCH default table A. That is, when push-TimeDomainAllocationList is set for the terminal device 1, the number of bits of the Time domain resource assignment' field may be given based on the number of entries included in push-TimeDomainAllocationList. When push-TimeDomainAllocationList is not set for the 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 (default table A). Specifically, when push-Config includes push-TimeDomainAllocationList, the value of I may be the number of entries included in push-TimeDomainAllocationList provided in push-Config. If push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList, the value of I is the number of entries included in push-TimeDomainAllocationList provided by push-ConfigCommon. May be. If push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon does not include push-TimeDomainAllocationList, the value of I may be the number of rows included in PUSCH default table A.

In other words, when the push-TimeDomainAllocationList is set (provided) for the terminal device 1, the number of bits of the'Time domain resource assignment' field is given as ceiling(log ₂ (I)). May be. When push-TimeDomainAllocationList is not set (provided) for the terminal device 1, the number of bits of the'Time domain resource assignment' field may be a fixed number of bits. For example, the fixed number of bits may be 4 bits. Here, I may be the number of entries included in the push-TimeDomainAllocationList. Specifically, when push-Config includes push-TimeDomainAllocationList, the value of I may be the number of entries included in push-TimeDomainAllocationList provided in push-Config. If push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList, the value of I is the number of entries included in push-TimeDomainAllocationList provided by push-ConfigCommon. May be.

With this, the terminal device 1 can specify the number of bits of the'Time domain resource assignment' field generated by the base station device 3. That is, the terminal device 1 can correctly transmit the PUSCH destined for the terminal device 1 scheduled by the base station device 3.

Hereinafter, the random access procedure of this embodiment will be described. Random access procedures are classified into two procedures: contention-based (CB) and contention-free (non-CB) (may be referred to as contention free). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA.
The random access procedure is applicable to (i) transmission of random access preamble (message 1, Msg1) on PRACH, (ii) reception of random access response (RAR) message (message 2, Msg2) with PDCCH/PDSCH, and applicable. In this case, (iii) message 3 PUSCH (Msg3 PUSCH) transmission and (iv) PDSCH reception for collision resolution may be included.

-The contention-based random access procedure is initiated by PDCCH order, MAC entity, notification of beam failure from lower layers, RRC, etc. When the beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, if a certain condition is satisfied, the MAC entity of the terminal device 1 starts a random access procedure. When the beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, it is determined whether a certain condition is satisfied, and the procedure of starting the random access procedure is called a beam failure recovery procedure. May be. This random access procedure is a random access procedure for beam failure recovery request. The random access procedure initiated by the MAC entity includes the random access procedure initiated by the scheduling request procedure. The random access procedure for beam failure recovery request may or may not be considered a random access procedure initiated by a MAC entity. The random access procedure for the beam failure recovery request and the scheduling request procedure are different from each other in the random access procedure started by the scheduling request procedure. Therefore, the random access procedure for the beam failure recovery request and the scheduling request procedure are distinguished. You may do it. The random access procedure for the beam failure recovery request and the scheduling request procedure may be a random access procedure initiated by a MAC entity. In an embodiment, a random access procedure initiated by a scheduling request procedure is referred to as a MAC entity initiated random access procedure, and a random access procedure for a beam failure recovery request is a random access by beam failure notification from a lower layer. You may call it a procedure. Hereinafter, the start of the random access procedure when receiving the beam failure notification from the lower layer may mean the start of the random access procedure for the beam failure recovery request.

The terminal device 1 is in the state of not being connected (communicating) with the base station device 3 at the time of initial access, and/or is being connected to the base station device 3, but is capable of transmitting uplink data or transmission to the terminal device 1. A contention-based random access procedure is performed at the time of scheduling request when possible sidelink data is generated. However, the use of contention-based random access is not limited to these.

The occurrence of uplink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the uplink data that can be transmitted is triggered. The occurrence of the transmittable uplink data in the terminal device 1 may include the pending scheduling request triggered based on the occurrence of the transmittable uplink data.

The occurrence of sidelink data that can be transmitted to the terminal device 1 may include that a buffer status report corresponding to the sidelink data that can be transmitted is triggered. Generation of sidelink data that can be transmitted to the terminal device 1 may include that a scheduling request triggered based on generation of sidelink data that can be transmitted is pending.

The non-contention-based random access procedure may be started when the terminal device 1 receives the information instructing the start of the random access procedure from the base station device 3. The non-contention based random access procedure may be started when the MAC layer of the terminal device 1 receives a beam failure notification from the lower layer.

The non-contention-based random access is performed quickly between the terminal device 1 and the base station device 3 when the base station device 3 and the terminal device 1 are connected but the handover or the transmission timing of the mobile station device is not effective. May be used to establish the uplink synchronization of. The non-contention based random access may be used to transmit a beam failure recovery request when a beam failure occurs in the terminal device 1. However, the use of non-contention based random access is not limited to these.

However, the information for instructing the start of the random access procedure is message 0, Msg. 0, NR-PDCCH order, PDCCH order, etc.

However, when the random access preamble index indicated by the message 0 has a predetermined value (for example, when all bits indicating the index are all 0), the terminal device 1 determines the preamble available to the terminal device 1. A contention-based random access procedure of randomly selecting and transmitting one from the set may be performed.

However, the random access setting information may include information that is common within the cell, and may also include dedicated information that is different for each terminal device 1.

However, part of the random access setting information may be associated with all SS/PBCH blocks in the SS burst set. However, a part of the random access setting information may be associated with all of the set one or more CSI-RSs. However, a part of the random access setting information may be associated with one downlink transmission beam (or beam index).

However, part of the random access setting information may be associated with one SS/PBCH block in the SS burst set. However, a part of the random access setting information may be associated with one of the set one or more CSI-RSs. However, a part of the random access setting information may be associated with one downlink transmission beam (or beam index). However, the information associated with one SS/PBCH block, one CSI-RS, and/or one downlink transmit beam may correspond to one SS/PBCH block, one CSI-RS, and/or Index information for identifying one downlink transmission beam (which may be, for example, an SSB index, a beam index, or a QCL setting index) may be included.

FIG. 8 is a diagram showing an example of a random access procedure of the terminal device 1 in this embodiment.

<Message 1 (S801)>
In S801, the terminal device 1 transmits the random access preamble to the base station device 3 via the PRACH. This transmitted random access preamble may be referred to as message 1 (Msg1). Transmission of the random access preamble is also called PRACH transmission. The random access preamble is configured to notify the base station device 3 of information by using one of the plurality of sequences. For example, 64 types of sequences (random access preamble index numbers 1 to 64) are prepared. When 64 kinds of sequences are prepared, 6-bit information (which may be ra-PreambleIndex or preamble index) can be shown to the base station apparatus 3. This information may be indicated as a Random Access Preamble Identifier (RAPID).

In the case of the contention-based random access procedure, the terminal device 1 itself randomly selects the index of the random access preamble. In the contention-based random access procedure, the terminal device 1 selects the SS/PBCH block having the RSRP of the SS/PBCH block exceeding the set threshold value, and selects the preamble group. When the relationship between the SS/PBCH block and the random access preamble is set, the terminal device 1 randomly selects one or more random access preambles associated with the selected SS/PBCH block and the selected preamble group. The ra-PreambleIndex is selected for, and the selected ra-PreambleIndex is set to the preamble index (PREAMBLE_INDEX). Further, for example, the selected SS/PBCH block and the selected preamble group may be divided into two subgroups based on the transmission size of the message 3. When the transmission size of the message 3 is small, the terminal device 1 randomly selects a preamble index from the subgroup corresponding to the transmission size of the small message 3, and when the transmission size of the message 3 is large, the preamble index is selected as the transmission size of the large message 3. The preamble index may be randomly selected from the corresponding subgroup. The index when the message size is small is usually selected when the characteristics of the propagation path are poor (or the distance between the terminal device 1 and the base station device 3 is long), and the index when the message size is large is the propagation path. Is good (or the distance between the terminal device 1 and the base station device 3 is short).

In the case of the non-contention based random access procedure, the index of the random access preamble is selected by the terminal device 1 based on the information received from the base station device 3. Here, the information received from the base station device 3 by the terminal device 1 may be included in the PDCCH. When the bit values of the information received from the base station device 3 are all 0, the terminal device 1 executes the contention-based random access procedure, and the terminal device 1 itself selects the index of the random access preamble.

<Message 2 (S802)>
Next, the base station device 3 that has received the message 1 generates a RAR message including an uplink grant (RAR UL grant, Random Access Response Grant, RAR UL grant) for instructing the terminal device 1 to transmit in S802. , And transmits a random access response including the generated RAR message to the terminal device 1 by DL-SCH. That is, the base station device 3 transmits a random access response including the RAR message corresponding to the random access preamble transmitted in S801 on the PDSCH in the primary cell (or primary secondary cell). The PDSCH corresponds to the PDCCH including RA-RNTI. The RA-RNTI is calculated by RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id. Here, s_id is an index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is an index of the first slot of PRACH in the system frame, and takes a value from 0 to 79. f_id is a PRACH index in the frequency domain and takes values from 0 to 7. ul_carrier_id is an uplink carrier used for Msg1 transmission. The ul_carrier_id for the NUL carrier is 0 and the ul_carrier_id for the SUL carrier is 1.

The random access response may be referred to as Message 2 or Msg2. In addition, the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble and a RAR message (MAC RAR) corresponding to the identifier in the message 2. The base station device 3 calculates a transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and transmits transmission timing adjustment information (TA command, Timing Advance Command) for adjusting the shift. ) Is included in the RAR message. The RAR message includes at least a random access response grant field mapped to an uplink grant, a Temporary C-RNTI field to which a Temporary C-RNTI (Cell Radio Network Temporary Identifier) is mapped, and a TA command (Timing Advance Command). Including. The terminal device 1 adjusts the timing of PUSCH transmission based on the TA command. The timing of PUSCH transmission may be adjusted for each group of cells. Also, the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble in the message 2.

In order to respond to the PRACH transmission, the terminal device 1 detects the DCI format 1_0 to which the CRC parity bit scrambled by the corresponding RA-RNTI is added in the SpCell (PCell or PSCell) during the random access response window. (Monitor) The period (window size) of the random access response window is given by the upper layer parameter ra-ResponseWindow. The window size is the number of slots based on the subcarrier spacing of the Type1-PDCCH common search space.

When the terminal device 1 detects the PDSCH including the DCI format 1_0 with the CRC scrambled by RA-RNTI and one DL-SCH transport block within the window period, the terminal device 1 detects the transport block. Pass to upper layer. The upper layer parses that transport block for the random access preamble identifier (RAPID) associated with the PRACH transmission. When the upper layer identifies the RAPID contained in the RAR message of its DL-SCH transport block, the upper layer indicates the uplink grant to the physical layer. To identify, the RAPID included in the received random access response and the RAPID corresponding to the transmitted random access preamble are the same. The uplink grant is called a random access response uplink grant (RAR UL grant) in the physical layer. That is, the terminal device 1 can identify the RAR message (MAC RAR) addressed to itself from the base station device 3 by monitoring the random access response (message 2) corresponding to the random access preamble identifier.

(I) When the terminal device 1 does not detect the DCI format 1_0 to which the CRC scrambled by RA-RNTI is added within the window period, or (ii) the terminal device 1 DL-on the PDSCH within the window period If the SCH transport block is not received correctly, or (iii) the upper layer does not identify the RAPID associated with the PRACH transmission, the upper layer instructs the physical layer to transmit the PRACH.

When the received random access response includes a random access preamble identifier corresponding to the transmitted random access preamble and the terminal device 1 selects the random access preamble based on the information received from the base station device 3, The device 1 considers that the non-contention based random access procedure has been successfully completed, and transmits the PUSCH based on the uplink grant included in the random access response.

If the received random access response includes the random access preamble identifier corresponding to the transmitted random access preamble, and the random access preamble is selected by the terminal device 1 itself, the TC-RNTI is included in the received random access response. The value of the TC-RNTI field is set, and the random access message 3 is transmitted by PUSCH based on the uplink grant included in the random access response. The PUSCH corresponding to the uplink grant included in the random access response is transmitted in the serving cell in which the corresponding preamble is transmitted on the PRACH.

RAR UL grant is used for PUSCH transmission (or RAR PUSCH) scheduling. The PUSCH (or PUSCH transmission) scheduled by the RAR UL grant may be referred to as RAR PUSCH (or RAR PUSCH transmission). In other words, RAR PUSCH transmission is PUSCH transmission corresponding to RAR UL grant. That is, the PUSCH (PUSCH transmission) scheduled by the RAR UL grant may be the PUSCH (PUSCH transmission) corresponding to the RAR UL grant.

In the contention-based random access procedure, the terminal device 1 transmits Msg3 (message 3) based on the RAR UL grant. That is, in the contention-based random access procedure, Msg3 PUSCH (Msg3 PUSCH transmission) is scheduled by the RAR UL grant. Msg3 may be the first scheduled transmission (PUSCH transmission, first scheduled transmission) of the contention based random access procedure. Msg3 is a message that includes C-RNTI MAC CE or CCCH SDU as part of the contention based random access procedure, and may be transmitted on UL-SCH. In the contention based random access procedure, the RAR PUSCH transmission may be Msg3 PUSCH transmission. In the non-contention based random access procedure, the terminal device 1 may transmit the PUSCH (RAR PUSCH) based on the RAR UL grant. That is, in the non-contention based random access procedure, the PUSCH scheduled by the RAR UL grant does not have to be called Msg3PUSCH. Also, in the non-contention based random access procedure, the PUSCH scheduled by the RAR UL grant may be referred to as Non-Msg3 PUSCH. That is, in the non-contention based random access procedure, the Non-Msg3 PUSCH may be the PUSCH scheduled by the RAR UL grant.

Also, in the present embodiment, the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the contention-based random access procedure. Further, the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the non-contention based random access procedure. That is, the Msg3 PUSCH may be the PUSCH scheduled by the RAR UL grant regardless of the type of random access procedure (contention-based random access procedure or non-contention-based random access procedure).

FIG. 9 is a diagram showing an example of fields included in the RAR UL grant. When the value of the frequency hopping flag (Frequency hopping flag) in FIG. 9 is 0, the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant without frequency hopping. When the value of the frequency hopping flag (Frequency hopping flag) is 1, the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant with frequency hopping. The frequency resource allocation of PUSCH scheduled by RAR UL grant may be uplink resource allocation type 1.

The (Msg3) PUSCH frequency resource allocation' field is used to indicate frequency domain resource allocation for PUSCH transmission scheduled by RAR UL grant.

The'(Msg3)PUSCH time resource allocation' field is used to indicate the time domain resource allocation for the PUSCH scheduled by the RAR UL grant.

The'MCS' field is used to determine the MCS index for PUSCH scheduled by RAR UL grant.

The'TPC command for scheduled PUSCH' field is used for setting the transmission power of the PUSCH scheduled by the RAR UL grant.

In the contention-based random access procedure, the'CSI request' field is reserved. In the non-contention based random access procedure, the'CSI request' field is used to determine whether the aperiodic CSI report is included in the PUSCH transmission.

<Message 3 (S803)>
The terminal device 1 performs PUSCH transmission scheduled by the RAR UL grant included in the RAR message received in S802. The terminal device 1 performs PRACH transmission and PUSCH transmission scheduled by the RAR UL grant on the same uplink carrier of the same serving cell. The PUSCH scheduled by the RAR UL grant is sent in the active UL BWP. The subcarrier spacing for the PUSCH scheduled by the RAR UL grant may be indicated from the upper layer parameter SubcarrierSpacing or the upper layer parameter SubcarrierSpacing2 set for the UL BWP. In FDD, the upper layer parameter SubcarrierSpacing may be used to indicate the DL BWP subcarrier spacing. In FDD, the upper layer parameter SubcarrierSpacing2 may be used to indicate the UL BWP subcarrier spacing. In SUL, the upper layer parameter SubcarrierSpacing may be used to indicate the subcarrier spacing of NUL (Normal Uplink, Non-SUL) carriers. In SUL, the upper layer parameter SubcarrierSpacing2 may be used to indicate the subcarrier spacing of the serving cell of the SUL carrier.

The terminal device 1 detects the DCI that schedules the PDSCH including the RAR message. The RAR message contains the RAR UL grant. The terminal device 1 transmits the PUSCH scheduled by the RAR UL grant in the RAR message. The slot number assigned to that PUSCH may be given by (Equation 2) Floor(n*2 ^μPUSCH /2 ^μPDSCH )+K ₂ +Δ. n is a slot in which the PDSCH including the RAR message is detected. Slot n is the number of the slot corresponding to the PDSCH subcarrier interval. μ _PDSCH is a subcarrier interval setting for _PDSCH . μ _PUSCH is a subcarrier interval setting for PUSCH scheduled by RAR UL grant. That is, when the terminal device 1 receives the PDSCH including the RAR message in the slot n, the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant in the slot Floor(n*2 ^μPUSCH /2 ^μPDSCH )+K ₂ +Δ. May be. The value of K ₂ may be indicated by the'PUSCH time resource allocation' field included in the RAR UL grant. Δ is an additional subcarrier spacing specific slot delay value for the first transmission of PUSCH scheduled by the RAR UL grant. That is, the value of Δ corresponds to the subcarrier interval to which the PUSCH scheduled by the RAR UL grant is applied. For example, if the subcarrier spacing to which the PUSCH scheduled by the RAR UL grant is applied is 15 kHz, the value of Δ may be 2 slots. If the subcarrier spacing is 30 kHz, the value of Δ may be 3 slots. If the subcarrier spacing is 60 kHz, the value of Δ may be 4 slots. If the subcarrier spacing is 120 kHz, the value of Δ may be 6 slots.

In other words, the number of the slot in which the PUSCH scheduled by the RAR UL grant is transmitted is (i) the first subcarrier interval for the PDSCH containing the RAR message, (ii) the RAR UL included in that PDSCH. Second subcarrier spacing for PUSCH scheduled by the grant, (iii) number of slots in which PDSCH containing RAR message is received, (iv) number of predefined slots corresponding to second subcarrier spacing Δ, (iv) may be given based on the slot offset value K ₂ given from the RAR UL grant.

FIG. 18 is a diagram showing an example of transmitting the PUSCH scheduled by the RAR UL grant. The slot length differs depending on the subcarrier interval setting μ. FIG. 18A shows slot numbers corresponding to a subcarrier spacing of 30 kHz (μ=1). FIG. 18B shows slot numbers corresponding to a subcarrier interval of 15 kHz (μ=0). In a subframe or a frame, the slot numbers corresponding to the subcarrier intervals are counted in ascending order from 0. The slot number n of the subcarrier interval setting of 15 kHz corresponds to the slot numbers 2n and 2n+1 of the subcarrier interval setting of 30 kHz.

In FIG. 18, the terminal device 1 may receive the PDSCH including the RAR message scheduled by the detected DCI by detecting the DCI (900). The PDSCH containing the RAR message may be PDSCH (901) or PDSCH (904) based on DCI (900).

For example, the subcarrier interval for PDSCH (901) including the RAR message is 15 kHz (μ _PDSCH =0). The subcarrier interval for the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is 15 kHz (μ _PUSCH =0). The value of Δ corresponding to a subcarrier spacing of 15 kHz is 2. When K ₂ is 0, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is transmitted is given as slot n+2 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (902) in slot n+2 corresponding to the subcarrier interval of 15 kHz. When K ₂ is 1, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is transmitted is given as slot n+3 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (903) in slot n+3 corresponding to the subcarrier interval of 15 kHz.

Further, for example, the subcarrier interval for the PDSCH (901) including the RAR message is 15 kHz (μ _PDSCH =0). The subcarrier interval for the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is 30 kHz (μ _PUSCH =1). The value of Δ corresponding to a subcarrier spacing of 30 kHz is 3. When K ₂ is 0, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is transmitted is given as slot 2n+3 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (905) in slot 2n+3 corresponding to the subcarrier interval of 30 kHz. When K ₂ is 1, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (901) is transmitted is given as slot 2n+4 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (906) in slot 2n+4 corresponding to the subcarrier spacing of 30 kHz.

Further, for example, the subcarrier interval for the PDSCH (904) including the RAR message is 30 kHz (μ _PDSCH =1). The subcarrier interval for the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is 30 kHz (μ _PUSCH =1). The value of Δ corresponding to a subcarrier spacing of 30 kHz is 3. When K ₂ is 0, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is transmitted is given as slot 2n+3 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (905) in slot 2n+3 corresponding to the subcarrier interval of 30 kHz. When K ₂ is 1, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is transmitted is given as slot 2n+4 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (906) in slot 2n+4 corresponding to the subcarrier spacing of 30 kHz.

Further, for example, the subcarrier interval for the PDSCH (904) including the RAR message is 30 kHz (μ _PDSCH =1). The subcarrier interval for the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is 15 kHz (μ _PUSCH =0). The value of Δ corresponding to a subcarrier spacing of 15 kHz is 2. When K ₂ is 0, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is transmitted is given as slot n+2 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (902) in slot n+2 corresponding to the subcarrier interval of 15 kHz. When K ₂ is 1, the slot in which the PUSCH scheduled by the RAR UL grant included in the PDSCH (904) is transmitted is given as slot n+3 based on (Equation 2). In this case, the scheduled PUSCH is the PUSCH (903) in slot n+3 corresponding to the subcarrier interval of 15 kHz.

<Retransmission of message 3 (S803a)>
Retransmission of message 3 is scheduled by DCI format 0_0 with a CRC parity bit scrambled by TC-RNTI included in the RAR message. That is, the PUSCH retransmission of the transport block transmitted on the PUSCH corresponding to the RAR UL grant included in the RAR message is scheduled by the DCI format 0_0 with the CRC parity bit scrambled by TC-RNTI. The DCI format 0_0 is transmitted on the PDCCH of the type 1 PDCCH common search space set. That is, the terminal device 1 may monitor the DCI format 0_0 that schedules the retransmission of the message 3 after transmitting the message 3 in S803. When the terminal device 1 detects the DCI format 0_0 that schedules the retransmission of the message 3 in S803a, S803b is executed.

<Retransmission of message 3 (S803b)>
When the DCI format 0_0 added with the CRC parity bit scrambled by TC-RNTI is detected in S803a, the terminal device 1 performs the PUSCH retransmission of the transport block transmitted in S803.

<Message 4 (S804)>
In order to respond to the PUSCH transmission (PUSCH scheduled by the RAR UL grant) of the message 3 (Msg3), the terminal device 1 that does not indicate the C-RNTI schedules the PDSCH including the UE contention resolution identity. DCI format 1_0 is monitored. Here, a CRC parity bit scrambled by the corresponding TC-RNTI is added to this DCI format 1_0. In order to respond to the PDSCH reception with the UE collision resolution identity, the terminal device 1 sends HARQ-ACK information on the PUCCH. The transmission of the PUCCH may be performed by the active UL BWP to which the message 3 (Msg 3) is transmitted.

With this, the terminal device 1 performing the random access procedure can perform uplink data transmission to the base station device 3.

FIG. 19 is a flowchart showing an example of a random access procedure of the MAC entity according to this embodiment.

<Start of random access procedure (S1001)>
In FIG. 19, S1001 is a procedure related to the start of a random access procedure (random access procedure initialization). In S1001, the random access procedure is initiated by a PDCCH order, a MAC entity itself, a beam failure notification from a lower layer, RRC, or the like. The random access procedure in SCell is started only by the PDCCH order including the ra-PreambleIndex which is not set to 0b000000.

In S1001, the terminal device 1 receives the random access setting information via the upper layer before starting the random access procedure (initiate). The random access setting information may include one or more elements of the following information or information for determining/setting the following information.
Prach-ConfigIndex: a set of one or more time/frequency resources (also called random access channel occasions, PRACH occasions, RACH occasions) available for transmission of a random access preamble. preambleReceivedTargetPower. : Initial power of preamble (may be target received power)
Rsrp-Threshold SSB: Reference signal received power (RSRP) threshold for selection of SS/PBCH blocks (which may be associated random access preambles and/or PRACH opportunities) rsrp-Threshold CSI-RS:CSI-RS Reference signal received power (RSRP) threshold for selection of (which may be associated random access preamble and/or PRACH opportunity) rsrp-Threshold SSB-SUL: NUL (Normal Uplink) carrier and SUL (Supplementary Uplink) Reference signal received power (RSRP) threshold for selection with carrier • powerControlOffset: power between rsrp-Threshold SSB and rsrp-Threshold CSI-RS when random access procedure is initiated for beam failure recovery. Offset/powerRampingStep: Power ramping step (power ramping factor). Indicates the step of the transmission power ramped up based on the preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER. • ra-PreambleIndex: One or more available random access preambles or one or more available in the plurality of random access preamble groups. Random access preamble ra-ssb-OcclusionMaskIndex: information for the MAC entity to determine the PRACH opportunity assigned to the SS/PBCH block sending the random access preamble ra-OccasionList: the MAC entity sends the random access preamble Information for determining PRACH opportunities allocated to good CSI-RSs • premTransMax: maximum number of preamble transmissions • ssb-perRACH- OccasionAndCB-PreamblesPerSSB (SpCell only): SS/PBCH block mapped to each PRACH opportunity Number and a parameter indicating the number of random access preambles mapped to each SS/PBCH block, ra-ResponseWindow: time window for monitoring random access response (SpCell only), ra-ContentionResolutionTimer: contention resolution (contention resolution: Contention Resolution) timer • numberOfRA-PreamblesGroupA: Random access preamble for each SS/PBCH block Number of random access preambles in group A • PREAMBLE_TRANSMISSION_COUNTER: Preamble transmit counter • DELTA_PREAMBLE_Random access preamble PRE format based on the random access preamble PAM. Preamble power ramping counter PREAMBLE_RECEIVED_TARGET_POWER: initial random access preamble power. The initial transmit power for random access preamble transmission is shown.
• PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.

When a random access procedure is started in a serving cell, the MAC entity refreshes the Msg3 buffer, sets the state variable PREAMBLE_TRANSMISSION_COUNTER to 1, sets the state variable PREAMBLE_POWER_RAMPING_COUNTER to 1 and sets the state variable PREAMBLE_BACKOFF to 0 ms. If the carrier used for the random access procedure is explicitly notified, the MAC entity selects the notified carrier to perform the random access procedure, and sets the state variable PCMAX to the maximum transmission power value of the notified carrier. set. When the MAC entity is not explicitly notified of the carrier used for the random access procedure, the SUL carrier is set for the serving cell, and the downlink path loss reference RSRP is smaller than rsrp-Threshold SSB-SUL. Then, the SUL carrier is selected to perform the random access procedure, and the state variable PCMAX is set to the maximum transmission power value of the SUL carrier. Otherwise, the MAC entity selects the NUL carrier to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the NUL carrier.

<Start of random access procedure (S1002)>
S1002 is a random access resource selection procedure. Hereinafter, a procedure for selecting a random access resource (including a time/frequency resource and/or a preamble index) in the MAC layer of the terminal device 1 will be described.

The terminal device 1 sets a value for the preamble index (may be referred to as PREAMBLE_INDEX) of the random access preamble to be transmitted by the following procedure.

The terminal device 1 (MAC entity) starts a random access procedure by (1) notification of beam failure from a lower layer, and (2) SS/PBCH block (also referred to as SSB) or CSI-RS with RRC parameters. Random access resources (which may be PRACH opportunities) for non-contention based random access for associated beam failure recovery requests are provided, and (3) one or more SS/PBCH blocks or CSIs. -If RSRP of RS exceeds a predetermined threshold, select the SS/PBCH block or CSI-RS for which RSRP exceeds the predetermined threshold. If the CSI-RS has been selected and there is no ra-PreambleIndex associated with the selected CSI-RS, the MAC entity shall determine the ra-PreambleIndex associated with the selected SS/PBCH block as the preamble index (PREAMBLE_INDEX). ) May be set. Otherwise, the MAC entity sets the preamble index to the ra-PreambleIndex associated with the selected SS/PBCH block or CSI-RS.

The terminal device 1 is provided with (1) ra-PreambleIndex by PDCCH or RRC, (2) the value of the ra-PreambleIndex is not a value (eg, 0b000000) indicating the contention-based random access procedure, and (3) RRC Set the signaled ra-PreambleIndex to the preamble index if the SS/PBCH block or CSI-RS is not associated with the random access resource for non-contention based random access. 0bxxxxxxx means a bit string arranged in a 6-bit information field.

In the terminal device 1, (1) random access resources for non-contention based random access associated with the SS/PBCH block are provided from the RRC, and (2) RSRP is predetermined among the associated SS/PBCH blocks. When one or more SS/PBCH blocks that exceed the threshold of are available, RSRP selects one of the SS/PBCH blocks that exceeds the predetermined threshold and selects the selected SS/PBCH block. Set the associated ra-PreambleIndex to the preamble index.

In the terminal device 1, (1) CSI-RS is associated with the random access resource for non-contention based random access by RRC, and (2) RSRP of the associated CSI-RS exceeds a predetermined threshold. When one or more CSI-RSs are available, RSRP selects one of the CSI-RSs exceeding the predetermined threshold and preambles the ra-PreambleIndex associated with the selected CSI-RS. Set to index.

The terminal device 1 performs the contention-based random access procedure when none of the above conditions is satisfied. In the contention-based random access procedure, the terminal device 1 selects the SS/PBCH block having the RSRP of the SS/PBCH block exceeding the set threshold value, and selects the preamble group. When the relationship between the SS/PBCH block and the random access preamble is set, the terminal device 1 randomly selects one or more random access preambles associated with the selected SS/PBCH block and the selected preamble group. The ra-PreambleIndex is selected for, and the selected ra-PreambleIndex is set as the preamble index.

When the MAC entity selects one SS/PBCH block and the association between the PRACH opportunity and the SS/PBCH block is set, the MAC entity selects the next PRACH opportunity associated with the selected SS/PBCH block. May determine available PRACH opportunities. However, when the terminal device 1 selects one CSI-RS and the association (association) between the PRACH opportunity and the CSI-RS is set, the terminal device 1 selects the next PRACH opportunity associated with the selected CSI-RS. May determine available PRACH opportunities.

Available PRACH opportunities may also be identified based on mask index information, SSB index information, resource settings configured in RRC parameters, and/or selected reference signals (SS/PBCH blocks or CSI-RS). Good. The resource setting set by the RRC parameter includes a resource setting for each SS/PBCH block and/or a resource setting for each CSI-RS.

The base station device 3 may transmit the resource setting for each SS/PBCH block and/or the resource setting for each CSI-RS to the terminal device 1 by an RRC message. The terminal device 1 receives the resource setting for each SS/PBCH block and/or the resource setting for each CSI-RS by the RRC message from the base station device 3. The base station device 3 may transmit the mask index information and/or the SSB index information to the terminal device 1. The terminal device 1 acquires the mask index information and/or the SSB index information from the base station device 3. The terminal device 1 may select the reference signal (SS/PBCH block or CSI-RS) based on a certain condition. The terminal device 1 determines the next available PRACH opportunity based on the mask index information, the SSB index information, the resource setting set by the RRC parameter, and the selected reference signal (SS/PBCH block or CSI-RS). May be specified. The MAC entity of the terminal device 1 may instruct the physical layer to transmit the random access preamble using the selected PRACH opportunity.

The mask index information is information indicating an index of PRACH opportunities that can be used for transmitting the random access preamble. The mask index information may be information indicating a part of PRACH opportunities of a group of one or a plurality of PRACH opportunities defined by prac-ConfigurationIndex. Further, the mask index information may be information indicating some PRACH opportunities in the group of PRACH opportunities to which the specific SSB index specified by the SSB index information is mapped.

The SSB index information is information indicating an SSB index corresponding to one of one or more SS/PBCH blocks transmitted by the base station device 3. The terminal device 1 that has received the message 0 identifies the group of PRACH opportunities to which the SSB index indicated by the SSB index information is mapped. The SSB index mapped to each PRACH opportunity is determined by the PRACH configuration index, the upper layer parameter SB-perRACH-Occlusion, and the upper layer parameter cb-preamblePerSSB.

<Transmission of random access preamble (S1003)>
S1003 is a procedure relating to transmission of a random access preamble (random access preamble transmission). For each random access preamble, the MAC entity shall (1) have state variable PREAMBLE_TRANSMISSION_COUNTER greater than 1 and (2) have not received a power ramp counter notification from the upper layer and (3) select Increment the state variable PREAMBLE_POWER_RAMPING_COUNTER by one if the assigned SS/PBCH block has not changed.

Next, the MAC entity selects the value of DELTA_PREAMBLE and sets the state variable PREAMBLE_RECEIVED_TARGET_POWER to a predetermined value. The predetermined value is calculated by preambleReceivedTargetPower+DELTA_PREAMBLE+(PREAMBLE_POWER_RAMPING_COUNTER-1)*powerRampingStep.

Next, the MAC entity calculates the RA-RNTI associated with the PRACH opportunity where the random access preamble is sent, except for non-contention based random access preamble due to beam failure recovery request. The RA-RNTI is calculated by RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id. Here, s_id is an index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is an index of the first slot of PRACH in the system frame, and takes a value from 0 to 79. f_id is a PRACH index in the frequency domain and takes values from 0 to 7. ul_carrier_id is an uplink carrier used for Msg1 transmission. The ul_carrier_id for the NUL carrier is 0 and the ul_carrier_id for the SUL carrier is 1.

-The MAC entity instructs the physical layer to transmit the random access preamble using the selected PRACH.

<Reception of random access response (S1004)>
S1004 is a procedure related to the reception of a random access response (random access response reception). Once the random access preamble is transmitted, the MAC entity will perform the following actions regardless of possible occurrence of measurement gaps. Here, the random access response may be a MAC PDU for the random access response.

A MAC PDU (random access response MAC PDU) consists of one or more MAC subPDUs and possible padding. Each MAC subPDU is composed of any of the following.
MAC sub-header (subheader) containing only Backoff Indicator
-MAC subheader (subheader) indicating only RAPID
-MAC subheader (subheader) indicating RAPID and MAC RAR (MAC payload for Random Access Response)
The MAC sub PDU including only the Backoff Indicator is placed at the head of the MAC PDU. The padding is placed at the end of the MAC PDU. The MAC subPDU including only the RAPID and the MAC subPDU including the RAPID and the MAC RAR may be arranged anywhere between the padding and the MAC subPDU including only the Backoff Indicator.

MAC RAR has a fixed size and consists of reserved bits (Reserved bits) that are set to 0, transmission timing adjustment information (TA command, Timing Advance Command), UL grant (UL grant, RAR UL grant), and TEMPORARY_C-RNTI. Has been done. Hereinafter, the RAR message may be a MAC RAR. The RAR message may be a random access response.

In S1004, if the MAC entity sends a non-contention based random access preamble for a beam failure recovery request, the MAC entity sends a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of the random access preamble transmission. To start. Then, while the random access response window is running, the MAC entity monitors the SpCell PDCCH identified by the C-RNTI for response to the beam failure recovery request. Here, the period (window size) of the random access response window is given by ra-ResponseWindow included in the upper layer parameter BeamFailureRecoveryConfig. Otherwise, the MAC entity starts a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of random access preamble transmission. Here, the period (window size) of the random access response window is given by ra-ResponseWindow included in the upper layer parameter RACH-ConfigCommon. Then, the MAC entity monitors the PDCCH of the SpCell identified by RA-RNTI for random access response while the random access response window is running. Here, the information element BeamFailureRecoveryConfig is used for setting the RACH resource and the candidate beam for the beam failure recovery for the terminal device 1 when the beam failure is detected. The information element RACH-ConfigCommon is used to specify cell-specific random access parameters.

The MAC entity receives (1) an acknowledgment of the PDCCH transmission from the lower layer, (2) the PDCCH transmission is scrambled by the C-RNTI, and (3) the MAC entity is on a non-contention basis for the beam failure recovery request. The random access procedure may be considered to have been successfully completed if the random access preamble is sent.

Next, the MAC entity performs the following operations when (1) the downlink assignment is received on the PDCCH of RA-RNTI and (2) the received transport block is successfully decoded.

The MAC entity sets PREAMBLE_BACKOFF to the value of the BI field included in the MAC subPDU when the random access response includes the MAC subPDU including the BackoffIndicator. Otherwise, the MAC entity sets PREAMBLE_BACKOFF to 0ms.

The MAC entity may consider that the random access response has been successfully received when it includes a MAC subPDU including a random access preamble identifier corresponding to the PREAMBLE_INDEX to which the random access response is transmitted.

The MAC entity considers the random access procedure to be successfully completed if (1) the random access response is considered to be successfully received, and (2) the random access response includes a MAC subPDU containing only RAPID, and , Reception of an acknowledgment to an SI request (symstem information request) is shown in the upper layer. Here, when the condition (2) is not satisfied, the MAC entity applies the following operation A to the serving cell in which the random access preamble is transmitted.
<Start of operation A>
The MAC entity processes the received transmission timing adjustment information (Timing Advance Command) and indicates to the lower layer the preambleReceivedTargetPower and the amount of power ramping applied to the latest random access preamble transmission. Here, the transmission timing adjustment information is used to adjust the deviation of the transmission timing between the terminal device 1 and the base station device 3 from the received random access preamble.

If the serving cell for the random access procedure is the SCell for SRS only, the MAC entity may ignore the received UL grant. Otherwise, the MAC entity processes the received UL grant value and indicates it to lower layers.

If the random access preamble is not selected by the MAC entity from the range of contention-based random access preambles, the MAC entity may consider the random access procedure to have completed successfully.
<End of operation A>
When the random access preamble is selected by the MAC entity from the range of contention based random access preamble, the MAC entity sets TEMPORARY_C-RNTI to the value of the Temporary C-RNTI field included in the received random access response. Then, when the random access response is successfully received for the first time in this random access procedure, the MAC entity, if not transmitting to the CCCH logical channel (common control channel logical channel), Notify a predetermined entity (Multiplexing and assembly entity) that the next uplink transmission includes the C-RNTI MAC CE, and acquire and obtain a MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity). The stored MAC PDU is stored in the Msg3 buffer. When transmission is performed on the CCCH logical channel, the MAC entity acquires a MAC PDU for transmission from a predetermined entity (Multiplexing and assembly entity) and stores the acquired MAC PDU in the Msg3 buffer.

If at least one of the following conditions (3) to (4) is satisfied, the MAC entity considers that the random access response has not been successfully received, and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one. The MAC entity indicates a random access problem to the upper layer when the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions+1) and the random access preamble is transmitted in SpCell. Then, if the random access procedure is initiated for the SI request, the MAC entity considers that the random access procedure has not been completed successfully.

The MAC entity determines that the random access procedure has not been successfully completed when the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions+1) and the random access preamble is transmitted in the SCell. I reckon.

The condition (3) is that the period of the random access response window set in RACH-ConfigCommon has been expired and the random access response including the random access preamble identifier matching the transmitted preamble index has not been received. That's what it means. The condition (4) is that the period of the random access response window set by BeamFailureRecoveryConfig has expired and the PDCCH scrambled by the C-RNTI has not been received.

If the random access procedure has not been completed, the MAC entity shall choose between 0 and PREAMBLE_BACKOFF if the random access preamble was selected by the MAC itself from the range of contention based random access preambles in the random access procedure. A backoff time is selected, the next random access preamble transmission is delayed at the selected backoff time, and S1002 is executed. If the random access procedure is not completed, the MAC entity performs S1002 if the random access preamble is not selected by the MAC itself from the contention based random access preamble range in the random access procedure.

The MAC entity may stop the random access response window upon successful receipt of a random access response containing a random access preamble identifier that matches the transmitted preamble index.

The terminal device 1 transmits the message 3 by PUSCH based on the UL grant.

<Collision resolution (S1005)>
S1005 is a procedure related to collision resolution (Contention Resolution).

Once Msg3 is sent, the MAC entity starts a collision resolution timer and restarts the collision resolution timer at each HARQ retransmission. The MAC entity monitors the PDCCH while the collision resolution timer is running, regardless of possible occurrence of measurement gaps.

When the PDCCH transmission reception notification is received from the lower layer and the C-RNTI MAC CE is included in Msg3, the MAC entity is provided if at least one of the following conditions (5) to (7) is satisfied. , The contention resolution is considered successful, the contention resolution timer is stopped, the TEMPORARY_C-RNTI is discarded, and the random access procedure is considered successfully completed.

Condition (5) is that the random access procedure is initiated by the MAC sublayer itself or the RRC sublayer, the PDCCH transmission is scrambled by the C-RNTI, and the PDCCH transmission includes an uplink grant for initial transmission. .. Condition (6) is that the random access procedure is initiated by the PDCCH order and the PDCCH transmission is scrambled by the C-RNTI. Condition (7) is that the random access procedure is initiated for beam failure recovery and the PDCCH transmission is scrambled by the C-RNTI.

If CCCH SDU (UE contention resolution identity) is included in Msg3 and the PDCCH transmission is scrambled by TEMPORARY_C-RNTI, the MAC entity will stop the collision resolution timer if the MAC PDU is successfully decoded. .. Then, if the successfully decoded MAC PDU contains the UE contention resolution identity MAC CE and the UE collision resolution identity in the MAC CE matches the CCCH SDU sent in Msg3, The MAC entity regards the collision resolution as successful and terminates the disassembly and demultiplexing of the MAC PDU. Then, if the random access procedure is initiated for the SI request, the MAC entity indicates to the higher layers the receipt of an acknowledgment for the SI request. If the random access procedure is not initiated due to the SI request, the MAC entity sets C-RNTI to the value of TEMPORARY_C-RNTI. Subsequently, the MAC entity discards TEMPORARY_C-RNTI and considers the random access procedure to be completed successfully.

The MAC entity discards TEMPORARY_C-RNTI when the UE collision resolution identity in the MAC CE does not match the CCCH SDU sent in Msg3, considers that the collision resolution is not successful, and decodes the successfully decoded MAC PDU. Discard.

-The MAC entity discards TEMPORARY_C-RNTI when the conflict resolution timer expires and considers that conflict resolution is not successful. The MAC entity flushes the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1 when it is considered that the conflict resolution is not successful. When the value of the preamble transmission counter reaches a predetermined value (maximum number of preamble transmissions+1), the MAC entity indicates a random access problem to the upper layer. Then, if the random access procedure is initiated for the SI request, the MAC entity considers that the random access procedure has not been completed successfully.

If the random access procedure has not been completed, the MAC entity selects a random backoff time between 0 and PREAMBLE_BACKOFF, delays the next random access preamble transmission at the selected backoff time, and executes S1002.

Upon completion of the random access procedure, the MAC entity discards the explicitly signaled non-contention based random access resource for non-contention based random access procedures other than the non-contention based random access procedure for beam failure recovery request. Then, the HARQ buffer used for transmitting the MAC PDU in the Msg3 buffer is flushed.

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

FIG. 20 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. As illustrated, the terminal device 1 is configured to include a wireless transmission/reception unit 10 and an upper layer processing unit 14. The wireless 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 wireless transceiver 10 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor. The upper layer processing unit 14 is also referred to as a measurement unit, a selection unit or a control unit 14.

The upper layer processing unit 14 outputs the uplink data (which may be referred to as a transport block) generated by a user's operation or the like to the wireless transmission/reception unit 10. The upper layer processing unit 14 is a medium access control (MAC: Medium Access Control) layer, a packet data integration protocol (Packet Data Convergence Protocol: PDCP) layer, a radio link control (Radio Link Control: RLC) layer, a radio resource control (Radio). (Resource Control:RRC) Performs some or all of the layers. The upper layer processing unit 14 may have a function of selecting one reference signal from one or a plurality of reference signals based on the measurement value of each reference signal. The upper layer processing unit 14 may have a function of selecting a PRACH opportunity associated with one selected reference signal from one or a plurality of PRACH opportunities. The upper layer processing unit 14 sets 1 set in the upper layer (for example, the RRC layer) when the bit information included in the information instructing the start of the random access procedure received by the wireless transmission/reception unit 10 has a predetermined value. It may have a function of specifying one index from one or a plurality of indexes and setting it as a preamble index. The upper layer processing unit 14 may have a function of identifying an index associated with the selected reference signal from among one or more indexes set by RRC and setting it as a preamble index. The upper layer processing unit 14 may have a function of determining the next available PRACH opportunity based on the received information (eg, SSB index information and/or mask index information). The upper layer processing unit 14 may have a function of selecting an SS/PBCH block based on the received information (for example, SSB index information).

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 transmission of a scheduling request based on various setting information/parameters managed by the radio resource control layer processing unit 16.

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 the 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 the information indicating 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 the downlink control information received from the base station device 3.

The wireless transmission/reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transmission/reception unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The wireless transmission/reception unit 10 generates a transmission signal by modulating and encoding data and transmits it to the base station device 3. The wireless transmission/reception unit 10 may have a function of receiving one or more reference signals in a certain cell. The wireless transceiver 10 may have a function of receiving information (for example, SSB index information and/or mask index information) that identifies one or more PRACH opportunities. The wireless transmission/reception unit 10 may have a function of receiving a signal including instruction information for instructing the start of the random access procedure. The wireless transmission/reception unit 10 may have a function of receiving information that receives information that specifies a predetermined index. The wireless transmission/reception unit 10 may have a function of receiving information specifying an index of random access printing. The wireless transmission/reception unit 10 may have a function of transmitting the random access preamble at the PRACH opportunity determined by the upper layer processing unit 14.

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

The baseband unit 13 converts an analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to CP (Cyclic Prefix) from the converted digital signal, performs a fast Fourier transform (FFT) on the signal from which the CP is removed, and outputs a signal in the frequency domain. Extract.

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, and generates a baseband digital signal to generate a baseband signal. Converts band digital signals to analog signals. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 uses a low-pass filter to remove excess frequency components from the analog signal input from the baseband unit 13, upconverts the analog signal to a carrier frequency, and transmits it via the antenna unit 11. To do. Further, the RF unit 12 amplifies the power. The RF unit 12 may have a function of determining the transmission power of the uplink signal and/or the uplink channel transmitted in the serving cell. The RF unit 12 is also referred to as a transmission power control unit.

FIG. 21 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As illustrated, the base station device 3 is configured to include a wireless transmission/reception unit 30 and an upper layer processing unit 34. The wireless 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 medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver 30 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor. In addition, a control unit that controls the operation of each unit based on various conditions may be separately provided. The upper layer processing unit 34 is also referred to as the control unit 34.

The upper layer processing unit 34 includes a medium access control (MAC: Medium Access Control) layer, a packet data integration protocol (Packet Data Convergence Protocol: PDCP) layer, a radio link control (Radio Link Control: RLC) layer, and a radio resource control (Radio). (Resource Control:RRC) Performs some or all of the layers. The upper layer processing unit 34 may have a function of specifying one reference signal from one or a plurality of reference signals based on the random access preamble received by the wireless transmission/reception unit 30. The upper layer processing unit 34 may specify the PRACH opportunity to monitor the random access preamble from at least the SSB index information and the mask index information.

The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs processing of the MAC layer. The medium access control layer processing unit 35 performs processing relating to a scheduling request based on various setting information/parameters managed by the wireless resource control layer processing unit 36.

A 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 downlink control information (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 receives downlink control information, downlink data (transport block, random access response) arranged on the physical downlink shared channel, system information, RRC message, MAC CE (Control Element), etc. It is generated or acquired from the upper node and output to the wireless transmission/reception unit 30. Further, 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 an upper layer. That is, the radio resource control layer processing unit 36 transmits/notifies information indicating various setting information/parameters. The radio resource control layer processing unit 36 may transmit/notify information for specifying the setting of one or more reference signals in a certain cell.

When an RRC message, a MAC CE, and/or a PDCCH are transmitted from the base station device 3 to the terminal device 1 and the terminal device 1 performs processing based on the reception, the base station device 3 performs the processing. The processing (control of the terminal device 1 and the system) is performed assuming that the operation is being performed. That is, the base station device 3 sends to the terminal device 1 an RRC message, a MAC CE, and/or a PDCCH that causes the terminal device to perform processing based on the reception.

The wireless transmission/reception unit 30 has a function of transmitting one or more reference signals. Further, the wireless transmission/reception unit 30 may have a function of receiving a signal including the beam failure recovery request transmitted from the terminal device 1. The wireless transmission/reception unit 30 may have a function of transmitting information (for example, SSB index information and/or mask index information) identifying one or more PRACH opportunities to the terminal device 1. The wireless transmission/reception unit 30 may have a function of transmitting information specifying a predetermined index. The wireless transmission/reception unit 30 may have a function of transmitting information specifying the index of the random access preamble. The wireless transmission/reception unit 30 may have a function of monitoring the random access preamble at the PRACH opportunity specified by the upper layer processing unit 34. Other than that, a part of the function of the wireless transmission/reception unit 30 is the same as that of the wireless transmission/reception unit 10, and the description thereof will be omitted. If the base station device 3 is connected to one or more transmission/reception points 4, some or all of the functions of the wireless transmission/reception unit 30 may be included in each transmission/reception point 4.

Also, the upper layer processing unit 34 transmits (transfers) a control message or user data between the base station devices 3 or between the upper network device (MME, S-GW (Serving-GW)) and the base station device 3. ) Or receive. In FIG. 21, other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are omitted. It is clear that it has a plurality of blocks that it has as a component. For example, the upper layer processing unit 34 has a radio resource management layer processing unit and an application layer processing unit. The upper layer processing unit 34 may also have a function of setting a plurality of scheduling request resources corresponding to each of a plurality of reference signals transmitted from the wireless transmission/reception unit 30.

“Parts” in the figure are elements that realize the functions and procedures of the terminal device 1 and the base station device 3, which are also expressed by terms such as sections, circuits, constituent devices, devices, and units.

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

(1) More specifically, the terminal device 1 performing the random access procedure in the first aspect of the present invention receives the upper layer first parameter and the second parameter, and receives the PDCCH including DCI. A receiver 10 and a transmitter 10 for transmitting the PUSCH scheduled by the DCI, wherein a third parameter is predefined by a default table, the first parameter, the second parameter, And, the third parameter indicates information of PUSCH time domain resource allocation, and when a CRC scrambled by TC-RNTI is added to the DCI, regardless of whether or not the second parameter is received, One of the first parameter and the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.

(2) The base station device 3 that communicates with the terminal device that performs the random access procedure according to the second aspect of the present invention transmits the upper layer first parameter and the second parameter, and transmits the PDCCH including DCI. A transmitter 30 and a receiver 30 for receiving the PUSCH scheduled by the DCI, the third parameter being predefined by a default table, the first parameter, the second parameter, And, the third parameter indicates information of PUSCH time domain resource allocation, and when a CRC scrambled by TC-RNTI is added to the DCI, regardless of whether or not the second parameter is received, One of the first parameter and the third parameter is selected, and the PUSCH time domain resource allocation is given based on the selected parameter.

(3) In the first aspect or the second aspect of the present invention, when the first parameter is not indicated, the PUSCH time domain resource allocation is given based on the third parameter, When the first parameter is indicated, the PUSCH time domain resource allocation is provided based on the first parameter, not on the third parameter.

(4) In the first or second aspect of the present invention, the first parameter is included in a cell-common PUSCH configuration, and the second parameter is included in a UE-specific PUSCH configuration. ..

(5) In the first aspect or the second aspect of the present invention, the information of the PUSCH time domain resource allocation includes a slot offset between the DCI and the PUSCH, a start symbol of the PUSCH in a slot, and a continuous slot. The number of symbols to be allocated and the PUSCH mapping type are shown.

With this, the terminal device 1 can efficiently communicate with the base station device 3.

The program running on the device according to one aspect of the present invention is a program for controlling a Central Processing Unit (CPU) or the like to cause a computer to function so as to realize the function of the embodiment according to one aspect of the present invention. Is also good. The program or information handled by the program is temporarily stored in a volatile memory such as Random Access Memory (RAM) or a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.

The program for realizing the functions of the embodiments according to the present invention may be recorded in a computer-readable recording medium. It may be realized by causing a computer system to read and execute the program recorded on this recording medium. The “computer system” referred to here is a computer system built in the apparatus and includes an operating system and hardware such as peripheral devices. Further, the “computer-readable recording medium” is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another computer-readable recording medium. Is also good.

Also, each functional block or various features of the device used in the above-described embodiment may be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or others. Programmable logic device, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general-purpose processor may be a microprocessor, conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, in the event that an integrated circuit technology that replaces the current integrated circuit has emerged due to the progress of semiconductor technology, one or more aspects of the present invention can use a new integrated circuit according to the technology.

In addition, in the embodiment related to the present invention, the example applied to the communication system including the base station device and the terminal device has been described. Is also applicable.

Note that the present invention is not limited to the above embodiment. Although an example of the apparatus is described in the embodiment, the present invention is not limited to this, and a stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device, a kitchen device, It can be applied to terminal devices or communication devices such as cleaning/laundry equipment, air conditioning equipment, office equipment, vending machines, and other household appliances.

Although the embodiment of the present invention has been described in detail above with reference to the drawings, the specific configuration is not limited to this embodiment, and includes design changes and the like within a range not departing from the gist of the present invention. Further, the present invention can be variously modified 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. Be done. Further, a configuration in which elements described in each of the above embodiments and having the same effect are replaced with each other is also included.

Claims (12)

1. A terminal device that performs a random access procedure,
   A receiving unit for receiving the first parameter and the second parameter of the upper layer and receiving the PDCCH including the DCI;
   A transmitter for transmitting the PUSCH scheduled by the DCI,
   The third parameter is predefined by the default table,
   The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
   When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. The terminal device provided with the PUSCH time domain resource allocation based on selected parameters.
2. If the first parameter is not indicated, the PUSCH time domain resource allocation is given based on the third parameter, and if the first parameter is indicated, the PUSCH time domain resource allocation is given. The terminal device according to claim 1, wherein the resource allocation is given based on the first parameter, not based on the third parameter.
3. The first parameter is included in the cell-wide PUSCH configuration,
   The terminal device according to claim 1, wherein the second parameter is included in a UE-specific PUSCH configuration.
4. The information of the PUSCH time domain resource allocation indicates a slot offset between the DCI and the PUSCH, a start symbol of the PUSCH and a number of consecutively allocated symbols in the slot, and a mapping type of the PUSCH. The terminal device to do.
5. A base station device that communicates with a terminal device that performs a random access procedure,
   A transmission unit for transmitting the first parameter and the second parameter of the upper layer and transmitting the PDCCH including the DCI;
   A receiving unit for receiving the PUSCH scheduled by the DCI,
   The third parameter is predefined by the default table,
   The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
   When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. The time domain resource allocation of the PUSCH is given based on a selected parameter.
6. If the first parameter is not indicated, the PUSCH time domain resource allocation is given based on the third parameter, and if the first parameter is indicated, the PUSCH time domain resource allocation is given. The base station apparatus according to claim 5, wherein the resource allocation is given based on the first parameter, not based on the default table.
7. The first parameter is included in the cell-wide PUSCH configuration,
   The base station apparatus according to claim 5, wherein the second parameter is included in a UE-specific PUSCH configuration.
8. The information of the PUSCH time domain resource allocation indicates a slot offset between the DCI and the PUSCH, a start symbol of the PUSCH and a number of consecutively allocated symbols in the slot, and a mapping type of the PUSCH. Base station device.
9. A communication method of a terminal device performing a random access procedure, comprising:
   Receiving an upper layer first parameter and a second parameter, and receiving a PDCCH including DCI,
   Transmitting a PUSCH scheduled by the DCI,
   The third parameter is predefined by the default table,
   The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
   When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. A communication method in which the PUSCH time domain resource allocation is given based on selected parameters.
10. A communication method of a base station device for communicating with a terminal device performing a random access procedure, comprising:
    Transmitting a first parameter and a second parameter of an upper layer, and transmitting a PDCCH including DCI,
    Receiving a PUSCH scheduled by the DCI,
    The third parameter is predefined by the default table,
    The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
    When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. A communication method in which the PUSCH time domain resource allocation is given based on selected parameters.
11. An integrated circuit mounted on a terminal device performing a random access procedure,
    A function of receiving a first parameter and a second parameter of an upper layer and receiving a PDCCH including DCI,
    Causing the terminal device to exert the function of transmitting the PUSCH scheduled by the DCI,
    The third parameter is predefined by the default table,
    The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
    When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. The PUSCH time domain resource allocation is provided based on selected parameters.
12. An integrated circuit implemented in a base station device that communicates with a terminal device that performs a random access procedure,
    A function of transmitting a first parameter and a second parameter of an upper layer and transmitting a PDCCH including DCI,
    Causing the base station device to exhibit the function of receiving the PUSCH scheduled by the DCI;
    The third parameter is predefined by the default table,
    The first parameter, the second parameter, and the third parameter indicate information of PUSCH time domain resource allocation,
    When a CRC scrambled by TC-RNTI is added to the DCI, one of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received. The PUSCH time domain resource allocation is provided based on selected parameters.

Images