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

Abstract

To allow a terminal device and a base station device to efficiently communicate with each other.SOLUTION: A terminal device for performing a random access procedure receives a first parameter and a second parameter of an upper layer, receives a PDCCH including DCI, and transmits a PUSCH scheduled by the DCI. A third parameter is defined in advance by a default table. The first parameter, the second parameter, and the third parameter indicate information on PUSCH time domain resource allocation. When CRC scrambled by TC-RNTI is added to the DCI, one is selected from the first parameter and the third parameter regardless of whether the second parameter is received. The PUSCH time domain resource allocation is performed based on the selected parameter.SELECTED DRAWING: Figure 8

Description

The present invention relates to base station devices, terminal devices, communication methods, and integrated circuits.

Currently, LTE (Long Term Evolution)-Advanced Pro and NR (New Radio) in the Third Generation Partnership Project (3GPP) as wireless access methods and wireless network technologies for 5th generation cellular systems. Technology) has been studied and standards have been established (Non-Patent Document 1).

The 5th generation cellular system includes eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-latency and high-reliability communication, and IoT (Internet of Things). Three mMTCs (massive Machine Type Communication), in which a large number of machine-type devices are connected, are required as assumed scenarios for services.

RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016

An object 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-mentioned wireless communication system.

(1) In order to achieve the above object, the aspect of the present invention has taken the following measures. That is, the terminal device that performs the random access procedure according to one aspect of the present invention is scheduled by the receiving unit that receives the first parameter and the second parameter of the upper layer and receives the PDCCH including the DCI, and the DCI. It comprises a transmitter for transmitting PUSCH, a third parameter is predefined by a default table, the first parameter, the second parameter, and the third parameter are in the PUSCH time region. Indicates resource allocation information, and when a CRC scrambled by TC-RNTI is added to the DCI, the first parameter and the third parameter, regardless of whether or not the second parameter is received, One is selected from among them, and the time area resource allocation of the PUSCH is given based on the selected parameter.

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

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

(4) Further, the communication method in one 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 the first parameter and the second parameter of the upper layer. , A step of transmitting a PDCCH containing a DCI, and a step of receiving a PUSCH scheduled by the DCI, the third parameter being predefined by a default table, said first parameter, said first. The second parameter and the third parameter indicate information on the PUSCH time area resource allocation, and when a CRC scrambled by TC-RNTI is added to the DCI, whether or not the second parameter is received. Regardless, one of the first parameter and the third parameter is selected, and the PUSCH time region 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 mounted on a terminal device that performs a random access procedure, receives the first parameter and the second parameter of the upper layer, and performs DCI. The function of receiving the PDCCH including the PDCCH, the function of transmitting the PUSCH scheduled by the DCI, and the function of transmitting the PUSCH scheduled by the DCI, and the third parameter are defined in advance by the default table by the default table, and the first parameter, the said The second parameter, and the third parameter, indicate the information of the PUSCH time area resource allocation, and when the CRC scrambled by TC-RNTI is added to the DCI, the reception of the second parameter One of the first parameter and the third parameter is selected regardless of the presence or absence, and the time area resource allocation of the PUSCH is given based on the selected parameter.

(6) Further, the integrated circuit according to one 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 is a first parameter and a second parameter of the upper layer. The function of transmitting the PDCCH including the DCI, the function of receiving the PUSCH scheduled by the DCI, and the function of causing the base station apparatus to exert the third parameter are defined in advance by the default table. The first parameter, the second parameter, and the third parameter indicate information on PUSCH time region resource allocation, and when CRC scrambled by TC-RNTI is added to the DCI, the said. One of the first parameter and the third parameter is selected regardless of whether or not the second parameter is received, and the time area resource allocation of the PUSCH is given based on the selected parameter.

According to 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 concerns on embodiment of this invention. It is a figure which shows an example of the schematic structure of the uplink and the downlink slot which concerns on embodiment of this invention. It is a figure which showed the relationship in the time domain of the subframe, a slot, and a minislot which concerns on embodiment of this invention. It is a figure which shows an example of the slot or the subframe which concerns on embodiment of this invention. It is a figure which showed an example of the beamforming which concerns on embodiment of this 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 apparatus 1 which concerns on embodiment of this invention. It is a figure which shows an example of the field contained in the RAR UL grant which concerns on embodiment of this invention. It is a figure which defines the resource allocation table applied to the 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 the 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 the PUSCH scheduled by the RAR UL grant which concerns on this embodiment. It is a flow chart 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 apparatus 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.

Hereinafter, embodiments of the present invention will be described.

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

The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). The base station apparatus 3 includes a radio base station apparatus, 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 ( It is also called NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. The base station device 3 may include a core network device. Further, the base station apparatus 3 may include one or a plurality of transmission / reception points 4 (transmission reception points). At least a part of the functions / processes of the base station apparatus 3 described below may be the functions / processes at each transmission / reception point 4 included in the base station apparatus 3. The base station apparatus 3 may serve the terminal apparatus 1 with the communicable range (communication area) controlled by the base station apparatus 3 as one or a plurality of cells. Further, the base station apparatus 3 may serve the terminal apparatus 1 with the communicable range (communication area) controlled by one or a plurality of transmission / reception points 4 as one or a plurality of 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 subregions may be identified based on the beam index or precoding index used in beamforming.

The wireless communication link from the base station device 3 to the terminal device 1 is referred to as a downlink. The wireless communication link from the terminal device 1 to the base station device 3 is referred to as an uplink.

In FIG. 1, in wireless communication between a terminal device 1 and a base station device 3, orthogonal frequency division multiplexing (OFDM) including cyclic prefix (CP) and single carrier frequency division multiplexing (SC-) are used. FDM: Single-Carrier Frequency Division Multiplexing (FDM), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM), Multi-Carrier Code Division Multiplexing (MC-CDM) are used. May be good.

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

In the present embodiment, OFDM is described as a transmission method using an OFDM symbol, but the case where the above-mentioned other transmission methods are used is also included in the present invention.

Further, in FIG. 1, in the wireless communication between the terminal device 1 and the base station device 3, the above-mentioned transmission method in which CP is not used or zero padding is performed instead of CP may be used. Also, CP and zero padding may be added both forward and backward.

One aspect of this embodiment may be operated in carrier aggregation or dual connectivity with radio access technology (RAT) such as LTE and 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 standalone and stand-alone. In dual connectivity operations, SpCell (Special Cell) is either MCG's PCell or SCG's PSCell, depending on whether the MAC (MAC: Medium Access Control) entity is associated with MCG or SCG, respectively. It is 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 this embodiment, one or more serving cells may be set for the terminal device 1. The plurality of serving cells set may include one primary cell and one or more secondary cells. The primary cell may be the serving cell in which the initial connection establishment procedure was performed, the serving cell in which the connection re-establishment procedure was initiated, or the cell designated as the primary cell in the handover procedure. Good. One or more secondary cells may be set when or after an RRC (Radio Resource Control) connection is established. However, the plurality of set serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information on the uplink among one or a plurality of secondary cells in which the terminal device 1 is set. Further, a subset of two types of serving cells, a master cell group and a secondary cell group, may be set for the terminal device 1. The master cell group may consist of one primary cell and zero or more secondary cells. The secondary cell group may consist of one primary secondary cell and zero or more secondary cells.

TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) may be applied to the wireless communication system of the present embodiment. TD for all of multiple cells
A D (Time Division Duplex) system or an FDD (Frequency Division Duplex) system may be applied. Further, the cell to which the TDD method is applied and the cell to which the FDD method 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 referred to as a downlink component carrier (or downlink carrier). In the uplink, the carrier corresponding to the serving cell is referred to as an uplink component carrier (or uplink carrier). In the side link, the carrier corresponding to the serving cell is referred to as 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 channel and the physical signal 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.

Further, the PBCH may be used to notify the time index within the period of the block of the synchronization signal (also referred to as the SS / PBCH block). Here, the time index is information indicating the synchronization signal in the cell and the index of PBCH. For example, when transmitting an SS / PBCH block using the assumption of three transmission beams (transmission filter setting, pseudo-same position (QCL: Quasi Co-Location) regarding reception space parameters), it is set within a predetermined period or set. The time order within the cycle may be shown. Further, the terminal device may recognize the difference in the time index as the difference in the transmission beam.

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

For example, the following DCI formats 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
DCI format 0_0 may be used for scheduling PUSCH 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). DCI format 0_0 may be supplemented with a CRC scrambled by any of C-RNTI, CS-RNTI, MCS-C-RNTI, and / or TC-RNTI. DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

DCI format 0_1 may be used for scheduling PUSCH in a serving cell. DCI format 0_1 refers to information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band width part (BWP), channel state information (CSI) request, and sounding reference. It may include information about signal (SRS: Sounding Reference Signal) requests, antenna ports. DCI format 0-1 may be added with a CRC scrambled by any of RNTI, C-RNTI, CS-RNTI, SP (Semi Persistent) -CSI-RNTI, and / or MCS-C-RNTI. .. DCI format 0_1 may be monitored in the UE-specific search space.

DCI format 1_0 may be used for scheduling PDSCH 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). DCI format 1_0 is an identifier among C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI) -RNTI, Random Addition (RA) -RNTI, and / or , TC-RNTI scrambled CRC may be added. DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

DCI format 1-11 may be used for scheduling PDSCH in a serving cell. The DCI format 1-11 is information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
It may include information indicating a band portion (BWP), transmission configuration indication (TCI), and / or information about an antenna port. The DCI format 1-11 may be supplemented with a CRC scrambled by any of C-RNTI, CS-RNTI, and / or MCS-C-RNTI within RNTI. DCI format 1-11 may be monitored in the UE-specific search space.

DCI format 2_0 is used to signal the slot format of one or more slots. The slot format is defined as each OFDM symbol in the slot classified as downlink, flexible, or uplink. For example, when the slot format is 28, DDDDDDDDDDDDDFU is applied to the 14-symbol 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 slot will be described later.

The DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks and OFDM symbols that may be assumed to have no transmission. This information may be referred to as a preemption instruction (intermittent transmission instruction).

DCI format 2_2 is used for the transmission of transmit power control (TPC) commands for PUSCH and PUSCH.

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

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

The CRC (Cyclic Redundancy Check) parity bits added to the DCI format transmitted by one PDCCH are 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 to broadcast system information. P-RNTI may be an identifier used for paging and notification of system information changes. C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying the terminal device in the cell. The Temporary C-RNTI is an identifier for identifying the terminal device 1 that 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. The Temporary C-RNTI (TC-RNTI) is used to control PDSCH or PUSCH transmissions 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 the frequency and time position information of the physical random access channel that transmitted the random access preamble.

The PUCCH is used for transmitting 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 status of the downlink channel. Further, the uplink control information may include a scheduling request (SR: Scheduling Request) used for requesting 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).

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

PUSCH is uplink data (UL-SCH: Uplink Shared CHannel) from the MAC layer.
Alternatively, it may be used to transmit HARQ-ACK and / or CSI with uplink data. It may also be used to transmit 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). For example, the base station device 3 and the terminal device 1 transmit and receive RRC signaling (RRC message: Radio Resource Control message, also referred to as RRC information: Radio Resource Control information) in the radio resource control (RRC) layer. You may. Further, the base station device 3 and the terminal device 1 may transmit and receive MAC control elements in the MAC (Medium Access Control) layer. Further, the RRC layer of the terminal device 1 acquires the system information notified from the base station device 3. Here, RRC signaling, system information, and / or MAC control elements are also referred to as upper layer signals (higher layer signaling) or upper layer parameters. Since the upper layer here means an upper layer as seen from the physical layer, it may include one or more such as a MAC layer, an RRC layer, an RLC layer, a PDCP layer, and a NAS (Non Access Stratum) layer. For example, in the processing of the MAC layer, the upper layer may include one or more such as an RRC layer, an RLC layer, a PDCP layer, and a NAS layer. Hereinafter, the meanings of "A is given by the upper layer" and "A is given by the upper layer" mean that the upper layer of the terminal device 1 (mainly the RRC layer, the MAC layer, etc.) is 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 the information element of A, the terminal device 1 receives the RRC message including the information element of A, and the terminal device 1 receives the terminal from the upper layer of the terminal device 1. It is given to the physical layer of the device 1. The information element is included in the RRC message.

The PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. Here, in PDSCH, the RRC signaling transmitted from the base station device 3 may be a signal common to a plurality of terminal devices 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 information specific to the terminal device (UE specific) may be transmitted to a certain terminal device 1 using dedicated signaling. The PUSCH may also be used to transmit the UE Capability on the uplink.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used to transmit 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 by the terminal device 1 to synchronize the frequency domain and the time domain of the downlink. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. The beam may be referred to as a transmit or receive filter setting, or a spatial domain transmit filter or a spatial domain receive filter.

The reference signal is used by the terminal device 1 to compensate the propagation path of the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate the downlink CSI. Further, the reference signal may be used for fine synchronization such as numerology such as radio parameters and subcarrier intervals and window synchronization of FFT.

In this 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 modulated signals. Two types of DMRS, a reference signal for demodulating PBCH and a reference signal for demodulating PDSCH, may be defined, or both may be referred to as DMRS. CSI-RS is used for channel state information (CSI) measurement and beam management, and periodic or semi-persistent or aperiodic CSI reference signal transmission methods are applied. The CSI-RS may be defined as a non-zero power (NZP: Non-Zero Power) CSI-RS and a zero power (ZP: Zero Power) CSI-RS with zero transmission power (or reception power). Here, ZP CSI-RS may be defined as a CSI-RS resource with zero or no transmit power; PTRS is used to track phase on the time axis for the purpose of guaranteeing frequency offset due to phase noise. Used. TRS is used to guarantee Doppler shift during high speed movement. TRS may be used as one setting of CSI-RS. For example, 1 port of CSI-RS is used as TRS. Radio resources may be set.

In this embodiment, any one or more of the following uplink reference signals are used.

・ DMRS (Demodulation Reference Signal)
・ PTRS (Phase Tracking Reference Signal)
・ SRS (Sounding Reference Signal)
DMRS is used to demodulate modulated signals. Two types of DMRS, a reference signal for demodulating PUCCH and a reference signal for demodulating PUSCH, may be defined, or both may be referred to as DMRS. SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management. PTRS is used to track the phase on the time axis for the purpose of guaranteeing the frequency offset due to phase noise.

The downlink physical channel and / or the downlink physical signal are collectively referred to as a downlink physical 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 collectively referred to as 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. The 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 referred to as a transport block (TB) and / or a MAC PDU (Protocol Data Unit). HARQ (Hybrid Automatic Repeat reQuest) is controlled for each transport block in the MAC layer. A transport block is a unit of data that the MAC layer delivers to the physical layer. In the physical layer, the transport block is mapped to a codeword, and the coding process is performed for each codeword.

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

The SS / PBCH block is a unit block containing at least a synchronization signal (PSS, SSS) and / or PBCH. Transmitting a signal / channel included in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When the base station apparatus 3 transmits a synchronization signal and / or PBCH using one or more SS / PBCH blocks in the SS burst set, an independent downlink transmission beam for each SS / PBCH block may be used. 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.

The SS burst set may be transmitted periodically. For example, a cycle to be used for initial access and a cycle to be set for a connected (Connected or RRC_Connected) terminal device may be defined. Also connected (Connected or RRC_Connected)
The period set for the terminal device may be set in the RRC layer. Also, the cycle set for the connected (Connected or RRC_Connected) terminal is the cycle of the radio resource in the time domain that may potentially transmit, and is the base station apparatus 3 actually transmitting? You may decide whether or not. Further, the cycle for being used for the initial access may be defined in advance in the specifications and the like.

The SS burst set may be determined based on the system frame number (SFN). Further, the start position (boundary) of the SS burst set may be determined based on the SFN and the period.

The SS / PBCH block is assigned an SSB index (which may be referred to as an SSB / PBCH block index) according to its 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 in each SS burst set in a plurality of SS burst sets are assigned the same SSB index. SS / PBCH blocks having the same relative time in each SS burst set in a plurality of SS burst sets may be assumed to be QCLs (or the same downlink transmission beam is applied). Also, antenna ports in SS / PBCH blocks with the same relative time in each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

Within a period of an SS burst set, SS / PBCH blocks to which the same SSB index is assigned may be assumed to be QCL with respect to mean delay, mean gain, Doppler spread, Doppler shift, spatial correlation. A setting corresponding to one or more SS / PBCH blocks (or a reference signal) which is a QCL may be referred to as a 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 (number) in the SS burst or SS burst set, or in the cycle of SS / PBCH blocks. May be defined. The number of SS / PBCH blocks may also 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, a beam group may be defined as the number of different SS / PBCH blocks or the number of different beams contained within an SS burst, or within an SS burst set, or within a period of SS / PBCH blocks.

Hereinafter, the reference signals described in the present embodiment are downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DM-RS, CSI-RS, uplink reference signals, SRS, and / or uplink DM-. Includes RS. For example, a downlink reference signal, a synchronization signal and / or an 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-RS, CSI-RS and the like. Reference signals used in the uplink include uplink reference signals, SRS, and / or uplink DM-RS and the like.

In addition, the reference signal may be used for radio resource measurement (RRM). The reference signal may also be used for beam management.

Beam management includes analog and / or digital beams in the transmitting device (base station device 3 in the case of downlink and terminal device 1 in the case of uplink) and the receiving device (terminal device 1 in the case of downlink). , In the case of uplink, the base station device 3) may be the procedure of the base station device 3 and / or the terminal device 1 for matching the directivity of the analog and / or digital beam and acquiring 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, 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 having a higher gain or changing the beam between the base station device 3 and the terminal device 1 which is optimal by moving the terminal device 1. The beam recovery may be a procedure for reselecting a beam when the quality of the communication link deteriorates due to a blockage caused by a shield or the passage of a person in the communication between the base station device 3 and the terminal device 1.

Beam management may include beam selection and beam improvement. Beam recovery may include the following procedures.
-Detection of beam failure-Discovery of a new beam-Transmission of beam recovery request-Monitoring of response to beam recovery request For example, when selecting the transmission beam of base station device 3 in 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. Further, the CSI-RS Resource Index (CRI) may be used as a report to the base station apparatus 3, or for demodulation used for demodulation of PBCH and / or PBCH included in the SS / PBCH block. An index indicated by a sequence of reference signals (DMRS) may be used.

Further, the base station apparatus 3 instructs the time index of CRI or SS / PBCH when instructing the beam to the terminal apparatus 1, and the terminal apparatus 1 receives based on the instructed time index of CRI or SS / PBCH. To do. At this time, the terminal device 1 may set a spatial filter based on the indicated CRI or SS / PBCH time index and receive it. Further, the terminal device 1 may receive using the assumption of pseudo-same position (QCL: Quasi Co-Location). One signal (antenna port, sync signal, reference signal, etc.) is "QCL" with another signal (antenna port, sync signal, reference signal, etc.), or "QCL assumption is used" means that one signal is It can be interpreted as being associated with another signal.

If the Long Term Property of a channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port, then the two antenna ports are said to be QCL. .. The long interval characteristics of the channel include one or more of delay spreads, Doppler spreads, Doppler shifts, average gains, and average delays. 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 also be extended to beam management. Therefore, a QCL extended to the space may be newly defined. For example, as the long term property of the channel in the QCL assumption of the spatial domain, the approach angle (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or the angle spread in the radio link or channel. (Angle Spread, for example ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)), delivery angle (AoD, ZoD, etc.) and its angle spread (Angle Spread, for example ASD (Angle Spread of Departure) and ZSD ( Zenith angle Spread of Departure), Spatial Correlation, reception space parameters.

For example, when the reception space parameter between the antenna port 1 and the antenna port 2 can be regarded as QCL, the reception beam (reception space filter) for receiving the signal from the antenna port 1 receives the signal from the antenna port 2. It means that the beam can be inferred.

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

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

The subframe will be described below. Although it is referred to as a subframe in the present embodiment, it may be referred to as a resource unit, a wireless frame, a time interval, 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 of the radio frames is 10 ms long. Further, each of the wireless frames 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 interval is 60 kHz, X = 7 or X = 14, which is 0.125 ms and 0.25 ms, respectively. Further, for example, in the case of X = 14, W = 10 when the subcarrier interval is 15 kHz, and W = 40 when the subcarrier interval is 60 kHz. FIG. 3 shows the case of X = 7 as an example. It can be expanded in the same manner when X = 14. Further, the uplink slot is also defined in the same manner, 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 bandwidth (BWP: BandWidth Part). Further, the slot may be defined as a transmission time interval (TTI). Slots do not have to be defined as TTI. The TTI may be the transmission period of the transport block.

The signal or physical channel transmitted in each of the slots may be represented by a resource grid. The resource grid is defined by multiple subcarriers and multiple OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and for each carrier. The number of subcarriers that make up a slot depends on the bandwidth of the downlink and uplink of the cell, respectively. 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.

The resource grid is used to represent the mapping of resource elements of a physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier interval is 15 kHz, the number of OFDM symbols included in the subframe is X = 14, and in the case of NCP, one physical resource block has 14 consecutive OFDM symbols in the time domain and the frequency domain. It is defined from 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 at a subcarrier interval of 60 kHz, one physical resource block is, for example, 12 (the number of OFDM symbols contained 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. For example, resource blocks may be configured at subcarrier intervals of 15 kHz and numbered in ascending order. Subcarrier index 0 at reference resource block index 0 may be referred to as reference point A (may simply be 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 block is a resource block numbered in ascending order from 0 contained in the band portion (BWP) described later, and the physical resource block is a resource block numbered in ascending order from 0 contained in the band portion (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 in the upper layer (upper layer) with respect to the downlink BWP, and the uplink It is given in the upper layer in BWP. Here, when μ is given, the subcarrier interval Δf is given at Δf = 2 ^ μ · 15 (kHz).

In the subcarrier spacing setting μ, slots are counted in ascending order from 0 to N ^ {subframe, μ} _ {slot} -1 in the subframe, and from 0 to N ^ {frame, μ} _ {slot in the frame. } -1 is counted in ascending order. There are consecutive OFDM symbols of N ^ {slot} _ {symb} in the slot based on the slot settings and 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, the subframe, the slot, and the mini slot will be described. FIG. 4 is a diagram showing the relationship between the subframe, the slot, and the mini slot 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 contained in the slot is 7 or 14, and the slot length varies depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, 14 OFDM symbols are included in one subframe. 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 (which may also be referred to as a subslot) is a time unit composed of fewer OFDM symbols than the slot contains. The figure shows the case where the mini slot is composed of 2 OFDM symbols as an example. The OFDM symbols in the minislot may match the OFDM symbol timings that make up the slot. The minimum unit of scheduling may be a slot or a mini slot. Also, allocating mini-slots may be referred to as non-slot-based scheduling. Also, scheduling a minislot may be expressed as a resource whose time position relative to the start position of the reference signal and data is fixed. 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 a slot format. Here, a 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 a downlink and U indicates an uplink. As shown in the figure, within a certain time interval (for example, the minimum time interval that must be assigned to one UE in the system).
-It may include one or more of the downlink symbol, the flexible symbol, and the uplink symbol. In addition, 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. It should be noted that scheduling a slot may be expressed as a resource whose 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.

FIG. 5A may also be referred to as a time interval (for example, the minimum unit of time resources that can be allocated 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. (May be), all of which are used for downlink transmission, and FIG. 5 (b) shows the PDCCH processing delay and downlink by scheduling the uplink via, for example, PDCCH with the first time resource. The uplink signal is transmitted via a flexible symbol that includes the uplink switching time and the generation of the transmit signal. FIG. 5C is the first time resource used to transmit the PDCCH and / or the downlink PDSCH, the PUSCH or PUCCH through the processing delay and downlink to uplink switching time, and the gap for generating the transmit signal. Used for transmission of. Here, as an example, the uplink signal may be used to transmit HARQ-ACK and / or CSI, i.e. UCI. FIG. 5 (d) shows the PDCCH and / or PDSCH transmission in the first time resource, the uplink PUSCH and / or the uplink PUSCH and / or through the downlink to uplink switching time, the gap for generating the transmit 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. 5 (e) 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 the antenna element 52 transmits the signal in any direction with respect to the transmission signal. You can direct the beam. Typically, the TXRU may be defined as an antenna port, and in the terminal device 1, only the antenna port may be defined. Since the directivity can be directed in an arbitrary direction by controlling the phase shifter 51, the base station device 3 can communicate with the terminal device 1 using a beam having a high gain.

Hereinafter, the band portion (BWP, Bandwidth part) will be described. BWP is also referred to as carrier BWP. The BWP may be set for each of the downlink and the uplink. A BWP is defined as a set of contiguous physical resources selected from a contiguous subset of common resource blocks. The terminal device 1 may be configured with up to four BWPs in which one downlink carrier BWP (DL BWP) is activated at a given time. The terminal device 1 may be configured with up to four BWPs in which one uplink carrier BWP (UL BWP) is activated at a given time. In the case of carrier aggregation, the BWP may be set in each serving cell. At this time, the fact that one BWP is set in a certain serving cell may be expressed as not setting the BWP. Further, it may be expressed that BWP is set when two or more BWPs are set.
<MAC entity operation>
In the activated serving cell, there is always one active (activated) BWP. BWP switching for a serving cell is used to activate an inactive (deactivated) BWP and deactivate an active (activated) BWP. Will be done. BWP switching for a serving cell is controlled by a PDCCH indicating a downlink assignment or uplink grant. BWP switching for a serving cell may also be further controlled by the BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of the random access procedure. In the addition of SpCell (PCell or PSCell) or activation of SCell, one BWP is primarily active without receiving a PDCCH indicating a downlink assignment or uplink grant. The first active DL BWP (first active DL BWP) and 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 serving cell is specified by the RRC or PDCCH sent from the base station device 3 to the terminal device 1. Further, 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 (such as a TDD band), 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 in which the BWP is set, the MAC entity of the terminal device 1 applies normal processing. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. 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 UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, Do not send SRS and do not receive DL-SCH. If a serving cell is deactivated, the active BWP may be absent (eg, the active BWP is deactivated).
<RRC operation>
The BWP information element (IE) included in the RRC message (notified system information or information sent in a 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 base station device 3) should have at least one downlink BWP (for example, if the serving cell is configured for uplink) or two (supplementary uplink). At least the initial BWP (initial BWP) including the uplink BWP of (such as when is used) is set for the terminal device 1. In addition, the network may set up additional uplink BWPs and downlink BWPs for a serving cell. BWP settings are divided into uplink parameters and downlink parameters. 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 with dedicated signals. The BWP is identified by the BWP ID. The initial BWP has a BWP ID of 0. The BWP ID of the other BWP takes a value from 1 to 4.

When 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 set to
For PDCCH reception in the Control Resource Set (CORESET) for the Type 0 PDCCH Common Search Space, it may be defined by the location and number of consecutive PRBs, subcarrier spacing, and cyclic prefixes. The position of the continuous PRB begins with the lowest index PRB and ends with the highest index PRB between the PRBs of the control resource set for the type 0PDCCH 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 ServingCellCongficomSIB is used within SIB1 to set cell-specific parameters of the serving cell for the terminal device 1.

That is, if 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 in the control resource set (CORESET # 0) for the type 0 PDCCH common search space. There 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 locationAndBandwise included in the upper layer parameter initialDownlinkBWP. The upper layer parameter locationAndBandwise may indicate the position and bandwidth of the frequency domain of the initial DL BWP.

As described above, a plurality of DL BWPs may be set for the terminal device 1. Then, among the DL BWP 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 for 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. The initial UL BWP (initial active UL BWP) may be set (provided) in the terminal device 1 by the parameter internalUplinkBWP of the upper layer for the operation in the SpCell or the secondary cell. When a supplementary UL carrier is set for the terminal device 1, the terminal device 1 is subjected to the initial UL of the supplementary uplink carrier by the initialUplinkBWP included in the upper layer parameter supplementaryUplink. BWP may be set.

Hereinafter, the control resource set (CORESET) in the present embodiment will be described.

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

The control resource set specified by the identifier 0 (ControlResourceSetId 0) of CORESET is referred to as CORESET # 0. CORESET # 0 may be set by pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in the ServingCellCongficomcon. That is, the setting information of CORESET # 0 may be pdcch-ConfigSIB1 included in the MIB or PDCCH-ConfigCommon included in the ServingCellCongficomcon. The setting information of CORESET # 0 may be set by the controlResourceSetZero included in the PDCCH-ConfigSIB1 or the PDCCH-ConfigCommon. That is, the information element controlResourceSetZero is used to indicate the initial DL BWP CORESET # 0 (common CORESET). The CORESET represented by pdch-ConfigSIB1 is CORESET # 0. The information element pdcch-ConfigSIB1 in the MIB or dedicated configuration is used to set the initial DL BWP. CORESET setting information for CORESET # 0 pdch-ConfigSIB1 explicitly specifies the CORESET identifier, the CORESET frequency resource (for example, the number of continuous resource blocks), and the time resource (the number of continuous symbols). No information is included, but the frequency resources (eg, the number of contiguous resource blocks) and time resources (for example, the number of contiguous symbols) of CORESET with respect to CORESET # 0 are implied by the information contained in pdch-ConfigSIB1 Can be identified. The information element PDCCH-ConfigCommon is used to set cell-specific PDCCH parameters provided by the SIB. The PDCCH-ConfigCommon may also be provided at the time of handover and the 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 have to be included in the BWP settings other than the initial BWP. The controlResourceSetZero corresponds to 4 bits (for example, 4 bits of MSB and 4 bits of the most significant bit) of pdch-ConfigSIB1. CORESET # 0 is a control resource set for a type 0 PDCCH common search space.

The setting information of the additional common CORESET (additional common control resource set) may be set by the controlControlResourceSet included in the PDCCH-ConfigCommon. Also, additional common CORESET configuration information may be used to specify additional common CORESET for system information and / or paging procedures. Additional common CORESET configuration information may be used to specify additional common CORESETs used for random access procedures. Additional common CORESET configuration information may be included within each BWP configuration. The CORESET identifier shown in the controlControlRelocationSet takes a non-zero value.

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

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, CORESET, search space, etc.) for a BWP. PDCCH-Config may be included in the settings of each BWP.

That is, in the present embodiment, the setting information of the common CORESET indicated by MIB is pdcch-ConfigSIB1, the setting information of the common CORESET indicated by PDCCH-ConfigCommon is controlResourceSetZero, and the setting information of the common CORESET indicated by PDCCH-ConfigCommon (addition). The setting information of (common CORESET) is commonControlResourceSet. Further, the setting information of one or a plurality of CORESETs (UE specifically configured Control Resource Sets, UE-specific CORESETs) indicated by PDCCH-Config is controlResourceSetToAdModList.

A search space is defined to search for PDCCH candidates. The searchSpaceType included in the search space setting information indicates that the search space is a common search space (CSS) or a UE-specific search space (USS). The UE-specific search space is derived from at least the 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 a CCE (Control Channel Element) having a predetermined index. CCE is composed of a plurality of resource elements. The search space setting information includes information in the DCI format monitored in the search space.

The search space setting information includes the CORESET identifier specified in 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, the CORESET associated with the search space is a CORESET identified by the identifier of the CORESET included in the search space. The DCI format indicated by the search space configuration information 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 the ra-SearchSpace. That is, the CRC-added DCI format scrambled by RA-RNTI or TC-RNTI is monitored on the CORESET associated with the ra-SearchSpace.

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 does not have to be included in the setting of BWP (additional BWP) other than the initial DLBWP. When a BWP (additional BWP) other than the initial DL BWP refers to the setting information of CORESET # 0 (refer, acquire, etc.), the CORESET # 0 and SS blocks are included in the additional BWP in the frequency domain, and the additional BWP is included. It may be necessary to at least meet the use of the same subcarrier spacing. In other words, when a BWP (additional BWP) other than the initial BWP refers to the setting information of CORESET # 0 (refer, acquire, etc.), the bandwidth and SS block of the initial DL BWP in the frequency domain 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 (refer, acquire, etc.) by indicating the identifier 0 of CORESET # 0. be able to. That is, at this time, CORESET # 0 is set only for the initial DL BWP, but the terminal device 1 operating on another BWP (additional BWP) refers to the setting information of CORESET # 0. Can be done. Further, 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 any of the conditions for using the same subcarrier interval is not satisfied. , The terminal device 1 does not have to expect the additional DL BWP to refer to the setting information of CORESET # 0. That is, in this case, the base station device 3 does not have to set the terminal device 1 to refer to the setting information of CORESET # 0 by the additional DL BWP. Here, the initial DL BWP may be an initial DL BWP of size N ^size _{BWP, 0} .

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

Terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs located in each active serving cell that is configured to monitor PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring means decoding each PDCCH candidate according to one or more DCI formats being monitored. The set of PDCCH candidates monitored by the terminal device 1 is defined by the PDCCH search space sets). One search space set is a common search space set or a UE-specific search space set. In the above, the search space set is referred to as a search space, the common search space set is referred to as a common search space, and the UE-specific search space set is referred to as a UE-specific search space. The terminal device 1 monitors PDCCH candidates with one or more of the following search space sets.
--Type0-PDCCH common search space set (a Type0-PDCCH common search)
space set, type 0 common search space): This search space set is contained in the upper layer parameters pdcch-ConfigSIB1 represented by MIB or search space SIB1 (searchSpaceSIB1) or PDCCH-ConfigCommon represented by PDCCH-ConfigCommon. Set by searchSpaceZero. This search space is for monitoring the DCI format of the SI-RNRI scrambled CRC in the primary cell.
--Type0A-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 an upper layer parameter. Will be done. This search space is for monitoring the DCI format of the SI-RNRI scrambled CRC in the primary cell.
--Type 1 PDCCH common search space set (a Type1-PDCCH common search)
space set, type 1 common search space): This search space set is set by the upper layer parameter, the search space (ra-SearchSpace) for the random access procedure represented by PDCCH-ConfigCommon. 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 random access procedures.
--Type2-PDCCH common search (a Type2-PDCCH common search)
space set, type 2 common search space): This search space set is set by the upper layer parameter, the pagingSearchSpace for the paging procedure represented by PDCCH-ConfigCommon. This search space is for monitoring the DCI format of the P-RNTI scrambled CRC in the primary cell.
--Type3 PDCCH common search space set (a Type3-PDCCH common search)
space set ,, type 3 common search space): In this search space set, the search space type indicated by PDCCH-Config, which is a parameter of the upper layer, is set by the common search space (SearchSpace). This search space is for monitoring the DCI format of CRC scrambled with INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. For the primary license, it is for monitoring the DCI format of the CRC scrambled with C-RNTI, CS-RNTI (s), or MSC-C-RNTI.

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

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

The 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 serving cell. The BWP identifier included in the UL BWP configuration information is used to identify (see) the UL BWP in a serving cell. The BWP identifier is given to each of 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 identifier of the BWP corresponding to the UL BWP may be referred to as the UL BWP index. The initial DL BWP is referenced by identifier 0 of the DL BWP. The initial UL BWP is referenced by the UL BWP identifier 0. Each of the other DL BWPs or other UL BWPs may be referenced from identifier 1 of the BWP to maxNrovBWPs. That is, the BWP identifier (bwp-Id = 0) set to 0 is associated with the initial BWP and cannot be used for other BWPs. maxNrovBWPs is the maximum number of BWPs per serving cell, which is 4. That is, the value of the identifier of the other BWP 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. The fact that the DL BWP and the UL BWP have the same BWP identifier may mean that the DL BWP and the UL BWP are paired.

In the terminal device 1, one primary cell and up to 15 secondary cells may be set.

The procedure for receiving the PDSCH will be described below.

The terminal device 1 may decode (receive) the corresponding PDSCH by detecting the PDCCH including the DCI format 1_1 or the DCI format 1-1.1. The corresponding PDSCH is scheduled (shown) by its DCI format (DCI). The scheduled start position (start symbol) of the PDSCH is referred to as S. The PDSCH start symbol S may be the first symbol to which the PDSCH is transmitted (mapped) in a slot. The start symbol S corresponds to the beginning 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 scheduled PDSCH is referred to as L. The number L of consecutive symbols is counted from the start symbol S.
The determination of S and L assigned to the 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 a value from 0 to 3. L takes a value from 3 to 14. However, the sum of S and L takes a value from 3 to 14. In PDSCH mapping type B, S takes a value 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 position of the DMRS symbol for PDSCH depends on the type of PDSCH mapping. The position of the first DM-RS symbol for the 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, if 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, if 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 a value of 3 only when dmrs-TypeA-Position is set to'pos3'. That is, when 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 a 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 assigned PDSCH S is 3. The L of the PDSCH assigned is 7. In FIG. 7A, 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 assigned PDSCH S is 4. The L of the PDSCH assigned is 4. In FIG. 7B, the position of the first DMRS symbol for PDSCH is the first symbol to which PDSCH is assigned.

Hereinafter, a method for specifying the PDSCH time domain resource allocation will be described.

The base station apparatus 3 may schedule the terminal apparatus 1 to receive the PDSCH by DCI. The terminal device 1 may receive the PDSCH by detecting DCI addressed to its own device. When specifying 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 contains 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 shown in the'Time domain resource assignment'field included in the DCI that schedules the PDSCH. That is, the base station device 3 determines the PDSCH resource allocation to the terminal device 1, generates a'Time domain resource allocation'field of a value based on the determined resource allocation, and DCI including the'Time domain resource assessment' field. Is transmitted to the terminal device 1. The terminal device 1 identifies the resource allocation in the PDSCH time direction 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 the PDSCH time domain resource allocation based on the table shown in FIG. The resource allocation table contains the configuration of one or more PDSCH 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 set from the RRC signal of the upper layer. The predefined resource allocation tables are defined as, for example, the default PDSCH time domain resource allocation A, the default PDSCH time domain resource allocation B, and the default PDSCH time domain resource allocation C. Hereinafter, the default PDSCH time domain resource allocation A will be referred to as a default table A. The default PDSCH time domain resource allocation B is referred to as the default table B. The default PDSCH time domain resource allocation C is referred to as the default table C.

FIG. 11 is a diagram showing an example of the default table A according to the present embodiment. FIG. 12 is a diagram showing an example of the default table B according to the present embodiment. FIG. 13 is a diagram showing an example of the default table C according to the present embodiment. In the example of FIG. 11, the number of rows in 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) has a PDSCH mapping type, a slot offset K ₀ between the PDCCH containing DCI and its PDSCH, the start symbol S of the PDSCH in the slot, and a continuous allocation. Define the number of symbols L to be.

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 contains one or more information elements PDSCH-TimeDomainRelocationAllocation. PDSCH-TimeDomainRelocationAllocation indicates the setting of PDSCH time domain resource allocation. The PDSCH-TimeDomainRelocationAllocation may be used to set the time domain relationship between the PDCCH containing DCI and the PDSCH. That is, the pdsch-TimeDomainAllocationList is a list containing one or more information elements. One PDSCH-TimeDomainRelocationAllocation may be referred to as one entry (or one row). For example, the pdsch-TimeDomainAllocationList contains up to 16 entries, and any one entry may be used depending on the 4-bit field contained in the DCI. However, the number of entries included in the pdsch-TimeDomainAllocationList may be different, and the number of bits of the related fields included in the DCI may be different. In each entry of pdsch-TimeDomainAllocationList, K ₀ , mappingType, and / or startSymbolAndLength may be indicated. K ₀ indicates the slot offset between the PDCCH containing DCI and its PDSCH. If the PDSCH-TimeDomainRelocationAllocation does not indicate K ₀ , the terminal device 1 may assume that the value of K ₀ is a predetermined value (eg 0). The mappingType indicates whether the mapping type of the corresponding PDSCH is PDSCH mapping type A or PDSCH mapping type B. The startSymbolAndLength is an index that gives a valid combination of the corresponding PDSCH start symbol S and the number of consecutive allocated symbols L. The startSymbolAndLength may be referred to as a start and length indicator (SLIV). When SLIV is applied, unlike the case of using the default table, 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. 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 cell-specific parameters for PDSCH for a BWP. The information element pdsch-Config is used to set UE-specific parameters for PDSCH for a BWP.

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

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

Hereinafter, the slot offset K ₀ will be described.

As described above, in the subcarrier spacing setting μ, slots are counted from 0 to N ^ {subframe, μ} _ {slot} -1 in the subframe in ascending order, and from 0 to N ^ {frame, in the frame. It is counted in ascending order to μ} _ {slot} -1. K ₀ is the number of slots based on the PDSCH subcarrier spacing. K ₀ can take a value from 0 to 32. FIG. 15 is a diagram showing an example in which DCI schedules PDSCH. The slot length differs depending on the subcarrier interval setting μ. FIG. 15A is a slot number corresponding to the subcarrier interval of 30 kHz (μ = 1). FIG. 15B is a slot number corresponding to the subcarrier interval of 15 kHz (μ = 0). In a subframe or frame, slot numbers are counted from 0 in ascending order. 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 containing DCI is 15 kHz (μ _PDCCH =
0). The subcarrier interval for PDSCH scheduled by the DCI is 15
It is kHz (μ _PDSCH = 0). The terminal device 1 includes a PDC including DCI in slot n.
CH (701) is detected. If K ₀ is 0, the slot assigned to the PDSCH scheduled by its 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 spacing of 15 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by its DCI (701) is given as slot n + 1 based on (Equation 1). In this case, the PDSCH scheduled by the DCI (701) is the PDSCH (703) in slot n + 1 corresponding to the subcarrier spacing of 15 kHz.

Further, for example, the subcarrier interval with respect to PDCCH including DCI is 15 kHz (μ _PDCCH = 0). The subcarrier interval for the PDSCH scheduled by the DCI is 30 kHz (μ _PDSCH = 1). The terminal device 1 detects the PDCCH (701) including DCI in slot n. If K ₀ is 0, the slot assigned to the PDSCH scheduled by its 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 slot 2n corresponding to the subcarrier spacing of 30 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by its 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 spacing of 30 kHz.

Further, for example, the subcarrier interval with respect to 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 its 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 spacing of 15 kHz. If K ₀ is 1, the slot assigned to the PDSCH scheduled by its DCI (704) is given as slot n + 1 based on (Equation 1). In this case, the PDSCH scheduled by the DCI (704) is the PDSCH (703) in slot n + 1 corresponding to the subcarrier spacing of 15 kHz.

As described above, the terminal device 1 may determine which resource allocation table to apply to the PDSCH time domain resource allocation with reference to FIG. 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: Type of RNTI that scrambles the CRC added to DCI
Element B: Type of search space in which DCI is detected Element C: Whether the CORESET associated with the search space is CORESET # 0 Element D: Whether pdsch-ConfigCommon contains pdsch-TimeDomainAllocationList Element E: pdsch-Config Does include pdsch-TimeDomainAllocationList Element F: SS / PBCH and CORESET Multiple Pattern In element A, the types of RNTI that scramble the CRC added to DCI are SI-RNTI, RA-RNTI, TC-RNTI, P- It is either 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 Example A, terminal device 1 may detect DCI in any common search space associated with CORESET # 0. The detected DCI is added with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, and CS-RNTI. 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 terminal device 1, terminal device 1 may determine a resource allocation table set from an upper layer RRC signal. The resource allocation table is given by the pdsch-TimeDomainAllocationList contained in pdsch-ConfigCommon. Further, when pdsch-ConfigCommon does not include the 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 to the determination of the PDSCH time domain resource allocation by using the default table A showing the configuration of the PDSCH time domain resource allocation.

Further, as Example B, the terminal device 1 may detect DCI in any common search space that is not associated with CORESET # 0. The detected DCI is added with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, and CS-RNTI. 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 terminal device 1, terminal device 1 allocates the resource allocation table applied to PDSCH time domain resource allocation from the pdsch-TimeDomainAllocationList provided by pdsch-Config. You may decide on the table. That is, when the pdsch-Config includes the pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by the pdsch-Config regardless of whether the pdsch-ConfigCommon includes or does not include the pdsch-TimeDomainAllocationList. It may be applied to the determination of space resource allocation. Further, when pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table to be applied to PDSCH time domain resource allocation in pdsch-ConfigCommon. It may be determined by the resource allocation table given from the provided pdsch-TimeDomainAllocationList. That is, the terminal device 1 applies to the determination of PDSCH time domain resource allocation by using the pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. Further, when pdsch-Config does not include the pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include the pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table applied to the PDSCH time domain resource allocation to the default table A. You may decide.

Further, as Example C, the terminal device 1 may detect DCI in the UE-specific search space. The detected DCI is added with a CRC scrambled by any of C-RNTI, MCS-C-RNTI, and CS-RNTI. Then, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH scheduled by the DCI. Pdsch-Config is pdsch-TimeDomainAllocation for terminal device 1.
When the list is included, the terminal device 1 may determine the resource allocation table to be applied to the PDSCH time domain resource allocation to the resource allocation table given from the pdsch-TimeDomainAllocationList provided by pdsch-Config. That is, when the pdsch-Config includes the pdsch-TimeDomainAllocationList, the terminal device 1 uses the pdsch-TimeDomainAllocationList provided by the pdsch-Config regardless of whether the pdsch-ConfigCommon includes or does not include the pdsch-TimeDomainAllocationList. It may be applied to the determination of space resource allocation. Further, when pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon includes pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table to be applied to PDSCH time domain resource allocation in pdsch-ConfigCommon. It may be determined by the resource allocation table given from the provided pdsch-TimeDomainAllocationList. That is, the terminal device 1 applies to the determination of PDSCH time domain resource allocation by using the pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. Further, when pdsch-Config does not include the pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include the pdsch-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table applied to the PDSCH time domain resource allocation to the default table A. You may decide.

From the viewpoint of 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 the resource applied to the PDSCH detected in any common search space not associated with CORESET # 0. It is the same as the method of determining the allocation table.

The terminal device 1 may subsequently select one PDSCH time domain resource allocation configuration in the determined resource allocation table based on the value shown in the'Time domain resource allocation'field contained in the DCI that schedules its PDSCH. Good. For example, if the resource allocation table applied to PDSCH time domain resource allocation is the default table A, then'Time domain resource assignment'
The value m shown in the field is the row index m of the default table A.
It may indicate +1. At this time, the PDSCH time domain resource allocation is the configuration of the time domain resource allocation indicated by the row index m + 1. The terminal device 1 receives the PDSCH, assuming the time domain resource allocation configuration indicated by the row index m + 1. For example, if the value m shown in the'Time domain resource allocation'field is 0, terminal device 1 is scheduled by its DCI using the PDSCH time domain resource allocation configuration for row index 1 in default table A. Identify the time-domain resource allocation of the PDSCH.

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

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

The terminal device 1 may decode (receive) the corresponding PDSCH by detecting the PDCCH including the DCI format 1_1 or the DCI format 1-1.1. The number of bits in 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. Further, the size of the'Time domain resource assignment'field included in the DCI format 1-11 may be a variable number of bits. For example, the number of bits in the'Time domain resource assignment'field included in DCI format 1-11 may be any of 0, 1, 2, 3, and 4.

Hereinafter, the determination of the number of bits in the'Time domain resource assignment'field included in the DCI format 1-11 will be described.

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

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 the 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. If the 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 the pdsch-TimeDomainAllocationList is set for the terminal device 1, the number of bits in the Time domain resource assignment'field may be given based on the number of entries included in the pdsch-TimeDomainAllocationList. If the pdsch-TimeDomainAllocationList is not set for terminal device 1, the number of bits in the Time domain resource assignment'field may be given based on the number of rows in the default table (default table A). Specifically, if pdsch-Config contains a pdsch-TimeDomainAllocationList, the value of I may be the number of entries contained in the pdsch-TimeDomainAllocationList provided by pdsch-Config. If pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon contains pdsch-TimeDomainAllocationList, the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. You may. Also, if pdsch-Config does not include a pdsch-TimeDomainAllocationList and pdsch-ConfigCommon does not include a pdsch-TimeDomainAllocationList, the value of I is the number of rows contained in the default table (eg, default table A). You may.

In other words, when the pdsch-TimeDomainAllocationList is set (provided) for the terminal device 1, the number of bits in the'Time domain resource assignment'field is given as ceiling (log ₂ (I)). You may. If the pdsch-TimeDomainAllocationList is not set (provided) for the terminal device 1, the number of bits in 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, if pdsch-Config contains a pdsch-TimeDomainAllocationList, the value of I may be the number of entries contained in the pdsch-TimeDomainAllocationList provided by pdsch-Config. If pdsch-Config does not include pdsch-TimeDomainAllocationList and pdsch-ConfigCommon contains pdsch-TimeDomainAllocationList, the value of I is the number of entries included in pdsch-TimeDomainAllocationList provided by pdsch-ConfigCommon. You may.

As a result, the terminal device 1 can specify the number of bits in the'Time domain resource assignment'field generated by the base station device 3. That is, the terminal device 1 can correctly receive the PDSCH addressed to the terminal device 1 scheduled by the base station device 3.

The procedure for receiving the PUSCH will be described below.

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 (shown) be scheduled according to its DCI format (DCI). The PUSCH may also be scheduled by the RAR UL grant included in the RAR message. The scheduled start position (start symbol) of the PUSCH is referred to as S. The PUSCH start symbol S may be the first symbol to which the PUSCH is transmitted (mapped) in a slot. The start symbol S corresponds to the beginning 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 referred to as 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.

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

The position of the DMRS symbol for PUSCH depends on the type of PUSCH mapping. The position of the first DM-RS symbol for PUSCH depends on the type of PUSCH mapping. For 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.

Hereinafter, a method for specifying the PUSCH time domain resource allocation will be described.

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 its own device. When specifying 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 contains one or more PUSCH time domain resource allocation configurations. Terminal device 1 may then select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value shown in the'Time domain resource allocation'field contained in the DCI that schedules its PUSCH. Good. That is, the base station apparatus 3 determines the resource allocation of the PUSCH to the terminal apparatus 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 apparatus 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 to be applied to the PUSCH time domain resource allocation based on the table shown in FIG. The resource allocation table contains the configuration of one or more PUSCH time domain resource allocations. In the present embodiment, the resource allocation table is classified into (I) a predefined resource allocation table and (II) a resource allocation table set from an upper layer RRC signal. The pre-defined 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 a 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, the PUSCH default table A contains 16 rows. Each row in the PUSCH default table A shows the configuration of PUSCH time domain resource allocation. Specifically, in FIG. 17, indexed row (indexed row) is, PUSCH mapping type, slot offset _{K 2} between the PDCCH and its PUSCH containing DCI, start symbol S of the PUSCH in the slots and, Define the number of consecutively assigned symbols L.

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. The 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, the push-TimeDomainAllocationList is a list containing 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 DCI and its scheduled PUSCH. If PUSCH-TimeDomainResourceAllocation does not indicate K ₂ , terminal device 1 assumes that the value of K ₂ is 1 when the PUSCH subcarrier spacing is 15 kHz or 30 kHz, and the PUSCH subcarrier spacing is When the value is 60 kHz, it may be assumed that the value of K ₂ is 2, and when the subcarrier interval of PUSCH is 120 kHz, the value of K ₂ may be assumed to be 3. The mappingType indicates either PUSCH mapping type A or PUSCH mapping type A. startSymbolAndLength is an index that gives a valid combination of the PUSCH start symbol S 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, which 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 apparatus 3 can set the value of SLIV so that the time domain resource allocation of PUSCH does not exceed the slot boundary. The value of SLIV is calculated based on the number of symbols contained in the slot, the starting symbol S, and the number of consecutive symbols L, as in the equation 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 cell-specific parameters for PUSCH for a BWP. The information element push-Config is used to set UE-specific parameters for PUSCH for a BWP.

The terminal device 1 detects the DCI that schedules the PUSCH. The slot to 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 any of j, j + 1, j + 2, or j + 3. The value of j is a value specified with respect to the PUSCH subcarrier interval. For example, when the subcarrier interval to which PUSCH is applied is 15 kHz or 30 kHz, the value of j may be one slot. For example, when the subcarrier interval to which PUSCH is applied is 60 kHz, the value of j may be 2 slots. For example, when the subcarrier interval 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 the PUSCH time domain resource allocation based on the table shown in FIG.

As Example D, terminal device 1 may determine a resource allocation table to apply to PUSCH scheduled by RAR UL grant (MAC RAR). When the push-ConfigCommon includes the 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 the push-TimeDomainAllocationList contained in push-ConfigCommon. Further, when the push-ConfigCommon does not include the 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 apply to the determination of the PUSCH time domain resource allocation by using the default table A showing the configuration of the PUSCH time domain resource allocation.

As Example E, the terminal device 1 may detect a DCI (eg, DCI format 0_0) to which a CRC scrambled by TC-RNTI is added in a common search space (eg, 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 the time of the PUSCH is based on the (m + 1) th element (entry, row) in the determined resource allocation table. Space resource allocation may be determined. That is, when the terminal device 1 determines the resource allocation table applied to the PUSCH time domain resource allocation scheduled by DCI, when CRC scrambled by TC-RNTI is added to the DCI, push- Regardless of whether 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 mentioned above, the value of m may be indicated in the'Time domain location assignment' field contained in the DCI. Whether or not the push-TimeDomainAllocationList included in pusch-Config is received (set) may mean whether the push-TimeDomainAllocationList is included or not included in push-Config. The fact that the push-TimeDomainAllocationList included in pusch-Config is not received may mean that the push-Config is not received. Not receiving the pusch-TimeDomainAllocationList contained in pusch-Config may mean that the pusch-Config was received, but the pusch-Config does not contain the pusch-TimeDomainAllocationList. Receiving the pusch-TimeDomainAllocationList contained in pusch-Config may mean that the pusch-Config is received and the received pusch-Config contains the pusch-TimeDomainAllocationList.

Specifically, when push-ConfigCommon includes push-TimeDomainAllocationList for terminal device 1, terminal device 1 provides a resource allocation table to be applied to PUSCH time domain resource allocation in push-ConfigCommon. It may be determined by the resource allocation table given from TimeDomainAllocationList. When the push-ConfigCommon does not include the push-TimeDomainAllocationList for the terminal device 1, the terminal device 1 may determine the resource allocation table to be applied to the PUSCH time domain resource allocation in 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 the push-TimeDomainAllocationList included in pusch-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 Example F, the terminal device 1 may detect DCI in any common search space associated with CORESET # 0. The detected DCI is added with a CRC scrambled by the first RNTI. In the present invention, the first RNTI may be any of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or 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 any common search space associated with CORESET # 0, it is included in (I) push-ConfigCommon regardless of whether or not the push-TimeDomainAllocationList included in push-Config is received (set). One may be selected from the 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 terminal device 1, terminal device 1 provides a resource allocation table to be applied to PUSCH time domain resource allocation in push-ConfigCommon. It may be determined by the resource allocation table given from TimeDomainAllocationList. Further, when push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 may determine the resource allocation table applied to the PUSCH time domain resource allocation as the PUSCH default table A.

Further, as Example G, the terminal device 1 may detect DCI in (i) an arbitrary common search space not associated with CORESET # 0, or (ii) a UE-specific search space. The detected DCI is added with a CRC scrambled by the first RNTI. In the present invention, the first RNTI may be any of C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or 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 that is not associated with CORESET # 0 or (ii) a UE-specific search space, (I) push-TimeDomainAllocationList, which is 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 terminal device 1, terminal device 1 provides a resource allocation table to be applied to PUSCH time domain resource allocation in push-Config. It may be determined by the resource allocation table given from TimeDomainAllocationList. That is, when push-Config includes push-TimeDomainAllocationList, the terminal device 1 uses the push-TimeDomainAllocationList provided by push-Config regardless of whether push-ConfigCommon includes or does not include push-TimeDomainAllocationList. It may be applied to the determination of space resource allocation. Further, when push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon includes push-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table to be applied to PUSCH time domain resource allocation in push-ConfigCommon. It may be determined by the resource allocation table given from the provided push-TimeDomainAllocationList. That is, the terminal device 1 applies to the determination of PUSCH time domain resource allocation by using the push-TimeDomainAllocationList provided by push-ConfigCommon. Further, when push-Config does not include push-TimeDomainAllocationList and push-ConfigCommon does not include push-TimeDomainAllocationList, the terminal device 1 sets the resource allocation table to be applied to PUSCH time domain resource allocation to PUSCH default table A. May be decided.

The terminal device 1 may subsequently select one PUSCH time domain resource allocation configuration in the determined resource allocation table based on the value shown in the'Time domain resource allocation'field contained in the DCI that schedules its PUSCH. Good. For example, if the resource allocation table applied to the PUSCH time domain resource allocation is the PUSCH default table A, the value m shown in the'Time domain resource assignment'field indicates the row index m + 1 of the default table A. May be good. At this time, the PUSCH time domain resource allocation is the configuration of the time domain resource allocation indicated by the row index m + 1. The terminal device 1 transmits the PUSCH assuming the configuration of the time domain resource allocation indicated by the row index m + 1. For example, if the value m shown in the'Time domain resource allocation'field is 0, terminal device 1 schedules by its DCI using the PUSCH time domain resource allocation configuration for row index 1 in the PUSCH default table A. Identify the time-domain resource allocation of the PUSCH to be done.

Further, when the resource allocation table applied to the PUSCH time domain resource allocation is the resource allocation table given from the push-TimeDomainAllocationList, the value m shown in the'Time domain resource allocation'field is the (m + 1) th in the list push-TimeDomainAllocationList. Corresponds to the element (entry, row) of.
For example, if 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, if 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 push-TimeDomainAllocationList.

As a result, the terminal device 1 can determine the time domain resource allocation of the PUSCH scheduled by the DCI based on the parameters of the upper layer 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.

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

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

Hereinafter, the determination of the number of bits of the'Time domain resource assignment'field included in the DCI format 0-1 will be described.

The number of bits in the'Time domain resource assignment'field contained in DCI format 0-1 is: (I) whether push-ConfigCommon contains a pussy-TimeDomainAllocationList and / or (II) whether push-Config contains a push-TimeDomainAllocationList. Please and / or (III) may be given based on at least the number of rows contained in the predefined default table. In the present embodiment, the DCI format 0-1 is added with a CRC scrambled by any 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 a push-TimeDomainAllocationList' may mean that'pusch-Config provides a push-TimeDomainAllocationList'. The meaning of'pusch-ConfigCommon contains push-TimeDomainAllocationList' may mean'pusch-ConfigCommon provides push-TimeDomainAllocationList'.

The number of bits in the'Time domain resource assignment'field may be given as ceiling (log ₂ (I)). When a push-TimeDomainAllocationList is set (provided) for the terminal device 1, the value of I may be the number of entries included in the push-TimeDomainAllocationList. If the push-TimeDomainAllocationList is not set (provided) for the terminal device 1, the value of I may be the number of rows in the PUSCH default table A. That is, when the push-TimeDomainAllocationList is set for the terminal device 1, the number of bits in the Time domain resource assignment'field may be given based on the number of entries included in the push-TimeDomainAllocationList. If the push-TimeDomainAllocationList is not set for terminal device 1, the number of bits in the Time domain resource assignment'field may be given based on the number of rows in the default table (default table A). Specifically, if push-Config includes a push-TimeDomainAllocationList, the value of I may be the number of entries contained in the push-TimeDomainAllocationList provided by push-Config. Also, if push-Config does not include a push-TimeDomainAllocationList and push-ConfigCommon contains a pussy-TimeDomainAllocationList, the value of I is the number of entries contained in the push-TimeDomainAllocationList provided by push-ConfigCommon. You may. Further, when push-Config does not include the push-TimeDomainAllocationList and the push-ConfigCommon does not include the push-TimeDomainAllocationList, the value of I may be the number of rows included in the PUSCH default table A.

In other words, when the push-TimeDomainAllocationList is set (provided) for the terminal device 1, the number of bits in the'Time domain resource assignment'field is given as ceiling (log ₂ (I)). You may. If the push-TimeDomainAllocationList is not set (provided) for the terminal device 1, the number of bits in 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, if push-Config includes a push-TimeDomainAllocationList, the value of I may be the number of entries contained in the push-TimeDomainAllocationList provided by push-Config. Also, if push-Config does not include a push-TimeDomainAllocationList and push-ConfigCommon contains a pussy-TimeDomainAllocationList, the value of I is the number of entries contained in the push-TimeDomainAllocationList provided by push-ConfigCommon. You may.

As a result, the terminal device 1 can specify the number of bits in the'Time domain resource assignment'field generated by the base station device 3. That is, the terminal device 1 can correctly transmit the PUSCH addressed to the terminal device 1 scheduled by the base station device 3.

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

Conflict-based random access procedures are initiated by PDCCH orders, MAC entities, beam failure notifications from lower layers, RRC, and the like. 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, the procedure of determining whether a certain condition is satisfied and starting the random access procedure is called a beam failure recovery procedure. You may. This random access procedure is a random access procedure for a beam failure recovery request. Random access procedures initiated by the MAC entity include random access procedures initiated by the scheduling request procedure. The random access procedure for a beam failure recovery request may or may not be considered a random access procedure initiated by the MAC entity. Distinguish between the random access procedure for a beam failure recovery request and the scheduling request procedure because the random access procedure for a beam failure recovery request and the random access procedure initiated by the scheduling request procedure may perform different procedures. You may do so. The random access procedure and scheduling request procedure for the beam failure recovery request may be a random access procedure initiated by the MAC entity. In one embodiment, the random access procedure initiated by the scheduling request procedure is referred to as the random access procedure initiated by the MAC entity, and the random access procedure for the beam failure recovery request is random access by notification of beam failure from a lower layer. It may be referred to as a procedure. Hereinafter, the start of the random access procedure when the notification of the beam failure from the lower layer is received may mean the start of the random access procedure for the beam failure recovery request.

The terminal device 1 is initially accessed from a state in which it is not connected (communicated) with the base station device 3, and / or uplink data or transmission that is connected to the base station device 3 but can be transmitted to the terminal device 1. Perform a conflict-based random access procedure at the time of scheduling request when possible side link data occurs. However, the use of contention-based random access is not limited to these.

The occurrence of transmittable uplink data to the terminal device 1 may include triggering a buffer status report corresponding to the transmittable uplink data. The occurrence of transmittable uplink data in the terminal device 1 may include pending scheduling requests triggered based on the generation of transmittable uplink data.

The occurrence of transmittable side link data to the terminal device 1 may include triggering a buffer status report corresponding to the transmittable side link data. The occurrence of transmittable side link data to the terminal device 1 may include that a scheduling request triggered based on the generation of transmittable side link data is pending.

The non-competitive-based random access procedure may be initiated when the terminal device 1 receives information from the base station apparatus 3 instructing the start of the random access procedure. The non-competitive-based random access procedure may be initiated when the MAC layer of the terminal device 1 is notified of a beam failure by a lower layer.

Non-competitive-based random access is to quickly perform 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. It may be used to synchronize the uplink of. Non-competitive based random access may be used to send a beam failure recovery request in the event of a beam failure in terminal device 1. However, the use of non-competitive random access is not limited to these.

However, the information instructing the start of the random access procedure is message 0, Msg. It may be referred to as 0, NR-PDCCH order, PDCCH order, or the like.

However, the terminal device 1 has a preamble that can be used by the terminal device 1 when the random access preamble index specified by the message 0 is a predetermined value (for example, when all the bits indicating the index are 0). A conflict-based random access procedure may be performed in which one is randomly selected from the set and transmitted.

However, the random access setting information may include common information in the cell, or may include dedicated information that differs for each terminal device 1.

However, a part of the random access setting information may be associated with all SS / PBCH blocks in the SS burst set. However, some 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, a part of the random access setting information may be associated with one SS / PBCH block in the SS burst set. However, some 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 includes one corresponding SS / PBCH block, one CSI-RS, and / or Index information for identifying one downlink transmit beam (eg, may be an SSB index, a beam index, or a QCL set index) may be included.

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

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

In the case of a conflict-based random access procedure, the terminal device 1 itself randomly selects the index of the random access preamble. In the competition-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 is randomly selected from one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group. Select ra-PreambleIndex and set the selected ra-PreambleIndex to the preamble index (PREABLE_INDEX). Also, 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. The terminal device 1 randomly selects a preamble index from the subgroup corresponding to the transmission size of the small message 3 when the transmission size of the message 3 is small, and sets the transmission size of the large message 3 when the transmission size of the message 3 is large. A 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 selected when the characteristics of the above are good (or the distance between the terminal device 1 and the base station device 3 is short).

In the non-competitive based random access procedure, the terminal device 1 selects a random access preamble index 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 all the bit values of the information received from the base station apparatus 3 are 0, the terminal apparatus 1 executes the conflict-based random access procedure, and the terminal apparatus 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. , A random access response including the generated RAR message is transmitted to the terminal device 1 by DL-SCH. That is, the base station apparatus 3 transmits a random access response including a RAR message corresponding to the random access preamble transmitted in S801 by PDSCH in the primary cell (or primary secondary cell). The PDSCH corresponds to a 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 the index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is the index of the first slot of PRACH in the system frame and takes a value from 0 to 79. f_id is an index of PRACH in the frequency domain and takes a value 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. Further, the base station apparatus 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 deviation between the terminal device 1 and the base station device 3 from the received random access preamble, and transmits timing adjustment information (TA command, Timing Advance Command) for adjusting the deviation. ) Is included in the RAR message. The RAR message is 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 at least includes TA command (Timing Advance Command). 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. Further, the base station apparatus 3 includes the random access preamble identifier corresponding to the received random access preamble in the message 2.

To respond to PRACH transmission, terminal device 1 detects DCI format 1_0 in the SpCell (PCell or PSCell) with the CRC parity bit scrambled by the corresponding RA-RNTI during the period of 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.

If the terminal device 1 detects a PDSCH containing a CRC-added DCI format 1_0 and one DL-SCH transport block scrambled by RA-RNTI within the window period, the terminal device 1 detects the transport block. Pass it to the upper layer. The upper layer parses its transport block for the random access preamble identifier (RAPID) associated with the PRACH transmission. The upper layer is the DL
-When identifying the RAPID contained in the RAR message of the SCH transport block, the upper layer indicates an 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 referred to as 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 its own device from the base station device 3 by monitoring the random access response (message 2) corresponding to the random access preamble identifier.

(I) If terminal device 1 does not detect CRC-added DCI format 1_0 scrambled by RA-RNTI within the window period, or (ii) terminal device 1 does not detect DL- in PDSCH during 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 terminal The device 1 considers that the non-conflict-based random access procedure has been completed successfully, and transmits the PUSCH based on the uplink grant included in the random access response.

The received random access response includes a random access preamble identifier corresponding to the transmitted random access preamble, and when the random access preamble is selected by the terminal device 1 itself, the TC-RNTI is included in the received random access response. The random access message 3 is transmitted by PUSCH based on the uplink grant included in the random access response by setting the value of the TC-RNTI field. 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 in PRACH.

RAR UL grant (RAR uplink grant) is a PUSCH transmission (or RAR PU
Used for SCH) scheduling. The PUSCH (or PUSCH transmission) scheduled by the RAR UL grant may also be referred to as the RAR PUSCH (or RAR PUSCH transmission). That is, the RAR PUSCH transmission is a PUSCH transmission corresponding to the 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 competition-based random access procedure, the terminal device 1 transmits Msg3 (message 3) based on the RAR UL grant. That is, in a conflict-based random access procedure, Msg3 PUSCH (Msg3 PUSCH transmission) is scheduled by the RAR UL grant. Msg3 may be the first scheduled transmission of the conflict-based random access procedure. Msg3 is a message containing a C-RNTI MAC CE or CCCH SDU as part of a conflict-based random access procedure and may be transmitted by UL-SCH. In the conflict-based random access procedure, the RAR PUSCH transmission may be an Msg3 PUSCH transmission. In the non-competitive base random access procedure, the terminal device 1 may transmit PUSCH (RAR PUSCH) based on the RAR UL grant. That is, in a non-competitive based random access procedure, the PUSCH scheduled by the RAR UL grant does not have to be referred to as Msg3 PUSCH. Also, in a non-competitive based random access procedure, the PUSCH scheduled by the RAR UL grant may also be referred to as the Non-Msg3 PUSCH. That is, in a non-competitive based random access procedure, the Non-Msg3 PUSCH may be a PUSCH scheduled by a RAR UL grant.

Also, in this embodiment, the Msg3 PUSCH may include a PUSCH scheduled by a RAR UL grant in a competitive-based random access procedure. The Msg3 PUSCH may also include a PUSCH scheduled by a RAR UL grant in a non-competitive based random access procedure. That is, the Msg3 PUSCH may be a PUSCH scheduled by a RAR UL grant, regardless of the type of random access procedure (competitive-based random access procedure or non-competitive-based random access procedure).

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

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

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

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

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

In the competition-based random access procedure, the'CSI request'field is reserved. In the non-competitive-based random access procedure, the'CSI request'field is used to determine if the apiriodic CSI report is included in the PUSCH transmission.

<Message 3 (S803)>
The terminal device 1 performs the 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 RAR UL Grant in the same uplink carrier in the same serving cell. PUSCHs scheduled by RAR UL Grant are transmitted at the active UL BWP. The subcarrier interval for PUSCH scheduled by RAR UL Grant is UL
It may be indicated by the parameter SubcarrierSpacing of the upper layer set for BWP or the parameter SubcarrierSpacing2 of the upper layer. 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 a DCI that schedules a PDSCH containing a RAR message. The RAR message contains a RAR UL grant. The terminal device 1 transmits a PUSCH scheduled by the RAR UL grant in the RAR message. The slot number assigned to the PUSCH may be given by (Equation 2) Floor (n * 2 ^μPUSCH / 2 ^μPDSCH ) + K ₂ + Δ. n is a slot in which a PDSCH containing a RAR message is detected. Slot n is the number of the slot corresponding to the subcarrier interval of the PDSCH. μ _PDSCH is a subcarrier interval setting for _PDSCH . μ _PUSCH is a subcarrier spacing setting for PUSCH scheduled by the RAR UL grant. That is, when the terminal device 1 receives the PDSCH containing 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 ₂ + Δ. You may. The value of K ₂ may be indicated by the'PUSCH time resource allocation' field contained in the RAR UL grant. Δ is an additional subcarrier interval 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 interval to which the PUSCH scheduled by the RAR UL grant is applied is 15 kHz, the value of Δ may be 2 slots. When the subcarrier interval is 30 kHz, the value of Δ may be 3 slots. When the subcarrier interval 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 into 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 contained in that PDSCH. The second subcarrier interval for the PUSCH scheduled by Grant, (iii) the number of slots in which the PDSCH containing the RAR message is received, (iv) the number of predefined slots corresponding to the second subcarrier interval. delta, it may be given based on the value _{K 2} of the slot offset provided from (IIV) RAR UL grant.

FIG. 18 is a diagram showing an example of transmitting a PUSCH scheduled by a RAR UL grant. The slot length differs depending on the subcarrier interval setting μ. FIG. 18A is a slot number corresponding to the subcarrier interval of 30 kHz (μ = 1). FIG. 18B is a slot number corresponding to the subcarrier interval of 15 kHz (μ = 0). In a subframe or frame, the slot numbers corresponding to each of the subcarrier intervals are counted from 0 in ascending order. 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 detect the DCI (900) and receive a PDSCH containing a RAR message scheduled by the detected DCI. 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) containing a RAR message is 15 kHz (μ _PDSCH = 0). The subcarrier interval for the PUSCH scheduled by the RAR UL grant contained in the PDSCH (901) is 15 kHz (μ _PUSCH = 0). The value of Δ corresponding to the subcarrier interval of 15 kHz is 2. K ₂
When is 0, the slot to 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, which corresponds to a subcarrier spacing of 15 kHz. K ₂ is 1
If, the slot into 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, which corresponds to a subcarrier spacing of 15 kHz.

Further, for example, the subcarrier interval with respect to the PDSCH (901) including the RAR message is 15 kHz (μ _PDSCH = 0). RAR included in the PDSCH (901)
The subcarrier interval for PUSCH scheduled by UL Grant is 30 kHz (μ _PUSCH = 1). The value of Δ corresponding to the subcarrier interval of 30 kHz is 3. When K ₂ is 0, the slot to 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 spacing of 30 kHz. When K ₂ is 1, the slot to 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, which corresponds to a subcarrier spacing of 30 kHz.

Further, for example, the subcarrier interval with respect to the PDSCH (904) including the RAR message is 30 kHz (μ _PDSCH = 1). RAR included in the PDSCH (904)
Subcarrier interval 30k for PUSCH scheduled by UL Grant
It is Hz (μ _PUSCH = 1). The value of Δ corresponding to the subcarrier interval of 30 kHz is 3. When K ₂ is 0, the slot to 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 spacing of 30 kHz. When K ₂ is 1, the slot to which the PUSCH scheduled by the RAR UL grant contained 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, which corresponds to a subcarrier spacing of 30 kHz.

Further, for example, the subcarrier interval with respect to the PDSCH (904) including the RAR message is 30 kHz (μ _PDSCH = 1). RAR included in the PDSCH (904)
The subcarrier interval for PUSCH scheduled by UL Grant is 15 kHz (μ _PUSCH = 0). The value of Δ corresponding to the subcarrier interval of 15 kHz is 2. When K ₂ is 0, the slot through which the PUSCH scheduled by the RAR UL grant contained 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, which corresponds to a subcarrier spacing of 15 kHz. When K ₂ is 1, the slot to which the PUSCH scheduled by the RAR UL grant contained 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, which corresponds to a subcarrier spacing of 15 kHz.

<Retransmission of message 3 (S803a)>
The retransmission of message 3 is scheduled in DCI format 0_0 with the 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 in DCI format 0_0 with the CRC parity bit scrambled by TC-RNTI added. The DCI format 0_0 is transmitted in 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 the message 3 is transmitted 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 to which the CRC parity bit scrambled by TC-RNTI is added is detected in S803a, the terminal device 1 retransmits the PUSCH of the transport block transmitted in S803.

<Message 4 (S804)>
In order to respond to the PUSCH transmission of message 3 (Msg3) (PUSCH scheduled by the RAR UL grant), the terminal device 1 in which C-RNTI is not shown schedules a PDSCH containing the UE contention resolution identity. Monitor DCI format 1_0. Here, the DCI format 1_0 is added with a CRC parity bit scrambled by the corresponding TC-RNTI. In order to respond to the PDSCH reception with the UE collision resolution identity, the terminal device 1 transmits 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.

As a result, the terminal device 1 that performs the random access procedure can transmit uplink data to the base station device 3.

FIG. 19 is a flow chart showing an example of a random access procedure of the MAC entity according to the present embodiment.

<Start of random access procedure (S1001)>
In FIG. 19, S1001 is a procedure relating to the initiation of a random access procedure (random access procedure initialization). In S1001, the random access procedure is initiated by the PDCCH order, the MAC entity itself, notification of beam failure from a lower layer, RRC, or the like. Random access procedures in SCell are initiated only by PDCCH orders containing ra-PreambleIndex that are not set to 0b000000.

In S1001, the terminal device 1 receives the random access setting information via the upper layer before initiating the random access procedure. The random access setting information may include one or more elements of the following information or information for determining / setting the following information.
Dust-ConfigIndex: A set of one or more time / frequency resources (also known as random access channel opportunities, PRACH occasions, RACH opportunities) that can be used to transmit a random access preamble. ・ PremiumReceivedTragetPower : Initial power of preamble (may be target received power)
Rsrp-Throshold SSB: Threshold for reference signal received power (RSRP) for selection of SS / PBCH blocks (which may be associated random access preambles and / or PRACH opportunities) • rsrp-Throshold CSI-RS: CSI-RS Reference signal received power (RSRP) threshold for selection (which may be a related 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 carriers-powerControlOffset: with rsrp-Throshold SSB and rsrp-Throshold CSI-RS when a random access procedure is initiated for beam failure recovery. Power offset between powerRampingStep: Power ramping step (power ramping factor). Shows the steps of transmit power ramped up based on the preamble transmission counter PREAMBLE_TRANSMISSION_COUNTER-ra-PreambleIndex: One or more random access preambles available or one or more available in said multiple random access preamble groups Random Access Preamble · ra-ssb-OccasionMaskIndex: Information for determining the PRACH opportunity assigned to the SS / PBCH block where the MAC entity sends a random access preamble · ra-OccasionList: MAC entity sends a random access preamble Information for determining the PRACH opportunity assigned to the CSI-RS. ・ PremiumTransMax: Maximum number of preamble transmissions. Parameters indicating the number and the number of random access preambles mapped to each SS / PBCH block ・ ra-ResponseWindow: Time window to monitor random access response (SpCell only) ・ ra-ContentionResolutionTimer: Collision resolution: Contention Resolution) Timer · numberOfRA-PreamblesGroupA: Number of random access preambles in random access preamble group A for each SS / PBCH block · PREAMBLE_TRANSMISSION_COUNTER: Preamble transmission counter · DELTA_PREAMBLE: Random access preamble_ Preamble power ramping counter ・ PREAMPLE_RECIVED_TARGET_POWER: Initial random access preamble power. Shows the initial transmission power for random access preamble transmission.
-PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.

When a random access procedure is initiated in a serving cell, the MAC entity freshs the Msg3 buffer, sets the state variable PREAMPLE_TRANSMISSION_COUNTER to 1, sets the state variable PREAMPLE_POWER_RAMPING_COUNTER to 1, and sets the state variable PREAMPLE_BACKOFF to 0 ms. If the carrier used for the random access procedure is explicitly notified, the MAC entity selects the carrier notified to perform the random access procedure and sets the state variable PCMAX to the maximum transmit power value of the notified carrier. set. 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-ThresholdSSB-SUL. Select the SUL carrier to perform the random access procedure, and set the state variable PCMAX 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 (which may be referred to as PREAMPLE_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) notifying the beam failure from the lower layer, and (2) using the RRC parameter to the SS / PBCH block (also called SSB) or CSI-RS. Random access resources (which may be PRACH opportunities) for non-conflict-based random access for associated beam failure recovery requests are provided and (3) one or more SS / PBCH blocks or CSIs. When the RSRP of -RS exceeds a predetermined threshold, the SS / PBCH block or CSI-RS in which the RSRP exceeds the predetermined threshold is selected. If the CSI-RS is selected and there is no ra-PreambleIndex associated with the selected CSI-RS, the MAC entity preambles the ra-PreambleIndex associated with the selected SS / PBCH block (PREAMBLE_INDEX). ) May be set. Otherwise, the MAC entity sets the ra-PreambleIndex associated with the selected SS / PBCH block or CSI-RS in the preamble index.

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 (for example, 0b000000) indicating a competition-based random access procedure, and (3) RRC. Sets the signaled ra-PreambleIndex to the preamble index when the SS / PBCH block or CSI-RS is not associated with a random access resource for non-competitive based random access. 0bxxxxxx means a bit string arranged in a 6-bit information field.

In the terminal device 1, (1) a random access resource for non-competitive-based random access associated with the SS / PBCH block is provided by RRC, and (2) RSRP is specified among the associated SS / PBCH blocks. When one or more SS / PBCH blocks exceeding the threshold value of are available, RSRP selects one of the SS / PBCH blocks exceeding the predetermined threshold value, and the selected SS / PBCH block is used. Set the associated ra-PreambleIndex to the preamble index.

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

If none of the above conditions is met, the terminal device 1 performs a conflict-based random access procedure. In the competition-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 is randomly selected from one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group. Select ra-PreambleIndex to set the selected ra-PreambleIndex to the preamble index.

If the MAC entity selects one SS / PBCH block and the association between the PRACH opportunity and the SS / PBCH block is set, the next of the PRACH opportunities associated with the selected SS / PBCH block The available PRACH opportunities may be determined. However, when one CSI-RS is selected and the association between the PRACH opportunity and the CSI-RS is set, the terminal device 1 is next among the PRACH opportunities associated with the selected CSI-RS. The PRACH opportunities available for may be determined.

Available PRACH opportunities are mask index information, SSB index information, R
It may be specified based on the resource settings set by the RC parameters and / or the selected reference signal (SS / PBCH block or CSI-RS). The resource settings set by the RRC parameters include resource settings for each SS / PBCH block and / or resource settings for each CSI-RS.

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

The mask index information is information indicating an index of PRACH opportunities that can be used to transmit a random access preamble. The mask index information may be information indicating a part of PRACH opportunities in a group of one or more PRACH opportunities defined by the dust-Configuration Index. Further, the mask index information may be information indicating a part of the 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 any one of one or a plurality of SS / PBCH blocks transmitted by the base station apparatus 3. Upon receiving the message 0, the terminal device 1 identifies a 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 setting index, the upper layer parameter SB-perRACH-Occation, and the upper layer parameter cb-preamblePerSSB.

<Random access preamble transmission (S1003)>
S1003 is a procedure relating to random access preamble transmission. For each random access preamble, the MAC entity has (1) the state variable PREAMPLE_TRANSMISSION_COUNTER is greater than 1, and (2) has not received notification of the stopped power ramp counter from the upper layer, and (3) has selected When the SS / PBCH block that has been set is not changed, the state variable PREAMPLE_POWER_RAMPING_COUNTER is incremented by one.

The MAC entity then 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 playableReceivedTargetPower + DELTA_PREAMBLE + (PREABLE_POWER_RAMPING_COUNTER-1) * powerRampingStep.

The MAC entity then calculates the RA-RNTI associated with the PRACH opportunity at which the random access preamble is transmitted, except for non-conflict-based random access preambles due to beam failure recovery requests. 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 the index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is the index of the first slot of PRACH in the system frame and takes a value from 0 to 79. f_id is an index of PRACH in the frequency domain and takes a value 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 send a random access preamble using the selected PRACH.

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

MAC PDUs (random access response MAC PDUs) consist of one or more MAC sub PDUs and possible padding. Each MAC subPDU is composed of any of the following.
-MAC subheader containing only the Backoff Indicator
-MAC subheader indicating only RAPID
-MAC subheader indicating RAPID and MAC RAR (MAC payload for Random Access Response)
A MAC sub PDU containing only the Backoff Indicator is placed at the beginning of the MAC PDU. The padding is placed at the end of the MAC PDU. A MAC subPDU containing only RAPID and a MAC subPDU containing only RAPID and MAC RAR can be placed anywhere between the MAC subPDU containing only the Backoff Indicator and padding.

MAC RAR is a fixed size, reserved bits to be set to 0, transmission timing adjustment information (TA command, Timing Advance Command), UL grant (UL)
It is composed of grant, RAR UL grant), and TEMPORARY_C-RNTI. Hereinafter, the RAR message may be MAC RAR. The RAR message may be a random access response.

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

The MAC entity is (1) received notification of PDCCH transmission from the lower layer, (2) the PDCCH transmission is scrambled by C-RNTI, and (3) the MAC entity is non-competitive based on a beam failure recovery request. If you send a random access preamble, you may consider the random access procedure to be completed successfully.

The MAC entity then performs the following actions when (1) the downlink assignment is received on the RA-RNTI PDCCH and (2) the received transport block is successfully decoded.

The MAC entity sets PREAMPLE_BACKOFF to the value of the BI field contained in the MAC subPDU when the random access response contains a MAC subPDU containing the BackoffIndicator. Otherwise, the MAC entity sets PREAMBLE_BACKOFF to 0ms.

A MAC entity may consider a successful reception of a random access response if it contains a MAC subPDU containing a random access preamble identifier corresponding to the PREAMPLE_INDEX to which the random access response was sent.

If (1) the random access response is considered successful and (2) the random access response contains a MAC subPDU containing only RAPID, the MAC entity considers the random access procedure to be successfully completed, and , The reception of the acknowledgement to the SI request (symstem information request) is shown to the upper layer. Here, if the condition (2) is not satisfied, the MAC entity applies the following operation A to the serving cell to which the random access preamble is transmitted.
<Start of operation A>
The MAC entity processes the received timing advance command and indicates to the lower layer the amount of preambleReceivedTargetPower and 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 a SCell for SRS only, the MAC entity may ignore the received UL grant. Otherwise, the MAC entity processes the received UL grant value and shows it to the lower layer.

If the random access preamble is not selected by the MAC entity from the range of conflict-based random access preambles, the MAC entity may consider the random access procedure to be successfully completed.
<End of operation A>
If the random access preamble is selected by the MAC entity from within the range of conflict-based random access preambles, the MAC entity sets the value of the Temporary C-RNTI field contained in the random access response that received TEMPORARY_C-RNTI. Subsequently, if the random access response is successfully received for the first time in this random access procedure, the MAC entity, if not transmitted to the CCCH logical channel (common control channel logical channel), Notify the predetermined entity (Multiplexing and assembly entity) that the next uplink transmission includes the C-RNTI MAC CE, and acquire and acquire the MAC PDU for transmission from the predetermined entity (Multiplexing and assembly entity). The generated MAC PDU is stored in the Msg3 buffer. When transmission is performed to 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 presents 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 by SpCell. Then, if the random access procedure is initiated for an SI request, the MAC entity considers the random access procedure to be incompletely completed.

The MAC entity states 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 by SCell. I reckon.

The condition (3) is that the period of the random access response window set by RACH-ConfigCommon has expired (3), 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. Condition (4) is that the period of the random access response window set by the BeamFairureRecoveryConfig has expired.
Moreover, the PDCCH scrambled by C-RNTI has not been received.

If the random access procedure has not been completed, the MAC entity will be random between 0 and PREAMBLE_BACKOFF if the random access preamble was selected by the MAC itself from within the range of conflict-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 has not been completed, the MAC entity executes S1002 if the random access preamble has not been selected by the MAC itself from the range of conflict-based random access preambles in the random access procedure.

The MAC entity may stop the random access response window after successfully receiving 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.

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

Receive notification of PDCCH transmission from lower layer and C-RNTI MAC
When CE is included in Msg3, the MAC entity considers that conflict resolution is successful if at least one of the following conditions (5) to (7) is met, stops the collision resolution timer, and TEMPORARY_C-RNTI. Is discarded and the random access procedure is considered to have been completed successfully.

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 C-RNTI, and the PDCCH transmission includes an uplink grant for the initial transmission. .. Condition (6) is that the random access procedure is initiated by the PDCCH order and the PDCCH transmission is scrambled by C-RNTI. Condition (7) is that the random access procedure is initiated for beam failure recovery and the PDCCH transmission is scrambled by C-RNTI.

CCCH SDU (UE contention resolution Identity) is included in Msg3, and
If 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. Subsequently, the successfully decoded MAC PDU contains the UE contention resolution identity MAC CE and is M.
If the UE collision resolution identity in the AC CE matches the CCCH SDU transmitted in Msg3, the MAC entity considers the collision resolution successful and terminates the disassembly and demultiplexing of the MAC PDU. Then, when the random access procedure is initiated for the SI request, the MAC entity indicates to the upper layer that it receives an acknowledgment for the SI request. If the random access procedure is not initiated due to an SI request, the MAC entity sets C-RNTI to the value of TEMPORARY_C-RNTI. The MAC entity then discards TEMPORARY_C-RNTI and considers the random access procedure to be completed successfully.

If the UE collision resolution identity in the MAC CE does not match the CCCH SDU sent by Msg3, the MAC entity discards TEMPORARY_C-RNTI, considers the collision resolution to be unsuccessful, and successfully decodes the decoded MAC PDU. Discard.

The MAC entity discards TEMPORARY_C-RNTI when the collision resolution timer expires and considers the conflict resolution to be unsuccessful. The MAC entity flushes the HARQ buffer used to transmit the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by one if the conflict resolution is deemed unsuccessful. 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 an SI request, the MAC entity considers the random access procedure to be incompletely completed.

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.

When the random access procedure is complete, the MAC entity discards the explicitly signaled non-conflict-based random access resource for non-conflict-based random access procedures other than the non-conflict-based random access procedure for beam failure recovery requests. Then, the HARQ buffer used for transmitting the MAC PDU in the Msg3 buffer is flushed.

Hereinafter, the configuration of the device according to this embodiment will be described.

FIG. 20 is a schematic block diagram showing the configuration of the terminal device 1 of the present embodiment. As shown in the figure, the terminal device 1 includes a wireless transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transmission / reception unit 10 is also referred to as a transmission unit, a reception unit, a monitor unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a measurement unit, a selection unit, or a control unit 14.

The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user operation or the like to the wireless transmission / reception unit 10. The upper layer processing unit 14 includes a medium access control (MAC) layer, a packet data integration protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs some or all of the layer processing. 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 measured 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 more PRACH opportunities. The upper layer processing unit 14 is set in the upper layer (for example, the RRC layer) when the bit information included in the information for instructing the start of the random access procedure received by the wireless transmission / reception unit 10 is a predetermined value. It may have a function of identifying one index from one or a plurality of indexes and setting it in the preamble index. The upper layer processing unit 14 may have a function of identifying an index associated with the selected reference signal from one or a plurality of indexes set by the RRC and setting it in the preamble index. The upper layer processing unit 14 may have a function of determining the next available PRACH opportunity based on the received information (for example, 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 received information (for example, SSB index information).

The medium access control layer processing unit 15 included in the upper layer processing unit 14 processes the MAC layer (medium access control layer). The medium access control layer processing unit 15 controls the transmission of the 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 processes the RRC layer (radio resource control layer). The wireless 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 signal of the upper layer received from the base station apparatus 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 apparatus 3. The radio resource control layer processing unit 16 controls (specifies) resource allocation based on the downlink control information received from the base station apparatus 3.

The wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, coding, 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 the data, and transmits the transmission signal 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 radio transmission / reception unit 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 instructing the start of the random access procedure. The wireless transmission / reception unit 10 may have a function of receiving information for receiving information that identifies a predetermined index. The wireless transmission / reception unit 10 may have a function of receiving information that identifies the index of the random access print. The wireless transmission / reception unit 10 may have a function of transmitting a 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 orthogonal demodulation (down covert), and removes unnecessary frequency components. RF
The unit 12 outputs the processed analog signal to the baseband unit.

The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 uses CP (Cyclic) from the converted digital signal.
The part corresponding to Prefix) is removed, and the signal in the frequency domain is extracted by performing Fast Fourier Transform (FFT) on the signal from which CP has been removed.

The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, and bases the data. Converts a band's digital signal to an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 removes an extra frequency component from the analog signal input from the baseband unit 13 using a low-pass filter, up-converts the analog signal to the carrier frequency, and transmits the analog signal via the antenna unit 11. To do. Further, the RF unit 12 amplifies the electric power. Further, the RF unit 12 may have a function of determining the transmission power of the uplink signal and / or the uplink channel to be transmitted in the service area 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 the present embodiment. As shown in the figure, the base station apparatus 3 includes a wireless transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transmission / reception unit 30 is also referred to as a transmission unit, a reception unit, a monitor unit, or a physical layer processing unit. Further, 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 a control unit 34.

The upper layer processing unit 34 includes a medium access control (MAC) layer, a packet data integration protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs some or all of the layer processing. The upper layer processing unit 34 may have a function of identifying 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 a 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 processes the MAC layer. The medium access control layer processing unit 35 performs processing related to the scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 36.

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 processes the RRC layer. The wireless resource control layer processing unit 36 generates downlink control information (uplink grant, downlink grant) including resource allocation information in the terminal device 1. The wireless 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), and the like. Generate or acquire from the upper node and output to the wireless transmission / reception unit 30. Further, the wireless resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1. The wireless resource control layer processing unit 36 may set various setting information / parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 transmits / notifies information indicating various setting information / parameters. The radio resource control layer processing unit 36 may transmit / notify information for identifying the setting of one or more reference signals in a cell.

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

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 a 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) that identifies one or more PRACH opportunities to the terminal device 1. The wireless transmission / reception unit 30 may have a function of transmitting information that identifies a predetermined index. The wireless transmission / reception unit 30 may have a function of transmitting information that identifies 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. Since some functions of the wireless transmission / reception unit 30 are the same as those of the wireless transmission / reception unit 10, the description thereof will be omitted. When the base station device 3 is connected to one or a plurality of 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.

Further, 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 the transmission path of data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are provided. It is clear that it has a plurality of blocks as components. For example, the upper layer processing unit 34 includes a radio resource management (Radio Resource Management) layer processing unit and an application layer processing unit. Further, the upper layer processing unit 34 may have a function of setting a plurality of scheduling request resources corresponding to each of the plurality of reference signals transmitted from the wireless transmission / reception unit 30.

The "part" in the drawing is an element that realizes 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 portion of the terminal device 1 with reference numerals 10 to 16 may be configured as a circuit. Each portion of the base station apparatus 3 with reference numerals 30 to 36 may be configured as a circuit.

(1) More specifically, the terminal device 1 that performs the random access procedure according to the first aspect of the present invention receives the first parameter and the second parameter of the upper layer, and receives the PDCCH including DCI. A receiving unit 10 and a transmitting unit 10 for transmitting a PUSCH scheduled by the DCI are provided, and a third parameter is defined in advance by a default table, the first parameter, the second parameter, and the like. And, the third parameter shows the information of the PUSCH time area resource allocation, and when 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 time area resource allocation of the PUSCH 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 first parameter and the second parameter of the upper layer, and transmits the PDCCH including the DCI. A transmitting unit 30 and a receiving unit 30 for receiving the PUSCH scheduled by the DCI are provided, and the third parameter is defined in advance by the default table, the first parameter, the second parameter, and the like. And, the third parameter shows the information of the PUSCH time area resource allocation, and when 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 region 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 shown, the time domain resource allocation of the PUSCH is given based on the third parameter. When the first parameter is indicated, the time domain resource allocation of the PUSCH is not based on the third parameter, but is given based on the first parameter.

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

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

As a result, the terminal device 1 can efficiently communicate with the base station device 3.

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

The program for realizing the function of the embodiment according to the present invention may be recorded on a computer-readable recording medium. It may be realized by loading the program recorded on this recording medium into a computer system and executing it. The "computer system" as used herein is a computer system built into a device, and includes hardware such as an operating system and 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 recording medium that can be read by a computer. Is also good.

Also, each functional block, or feature, of the device used in the embodiments described above may be implemented or implemented in an electrical circuit, such as an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein are general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof may be included. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. In addition, when an integrated circuit technology that replaces the current integrated circuit appears due to advances in semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit according to the technology.

In the embodiment related to the present invention, an example applied to a communication system composed of a base station device and a terminal device has been described, but in a system such as D2D (Device to Device) in which terminals communicate with each other. Is also applicable.

The invention of the present application is not limited to the above-described embodiment. Although an example of the device has been described in the embodiment, the present invention is not limited to this, and the present invention is not limited to this, and the stationary or non-movable electronic device installed indoors or outdoors, for example, an AV device, a kitchen device, and the like. It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design changes and the like within a range not deviating from the gist of the present invention are also included. Further, the present invention can be variously modified within the scope of the claims, and the technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in the different embodiments. Is done. In addition, the elements described in each of the above-described embodiments include a configuration in which elements having the same effect are replaced with each other.

1 (1A, 1B) Terminal equipment 3 Base station equipment 4 Transmission / reception point (TRP)
10 Wireless transmission / reception unit 11 Antenna unit 12 RF unit 13 Baseband unit 14 Upper layer processing unit 15 Media access control layer processing unit 16 Wireless resource control layer processing unit 30 Wireless transmission / reception unit 31 Antenna unit 32 RF unit 33 Baseband unit 34 Upper layer Processing unit 35 Media access control layer Processing unit 36 Wireless resource control layer Processing unit 50 Transmission unit (TXRU)
51 Phase shifter 52 Antenna element

Claims (12)

It is a terminal device that performs a random access procedure.
A receiver that receives the first and second parameters of the upper layer and receives PDCCH including DCI,
A transmitter that transmits 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 are P.
Shows information about USC 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 a terminal device given based on the selected parameters. When the first parameter is not shown, the time domain resource allocation of the PUSCH is given based on the third parameter, and when the first parameter is shown, the time domain of the PUSCH. The terminal device according to claim 1, wherein the resource allocation is given based on the first parameter, not based on the third parameter. The first parameter is included in the cell common PUSCH configuration.
The terminal device according to claim 1, wherein the second parameter is included in the UE-specific PUSCH configuration. The information on the PUSCH time domain resource allocation is described in claim 1, which indicates the slot offset between the DCI and the PUSCH, the start symbol of the PUSCH and the number of consecutively allocated symbols in the slot, and the mapping type of the PUSCH. Terminal device. It is a base station device that communicates with a terminal device that performs a random access procedure.
A transmitter that transmits the first and second parameters of the upper layer and transmits PDCCH including DCI,
A receiver that receives 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 are P.
Shows information about USC 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 the selected parameters. The time domain resource allocation of the PUSCH is given based on the third parameter when the first parameter is not shown, and when the first parameter is shown, the time domain of the PUSCH. 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. The first parameter is included in the cell common PUSCH configuration.
The base station apparatus according to claim 5, wherein the second parameter is included in the UE-specific PUSCH configuration. The information on the PUSCH time domain resource allocation is described in claim 5, which indicates the slot offset between the DCI and the PUSCH, the start symbol and the number of consecutively allocated symbols of the PUSCH in the slot, and the mapping type of the PUSCH. Base station equipment to do. It is a communication method of a terminal device that performs a random access procedure.
The step of receiving the first parameter and the second parameter of the upper layer and receiving the PDCCH including DCI, and
A step of 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 are P.
Shows information about USC 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 a communication method given based on a selected parameter. A communication method for a base station device that communicates with a terminal device that performs a random access procedure.
The step of transmitting the first parameter and the second parameter of the upper layer and transmitting the PDCCH including DCI, and
With a step 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 are P.
Shows information about USC 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 a communication method given based on a selected parameter. An integrated circuit mounted on a terminal device that performs a random access procedure.
The function of receiving the first and second parameters of the upper layer and receiving the PDCCH including DCI,
The function of transmitting the PUSCH scheduled by the DCI and the terminal device exerting it
The third parameter is predefined by the default table
The first parameter, the second parameter, and the third parameter are P.
Shows information about USC 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 an integrated circuit given based on selected parameters. An integrated circuit mounted on a base station device that communicates with a terminal device that performs a random access procedure.
A function to transmit the first parameter and the second parameter of the upper layer and transmit PDCCH including DCI, and
The function of receiving the PUSCH scheduled by the DCI and the function of causing the base station apparatus to exert it
The third parameter is predefined by the default table
The first parameter, the second parameter, and the third parameter are P.
Shows information about USC 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 an integrated circuit given based on selected parameters.

Images