WO2020031588A1

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

Info

Publication number: WO2020031588A1
Application number: PCT/JP2019/027107
Authority: WO
Inventors: 麗清劉; 山田　昇平; 高橋　宏樹; 星野　正幸; 秀和坪井
Original assignee: シャープ株式会社
Priority date: 2018-08-07
Filing date: 2019-07-09
Publication date: 2020-02-13
Also published as: JP2020025181A

Abstract

This terminal device and this base station device efficiently perform communications. The terminal device receives a RRCReconfiguraton message, and determines search space configuration information and CORESET configuration information for receiving SIB1. If a first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, and if an active DL BWP includes, in the frequency region, an initial DL BWP bandwidth and an SS block related to the initial DL BWP, and a sub-carrier interval that is the same as the initial DL BWP is used, the terminal device determines searchspace #0 configuration information and CORESET #0 configuration information. The terminal device then acquires SIB1 with the active DL BWP on the basis of the searchspace #0 configuration information and the CORESET #0 configuration information that have been determined. The first parameter is for reconfiguration to synchronize with a target cell SpCell.

Description

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

<< The present invention relates to a base station device, a terminal device, a communication method, and an integrated circuit. This application claims priority based on Japanese Patent Application No. 2018-148467 for which it applied to Japan on August 7, 2018, and uses the content here.

Currently, as the wireless access method and wireless network technology for the fifth generation cellular system, in the 3rd generation partnership project (3GPP: The Third Generation Partnership Project), LTE (Long Term Evolution) -Advanced Pro and NR (New Radio) technology) and standard formulation (Non-Patent Document 1).

5th generation cellular systems include enhanced mobile broadband (eMBB) for high-speed and large-capacity transmission, ultra-reliable and low-latency communication (URLLC) for low-latency and high-reliability communication, and Internet of Things (IoT). There are three demands for the service scenario: mmMTC (massive Machine Type Communication) to which many machine-type devices connect.

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

(1) In order to achieve the above object, the present invention has taken the following measures. That is, the terminal device according to one aspect of the present invention includes a receiving unit that receives an RRCReconfiguraton message, and a control unit that determines setting information of a search space for receiving the SIB1 and setting information of a RESET. If the first parameter reconfigurationWithSync is included, the control unit determines that the active DL @ BWP includes the bandwidth of the initial DL @ BWP and the SS block with which the initial DL @ BWP is related in the frequency domain, and the same subcarrier interval as the initial DL @ BWP. Is used, the setting information of searchspace # 0 and the setting information of RESET # 0 are determined, and the SIB1 is acquired by the active DL @ BWP based on the determined setting information of searchspace # 0 and the setting information of RESET # 0. And the first parameter is the target cell SpCell It is a parameter for synchronizing les configuration, the CORESET # 0 is relative to the initial DL BWP, set by ControlResourceSetZero, the searchspace # 0 is relative to the initial DL BWP, set by SearchSpaceZero.

(2) Further, a base station device that communicates with the terminal device according to one aspect of the present invention includes a transmitting unit that transmits an RRCReconfiguraton message, and a control unit that controls a search space for the terminal device to acquire SIB1 and CORESET. When the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the control unit determines that an active DL @ BWP operated by the terminal device is associated with an initial DL @ BWP bandwidth and an initial DL @ BWP in a frequency domain. If the terminal device includes the SS block to be used and uses the same subcarrier interval as the initial DL @ BWP, the terminal device is caused to acquire SIB1 by the active DL @ BWP based on the setting information of searchspace # 0 and the setting information of CORRESET # 0. , The first parameter is the target cell. The parameters for synchronous reconfiguration to the SpCell are set by controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is set by searchSpaceZero for the initial DL @ BWP. Is done.

(3) The communication method according to one aspect of the present invention is a communication method for a terminal device, which receives an RRCReconfiguraton message and determines search space setting information and CORESET setting information for receiving SIB1. If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the active DL @ BWP includes the bandwidth of the initial DL @ BWP and the SS block associated with the initial DL @ BWP in the frequency domain, and the same subcarrier interval as the initial DL @ BWP. Is used, the setting information of searchspace # 0 and the setting information of RESET # 0 are determined, and the SIB1 is acquired by the active DL @ BWP based on the determined setting information of searchspace # 0 and the setting information of RESET # 0. And the first parameter is the target cell Sp This is a parameter for synchronous reconfiguration to the Cell. The RESET # 0 is set by controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is set by searchSpaceZero for the initial DL @ BWP. You.

(4) The communication method according to an aspect of the present invention is a communication method for a base station apparatus, which is a communication method for a base station apparatus that communicates with a terminal apparatus that performs an RRC reconfiguration procedure, and transmits a RRCReconfiguraton message. Then, the terminal device controls a search space and a RESET for acquiring SIB1, and when the RRCReconfiguraton message includes the first parameter reconfigurationWithSync, the active DL @ BWP operated by the terminal device is initially set in the frequency domain. If the bandwidth of DL @ BWP and the initial DL @ BWP include the associated SS block, and if the same subcarrier interval as the initial DL @ BWP is used, the terminal device is used for the setting information of searchspace # 0 and the setting information of CORRESET # 0. Based on the active DL @ BWP B1 is acquired, the first parameter is a parameter for synchronous reconfiguration to the target cell SpCell, the RESET # 0 is set by the controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is set. Is set by searchSpaceZero for the initial DL @ BWP.

(5) The integrated circuit according to one embodiment of the present invention is an integrated circuit mounted on a terminal device, the function of receiving an RRCReconfiguraton message, the setting information of search space for receiving SIB1, and the setting of CORRESET. The function of determining information and letting the terminal device exercise the information, and when the first parameter reconfigurationWithSync is included in the message, the active DL @ BWP defines the bandwidth of the initial DL @ BWP and the SS block associated with the initial DL @ BWP in the frequency domain. If it is included and the same subcarrier interval as the initial DL @ BWP is used, the setting information of searchspace # 0 and the setting information of RESET # 0 are determined, and the setting information of the determined searchspace # 0 and the setting of RESET # 0 are determined. Based on the information, the active DL @ BWP is used to obtain SIB1, 1 is a parameter for synchronous reconfiguration to the target cell SpCell, the RESET # 0 is set by controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is a parameter for the initial DL @ BWP. On the other hand, it is set by searchSpaceZero.

(6) Further, an integrated circuit according to one aspect of the present invention is an integrated circuit mounted on a base station device, and has a function of transmitting an RRCReconfiguraton message, a search space for the terminal device to acquire SIB1, and a reset. When the first parameter reconfigurationWithSync is included in the message, the active DL @ BWP operated by the terminal apparatus is set to the initial DL @ BWP bandwidth and the initial DL @ BWP in the frequency domain. If the DL @ BWP includes an associated SS block and uses the same subcarrier interval as the initial DL @ BWP, the terminal apparatus is configured to use the active DL @ BWP based on the setting information of searchspace # 0 and the setting information of CORRESET # 0. SIB1 is acquired, and the first parameter is This is a parameter for synchronous reconfiguration to the get cell SpCell. The RESET # 0 is set by controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is set by searchSpaceZero for the initial DL @ BWP. Is done.

According to the present invention, the base station device and the terminal device can communicate efficiently.

FIG. 1 is a diagram illustrating a concept of a wireless communication system according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of an SS / PBCH block and an SS burst set according to the embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a schematic configuration of an uplink and a downlink slot according to the embodiment of the present invention. FIG. 5 is a diagram illustrating a relationship in a time domain of subframes, slots, and minislots according to the embodiment of the present invention. FIG. 3 is a diagram illustrating an example of a slot or a subframe according to the embodiment of the present invention. FIG. 3 is a diagram illustrating an example of beamforming according to the embodiment of the present invention. FIG. 7 is a diagram illustrating an example of SSB index allocation for PRACH opportunities according to an embodiment of the present invention. FIG. 4 is a diagram illustrating an example of a BWP setting according to the embodiment of the present invention. FIG. 8 is a diagram illustrating pseudo code related to a MAC entity determining BWP switching for a serving cell at the start of a random access procedure in a serving cell according to an embodiment of the present invention. It is a flowchart which shows an example of the random access procedure of the terminal device 1 concerning this embodiment. FIG. 14 is a diagram illustrating another example of pseudo code related to the determination of the BWP switching performed by the MAC entity on the serving cell at the start of the random access procedure in the serving cell according to the present embodiment. FIG. 1 is a schematic block diagram illustrating a configuration of a terminal device 1 according to an embodiment of the present invention. FIG. 2 is a schematic block diagram illustrating a configuration of a base station device 3 according to the embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described.

FIG. 1 is a conceptual diagram of the wireless communication system according to the present embodiment. In FIG. 1, the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3. Hereinafter, the

terminal devices

1A and 1B are also referred to as terminal devices 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), and an MS (Mobile Station). The base station device 3 includes a wireless base station device, a base station, a wireless base station, a fixed station, an NB (Node B), an eNB (evolved Node B), a BTS (Base Transceiver Station), a BS (Base Station), and an NR NB ( Also called NR (Node B), NNB, TRP (Transmission and Reception Point), and gNB. The base station device 3 may include a core network device. In addition, the base station device 3 may include one or more transmission / reception points 4 (transmission @ reception @ point). At least a part of the functions / processes of the base station device 3 described below may be the functions / processes at each transmission / reception point 4 of the base station device 3. The base station device 3 may serve the terminal device 1 with one or more cells in a communicable range (communication area) controlled by the base station device 3. Further, the base station device 3 may serve the terminal device 1 with one or a plurality of cells in a communicable range (communication area) controlled by one or a plurality of transmission / reception points 4. Further, one cell may be divided into a plurality of partial areas (Beamed @ area), and the terminal device 1 may be served in each of the partial areas. Here, the partial area may be identified based on an index of a beam used in beamforming or an index of precoding.

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

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

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

In this embodiment, OFDM symbols will be described using OFDM as a transmission method, but the present invention includes a case using the above-described other transmission methods.

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

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

In the present embodiment, one or more serving cells may be set for the terminal device 1. The set plurality of serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell in which an initial connection establishment procedure has been performed, a serving cell in which a connection re-establishment procedure has been started, or a cell designated as a primary cell in a handover procedure. Good. One or more secondary cells may be set at or after the establishment of an RRC (Radio Resource Control) connection. However, the set multiple 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. Further, a subset of two types of serving cells, a master cell group and a secondary cell group, may be set for the terminal device 1. The master cell group may be composed of one primary cell and zero or more secondary cells. The secondary cell group may be composed of one primary secondary cell and zero or more secondary cells.

無線 The wireless communication system of the present embodiment may employ TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). A TDD (Time Division Division Duplex) method or an FDD (Frequency Division Division Duplex) method may be applied to all of the plurality of cells. Also, 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 unpaired spectrum operation (Unpaired spectrum operation). The FDD scheme may be referred to as a paired spectrum operation (Paired spectrum operation).

キャリア In the downlink, a carrier corresponding to a serving cell is referred to as a downlink component carrier (or a 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, a carrier corresponding to a serving cell is referred to as a side link component carrier (or a 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 a carrier).

物理 The physical channel and the physical signal of the present embodiment will be described.

In FIG. 1, the following physical channels are used in 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 broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) containing important system information required by the terminal device 1.

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

The PDCCH is used to transmit (or carry) downlink control information (Downlink Control Information: DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or a plurality of DCIs (which may be referred to as DCI formats) are defined for transmission of downlink control information. That is, a field for downlink control information is defined as DCI and is mapped to information bits. The PDCCH is transmitted in PDCCH candidates. The terminal device 1 monitors a set of PDCCH candidates (candidate) in the serving cell. Monitoring means attempting 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 include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation).

The DCI format 0_1 is 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, sounding reference. It may include a signal (SRS: Sounding Reference Signal) request and information on an antenna port.

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_1 includes information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating a band portion (BWP), a transmission configuration instruction (TCI: Transmission Configuration Indication), and information regarding an antenna port. Is fine.

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

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

The DCI format 2_2 is used for transmitting a PUSCH and a transmission power control (TPC: Transmit Power Control) command for the 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 a plurality of terminal devices 1. Further, an SRS request may be transmitted together with the TPC command. Further, in DCI format 2_3, an SRS request and a TPC command may be defined for an uplink without a PUSCH and a PUCCH, or for an uplink in which SRS transmission power control is not associated with PUSCH transmission power control.

ＤＣThe DCI for the downlink is also called a downlink grant (downlink @ grant) or a downlink assignment (downlink @ assignment). Here, DCI for the uplink is also referred to as an uplink grant (uplink @ grant) or an uplink assignment (Uplink @ assignment).

The CRC (Cyclic Redundancy Check) parity bit added to the DCI format transmitted on one PDCCH is C-RNTI (Cell-Radio Network Network Temporary Identifier), CS-RNTI (Configured Scheduling-Radio Network Network Temporary Identifier), RA- It is scrambled with RNTI (Random @ Access-Radio @ Network @ Temporary @ Identity) or Temporary @ C-RNTI. 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 (contention based random access procedure).

C-RNTI (terminal device identifier (identification information)) is used to control PDSCH or PUSCH in one or more slots. CS-RNTI is used for periodically allocating PDSCH or PUSCH resources. Temporary @ C-RNTI is used to control PDSCH transmission or PUSCH transmission in one or more slots. Temporary @ C-RNTI is used to schedule retransmission of random access message 3 and 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 for transmitting uplink control information (Uplink Control Information: UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Here, the uplink control information may include channel state information (CSI: {Channel} State} Information) used to indicate the state of the downlink channel. Further, the uplink control information may include a scheduling request (SR: Scheduling Request) used to request the UL-SCH resource. In addition, the uplink control information may include HARQ-ACK (Hybrid \ Automatic \ Repeat \ request \ ACKnowledgement). HARQ-ACK may indicate HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).

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

The PUSCH may be used to transmit HARQ-ACK and / or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer. 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 and 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, RRC information: also referred to as Radio Resource Control information) in a radio resource control (RRC: Radio Resource Control) layer. May be. Further, the base station device 3 and the terminal device 1 may transmit and receive a MAC control element in a MAC (Medium Access Control) layer. Here, the RRC signaling and / or the MAC control element are also referred to as an upper layer signal (upper layer signal: higher @ layer @ signaling). The upper layer here means the upper layer as viewed from the physical layer, and 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.

$ PDSCH or PUSCH may be used for transmitting RRC signaling and MAC control elements. Here, in the PDSCH, RRC signaling transmitted from the base station device 3 may be common signaling to a plurality of terminal devices 1 in a cell. Further, the RRC signaling transmitted from the base station apparatus 3 may be signaling dedicated to a certain terminal apparatus 1 (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted to a certain terminal device 1 using dedicated signaling. Also, the PUSCH may be used for transmission of UE capability (UE Capability) in the uplink.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used for transmitting 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: Primary Synchronization Signal) and a secondary synchronization signal (SSS). The cell ID may be detected using the PSS and the SSS.

The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and the time domain. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that the beam may be called a 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 channel compensation of the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate downlink CSI. In addition, the reference signal may be used for fine synchronization (Fine synchronization) to enable numerology such as wireless parameters and subcarrier intervals, FFT window synchronization, and the like.

In the present 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 a modulated signal. In the DMRS, two types of reference signals for demodulating the PBCH and a reference signal for demodulating the PDSCH may be defined, or both may be referred to as DMRS. CSI-RS is used for channel state information (CSI) measurement and beam management, and a periodic, semi-persistent, or aperiodic CSI reference signal transmission method is applied. As the CSI-RS, a non-zero power (NZP: Non-Zero @ Power) CSI-RS and a zero power (ZP: Zero @ Power) CSI-RS having zero transmission power (or reception power) may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero or no transmit power, and a PTRS to track the phase in the time axis with a view to guaranteeing a frequency offset due to phase noise. TRS is used to guarantee Doppler shift during high-speed movement, where TRS may be used as one setting of CSI-RS, for example, one-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 a modulated signal. In the DMRS, two types of reference signals for demodulating the PUCCH and reference signals for demodulating the PUSCH may be defined, or both may be referred to as DMRS. The SRS is used for uplink channel state information (CSI) measurement, channel sounding, and beam management. PTRS is used to track the phase in the time axis in order to guarantee a frequency offset due to phase noise.

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

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

FIG. 2 is a diagram illustrating an example of an SS / PBCH block (also referred to as a synchronization signal block, an SS block, or an SSB) and an SS burst set (also referred to as a synchronization signal burst set) according to the present embodiment. FIG. 2 illustrates an example in which two SS / PBCH blocks are included in a periodically transmitted SS burst set, and the SS / PBCH blocks are configured by four consecutive OFDM symbols.

The SS / PBCH block is a unit block including at least a synchronization signal (PSS, SSS) and / or PBCH. Transmitting a signal / channel included in an SS / PBCH block is referred to as transmitting an SS / PBCH block. When transmitting the synchronization signal and / or the PBCH using one or a plurality of SS / PBCH blocks in the SS burst set, the base station apparatus 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 the PSS, SSS and / or PBCH are multiplexed in the time domain may be different from the example shown in FIG.

The SS burst set may be transmitted periodically. For example, a cycle to be used for initial access and a cycle to be set for a connected (Connected or RRC_Connected) terminal device may be defined. Further, the cycle set for the connected (Connected or RRC_Connected) terminal device may be set in the RRC layer. In addition, the cycle set for the connected (Connected or RRC_Connected) terminal is a cycle of a radio resource in a time domain that may potentially transmit, and is actually transmitted by the base station apparatus 3. You may decide. Further, the cycle to be 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 a system frame number (SFN: System Frame Number). Further, the start position (boundary) of the SS burst set may be determined based on the SFN and the cycle.

The SS / PBCH block is assigned an SSB index (also referred to as an SSB / PBCH block index) according to a temporal position in the SS burst set. The terminal device 1 calculates an SSB index based on PBCH information and / or reference signal information 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 in 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 a certain 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. A setting corresponding to one or a plurality of SS / PBCH blocks that are QCLs (or may be reference signals) may be referred to as a QCL setting.

The number of SS / PBCH blocks (which may also be referred to as the number of SS blocks or the number of SSBs) is, for example, the number of SS / PBCH blocks (number) in an SS burst or SS burst set, or in a period of an SS / PBCH block. May be defined. Also, the number of SS / PBCH blocks may indicate the number of beam groups for cell selection within an SS burst, within an SS burst set, or within a period of an 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, the SS burst set, or the period of the SS / PBCH block.

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

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

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

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

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

Beam management may include beam selection and beam improvement. Beam recovery may include the following procedures.
Detection of beam failure detection of a new beam transmission of a beam recovery request monitoring of a response to a beam recovery request

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

Further, the base station apparatus 3 indicates a time index of CRI or SS / PBCH when instructing a beam to the terminal apparatus 1, and the terminal apparatus 1 receives a signal based on the instructed CRI or SS / PBCH time index. I do. At this time, the terminal device 1 may set and receive a spatial filter based on the designated CRI or SS / PBCH time index. In addition, the terminal device 1 may receive the data using an assumption of a pseudo-same location (QCL: Quasi @ Co-Location). A signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" or another signal (antenna port, synchronization signal, reference signal, etc.) with another signal (antenna port, synchronization signal, reference signal, etc.) Can be interpreted as being associated with another signal.

Two antenna ports are said to be QCL if the Long Term Property of a channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port. . The long-range characteristics of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if 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. For this purpose, a QCL extended to the space may be newly defined. For example, as the long-term property of a 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 angle spread on a radio link or channel (Angle Spread, for example, ASA (Angle Spread of Arrival) or ZSA (Zenith angle Spread of Arrival)), transmission angle (AoD, ZoD, etc.) and its angular spread (Angle Spread, such as ASD (Angle Spread of Departure) or ZSD ( Zenith angle Spread of Departure)), spatial correlation (Spatial Correlation), and reception spatial parameters.

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

As the QCL type, a combination of long-range characteristics that may be regarded as a QCL may be defined. For example, the following types may be defined:
-Type A: Doppler shift, Doppler spread, average delay, delay spread-Type B: Doppler shift, Doppler spread-Type C: average delay, Doppler shift-Type D: reception spatial parameter

The above-mentioned QCL type sets and / or sets one or two reference signals and an assumption of QCL of PDCCH or PDSCH @ DMRS as a transmission setting instruction (TCI: Transmission Configuration Indication) in the RRC and / or MAC layer and / or DCI. You may instruct. For example, as one state of the TCI when the terminal device 1 receives the PDCCH, if the SS / PBCH block index # 2 and the QCL type A + QCL type B are set and / or indicated, the terminal device 1 performs PDCCH @ DMRS , When receiving the PDCCH DMRS, assuming the Doppler shift, the Doppler spread, the average delay, the delay spread, the reception spatial parameter and the long-term characteristics of the channel in the reception of the SS / PBCH block index # 2, An estimate may be made. At this time, a reference signal (SS / PBCH block in the above example) indicated by the TCI is a source reference signal, and a reference affected by long-term characteristics inferred from long-term characteristics of a channel when the source reference signal is received. The signal (PDCCH @ DMRS in the above example) may be referred to as a target reference signal. In the TCI, a combination of a source reference signal and a QCL type may be set for a plurality of TCI states and each state by RRC, and may be instructed to the terminal device 1 by a MAC layer or DCI.

With this method, the operations of the base station device 3 and the terminal device 1 equivalent to the beam management are defined by the assumption of the QCL in the spatial domain and the radio resources (time and / or frequency) as the beam management and the beam instruction / report. Good.

Hereinafter, the subframe will be described. In this embodiment, it is called a subframe, but may be called 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 the uplink and downlink slots according to the first embodiment of the present invention. Each of the radio frames is 10 ms long. Each radio frame is composed of 10 subframes and W slots. One slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms. Each slot has a time length defined by a subcarrier interval. For example, when the subcarrier interval of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X = 7 or X = 14, which are 0.5 ms and 1 ms, respectively. When the subcarrier interval is 60 kHz, X = 7 or X = 14, which are 0.125 ms and 0.25 ms, respectively. For example, when X = 14, W = 10 when the subcarrier interval is 15 kHz, and W = 40 when the subcarrier interval is 60 kHz. FIG. 3 shows a case where X = 7 as an example. It should be noted that the same applies to the case where X = 14. Also, an uplink slot is defined similarly, and a downlink slot and an uplink slot may be defined separately. Further, the bandwidth of the cell in FIG. 3 may be defined as a part of the bandwidth (BWP: BandWidth Part). Further, a slot may be defined as a transmission time interval (TTI: Transmission @ Time @ Interval). A slot may not be defined as a TTI. The TTI may be a transmission period of a transport block.

The signal or physical channel transmitted in each of the slots may be represented by a resource grid. A resource grid is defined by multiple subcarriers and multiple OFDM symbols. The number of subcarriers forming one slot depends on the downlink and uplink bandwidth of the cell, respectively. Each of the elements in the resource grid is called a resource element. Resource elements may be identified using subcarrier numbers and OFDM symbol numbers.

The resource grid is used to represent the mapping of resource elements of a certain physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier interval is 15 kHz, the number of OFDM symbols included in the subframe is X = 14. In the case of NCP, one physical resource block is composed of 14 consecutive OFDM symbols in the time domain and 14 in the frequency domain. It is defined from 12 * Nmax consecutive subcarriers. Nmax is the maximum number of resource blocks determined by a subcarrier interval setting μ described later. That is, the resource grid is composed of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended @ CP), since it is supported only at a subcarrier interval of 60 kHz, one physical resource block is, for example, 12 (the number of OFDM symbols included in one slot) * 4 (included in one subframe) in the time domain. (Number of slots to be used) = 48 continuous OFDM symbols and 12 * Nmax, μ continuous 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 continuous subcarriers in the frequency domain. The reference resource block is common to all subcarriers. For example, a resource block may be configured at a subcarrier interval of 15 kHz, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or simply referred to as "reference point"). The common resource block is a resource block that is numbered in ascending order from 0 at 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 a bandwidth portion (BWP) described later, and the physical resource blocks are allocated in ascending order from 0 included in the bandwidth portion (BWP). This is a numbered resource block. A physical uplink channel is first mapped to a virtual resource block. Thereafter, the virtual resource blocks are mapped to physical resource blocks.

Next, the subcarrier interval setting μ will be described. As mentioned above, NR supports multiple OFDM numerologies. In a certain BWP, a subcarrier interval setting μ (μ = 0, 1,..., 5) and a cyclic prefix length are given in an upper layer (upper layer) with respect to a downlink BWP, Provided in the upper layer in BWP. Here, when μ is given, the subcarrier interval Δf is given by Δf = 2 ＾ μ · 15 (kHz).

In the subcarrier interval setting μ, slots are counted in ascending order from 0 to N ^ {subframe, μ} _ {slot} -1 in a subframe, and from 0 to N ^ {frame, μ} _ {slot } -1 is counted in ascending order. Based on the slot configuration and the cyclic prefix, N ^ {slot} _ {symb} consecutive OFDM symbols are in the slot. 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. Are aligned.

Next, subframes, slots, and minislots will be described. FIG. 4 is a diagram showing the relationship in the time domain between subframes, slots, and minislots. 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 varies depending on the subcarrier interval. Here, when the subcarrier interval is 15 kHz, 14 OFDM symbols are included in one subframe. The downlink slot may be referred to as PDSCH mapping type A. Uplink slots may be referred to as PUSCH mapping type A.

A minislot (which 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 an example where the minislot is composed of 2 OFDM symbols. An OFDM symbol in a mini-slot may coincide with the OFDM symbol timing making up the slot. The minimum unit of scheduling may be a slot or a minislot. Assigning minislots may also be referred to as non-slot based scheduling. In addition, scheduling a minislot may be expressed as scheduling a resource whose relative time position between the reference signal and the data start position is fixed. The downlink minislot may be referred to as PDSCH mapping type B. An uplink minislot may be referred to as PUSCH mapping type B.

FIG. 5 is a diagram illustrating an example of the slot format. Here, a case where the slot length is 1 ms at a subcarrier interval of 15 kHz is shown as an example. In the figure, D indicates downlink and U indicates uplink. As shown in the figure, within a certain time interval (for example, the minimum time interval that must be assigned to one UE in the system)
One or more of downlink symbols, flexible symbols, and uplink symbols may be included. Note that these ratios may be predetermined as a slot format. Also, it may be defined by the number of downlink OFDM symbols included in the slot or the start position and the end position in the slot. Also, 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 the end position in the slot. It should be noted that scheduling a slot may be expressed as scheduling a resource whose relative time position between the reference signal and the slot boundary is fixed.

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

FIG. 5A may be referred to as a certain time section (for example, a minimum unit of a time resource that can be allocated to one UE, a time unit, or the like. Also, a bundle of a plurality of minimum units of a time resource is referred to as a time unit. FIG. 5B illustrates an example in which uplink scheduling is performed using, for example, a PDCCH in the first time resource, and processing delay of the PDCCH and downlink are performed. To transmit an uplink signal through a flexible symbol including an uplink switching time and generation of a transmission signal. FIG. 5 (c) is used for transmission of the PDCCH and / or the downlink PDSCH in the first time resource, and includes PUSCH or PUCCH via a processing delay and a switching time from downlink to uplink, a gap for generation of a transmission signal. Is used for transmission. Here, as an example, the uplink signal may be used for transmission of HARQ-ACK and / or CSI, that is, UCI. FIG. 5 (d) is used for transmission of the PDCCH and / or PDSCH in the first time resource, and the PUSCH and / or the uplink are transmitted via a processing delay and a switching time from downlink to uplink, and a gap for generating 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) shows an example in which all are used for uplink transmission (PUSCH or PUCCH).

下り The above-mentioned downlink part and uplink part may be composed of a plurality of OFDM symbols as in LTE.

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

Hereinafter, the band portion (BWP, {Bandwidth} part) will be described. BWP is also called carrier BWP. The 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 a common resource block. 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 not setting the BWP. The setting of two or more BWPs may be expressed as the setting of the BWP.

<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. Is done. BWP switching for a certain serving cell is controlled by a PDCCH indicating a downlink assignment or an uplink grant. BWP switching for a serving cell may be further controlled by a BWP inactivity timer, RRC signaling, or by the MAC entity itself at the start of the random access procedure. In addition of SpCell (PCell or PSCell) or activation of SCell, one BWP is initially active without receiving a PDCCH indicating a downlink assignment or an uplink grant. The initially active DL BWP and UL BWP may be specified in an RRC message sent from the base station device 3 to the terminal device 1. The active BWP for a certain serving cell is specified by RRC or PDCCH sent from base station apparatus 3 to terminal apparatus 1. In an unpaired spectrum (such as a TDD band), DL BWP and UL BWP are paired, and BWP switching is common to UL and DL. In the active BWP for each of the activated serving cells in which the BWP is set, the MAC entity of the terminal device 1 applies a normal process. Normal processing includes transmitting a UL-SCH, transmitting a RACH, monitoring a PDCCH, transmitting a PUCCH, transmitting an SRS, and receiving a DL-SCH. In the inactive BWP for each activated serving cell for which BWP is set, the MAC entity of the terminal device 1 does not transmit the UL-SCH, does not transmit the RACH, does not monitor the PDCCH, does not transmit the PUCCH, No SRS is transmitted and no DL-SCH is received. If a serving cell is deactivated, there may be no active BWP (eg, the active BWP is deactivated).

<RRC operation>
A BWP information element (IE) included in an RRC message (system information to be broadcast or information sent in a dedicated RRC message) is used for setting BWP. The RRC message transmitted from the base station device 3 is received by the terminal device 1. For each serving cell, the network (such as base station apparatus 3) has at least one downlink BWP and one (for example, if the serving cell is configured for uplink) or two (appendix uplink (supplementary uplink)). In this case, at least an initial BWP (initial BWP) including the uplink BWP in the case where is used is set for the terminal device 1. Further, the network may configure additional uplink and downlink BWPs for certain serving cells. BWP configuration is divided into uplink parameters and downlink parameters. The BWP setting is divided into a common parameter and a dedicated parameter. Common parameters (such as BWP uplink common IE and BWP downlink common IE) are cell-specific. Common parameters of the primary BWP of the primary cell are also provided in the system information. For all other serving cells, the network provides common parameters with dedicated signals. BWP is identified by BWP ID. The initial BWP has a BWP ID (BWP identifier) of 0. BWP IDs of other BWPs take values from 1 to 4.

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

<< Random access procedure (Random Access procedure) of this embodiment is demonstrated. The random access procedure is classified into two procedures: a contention-based (CB: Content @ Base) and a non-contention-based (non-CB) (CF: Content: Free). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA

The random access procedure includes (i) transmission of a random access preamble (message 1, Msg1) on PRACH, (ii) reception of a random access response (RAR) message with PDCCH / PDSCH (message 2, Msg2), and applicable. In such a case, (iii) transmission of message 3 PUSCH (Msg3 PUSCH) and (iv) reception of PDSCH for resolving collision may be included.

FIG. 10 is a flowchart illustrating an example of the random access procedure of the terminal device 1 according to the present embodiment.

<Start of random access procedure (S1001)>
In FIG. 10, S1001 is a procedure relating 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 notification of a beam failure from a MAC entity, a lower layer, an 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 random access setting information via an upper layer before starting (initiate) a random access procedure. The random access setting information may include the following information or information for determining / setting the following information.
• prach-ConfigIndex: a set of one or more time / frequency resources (also referred to as random access channel occasions, PRACH occasions, RACH occasions) available for transmission of the random access preamble • premableReceivedTargetPower : Initial power of preamble (may be target received power)
Rsrp-ThresholdSSB: Reference signal received power (RSRP) threshold for selection of SS / PBCH block (which may be the associated random access preamble and / or PRACH opportunity) rsrp-ThresholdCSI-RS: CSI-RS Reference signal received power (RSRP) threshold for selection of (which may be an associated random access preamble and / or PRACH opportunity) rsrp-ThresholdSSB-SUL: NUL (Normal Uplink) carrier and SUL (Supplementary Uplink) Reference signal received power (RSRP) threshold for selection with carrier powerControlOffset: rsrp-ThresholdSSB if random access procedure is started for beam failure recovery rsrp-ThresholdCSI-RS between the power offset · powerRampingStep: power ramping step (power ramping factor). Indicates the step of the transmission power to be 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-OccationMaskIndex: Information for determining the PRACH opportunity allocated to the SS / PBCH block in which the MAC entity transmits the random access preamble ra-OccasionList: CSI in which the MAC entity transmits the random access preamble -Information for determining the PRACH opportunity assigned to the RS-premTransMax Maximum number of preamble transmissions ssb-perRACH-OccationAndCB-PreamblesPer SSB (SpCell only): Parameter indicating the number of SS / PBCH blocks mapped to each PRACH opportunity and the number of random access preambles mapped to each SS / PBCH block. ra-ResponseWindow: Time window for monitoring random access response (SpCell only) ra-ContentionResolutionTimer: Contention Resolution timer, numberOfRA-PreamblesGroupA: Random burst for each SS / PBCH block Number of random access preambles in group A · PREAM BLE_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 preamble 5 shows an initial transmission power for random access preamble transmission.
PREAMBLE_BACKOFF: Used to adjust the timing of random access preamble transmission.

When the random access procedure for a certain serving cell is started, the MAC entity flushes 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 0ms. If the carrier used for the random access procedure is explicitly reported, the MAC entity selects the reported carrier for performing the random access procedure and sets the state variable PCMAX to the maximum transmission power value of the reported carrier. set. When the MAC entity does not explicitly notify the carrier used for the random access procedure, and the SUL carrier is set for the serving cell, and the RSRP for downlink path loss reference is smaller than rsrp-ThresholdSSB-SUL Then, the SUL carrier is selected for performing 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 a NUL carrier for performing the random access procedure and sets the state variable PCMAX to the maximum transmission power value of the NUL carrier.

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

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

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

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

The terminal device 1 provides (1) a random access resource for non-contention-based random access associated with the SS / PBCH block from the RRC, and (2) a predetermined RSRP among the associated SS / PBCH blocks. When one or more SS / PBCH blocks exceeding the threshold value are available, one of the SS / PBCH blocks whose RSRP exceeds the predetermined threshold value is selected, and the selected SS / PBCH block is Set the associated ra-PreambleIndex to the preamble index.

The terminal device 1 (1) associates a CSI-RS with a random access resource for non-contention-based random access by RRC, and (2) RSRP of the associated CSI-RS exceeds a predetermined threshold If one or more CSI-RSs are available, select one of the CSI-RSs whose RSRP exceeds the predetermined threshold and preamble the ra-PreambleIndex associated with the selected CSI-RS. Set to index.

If the terminal device 1 does not satisfy any of the above conditions, the terminal device 1 performs a contention-based random access procedure. In the contention-based random access procedure, the terminal device 1 selects an SS / PBCH block having an RSRP of an SS / PBCH block exceeding a set threshold, and selects a preamble group. When the relationship between the SS / PBCH block and the random access preamble has been set, the terminal device 1 determines a random number from one or more random access preambles associated with the selected SS / PBCH block and the selected preamble group. , Select ra-PreambleIndex, and set the selected ra-PreambleIndex to the preamble index.

The MAC entity selects one SS / PBCH block, and if an association between the PRACH opportunity and the SS / PBCH block is set, the next of the PRACH opportunities associated with the selected SS / PBCH block May determine available PRACH opportunities. However, the terminal device 1 selects one CSI-RS, and if the association (association) between the PRACH opportunity and the CSI-RS is set, the terminal device 1 selects the next PRACH opportunity among the PRACH opportunities 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 with RRC parameters, and / or a selected reference signal (SS / PBCH block or CSI-RS). Good. The resource settings set by the RRC parameters include resource settings for each SS / PBCH block and / or resource settings for each CSI-RS.

The base station device 3 may transmit the resource setting for each SS / PBCH block and / or the resource setting for each CSI-RS to the terminal device 1 by an RRC message. The terminal device 1 receives the resource setting for each SS / PBCH block and / or the resource setting for each CSI-RS from the base station device 3 in the RRC message. 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 a 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). It 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.

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

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

<Transmission of random access preamble (S1003)>
S1003 is a procedure related to transmission of a random access preamble (random access preamble transmission). For each random access preamble, the MAC entity determines (1) that the state variable PREAMBLE_TRANSMISSION_COUNTER is greater than 1 and (2) that no notification of a stopped power ramp counter has been received from higher layers, and (3) the selection If the changed SS / PBCH block has not been changed, the state variable PREAMBLE_POWER_RAMPING_COUNTER is incremented by one.

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

Next, the MAC entity calculates the RA-RNTI associated with the PRACH opportunity where the random access preamble is transmitted, other than the non-contention based random access preamble due to the 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 the index of the first OFDM symbol of the PRACH to be transmitted, and takes a value from 0 to 13. t_id is the index of the first slot of the 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 a value from 0 to 7. ul_carrier_id is an uplink carrier used for Msg1 transmission. The ul_carrier_id for the NUL carrier is 0, and the ul_carrier_id for the SUL carrier is 1.

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

<Reception of random access response (S1004)>
S1004 is a procedure for receiving a random access response. Once the random access preamble has been transmitted, the MAC entity performs the following operations regardless of the possible occurrence of measurement gaps.

In S1004, if the MAC entity has transmitted a non-contention-based random access preamble for a beam failure recovery request, the MAC entity uses a random access response window (ra-ResponseWindow) at the first PDCCH opportunity from the end of the random access preamble transmission. Start. Then, while the random access response window is running, the MAC entity monitors the SpCell PDCCH identified by the C-RNTI for a 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 the 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, while the random access response window is running, the MAC entity monitors the SpCell PDCCH identified by the RA-RNTI for a random access response. Here, the information element BeamFailureRecoveryConfig is used for setting a RACH resource and a candidate beam for the terminal apparatus 1 for beam failure recovery in the case of beam failure detection. The information element RACH-ConfigCommon is used to specify a cell-specific random access parameter.

The MAC entity may (1) receive acknowledgment of the PDCCH transmission from the lower layer, (2) the PDCCH transmission may be scrambled by the C-RNTI, and (3) the MAC entity may use a non-contention based When the random access preamble is transmitted, the random access procedure may be deemed to have been successfully completed.

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

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

The $ MAC entity may deem that the random access response has been successfully received if the MAC entity includes a MAC $ subPDU that includes the random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX.

The MAC entity considers that the random access procedure has been successfully completed if (1) the reception of the random access response is considered successful and (2) the random access response includes only the MAC @ subPDU containing the RAPID; , The reception of the acknowledgment (acknowledgement) to the SI request (symstem @ information @ request) is indicated to the upper layer. Here, if the condition (2) is not satisfied, the MAC entity applies the following operation A to the serving cell where the random access preamble is transmitted.

<Start of operation A>
The MAC entity processes the received transmission timing adjustment information (Timing Advance Command), and indicates to the lower layer the preambleReceivedTargetPower and the amount of power ramping applied to the latest random access preamble transmission. Here, the transmission timing adjustment information is used to adjust a shift in transmission timing between the terminal device 1 and the base station device 3 from the received random access preamble.

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

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

<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. Subsequently, if the random access response is successfully received for the first time in this random access procedure, then the MAC entity may, if not transmitting on the CCCH logical channel (common control channel logical channel), Notify a predetermined entity (multiplexing and assembly entity) that the C-RNTI MAC CE will be included in the next uplink transmission, and obtain and obtain a MAC PDU for transmission from the predetermined entity (multiplexing and assembly entity) The stored MAC PDU is stored in the Msg3 buffer. When transmission is performed on the CCCH logical channel, the MAC entity acquires a MAC PDU for transmission from a predetermined entity (multiplexing and assembly entity), and stores the acquired MAC PDU in the Msg3 buffer.

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

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

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

If the random access procedure has not been completed, the MAC entity may determine whether the random access preamble is selected by the MAC itself from the range of contention-based random access preambles, if the random access procedure is between 0 and PREAMBLE_BACKOFF. A backoff time is selected, transmission of the next random access preamble is delayed by the selected backoff time, and S1002 is executed. If the random access procedure has not been completed, the MAC entity performs S1002 if the random access preamble has not been selected from the range of the contention-based random access preamble by the MAC itself 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 matching 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 contention resolution.

{Once Msg3 is transmitted, 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.

In the case where the reception notification of the PDCCH transmission is received from the lower layer and the C-RNTI {MAC} CE is included in Msg3, the MAC entity determines that at least one of the following conditions (5) to (7) is satisfied: , Deem the contention resolution to be successful, stop the collision resolution timer, discard the TEMPORARY_C-RNTI, and deem that the random access procedure has 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 the initial transmission. . Condition (6) is that the random access procedure is started by PDCCH order and PDCCH transmission is scrambled by C-RNTI. Condition (7) is that the random access procedure is started for beam failure recovery, and the PDCCH transmission is scrambled by C-RNTI.

If CCCH SDU (UE contention resolution Identiy) is included in Msg3 and the PDCCH transmission is scrambled by TEMPORARY_C-RNTI, the MAC entity stops the collision resolution timer if the MAC PDU is successfully decoded. . Subsequently, if the successfully decoded MAC PDU includes a UE contention resolution identity MAC CE, and the UE collision resolution identity in the MAC CE matches the CCCH SDU transmitted on Msg3, The MAC entity considers that the collision resolution is successful and ends the disassembly and demultiplexing of the MAC @ PDU. Then, when the random access procedure is started for the SI request, the MAC entity indicates to the upper layer the receipt of the acknowledgment for the SI request. If the random access procedure is not started due to the SI request, the MAC entity sets C-RNTI to the value of TEMPORARY_C-RNTI. Subsequently, the MAC entity discards the TEMPORARY_C-RNTI and considers the random access procedure to be successfully completed.

If the UE collision resolution identity in the MAC $ CE does not match the CCCH $ SDU sent in Msg3, the MAC entity discards the TEMPORARY_C-RNTI, assumes that the collision resolution is not successful, and returns the successfully decoded MAC $ PDU. Discard.

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

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 by the selected backoff time, and executes S1002.

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

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

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

The control resource set specified by the 識別子 CORESET identifier 0 (ControlResourceSetId） 0) is referred to as RESET # 0. CORESET # 0 may be set by pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. That is, the setting information of CORRESET # 0 may be pdcch-ConfigSIB1 included in MIB, or PDCCH-ConfigCommon included in ServingCellConfigConfig. The setting information of RESET # 0 may be set by controlResourceSetZero included in PDCCH-ConfigCommon. CORESET indicated by pdcch-ConfigSIB1 is CORESET # 0. The RESET setting information pdcch-ConfigSIB1 for RESET # 0 does not include information for explicitly specifying the RESET identifier and the RESET frequency resource, but the RESET frequency resource for RESET # 0 is included in the pdcch-ConfigSIB1. Information can be specified implicitly. The information element PDCCH-ConfigCommon is used to set a cell-specific PDCCH parameter provided in the SIB. Also, the PDCCH-ConfigCommon may be provided at the time of handover and addition of PSCell and / or SCell. The setting information of the coreset # 0 is included in the setting of the initial BWP. That is, the setting information of CORRESET # 0 may not be included in the settings of BWP other than the initial BWP.

The setting information of the additional common CORRESET (additional common control resource set) may be set by a commonControlResourceSet included in the PDCCH-ConfigCommon. The configuration information of the additional common coreset may be used to specify the additional common coreset used for the random access procedure. Additional common CORESET configuration information may be included in each BWP configuration. The identifier of the RESET shown in the commonControlResourceSet takes a value other than 0.

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

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

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

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

(4) The search space setting information includes the coreset identifier specified by the coreset setting information. The coreset specified by the coreset identifier included in the search space setting information is associated with the search space. In other words, the coreset associated with the search space is the coreset specified by the coreset identifier included in the search space. The DCI format indicated by the setting information of the search space is monitored by the associated CORRESET. 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, the DCI format to which the CRC scrambled by the RA-RNTI or the TC-RNTI is added in the CORESET associated with the ra-SearchSpace is monitored.

The terminal device 1 monitors a set of PDCCH candidates in one or more coresets arranged in each active serving cell set to monitor the PDCCH. The set of PDCCH candidates corresponds to one or more search space sets. Monitoring means decoding each PDCCH candidate according to one or more DCI formats to be 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 description, 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 in one or a plurality of the following search space sets. -A Type 0-PDCCH common search space set: This search space set is a search space zero (searchSpaceZero) indicated by MIB or a search space indicated by PDCCH-ConfigCommon, which is an upper layer parameter. This is set by SIB1 (searchSpaceSIB1). This search space is for monitoring the DCI format of the CRC scrambled with the SI-RNRI in the primary cell.
A Type 0A-PDCCH common search space set: This search space set is set by a search space OSI (searchSpace-OSI) indicated by PDCCH-ConfigCommon, which is a parameter of an upper layer. This search space is for monitoring the DCI format of the CRC scrambled with the SI-RNRI in the primary cell.
-A Type1-PDCCH common search space set: This search space set is a search space (ra-SearchSpace) for a random access procedure indicated by PDCCH-ConfigCommon, which is an upper layer parameter. Is set by This search space is for monitoring the DCI format of the CRC scrambled with RA-RNRI or TC-RNTI in the primary cell.
-A Type2-PDCCH common search space set: This search space set is set by the paging search space (pagingSearchSpace) for the paging procedure indicated by the upper layer parameter, PDCCH-ConfigCommon. You. This search space is for monitoring the DCI format of the CRC scrambled with the P-RNTI in the primary cell.
-Type 3 PDCCH common search space set (a Type3-PDCCH common search space set): This search space set is set by a search space (SearchSpace) in which the search space type indicated by PDCCH-Config which is a parameter of an upper layer is common. You. This search space is for monitoring the DCI format of the CRC scrambled by the INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI. For the primary lycel, it is for monitoring the DCI format of the CRC scrambled with the C-RNTI or CS-RNTI (s).
-UE-specific search space set: In this search space set, a search space type indicated by PDCCH-Config, which is a parameter of an upper layer, is set by a UE-specific search space. . This search space is for monitoring the DCI format of the CRC scrambled with C-RNTI or CS-RNTI (s).

The setting information of $ BWP is divided into setting information of DL @ BWP and setting information of UL @ BWP. The BWP setting information includes an information element bwp-Id (BWP identifier). The BWP identifier included in the DL @ BWP setting information is used to specify (refer to) the DL @ BWP in a certain serving cell. The BWP identifier included in the UL @ BWP setting information is used to specify (refer to) UL @ BWP in a certain serving cell. The BWP identifier is given to each of DL @ BWP and UL @ BWP. For example, the identifier of the BWP corresponding to DL @ BWP may be referred to as DL @ BWP @ index (DL @ BWP @ index). The identifier of the BWP corresponding to UL @ BWP may be referred to as 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 values of the identifiers of other BWPs take values from 1 to 4. The other upper layer setting information is associated with a specific BWP by using the BWP identifier.

FIG. 8 is a diagram showing an example of the BWP setting according to the embodiment of the present invention.

{One initial BWP including at least one DL @ BWP and one UL @ BWP is set for each serving cell. Then, additional BWP (additional UL @ BWP and additional DL @ BWP) may be set for a certain serving cell. Up to four additional BWPs may be set. However, in one serving cell, one DL @ BWP becomes active and one UL @ BWP becomes active.

In FIG. 8, one initial BWP (BWP # 0) and two additional BWPs (BWP # 1 and BWP # 2) are set for a terminal device 1 in a certain serving cell. Reference numeral 801 denotes an initial DL @ BWP (DL @ BWP # 0). Reference numeral 802 denotes an initial UL @ BWP (UL @ BWP # 0). Reference numeral 805 denotes an additional DL @ BWP (DL @ BWP # 1). Reference numeral 806 denotes an additional UL @ BWP (UL @ BWP # 1). Reference numeral 808 denotes an additional DL @ BWP (DL @ BWP # 2). 809 is an additional UL @ BWP (UL @ BWP # 2). Hereinafter, it is assumed that DL @ BWP # 1 is activated and UL @ BWP # 0 is activated. That is, DL @ BWP # 0 and UL @ BWP # 1 are inactive BWPs. DL @ BWP # 2 and UL @ BWP # 2 are inactive BWPs. In this case, the activated DL @ BWP # 1 may be referred to as an active DL @ BWP (active DL @ BWP, currently @ active @ DL @ BWP). The activated initial UL @ BWP # 0 may be referred to as an initially active ULBWP. The terminal device 1 performs downlink reception with the active DL @ BWP # 1, and performs uplink transmission with the initially active UL @ BWP.

$ 803 is a reset # 0 set for the initial DL $ BWP. 804 is an additional common coreset set for the initial DL @ BWP. Reference numeral 807 denotes a reset that is set for the additional BWP # 1. Reference numeral 810 denotes a coreset set for the additional BWP # 2. 807 and 810 may be referred to as UE-specific CORESET (UE \ specifically \ configured \ Control \ Resource \ Sets). As described above, the setting information of CORRESET # 0 (803) may be set by pdcch-ConfigSIB1 or PDCCH-ConfigCommon. The setting information of the additional common CORESET (804) may be set by commonControlResourceSet included in the PDCCH-ConfigCommon. The setting information of RESET (807 and 810) may be set by controlResourceSetToAddModList included in PDCCH-Config. The value of the identifier of the RESET of 803 is given as 0. The value of the RESET identifier of 804 may be given as one. The value of the identifier of the RESET of 807 may be given by 3. The value of the identifier of the RESET at 810 may be given by 6. For the DL @ BWP # 0, the value of the identifier of the RESET including the ra-searchspace is set to 1, and for the DL @ BWP # 2, the value of the identifier of the RESET including the ra-searchspace is set to 6.

In FIG. 8, ra-searchspace is set for each of DL @ BWP # 0, DL @ BWP # 1, and DL @ BWP # 2. As described above, the setting information of the search space for the random access procedure may be set according to ra-SearchSpace. As a first example, the identifier of the RESET included in the ra-searchspace set for a certain DL @ BWP is set to the value of the identifier of the RESET that specifies the setting information of the RESET set for the DL @ BWP. Alternatively, it may be set to the value of the identifier of CORESET included in the ra-SearchSpace set for the initial BWP. That is, the ra-searchspace set for a certain DL @ BWP may indicate the identifier of the RESET that specifies the setting information of the RESET set for the DL @ BWP, or the The identifier of CORESET included in the set ra-SearchSpace may be indicated. That is, the ra-searchspace set for a certain DL @ BWP does not indicate the identifier of the common and UE-specific CORESET set for the DL @ BWP and other DL @ BWPs other than the initial DL @ BWP. Is also good. In other words, the ra-searchspace set by the base station apparatus 3 for a certain DL @ BWP is a common set for the DL @ BWP other than the DL @ BWP and the initial DL @ BWP. And the RRC message may be transmitted so as not to indicate the identifier of the UE-specific CORRESET. For example, for the DL @ BWP # 1, the value of the identifier of the RESET including the ra-searchspace may be set to 1, or may be set to 3. The value of the identifier of the RESET including the ra-searchspace for DL @ BWP # 1 is not set to 6. When the value of the identifier of the RESET including the ra-searchspace for DL @ BWP # 1 is set to 1, the terminal device 1 is set based on the setting information of the RESET # 1 (804) specified by the identifier 1 of the RESET. The active DL @ BWP # 1 monitors the DCI format included in the ra-searchspace. When the value of the identifier of the RESET including the ra-searchspace for DL @ BWP # 1 is set to 3, the terminal device 1 is set based on the setting information of the RESET # 3 (807) specified by the identifier 3 of the RESET. The active DL @ BWP # 1 monitors the DCI format included in the ra-searchspace. That is, the ra-searchspace set for a certain DL @ BWP may indicate the identifier of the coreset that specifies the setting information of the common coreset. For example, the value of the identifier of CORESET including ra-searchspace for DL @ BWP # 1 may be set to 1. In other words, if RESET # 1 is set in the initial DL @ BWP, RESET # 0 cannot be called as ra-searchspace. If RESET # 1 is not set in the initial DL @ BWP, RESET # 0 can be called as ra-searchspace. However, as an extension of the first example, even when RESET # 1 is set in the initial DL @ BWP, the RESET # 0 can be called by the DL @ BWP as a ra-searchspace. Is also good.

Further, as a second example, the identifier of the RESET included in the ra-searchspace set for a certain DL @ BWP is the identifier of the RESET that specifies the setting information of the common RESET set for the DL @ BWP. It may be set to a value, or may be set to the value of the identifier of the common coreset for the random access procedure set for another BWP. That is, the ra-searchspace set for a certain DL @ BWP may indicate the identifier of the RESET that specifies the setting information of the common RESET that is set for the DL @ BWP, or may indicate to other BWPs. The identifier of the common CORESET for the random access procedure set for this may be indicated. For example, with respect to DL @ BWP # 1, the value of the identifier of the RESET including the ra-searchspace may be set to 1, 3, or 6, may be set. That is, when RESET # 1 is set in the initial DL @ BWP, CORRESET # 0 cannot be called as the ra-searchspace of the DL @ BWP. If the RESET # 1 is not set in the initial DL @ BWP, the RESET # 0 can be called as the DL-BWP ra-searchspace.

Further, as a third example, the identifier of CORESET included in the ra-searchspace set for a certain DL @ BWP may be set to the value of the identifier of every common CORESET set in the terminal device 1. . That is, the ra-searchspace set for a certain DL @ BWP may indicate the identifier of the coreset that specifies the setting information of all the common coresets set in the serving cell. For example, the value of the identifier of the coreset including ra-searchspace for DL @ BWP # 1 may be set to 0, 1, 3, or 6.

The setting information of the coreset set for the DL @ BWP may be set to the value of the coreset identifier for specifying the coreset, or set to the value of the coreset identifier set for another BWP. You may. That is, the ra-searchspace set for a certain DL @ BWP may indicate the identifier of the RESET that specifies the setting information of the RESET set for the DL @ BWP, or may be used for another BWP. May be indicated. For example, for DL @ BWP # 1, the value of the identifier of CORESET including ra-searchspace may be set to 0, may be set to 1, may be set to 3, or may be set to 6. May be set.

In this embodiment, at the start of the above-described random access procedure in the serving cell, the MAC entity determines whether to switch BWP for this serving cell. Hereinafter, BWP switching at the start of the random access procedure in the serving cell will be described.

In this embodiment, at the start of the random access procedure in a certain serving cell, the MAC entity determines the active DL BWP based on at least some or all of the following elements (i) to (vi): Determine whether to switch from BWP to another DL BWP (e.g., initial DL BWP, first active DL BWP, DL BWP having the same BWP identifier as active UL BWP), and BWP capable of performing a random access procedure May be determined.
(I) whether the PRACH opportunity is set for the active UL BWP, (ii) whether the serving cell is a SpCell, or (iii) the identifier of the active DL BWP and the identifier of the active UL BWP. (V) In the DL BWP having the same identifier of the CORSET specifying the control resource set associated with the ra-SearchSpace set for the active DL BWP and the same BWP identifier as the active UL BWP. Whether the identifier of the RESET associated with the set ra-SearchSpace is the same. (Vi) whether the ra-SearchSpace is set for the active DL BWP.

The PRACH opportunity is the time and frequency resources available for transmitting the random access preamble. The PRACH opportunity will be described later.

FIG. 9 is a diagram showing pseudo code regarding a MAC entity at the start of a random access procedure in a serving cell, the BWP switching determination for the serving cell.

In FIG. 9, condition A is that no PRACH opportunity is set for the active UL @ BWP. Condition B is that the serving cell is SpCell. Condition C is that the active DL @ BWP does not have the same bwp-Id as the active UL @ BWP. Condition D is that the ra-SearchSpace set for the active DL @ BWP has the same CORESET identifier as the ra-SearchSpace set for the DL @ BWP that has the same BWP identifier as the active UL @ BWP. That is not to do. Alternatively, condition D is that the ra-SearchSpace set for the active DL @ BWP has the same BWP identifier as the active UL @ BWP, and the same RESET identifier as the ra-SearchSpace set for the DL @ BWP. Is not associated with Alternatively, the condition D is that the identifier of the RESET shown in the ra-SearchSpace set for the active DL @ BWP is set for the DL @ BWP having the same BWP identifier as the active UL @ BWP. This is different from the CORSET identifier shown in the SearchSpace. Satisfaction of the condition D may mean that both the condition E and the condition F are not satisfied. Unsatisfaction of condition D may mean that either condition E or condition F is satisfied. Conditions E and F will be described later.

Process A is for the MAC entity to switch the active UL BWP to the initial UL BWP. Process B is that the MAC entity switches the active DL @ BWP to the initial DL @ BWP. Process C is for the MAC entity to switch the active DL @ BWP to a DL @ BWP having the same BWP identifier as the active UL @ BWP. Process D is that the MAC entity performs a random access procedure on the active DL @ BWP of the SpCell and the active UL @ BWP of the serving cell.

In FIG. 9, the MAC entity may determine which step to select and proceed next based on the condition A in S11. If the condition A is not satisfied, the MAC entity proceeds to S15. If the condition A is satisfied, the MAC entity proceeds to S12. That is, when the condition A is satisfied, the MAC entity executes the process A of S12. Subsequently, the MAC entity determines the condition B in S13. If the condition B is satisfied, the MAC entity executes the process B. If the condition B is not satisfied, the MAC entity proceeds to S20. That is, when the condition A and the condition B are satisfied, the MAC entity executes the process B. If the condition A is satisfied and the condition B is not satisfied, the MAC entity proceeds to S20.

S15 is that the condition A is not satisfied. That is, S15 is that the PRACH opportunity is set for the active UL @ BWP. Proceeding to S15, the MAC entity may determine which step to select and proceed next based on condition B of S16. Here, if the condition B of S16 is not satisfied, the MAC entity proceeds to S20. That is, when the condition A is not satisfied and the condition B is not satisfied, the MAC entity proceeds to S20.

$ If the condition B of S16 is satisfied, the MAC entity proceeds to S17. Here, when the condition C and the condition D are satisfied, the MAC entity executes the process C of S19. That is, when the condition A is not satisfied, the condition B is satisfied, the condition C is satisfied, and the condition D is satisfied, the MAC entity executes the process C of S19. If the condition A is not satisfied, the condition B is satisfied, and at least one of the condition C and the condition D is not satisfied, the MAC entity does not execute the process C of S19, and proceeds to S20. In S20, the MAC entity executes the process D.

FIG. 11 is a diagram showing another example of the pseudo code related to the MAC entity determining the BWP switching for the serving cell at the start of the random access procedure in the serving cell.

Also, in FIG. 9, the MAC entity that starts the random access procedure in a certain serving cell sets the active UL @ BWP to the initial (initial) UL @ BWP when the PRACH opportunity is not set for the active UL @ BWP. Switch. Then, when the serving cell is SpCell and ra-SearchSpace is not set for the active DL @ BWP (S13), the MAC entity switches the active DL @ BWP to the initial (initial) @ DL @ BWP. . That is, in FIG. 9, the condition of S13 may be that the serving cell is SpCell and / or that no ra-SearchSpace is set for the active DL @ BWP.

In the following embodiment, the first information is the ra-SearchSpace set for the first DL @ BWP. The second information is the ra-SearchSpace set for the second DL @ BWP having the same BWP identifier as the first UL @ BWP. The first UL @ BWP is the UL @ BWP set to the active UL @ BWP at this time. The first DL @ BWP is the DL @ BWP set to the active DL @ BWP at this time. The second DL @ BWP is a DL @ BWP having the same BWP identifier as the first UL @ BWP.

In aspect A of this embodiment (steps subsequent to S15), the control resource set associated with the first information set for the first DL @ BWP has the same BWP identifier as the first UL @ BWP. Switch the active DL @ BWP to the second DL @ BWP based on whether or not it has the same CORRESET identifier as the control resource set (CORESET) associated with the second information set for the second DL @ BWP Determine whether or not. For example, the MAC entity may change the active DL @ BWP to the first DL if the control resource set (CORESET) associated with the first information does not have the same CORESET identifier as the control resource set associated with the second information. You may switch from BWP to 2nd DL @ BWP. The MAC entity converts the active DL @ BWP from the first DL @ BWP to the second DL if the control resource set associated with the first information has the same CORRESET identifier as the control resource set associated with the second information. It is not necessary to switch to BWP. The MAC entity determines that the serving cell is a SpCell, and a PRACH opportunity is set for a first UL @ BWP set to an active UL @ BWP, and a first is set to an active DL @ BWP. The above determination may be made when the DL @ BWP does not have the same BWP identifier as the first UL @ BWP.

In other words, in other words in aspect A, the MAC entity determines whether the identifier of the coreset indicated (included) in the first information is the same as the identifier of the coreset indicated (included) in the second information. , Determine whether to switch the active DL @ BWP to the second DL @ BWP. The MAC entity may switch the active DL @ BWP from the first DL @ BWP to the second DL @ BWP when the identifier of the RESET shown in the first information is different from the identifier of the RESET shown in the second information. Good. The MAC entity does not switch the active DL @ BWP from the first DL @ BWP to the second DL @ BWP when the identifier of the RESET shown in the first information is the same as the identifier of the RESET shown in the second information. You may. The MAC entity determines that the serving cell is a SpCell, and a PRACH opportunity is set for a first UL @ BWP set to an active UL @ BWP, and a first is set to an active DL @ BWP. The above determination may be made when the DL @ BWP does not have the same BWP identifier as the first UL @ BWP.

態様 The mode B (steps after S15) of the present embodiment will be described. In the aspect B, the condition E is that the BWP identifier of the DL @ BWP in which the setting information of the RESET specified by the identifier of the RESET shown in the first information is set is the same as the BWP identifier of the first UL @ BWP. It is. Alternatively, the condition E is that UL @ BWP having the same BWP identifier as DL @ BWP in which the RESET setting information specified by the RESET identifier indicated in the first information is set is the first UL @ BWP. is there. Condition F is that the DL @ BWP in which the RESET setting information specified by the RESET identifier indicated in the second information is set is the active DL @ BWP.

In aspect B of the present embodiment, the MAC entity does not have to switch the active DL @ BWP from the first DL @ BWP to the second DL @ BWP when either of the condition E or the condition F is satisfied. . Further, the MAC entity may switch the active DL @ BWP from the first DL @ BWP to the second DL @ BWP when both the condition E and the condition F are not satisfied. The MAC entity determines that the serving cell is a SpCell, and a PRACH opportunity is set for a first UL @ BWP set to an active UL @ BWP, and a first is set to an active DL @ BWP. When the DL @ BWP does not have the same BWP identifier as the first UL @ BWP, the above-described conditions E and F may be determined.

In aspect C of this embodiment, the MAC entity that starts the random access procedure in a certain serving cell changes the active UL @ BWP to the initial (initial) UL @ BWP when no PRACH opportunity is set for the active UL @ BWP. Switch. Then, the MAC entity determines that the serving cell is SpCell and that the setting information of the RESET specified by the identifier of the RESET shown in the first information set for the active DL @ BWP is the initial DL @ BWP. It is determined whether to switch the active DL @ BWP to the initial DL @ BWP (or the first active DL @ BWP) based on whether or not the active DL @ BWP is set. For example, the MAC entity determines that the serving cell is SpCell and that the configuration information of the RESET specified by the identifier of the RESET shown in the first information set for the active DL @ BWP is the initial DL @ BWP. If it is set, it is not necessary to switch the active DL @ BWP to the initial DL @ BWP. Also, the MAC entity indicates that the serving cell is SpCell, and the configuration information of the RESET specified by the identifier of the RESET shown in the first information set for the active $ DL @ BWP is other than the initial DL @ BWP. If it is set for another DL @ BWP, the active DL @ BWP may be switched to the initial DL @ BWP.

In aspect D of the present embodiment, the MAC entity that starts the random access procedure in a certain serving cell changes the active UL @ BWP to the initial (initial) UL @ BWP when the PRACH opportunity is not set for the active UL @ BWP. Switch. Then, the MAC entity determines the active DL @ BWP as the first DL based on whether or not the serving cell is SpCell and the RESET specified by the RESET identifier indicated in the first information is the common RESET. It is determined whether to switch from BWP to the second DL @ BWP. For example, if the serving cell is SpCell, and the CORESET specified by the CORSET identifier indicated in the first information is a common CORESET, the MAC entity changes the active DL @ BWP from the first DL @ BWP to the second DL @ BWP. It is not necessary to switch to DL @ BWP. In other words, if the serving cell is SpCell and the RESET specified by the RESET identifier indicated in the first information is not the common RESET, the MAC entity changes the active DL @ BWP from the first DL @ BWP to the second DL You may switch to BWP.

Also, in the aspect E (steps after S15) of the present embodiment, the MAC entity determines that the coreset specified by the coreset identifier indicated in the first information set for the first DL @ BWP is the common coreset. Is determined based on whether the active DL @ BWP is switched to the second DL @ BWP. For example, if the coreset specified by the identifier of the coreset indicated in the first information set for the first DL @ BWP is a common coreset, the MAC entity changes the active DL @ BWP to the first DL @ BWP. It is not necessary to switch from to the second DL @ BWP. In addition, the MAC entity converts the active DL @ BWP into the first DL @ BWP if the CORESET specified by the identifier of the CORESET shown in the first information set for the first DL @ BWP is not the common CORESET. May be switched to the second DL BWP. The MAC entity determines that the serving cell is a SpCell and that a PRACH opportunity is set for a first UL @ BWP that is set to an active UL @ BWP and that a first UL is set to an active DL @ BWP. The above processing may be performed when the DL @ BWP does not have the same BWP identifier as the first UL @ BWP.

Also, in the above aspect, the MAC entity may satisfy the above condition that the active DL @ BWP is not switched from the first DL @ BWP to the second DL @ BWP, and associate the MAC entity with the PDCCH monitor indicated in the first information. If the parameter to be performed and the parameter related to the PDCCH monitor indicated in the second information indicate the same value, it is not necessary to switch the active DL @ BWP from the first DL @ BWP to the second DL @ BWP. That is, if the above condition that the active DL @ BWP is not switched from the first DL @ BWP to the second DL @ BWP is satisfied, the MAC entity and the parameter related to the PDCCH monitor indicated in the first information and the second May be switched from the first DL @ BWP to the second DL @ BWP if the parameters related to the PDCCH monitor indicated in the information of the above do not indicate the same value. For example, the parameter related to the PDCCH monitor included in the ra-SearchSpace may be monitoringSlotPeriodicityAndOffset. monitoringSlotPeriodicityAndOffset is used to set the period and offset for PDCCH monitoring. The parameter associated with the PDCCH monitor may be monitoringSymbolsWithinSlot. monitoringSymbolsWithinSlot is used to indicate the first symbol of CORESET in the slot for PDCCH monitoring.

In FIG. 11, the MAC entity may determine which step to select and proceed next based on whether a PRACH opportunity has been set for the active UL @ BWP. When the PRACH opportunity is not set for the active UL @ BWP (S21), the MAC entity switches the active UL @ BWP to the initial UL @ BWP (S22), and proceeds to S23. If the PRACH opportunity has been set for the active UL @ BWP, the MAC entity proceeds to S23.

{Also, as another example, the MAC entity may determine which step to select and proceed next based on whether a PRACH opportunity has been set for the active UL @ BWP. When the PRACH opportunity is not set for the active UL @ BWP (S21), the MAC entity switches the active UL @ BWP to the initial UL @ BWP (S22), and proceeds to S23A. If the PRACH opportunity has been set for the active UL @ BWP, the MAC entity proceeds to S23A. The condition of S23A may be that the serving cell is SpCell and / or that no ra-SearchSpace is set for the active DL @ BWP. When the condition of S23A is satisfied, the MAC entity switches the active DL @ BWP to the initial (DL) BWP, and then proceeds to S27 (or S23). When the condition of S23A is not satisfied, the MAC entity proceeds to S23. That is, when the condition of S23A is not satisfied, the MAC entity may not switch the active DL @ BWP to the initial (initial) @ DL @ BWP.

(S23) Next, the MAC entity determines whether the serving cell in which the random access procedure is started is SpCell. If the serving cell is not an SpCell, the MAC entity performs a random access procedure in the active DL @ BWP of the SpCell and the active UL @ BWP of the serving cell (S27).

The MAC entity switches the active DL @ BWP to the DL @ BWP having the same BWP identifier as the active UL @ BWP when the serving cell is the SpCell (S23) and when the conditions of S24 and S25 are satisfied. , And S27 may be executed. If the serving cell is a SpCell (S23), and if at least one of the conditions of S24 and S25 is not satisfied, the MAC entity converts the active DL @ BWP into a DL having the same BWP identifier as the active UL @ BWP. S27 may be executed without switching to BWP. Here, the condition of S24 may be the condition C in FIG. 9 described above. The condition of S25 may be the condition D in FIG. 9 described above.

により With the above-described operation, it is possible to determine between the terminal device 1 and the base station device 3 an active DL @ BWP and an active UL @ BWP to be performed by the random access procedure.

As described above, the contention based random access procedure is initiated by a PDCCH order, MAC entity, notification of beam failure from lower layer, RRC, etc. When a beam failure notification is provided from the physical layer of the terminal device 1 to the MAC entity of the terminal device 1, if a certain condition is satisfied, the MAC entity of the terminal device 1 starts a random access procedure. When the beam failure notification is provided from the physical layer of the terminal device 1 to the MAC entity of the terminal device 1, a procedure for determining whether a certain condition is satisfied and starting a random access procedure is referred to as a beam failure recovery procedure. You may. This random access procedure is a random access procedure for a beam failure recovery request. The random access procedure initiated by the MAC entity includes a random access procedure initiated by a scheduling request procedure. The random access procedure for the beam failure recovery request may or may not be considered a random access procedure initiated by the MAC entity. Since the random access procedure for the beam failure recovery request and the random access procedure started by the scheduling request procedure may be different, a distinction is made between the random access procedure for the beam failure recovery request and the scheduling request procedure. You may do so. The random access procedure for the beam failure recovery request and the scheduling request procedure may be a random access procedure initiated by the MAC entity. In an embodiment, the random access procedure initiated by the scheduling request procedure is referred to as a random access procedure initiated by the MAC entity, and the random access procedure for the beam failure recovery request is referred to as a random access by a notification of a beam failure from a lower layer. It may be called a procedure. Hereinafter, the start of the random access procedure when the notification of the beam failure from the lower layer is received may mean the start of the random access procedure for the beam failure recovery request.

The terminal device 1 performs initial access from a state where the terminal device 1 is not connected (communicated) with the base station device 3 and / or uplink data or transmission that is connected to the base station device 3 but can be transmitted to the terminal device 1. A contention-based random access procedure is performed at the time of a scheduling request when possible side link data is generated. However, applications of contention-based random access are not limited to these.

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

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

The non-contention-based random access procedure may be started when the terminal device 1 receives, from the base station device 3, information indicating the start of the random access procedure. 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 a lower layer.

The non-contention based random access is performed between the terminal device 1 and the base station device 3 quickly 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 valid. May be used for uplink synchronization. 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 application of the non-contention based random access is not limited to these.

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

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

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

However, random access setting information may be set for each SS / PBCH block in the SS burst set, or one common random access setting information may be set for all SS / PBCH blocks in the SS burst set. Good. The terminal device 1 receives one or a plurality of random access setting information by a downlink signal, and each of the one or a plurality of random access setting information is an SS / PBCH block (CSI-RS or a downlink transmission beam. May be associated). The terminal device 1 selects one of the received one or a plurality of SS / PBCH blocks (which may be a CSI-RS or a downlink transmission beam) and is associated with the selected SS / PBCH block. A random access procedure may be performed using the random access setting information.

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 an upper layer parameter pach-ConfigIndex provided in an upper layer (upper layer signal). According to the PRACH setting (physical random access channel setting) index given by the "prach-ConfigIndex" and a predetermined table (also referred to as a random access channel setting (PRACH @ config) table), one that can be used for random access preamble transmission is used. 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 device 3.

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

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

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

For PRACH opportunities, the SSB index may be mapped according to the following rules.
(1) First, mapping is performed in ascending order of preamble index in one PRACH opportunity. For example, if the number of preambles of a PRACH opportunity is 64 and the number of random access preambles mapped to each SS / PBCH block at each PRACH opportunity is 32, the SSB indexes 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 index. For example, if two PRACH opportunities are frequency-multiplexed and the SSB indexes mapped to PRACH opportunities with small frequency resource indexes are n and n + 1, the SSB indexes mapped to PRACH opportunities with large frequency resource indexes are n + 2. n + 3.
(3) Third, a plurality of PRACH opportunities time-multiplexed in the PRACH slot are mapped in ascending order of the time resource index. For example, if two more PRACH opportunities are multiplexed in the PRACH slot in the time direction in addition to the example of (2) above, the SSB indexes mapped to these PRACH opportunities are n + 4, n + 5 and n + 6, n + 7. .
(4) Fourth, multiple PRACH slots are mapped in ascending index order. For example, when there is a RACH opportunity in the next PRACH slot in addition to the example of the above (3), the mapped SSB indexes 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. 7 is a diagram illustrating an example of SSB index allocation for PRACH opportunities according to an embodiment of the present invention. FIG. 7 shows that two PRACH slots exist in a certain time interval, two PRACH opportunities (ROs) exist in one PRACH slot in the time direction and two PRACH opportunities exist in the frequency direction, and the SSB index exists from 0 to 11. An example of the case is shown. Two SSB indices are mapped to one PRACH opportunity, SSB indices are mapped according to the rules (1) to (4), and SSB index 0 is mapped again from the seventh PRACH opportunity.

Although the SSB index is mapped to each PRACH opportunity, even when all the PRACH opportunities within the PRACH setting cycle specified by theprach-ConfigIndex are used, all the SSB indexes (all the SSS indexes transmitted by the base station apparatus 3) are used. / PBCH block), the SSB index may be mapped over multiple PRACH configuration periods. However, the number of all SS / PBCH blocks transmitted by the base station device 3 may be indicated by higher layer parameters. A cycle in which the PRACH setting cycle is repeated a predetermined number of times so that all SSB indexes are mapped at least once is referred to as an association cycle (association @ period). As the number of PRACH setting periods that constitute the association period, a minimum value that satisfies the above condition from a predetermined set of a plurality of values may be used. The set of the plurality of predetermined values may be determined for each PRACH setting cycle. However, if all the SSB indexes are mapped for the PRACH opportunities in the association cycle and the number of remaining PRACH opportunities is larger than the number of SS / PBCH blocks, the SSB indexes may be mapped again. Good. However, if all the SSB indices are mapped to the PRACH opportunities in the association cycle and the number of remaining PRACH opportunities is smaller than the number of SS / PBCH blocks, the remaining PRACH opportunities have SSB The index need not be mapped. A cycle in which a PRACH opportunity is assigned once for every SSB index is called an SSB index assignment cycle. If the SSB-perRACH-Occasion is 1 or more, each SSB index is mapped to one PRACH opportunity in one SSB index allocation cycle. If SSB-perRACH-Occasion is a value less than 1, each SSB index is mapped to PRACH opportunity of 1 / SSB-perRACH-Occasion 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 in the upper layer (upper layer signal). .

１ One or more random access preamble groups included in the random access setting information may be associated with each reference signal (eg, SS / PBCH block, CSI-RS, or downlink transmission beam). The terminal device 1 may select a 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 an upper layer. One of the one or more parameters may be an index (eg, a start index) of one or more available preambles. One of the one or more parameters may be a 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 a 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 and receives random access setting information associated with one downlink signal among the downlink signals. Then, a 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 information. A random access procedure may be performed based on the information. The terminal device 1 receives one or a plurality of CSI-RSs, receives random access setting information associated with one of the CSI-RSs, and performs a random access procedure based on the received random access setting information. May be performed.

パラメータ Parameters regarding random access for each reference signal may be included in the random access channel setting.

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

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

One 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 accesses 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 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. Is also good. For example, the terminal device 1 may transmit a 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 a downlink transmission beam to be applied when transmitting a 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 in the random access setting information associated with a certain downlink transmission beam. The base station apparatus 3 transmits the downlink signal to the terminal apparatus 1 based on the random access preamble received from the terminal apparatus 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 an RRC parameter including one or more pieces of random access setting information (which may include random access resources) as an RRC message.

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

As described above, the configuration information of the additional common coreset may be used to specify the additional common coreset used for the random access procedure. Also, in this embodiment, the additional common CORESET configuration information may be used to specify additional common CORESET for system information and / or paging procedures. That is, the additional common CORESET may be used for receiving SIB1 and / or SI messages (other \ system \ information, for example, SIB2 and SIB after SIB2), paging, and RAR. Stated another way, the common search space set for SIB1 (eg, type 0 PDCCH common search space set) may be associated with an additional common coreset. A common search space set for SI messages (eg, type 0 APDCCH common search space set) may be associated with an additional common CORRESET. A common search space set for paging (eg, type 2 PDCCH common search space set) may be associated with an additional common CORRESET. A common search space set for the RAR (eg, a type 1 PDCCH common search space set) may be associated with an additional common coreset.

In the present embodiment, the type 0 PDCCH common search space (common search space for SIB1) may be set by searchSpaceZero included in MIB or searchSpaceSIB1 included in ServingCellConfigCommon.

When the upper layer parameter searchSpaceOtherSystemInformation is not provided to the terminal device 1, the association between the PDCCH monitoring opportunity (monitoring @ occasions) for the type 0 APDCCH common search space set and the SS / PBCH block index is the PDCCH monitoring opportunity for the type 0 PDCCH common search space set. And the association with the SS / PBCH block index. Also, when the upper layer parameter pagingSearchSpace is not provided to the terminal device 1, the association between the PDCCH monitoring opportunity (monitoring @ occasions) for the type 2 PDCCH common search space set and the SS / PBCH block index is the PDCCH for the type 0 PDCCH common search space set. It may be the same as the association between the monitoring opportunity and the SS / PBCH block index.

In this embodiment, the initial DL BWP is the number of PRB locations and consecutive PRBs for the control resource set (CORESET, CORRESET # 0) for the type 0 PDCCH common search space, the subcarrier spacing, and It may be defined by a cyclic prefix. That is, the initial DL BWP may be set by pdcch-ConfigSIB1 included in MIB or PDCCH-ConfigCommon included in ServingCellConfigCommon. The information element ServingCellConfigCommon is used to set a cell-specific parameter of the serving cell for the terminal device 1. Specifically, the bandwidth of the initial DL BWP is the bandwidth of CORRESET # 0. The controlResourceSetZero indicating the setting information of CORRESET # 0 corresponds to 4 bits (for example, 4 bits of MSB, 4 bits of the most significant bit) of pdcch-ConfigSIB1. The controlResourceSetZero may be included in PDCCH-ConfigSIB1 or PDCCH-ConfigCommon. SearchSpaceZero indicating the setting information of SearchSpace # 0 (search space # 0) corresponds to 4 bits (for example, 4 bits of LSB, 4 bits of the least significant bit) in pdcch-ConfigSIB1. That is, the size of the initial DL BWP is N ^size _{BWP, 0} (the first size, the size of the RESET). N ^size _{BWP, 0} is the number of resource blocks indicating the bandwidth of the initial DL BWP. Here, the initial DL BWP may be referred to as a first size initial DL BWP.

Further, the terminal device 1 may be provided with the initial DL BWP by SIB1 (systemInformationBlockType1) or ServingCellConfigCommon (for example, ServingCellConfigCommonSIB). Specifically, the initial DL BWP is indicated by the upper layer parameter locationAndBandwidth included in BWP-DownlinkCommon. The position and bandwidth of the frequency domain of the initial DL BWP may be given based on the locationAndBandwidth. The information element BWP-DownlinkCommon may be included in ServingCellConfigCommon or SIB1. The information element ServingCellConfigCommonSIB is used to set a cell-specific parameter of a serving cell for the terminal device 1 in the SIB1. In this case, the size of the initial DL BWP is N ^size _{BWP, 1} . That is, N ^size _{BWP, 1} is the number of resource blocks of the initial DL BWP indicated by SIB1 (SystemInformationBlockType1) or ServingCellConfigCommon. N ^size _{BWP, 1} may be equal to N ^size _{BWP, 0} _. N ^size _{BWP, 1} may be different from N ^size _{BWP, 0} . Here, the initial DL BWP may be referred to as an initial DL BWP of size N ^size _{BWP, 1} (second size).

In the present embodiment, there may be two initial DLs BWP. In this case, the initial DL @ BWP may be distinguished as a first size initial DL @ BWP and a second size initial DL @ BWP.

In the present embodiment, there may be one initial DL BWP. In this case, the initial DL @ BWP is the above-described initial DL @ BWP of the second size. Then, the above-mentioned initial DL @ BWP of the first size may be referred to as a bandwidth (size) of CORESET # 0. Also, the initial DL @ BWP of the first size may be referred to as an initial active DL @ BWP. That is, the initial active DL @ BWP is the number of PRB locations and the number of consecutive PRBs for the control resource set (CORESET, CORRESET # 0) for the type 0 PDCCH common search space, the subcarrier interval, and the cyclic. May be defined by a prefix. That is, in this embodiment, the initial DL @ BWP may mean the initial DL @ BWP of the second size unless otherwise specified.

The terminal device 1 may be provided with the initial UL \ BWP by SIB1 (systemInformationBlockType1) or initialUplinkBWP. The information element initialUplinkBWP is used to set an initial UL @ BWP.

よう As described above, a plurality of DLＷBWPs may be set for the terminal device 1. Then, of the DL @ BWP set for the terminal device 1, the default DL @ BWP can be set by the upper layer parameter defaultDownlinkBWP-Id. When the upper layer parameter defaultDownlinkBWP-Id is not provided to the terminal device 1, the default DL @ BWP is the initial DL @ BWP. Here, the initial DL @ BWP may be the initial DL @ BWP of the second size.

In the following, a description will be given of a condition in this embodiment in which an additional BWP refers to the setting information of CORET # 0 and / or SearchSpace # 0.

{As described above, the setting information of CORRESET # 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 DL @ BWP. The setting information of SearchSpace # 0 is included in the setting of the initial DL @ BWP. The setting information of SearchSpace # 0 may not be included in the setting of BWP (additional BWP) other than the initial DL @ BWP. When BWPs (additional BWPs) other than the initial DL @ BWP refer to the setting information of the RESET # 0 and / or the setting information of the SearchSpace # 0 (refer, @acquire, etc.), the RESET # 0 and the SS block in the frequency domain. It may be necessary to at least satisfy that it is included in the additional BWP and uses the same subcarrier spacing. Using the same subcarrier interval means that the subcarrier interval for the additional DL @ BWP and the subcarrier interval for the initial DL @ BWP (or CORRESET # 0) are the same. Stated another way, if a BWP other than the initial BWP (additional BWP) refers to CORRESET # 0 and / or SearchSpace # 0 (refer, @acquire, etc.), the initial DL @ BWP bandwidth and It may be necessary to at least satisfy that the SS block is included in the additional BWP and use the same subcarrier spacing. At this time, the search space set for the additional BWP can refer to the setting information of CORESET # 0 (refer, @acquire, etc.) by indicating the identifier 0 of CORESET # 0. That is, at this time, although the RESET # 0 is set only for the initial DL @ BWP, the terminal device 1 operating with another BWP (additional BWP) refers to the setting information of the RESET # 0. Can be. The search space set for the additional BWP can refer to the setting information of SearchSpace # 0 (refer, @acquire, etc.) by indicating the search space identifier 0. That is, at this time, SearchSpace # 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 SearchSpace # 0. Can be.

Also, in the frequency domain, the bandwidth of the initial DL BWP (or the bandwidth of CORRESET # 0) is included in the additional DL BWP, and the SS block is included in the additional DL BWP, and uses the same subcarrier interval. If any of the conditions is not satisfied, the terminal device 1 does not have to expect that the additional DL BWP refers to the setting information of CORET # 0 and / or the setting information of SearchSpace # 0. That is, in this case, the base station apparatus 3 does not have to set the additional DL BWP for the terminal apparatus 1 to refer to the setting information of CORRESET # 0 and / or the setting information of SearchSpace # 0. Here, the initial DL BWP may be an initial DL BWP of size N ^size _{BWP, 0} (first size). Further, the initial DL BWP may be an initial DL BWP of a size N ^size _{BWP, 1} (second size).

The SS block described above may be associated with the initial DL BWP. The SS block may be a cell-defining @ SS block for a cell. The cell-defining @ SS block may be associated with CORRESET # 0. The terminal device 1 may determine the RESET (CORESET # 0) for the type 0 PDCCH common search space set by the Cell-defining @ SS block. An SS block that is not cell-defining @ SS block does not have to be associated with CORRESET # 0. That is, the terminal device 1 cannot acquire the setting information of CORESET # 0 by an SS block that is not the cell-defining @ SS block.

In the present embodiment, the base station device 3 may start the RRC reconfiguration procedure for the terminal device 1 in the RRC connection state for a specific purpose. The purpose of the RRC reconfiguration procedure (RRC reconfiguration procedure) is to change the RRC connection (RRC connection) to the terminal device 1. For example, establishing / changing / releasing radio bearers, performing reconfiguration with synchronization, setting / changing / releasing measurements, adding / changing / releasing SCells and cell groups. It is to be. The RRCReconfiguraton message is a command for changing the RRC connection. The RRCReconfiguraton message may include a masterCellGroup. masterCellGroup is used for configuration of a master cell group (MCG). CellGroupConfig in masterCellGroup includes spCellConfig. spCellConfig is a PCell parameter of MCG. In the case of changing the SpCell, adding the PSCell, and changing the security key, spCellConfig always includes the reconfigurationWithSync field. reconfigurationWithSync is a parameter for synchronous reconfiguration to the target SpCell.

Then, when reconfigurationWithSync is included in spCellConfig of the MCG, if the common search space is set for the active DL @ BWP, or the above-described CORRESET # 0 and / or SearchSpace # 0 If the condition for referring to the setting information is satisfied, the SIB1 of the target SpCell of the MCG may be acquired (acquire). The active DL @ BWP is indicated by the firstActiveDownlinkBWP-Id for the target SpCell of the MCG. In this case, the active DL @ BWP may be referred to as the first active DL @ BWP (first @ active @ DL @ BWP). In this embodiment, in addition of SpCell (PCell or PSCell) or activation of SCell, one BWP is first active without receiving a PDCCH indicating a downlink assignment or an uplink grant. First, the active DL @ BWP and UL @ BWP (first @ active @ UL @ BWP) may be specified in the RRC message sent from the base station apparatus 3 to the terminal apparatus 1. The active BWP for a certain serving cell is specified by RRC or PDCCH sent from the base station device 3 to the terminal device 1. In addition, the first active DL {BWP} (first active DL DL BWP) and UL BWP (first active UL UL BWP) may be included in the message 4.

The fact that the common search space is set for the {active DL} BWP may mean that the information element PDCCH-configcommon for the DL @ BWP indicates a common search space for the SIB1 (for example, searchSpaceSIB1). The terminal device 1 monitors the DCI format for scheduling the SIB1 based on the information indicated in the common search space and the setting information of the RESET associated with the common search space. The terminal device 1 can acquire the SIB1 of the target SpCell of the MCG by detecting the DCI format.

In addition, even if the common search space is not set for the active DL @ BWP, the terminal device 1 can set the target of the MCG when the condition for referring to the setting information of CORRESET # 0 and / or SearchSpace # 0 is satisfied. The SCell 1 of the SpCell may be acquired. That is, even if the common search space is not set for the active DL @ BWP, the terminal apparatus 1 includes the bandwidth of the initial DL @ BWP and the SS block in the frequency domain and includes the same subcarrier If the condition using the interval is satisfied, SIB1 of the target SpCell of the MCG may be acquired. At this time, the terminal device 1 monitors the DCI format for scheduling the SIB1 based on the setting information of SearchSpace # 0 and the setting information of CORRESET # 0. The terminal device 1 can acquire the SIB1 of the target SpCell of the MCG by detecting the DCI format.

Here, the DCI format for scheduling SIB1 may be DCI format 1_0 to which CRC parity bits scrambled by SI-RNTI or SIB1-RNTI are added. SI-RNTI may be used for broadcasting system information. SIB1-RNTI may be used for broadcasting system information of SIB1.

Hereinafter, a description will be given of a condition in the present embodiment in which the additional BWP refers to the setting information of the additional common CORESET set for the initial DL @ BWP.

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

More specifically, for example, if the common search space is not set for the active DL @ BWP, the terminal device 1 may add the additional DL in which the active DL @ BWP is set for another BWP in the frequency domain. Includes the bandwidth of the common CORESET (or the bandwidth of another BWP), and the active DL @ BWP includes another BWP (an additional common CORESET set for the other BWP) (or SIB1 may be acquired in the case of including the (related) SS block and using the same subcarrier interval. At this time, the terminal device 1 monitors the DCI format for scheduling the SIB1 based on the setting information of the additional common CORESET and the setting information of the common search space related to the additional common CORESET. The terminal device 1 can acquire the SIB1 by detecting the DCI format. Here, the common search space may be a common search space for SIB1. That is, for other BWPs, the common search space for SIB1 may be associated with an additional common coreset. Another BWP for which the additional common CORESET is set may be the initial DL @ BWP. Further, another BWP in which the additional common CORESET is set may be additional DL @ BWP. Here, when the other BWP is the initial DL @ BWP, the common search space for SIB1 may be SearchSpace # 0 indicated by searchSpaceZero, or the common search space indicated by searchspaceSIB1 (other than search space identifier 0). Common search space). If the other BWP is additional DL @ BWP, the common search space for SIB1 may be the common search space indicated by searchspaceSIB1 (common search space other than search space identifier 0).

Further, as an extension of the above example, for example, when the SS block associated with another BWP (an additional common CORESET set for another BWP) is a cell-defining @ SS block under the above conditions, The active DL @ BWP may not include the SS block that the other BWP includes (associated with). In other words, even if the active DL @ BWP does not include the SS block included in (related to) the other BWP, the active DL @ BWP does not include the additional common coreset bandwidth (or the other BWP bandwidth). ) And using the same subcarrier interval, additional common CORESET setting information may be obtained. That is, in this case, if the common search space is not set for the active DL @ BWP, the terminal device 1 sets the additional common CORESET in which the active DL @ BWP is set for another BWP in the frequency domain. The SIB1 may be acquired (acquired) when the bandwidth includes the bandwidth (or other BWP bandwidth) and uses the same subcarrier interval.

Also, if the SS block associated with another BWP (additional common CORESET set for another BWP) is not a cell-defining @ SS block, the active DL @ BWP includes (related) the other BWP. It is necessary to include the SS block. When the active DL @ BWP does not include the SS block included in (related to) the other BWP, the terminal device 1 acquires the setting information of the additional common CORESET set for the other BWP in the active DL @ BWP. Can not do it. In this case, if the common search space is not set for the active DL @ BWP, the terminal device 1 sets the bandwidth of the additional common CORRESET in which the active DL @ BWP is set for another BWP in the frequency domain. SS block that contains (or the bandwidth of another BWP), and that the active DL @ BWP contains (or is associated with) another BWP (an additional common coreset set for the other BWP) And when the same subcarrier interval is used, SIB1 may be acquired.

In the present embodiment, the base station device 3 requests the terminal device 1 for the capability information of the terminal device 1 using a UECapabilityEnquiry message. That is, the UECapabilityEnquiry message is used to request the wireless access capability of the terminal device 1 for the NR and other RATs (Radio Access Technology, a wireless access method). Then, the terminal device 1 that has received the UECapabilityEnquiry message transmits (reports) the capability information to the base station device 3.

ケイ The capability information of the terminal device 1 to be transmitted to the base station device 3 may include capability information relating to the BWP operation. For example, the first BWP operation capability information may indicate that an additional BWP may be configured in the frequency domain that may not include either or both of the initial DL BWP bandwidth and / or SS blocks for the cell. .

If the terminal device 1 does not indicate the first BWP operation capability, the base station device 3 adds, to the terminal device 1, an additional bandwidth including both the initial DL @ BWP bandwidth and the SS block for the cell in the frequency domain. Set only BWP. When the terminal device 1 indicates the first BWP operation capability, the base station device 3 provides the terminal device 1 with any one of the initial DL @ BWP bandwidth and the SS block for the cell in the frequency domain, or An additional BWP that does not need to include both may be set.

In the present embodiment, when the terminal device 1 indicates the first BWP operation capability, the condition for referring to the above-described setting information of CORRESET # 0 and / or SearchSpace # 0 may be changed. For example, when the terminal device 1 indicates the first BWP operation capability, and the additional BWP includes the bandwidth of the initial DL BWP (CORESET # 0) in the frequency domain, and the same subcarrier interval as the initial DL BWP If the terminal device 1 is used, the terminal device 1 can refer to CORRESET # 0 and / or SearchSpace # 0 (refer, $ acquire, etc.) with additional BWP. Here, the additional BWP may not include the SS block of the cell. However, the terminal device 1 does not show the first BWP operation capability, and the additional BWP includes the bandwidth of the initial DL @ BWP (CRESET # 0) in the frequency domain, and has the same subcarrier interval as the initial DL @ BWP. When used, and if the additional BWP does not include the SS block of the cell, the terminal device 1 cannot refer to CORRESET # 0 and / or SearchSpace # 0 (refer, @acquire, etc.) with the additional BWP.

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

FIG. 12 is a schematic block diagram showing the configuration of the terminal device 1 of the present 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 transmitting / receiving unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transmission / reception unit 10 is also called a transmission unit, a reception unit, a monitor unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a measurement unit, a selection unit, or a control unit.

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

(4) The medium access control layer processing unit 15 provided in the upper layer processing unit 14 performs processing of a 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.

(4) 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 the 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 information indicating various setting information / parameters 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 the transmission signal to the base station device 3. The wireless transmission / reception unit 10 may have a function of receiving one or a plurality of reference signals in a certain cell. The wireless transmission / reception unit 10 may have a function of receiving information (for example, SSB index information and / or mask index information) specifying one or a plurality of PRACH opportunities. The wireless transmission / reception unit 10 may have a function of receiving a signal including instruction information for instructing start of a random access procedure. The wireless transmission / reception unit 10 may have a function of receiving information for receiving information for specifying a predetermined index. The wireless transmission / reception unit 10 may have a function of receiving information for specifying an index of a random access preamble. The wireless transmission / reception unit 10 may have a function of transmitting a random access preamble at the PRACH opportunity determined by the upper layer processing unit 14.

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

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

The baseband unit 13 performs an inverse fast Fourier transform (Inverse フー Fast Fourier Transform: IFFT) on the data, generates an OFDM symbol, adds a CP to the generated OFDM symbol, generates a baseband digital signal, The digital signal of the band is converted into an analog signal. The baseband unit 13 outputs the converted analog signal to the RF unit 12.

The RF unit 12 removes extra frequency components from the analog signal input from the baseband unit 13 using a low-pass filter, up-converts the analog signal to a carrier frequency, and transmits the analog signal via the antenna unit 11. I do. 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 called a transmission power control unit.

FIG. 13 is a schematic block diagram showing the configuration of the base station device 3 of the present embodiment. As illustrated, the base station device 3 is configured to include a radio 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 is configured to include a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transmission / reception unit 30 is also referred to as a transmission unit, a reception unit, a monitor unit, or a physical layer processing unit. Further, a control unit for controlling the operation of each unit based on various conditions may be separately provided. The upper layer processing unit 34 is also called a terminal control unit.

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

(4) 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 a process related to a scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 36.

(4) 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 data (transport block), system information, RRC message, MAC @ CE (Control @ Element), and the like arranged in the physical downlink shared channel, or obtains it from the upper node. , 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 of the terminal devices 1 via a signal of an upper layer. That is, the radio resource control layer processing unit 36 transmits / reports information indicating various setting information / parameters. The radio resource control layer processing unit 36 may transmit / broadcast information for specifying settings of a plurality of reference signals in a certain cell.

When transmitting an RRC message, MAC @ CE, and / or PDCCH from the base station apparatus 3 to the terminal apparatus 1 and performing processing based on the reception, the base station apparatus 3 The processing (control of the terminal device 1 and the system) is performed assuming that the processing is performed. That is, the base station device 3 sends the terminal device 1 an RRC message, MAC @ CE, and / or 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 a plurality of reference signals. Further, the wireless transmission / reception unit 30 may have a function of receiving a signal including a beam failure recovery request transmitted from the terminal device 1. The wireless transmission / reception unit 30 may have a function of transmitting information (for example, SSB index information and / or mask index information) specifying one or a plurality of PRACH opportunities to the terminal device 1. The wireless transmission / reception unit 30 may have a function of transmitting information specifying a predetermined index. The wireless transmission / reception unit 30 may have a function of transmitting information for 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 functions of the wireless transmission / reception unit 30 are the same as those of the wireless transmission / reception unit 10, and thus description thereof is omitted. When the base station device 3 is connected to one or a plurality of transmission / reception points 4, some or all of the functions of the radio transmission / reception unit 30 may be included in each transmission / reception point 4.

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

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

部 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 embodiment of the present invention determines the receiving unit 10 that receives the RRCReconfiguraton message, and the setting information of the search space and the setting information of the RESET for receiving the SIB1. A control unit 16 which performs the first parameter reconfigurationWithSync in the message, the control unit determines that the active DL @ BWP is a bandwidth of the initial DL @ BWP and the SS block to which the initial DL @ BWP is related in the frequency domain. If it is included and the same subcarrier interval as the initial DL @ BWP is used, the setting information of searchspace # 0 and the setting information of RESET # 0 are determined, and the setting information of the determined searchspace # 0 and the setting of RESET # 0 are determined. SIB1 is acquired by the active DL @ BWP based on the information, and the first parameter is acquired. Is a parameter for synchronous reconfiguration to the target cell SpCell, the RESET # 0 is set by controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is a parameter for the initial DL @ BWP. , Set by searchSpaceZero.

(2) The base station device 3 according to the second aspect of the present invention includes a transmitting unit 30 that transmits an RRCReconfiguraton message, and a control unit 36 that controls a search space for the terminal device to acquire the SIB1 and a RESET. If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the control unit determines that the active DL @ BWP operated by the terminal device is an SS block associated with the initial DL @ BWP bandwidth and the initial DL @ BWP in the frequency domain. And if the same subcarrier interval as the initial DL @ BWP is used, the terminal device is caused to acquire SIB1 by the active DL @ BWP based on the setting information of searchspace # 0 and the setting information of

CORRESET #

0, 1 parameter is synchronization to target cell SpCell This is a parameter for reconfiguration. The RESET # 0 is set by the controlResourceSetZero for the initial DL @ BWP, and the searchspace # 0 is set by the searchSpaceZero for the initial DL @ BWP.

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

The program that operates on 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 embodiment 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), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage system.

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

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, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other Logic devices, discrete gate or transistor logic, discrete hardware components, or a combination thereof. A general purpose processor may be a microprocessor, or may be a conventional processor, controller, microcontroller, or state machine. The above-described electric circuit may be constituted by a digital circuit or may be constituted by an analog circuit. In addition, in the case where a technology for forming an integrated circuit that replaces a current integrated circuit appears with the progress of semiconductor technology, one or more aspects of the present invention can use a new integrated circuit based on the technology.

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

発明 Note that the present invention is not limited to the above embodiment. In the embodiment, an example of the device is described. However, the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, for example, AV devices, kitchen devices, It can be applied to terminal devices or communication devices such as cleaning / washing equipment, air conditioning equipment, office equipment, vending machines, and other living equipment.

Although the embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to the embodiments, and may include design changes within the scope of the present invention. Further, the present invention can be variously modified within the scope shown in the claims, and the technical scope of the present invention includes embodiments obtained by appropriately combining technical means disclosed in different embodiments. It is. The elements described in the above embodiments also include a configuration in which elements having the same effects are replaced.

Claims

A terminal device that performs an RRC reconfiguration procedure,
A receiver for receiving the RRCReconfiguraton message,
A control unit for determining search space setting information and CORESET setting information for receiving SIB1,
With
When the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the control unit determines that the active DL BWP includes an SS block in which the initial DL BWP bandwidth and the initial DL BWP are related in the frequency domain, and the initial DL BWP and If the same subcarrier interval is used, the setting information of searchspace # 0 and the setting information of CORESET # 0 are determined, and based on the determined setting information of searchspace # 0 and the setting information of CORESET # 0, the active DL BWP is determined. To get SIB1,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The terminal device, wherein the searchspace # 0 is set by searchSpaceZero for the initial DL BWP.
A base station device that communicates with a terminal device that performs an RRC reconfiguration procedure,
A transmitting unit for transmitting an RRCReconfiguraton message,
A control unit that controls a search space and a RESET for the terminal device to acquire SIB1,
With
When the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the control unit determines that the active DL BWP operated by the terminal device is in the frequency domain, the initial DL BWP bandwidth and the SS block to which the initial DL BWP is related. Including, and if the same subcarrier interval as the initial DL BWP is used, the terminal device is caused to acquire SIB1 by the active DL BWP based on the setting information of searchspace # 0 and the setting information of CORRESET # 0,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The search space # 0 is set by searchSpaceZero with respect to the initial DL BWP.
A communication method of a terminal device performing an RRC reconfiguration procedure,
Receive RRCReconfiguraton message,
Determine search space setting information and CORESET setting information for receiving SIB1,
If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the active DL BWP includes the bandwidth of the initial DL BWP and the SS block to which the initial DL BWP is related in the frequency domain, and has the same subcarrier interval as the initial DL BWP. If used, the setting information of searchspace # 0 and the setting information of CORRESET # 0 are determined, and based on the determined setting information of searchspace # 0 and the setting information of CORRESET # 0, SIB1 is acquired by the active DL BWP. ,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The communication method in which searchspace # 0 is set by searchSpaceZero with respect to the initial DL BWP.
A communication method of a base station apparatus communicating with a terminal apparatus performing an RRC reconfiguration procedure,
Send RRCReconfiguraton message,
The terminal device controls a search space and a RESET for acquiring SIB1,
If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the active DL BWP operated by the terminal device includes an initial DL BWP bandwidth and an SS block associated with the initial DL BWP in a frequency domain, and If the same subcarrier interval as DL BWP is used, the terminal apparatus is caused to acquire SIB1 by the active DL BWP based on the setting information of searchspace # 0 and the setting information of CORRESET # 0,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The communication method in which searchspace # 0 is set by searchSpaceZero with respect to the initial DL BWP.
An integrated circuit mounted on a terminal device that performs an RRC reconfiguration procedure,
The ability to receive RRCReconfiguraton messages,
A function of determining the setting information of the search space for receiving the SIB1 and the setting information of the RESET;
If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the active DL BWP includes the bandwidth of the initial DL BWP and the SS block to which the initial DL BWP is related in the frequency domain, and has the same subcarrier interval as the initial DL BWP. If used, the setting information of searchspace # 0 and the setting information of CORRESET # 0 are determined, and based on the determined setting information of searchspace # 0 and the setting information of CORRESET # 0, SIB1 is acquired by the active DL BWP. ,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The searchspace # 0 is set by searchSpaceZero for the initial DL BWP integrated circuit.
An integrated circuit mounted on a base station device that communicates with a terminal device that performs an RRC reconfiguration procedure,
The ability to send RRCReconfiguraton messages,
A function of controlling a search space and a RESET in which the terminal device acquires SIB1, a function of controlling the base station device,
If the first parameter reconfigurationWithSync is included in the RRCReconfiguraton message, the active DL BWP operated by the terminal device includes an initial DL BWP bandwidth and an SS block associated with the initial DL BWP in a frequency domain, and If the same subcarrier interval as DL BWP is used, the terminal apparatus is caused to acquire SIB1 by the active DL BWP based on the setting information of searchspace # 0 and the setting information of CORRESET # 0,
The first parameter is a parameter for synchronous reconfiguration to the target cell SpCell,
The RESET # 0 is set by the controlResourceSetZero for the initial DL BWP,
The searchspace # 0 is set by searchSpaceZero for the initial DL BWP integrated circuit.