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

Abstract

To provide a method that performs efficient communication between a terminal device and a base station device.SOLUTION: A terminal device 1 receives a first parameter and a second parameter of an upper-level layer. The first parameter is used for validating transform precoding for PUSCH in a random access procedure. The second parameter is used for indicating UE-specific selection of transform precoding for PUSCH. The terminal device 1 receives an RAR message S802 and transmits the PUSCH scheduled by a first UL grant included in the message. The transform precoding for PUSCH transmission is set to 'valid' or 'invalid' on the basis of the second parameter in a case where the second parameter is set, and is set to 'valid' or 'invalid' on the basis of the first parameter in a case where no second parameter is set.SELECTED DRAWING: Figure 8

Description

  The present invention relates to a base station device, a terminal device, a communication method, and an integrated circuit.

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

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

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

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

  (1) In order to achieve the above object, the embodiment of the present invention takes the following means. That is, the terminal device according to one aspect of the present invention receives a first parameter and a second parameter of an upper layer and receives a PDSCH including a RAR message, and a first UL included in the RAR message. A transmitter for transmitting a PUSCH scheduled by a grant, the first parameter being used to enable transform precoding for the PUSCH in a contention-based random access procedure; 2 parameters are used to indicate the UE-specific selection of transform precoding for PUSCH, and in the non-contention based random access procedure, the transform precoding for PUSCH transmission is If set, the second Based on the parameter, it is set to either'valid 'or'invalid', and if the second parameter is not set, it is set to'valid 'or'invalid' based on the first parameter. .

(2) Further, the base station device according to one aspect of the present invention includes: a transmission unit that transmits the first parameter and the second parameter of an upper layer and transmits PDSCH including a RAR message; A receiver for receiving a PUSCH scheduled by a first UL grant, the first parameter being used to enable transform precoding for the PUSCH in a contention based random access procedure. And the second parameter is used to indicate a UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is performed by the second parameter. If two parameters are set, If the second parameter is set to either “valid” or “invalid” based on the second parameter and the second parameter is not set, then it is set to “valid” or “invalid” based on the first parameter. Set.

  (3) Further, a communication method according to one aspect of the present invention is a communication method for a terminal device, wherein the first parameter and the second parameter of an upper layer are received, PDSCH including a RAR message is received, and The PUSCH scheduled by the first UL grant included in the RAR message is transmitted, and the first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure. , The second parameter is used to indicate UE-specific selection of transform precoding for PUSCH, and in pre-contention based random access procedure, transform precoding for PUSCH transmission is performed by the second parameter. If the parameters of If the second parameter is not set and is set to either'valid 'or'invalid' according to the first parameter, it is set to'valid 'or'invalid' based on the first parameter. It

  (4) Further, a communication method according to an aspect of the present invention is a communication method for a base station apparatus, including transmitting a first parameter and a second parameter of an upper layer, transmitting a PDSCH including a RAR message, The PUSCH scheduled by the first UL grant included in the RAR message is received, and the first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure. And the second parameter is used to indicate a UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is performed by the second parameter. If 2 parameters are set, If the second parameter is set to either “valid” or “invalid” based on the second parameter and the second parameter is not set, either “valid” or “invalid” is determined based on the first parameter. Set.

  (5) Further, the integrated circuit according to one aspect of the present invention is an integrated circuit mounted on a terminal device, which receives a first parameter and a second parameter of an upper layer and receives a PDSCH including a RAR message. And a function of transmitting the PUSCH scheduled by the first UL grant included in the RAR message to the terminal device, wherein the first parameter is the contention based random access procedure, And the second parameter is used to indicate UE-specific selection of transform precoding for PUSCH, in a non-contention based random access procedure, Transform precoding for PUSCH transmission The flag is set to either'valid 'or'invalid' based on the second parameter if the second parameter is set, and to the first if the second parameter is not set. Set to either'valid 'or'invalid' based on the parameter.

(6) Further, an integrated circuit according to an aspect of the present invention is an integrated circuit mounted in a base station device, which transmits a PDSCH including a RAR message by transmitting a first parameter and a second parameter of an upper layer. The base station apparatus is caused to exhibit the function of transmitting and the function of receiving the PUSCH scheduled by the first UL grant included in the RAR message, and the first parameter is the contention-based random access procedure, The second parameter is used to enable transform precoding for the PUSCH, the second parameter is used to indicate a UE-specific selection of transform precoding for the PUSCH, and a non-contention based random access procedure. In the transform precoding for the PUSCH transmission, If the second parameter is set, the ringing is set to either'valid 'or'invalid' based on the second parameter, and if the second parameter is not set, the first Set to either'valid 'or'invalid' based on the 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 radio | wireless communications system which concerns on embodiment of this invention. It is a figure which shows the example of the SS / PBCH block and SS burst set which concern on embodiment of this invention. It is a figure which shows an example of schematic structure of the uplink and downlink slot which concerns on embodiment of this invention. FIG. 6 is a diagram showing a relationship in the time domain of subframes, slots, and minislots according to the embodiment of the present invention. It is a figure which shows an example of the slot or sub-frame which concerns on embodiment of this invention. It is a figure showing an example of beamforming concerning an embodiment of the present invention. It is a figure which shows an example of the frequency hopping which concerns on embodiment of this invention. . It is a figure which shows an example of the random access procedure of the terminal device 1 which concerns on embodiment of this invention. It is a figure which shows an example of the field contained in RAR UL grant which concerns on embodiment of this invention. It is a figure which shows an example of interpretation of the'PUSCH frequency resource allocation 'field which concerns on this embodiment. It is a figure which shows an example explaining the uplink resource allocation type 1 with respect to BWP which concerns on this embodiment. It is a figure which shows an example which calculates RIV which concerns on embodiment of this invention. It is a figure which shows an example of allocation of the SSB index with respect to the PRACH opportunity which concerns on this embodiment. It is a flowchart which shows an example of the random access procedure of the MAC entity which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the terminal device 1 which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the base station apparatus 3 which concerns on embodiment of this invention. FIG. 6 is a diagram illustrating an example of a second hop frequency offset for a PUSCH scheduled by a RAR UL grant with frequency hopping according to an embodiment of the present invention.

  Hereinafter, embodiments of the present invention will be described.

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

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

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

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

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

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

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

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

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

The wireless communication system of this embodiment may be applied with TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). TD for all of the cells
A D (Time Division Duplex) method or an FDD (Frequency Division Duplex) method may be applied. Further, cells to which the TDD scheme is applied and cells to which the FDD scheme is applied may be aggregated. The TDD scheme may be referred to as an unpaired spectrum operation. The FDD scheme may be referred to as Paired spectrum operation.

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

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

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

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

  The PBCH is used to notify an important information block (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1.

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

The PDCCH is used to transmit (or carry) downlink control information (Downlink Control Information: DCI) in downlink radio communication (radio communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (which may be referred to as DCI formats) are defined for transmission of downlink control information. That is, a field for downlink control information is defined as DCI and is mapped to information bits. The PDCCH is transmitted in the PDCCH candidate. The terminal device 1 monitors a set of PDCCH candidates (candidate) in the serving cell. Monitoring means trying to decode the PDCCH according to a certain DCI format.

For example, the following DCI format may be defined.
・ DCI format 0_0
・ DCI format 0_1
・ DCI format 1_0
・ DCI format 1_1
・ DCI format 2_0
・ DCI format 2_1
・ DCI format 2_2
・ DCI format 2_3

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

  The DCI format 0_1 may be used for PUSCH scheduling in a serving cell. The DCI format 0_1 refers to information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP: BandWidth Part), channel state information (CSI: Channel State Information) request, and sounding reference. A signal (SRS: Sounding Reference Signal) request and information about the antenna port may be included. The DCI format 0_1 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, SP-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 PDSCH scheduling in a serving cell. The DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation). The DCI format 1_0 is added with a CRC scrambled by any one of C-RNTI, CS-RNTI, MCS-C-RNTI, P-RNTI, SI-RNTI, RA-RNTI, and / or TC-RNTI. May be. DCI format 1_0 may be monitored in the common search space or the UE-specific search space.

DCI format 1_1 may be used for PDSCH scheduling in a serving cell. The DCI format 1_1 includes PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), band portion (BWP) information, transmission configuration indication (TCI), and antenna port information. Good. The DCI format 1_1 may have a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI. DCI format 1_1 may be monitored in the UE-specific search space.

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

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

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

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

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

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

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

The PUCCH is used to transmit uplink control information (UCI) in uplink radio communication (radio communication from the terminal device 1 to the base station device 3). Here, the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel. Further, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request the UL-SCH resource. Further, the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement). HARQ-ACK is downlink data (Transport block, Medium Access).
HARQ-ACK for Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH) may be indicated.

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

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

Here, the base station device 3 and the terminal device 1 exchange (transmit / receive) signals in an upper layer (upper layer: higher 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 a radio resource control (RRC: Radio Resource Control) layer. You may. Further, the base station device 3 and the terminal device 1 may transmit / receive a MAC control element in a MAC (Medium Access Control) layer. Further, the RRC layer of the terminal device 1 acquires the system information reported from the base station device 3. Here, the RRC signaling, the system information, and / or the MAC control element are also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter. The upper layer here means an upper layer viewed from the physical layer, and thus may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like. For example, in the processing of the MAC layer, the upper layer may include one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer and the like. Hereinafter, the meaning of “A is given by the upper layer” and “A is given by the upper layer” means that the upper layer (
It may mean that the RRC layer, the MAC layer and the like) receive A from the base station device 3 and give the received A from the upper layer of the terminal device 1 to the physical layer of the terminal device 1.

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

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used for transmitting the information output from the upper layer, but is used by the physical layer.
・ Synchronization signal (SS)
・ Reference Signal (RS)

  The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The cell ID may be detected using PSS and SSS.

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

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

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

DMRS is used to demodulate the modulated signal. Two types of reference signals for demodulating PBCH and PDSCH may be defined in DMRS, or both may be referred to as DMRS. The CSI-RS is used for measuring channel state information (CSI) and beam management, and a periodic or semi-persistent or aperiodic CSI reference signal transmission method is applied. The CSI-RS may be defined as a non-zero power (NZP) CSI-RS and a zero-power (ZP: Zero Power) CSI-RS having zero transmission power (or reception power). Here, the ZP CSI-RS may be defined as a CSI-RS resource that has zero transmission power or is not transmitted. TRS is used to guarantee Doppler shift during high-speed movement, and TRS may be used as one setting of CSI-RS, for example, 1-port CSI-RS is used as TRS. Radio resources may be configured.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The following procedure may be included as a procedure for configuring, setting, or establishing a beam pair link.
・ Beam selection
・ Beam refinement
・ Beam recovery

  For example, the beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Further, the beam improvement may be a procedure of selecting a beam having a higher gain or changing the beam between the base station device 3 and the terminal device 1 optimally by moving the terminal device 1. The beam recovery may be a procedure of reselecting a beam when the quality of the communication link is deteriorated due to a blockage generated by a blocking object or a person passing in the communication between the base station device 3 and the terminal device 1.

Beam management may include beam selection and beam refinement. Beam recovery may include the following procedures.
・ Detection of beam failure ・ Finding a new beam ・ Sending beam recovery request ・ Monitoring response to beam recovery request

For example, when selecting the transmission beam of the base station apparatus 3 in the terminal device 1, RSPI (Reference Signal Received Power) of CSI-RS or SSS included in the SS / PBCH block may be used, or CSI may be used. Good. In addition, a CSI-RS resource index (CRI: CSI-RS Resource Index) may be used as a report to the base station device 3, or PBCH included in the SS / PBCH block and / or for demodulation used for demodulating the PBCH. An index designated by a reference signal (DMRS) sequence may be used.

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

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

This QCL can be extended to beam management. Therefore, the QCL extended to the space may be newly defined. For example, as the long term property of the channel in the assumption of QCL in the spatial domain, the arrival angle (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or the angular spread in the wireless link or the channel are used. (Angle Spread, such as ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)), sending angle (AoD, ZoD, etc.) and its angular spread (Angle Spread,
For example, ASD (Angle Spread of Departure) and ZSD (Zenith angle Spread of Departure)
), Spatial correlation (Spatial Correlation), and reception spatial parameter.

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

As the QCL type, a combination of long-term characteristics that may be considered to be QCL may be defined. For example, the following types may be defined.
-Type A: Doppler shift, Doppler spread, average delay, delay spread-Type B: Doppler shift, Doppler spread-Type C: Average delay, Doppler shift-Type D: Reception spatial parameter

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

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

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

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

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

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

Reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined as resource blocks. One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may constitute a resource block at a subcarrier interval of 15 kHz, for example, and may be numbered in ascending order. The subcarrier index 0 in the reference resource block index 0 may be referred to as a reference point A (point A) (may be simply referred to as “reference point”). The common resource block is a resource block numbered in ascending order from 0 in each subcarrier interval setting μ from the reference point A. The resource grid described above is defined by this common resource block. The physical resource blocks are resource blocks numbered in ascending order from 0 included in the band portion (BWP) described later, and the physical resource blocks are in ascending order from 0 included 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 to the downlink BWP in the upper layer (upper layer), and are set in the uplink. It is given in the upper layers in BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf = 2 ^ μ · 15 (kHz).

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

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

  A minislot (may be referred to as a subslot) is a time unit composed of fewer OFDM symbols than the number of OFDM symbols included in the slot. The figure shows the case where the minislot is composed of 2 OFDM symbols as an example. The OFDM symbols in a minislot may match the OFDM symbol timing that makes up the slot. The minimum unit of scheduling may be a slot or a minislot. Also, assigning minislots may be referred to as non-slot based scheduling. Further, scheduling a minislot may be expressed as scheduling a resource in which a relative time position between a reference signal and a start position of 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 the slot format. Here, the case where the slot length is 1 ms at a subcarrier interval of 15 kHz is shown as an example. In the figure, D indicates a downlink and U indicates an uplink. As shown in the figure, within a certain time period (for example, the minimum time period that must be assigned to one UE in the system),
It may include one or more of a downlink symbol, a flexible symbol, and an uplink symbol. Note that these ratios may be predetermined as a slot format. Further, it may be defined by the number of downlink OFDM symbols included in the slot or the start position and end position in the slot. Further, it may be defined by the number of uplink OFDM symbols or DFT-S-OFDM symbols included in the slot or the start position and end position in the slot. Note that scheduling a slot may be expressed as scheduling a resource in which the relative time position between the reference signal and the slot boundary is fixed.

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

  5A may also be referred to as a certain time period (for example, a minimum unit of time resources that can be assigned to one UE, a time unit, or the like. Further, a plurality of minimum units of time resources are bundled and referred to as a time unit. 5B), all of them are used for downlink transmission. In FIG. 5B, uplink scheduling is performed via the PDCCH in the first time resource, and the processing delay of the PDCCH and the downlink are performed. The uplink signal is transmitted via the flexible symbol including the switching time from the uplink to the generation of the transmission signal. FIG. 5C is used for transmission of the PDCCH and / or the downlink PDSCH in the first time resource, and the PUSCH or the PUCCH is transmitted through the processing delay, the switching time from the downlink to the uplink, and the gap for generating the transmission signal. It is used to send. Here, as an example, the uplink signal may be used for transmitting HARQ-ACK and / or CSI, that is, UCI. FIG. 5 (d) is used for transmission of PDCCH and / or PDSCH in the first time resource, and has processing delay, downlink to uplink switching time, and uplink PUSCH and / or via a gap for generation of a transmission signal. Alternatively, it is used for PUCCH transmission. Here, as an example, the uplink signal may be used for transmission of uplink data, that is, UL-SCH. FIG. 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 configured by 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 transmitter unit (TXRU: Transceiver unit) 50, the phase is controlled by a phase shifter 51 for each antenna element, and the antenna element 52 transmits the signal in an arbitrary direction with respect to the transmission signal. The beam can be aimed. Typically, TXRU may be defined as an antenna port, and in the terminal device 1, only the antenna port may be defined. By controlling the phase shifter 51, directivity can be directed in an arbitrary direction, so that the base station device 3 can communicate with the terminal device 1 using a beam having a high gain.

  The band part (BWP, Bandwidth part) will be described below. BWP is also referred to as carrier BWP. BWP may be set for each of the downlink and the uplink. BWP is defined as a set of contiguous physical resources selected from a contiguous subset of common resource blocks. The terminal device 1 can set up to four BWPs in which one downlink carrier BWP (DL BWP) is activated at a certain time. The terminal device 1 can set up to four BWPs in which one uplink carrier BWP (UL BWP) is activated at a certain time. In the case of carrier aggregation, BWP may be set in each serving cell. At this time, the fact that one BWP is set in a certain serving cell may be expressed as the case where no BWP is set. Further, the setting of two or more BWPs may be expressed as the BWP being set.

<MAC entity operation>
In an 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. To be done. BWP switching for a serving cell is controlled by PDCCH indicating downlink allocation or uplink grant. BWP switching for a serving cell may also be controlled by the BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of the random access procedure. Upon addition of SpCell (PCell or PSCell) or activation of SCell, one BWP is first active without receiving PDCCH indicating downlink allocation or uplink grant. 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 certain serving cell is designated by the RRC or PDCCH sent from the base station device 3 to the terminal device 1. Also, the first active DL BWP (first active DL BWP) and the UL BWP (first active UL BWP) may be included in the message 4. In the unpaired spectrum (TDD band, etc.), DL BWP and UL BWP are paired, and BWP switching is common to UL and DL. In the active BWP for each of the activated serving cells for which the BWP is set, the MAC entity of the terminal device 1 applies normal processing. Normal processing includes transmitting UL-SCH, transmitting RACH, monitoring PDCCH, transmitting PUCCH, transmitting SRS, and receiving DL-SCH. For each activated serving cell for which BWP is set, in the inactive BWP, the MAC entity of the terminal device 1 does not transmit UL-SCH, does not transmit RACH, does not monitor PDCCH, does not transmit PUCCH, Does not send SRS and does not receive DL-SCH. If a serving cell is deactivated, no active BWP may be present (eg, active BWP is deactivated).

<RRC operation>
A BWP information element (IE) included in the RRC message (system information to be broadcast or information sent in the dedicated RRC message) is used to set the BWP. The RRC message transmitted from the base station device 3 is received by the terminal device 1. For each serving cell, the network (such as the base station device 3) should have at least one downlink BWP and one (if the serving cell is configured for uplink) or two (supplementary uplink in the Appendix). Is used), at least an initial BWP (initial BWP) including an uplink BWP for the terminal device 1,
Set. Further, the network may configure additional uplink BWP or downlink BWP for a serving cell. The BWP setting is divided into an uplink parameter and a downlink parameter. In addition, the BWP setting is divided into a common parameter and a dedicated parameter. Common parameters (BWP uplink common I
E, BWP downlink common IE, etc.) are cell-specific. The common parameters of the initial BWP of the primary cell are also provided in the system information. For all other serving cells, the network provides common parameters on dedicated signals. The BWP is identified by the BWP ID. The initial BWP has a BWP ID of 0. BWP IDs of other BWPs take values 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) is
For PDCCH reception in the control resource set (CORESET) for the type 0 PDCCH common search space, the position and number of consecutive PRBs, the subcarrier spacing, and the cyclic prefix may be defined. The position of the consecutive PRBs starts from the PRB with the smallest index and ends with the PRB with the largest index among the PRBs of the control resource set for the type 0 PDCCH common search space. 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 is SIB1 (systemInformationBlock
Type1, ServingCellConfigCommonSIB) or ServingCellCongfigC
It may be included in ommon. The information element ServingCellCongfigureCommon SIB is used in SIB1 to set the cell-specific parameter of the serving cell for the terminal device 1.

  That is, when the upper layer parameter initialDownlinkBWP is not set (provided) to the terminal device 1, the size of the initial DL BWP is the number of resource blocks of the control resource set (CORESET # 0) for the type 0 PDCCH common search space. It may be. When the upper layer parameter initialDownlinkBWP is set (provided) for the terminal device 1, the size of the initial DL BWP may be given by the locationAndBandwidth included in the upper layer parameter initialDownlinkBWP. The upper layer parameter locationAndBandwidth may indicate the position and bandwidth in 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, of the DL BWPs set for the terminal device 1, the default DL BWP can be set by the parameter defaultDownlinkBWP-Id of the upper layer. If the upper layer parameter defaultDownlinkBWP-Id is not provided to the terminal device 1, the default DL
BWP is the initial DL BWP.

The 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. An initial UL BWP (initial active UL BWP) may be set (provided) in the terminal device 1 by the upper layer parameter initialUplinkBWP for the operation in the SpCell or the secondary cell. When a supplementary uplink carrier (supplementary UL carrier) is set to the terminal device 1, the terminal device 1 uses the initialUplinkBWP included in the parameter supplementaryUplink of the upper layer to set the initial UL on the supplementary uplink carrier. BWP may be set.

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

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

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

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

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

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

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

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

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

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

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

The terminal device 1 monitors a set of PDCCH candidates in one or more CORESETs arranged in each active serving cell configured to monitor the PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring refers to decoding each PDCCH candidate depending on the DCI format or formats being monitored. A set of PDCCH candidates monitored by the terminal device 1 is defined by a PDCCH search space set). One search space set is a common search space set or a UE-specific search space set. In the above, the search space set is called a search space, the common search space set is called a common search space, and the UE-specific search space set is called a UE-specific search space. The terminal device 1 monitors PDCCH candidates with one or more of the following search space sets.
-Type 0 PDCCH common search space set (a Type0-PDCCH common search
space set): This search space set is a higher-layer parameter pdcch-ConfigSIB1 indicated by MIB or search space SIB1 (searchSpaceSIB1) indicated by PDCCH-ConfigCommon or search space zero included in PDCCH-ConfigCommon (searchSpaceZero). Set by. This search space is for monitoring the DCI format of the CRC scrambled with SI-RNRI in the primary cell.
-Type 0A-PDCCH common search space set: This search space set is set by the search space (searchSpaceOtherSystemInformation) indicated by PDCCH-ConfigCommon, which is a parameter of the upper layer. This search space is for monitoring the DCI format of the CRC scrambled with SI-RNRI in the primary cell.
-Type 1 PDCCH common search space set (a Type1-PDCCH common search
space set): This search space set is a parameter of the upper layer, PDCCH.
-Set by the search space (ra-SearchSpace) for the random access procedure denoted by 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 a random access procedure.
-Type 2 PDCCH common search space set (a Type2-PDCCH common search
space set): This search space set is a parameter of the upper layer, PDCCH.
-Set by the search space (pagingSearchSpace) for the paging procedure indicated by ConfigCommon. This search space is for monitoring the DCI format of the P-RNTI scrambled CRC in the primary cell.
-Type 3 PDCCH common search space set (a Type3-PDCCH common search
space set): This search space set is a parameter of the upper layer, PDCCH.
The search space type indicated by -Config is set by the common search space (SearchSpace). This search space is for monitoring 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 C-RNTI, CS-RNTI (s), or MSC-C-RNTI scrambled CRC.
-UE-specific search space set: In this search space set, the search space type indicated by PDCCH-Config, which is an upper layer parameter, is set by the UE-specific search space (SearchSpace). . This search space is for monitoring 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 a plurality of search space sets according to the corresponding upper layer parameters (searchSpaceZero, searchSpaceSIB1, searchSpaceOtherSystemInformation, pagingSearchSpace, ra-SearchSpace, etc.), the terminal device 1 may use the C-RNTI or When CS-RNTI is provided, the terminal device 1 monitors PDCCH candidates for DCI format 0_0 and DCI format 1_0 having C-RNTI or CS-RNTI in the one or more search space sets. May be.

  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 configuration information is used to identify (reference) the DL BWP in a certain serving cell. The BWP identifier included in the UL BWP configuration information is used to identify (reference) the UL BWP in a certain serving cell. The BWP identifier is given to each of the DL BWP and UL BWP. For example, the identifier of the BWP corresponding to the DL BWP may be referred to as a DL BWP index. The identifier of the BWP corresponding to the UL BWP may be referred to as the UL BWP index (UL BWP index). The initial DL BWP is referenced by the DL BWP identifier 0. The initial UL BWP is referenced by the UL BWP identifier 0. Each of the other DL BWPs or other UL BWPs may be referenced from BWP identifier 1 to maxNrofBWPs. That is, the BWP identifier (bwp-Id = 0) set to 0 is associated with the initial BWP and cannot be used for another BWP. maxNofBWPs is the maximum number of BWPs per serving cell and is 4. That is, the value of the other BWP identifier takes a value from 1 to 4. The setting information of the other upper layer is associated with a specific BWP by using the BWP identifier. 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.

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

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

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

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

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

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

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

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

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

  In the terminal device 1, (1) the CSI-RS and the random access resource for non-contention based random access are associated with the RRC, and (2) the 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 exceeding the predetermined threshold and preambles the ra-PreambleIndex associated with the selected CSI-RS. Set to index.

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

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

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

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

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

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

<Transmission of random access preamble (S1003)>
S1003 is a procedure relating to transmission of a random access preamble (random access preamble transmission). For each random access preamble, the MAC entity shall: (1) state variable PREAMBLE_TRANSMISSION_COUNTER is greater than 1; Increment the state variable PREAMBLE_POWER_RAMPING_COUNTER by one if the assigned SS / PBCH block has not changed.

  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 preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER-1) * powerRampingStep.

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

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

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

A MAC PDU (random access response MAC PDU) consists of one or more MAC subPDUs and possible padding. Each MAC subPDU is composed of any of the following.
MAC sub-header (subheader) containing only Backoff Indicator
-MAC subheader (subheader) indicating only RAPID
MAC sub-header (subheader) indicating RAPID and MAC RAR (MAC payload for Random Access Response)

  The MAC sub PDU including only the Backoff Indicator is placed at the head of the MAC PDU. The padding is placed at the end of the MAC PDU. The MAC subPDU including only the RAPID and the MAC subPDU including the RAPID and the MAC RAR can be arranged anywhere between the padding and the MAC subPDU including only the Backoff Indicator.

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

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

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

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

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

  A MAC entity may consider a random access response to be successfully received if it contains a MAC subPDU that includes a random access preamble identifier corresponding to the PREAMBLE_INDEX to which the random access response was sent.

  The MAC entity considers the random access procedure to be successfully completed if (1) the random access response is considered to be successfully received, and (2) the random access response includes a MAC subPDU containing only RAPID, and , Reception of an acknowledgment to an SI request (symstem information request) is shown in the upper layer. Here, when the condition (2) is not satisfied, the MAC entity applies the following operation A to the serving cell in which the random access preamble is transmitted.

<Start of operation A>
The MAC entity processes the received transmission timing adjustment information (Timing Advance Command) and indicates to the lower layer the 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 the SCell for SRS only, the MAC entity may ignore the received UL grant. Otherwise, the MAC entity processes the received UL grant value and indicates it to lower layers.

  If the random access preamble is not selected by the MAC entity from the range of contention based random access preambles, the MAC entity may consider the random access procedure to have completed successfully.

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

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

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

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

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

  The MAC entity may stop the random access response window upon successfully receiving a random access response including a random access preamble identifier that matches the transmitted preamble index.

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

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

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

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

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

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

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

The MAC entity discards the TEMPORARY_C-RNTI if the collision resolution timer expires and considers the contention resolution not successful. The MAC entity flushes the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer and increments the preamble transmission counter (PREAMBLE_TRANSMISSION_COUNTER) by 1 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 the SI request, the MAC entity considers that the random access procedure has not been completed successfully.

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

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

The random access procedure of this embodiment will be described.
Random access procedures are classified into two procedures: contention-based (CB) and contention-free (non-CB) (which may also be referred to as CF). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA.

  The random access procedure is applicable to (i) transmission of random access preamble (message 1, Msg1) on PRACH, (ii) reception of random access response (RAR) message with PDCCH / PDSCH (message 2, Msg2), and applicable. In this case, (iii) message 3 PUSCH (Msg3 PUSCH) may be transmitted, and (iv) PDSCH for conflict resolution may be received.

  The contention based random access procedure is initiated by PDCCH order, MAC entity, beam failure notification from lower layers, RRC, etc. When the beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1, if a certain condition is satisfied, the MAC entity of the terminal device 1 starts the 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. May be. This random access procedure is a random access procedure for beam failure recovery request. The random access procedure initiated by the MAC entity includes the random access procedure initiated by the scheduling request procedure. The random access procedure for beam failure recovery request may or may not be considered a random access procedure initiated by a MAC entity. Since the random access procedure for beam failure recovery request and the random access procedure started by the scheduling request procedure may perform different procedures, the random access procedure for beam failure recovery request and the scheduling request procedure are distinguished. You may do it. The random access procedure for the beam failure recovery request and the scheduling request procedure may be a random access procedure initiated by a MAC entity. In one embodiment, a random access procedure initiated by a scheduling request procedure is referred to as a MAC entity initiated random access procedure, and a random access procedure for a beam failure recovery request is a random access by beam failure notification from a lower layer. You may call it a procedure. Hereinafter, the start of the random access procedure when receiving the beam failure notification from the lower layer may mean the start of the random access procedure for the beam failure recovery request.

  The terminal device 1 makes an initial access from a state where it is not connected (communicated) with the base station device 3, and / or uplink data or transmission which is connected to the base station device 3 but is transmittable to the terminal device 1. A contention-based random access procedure is performed at the time of scheduling request when possible sidelink data occurs. However, the use of contention-based random access is not limited to these.

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

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

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

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

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

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

  However, the random access setting information may include common information within the cell, or may include dedicated information that is different 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, a part of the random access setting information may be associated with all of the set one or more CSI-RSs. However, a part of the random access setting information may be associated with one downlink transmission beam (or beam index).

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

  The PRACH opportunity will be described below.

  The set of one or more PRACH opportunities available for transmission of the random access preamble may be specified by the upper layer parameter prac-ConfigIndex provided in the upper layer (upper layer signal). According to a PRACH setting (physical random access channel setting) index given by prac-ConfigIndex and a predetermined table (also referred to as a random access channel setting (PRACH config) table), it can be used for transmitting a random access preamble 1 A set of one or more PRACH opportunities is identified. However, the specified one or more PRACH opportunities may be a set of PRACH opportunities associated with each of one or more SS / PBCH blocks transmitted by the base station apparatus 3.

  However, the PRACH setting index can transmit a random access preamble, which is a cycle in which a set of PRACH opportunities shown in the random access setting table is temporally repeated (PRACH setting cycle (physical random access channel setting cycle: PRACH configuration period)). It may be used to set the subcarrier index, resource block index, subframe number, slot number, system frame number, symbol number, and / or preamble format.

  However, the number of SS / PBCH blocks mapped to each PRACH opportunity may be indicated by an upper layer parameter SSB-perRACH-Occasion provided in the upper layer. If SSB-perRACH-Occlusion is less than 1, then one SS / PBCH block is mapped to multiple consecutive PRACH opportunities.

  However, the number of random access preambles mapped to each SS / PBCH block may be indicated by the upper layer parameter cb-preamblePerSSB provided in the upper layer. The number of random access preambles mapped to each SS / PBCH block at each PRACH opportunity may be calculated from SSB-perRACH-Occlusion and cb-preamblePerSSB. The index of the random access preamble mapped to each SS / PBCH block on each PRACH occasion may be identified from the SB-perRACH-Occasion, cb-preamblePerSSB, and SSB index.

For PRACH opportunities, the SSB index may be mapped with the following rules.
(1) First, one PRACH opportunity is mapped in ascending order of preamble indexes. For example, if the number of preambles in a PRACH opportunity is 64 and the number of random access preambles mapped to each SS / PBCH block in each PRACH opportunity is 32, the SSB indices mapped to a certain PRACH opportunity are n and n + 1. Becomes
(2) Second, a plurality of frequency-multiplexed PRACH opportunities are mapped in ascending order of frequency resource indexes. For example, when two PRACH opportunities are frequency-multiplexed and the SSB indexes mapped to the PRACH opportunities with a small frequency resource index are n and n + 1, the SSB indexes mapped to the PRACH opportunities with a large frequency resource index are n + 2. It becomes n + 3.
(3) Third, multiple PRACH opportunities time-multiplexed in the PRACH slot are mapped in ascending order of time resource index. For example, in addition to the example of (2) above, when two more PRACH opportunities are multiplexed in the time direction within the PRACH slot, the SSB indices mapped to these PRACH opportunities are n + 4, n + 5 and n + 6, n + 7. .
(4) Fourth, a plurality of PRACH slots are mapped in ascending order of index. For example, when the RACH opportunity exists in the next PRACH slot in addition to the example of the above (3), the SSB indexes to be mapped are n + 8, n + 9, .... However, in the above example, when n + x becomes larger than the maximum value of the SSB index, the value of the SSB index returns to 0.

  FIG. 13 is a diagram illustrating an example of SSB index allocation to PRACH opportunities according to the embodiment of the present invention. In FIG. 13, two PRACH slots exist in a certain time period, two PRACH slots (RO) exist in the time direction and two PRACH opportunities (RO) exist in one PRACH slot, and SSB indexes 0 to 11 exist. An example of the case is shown. Two SSB indexes are mapped to one PRACH opportunity, SSB indexes are mapped according to the rules of (1) to (4) above, and SSB index 0 is mapped again from the seventh PRACH opportunity.

  An SSB index is mapped to each PRACH opportunity, but even if all PRACH opportunities within the PRACH setting cycle specified by prac-ConfigIndex are used, all SSB indexes (all SSs transmitted by the base station device 3 are / PBCH block), the SSB index may be mapped over multiple PRACH setup periods. However, the number of all SS / PBCH blocks transmitted by the base station device 3 may be indicated by an upper layer parameter. A period in which the PRACH setting period is repeated a predetermined number of times so that all SSB indexes are mapped at least once is referred to as an association period. As the number of PRACH setting cycles forming the association cycle, a minimum value satisfying the above condition may be used from a set of a plurality of predetermined values. The predetermined set of values may be set for each PRACH setting cycle. However, even if all the SSB indexes are mapped to the PRACH opportunities in the association period and the number of remaining PRACH opportunities is larger than the number of SS / PBCH blocks, the SSB indexes are mapped again. Good. However, if all SSB indexes are mapped to PRACH opportunities in the association period and the number of remaining PRACH opportunities is smaller than the number of SS / PBCH blocks, the remaining PRACH opportunities have SSB. The index does not have to be mapped. A cycle in which a PRACH opportunity is allocated once for all SSB indexes is called an SSB index allocation cycle. When SSB-perRACH-Occlusion is 1 or more, each SSB index is mapped to one PRACH opportunity in one SSB index allocation cycle. When SSB-perRACH-Occlusion has a value smaller than 1, each SSB index is mapped to the PRACH opportunity of 1 / SSB-perRACH-Occlusion in one SSB index allocation cycle. The terminal device 1 may specify the association cycle based on the PRACH setting cycle indicated by the PRACH setting index and the number of SS / PBCH blocks specified by the upper layer parameter provided by the upper layer (upper layer signal). .

  Each of the one or more random access preamble groups included in the random access setting information may be associated with each reference signal (for example, SS / PBCH block, CSI-RS, or downlink transmission beam). The terminal device 1 may select the random access preamble group based on the received reference signal (for example, SS / PBCH block, CSI-RS, or downlink transmission beam).

However, the random access preamble group associated with each SS / PBCH block may be specified by one or more parameters notified by the upper layer. One of the one or more parameters may be an index (eg, a start index) of one or more preambles available. One of the one or more parameters may be the number of preambles available for contention based random access per SS / PBCH block. One of the one or more parameters may be the sum of the number of preambles available for contention-based random access and the number of preambles available for non-contention-based random access per SS / PBCH block. One of the one or more parameters may be the number of SS / PBCH blocks associated with one PRACH opportunity.

  However, the terminal device 1 receives one or a plurality of downlink signals transmitted using one downlink transmission beam, respectively, and receives random access setting information associated with one downlink signal among them. However, the random access procedure may be performed based on the received random access setting information. The terminal device 1 receives one or more SS / PBCH blocks in the SS burst set, receives random access setting information associated with one SS / PBCH block in the SS burst set, and receives the received random access setting. A random access procedure may be performed based on the information. The terminal device 1 receives one or more CSI-RSs, receives random access setting information associated with one CSI-RS therein, and performs a random access procedure based on the received random access setting information. May be performed.

  The one or more random access setting information may be configured with one random access channel setting (RACH-Config) and / or one physical random access channel setting (PRACH-Config).

  Parameters related to random access for each reference signal may be included in the random access channel setting.

  Parameters related to the physical random access channel for each reference signal (PRACH setting index, PRACH opportunity, etc.) may be included in the physical random access channel setting.

  One piece of random access setting information may indicate a parameter related to random access corresponding to one reference signal, and a plurality of pieces of random access setting information may indicate a parameter related to a plurality of random access corresponding to a plurality of reference signals.

  One piece of random access setting information indicates a parameter related to physical random access corresponding to one reference signal, and may indicate a parameter related to a plurality of random access corresponding to a plurality of reference signals.

  If the corresponding reference signal is selected, random access setting information (random access channel setting corresponding to the reference signal, physical random access channel setting corresponding to the reference signal) corresponding to the reference signal may be selected. .

  However, the terminal device 1 receives one or a plurality of pieces of random access setting information from the base station device 3 and / or the transmission / reception point 4 different from the base station device 3 and / or the transmission / reception point 4 transmitting the random access preamble. Good. For example, the terminal device 1 may transmit the random access preamble to the second base station device 3 based on at least one of the random access setting information received from the first base station device 3.

However, the base station device 3 may determine the downlink transmission beam to be applied when transmitting the downlink signal to the terminal device 1, by receiving the random access preamble transmitted by the terminal device 1. The terminal device 1 may transmit the random access preamble using the PRACH opportunity indicated by the random access setting information associated with a certain downlink transmission beam. The base station device 3 should apply when transmitting a downlink signal to the terminal device 1 based on the random access preamble received from the terminal device 1 and / or the PRACH opportunity receiving the random access preamble. The link transmit beam may be determined.

  The base station device 3 transmits, to the terminal device 1, RRC parameters including one or more pieces of random access setting information (which may include random access resources) as an RRC message.

  The terminal device 1 determines one or more available random access preambles and / or one or more available PRACH opportunities to be used for the random access procedure based on the channel characteristics with the base station device 3. You may choose. The terminal device 1 is based on the channel characteristic (for example, reference signal reception power (RSRP)) measured by the reference signal (for example, SS / PBCH block and / or CSI-RS) received from the base station device 3. May select one or more available random access preambles and / or one or more PRACH opportunities to use for the random access procedure.

  Hereinafter, in the present embodiment, uplink resource allocation in the frequency direction will be described.

  For PUSCH transmissions scheduled by the RAR UL grant and excluding PUSCH transmissions, the terminal device 1 determines the resource block assignment (resource assignment) in the frequency direction using the resource allocation field included in the detected PDCCH DCI. May be. In this embodiment, uplink resource allocation types 0 and 1 are supported. The terminal device 1 may assume that the uplink resource allocation type 1 is used when receiving the PDCCH with the DCI format 0_0 that schedules the PUSCH.

  When detecting the PDCCH for the terminal device 1, the terminal device 1 first decides the UL BWP to which the resource assignment is applied, and then decides the resource allocation in the decided UL BWP. The resource block numbering (RB numbering) of the resource allocation starts from the lowest RB of its established UL BWP. That is, the UL BWP to which the resource assignment is applied is the UL BWP determined by the terminal device 1. The UL BWP determined by the terminal device 1 is a BWP on which uplink transmission (PUSCH transmission) is performed.

Specifically, when the BWP indicator field (bandwidth part indicator field) is not set in the DCI format (scheduling DCI), or when the terminal device 1 does not support active BWP change via the DCI format, resource allocation is performed. The RB numbering (RB indexing) of (uplink resource allocation type 0 and type 1) is determined in the active BWP of the terminal device 1. That is, in this case, the UL BWP determined by the terminal device 1 may be an active BWP. That is, the UL BWP to which the resource assignment is applied may be an active BWP (active UL BWP). If the BWP indicator field (bandwidth part indicator field) is set in the DCI format (scheduling DCI) and / or the terminal device 1 supports active BWP changes via the DCI format, RB numbering of resource allocation (RB indexing) may be determined within the BWP indicated in the BWP indication field. That is, in this case, the UL BWP determined by the terminal device 1 may be the BWP indicated in the BWP instruction field. That is, the UL BWP to which the resource assignment is applied may be the BWP indicated in the BWP indication field. DCI format 0_0 does not include a BWP indication field.

In the uplink resource allocation type 0 (uplink resource allocation type 0, uplink type 0 resource allocation), the resource block assignment information includes resource block groups (RBGs, Resource Block Groups) allocated to the terminal device 1.
) Is included in the bitmap. A resource block group is a set of continuous virtual resource blocks and may be defined from upper layer parameters.

In the uplink resource allocation type 1 (uplink resource allocation type 1), the resource block assignment information is continuous with respect to the scheduled terminal device 1 within the active _BWP of size N ^size _BWP. 3 illustrates a set of non-interleaved virtual resource blocks that are dynamically allocated. Here, the size N ^size _BWP is the number of resource blocks indicating the bandwidth of the active UL BWP. However, if DCI format 0_0 is detected in any common search space set, the size bandwidth N ^size _{BWP, 0 of} the initial UL BWP is used. That is, in this case, the resource block assignment information indicates a set of non-interleaved virtual resource blocks continuously allocated to the scheduled terminal device 1 within the initial UL BWP of size N ^size _{BWP, 0} .

The uplink type 1 resource assignment field is a resource indication value (RIV, Resource Indication Value) corresponding to a start resource block (RB _start, start virtual resource block) and the number of resource blocks (L _RBs ) continuously allocated. Consists of. That is, the resource instruction value RIV is indicated in the resource assignment field. RB _start indicates the start position of the allocated resource block. L _RBs indicates the number (length, size) of resource blocks of continuously allocated resources. The base station device 3 determines the resource allocation in the UL BWP determined by the terminal device 1, generates the RIV, and transmits the resource assignment including the bit string indicating the RIV to the terminal device 1. The terminal device 1 specifies the resource block allocation in the frequency direction of the determined UL BWP (of the PUSCH) based on the bit string of the resource assignment field.

  FIG. 12 is a diagram illustrating an example of calculating RIV.

In FIG. 12A, N ^size _BWP is the number of resource blocks indicating the bandwidth of the active UL BWP. The value of RIV is calculated based on the size N ^size _BWP of the active UL BWP, the start position RB _start of the virtual resource block, and the number L _{RBs of} resource blocks continuously allocated. Here, the value of L _RBs is equal to or greater than 1 and does not exceed (N ^size _BWP- RB _start ). However, as described above, when the DCI format 0_0 is detected in an arbitrary common search space set (for example, the type 1 PDCCH common search space set), the ^size of the initial UL BWP for the N ^size _BWP in FIG. The number of resource blocks indicating the bandwidth, N ^size _{BWP, 0} is used. However, as described above, when the DCI format 0_0 is detected in any of the common search space set, initial UL size BWP bandwidth ^N _{size BWP, 0} is used to ^N _{size BWP} in FIG 12 (A). Here, the value of L _RBs is equal to or greater than 1 and does not exceed (N ^size _{BWP, 0-} RB _start ).

In FIG. 12B, N ^initial _BWP is the number of resource blocks indicating the bandwidth of the initial BWP (UL BWP). N ^active _BWP is the number of resource blocks indicating the bandwidth of an active BWP (UL BWP). That is, the N ^initial _BWP is the size of the initial BWP (UL BWP). N ^active _BWP is the size of the active BWP (UL BWP). The value of RIV is calculated based on the size N ^initial _{BWP of} the ^initial UL BWP, the start position RB ′ _{start of} the resource block, and the number L ′ _RBs of resource blocks continuously allocated. The multiplication of RB _'start and the coefficient K is _{RB start.} The multiplication of L'RBs and the coefficient K is L _RBs . The value of the coefficient K is calculated based on the size of the initial UL BWP and the size of the active BWP. If N ^active _BWP is greater than N ^initial _BWP , the value of K is the largest value in the set {1, 2, 4, 8} that satisfies K <= Floor (N ^active _BWP / N ^initial _BWP ). Here, the function Floor (A) outputs the largest integer that does not exceed A. The value of K is 1 if the N ^active _BWP is equal to or less than the N ^initial _BWP . As a result, the resource to be allocated is specified by the start position RB _{start of} the resource block and the number of resource blocks L _{RBs that} are continuously allocated.

  In the resource identification method of FIG. 12B, the size of the DCI format in USS (or the size of the frequency domain resource assignment field included in the DCI format) is derived by the initial BWP, but is applied to the active BWP. It may be used in the case. The DCI format may be DCI format 0_0 and / or DCI format 0_1.

  FIG. 11 is a diagram showing an example for explaining uplink resource allocation type 1 for BWP.

In FIG. 11, one initial UL BWP (1101) and two additional UL BWPs (1102 and 1103) are set for the terminal device 1. As described above, the common resource block n _PRB is a resource block numbered in ascending order from 0 in each subcarrier interval setting μ from the point A. That is, 1114 is a common resource block (common resource block 0) to which the number 0 is attached. In the subcarrier interval setting μ, the center of the subcarrier index 0 of the common resource block 0 (common resource block index 0, n _CRB # 0) coincides with the point A. 1104 is the start position of the carrier in the subcarrier interval setting μ and is given from the upper layer parameter OffsetToCarrier. That is, the upper layer parameter OffsetToCarrier is an offset in the frequency domain between the point A and the lowest usable subcarrier of the carrier. The offset (1115) indicates the number of resource blocks in the subcarrier interval setting μ. That is, when the subcarrier interval setting μ is different, the band of the frequency region of the offset is different. In the subcarrier interval setting μ, 1104 may be the position of the resource block where the carrier starts. The physical resource blocks are resource blocks numbered in ascending order from 0 for each BWP. In the subcarrier interval setting μ of each BWP index i, the relationship between the physical resource block n _PRB and the common resource block n _CRB at that BWP index i is given by (Equation 3) n _CRB = n _PRB + N ^start _{BWP, i} . In the subcarrier interval setting μ of each BWP, N ^start _{BWP, i} is the number of common resource blocks starting with the BWP index i for the common resource block index 0. N ^size _{BWP, i} is the number of resource blocks indicating the BWP bandwidth of index i in the subcarrier interval setting μ of BWP index i.

The position and bandwidth of the BWP in the frequency domain are given by the upper layer parameter locationAndBandwidth. Specifically, the number of physical resource blocks continuous with the first physical resource block (physical resource block index 0) of the BWP index i is given by the upper layer parameter locationAndBandwidth. The value indicated by the parameter locationAndBandwidth of the upper layer is interpreted as the RIV value for the carrier. As shown in FIG. 12A, N ^size _BWP is set to 275. RB _start and L _RBs identified by the value of RIV indicate the number of consecutive physical resource blocks indicating the first physical resource block (physical resource block index 0) of BWP and the bandwidth of BWP. The first physical resource block of the BWP index i is the physical resource block offset with respect to the physical resource block (1104) indicated by the upper layer parameter OffsetToCarrier. The number of resource blocks indicating the bandwidth of the BWP index i is N ^size _{BWP, i} . ^N _{start BWP, i} of BWP index i is given from the offset indicated by the parameter OffsetToCarrier of the first physical resource block and the upper layer of the BWP index i.

That is, in FIG. 11, 1105 is the physical resource block index 0 (n _PRB # 0) in the UL BWP # 0 (1101) in the sub carrier interval setting μ of the UL BWP # 0. The relationship between the physical resource block and the common resource block in UL BWP # 0 is given by n _CRB = n _PRB + N ^start _{BWP, 0} . In the sub carrier interval setting μ of UL BWP # 0, N ^start _{BWP, 0} (1107) is a common resource block started by UL BWP # 0 for common resource block index 0. N ^size _{BWP, 0} (1106) is the number of resource blocks indicating the bandwidth of UL BWP # 0 in the subcarrier interval setting μ of UL BWP # 0.

In FIG. 11, 1108 is the physical resource block index 0 (n _PRB # 0) in UL BWP # 1 (1102) in the sub carrier interval setting μ of UL BWP # 1. The relationship between physical resource blocks and common resource blocks in UL BWP # 1 is given by n _CRB = n _PRB + N ^start _{BWP, 1} . In the subcarrier interval setting μ of UL BWP # 1, N ^start _{BWP, 1} (1110) is a common resource block started by UL BWP # 1 for common resource block index 0. N ^size _{BWP, 1} (1109) is the number of resource blocks indicating the bandwidth of UL BWP # 0 in the subcarrier interval setting μ of UL BWP # 1.

In FIG. 11, in the subcarrier interval setting μ of UL BWP # 2, 1111 is the physical resource block index 0 (n _PRB # 0) in UL BWP # 2 (1102). The relationship between physical resource blocks and common resource blocks in UL BWP # 2 is given by n _CRB = n _PRB + N ^start _{BWP, 2} . In the subcarrier interval setting μ of UL BWP # 2, N ^start _{BWP, 2} (1113) is a common resource block started by UL BWP # 2 for common resource block index 0. N ^size _{BWP, 2} (1112) is the number of resource blocks indicating the bandwidth of UL BWP # 2 in the subcarrier interval setting μ of UL BWP # 2.

As seen from FIG. 11, the start position (starting common resource block, N ^start _BWP ) and the number of resource blocks (N ^size _BWP ) are different for each BWP set in the terminal device 1. RB numbering of resource allocations starts with the lowest RB of the established UL BWP. For example, even if the calculated RB _start value is the same, if the lowest RB of the determined UL BWP is different, the position of the common resource block to start is also different.

  FIG. 8: is a figure which shows an example of the random access procedure of the terminal device 1 in this embodiment.

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

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

  In the case of the non-contention based random access procedure, the terminal device 1 selects the index of the random access preamble 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 device 3 are 0, the terminal device 1 executes the contention-based random access procedure, and the terminal device 1 itself selects the index of the random access preamble.

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

The random access response may be referred to as Message 2 or Msg2. In addition, the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble and a RAR message (MAC RAR) corresponding to the identifier in the message 2. The base station device 3 calculates a transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and transmits transmission timing adjustment information (TA command, Timing Advance Command) for adjusting the shift. ) Is included in the RAR message. The RAR message includes 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 a 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. Also, the base station device 3 includes a random access preamble identifier corresponding to the received random access preamble in the message 2.

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

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

  (I) When the terminal device 1 does not detect the DCI format 1_0 to which the CRC scrambled by RA-RNTI is added within the window period, or (ii) the terminal device 1 DL-on the PDSCH 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 device 1 considers that the non-contention based random access procedure has been successfully completed, and transmits the PUSCH based on the uplink grant included in the random access response.
If the received random access response includes a random access preamble identifier corresponding to the transmitted random access preamble and the terminal device 1 itself selects the random access preamble, TC-RNTI is included in the received random access response. The value of the TC-RNTI field is set, and the random access message 3 is transmitted by PUSCH based on the uplink grant included in the random access response. The PUSCH corresponding to the uplink grant included in the random access response is transmitted in the serving cell in which the corresponding preamble is transmitted on the PRACH.

RAR UL grant is used for PUSCH transmission (or RAR PU
SCH) used for scheduling. PUSCH (or PUSCH transmission) scheduled by RAR UL grant to RAR PUSCH (or RAR
PUSCH transmission). That is, the RAR PUSCH transmission is the 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 contention-based random access procedure, the terminal device 1 transmits Msg3 (message 3) based on the RAR UL grant. That is, in the contention based random access procedure, the Msg3 PUSCH (Msg3 PUSCH transmission) is scheduled by the RAR UL grant. Msg3 may be the first scheduled transmission of the contention based random access procedure (PUSCH transmission). Msg3 is a message containing a C-RNTI MAC CE or CCCH SDU as part of the contention based random access procedure, which may be transmitted on the UL-SCH. In the contention based random access procedure, the RAR PUSCH transmission may be Msg3 PUSCH transmission. In the non-contention based random access procedure, the terminal device 1 may transmit the PUSCH (RAR PUSCH) based on the RAR UL grant. That is, in the non-contention based random access procedure, R
The PUSCH scheduled by the AR UL grant may not be referred to as Msg3 PUSCH. Also, in the non-contention based random access procedure, the PUSCH scheduled by the RAR UL grant may be referred to as Non-Msg3 PUSCH. That is, in the non-contention based random access procedure, the Non-Msg3 PUSCH may be the PUSCH scheduled by the RAR UL grant.

  Further, in the present embodiment, the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the contention based random access procedure. Also, the Msg3 PUSCH may include the PUSCH scheduled by the RAR UL grant in the contention-based random access procedure. The Msg3 PUSCH may be the first scheduled uplink transmission in the random access procedure (PUSCH transmission, first scheduled transmission). That is, the Msg3 PUSCH may be a PUSCH scheduled by the RAR UL grant regardless of the type of random access procedure (contention based random access procedure or non-contention based random access procedure). Then, in the contention based random access procedure, the retransmission of the Msg3 PUSCH may be scheduled by the DCI format 0_0 with the CRC parity bit scrambled by the TC-RNTI added. In the non-contention based random access procedure, the retransmission of the Msg3 PUSCH may be scheduled by the DCI format 0_0 with the CRC parity bit scrambled by the C-RNTI.

The '(Msg3) PUSCH time resource allocation' field is used to indicate time domain resource allocation for PUSCH scheduled by the RAR UL grant.
The'MCS 'field is used to determine the MCS index for the PUSCH scheduled by the RAR UL grant.
The'TPC command for scheduled PUSCH 'field is used for setting the transmission power of the PUSCH scheduled by the RAR UL grant.
In the contention based random access procedure, the'CSI request 'field is reserved. In the non-contention based random access procedure, the'CSI request 'field is used to determine whether an aperiodic CSI report is included in the PUSCH transmission.

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

  FIG. 7 is a diagram showing an example of frequency hopping in the present embodiment. FIG. 7A is an example of PUSCH transmission without frequency hopping. FIG. 7B is an example of PUSCH transmission accompanied by intra-slot frequency hopping. FIG. 7C is an example of PUSCH transmission with inter-slot frequency hopping.

In FIG. 7 (b), PUSCH transmission with intra-slot frequency hopping is performed in a slot with a first frequency hop (first frequency hop, first hop, first frequency unit) and a second frequency hop (second frequency hop). hop, first hop, second frequency unit). The number of symbols for the first frequency hop may be given by Floor (N ^{PUSCH, s} _symb / 2). The number of symbols for the second frequency hop may be given by N ^{PUSCH, s} _symb -Floor (N ^{PUSCH, s} _symb / 2). N ^{PUSCH, s} _symb is the length of PUSCH transmission in OFDM symbols in one slot. That is, N ^{PUSCH, s} _symb may be the number of OFDM symbols used for the scheduled PUSCH in one slot. The value of N ^{PUSCH, s} _symb may be indicated in a field included in the DCI format or RAR UL grant. First frequency hop start RB (starting RB) and first frequency hop start R
The resource block difference RB _offset between B may be referred to as a resource block frequency offset. That is, RB _offset is the frequency offset of RB between two frequency hops. Also, the RB _offset may be referred to as a frequency offset for the second frequency hop. For example, the first
The start RB of the frequency hop of is called RB _start . The starting RB of the second frequency hop is (
Equation 5) (RB _{start +} RB _offset ) may be given by modN ^size _BWP . The RB _start may be given by the frequency resource allocation field. The function (A) mod (B) divides A and B, and outputs the undivisible remainder. In FIG. 7 (b), intra-slot frequency hopping may be applied to single-slot PUSCH transmission and / or multi-slot PUSCH transmission.

In FIG. 7C, frequency hopping between slots may be applied to multi-slot PUSCH transmission. RB _offset is the frequency offset of RB between two frequency hops.

Hereinafter, the interpretation of the '(Msg3) PUSCH frequency resource allocation' field will be described. This field is used for resource allocation for PUSCH transmissions scheduled by RAR UL grant. '(Msg3) PUSCH frequency resource allocation' (PUSCH frequency resource assignment, Msg3 PUSCH frequency resource assignment, PUSCH frequency resource assignment) field is a fixed size resource block assignment (fixed size resource block assignment), or RAR PUSCH frequency resource RAR PUSCH frequency resource allocation
). The PUSCH frequency resource allocation field (or frequency resource assignment field) has a fixed number of bits regardless of the UL BWP bandwidth set for the terminal device 1. The terminal device 1 processes the frequency resource allocation field based on the size N ^size _BWP of the active UL BWP. That is, the terminal device 1 truncates or inserts bits in PUSCH frequency resource allocation based on the size of the active UL BWP (N ^size _BWP ). Then, the terminal device 1 can adapt to the bandwidth of the UL BWP to which the resource allocation is applied by truncating or inserting bits in the PUSCH frequency resource allocation.

  FIG. 10 is a diagram showing an example of interpretation of the'PUSCH frequency resource allocation 'field according to the present embodiment.

Reference numeral 1001 in FIG. 10A is a fixed'PUSCH frequency resource allocation 'field having 14 bits. 1002 is a N _{UL, hop} hopping bit. Reference numeral 1003 denotes the bits remaining after removing the N _{UL, hop} hopping bits from 1001 and is (14−N _{UL, hop} ) bits. That is, 1
The 4-bit 1001 is composed of 1002 and 1003. The number of N _{UL, hop} hopping bits is given based on the value indicated in the'Frequency hopping flag 'field and / or the bandwidth of N ^size _BWP . For example, the number of bits in the N _{UL, hop} example may be 1 bit when the size of the N ^size _BWP is smaller than the value of the predetermined number of resource blocks. The number of bits in _{NUL, hop} example is
It may be 2 bits when the size of the N ^size _BWP is equal to or larger than the value of the predetermined number of resource blocks. The value of the predetermined number of resource blocks may be 50. A description of N ^size _BWP will be given later.

As described above, when the value of the frequency hopping flag (Frequency hopping flag) is 0, the N _{UL, hop} hopping bit is 0 bit. In this case, 1003 is 1001
And has 14 bits. When the value of the frequency hopping flag (Frequency hopping flag) is 1, does the number of bits of N _{UL, hop} hopping bits exceed the value Y (for example, 50) of the predetermined number of resource blocks for the value of N ^size _BWP ? It may be given to 1 bit or 2 bits depending on whether or not. For example, when N ^size _BWP is smaller than the value Y of a predetermined number of resource blocks, N _{UL, hop} hopping bits may be given to 1 bit. If N ^size _BWP is equal to or greater than the value Y of a given number of resource blocks, then N _{UL, hop} hopping bits may be given to 2 bits. That is,
1003 has 12 bits or 13 bits.

FIG. 10B is a diagram illustrating an example of truncating the bits of the'PUSCH frequency resource allocation 'field when N ^size _BWP is smaller than or equal to a predetermined resource block number value of 180.

In FIG. 10B, the terminal device 1 truncates the bits of PUSCH frequency resource allocation from the least significant bit (LSB) to b bits when N ^size _BWP is smaller than or equal to the value X of the predetermined number of resource blocks. That is, b bits is the number of truncated bits. The value of b is calculated by (Equation 1) b = Ceiling (log ₂ (N ^size _BWP (N ^size _BWP +1) / 2)). Here, the function Ceiling (A) outputs the smallest integer not less than A. The truncated PUSCH frequency resource allocation may be referred to as the truncated frequency resource allocation field. The terminal device 1 may interpret the truncated frequency resource allocation field according to the rule for the frequency resource allocation field included in the DCI format 0_0.

In FIG. 10B, 1004 is a PUSCH frequency resource allocation having 14 bits. 1005 is a _{NUL, hop} hopping bit. 1006 is PUSCH
Bits other than N _{UL, hop} hopping bits in the frequency resource allocation. 1
008 is the resource block allocation to be truncated. The number of bits of 1008 is b bits. The number of bits of 1007 is 14-b.

FIG. 10C is a diagram illustrating an example of inserting a bit in the'PUSCH frequency resource allocation 'field when the bandwidth of the N ^size _BWP is larger than the predetermined resource block value of 180.

In FIG. 10C, 1009 is PUSCH frequency resource allocation having 14 bits. Reference _numeral 1010 is a _{NUL, hop} hopping bit. 1012 is PUSCH
It is the remaining bits except N _{UL, hop} hopping bits from frequency resource allocation. The number of bits of 1012 is (14-N _{UL, hop} ) bits. The terminal device 1 is N
^{If the size} _BWP is larger than the value X of the predetermined number of resource blocks, set to a value of '0' after the N _{UL, hop} hopping bits in the PUSCH frequency resource allocation b
Insert the most significant bits (MSB). That is, b bits is the number of bits to be inserted. The value of b is calculated by (Equation 2) b = (Ceiling (log ₂ (N ^size _BWP (N ^size _BWP +1) / 2))-Z). The value of Z may be 14. The PUSCH frequency resource allocation in which b bits are inserted may be referred to as an extended resource block allocation field. The terminal device 1 may interpret the extended frequency resource allocation field according to the rule for the frequency resource allocation field (frequency domain resource assignment) included in the DCI format 0_0. In FIG. 10C, the number of bits of 1011 is b bits. Reference numeral 1009 denotes expanded frequency resource allocation. The number of bits of 1009 is the sum of 14 bits and b bits of PUSCH frequency resource allocation.

This is one aspect A of this embodiment, and in FIG. 10, N ^size _BWP is an active UL.
It may be of BWP size. One initial BWP including at least one DL BWP and one UL BWP is set for the terminal device 1. Furthermore, up to four additional BWPs are set for the terminal device 1. The size of each UL BWP set for the terminal device 1 may be different. As mentioned above, there is always one active (activated) BWP in an activated serving cell. For example, if the active UL BWP is the initial UL BWP, then N ^size _BWP is the ^size of the initial UL BWP. If the active UL BWP is an additional UL BWP, then N ^size _BWP is the ^size of the activated additional UL BWP. The size of UL BWP is the number of resource blocks indicating the bandwidth of the corresponding UL BWP. When specifying the resource allocation, the terminal device 1 first determines the UL BWP to which the resource allocation is applied, and then determines the resource allocation in the confirmed UL BWP.

In FIG. 10, the terminal device 1 determines to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N ^size _BWP of the active UL BWP. However, in the contention-based random access procedure, the terminal device 1 decides to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N ^size _{BWP, 0} of the initial UL BWP. May be. That is, in the contention-based random access procedure, the terminal device 1 performs frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission in the active UL BWP based on the following conditions 1 and 2. You may decide. The frequency domain resource allocation may be determined within the active UL BWP. Retransmission of Msg3 PUSCH means retransmission of transport block in Msg3 PUSCH. The retransmission of the transport block in the Msg3 PUSCH may be scheduled by the DCI format 0_0 with the CRC scrambled by the TC-RNTI shown in the RAR message. That is, in the contention-based random access procedure, the PUSCH retransmission of the transport block transmitted on the PUSCH corresponding to the RAR UL grant included in the RAR message is a DCI format to which a CRC parity bit scrambled by TC-RNTI is added. Scheduled by 0_0. The DCI format 0_0 is transmitted on the PDCCH of the type 1 PDCCH common search space set. The initial UL BWP and the active UL BWP in the following Condition 1 and Condition 2 correspond to the same uplink carrier of the same serving cell. The uplink carrier may be an uplink carrier on which PRACH transmission and Msg3 PUSCH transmission are performed.

The terminal device 1 (condition 1) has an active UL BWP having an active UL BWP and an initial UL BWP having the same subcarrier interval and the same CP (Cyclic Prefix) length, and is active UL BW.
If P includes all resource blocks of the initial UL BWP, or (condition 2) the active UL BWP is the initial UL BWP, then the initial UL BWP is used and Msg3 PUSCH transmission and / or in the active UL BWP is used. Determine frequency resource allocation for Msg3 PUSCH retransmission. That is, the value of RIV shown in the Msg3 PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the number of resource blocks to be continuously allocated L _RBs. Given based on. That is, the RIV value shown in the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L _RBs that are allocated. In Msg3 PUSCH transmission or Msg3 PUSCH retransmission, if either or both of (Condition 1) and (Condition 2) are satisfied, the N ^size _BWP used to calculate the frequency offset set for the second hop is , May be the size of the initial UL BWP. That is, in this case, in FIG. 17, the N ^size _BWP may be the size of the initial UL BWP.

In other words, for frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission, the terminal device 1 is (condition 1) active UL BWP and initial UL BWP are the same subcarriers. It has the same CP (Cyclic Prefix) length as the interval and the active UL BWP includes all resource blocks of the initial UL BWP, or (condition 2) the active UL BWP is the initial UL BWP. In some cases, the initial UL BWP is determined, and the resource allocation in the frequency direction within the determined initial UL BWP is determined. Resource block numbering for resource allocation is determined by the initial UL
Start with the lowest RB of BWP. That is, when calculating the RIV using FIG. 12A, the terminal device 1 uses the size bandwidth N ^size _{BWP, 0} of the initial UL BWP as the N ^size _BWP in FIG. 12A. The RB numbering of frequency resource allocation for Msg3 PUSCH transmission or Msg3 PUSCH retransmission may start from the lowest RB (first RB, lowest RB) of the initial UL BWP. Here, Msg3 PUSCH transmission or Msg3 PUSCH retransmission is performed in the active UL BWP. Active UL
If the BWP is the initial UL BWP, the Msg3 PUSCH transmission is done on the initial UL BWP (the activated initial UL BWP). If the active UL BWP is not the initial UL BWP, the Msg3 PUSCH transmission is done on the active UL BWP.

In the case where both the condition 1 and the condition 2 are not satisfied, the terminal device 1 determines that the maximum number of resource blocks for frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission is the resource block of the initial UL BWP. It may be determined that the RB numbering equals the number and starts with the lowest RB (first RB, lowest RB) of the active UL BWP. At this time, the RIV value shown in the Msg3 PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the number L of resource blocks continuously allocated. Given based on _RBs . That is, the RIV value shown in the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L _RBs that are allocated. However, the RB numbering may start from the lowest RB (first RB, lowest RB) of the active UL BWP. In Msg3 PUSCH transmission or Msg3 PUSCH retransmission, if both (Condition 1) and (Condition 2) are not satisfied, the N ^size _BWP used for calculating the frequency offset set for the second hop is the active UL BWP. It may be the size. That is, in this case, in FIG. 17, the N ^size _BWP may be the size of the active UL BWP. Further, in the Msg3 PUSCH transmission or the Msg3 PUSCH retransmission, if both (condition 1) and (condition 2) are not satisfied, the N ^size _BWP used for calculation of the frequency offset set for the second hop is the initial UL BWP. Can be any size. That is, in this case, in FIG. 17, the N ^size _BWP may be the size of the initial UL BWP.

For frequency domain resource allocation for Msg3 PUSCH transmission and / or Msg3 PUSCH retransmission, the terminal device 1 determines and determines the active UL BWP if both Condition 1 and Condition 2 are not met. Determine resource allocation in the frequency direction within the active UL BWP. The resource block numbering of frequency resource allocation for Msg3 PUSCH transmission or Msg3 PUSCH retransmission starts from the lowest RB of the established active UL BWP. However, the terminal device 1 uses the size bandwidth N ^size _{BWP, 0} of the initial UL BWP for the N ^size _BWP in FIG. 12A when calculating the RIV using FIG. 12A. Here, Msg3 PUSCH transmission or Msg3 PUSCH retransmission is performed in the active UL BWP. If the active UL BWP is the initial UL BWP, the Msg3 PUSCH transmission is done on the initial UL BWP (the activated initial UL BWP). If the active UL BWP is not the initial UL BWP, the Msg3 PUSCH transmission is done on the active UL BWP.

As described above, when the value of the frequency hopping flag is set to 1, the number of N _{UL, hop} hopping bits exceeds the value Y of the predetermined number of resource blocks when the value of N ^size _BWP exceeds Y. It may be given to 1 bit or 2 bits depending on whether it is present or not. In Msg3 PUSCH transmission or Msg3 PUSCH retransmission, the number of N _{UL, hop} hopping bits is 1 bit or 2 bits based on whether the size of the initial UL BWP exceeds the value Y of the predetermined resource block number. May be given to. In Msg3 PUSCH transmission, the bits of N _{UL, hop} hopping bits may be included in the PUSCH frequency resource allocation field included in the RAR UL grant. In retransmission of Msg3 PUSCH, the bits of N _{UL, hop} hopping bits may be included in the frequency domain resource allocation field included in DCI format 0_0. In Msg3 PUSCH transmission or Msg3 PUSCH retransmission, the value of the frequency offset for the second hop may be given by FIG. FIG. 17 is a diagram illustrating a second hop frequency offset for PUSCH scheduled by a RAR UL grant with frequency hopping in the present embodiment. That is, in Msg3 PUSCH transmission or Msg3 PUSCH retransmission, N ^size _BWP in FIG. 17 may be the size of the initial UL BWP (N ^size _{BWP, 0} ). Specifically, in Msg3 PUSCH transmission or Msg3 PUSCH retransmission, the value of the frequency offset for the second hop is the size of the initial UL BWP (
N ^size _{BWP, 0} ). Referring to FIG. 17, when the N ^size _BWP is smaller than the value Y of the predetermined number of resource blocks, the N _{UL, hop} hopping bit may be given to 1 bit. The second hop frequency _offset (RB _offset ) for Msg3 PUSCH transmission is Floor (N ^size _BWP / 2) or Floor (N ^size _BWP).
/ 4). If N ^size _BWP is equal to or greater than the value Y of a given number of resource blocks, then N _{UL, hop} hopping bits may be given to 2 bits. The second hop frequency offset for Msg3 PUSCH transmission is Floor (N ^size _BWP / 2), Floor (N ^size _BWP / 4), or -Floor (N ^size _BWP / 4). Here, in FIG. 17, the N ^size _BWP used for the frequency offset of the second hop for Msg3 PUSCH transmission may be the size of the initial UL BWP. Also, the N ^size _BWP used for the second hop frequency offset for Msg3 PUSCH transmission may be the ^size of the active UL BWP.

As described above, the DCI format 0_0 that schedules the retransmission of the Msg3 PUSCH is added with the CRC scrambled by the TC-RNTI. That is, the frequency offset value may be determined based on FIG. 17 for the PUSCH scheduled by the DCI format 0_0 to which the CRC scrambled by TC-RNTI is added. At this time, the N ^size _BWP in FIG. 17 may be the size of the initial UL BWP. For PUSCH scheduled by DCI format 0_0 (or DCI format 0_1) to which CRC scrambled by RNTI other than TC-RNTI (for example, C-RNTI, MCS-C-RNTI, CS-RNTI) is added, The value of the frequency offset is set by an upper layer parameter frequencyHoppingOffsetLists included in PUSCH-Config. The upper layer parameter frequencyHoppingOffsetLists is used to indicate the set of frequency offset (frequency hopping offset) values when frequency hopping is applied. For example, if the size of the active UL BWP is smaller than the predetermined resource block number value 50 PRB, the DCI format may indicate one of two frequency offsets for which upper layer parameters are set. In addition, when the size of the active UL BWP is equal to or larger than the value 50PRB of the predetermined number of resource blocks, the DCI format may indicate one of the four frequency offsets for which upper layer parameters are set. Good. Uplink resource allocation type 1 may be used for the scheduled PUSCH. In this embodiment, frequency hopping may be associated with uplink resource allocation type 1.

In the non-contention based random access procedure, the terminal device 1 determines whether to truncate or insert a bit in the PUSCH frequency resource allocation field based on the size N ^size _BWP of the active UL BWP. Good. That is, in the contention-based random access procedure, the terminal device 1 is based on the size N ^size _BWP of the active UL BWP, and within the active UL BWP, PUSCH transmission scheduled by the RAR UL grant and / or its scheduled PUSCH transmission. PUS
Frequency domain resource allocation for CH retransmissions may be determined. The PUSCH retransmission scheduled by the RAR UL grant means the retransmission of the transport block in the PUSCH scheduled by the RAR UL grant. Re-transmission of the transport block may be scheduled by DCI format 0_0 (or DCI format 0_1) with a CRC that is scrambled by C-RNTI (or MCS-C-RNTI).

In other words, in the contention-based random access procedure, the terminal device 1 responds to the PUSCH transmission scheduled by the RAR UL grant and / or the frequency domain resource allocation for the scheduled retransmission of the PUSCH. , Active UL BWP is determined, and resource allocation in the frequency direction within the determined active UL BWP is determined. The resource block numbering of frequency domain resource allocations for PUSCH transmissions scheduled by RAR UL grants and / or their scheduled PUSCH retransmissions starts from the lowest RB of the established active UL BWP. At this time, the value of RIV shown in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the active UL BWP, the start position RB _start of the virtual resource block, and the number L of resource blocks continuously allocated. Given based on _RBs . Further, the frequency domain resource allocation field included in the DCI format 0_0 that schedules the retransmission of the PUSCH scheduled by the RAR UL grant includes the size of the active UL BWP, the start position RB _start of the virtual resource block, and continuously. It is given based on the number of allocated resource blocks L _RBs . Specifically, the terminal device 1 uses the size N ^size _BWP of the active UL BWP in FIG. 12 (A) when calculating the RIV using FIG. 12 (A).

In addition, in the non-contention based random access procedure, for PUSCH transmission scheduled by RAR UL grant and / or retransmission of the scheduled PUSCH, the number of N _{UL, hop} hopping bits is equal to the number of active UL BWP. It may be given to 1 bit or 2 bits, depending on whether the size exceeds the value Y of the predetermined number of resource blocks. In PUSCH transmission scheduled by the RAR UL grant, the bits of N _{UL, hop} hopping bits may be included in the PUSCH frequency resource allocation field included in the RAR UL grant. In retransmission of PUSCH scheduled by RAR UL grant, N _{UL, hop} hopping bits may be included in the frequency domain resource allocation field included in the DCI format that schedules retransmission. Then, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG. In the non-contention based random access procedure, the N ^size _BWP in FIG. 17 may be the size of the active UL BWP. That is, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH is given by the size of the active UL BWP. Good.

Further, in the non-contention based random access procedure, the frequency offset value may not be determined based on FIG. 17 for the PUSCH scheduled by the RAR UL grant and / or the retransmission of the scheduled PUSCH. . That is, in the contention-based random access procedure, for PUSCH scheduled by the RAR UL grant and / or retransmission of the scheduled PUSCH, the value of the frequency offset is the upper layer parameter frequencyHoppingOffsetLists included in PUSCH-Config. Set by. The upper layer parameter frequencyHoppingOffsetLists is used to indicate the set of frequency offset (frequency hopping offset) values when frequency hopping is applied. For example, if the size of the active UL BWP is smaller than the predetermined resource block number value 50 PRB, the DCI format may indicate one of two frequency offsets for which upper layer parameters are set. In addition, when the size of the active UL BWP is equal to or larger than the value 50PRB of the predetermined number of resource blocks, the DCI format may indicate one of the four frequency offsets for which upper layer parameters are set. Good.

Further, it is the aspect B of the present embodiment, and in FIG. 10, N ^size _BWP may be the size of the initial UL BWP. That is, in FIG. 10, the terminal device 1 determines to truncate or insert a bit in the PUSCH frequency resource allocation field based on the size N ^size _{BWP, 0} of the initial UL BWP. That is, the terminal device 1 truncates or inserts bits into or from the PUSCH frequency resource allocation field based on the size N ^size _{BWP, 0} of the initial UL BWP regardless of the type of the random access procedure. You may decide.

In the present aspect B, also for the non-contention based random access procedure, the terminal device 1 is PUSCH scheduled by the RAR UL grant in the active UL BWP based on the size N ^size _{BWP, 0} of the initial UL BWP. Frequency domain resource allocations for transmission and / or its scheduled PUSCH retransmissions may be determined. That is, in the non-contention based random access procedure, the value of RIV indicated in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the continuous allocation. It is given based on the number of resource blocks L _RBs that are allocated. Specifically, when the terminal device 1 calculates the RIV using FIG. 12A, the size bandwidth of the initial UL BWP with respect to the active UL BWP size N ^size _BWP in FIG. Use N ^size _{BWP, 0} . However, the resource block numbering of frequency domain resource allocations for PUSCH transmissions scheduled by RAR UL grants and / or their scheduled PUSCH retransmissions may start from the lowest RB of a confirmed active UL BWP. Good.

Also, in a non-contention based random access procedure, for PUSCH transmission scheduled by RAR UL grant and / or retransmission of that scheduled PUSCH, the number of N _{UL, hop} hopping bits is the size of the initial UL BWP. May be given to 1 bit or 2 bits depending on whether or not exceeds a predetermined resource block number value Y. Then, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG. In the non-contention based random access procedure, the N ^size _BWP in FIG. 17 may be the size of the initial UL BWP. That is, PUSCH transmission and / or scheduled by RAR UL grant
Or the value of the frequency offset for the second hop for that scheduled PUSCH may be given by the size of the initial UL BWP.

In addition, in the non-contention based random access procedure, for PUSCH transmission scheduled by RAR UL grant and / or retransmission of the scheduled PUSCH, the number of N _{UL, hop} hopping bits is equal to the number of active UL BWP. It may be given to 1 bit or 2 bits, depending on whether the size exceeds the value Y of the predetermined number of resource blocks. Then, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for the scheduled PUSCH may be given by FIG. In the non-contention based random access procedure, the N ^size _BWP in FIG. 17 may be the size of the active UL BWP. That is, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH may be given by the size of the active UL BWP. .

Further, this is the aspect C of the present embodiment, and in FIG. 10, N ^size _BWP may be the size of the active UL BWP. That is, in FIG. 10, the terminal device 1 may decide to truncate or insert a bit into the PUSCH frequency resource allocation field based on the size N ^size _BW of the active UL BWP.

In this aspect B or aspect C, the terminal device 1 irrespective of the type of the random access procedure, the PUSCH and / or the PUSCH scheduled by the RAR UL grant in the active UL BWP based on the condition 1 and the condition 2 described above. Frequency domain resource allocation for the PUSCH retransmission may be determined. The PUSCH retransmission means the retransmission of the transport block in the PUSCH scheduled by the RAR UL grant. Specifically, the retransmission of the transport blocks in the PUSCH is scheduled in the contention based random access procedure even by the DCI format 0_0 with the CRC scrambled by the TC-RNTI indicated in the RAR message. Good. Retransmissions of transport blocks in the PUSCH may be scheduled by DCI format 0_0 with CRC appended by C-RNTI in a non-contention based random access procedure.

Then, the terminal device 1 (condition 1) has the same subcarrier interval and the same CP (Cyclic Prefix) length in the active UL BWP and the initial UL BWP, and the active U BWP
If the L BWP includes all the resource blocks of the initial UL BWP, or (condition 2) the active UL BWP is the initial UL BWP, the initial UL BWP is determined, and within the determined initial UL BWP, Determine resource allocation in the frequency direction. The resource block numbering of resource allocation starts from the lowest RB of the finalized UL BWP. That is, when calculating the RIV using FIG. 12A, the terminal device 1 uses the size bandwidth N ^size _{BWP, 0} of the initial UL BWP as the N ^size _BWP in FIG. 12A. PUSCH and / or its P scheduled by RAR UL Grant
The RB numbering of frequency resource allocation for USCH retransmission may start from the lowest RB (first RB, lowest RB) of the initial UL BWP. In this case, the value of the frequency offset for the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH may be given by the size of the initial UL BWP. . That is, in this case, the N ^size _BWP in FIG. 17 may be the size of the initial UL BWP. Here, the retransmission of the PUSCH and / or its PUSCH scheduled by the RAR UL grant is done in the active UL BWP.

When both the condition 1 and the condition 2 are not satisfied, the terminal device 1 determines that the maximum number of resource blocks of frequency domain resource allocation for retransmission of PUSCH and / or its PUSCH scheduled by the RAR UL grant is the initial UL. It may be determined that the RB numbering is equal to the number of resource blocks of the BWP and that the RB numbering starts from the lowest RB (first RB, lowest RB) of the active UL BWP. At this time, the RIV value indicated in the PUSCH frequency resource allocation field included in the RAR UL grant is the size of the initial UL BWP, the start position RB _start of the virtual resource block, and the number of continuously allocated resource blocks L _RBs. Given based on. That is, the terminal device 1
Uses the size bandwidth N ^size _{BWP, 0} of the initial UL BWP for N ^size _BWP in FIG. 12 (A) when calculating RIV using FIG. 12 (A). However, the RB numbering may start from the lowest RB (first RB, lowest RB) of the active UL BWP. That is, PUSCH and / or its P scheduled by RAR UL grant
For frequency domain resource allocation for USCH retransmission, the terminal device 1 determines the active UL BWP when both the condition 1 and the condition 2 are not satisfied, and determines the frequency within the determined active UL BWP. Determine resource allocation for directions. The resource block numbering of the frequency resource allocations for retransmissions of the PUSCH and / or its PUSCH scheduled by the RAR UL grant starts from the lowest RB of the established active UL BWP. In this case, the PUSCH transmission scheduled by the RAR UL grant and / or the second hop for that scheduled PUSCH.
The value of the frequency offset for) may be given by the size of the active UL BWP. That is, in this case, the N ^size _BWP in FIG. 17 may be the size of the active UL BWP. Also, a PUSCH transmission scheduled by the RAR UL grant and / or a second hop for the scheduled PUSCH.
The value of the frequency offset for the may be given by the size of the initial UL BWP.

When the terminal device 1 receives the PDSCH including the RAR message in the slot n, the terminal device 1 may transmit the PUSCH scheduled by the RAR UL grant in the slot n + k ₂ + a. Here, the value of k ₂ may be indicated by the '(Msg3) PUSCH time resource allocation' field included in the RAR UL grant. a is an additional subcarrier spacing specific slot delay value for the first transmission of the PUSCH scheduled by the RAR UL grant. That is, the value of a corresponds to the subcarrier interval to which the PUSCH scheduled by the RAR UL grant is applied. For example, if the subcarrier spacing to which the PUSCH scheduled by the RAR UL grant is applied is 15 kHz, the value of a may be 2 slots. If the subcarrier spacing is 30 kHz, the value of a may be 3 slots. If the subcarrier spacing is 60 kHz, the value of a may be 4 slots. If the subcarrier spacing is 120 kHz, the value of a may be 6 slots. That is, when the terminal device 1 transmits the PUSCH scheduled by the RAR UL grant, the value of a corresponding to the subcarrier interval of the PUSCH to be transmitted is applied in addition to the k ₂ value.

<Message 3 (S803)>
The terminal device 1 performs PUSCH transmission of the message 3 based on the RAR UL grant included in the RAR message received in S802. The PUSCH corresponding to the transmission of the message 3 is transmitted in the serving cell in which the corresponding preamble is transmitted on the PRACH. Specifically, the PUSCH corresponding to the transmission of message 3 is transmitted in the active UL BWP.

Hereinafter, in the present embodiment, the determination of transform precoding for PUSCH transmission scheduled by the RAR UL grant will be described.

In the present embodiment, “validating” the transform precoding means that in the uplink communication (for example, PUSCH transmission) between the terminal device 1 and the base station device 3, a discrete Fourier transform spread OFDM (DFT-S- OFDM: Discrete Fourier Transform Spread OFDM) may be used. In addition, “disabling” the transform precoding means that in uplink communication (for example, PUSCH transmission) between the terminal device 1 and the base station device 3, an orthogonal frequency including a cyclic prefix (CP: Cyclic Prefix) is included. It may mean that divisional multiplexing (OFDM) is used. Enabling the transform precoding may mean that the transform precoding is applied. Disabling transform precoding may mean that transform precoding does not apply.

In the contention-based random access procedure, in Msg3 PUSCH transmission (and / or Msg3 PUSCH retransmission), the terminal device 1 sets the transform precoding to'valid 'or'invalid' based on the upper layer parameter msg3-transformPrecoding. May be regarded as either of The base station device 3 uses the upper layer parameter msg3-transformPrecoding to indicate to the terminal device 1 whether or not transform precoding is applied to Msg3 PUSCH transmission (and / or Msg3 PUSCH retransmission). Good. When the upper layer parameter msg3-transformPrecoding is set to “valid” (set), the terminal device 1 may regard the transform precoding as “valid”. That is, the terminal device 1 may use discrete Fourier transform spread OFDM for Msg3 PUSCH transmission. Also, the upper layer parameter msg3-transformPrecoding is'
When set to “disabled”, the terminal device 1 may regard the transform precoding as “disabled”. When the upper layer parameter msg3-transformPrecoding is not set (does not exist), the terminal device 1 may regard the transform precoding as'invalid '. That is, the terminal device 1 may use orthogonal frequency division multiplexing for Msg3 PUSCH transmission. The upper layer parameter msg3-transformPrecoding is SIB
1 or from the information element RACH-ConfigCommon.

Hereinafter, a first example of determining transform precoding for PUSCH scheduled by the RAR UL grant in the non-contention based random access procedure will be described.

In the non-contention based random access procedure, for the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant, the terminal device 1 uses the transformer msg3-transformPrecoding of the upper layer to perform the transcoding. Form precoding may be considered either'enabled 'or'disabled'. Specifically, in the non-contention based random access procedure, the terminal device 1 may use the PUSCH (and / or its schedule) scheduled by the RAR UL grant if the upper layer parameter msg3-transformPrecoding is set to'valid '. PUSCH re-transmission) may be considered as'valid 'for transform precoding. In addition, the terminal device 1 disables the transform precoding for the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant when the upper layer parameter msg3-transformPrecoding does not exist. May be regarded as'.

That is, in the first example, with respect to the PUSCH retransmission scheduled by the RAR UL grant, the terminal device 1 based on the upper layer parameter msg3-transformPrecoding, the transform precoding is'enabled 'or'disabled'. 'May be regarded as either. As described above, the retransmission of the PUSCH scheduled by the RAR UL grant may mean the retransmission of the transport block in the PUSCH scheduled by the RAR UL grant. The retransmission may be scheduled by DCI format 0_0 (or DCI format 0_1) with a CRC that is scrambled by C-RNTI (or MCS-C-RNTI). The DCI that schedules the retransmission may be DCI format 0_0 transmitted in CSS. The DCI that schedules the retransmission is DCI format 0 transmitted in USS
It may be _0. The DCI that schedules the retransmission may be DCI format 0_1 transmitted in USS. Further, the DCI format 0_0 that schedules the retransmission may be transmitted in CSS and may not be transmitted in USS. Also, the DCI that schedules the retransmission is DCI format 0_0, and need not be DCI format 0_1.

That is, in the first example, if DCI format 0_1 (and / or DCI format 0_0 transmitted in USS) schedules a PUSCH retransmission (first PUSCH retransmission) scheduled by a RAR UL grant. The terminal device 1 may regard the transform precoding as either “valid” or “invalid” for the retransmission of the first PUSCH based on the parameter msg3-transformPrecoding of the upper layer. If DCI format 0_1 (and / or DCI format 0_0 transmitted in USS) schedules the second PUSCH transmission, the terminal device 1 sets the upper layer parameter transformPrecoder included in PUSCH-Config. If it is present, the transform precoding for the second PUSCH transmission may be considered to be either “valid” or “invalid” according to the upper layer parameter transformPrecoder, or if the upper layer parameter transformPrecoder is not set. In addition, the transform precoding for the second PUSCH transmission may be considered to be either “valid” or “invalid” according to the upper layer parameter msg3-transformPrecoder. The second PUSCH transmission need not be a retransmission of the first PUSCH.

That is, in the present embodiment, the terminal device 1 is configured so that, regardless of whether the random access procedure is the contention-based random access procedure or the non-contention-based random access procedure, the PUSCH (and / or its scheduled) scheduled by the RAR UL grant is used. For PUSCH retransmission), the transform precoding may be considered to be either'valid 'or'invalid' based on the higher layer parameter msg3-transformPrecoding. That is, the terminal device 1 transforms the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant when the upper layer parameter msg3-transformPrecoding is set to'valid '. Precoding may be considered'valid '. In addition, the terminal device 1 disables the transform precoding for the PUSCH (and / or the retransmission of the scheduled PUSCH) scheduled by the RAR UL grant when the upper layer parameter msg3-transformPrecoding does not exist. May be regarded as'.

Hereinafter, a second example of determining transform precoding for PUSCH scheduled by RAR UL grant in the non-contention based random access procedure will be described.

In the non-contention based random access procedure, for PUSCH (initial PUSCH transmission) scheduled by the RAR UL grant, the terminal device 1 sets the transform precoding to'valid 'or based on the upper layer parameter msg3-transformPrecoding. It may be considered as "invalid". In addition, the terminal device 1 performs the first for the PUSCH retransmission (first PUSCH retransmission) scheduled by the RAR UL grant.
It may be determined whether transform precoding is applied based on the DCI format and / or the search space that schedules the PUSCH of the. If the DCI that schedules the retransmission of the first PUSCH is DCI format 0_1 and / or DCI format 0_0 transmitted in USS, the terminal device 1 is configured with the upper layer parameter transformPrecoder included in PUSCH-Config. In this case, according to the upper layer parameter transformPrecoder, the transform precoding for the first PUSCH retransmission may be regarded as either “valid” or “invalid”, and the upper layer parameter transformPrecoder may be If not set, the transform precoding for the first PUSCH retransmission may be considered to be either'valid 'or'invalid' according to the higher layer parameter msg3-transformPrecoder. Further, if the DCI that schedules the retransmission of the first PUSCH is DCI format 0_0 (or DCI format 0_0 transmitted by CSS), the terminal device 1 uses the first layer parameter msg3-transformPrecoding based on the first layer. Transform precoding may be considered to be either'valid 'or'invalid' for the PUSCH retransmissions.

Hereinafter, a third example of determining transform precoding for PUSCH scheduled by RAR UL grant in the non-contention based random access procedure will be described.

For example, in the non-contention based random access procedure, if the upper layer parameter transformPrecoder included in PUSCH-Config is set for the terminal device 1, the terminal device 1 follows the RAR UL according to the upper layer parameter transformPrecoder. Transform precoding for a PUSCH (or retransmission of that PUSCH) scheduled by a grant may be considered either'valid 'or'invalid'. Specifically, when the upper layer parameter transformPrecoding is set to “enabled” (set), the terminal device 1 may regard the transform precoding as “enabled”. That is, the terminal device 1 may use the discrete Fourier transform spread OFDM for the PUSCH transmission. When the upper layer parameter transformPrecoding is set to “invalid” (set), the terminal device 1 may regard the transform precoding as “invalid”. If the upper layer parameter transformPrecoding is not set (does not exist), the terminal device 1 may regard the transform precoding for the PUSCH transmission as'invalid '. That is, the terminal device 1 may use orthogonal frequency division multiplexing for the PUSCH transmission.

Also, for example, in the non-contention based random access procedure, if the upper layer parameter transformPrecoder included in PUSCH-Config is not set for the terminal device 1, the terminal device 1 follows the RAR according to the upper layer parameter msg3-transformPrecoder. Transform precoding for PUSCH (or retransmission of that PUSCH) scheduled by UL grant may be considered as either'valid 'or'invalid'. That is, the upper layer parameter msg3-transformPrecoding is'enabled '(set)
In this case, the terminal device 1 may regard the transform precoding for the PUSCH transmission as'valid '. That is, the terminal device 1 may perform the PUSCH transmission using the discrete Fourier transform spread OFDM. When the upper layer parameter msg3-transformPrecoding is set to “invalid” (set), the terminal device 1 may regard the transform precoding for PUSCH transmission as “invalid”. When the upper layer parameter msg3-transformPrecoding is not set (does not exist), the terminal device 1 may regard the transform precoding for the PUSCH transmission as'invalid '. That is, the terminal device 1 may perform the PUSCH transmission using orthogonal frequency division multiplexing.

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

The DCI format 0_0, which schedules the retransmission of message 3, contains a frequency domain resource assignment field. The bits of the field are given based on the initial UL BWP. Specifically, the number of bits in the field is calculated by (Equation 4) Ceiling (log ₂ (N ^{UL, BWP} _RB (N ^{UL, BWP} _RB +1) / 2)). Where N ^{UL and BWP} _RB are
It is the number of resource blocks indicating the bandwidth of the initial UL BWP. That is, no matter which UL BWP is set for the terminal device 1, which UL BWP is used to schedule the resource for the retransmission of the message 3, the number of bits of the frequency domain resource assignment field is set. Becomes a fixed value (same value) based on the bandwidth of the initial UL BWP.

Also, as an example, N ^{UL, BWP} _RB may be provided based on the type of random access procedure. For example, in the contention-based random access procedure, N ^{UL, BWP} _RB is the number of resource blocks indicating the bandwidth of the initial UL BWP. Also, for example, in a non-contention based random access procedure, N ^{UL, BWP} _RB are active UL
It is the number of resource blocks indicating the bandwidth of BWP.

  The terminal device 1 needs to interpret the bits of the frequency domain resource assignment field based on the initial UL BWP in order to adapt to the bandwidth of the UL BWP to which the frequency domain resource assignment (frequency domain resource assignment field) is applied. There is. As described above, the terminal device 1 determines the UL BWP to which the Msg3 PUSCH frequency resource assignment is applied when truncating or inserting bits in the Msg3 PUSCH frequency resource assignment. Here, the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied may be determined by the same determination method as the UL BWP to which the PUSCH frequency resource assignment is applied as described above. That is, the UL BWP to which the frequency domain resource assignment included in the DCI format 0_0 is applied may be the UL BWP to which the PUSCH frequency resource assignment is applied. That is, the terminal device 1 may specify the resource block allocation in the frequency direction of the PUSCH to the UL BWP to which the PUSCH frequency resource assignment is applied, based on the RIV value indicated in the frequency domain resource assignment field.

For example, if the UL BWP to which the PUSCH frequency resource assignment is applied is the initial UL BWP (or the initial active UL BWP), the UL BWP to which the frequency domain resource assignment field included in the DCI format 0_0 is applied is the initial UL BWP. It is UL BWP. The base station device 3 uses the size of the initial UL BWP to which the resource assignment is applied to generate the RIV, determines the bit string to be included in the field of the frequency resource assignment, and transmits the bit string to the terminal device 1. Then, the terminal device 1 irrespective of which UL BWP the UL BWP actually activated is, the PUSCH of the physical resource block of the UL BWP (initial UL BWP) to which the resource assignment is applied is applied. Identify resource allocation in the frequency direction. The terminal device 1 can specify the RB _start and the L _RBs corresponding to the physical resource block of the initial BWP by using FIG. Here, N ^size _BWP in FIG. 12A is a resource block indicating the bandwidth of the initial UL BWP. That is, the value of RIV indicated in the frequency domain resource assignment field is given based on the size of the initial UL BWP to which the resource assignment is applied, and the RB _start and L _RBs corresponding to the resource block of the initial UL BWP. The RB _start is the number of resource blocks indicating the start position of resource allocation with reference to the physical resource block index 0 of the initial BWP UL. L _RBs cannot exceed the number of resource blocks indicating the bandwidth of the initial UL BWP. That is, the numbering of the resources indicated in the frequency domain resource assignment field starts from the smallest number of physical resource blocks of the initial UL BWP.

<Retransmission of message 3 (S803b)>
When the DCI format 0_0 added with the CRC parity bit scrambled by TC-RNTI is detected in S803a, the terminal device 1 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), the terminal device 1 not indicated by the C-RNTI monitors the DCI format 1_0 that schedules the PDSCH including the UE contention resolution identity. Here, a CRC parity bit scrambled by the corresponding TC-RNTI is added to this DCI format 1_0. In order to respond to the PDSCH reception with the UE collision resolution identity, the terminal device 1 sends HARQ-ACK information on the PUCCH. The transmission of the PUCCH may be performed by the active UL BWP to which the message 3 (Msg 3) is transmitted.

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

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

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

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

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

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

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

The RF unit 12 converts a signal received via the antenna unit 11 into a baseband signal by quadrature 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 converts the converted digital signal into CP (Cyclic
A portion corresponding to Prefix) is removed, and a signal from which CP is removed is subjected to Fast Fourier Transform (FFT) to extract a frequency domain signal.

  The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate an OFDM symbol, adds CP to the generated OFDM symbol, and generates a baseband digital signal to generate a baseband signal. Converts band digital signals to analog signals. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

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

  FIG. 16 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As illustrated, the base station device 3 is configured to include a wireless transmission / reception unit 30 and an upper layer processing unit 34. The wireless transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver 30 is also referred to as a transmitter, a receiver, a monitor, or a physical layer processor. In addition, a control unit that controls the operation of each unit based on various conditions may be separately provided. The upper layer processing unit 34 is also referred to as the control unit 34.

  The upper layer processing unit 34 includes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs some or all of the layers. The upper layer processing unit 34 may have a function of 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 the PRACH opportunity to monitor the random access preamble from at least the SSB index information and the mask index information.

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

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 generates downlink control information (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 receives downlink control information, downlink data (transport block, random access response) arranged in the physical downlink shared channel, system information, RRC message, MAC CE (Control Element), and the like. It is generated or acquired from an upper node and output to the wireless transmission / reception unit 30. Further, the radio resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1. The radio resource control layer processing unit 36 may set various setting information / parameters for each terminal device 1 via a signal of an upper layer. That is, the radio resource control layer processing unit 36 transmits / notifies information indicating various setting information / parameters. The radio resource control layer processing unit 36 may transmit / notify information for specifying the setting of one or more reference signals in a certain cell.

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

The wireless transmission / reception unit 30 has a function of transmitting one or more reference signals. Further, the wireless transmission / reception unit 30 may have a function of receiving a signal including the beam failure recovery request transmitted from the terminal device 1. The wireless transmission / reception unit 30 has one or more PRACHs for the terminal device 1.
It may have a function of transmitting information specifying an opportunity (for example, SSB index information and / or mask index information). The wireless transmission / reception unit 30 may have a function of transmitting information specifying a predetermined index. The wireless transmission / reception unit 30 may have a function of transmitting information specifying the index of the random access preamble. The wireless transmission / reception unit 30 may have a function of monitoring the random access preamble at the PRACH opportunity specified by the upper layer processing unit 34. Other than that, a part of the function of the wireless transmission / reception unit 30 is similar to that of the wireless transmission / reception unit 10, and thus the description thereof is omitted. When the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless 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 between the base station devices 3 or between a higher-level network device (MME, S-GW (Serving-GW)) and the base station device 3 or user data. ) Or receive. In FIG. 16, other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are omitted. It is clear that it has a plurality of blocks that it has as a component. For example, the upper layer processing unit 34 includes a 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 a plurality of reference signals transmitted from the wireless transmission / reception unit 30.

  The “section” in the figure is an element that realizes the function and each procedure of the terminal device 1 and the base station device 3, which is also expressed by terms such as section, circuit, constituent device, device, and unit.

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

  (1) More specifically, the terminal device 1 according to the first aspect of the present invention includes a receiving unit 10 that receives a first parameter of an upper layer and receives a PDSCH including a RAR message, and the RAR message. A transmission unit 10 for transmitting PUSCH with frequency hopping scheduled by the included first UL grant, the first parameter being between a first frequency hop and a second frequency hop in a frequency domain. FIG. 3 shows a set including one or more frequency offset values, wherein the PUSCH with frequency hopping consists of a first frequency hop and a second frequency hop in one slot, and in a contention-based random access procedure, The frequency offset between the first frequency hop and the second frequency hop is the first frequency hop. Given on the basis of the parameter, the contention based random access procedure, the frequency offset between the first frequency hop and the second frequency hops is given based on the size of the initial UL BWP.

(2) The base station device 3 according to the second aspect of the present invention transmits the first parameter of the upper layer and transmits the PDSCH including the RAR message, and the first unit included in the RAR message. A receiver 30 for receiving PUSCH with frequency hopping scheduled by UL grant, wherein the first parameter is one or more between a first frequency hop and a second frequency hop in a frequency domain. The PUSCH with frequency hopping, which shows one set including frequency offset values, consists of a first frequency hop and a second frequency hop in one slot, and in a contention-based random access procedure, the first frequency hop is used. The frequency offset between the hop and the second frequency hop is based on the first parameter. Given can, the contention based random access procedure, the frequency offset between the said first frequency hop second frequency hops, initial UL
Given based on the size of the BWP.

(3) The terminal device 1 according to the third aspect of the present invention receives the first parameter of the upper layer and receives the PDCCH including the DCI format, and the frequency hopping scheduled by the DCI format. A transmitter 30 for transmitting the associated PUSCH, wherein the first parameter comprises a set comprising one or more frequency offset values between a first frequency hop and a second frequency hop in a frequency domain. Shown, said PUSCH with frequency hopping consists of a first frequency hop and a second frequency hop in one slot, and if said DCI format is scrambled by TC-RNTI, said first frequency hop and said first frequency hop. The frequency offset between the two frequency hops is based on the size of the initial UL BWP. When the DCI format is scrambled by an RNTI other than TC-RNTI, the frequency offset between the first frequency hop and the second frequency hop is given based on the first parameter. Here, the DCI format may be DCI format 0_0.

(4) The base station device 3 according to the fourth aspect of the present invention transmits the upper layer first parameter, and transmits the PDCCH including the DCI format, and the frequency hopping scheduled by the DCI format. A receiving unit 30 for receiving a PUSCH with the first parameter, wherein the first parameter comprises one or more frequency offset values between a first frequency hop and a second frequency hop in a frequency domain. , The PUSCH with frequency hopping consists of a first frequency hop and a second frequency hop in one slot, and if the DCI format is scrambled by TC-RNTI, then the first frequency hop and the The frequency offset between the second frequency hops depends on the size of the initial UL BWP. And the DCI format is scrambled by an RNTI other than TC-RNTI, the frequency offset between the first frequency hop and the second frequency hop is given based on the first parameter. Here, the DCI format may be DCI format 0_0.

  (5) In the third and fourth aspects of the present invention, the RNTI other than TC-RNTI may be any of C-RNTI, CS-RNTI, or MCS-C-RNTI.

  (6) The terminal device 1 according to the fifth aspect of the present invention includes the receiving unit 10 that receives the first parameter and the second parameter of the upper layer and receives the PDSCH including the RAR message, and the receiving unit 10 that is included in the RAR message. And a transmitter 10 for transmitting a PUSCH scheduled by a first UL grant, the first parameter for enabling transform precoding for the PUSCH in a contention based random access procedure. And the second parameter is used to indicate UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is When the second parameter is set If the second parameter is set to either'valid 'or'invalid' and the second parameter is not set, either'valid 'or'invalid' is set according to the first parameter. Is set to.

(7) The base station device 3 in the sixth aspect of the present invention transmits the first parameter and the second parameter of the upper layer, and transmits the PDSCH including the RAR message, and the RAR message. A receiving unit 30 for receiving a PUSCH scheduled by the included first UL grant, the first parameter enabling transform precoding for the PUSCH in a contention based random access procedure. And the second parameter is used to indicate a UE-specific selection of transform precoding for PUSCH, and in a non-contention based random access procedure, transform precoding for PUSCH transmission is , When the second parameter is set , "Valid" or "invalid" based on the second parameter, and if the second parameter is not set, either "valid" or "invalid" based on the first parameter. It is set to crab.

  (8) In the fifth and sixth aspects of the present invention, when both the first parameter and the second parameter are not set, the transform precoding for PUSCH transmission is'invalid '. To be

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

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

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

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

  In addition, in the embodiment related to the present invention, the example applied to the communication system including the base station device and the terminal device is described. However, in a system such as D2D (Device to Device) in which terminals communicate with each other. Is also applicable.

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

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

1 (1A, 1B) Terminal device 3 Base station device 4 Transmission / reception point (TRP)
10 Radio Transmission / Reception Section 11 Antenna Section 12 RF Section 13 Baseband Section 14 Upper Layer Processing Section 15 Medium Access Control Layer Processing Section 16 Radio Resource Control Layer Processing Section 30 Radio Transmission / Reception Section 31 Antenna Section 32 RF Section 33 Baseband Section 34 Upper Layer Processor 35 Medium access control layer processor 36 Radio resource control layer processor 50 Transmission unit (TXRU)
51 phase shifter 52 antenna element

Claims (8)

A receiving unit that receives the first parameter and the second parameter of the upper layer, and receives the PDSCH including the RAR message;
A transmitter for transmitting a PUSCH scheduled by the first UL grant included in the RAR message;
Equipped with
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is used to indicate UE specific selection of transform precoding for PUSCH,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. And the second parameter is not set, the terminal device is set to either “valid” or “invalid” based on the first parameter. The terminal device according to claim 1, wherein transform precoding for the PUSCH transmission is made “invalid” when both the first parameter and the second parameter are not set. A transmission unit for transmitting the first parameter and the second parameter of the upper layer and transmitting the PDSCH including the RAR message;
A receiving unit for receiving a PUSCH scheduled by the first UL grant included in the RAR message;
Equipped with
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is used to indicate UE specific selection of transform precoding for PUSCH,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. The base station apparatus is set to either “valid” or “invalid” based on the first parameter when the second parameter is not set. The base station apparatus according to claim 3, wherein transform precoding for the PUSCH transmission is made “invalid” when both the first parameter and the second parameter are not set. A communication method of a terminal device, comprising:
Receiving a first parameter and a second parameter of an upper layer, receiving a PDSCH including a RAR message,
Transmitting a PUSCH scheduled by the first UL grant included in the RAR message,
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is U of transform precoding for PUSCH.
E is used to indicate unique selection,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. And the second parameter is not set, the communication method is set to either “valid” or “invalid” based on the first parameter. A communication method of a base station device, comprising:
Transmitting the upper layer first parameter and the second parameter, transmitting the PDSCH including the RAR message,
Receiving a PUSCH scheduled by the first UL grant included in the RAR message,
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is used to indicate UE specific selection of transform precoding for PUSCH,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. And the second parameter is not set, the communication method is set to either “valid” or “invalid” based on the first parameter. An integrated circuit mounted on a terminal device,
A function of receiving the upper layer first parameter and the second parameter, and receiving the PDSCH including the RAR message;
Causing the terminal device to exert the function of transmitting the PUSCH scheduled by the first UL grant included in the RAR message,
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is used to indicate UE specific selection of transform precoding for PUSCH,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. And the second parameter is not set, the integrated circuit is set to either “valid” or “invalid” based on the first parameter. An integrated circuit mounted on a base station device,
A function of transmitting a first parameter and a second parameter of an upper layer and transmitting a PDSCH including a RAR message;
Causing the base station device to exhibit the function of receiving the PUSCH scheduled by the first UL grant included in the RAR message,
The first parameter is used to enable transform precoding for the PUSCH in a contention based random access procedure,
The second parameter is used to indicate UE specific selection of transform precoding for PUSCH,
In the non-contention based random access procedure, the transform precoding for PUSCH transmission is set to either'valid 'or'invalid' based on the second parameter when the second parameter is set. And the second parameter is not set, the integrated circuit is set to either “valid” or “invalid” based on the first parameter.

Images