JP2022102123A - Terminal device, base station device, and communication method - Google Patents

Abstract

To allow a terminal device and a base station device to efficiently perform communication.SOLUTION: A terminal device transmits a random access preamble in a PRACH opportunity, receives DCI including a CRC bit scrambled with an RNTI in a PDCCH, and receives a random access response scheduled in the DCI. The value of the RNTI is calculated by using an index in a frequency domain of the PRACH opportunity and an index of an uplink BWP in which the PRACH opportunity is arranged.SELECTED DRAWING: Figure 17

Description

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

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

In the 5th generation cellular system, eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-latency and high-reliability communication, IoT (Internet of Things), etc. Three mMTCs (massive Machine Type Communication), in which a large number of machine-type devices are connected, are required as assumed scenarios for services. In addition, the future release of NR, Release 17, envisions applications such as sensor networks, surveillance cameras, and / or wearable devices, and does not require high requirements like eMBB or URLLC, while reducing costs and reducing battery power. A reduced capability (REDCAP) NR device for long life is being studied (Non-Patent Document 2).

RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016 RP-193238, Ericsson, “New SID on support of reduced capability NR devices”, December 2019

An object of the present invention is to provide a terminal device, a base station device, and a communication method that enable efficient communication in the above-mentioned wireless communication system.

(1) In order to achieve the above object, the aspect of the present invention has taken the following measures. That is, the terminal device according to one aspect of the present invention includes downlink control information including a transmitter that transmits a random access preamble on a physical random access channel (PRACH) opportunity and a CRC bit scrambled by a wireless network temporary identifier (RNTI). It comprises a receiver that receives (DCI) on a physical downlink control channel (PDCCH) and receives a random access response scheduled in said DCI, and the value of said RNTI is an index in the frequency region of said PRACH opportunity. And the index of the uplink BWP in which the PRACH opportunity is arranged, and calculated using.

(2) Further, the base station apparatus according to one aspect of the present invention is a receiver that receives a random access preamble from a terminal apparatus at a physical random access channel (PRACH) opportunity, and a CRC scrambled by a wireless network temporary identifier (RNTI). A transmitter that transmits downlink control information (DCI) including bits on a physical downlink control channel (PDCCH) and transmits a random access response scheduled by said DCI, wherein the value of the RNTI is the PRACH opportunity. It is calculated using the index in the frequency region of the above and the index of the uplink BWP in which the PRACH opportunity is arranged.

(3) Further, the communication method in one aspect of the present invention is a communication method of a terminal device, in which a random access preamble is transmitted at a physical random access channel (PRACH) opportunity and scrambled by a wireless network temporary identifier (RNTI). The downlink control information (DCI) including the CRC bit is received on the physical downlink control channel (PDCCH), the random access response scheduled by the DCI is received, and the value of the RNTI is the frequency region of the PRACH opportunity. It is calculated using the index in and the index of the uplink BWP in which the PRACH opportunity is arranged.

(4) Further, the communication method in one aspect of the present invention is the communication method of the base station device, in which a random access preamble is received from the terminal device at the opportunity of a physical random access channel (PRACH), and a wireless network temporary identifier ( The downlink control information (DCI) containing the CRC bits scrambled by RNTI) is transmitted on the physical downlink control channel (PDCCH), and the random access response scheduled by the DCI is transmitted, and the value of the RNTI is the PRACH opportunity. It is calculated using the index in the frequency region of the above and the index of the uplink BWP in which the PRACH opportunity is arranged.

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

It is a figure which shows the concept of the wireless communication system which concerns on embodiment of this invention. It is a figure which shows an example of the schematic structure of the uplink and the downlink slot which concerns on embodiment of this invention. It is a figure which showed the relationship in the time domain of the subframe, a slot, and a minislot which concerns on embodiment of this invention. It is a figure which shows an example of the structure of the RRC parameter PDCCH-ConfigSIB1-RC which is the information which shows the setting about PDCCH for REDCAP SIB1 which concerns on embodiment of this invention. It is a figure which shows an example of the table to which the value of controlResourceSetZero which concerns on embodiment of this invention is applied as an index. It is a figure which shows an example of the table to which the value of searchSpaceZero which concerns on embodiment of this invention is applied as an index. It is a figure which shows an example of the table of the index and the number of times of repeated transmission of PDCCH shown by the 2-bit parameter PDCCH-repetitions in the REDCAP MIB which concerns on embodiment of this invention. It is a figure which shows the example of the SS / PBCH block and SS burst set which concerns on embodiment of this invention. It is a figure which shows an example of the REDCAP PBCH block which concerns on embodiment of this invention, and the half frame which one or more REDCAP PBCH blocks are transmitted. It is a figure which shows the resource which DMRS for PSS, SSS, PBCH and PBCH is arranged in the SS / PBCH block which concerns on embodiment of this invention. It is a figure which shows the example of the REDCAP PBCH block which concerns on embodiment of this invention, and the half frame which one or more REDCAP PBCH blocks are transmitted. It is a figure which shows the resource which DMRS for REDCAP PBCH and REDCAP PBCH is arranged in the REDCAP PBCH block which concerns on embodiment of this invention. It is a figure which shows the example of the REDCAP PBCH block which concerns on embodiment of this invention. It is a figure which shows another example of the REDCAP PBCH block which concerns on embodiment of this invention. It is a figure which shows an example of the downlink transmission using a plurality of initial downlink sub-BWP which concerns on embodiment of this invention. It is a flow diagram which shows an example of the random access procedure using PDCCH order in the terminal apparatus 1 which concerns on embodiment of this invention. It is a flow diagram which shows an example of the random access procedure using RNTI in the terminal apparatus 1 which concerns on embodiment of this invention. It is a figure which showed an example of the beamforming which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the terminal apparatus 1 which concerns on embodiment of this invention. It is a schematic block diagram which shows the structure of the base station apparatus 3 which concerns on embodiment of this invention.

Hereinafter, embodiments of the present invention will be described.

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

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

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

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

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

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

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

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

In this embodiment, one or more serving cells may be set for the terminal device 1. The plurality of serving cells configured may include one primary cell and one or more secondary cells. The primary cell may be the serving cell in which the initial connection establishment procedure was performed, the serving cell in which the connection re-establishment procedure was initiated, or the cell designated as the primary cell in the handover procedure. good. One or more secondary cells may be configured when or after an RRC (Radio Resource Control) connection is established. However, the plurality of set serving cells may include one primary secondary cell. The primary secondary cell may be one or a plurality of secondary cells in which the terminal device 1 is set, and may be a secondary cell capable of transmitting control information on the uplink. Further, a subset of two types of serving cells, a master cell group and a secondary cell group, may be set for the terminal device 1. The master cell group may consist of one primary cell and zero or more secondary cells. A secondary cell group may consist of one primary secondary cell and zero or more secondary cells.

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

The subframe will be described below. In the present embodiment, the following is referred to as a subframe, but the subframe according to the present embodiment may be referred to as a resource unit, a radio frame, a time interval, a time interval, or the like.

FIG. 2 is a diagram showing an example of a schematic configuration of an uplink and a downlink slot according to the first embodiment of the present invention. Each of the radio frames is 10ms long. In addition, each radio frame is composed of 10 subframes and W slots. Also, one slot is composed of X OFDM symbols. That is, the length of one subframe is 1 ms. For each slot, the time length is defined by the subcarrier interval. For example, when the subcarrier interval of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X = 7 or X = 14, which are 0.5 ms and 1 ms, respectively. When the subcarrier interval is 60 kHz, X = 7 or X = 14, which are 0.125 ms and 0.25 ms, respectively. Further, for example, in the case of X = 14, W = 10 when the subcarrier interval is 15 kHz, and W = 40 when the subcarrier interval is 60 kHz. FIG. 2 shows the case of X = 7 as an example. Note that the example in FIG. 2 can be similarly extended in the case of X = 14. Further, the uplink slot is also defined in the same manner, and the downlink slot and the uplink slot may be defined separately. Further, the bandwidth of the cell in FIG. 2 may be defined as a partial band (BWP: BandWidth Part). Slots may also be defined as Transmission Time Intervals (TTIs). Slots do not have to be defined as TTIs. The TTI may be the transmission period of the transport block. However, the BWP on the uplink may be referred to as the uplink BWP, and the BWP on the downlink may be referred to as the downlink BWP. The BWP in the following description may be an uplink BWP and / or a downlink BWP. The BWP may also contain one or more bands called sub-BWPs. The sub BWP on the uplink may be referred to as the uplink sub BWP, and the sub BWP on the downlink may be referred to as the downlink sub BWP. One or more uplink BWPs, one or more uplink sub-BWPs, one or more downlink BWPs and / or one or more downlink sub-BWPs can be RRC messages, MAC CE, and / or It may be set for terminal device 1 by DCI.

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

The resource grid is used to represent the mapping of resource elements for a physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, if the subcarrier spacing is 15 kHz, then the number of OFDM symbols in the subframe is X = 14, and in the case of NCP, one physical resource block is 14 consecutive OFDM symbols in the time domain and in the frequency domain. Defined from 12 * Nmax consecutive subcarriers. Nmax is the maximum number of resource blocks (RB) determined by the subcarrier interval setting μ described later. That is, the resource grid is composed of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended CP), it is supported only at the subcarrier interval of 60kHz, so one physical resource block is, for example, 12 (the number of OFDM symbols contained in one slot) * 4 (included in one subframe) in the time domain. Number of slots) = 48 consecutive OFDM symbols and 12 * Nmax, μ consecutive subcarriers in the frequency domain. That is, the resource grid is composed of (48 * 12 * Nmax, μ) resource elements.

Reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined as resource blocks (RBs). One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, for example, resource blocks may be configured at subcarrier intervals of 15 kHz and numbered in ascending order. SubcarrierIndex 0 at Reference Resource Block Index 0 may be referred to as reference point A (may simply be referred to as "reference point"). The common resource block is a resource block numbered from 0 in ascending order in each subcarrier interval setting μ from the reference point A. The resource grid described above is defined by this common resource block. The physical resource block is a resource block numbered in ascending order from 0 contained in the partial band (BWP: BandWidth Part) described later, and the physical resource block is numbered in ascending order from 0 contained in the BWP. It is a resource block with. A physical uplink channel is first mapped to a virtual resource block. The virtual resource block is then mapped to the physical resource block. Hereinafter, the resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

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

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

Next, the subframe, the slot, and the mini slot will be described. FIG. 3 is a diagram showing an example of the relationship between the subframe, the slot, and the mini slot in the time domain. As shown in the figure, three types of time units are defined. The subframe is 1 ms regardless of the subcarrier interval, and the number of OFDM symbols contained in the slot is 7 or 14 (provided that the cyclic prefix (CP) attached to each symbol is Extended CP, 6). Or 12), the slot length depends on the subcarrier spacing. Here, if the subcarrier interval is 15 kHz, one subframe contains 14 OFDM symbols. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot may be referred to as PUSCH mapping type A.

A minislot (which may also be referred to as a subslot) is a time unit composed of fewer OFDM symbols than the number of OFDM symbols contained in one slot. The figure shows the case where the mini slot is composed of 2OFDM symbols as an example. The OFDM symbols in the minislot may match the OFDM symbol timings that make up the slot. The minimum unit of scheduling may be a slot or a mini slot. Also, allocating mini-slots may be referred to as non-slot-based scheduling. Also, scheduling a minislot may be expressed as 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. The uplink minislot may be referred to as PUSCH mapping type B.

In the terminal device 1, the transmission direction (uplink, downlink or flexible) of the symbols in each slot is set in the upper layer using an RRC message including a predetermined upper layer parameter received from the base station device 3. It is set by the PDCCH of a specific DCI format (for example, DCI format 2_0) received from the base station apparatus 3. In the present embodiment, a slot format in which each symbol in the slot sets any of uplink, downlink, and flexibility in each slot is referred to as a slot format. One slot format may include downlink symbols, uplink symbols and flexible symbols.

In the downlink of the present embodiment, the carrier corresponding to the serving cell is referred to as a downlink component carrier (or downlink carrier). In the uplink of the present embodiment, the carrier corresponding to the serving cell is referred to as an uplink component carrier (or uplink carrier). In the side link of the present embodiment, the carrier corresponding to the serving cell is referred to as a side link component carrier (or side link carrier). Downlink component carriers, uplink component carriers, and / or sidelink component carriers are collectively referred to as component carriers (or carriers).

The physical channel and the physical signal of this embodiment will be described.

In FIG. 1, the following physical channels may be used for wireless communication between the terminal device 1 and the base station device 3.

・ PBCH (Physical Broadcast CHannel)
・ REDCAP PBCH (REDuction CAPability Physical Broadcast Channel, R-PBCH)
・ 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)

PBCH is a critical information block (MIB: Master) that contains critical system information required by terminal unit 1.
Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) is used to notify. The MIB contains information for identifying the number (SFN: System Frame Number) of the radio frame (also called the system frame) to which the PBCH is mapped, and the subcarrier interval of the system information block 1 (SIB1: System Information Block 1). Information that identifies the frequency region between the grid of resource blocks and the SS / PBCH block (also known as sync signal block, SS block, SSB), and information about the PDCCH settings for SIB1. May be included. However, SIB1 contains information necessary for evaluating whether the terminal device 1 is allowed to connect to the cell, and includes information for determining the scheduling of other system information (SIB: System Information Block). However, the information indicating the PDCCH settings for SIB1 may be CORESET (ControlResourceSet) 0 (also referred to as common CORESET), common search space and / or information that determines the required PDCCH parameters. However, CORESET indicates the resource element of PDCCH, and CORESET0 is CORESET for PDCCH that schedules SIB1.

In addition, the PBCH is information for identifying the number (SFN: System Frame Number) of the radio frame (also referred to as a system frame) to which the PBCH is mapped, and / or the half radio frame (HRF) (half). It may be used to convey information that identifies (also referred to as a frame). However, the half radio frame is a time frame having a length of 5 ms, and the information for specifying the half radio frame may be information for specifying whether the first half 5 ms or the second half 5 ms of the 10 ms radio frame.

PBCH may also be used to signal the time index within the period of the SS / PBCH block. Here, the time index is information indicating the synchronization signal in the cell and the index of PBCH. The time index may be referred to as an SSB index or an SS / PBCH block index. For example, when transmitting an SS / PBCH block using multiple transmit beams, transmit filter settings and / or pseudo-coordinate (QCL) assumptions for receive space parameters, within a predetermined period or setting. It may indicate the time order within the cycle. The terminal may also recognize the difference in time index as the difference in QCL assumptions regarding the transmit beam, transmit filter settings and / or receive spatial parameters.

The REDCAP PBCH may be used by the terminal device 1 to broadcast a REDCAP important information block (also referred to as REDCAP MIB, REDCAP EIB, REDCAP BCH, R-MIB) containing important system information required. However, the REDCAP MIB may be used only for terminal equipment 1 that meets certain conditions (eg, UE Capability and / or indicates specific parameters in UE Category, etc.). However, the REDCAP MIB contains information for identifying the SFN to which the REDCAP PBCH is mapped, or information for identifying the SFN to which the SS / PBCH block corresponding to the REDCAP PBCH is mapped, and the REDCAP system information block. Information that identifies the subcarrier spacing of 1 (also known as REDCAP SIB1, R-SIB1), the frequency between the grid of resource blocks and the SS / PBCH block (also known as sync signal block, SS block, SSB). It may contain information indicating the region offset, information indicating the settings for PDCCH for REDCAP SIB1. However, REDCAP SIB1 contains the information needed to evaluate whether terminal device 1 is allowed to connect to a cell, and schedules other REDCAP system information blocks (also known as REDCAP SIB, R-SIB). Contains information to determine. However, the REDCAP SIB1 is used in assessing whether a terminal device 1 that meets certain conditions (eg, UE Capability and / or indicates a particular parameter in the UE Category) is allowed to connect to the cell. It may contain the required information and other information that determines the scheduling of the REDCAP SIB. However, some or all of the information contained in the REDCAP MIB may be the same as some or all of the information contained in the MIB broadcast by PBCH. For example, the above REDCAP SIB1 may be SIB1. However, some or all of the information in the REDCAP MIB may be communicated via PBCH. However, REDCAP PBCH may inform the MIB. For example, the REDCAP MIB included in the information transmitted by the REDCAP PBCH may be the same as the MIB contained in the information transmitted by the PBCH contained in the SS / PBCH block to which the REDCAP PBCH is associated. However, the processing related to the MIB described below may be applied to the processing related to the REDCAP MIB in the same way.

Further, the information transmitted by the REDCAP PBCH may include information for specifying the number of the radio frame to which the REDCAP PBCH is mapped and / or information for specifying the half radio frame. However, the information transmitted by the REDCAP PBCH includes information that identifies the number of the radio frame to which the REDCAP PBCH is associated (associated) PSS and / or SSS and / or information that identifies the half radio frame. May be included. However, even if the information transmitted by REDCAP PBCH contains information that identifies the number of the radio frame to which the associated SS / PBCH block is mapped and / or information that identifies the half radio frame. good.

Also, the information transmitted by REDCAP PBCH may include a time index within the period of the associated SS / PBCH block. The time index may be referred to as an SSB index or an SS / PBCH block index. For example, if the base station appliance 3 transmits an SS / PBCH block with multiple transmit beams, transmit filter settings and / or QCL assumptions for receive space parameters, within a predetermined period or within a set period. It may indicate the chronological order. The terminal device 1 may also recognize the difference in time index as the difference in QCL assumptions regarding the transmit beam, transmit filter settings and / or receive spatial parameters. In addition, the information transmitted by REDCAP PBCH may include the time index of REDCAP PBCH.

The information indicating the PDCCH settings for REDCAP SIB1 sent by REDCAP PBCH is REDCA.
It may be information that determines CORESET0, common search space and / or required PDCCH parameters for the PDCCH that schedules P SIB1. However, the information shown in the REDCAP MIB about CORESET0, common search space and / or determining the required PDCCH parameters is the information shown in the MIB about CORESET0, common search space and / or determining the required PDCCH parameters. It may be the same.

Figure 4 shows an example of the configuration of the RRC parameter PDCCH-ConfigSIB1-RC, which is information showing the settings for PDCCH for REDCAP SIB1. The RRC parameter PDCCH-ConfigSIB1-RC consists of the parameter controlResourceSetZero used to set CORESET0 and the parameter searchSpaceZero used to set the common search space. The information element (IE: Information Element) indicated by controlResourceSetZero is set to a value from 0 to 15. However, the number of values that can be set in ControlResourceSetZero may be other than 16, for example, 32. The information element SearchSpaceZero indicated by searchSpaceZero is set to a value from 0 to 15. However, the number of values that can be set in SearchSpaceZero may be other than 16, for example, 32.

Terminal 1 determines the number of contiguous resource blocks and the number of contiguous symbols for CORESET0 from controlResourceSetZero in PDCCH-ConfigSIB1-RC. However, the value indicated by controlResourceSetZero is applied to the given table as an index. However, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE Capability. However, the terminal device 1 may determine the table to be applied based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier interval of the SS / PBCH block, the subcarrier interval of REDCAP PBCH and / or the subcarrier interval of CORESET0. Figure 5 shows an example of a table to which the value of controlResourceSetZero is applied as an index. As shown in the table shown in Figure 5, each row of the table to which the value of controlResourceSetZero is applied as an index has the index indicated by controlResourceSetZero, the multiple pattern of REDCAP PBCH and CORESET, and the number of RBs (may be PRB) of CORESET0. , CORESET0 symbol count, offset and / or PDCCH repeat count.

The REDCAP PBCH and CORESET multiplex pattern shows the pattern of the frequency / time position relationship between the REDCAP PBCH that detected the REDCAP MIB and the corresponding CORESET0. For example, if the multiplex pattern of REDCAP PBCH and CORESET is 1, REDCAP PBCH and CORESET are time-multiplexed to different symbols. However, the multiple pattern of REDCAP PBCH and CORESET is REDCAP that detected the REDCAP MIB.
The pattern of the relationship between the SS / PBCH block corresponding to PBCH and the frequency / time position of CORESET0 may be shown. However, the multiple pattern of REDCAP PBCH and CORESET is not defined in the table and may always be a fixed pattern (for example, pattern 1).

The number of RBs in CORESET0 indicates the number of resource blocks that are continuously allocated to CORESET0. The number of symbols of CORESET0 indicates the number of symbols continuously assigned to CORESET0.

Offset indicates the offset from the lowest RB index of the resource block assigned to CORESET0 to the lowest RB index of the common resource block where the first resource block of the corresponding REDCAP PBCH overlaps. However, the offset indicates the offset from the smallest RB index of the resource block assigned to CORESET0 to the smallest RB index of the common resource block where the first resource block of the SS / PBCH block corresponding to REDCAP PBCH overlaps. good.

PDCCH repeat count indicates the number of PDCCH repeat transmissions that schedule REDCAP SIB1. If the number of iterations of the PDCCH shown in the table is greater than 1, terminal 1 considers the PDCCH scheduling REDCAP SIB1 to be transmitted repeatedly.

Terminal 1 receives the REDCAP MIB containing the RRC parameter controlResourceSetZero on the REDCAP PBCH, and repeats the controlResourceSetZero and the index, REDCAP PBCH and CORESET multiple pattern, CORESET0 RB number, CORESET0 symbol number, offset and / or PDCCH. Monitor the PDCCH showing the scheduling information for REDCAP SIB1 based on the table showing the number of times.

Terminal device 1 determines the PDCCH monitoring opportunity from searchSpaceZero in PDCCH-ConfigSIB1-RC. However, the value indicated by searchSpaceZero is applied to the given table as an index. However, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE Capability. However, the terminal device 1 may determine the table to be applied based on the frequency range. However, the terminal device 1 may determine the table to be applied based on the multiple pattern of REDCAP PBCH and CORESET. Figure 6 shows an example of a table to which the value of searchSpaceZero is applied as an index.

The terminal device 1 monitors PDCCH with the Type 0-PDCCH common search space set (Type0-PDCCH CSS Set) from slot n0 to two consecutive slots. Terminal 1 determines n0 and the system frame number based on the parameters O and M shown in the table in the REDCAP PBCH and / or the corresponding SS / PBCH block with the index i.

However, if a field in the REDCAP MIB indicates that REDCAP SIB1 does not exist (absent), the information indicating the PDCCH settings for REDCAP SIB1 sent by REDCAP PBCH is that terminal device 1 uses REDCAP SIB1. Find REDCAP PBCH and / or corresponding SS / PBCH block with REDCAP PBCH (find) May indicate a frequency range where the frequency location or network does not provide REDCAP PBCH with REDCAP SIB1 and / or the corresponding SS / PBCH block. ..

In addition, the information transmitted by REDCAP PBCH may include a field PDCCH-repetitions indicating the number of repeated transmissions of PDCCH that schedules REDCAP SIB1. For example, the number of repeated transmissions of PDCCH may be indicated by 2 bits in the REDCAP MIB. FIG. 7 is a diagram showing an example of a table of the number of repeated transmissions of PDCCH and the index indicated by the 2-bit parameter PDCCH-repetitions in the REDCAP MIB. In the table of FIG. 7, indexes 0, 1, 2, and 3 shown by the RED CAP MIB correspond to N / A, 1, 2, and 4 in the number of repeated PDCCH transmissions, respectively. However, a PDCCH repeat transmission value of N / A may indicate that the PDCCH and / or REDCCAP SIB1 that schedules REDCAP SIB1 has not been transmitted. In this case, terminal 1 considers that the PDCCH and / or REDCCAP SIB1 that schedules REDCAP SIB1 has not been transmitted if the index represented by the two bits in the REDCAP MIB is 0. However, the fact that the value of the number of repeated transmissions of PDCCH is N / A may indicate that the cell is prohibited (barred).

The terminal device 1 receives the REDCAP MIB including the RRC parameter PDCCH-repetitions in REDCAP PBCH, determines the number of repeated transmissions of PDCCH indicating the scheduling information of REDCAP SIB1 based on the PDCCH-repetitions, and the PDCCH-repetitions is predetermined. If the value is, it is considered that PDCCH has not been transmitted.

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

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

DCI format 0_0 may be used for scheduling PUSCH in a serving cell. DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation). DCI format 0_0 is an identifier of Radio Network Temporary Identifier (RNTI), Cell-RNTI (C-RNTI), Configured Scheduling (CS) -RNTI), MCS-C-RNTI, and / or Temporary C-NRTI. A CRC (Cyclic Redundancy Check) scrambled by any of (TC-RNTI) may be added. DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

DCI format 0_1 may be used for scheduling PUSCH in a serving cell. DCI format 0_1 is information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, channel state information (CSI) request, sounding reference signal (SRS). ) Requests and / or may include information about the antenna port. DCI format 0_1 may be supplemented with a CRC scrambled by any of the RNTIs C-RNTI, CS-RNTI, Semi Persistent (SP) -CSI-RNTI, and / or MCS-C-RNTI. .. DCI format 0_1 may be monitored in the UE-specific search space.

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

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

DCI format 1_1 may be used for PDSCH scheduling in a serving cell. DCI format 1_1 contains information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, transmission configuration indication (TCI), and / or information regarding antenna ports. It's fine. DCI format 1_1 may be added with a CRC scrambled by any of the C-RNTI, CS-RNTI, and / or MCS-C-RNTI of the RNTIs. DCI format 1_1 may be monitored in the UE-specific search space.

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

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

DCI format 2_1 is used to notify terminal device 1 of a physical resource block (PRB or RB) 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).

DCI format 2_2 is used for the transmission of PUSCH and Transmit Power Control (TPC) commands for PUSCH.

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

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

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

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

C-RNTI and / or other RNTIs may have different values depending on the type of PDSCH or PUSCH traffic. C-RNTI and other RNTIs may use different values depending on the service type (eMBB, URLLC, and / or mMTC) of the data transmitted by PDSCH or PUSCH. The base station apparatus 3 may use RNTIs having different values depending on the service type of the data to be transmitted. Terminal 1 may identify the service type of data transmitted on the associated PDSCH or PUSCH by the value of RNTI (used for scrambling) applied to the received DCI.

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

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

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

Here, the base station device 3 and the terminal device 1 exchange (transmit / receive) signals in an upper layer (upper layer). For example, the base station device 3 and the terminal device 1 may send and receive RRC messages (also referred to as RRC message, RRC information, and RRC signaling) in the radio resource control (RRC) layer. Further, the base station device 3 and the terminal device 1 may transmit and receive a MAC control element in the MAC (Medium Access Control) layer. Further, the RRC layer of the terminal device 1 acquires the system information notified from the base station device 3. Here, RRC messages, system information, and / or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each of the parameters included in the upper layer signal received by the terminal device 1 may be referred to as an upper layer parameter. Since the upper layer here means an upper layer seen from the physical layer, it may include one or more such as a MAC layer, an RRC layer, an RLC layer, a PDCP layer, and a NAS (Non Access Stratum) layer. For example, in the processing of the MAC layer, the upper layer may include one or more such as an RRC layer, an RLC layer, a PDCP layer, and a NAS layer. Hereinafter, the meanings of "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" mean the upper layer (mainly RRC layer and MAC) of the terminal device 1. It may mean that the layer, etc.) receives A from the base station apparatus 3, and the received A is given (provided) to the physical layer of the terminal apparatus 1 from the upper layer of the terminal apparatus 1. For example, in the terminal device 1, "provided with the upper layer parameter" means that the upper layer signal is received from the base station device 3 and the upper layer parameter included in the received upper layer signal is the terminal from the upper layer of the terminal device 1. It may mean that it is provided to the physical layer of device 1. Setting the upper layer parameter to the terminal device 1 may mean that the upper layer parameter is given (provided) to the terminal device 1. For example, setting the upper layer parameter in the terminal device 1 may mean that the terminal device 1 receives the upper layer signal from the base station device 3 and sets the received upper layer parameter in the upper layer. .. However, setting the upper layer parameter in the terminal device 1 may include setting the default parameter given in advance to the upper layer of the terminal device 1.

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

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

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

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

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

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

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

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

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

In this embodiment, the downlink physical channel and / or the downlink physical signal is generally referred to as a downlink physical signal. In this embodiment, the uplink physical channel and / or the uplink physical signal are generally referred to as an uplink signal. In this embodiment, the downlink physical channel and / or the uplink physical channel are generally referred to as a physical channel. In this embodiment, the downlink physical signal and / or the uplink physical signal are generally referred to as physical signals.

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

FIG. 8 shows a half frame (Half frame with SS / PBCH) in which an SS / PBCH block (also referred to as a synchronization signal block, an SS block, or an SSB) and one or more SS / PBCH blocks according to the present embodiment are transmitted. It is a figure which shows an example (which may be called a block or SS burst set). FIG. 8 shows an example in which two SS / PBCH blocks are contained in an SS burst set existing in a fixed period (which may be referred to as an SSB period), and the SS / PBCH block is composed of consecutive 4OFDM symbols. Shows.

The SS / PBCH block may be a block containing a sync signal (PSS, SSS), PBCH and DMRS for PBCH. However, the SS / PBCH block may be a block containing DMRS for synchronization signals (PSS, SSS), REDCAP PBCH and REDCAP PBCH. Transmitting a signal / channel contained in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When base station apparatus 3 transmits a synchronization signal and / or PBCH using one or more SS / PBCH blocks in the SS burst set, even if an independent downlink transmission beam is used for each SS / PBCH block. good.

The base station apparatus 3 according to the present embodiment transmits DMRS for REDCAP PBCH and REDCAP PBCH with a time resource different from that of the SS / PBCH block and / or a different frequency resource. However, in the present embodiment, transmitting / receiving / processing REDCAP PBCH may be transmitting / receiving / processing DMRS for REDCAP PBCH and REDCAP PBCH. A block containing DMRS for REDCAP PBCH and REDCAP PBCH may be referred to as a REDCAP PBCH block. However, transmitting a signal / channel contained in a REDCAP PBCH block may be expressed as transmitting a REDCAP PBCH block. When base station apparatus 3 transmits REDCAP PBCH using one or more REDCAP PBCH blocks within a predetermined time interval (may be referred to as REDCAP PBCH burst set), the downlink is independent for each REDCAP PBCH block. A transmission beam may be used. However, the REDCAP PBCH block according to this embodiment may be the DMRS itself for REDCAP PBCH and / or REDCAP PBCH. For example, transmitting / receiving / processing a REDCAP PBCH block may be transmitting / receiving / processing DMRS for REDCAP PBCH and / or REDCAP PBCH. However, the DMRS for REDCAP PBCH and / or REDCAP PBCH according to this embodiment may be DMRS for REDCAP PBCH and / or REDCAP PBCH transmitted outside the SS / PBCH block. For example, DMRS for REDCAP PBCH and / or REDCAP PBCH is for REDCAP PBCH and / or REDCAP PBCH transmitted at a different time and / or frequency than the SS / PBCH block transmitted periodically in the SSB cycle. It may be DMRS. However, the REDCAP PBCH block according to this embodiment may be an SS / PBCH block without PSS and / or SSS.

The REDCAP PBCH block and / or REDCAP PBCH according to the present embodiment is associated with one SS / PBCH block transmitted within the SS burst set (Half frame with SS / PBCH block). The transport block transmitted on the REDCAP PBCH and the transport block transmitted on the PBCH in the corresponding SS / PBCH block may be the same.

FIG. 9 shows an example of a half frame (which may be referred to as a Half frame with REDCAP PBCH block or REDCAP PBCH burst set) in which a REDCAP PBCH block and one or more REDCAP PBCH blocks according to the present embodiment are transmitted. It is a figure. Figure 9 shows an example in which two REDCAP PBCH blocks are contained within a REDCAP PBCH burst set that exists in a fixed period (sometimes referred to as an SSB period), and the REDCAP PBCH block consists of consecutive 4OFDM symbols. ing. In the REDCAP PBCH block, each OFDM symbol is frequency-multiplexed with a REDCAP PBCH modulation symbol and DMRS for REDCAP PBCH.

However, a block containing a synchronization signal (PSS, SSS), REDCAP PBCH and DMRS for REDCAP PBCH may be defined as a separate block to distinguish it from the SS / PBCH block. For example, REDCAP a block containing DMRS for sync signals (PSS, SSS), REDCAP PBCH and REDCAP PBCH.
It may be referred to as SS / PBCH block, REDCAP synchronization signal block, REDCAP SS block or REDCAP SSB. However, the description regarding the SS / PBCH block according to the present embodiment of the REDCAP SS / PBCH block may also be applied to the REDCAP SS / PBCH block.

In FIG. 8, one SS / PBCH block is time / frequency-multiplexed with DMRS for PSS, SSS, PBCH and PBCH. FIG. 10 is a table showing the resources in which DMRS for PSS, SSS, PBCH and PBCH are placed within the SS / PBCH block.

The PSS may be mapped to the first symbol in the SS / PBCH block (the OFDM symbol whose relative to OFDM symbol number is 0 with respect to the start symbol of the SS / PBCH block). The PSS series consists of 127 symbols and is the subcarrier whose subcarrier number is 56 to 182 for the starting subcarrier of the SS / PBCH block from the 57th subcarrier to the 183rd subcarrier in the SS / PBCH block. ) May be mapped to.

The SSS may be mapped to a third symbol in the SS / PBCH block (an OFDM symbol having an OFDM symbol number of 2 relative to the start symbol of the SS / PBCH block). The SSS series consists of 127 symbols and is the subcarrier whose subcarrier number is 56 to 182 for the starting subcarrier of the SS / PBCH block from the 57th subcarrier to the 183rd subcarrier in the SS / PBCH block. ) May be mapped to.

PBCH and DMRS are the second, third, and fourth symbols in the SS / PBCH block (OFDM whose relative to OFDM symbol numbers are 1, 2, and 3 for the start symbol of the SS / PBCH block. May be mapped to a symbol). The sequence of modulation symbols for _PBCH consists of M symb symbols, the second symbol in the SS / PBCH block and the 240th subcarrier from the first subcarrier of the fourth symbol (the start of the SS / PBCH block). Subcarrier number is 0 for subcarrier
~ 239 subcarriers) and the 48th subcarrier from the 1st subcarrier and the 184th to 240th subcarriers of the 3rd symbol in the SS / PBCH block (to the starting subcarrier of the SS / PBCH block) On the other hand, subcarriers whose subcarrier numbers are 0 to 47 and 192 to 239) may be mapped to resources for which DMRS is not mapped.
The DMRS symbol sequence consists of 144 symbols, the first to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (the starting subcarrier of the SS / PBCH block). Subcarriers whose subcarrier numbers are 0 to 239), the 48th subcarrier from the 1st subcarrier of the 3rd symbol in the SS / PBCH block, and the 184th to 240th subcarriers (SS). Subcarriers whose subcarrier numbers are 0 to 47 and 192 to 239 for the starting subcarrier of the / PBCH block) may be mapped to 1 subcarrier for every 4 subcarriers. For example, for 240 subcarriers, 180 subcarriers may be mapped to the PBCH modulation symbol and 60 subcarriers may be mapped to DMRS for the PBCH.

Different SS / PBCH blocks in the SS burst set may be assigned different SSB indexes. The SS / PBCH block to which a certain SSB index is assigned may be periodically transmitted by the base station apparatus 3 based on the SSB cycle. For example, an SSB period for the SS / PBCH block to be used for initial access and an SSB period set for the connected (Connected or RRC_Connected) terminal device 1 may be defined. Also, the SSB period set for the connected (Connected or RRC_Connected) terminal device 1 may be set by the RRC parameter. Also, the SSB cycle set for the connected (Connected or RRC_Connected) terminal device 1 is the cycle of radio resources in the time domain that may potentially transmit, and is actually the cycle of the base station device 3 You may decide whether to send. Further, the SSB cycle for the SS / PBCH block to be used for the initial access may be defined in advance in the specifications and the like. For example, the terminal device 1 that performs the initial access may consider the SSB period to be 20 milliseconds.

The time position of the SS burst set to which the SS / PBCH block is mapped is determined based on the information that identifies the system frame number (SFN) contained in the PBCH and / or the information that identifies the half frame. good. The terminal device 1 that has received the SS / PBCH block may specify the current system frame number and the half frame based on the received SS / PBCH block.

SS / PBCH blocks are assigned SSB indexes (may be referred to as SS / PBCH block indexes) according to their temporal position in the SS burst set. The terminal device 1 identifies the SSB index based on the PBCH information and / or the reference signal information contained in the detected SS / PBCH block.

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

Within a period of an SS burst set, SS / PBCH blocks to which the same SSB index is assigned may be assumed to be QCL in terms of mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation. A setting corresponding to one or more SS / PBCH blocks (or may be a reference signal) that is a QCL may be referred to as a QCL setting.

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

The RED CAP PBCH according to this embodiment is transmitted with the OFDM symbol associated with the corresponding SS / PBCH block or the corresponding synchronization signal (PSS, SSS).

The time-positional relationship between the REDCAP PBCH according to the present embodiment and the corresponding SS / PBCH block may be determined by the time-positional relationship between the half frame including the REDCAP PBCH and the half frame including the corresponding SS / PBCH block, respectively. For example, the half frame containing the REDCAP PBCH may be the half frame after a predetermined time offset from the half frame containing the corresponding SS / PBCH block. For example, the time position of the REDCAP PBCH in the half frame containing the REDCAP PBCH and the time position of the SS / PBCH block in the half frame containing the corresponding SS / PBCH block may be the same.

The starting subcarrier of the RED CAP PBCH according to the present embodiment may be a subcarrier in which a predetermined frequency offset is added to the starting subcarrier of the corresponding SS / PBCH block. However, if the value to which the frequency offset is added exceeds a certain value, the value obtained by subtracting the constant value may be used as the starting subcarrier of REDCAP PBCH. For example, if the value obtained by adding a predetermined frequency offset to the start subcarrier of the corresponding SS / PBCH block exceeds the band to which the REDCAP PBCH can be allocated, the bandwidth of the band to which the REDCAP PBCH can be allocated from the value. The value obtained by subtracting the above may be used as the starting subcarrier of the REDCAP PBCH.

FIG. 11 is a diagram showing an example of a REDCAP PBCH block according to the present embodiment and a half frame in which one or more REDCAP PBCH blocks are transmitted. Figure 11 shows an example in which a half frame containing a REDCAP PBCH block exists between half frames containing an SS / PBCH block existing at a fixed cycle (SSB cycle), and the REDCAP PBCH block is composed of consecutive 3OFDM symbols. Shows. The REDCAP PBCH block is transmitted with the resource corresponding to one SS / PBCH block, and all the resources in the REDCAP PBCH block have DMRS for REDCAP PBCH or REDCAP PBCH. Figure 12 is a table showing an example of a resource in which DMRS for REDCAP PBCH and REDCAP PBCH is placed within a REDCAP PBCH block. For example, the sequence of modulated symbols in REDCAP PBCH consists of M _symb2 symbols, each of the three symbols in the REDCAP PBCH block from the first subcarrier to the 240th subcarrier (subcarriers to the starting subcarrier of the REDCAP PBCH block). The DMRS for REDCAP PBCH may be mapped to a resource that is not mapped out of the subcarriers whose carrier number is 0 to 239). The DMRS symbol sequence for REDCAP PBCH consists of 180 symbols, from the first subcarrier to the 240th subcarrier of the three symbols in the REDCAP PBCH block (subcarriers to the starting subcarrier of the REDCAP PBCH block). Subcarriers with numbers 0 to 239) may be mapped by 1 subcarrier for every 4 subcarriers. However, the number of symbols that make up the REDCAP PBCH block does not have to be three. For example, the REDCAP PBCH block consists of 4 symbols, and DMRS for REDCAP PBCH or REDCAP PBCH may be present for 240 subcarriers of each symbol. However, the number of subcarriers constituting the REDCAP PBCH block does not have to be 240 subcarriers. For example, a REDCAP PBCH block may consist of 180 subcarriers and 4OFDM symbols, with DMRS for REDCAP PBCH or REDCAP PBCH for 180 subcarriers of each symbol.

FIG. 13 is a diagram showing an example of the REDCAP PBCH block according to the present embodiment. FIG. 13 shows an example in which a REDCAP PBCH block exists in a half frame including an SS / PBCH block existing at a fixed cycle (SSB cycle), and the REDCAP PBCH block is composed of consecutive 4OFDM symbols. The REDCAP PBCH block is transmitted with the resource corresponding to one SS / PBCH block, and all the resources in the REDCAP PBCH block have DMRS for REDCAP PBCH or REDCAP PBCH. For example, the sequence of modulated symbols in REDCAP PBCH consists of M _symb2 symbols, each of the four symbols in the REDCAP PBCH block from the first subcarrier to the 240th subcarrier (subcarriers to the starting subcarrier of the REDCAP PBCH block). The DMRS for REDCAP PBCH may be mapped to a resource that is not mapped out of the subcarriers whose carrier number is 0 to 239). The DMRS symbol sequence for REDCAP PBCH consists of 240 symbols, from the first subcarrier to the 240th subcarrier of the four symbols in the REDCAP PBCH block (subcarriers to the starting subcarrier of the REDCAP PBCH block). Subcarriers with numbers 0 to 239) may be mapped by 1 subcarrier for every 4 subcarriers. However, DMRS for REDCAP PBCH or REDCAP PBCH does not have to exist for all resources in the REDCAP PBCH block. For example, the REDCAP PBCH block consists of 4 symbols, one of which may be set to 0.

FIG. 14 is a diagram showing another example of the REDCAP PBCH block according to the present embodiment. FIG. 14 shows an example in which a REDCAP PBCH block exists in some slots in a half frame including an SS / PBCH block existing at a fixed cycle (SSB cycle), and the REDCAP PBCH block is composed of consecutive 4OFDM symbols. Is shown. However, the slot in which the REDCAP PBCH block is placed may be a slot that does not include the candidate resource of the SS / PBCH block. The REDCAP PBCH block is transmitted with the resource corresponding to one SS / PBCH block, and all the resources in the REDCAP PBCH block have DMRS for REDCAP PBCH or REDCAP PBCH. For example, the sequence of modulated symbols in REDCAP PBCH consists of M _symb2 symbols, each of the four symbols in the REDCAP PBCH block from the first subcarrier to the 240th subcarrier (subcarriers to the starting subcarrier of the REDCAP PBCH block). The DMRS for REDCAP PBCH may be mapped to a resource that is not mapped out of the subcarriers whose carrier number is 0 to 239). The DMRS symbol sequence for REDCAP PBCH consists of 240 symbols, from the first subcarrier to the 240th subcarrier of the four symbols in the REDCAP PBCH block (subcarriers to the starting subcarrier of the REDCAP PBCH block). Subcarriers with numbers 0 to 239) may be mapped by 1 subcarrier for every 4 subcarriers. However, DMRS for REDCAP PBCH or REDCAP PBCH does not have to exist for all resources in the REDCAP PBCH block. For example, the REDCAP PBCH block may consist of 4 symbols, one of which may be set to 0 and the remaining 3 symbols may have DMRS for REDCAP PBCH and REDCAP PBCH.

One or more REDCAP PBCH blocks in a half frame containing REDCAP PBCH (REDCAP PBCH burst set) may be assigned different SSB indexes. The REDCAP PBCH block to which a certain SSB index is assigned is associated with the SS / PBCH block of the SSB index and may be periodically transmitted by the base station apparatus 3. However, a plurality of REDCAP PBCH blocks to which the same SSB index is assigned may exist for one SS / PBCH block. For example, a REDCAP PBCH block with the same SSB index may be transmitted multiple times within the SSB cycle.

The time position of the half frame to which the REDCAP PBCH block is mapped is the information that identifies the SFN contained in the PBCH and / or REDCAP PBCH of the corresponding SS / PBCH block and / or the information that identifies the half frame. It may be specified based on the time offset of the corresponding SS / PBCH block and REDCAP PBCH block. However, the information specifying the SFN and / or the half frame contained in the REDCAP PBCH of the REDCAP PBCH block may be the information specifying the SFN and the half frame to which the corresponding SS / PBCH block is transmitted. The terminal device 1 that has received the REDCAP PBCH block may specify the SFN and the half frame to which the corresponding SS / PBCH block is transmitted based on the received REDCAP PBCH block.

The REDCAP PBCH block is assigned an SSB index according to its temporal position within the transmitted half frame. Terminal 1 identifies the SSB index based on the REDCAP PBCH information and / or reference signal information contained in the detected REDCAP PBCH block.

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

Within a period of an SS burst set, SS / PBCH blocks and REDCAP PBCH blocks to which the same SSB index is assigned are assumed to be QCL in terms of mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation. good.

The terminal device 1 according to the present embodiment receives PSS and SSS in the SS / PBCH block, and receives one or more REDCAP PBCH corresponding to the PBCH and / or the SS / PBCH block in the SS / PBCH block. do. By receiving one or more REDCAP PBCHs, the terminal device 1 can improve the detection accuracy of the MIB or the REDCAP MIB, and can increase the cell coverage in which the terminal device 1 can receive the MIB or the REDCAP MIB. However, the terminal device 1 that receives the REDCAP PBCH may be only the terminal device 1 having a predetermined capability. For example, a terminal device 1 having a capacity limited for the purpose of cost reduction and / or power consumption reduction of the device is referred to as corresponding to REDCAP (Reduction Capability), and the terminal device 1 corresponding to REDCAP is an SS / PBCH block and /. Alternatively, the terminal device 1 that receives REDCAP PBCH and does not support REDCAP may receive only the SS / PBCH block and not the REDCAP PBCH block.

The terminal device 1 according to the present embodiment receives an SS / PBCH block in which DMRS for PSS, SSS, PBCH and PBCH is mapped in a certain radio frame, and REDCAP PBCH in the same or different radio frame as the certain radio frame. And DMRS for REDCAP PBCH may be received and the MIB of the transport block transmitted on PBCH and REDCAP PBCH may be obtained. However, PBCH and REDCAP PBCH carry at least the MIB and additional bit information, and the radio frame to which the SS / PBCH block is transmitted may be identified based on the MIB and additional bit information.

The terminal device 1 according to the present embodiment receives an SS / PBCH block in which DMRS for PSS, SSS, PBCH and PBCH is mapped in a certain radio frame, and REDCAP PBCH in the same or different radio frame as the certain radio frame. And DMRS for REDCAP PBCH may be received and the MIB of the transport block transmitted on PBCH and REDCAP PBCH may be obtained.

The terminal device 1 according to the present embodiment has, in a certain cell, a connection state, a predetermined timer execution state, received MIB (which may be a REDCAP MIB) information, and / or received SIB (REDCAP SIB, SIB1, SIB1, Alternatively, based on the information in REDCAP SIB1), determine whether the cell is considered a "barred" cell. However, the regulated cell may be a cell in which the terminal device 1 is not allowed to camp in the cell. For example, terminal device 1 does not camp on regulated cells.

The terminal device 1 according to the present embodiment has a connection state of the RRC idle state (RRC_IDLE), the RRC inactive state (RRC_INACTIVE), or the RRC connection state (RRC_CONNECTED) in which the timer T311 is being executed in a certain cell. Determines whether the cell is considered a "barred" cell based on the received MIB. However, the timer T311 is a timer executed during the RRC connection reestablishment procedure, and when the timer expires, the terminal device 1 sets the connection state to the RRC idle state.

The terminal device 1 considers a cell to be a regulated cell when the value of the parameter cellBarred contained in the received MIB is a predetermined value. However, the parameter cellBarred is a parameter indicating whether or not the corresponding cell is barred. However, the parameter cellBarred may be ignored when the terminal device 1 is a predetermined terminal device (for example, REDCAP UE). The terminal device 1 considers the cell to be a regulated cell if the parameter cellBarred-rc, which is different from the parameter cellBarred contained in the received MIB, has a predetermined value. However, the parameter cellBarred-rc is a parameter indicating whether or not the corresponding cell is barred for a predetermined terminal device (for example, REDCAP UE). However, the parameter cellBarred-rc may be ignored when the terminal device 1 is other than a predetermined terminal device (for example, REDCAP UE). However, the information indicated by the parameter cellBarred-rc may be realized by other parameters contained in the MIB. For example, if the MIB contains a parameter relating to the setting of CORESET0 and the parameter indicates a predetermined value, the terminal device 1 may consider the cell to be a regulated cell. Even if the terminal device 1 does not indicate that it is a regulated cell in any of the parameters contained in the received MIB, it may apply other parameters contained in the MIB (for example, information indicating SFN). good.

In the terminal device 1 according to the present embodiment, the connection state is the RRC connection state in which the timer T311 is not being executed (
Received SIB1 (REDCAP) if not in RRC_CONNECTED while T311 is not running)
Based on the parameters (which may be SIB1), determine whether the cell should be considered a "barred" cell.

The base station apparatus 3 according to the present embodiment is SIB1 (may be REDCAP SIB1) including a parameter for determining whether or not the cell is regulated in a cell in which the terminal apparatus 1 is located with respect to the terminal apparatus 1. To send.

If initialDownlinkBWP is not provided for terminal device 1, initialDownlink BWP (initial)
DL BWP) is the position and number of consecutive PRBs starting from the lowest index PRB and ending with the highest index PRB in the CORESET (CORESET0 etc.) PRB (Physical Resource Block) of the Type0-PDCCH CSS Set, and the Type0-PDCCH CSS. It may be defined by SCS (SubCarrier Spacing) and cyclic prefix of PDCCH received by CORESET of Set. If the initialDownlinkBWP is provided to terminal 1, the initial downlink BWP may be defined in the initialDownlinkBWP. Terminal device 1 may be configured with multiple initial downlink sub-BWPs by SIB1. At least one of the plurality of initial downlink sub-BWPs may be configured to include an SS / PBCH block. The terminal device 1 may operate by regarding the initial downlink sub-BWP including the SS / PBCH block (cell-defined SS / PBCH block (cell-defining SSB), etc.) as the initial downlink BWP. At least one of the plurality of initial downlink sub-BWPs may be configured to include CORESET0. All of the multiple initial downlink sub-BWPs may be configured to include their respective CORESET0. The terminal device 1 may operate by regarding the initial downlink sub BWP including CORESET 0 as the initial downlink BWP. The terminal device 1 may operate by regarding the initial downlink sub-BWP as the initial downlink BWP. Multiple initial downlink sub-BWPs may be considered as multiple initial downlink BWPs. The plurality of initial downlink sub-BWPs may be designed to be included in the frequency band of one initial downlink BWP. The initial downlink sub BWP may be paraphrased as the downlink BWP or the downlink sub BWP.

The initial uplink BWP may be defined in the initialUplinkBWP. Terminal device 1 may be configured with multiple initial uplink sub-BWPs by SIB1. At least one of the plurality of initial uplink sub-BWPs may be configured to include resources for a physical random access channel. The terminal device 1 may operate by regarding the initial uplink sub-BWP as the initial uplink BWP. Multiple initial uplink sub-BWPs may be considered as multiple initial uplink BWPs. The plurality of initial uplink sub-BWPs may be designed to be included in the frequency band of one initial uplink BWP. The initial uplink sub BWP may be paraphrased as uplink BWP or uplink sub BWP.

When a plurality of initial downlink sub-BWPs are set by SIB1, the base station apparatus 3 uses at least two of the plurality of initial downlink sub-BWPs to apply frequency hopping to the downlink signal (for example, PDSCH, PDCCH). , PBCH, sync signal, Msg2 in a random access procedure and / or Msg4 in a random access procedure). However, the initial downlink sub-BWP is a frequency resource that can be used at least during initial access before the RRC connection is established. When a plurality of initial downlink sub-BWPs are set by SIB1, the terminal device 1 may receive a downlink signal to which frequency hopping is applied by using at least two of the plurality of initial downlink sub-BWPs. .. However, the plurality of initial downlink sub-BWPs according to the present embodiment may be downlink BWPs to which the same identifier (BWP ID) is assigned. However, the plurality of initial downlink sub-BWPs according to the present embodiment may be a plurality of downlink BWPs to which different identifiers (BWP IDs) are assigned. The plurality of initial downlink sub-BWPs may be a plurality of frequency bands composed of a plurality of sets of a plurality of resource blocks set by SIB1. Each of the initial downlink sub-BWPs may consist of a plurality of contiguous resource blocks in the frequency domain. For example, the plurality of initial downlink sub-BWPs may be a plurality of downlink sub-BWPs set in the initial downlink BWP having a BWP ID of 0 set by SIB1. For example, each downlink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0a, 0b, etc.). In that case, the initial downlink BWP settings and the settings of multiple downlink sub-BWPs are set by SIB1.

FIG. 15 is a diagram showing an example of downlink transmission using a plurality of initial downlink sub-BWPs according to the present embodiment. FIG. 15 shows a case where four initial DL sub BWPs (initial DL sub BWP # 0, # 1, # 2, # 3) are set in a carrier existing in a certain frequency band. Terminal 1 supports a wider channel bandwidth than each of the four initial downlink sub-BWPs. In the example of FIG. 15, the terminal device 1 repeatedly transmits one downlink signal while frequency hopping using the initial downlink sub BWP # 0 and the initial downlink sub BWP # 2.

When a plurality of initial downlink sub-BWPs are set by SIB1, the base station apparatus 3 uses one of the plurality of initial downlink sub-BWPs for a downlink signal (for example, PDSCH, PDCCH, PBCH, synchronization signal). , Msg2 in the random access procedure and / or Msg4 in the random access procedure) may be transmitted. When a plurality of initial downlink sub-BWPs are set by SIB1, the terminal device 1 may receive a downlink signal using one of the plurality of initial downlink sub-BWPs. The initial downlink sub-BWP may be a frequency band composed of a plurality of sets of a plurality of resource blocks set by SIB1. The initial downlink sub-BWP may consist of a plurality of contiguous resource blocks in the frequency domain. For example, the initial downlink sub-BWP may be one of a plurality of downlink sub-BWPs configured within the initial downlink BWP whose BWP ID set by SIB1 is 0. For example, each downlink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.). In that case, the initial downlink BWP setting and the downlink sub BWP setting are set by SIB1.

When a plurality of initial uplink sub-BWPs are set by SIB1, the terminal device 1 applies frequency hopping using at least two of the plurality of initial uplink sub-BWPs (for example, PUSCH, PUCCH). , PRACH and / or may be Msg3 in a random access procedure). However, the initial uplink sub-BWP is a frequency resource that can be used at least during initial access before the RRC connection is established. When a plurality of initial uplink sub-BWPs are set by SIB1, the base station apparatus 3 receives an uplink signal to which frequency hopping is applied by using at least two of the plurality of initial uplink sub-BWPs. good. However, the plurality of initial uplink sub-BWPs according to the present embodiment may be set in the frequency band of the uplink BWP to which the same identifier (BWP ID) is assigned. However, the plurality of initial uplink BWPs according to the present embodiment may be a plurality of uplink BWPs to which different identifiers (BWP IDs) are assigned. The plurality of initial uplink sub-BWPs may be a plurality of frequency bands composed of a plurality of sets of a plurality of resource blocks set by SIB1. Each of the initial uplink sub-BWPs may consist of a plurality of contiguous resource blocks in the frequency domain. For example, the plurality of initial uplink BWPs may be a plurality of uplink sub-BWPs configured within the initial uplink BWP with a BWP ID of 0 set by SIB1. For example, each uplink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.). In that case, the initial uplink BWP settings and the settings of multiple uplink sub-BWPs are set by SIB1.

When a plurality of initial uplink sub-BWPs are set by SIB1, the terminal device 1 uses one of the plurality of initial uplink sub-BWPs to apply frequency hopping to the uplink signal (for example, PUSCH, PUCCH, etc.). PRACH and / or Msg3 in a random access procedure) may be transmitted. When a plurality of initial uplink sub-BWPs are set by SIB1, the base station apparatus 3 may receive an uplink signal to which frequency hopping is applied by using one of the plurality of initial uplink sub-BWPs. .. The initial uplink sub-BWP may be a frequency band composed of a plurality of sets of a plurality of resource blocks set by SIB1. The initial uplink sub-BWP may consist of a plurality of contiguous resource blocks in the frequency domain. For example, the plurality of initial uplink BWPs may be a plurality of uplink sub-BWPs configured within the initial uplink BWP with a BWP ID of 0 set by SIB1. For example, each uplink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.). In that case, the initial uplink BWP setting and the uplink sub BWP setting are set by SIB1.

SIB1 may include downlinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one of the parameters for determining whether the terminal device 1 is regulated in a cell may be included in the downlinkConfigCommon indicating the common downlink parameter of the cell. downlinkConfigCommon is a parameter that indicates the basic parameters for one downlink carrier and transmission (eg, referred to as frequencyInfoDL), a parameter that indicates the initial downlink BWP setting for a serving cell (eg, referred to as initialDownlinkBWP), and / or multiple. It may include a parameter indicating the setting of the initial downlink sub-BWP (for example, referred to as initialDownlinkBWP-rc).

The information element of the BWP may be a parameter indicating the frequency position and bandwidth of the BWP. The information elements of the BWP are the parameter subcarrierSpacing, which indicates the subcarrier spacing used in the BWP, the parameter locationAndBandwidth, which indicates the position and bandwidth (number of resource blocks) of the BWP in the frequency domain, and / or the standard CP (cyclic) in the BWP. It may include a parameter cyclicPrefix indicating whether prefix) is used or extended CP is used. That is, BWP is defined by subcarrier spacing, CP, and position and bandwidth in the frequency domain. However, the value indicated by locationAndBandwidth may be interpreted as a resource indicator value (RIV). The resource indicator value indicates the number of PRBs consecutive to the starting PRB index of the BWP. However, the first PRB that defines the region of the resource indicator value is the subcarrier interval given by the subcarrierSpacing of the BWP and the FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier interval. It may be a PRB determined by offsetToCarrier set by SCS-SpecificCarrier included in. The size that defines the area of the resource indicator value is 275.

Sub-BWPs (eg, uplink sub-BWPs and downlink sub-BWPs), like BWP, depend on subcarrier spacing, CP, and position in the frequency domain and bandwidth in the frequency domain (such as the number of consecutive resource blocks). May be defined. The sub-BWP may be defined by the position in the frequency domain and the bandwidth in the frequency domain.

The initialDownlinkBWP contains information elements for BWP, PDCCH settings, and / or PDSCH settings. However, the initial downlink BWP may be network configured to include CORESET0 in the frequency domain.

The initialDownlinkBWP-rc contains information indicating the settings of the sub BWP, information elements of the PDCCH settings, and / or information elements of the PDSCH settings. initialDownlinkBWP-rc may be a parameter indicating the setting of each of the plurality of initial downlink sub-BWPs. However, each of the plurality of initial downlink sub-BWPs set by initialDownlinkBWP-rc may be the initial downlink BWP (initial DL BWP). However, each of the plurality of downlink sub-BWPs may be configured by the network to include CORESET0 in the frequency domain. The initialDownlinkBWP-rc may include a list of information indicating the position in the frequency domain and the bandwidth in the frequency domain (such as the number of consecutive resource blocks). Each entry in the list of frequency position and bandwidth information may correspond to each of a plurality of initial downlink sub-BWPs. Each entry in the list of information indicating frequency position and bandwidth may be an information element of the BWP (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). Multiple initial downlink sub-BWPs may have a common bandwidth, and initialDownlinkBWP-rc may indicate a common bandwidth with a list of frequency positions of the initial downlink sub-BWP. Multiple initial downlink sub-BWPs have a common subcarrierSpacing, a common cyclicPrefix, and initialDownlinkBWP-rc shows a list of frequency positions of the initial downlink BWP and a common bandwidth, a common subcarrierSpacing, and a common cyclicPrefix. You may. Alternatively, the subcarrierSpacing and cyclicPrefix indicated by the initialDownlinkBWP may be set in a plurality of initial downlink subBWPs. That is, the initialDownlinkBWP-rc may be information for specifying the frequency position and bandwidth of each of the plurality of initial downlink sub-BWPs. However, the parameter indicating the setting of a plurality of initial downlink sub-BWPs may be set by the above-mentioned initialDownlinkBWP. Parameters indicating the initial downlink BWP setting of a serving cell include parameters indicating the frequency position and bandwidth of the initial downlink BWP, subcarrierSpacing of the initial downlink BWP, and cyclicPrefix of the initial downlink BWP, and multiple initial downlink sub BWPs. It may include a parameter indicating the setting of.

The frequencyInfoDL may include a frequencyBandList showing a list of one or more frequency bands to which the downlink carrier belongs and a list of SCS-Specific Carriers showing a set of parameters for carriers per subcarrier interval. frequencyInfoUL may include a frequencyBandList showing a list of one or more frequency bands to which the uplink carrier belongs and a list of SCS-Specific Carriers showing a set of parameters for carriers per subcarrier interval.

The SCS-SpecificCarrier may include parameters indicating the actual carrier position, bandwidth, and carrier bandwidth. More specifically, the SCS-Specific Carrier, which is an information element in frequencyInfoDL, indicates a setting for a particular carrier and includes subcarrierSpacing, carrierbandwidth and / or offsetToCarrier. Subcarrier Spacing is a parameter indicating the subcarrier spacing of the carrier (for example, FR1 indicates 15 kHz or 30 kHz, FR2 indicates 60 kHz or 120 kHz). The carrierbandwidth is a parameter indicating the bandwidth of the carrier by the number of PRBs (Physical Resource Blocks). offsetToCarrier sets the offset in the frequency domain between reference point A (lowest subcarrier of common RB0) and the lowest usable subcarrier of the carrier by the number of PRBs (however, the subcarrier spacing is subcarrierSpacing). It is a parameter shown by), which is the subcarrier interval of the carrier given in. For example, for downlink carriers, the carrier bandwidth is given by the upper layer parameter carrierbandwidth in the SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval, and the starting position on that frequency is the SCS in frequencyInfoDL for each subcarrier interval. -Given by the parameter offsetToCarrier in SpecificCarrier. For example, for uplink carriers, the carrier bandwidth is given by the upper layer parameter carrierbandwidth in the SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval, and the starting position on that frequency is the SCS in frequencyInfoUL for each subcarrier interval. -Given by the parameter offsetToCarrier in SpecificCarrier.

The terminal device 1 has a plurality of initial downlink sub-BWPs (initial downlink) depending on the received SIB1.
sub-BWP) may be set. The terminal device 1 may determine whether the cell is a regulated cell based on the bandwidth of the initial downlink BWP set by the received SIB1 corresponding to the cell. Terminal 1 may determine if the cell is a regulated cell based on whether it supports a downlink bandwidth equal to or wider than the bandwidth of the initial downlink BWP set by SIB1. .. For example, if the terminal device 1 does not support a downlink bandwidth equal to or wider than the bandwidth of the initial downlink BWP set by SIB1, the terminal device 1 may consider the cell as a regulated cell. .. The terminal device 1 may determine whether the cell is a regulated cell based on the bandwidth of the plurality of initial downlink sub-BWPs set by the received SIB1 corresponding to the cell. The terminal device 1 supports the same or wider downlink bandwidth as the widest bandwidth of each of the plurality of initial downlink sub-BWPs set by SIB1. You may decide if it is a regulated cell. For example, if the terminal device 1 does not support the same or wider downlink bandwidth as the widest bandwidth of each of the plurality of initial downlink sub-BWPs set by SIB1, the terminal device 1 may use the terminal device 1. , The cell may be regarded as a regulated cell. Terminal device 1 is based on whether terminal device 1 supports the same or wider downlink bandwidth that is commonly set for multiple initial downlink sub-BWPs set by SIB1. May determine if is a regulated cell. For example, if terminal device 1 does not support a downlink bandwidth equal to or wider than the bandwidth commonly set for multiple initial downlink sub-BWPs set by SIB1, the terminal device 1 will use the cell. May be regarded as a regulated cell. Terminal device 1 regulates the cell based on whether it supports the same or wider downlink bandwidth as specified by the parameters that configure multiple initial downlink sub-BWPs notified by SIB1. You may decide if it is a cell. For example, if terminal device 1 does not support a downlink bandwidth that is equal to or wider than the bandwidth specified by the parameters that configure multiple initial downlink sub-BWPs notified by SIB1, then the terminal device 1 is concerned. The cell may be regarded as a regulated cell. Terminal 1 determines if the cell is a regulated cell based on whether it supports downlink bandwidth equal to or wider than the reference bandwidth identified from the bandwidth notified by SIB1. It's okay. For example, if the terminal device 1 does not support a downlink bandwidth equal to or wider than the reference bandwidth identified from the bandwidth notified by SIB1, the terminal device 1 may consider the cell to be a regulated cell. good. However, the reference bandwidth may be the bandwidth specified by the bandwidth of one initial downlink BWP notified by SIB1 and the number of initial downlink sub-BWPs configured. However, the reference bandwidth may be the bandwidth specified by dividing one initial downlink BWP notified by SIB1 by a predetermined number.

The terminal device 1 may determine whether the cell is a regulated cell based on whether it supports downlink bandwidth equal to or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth equal to or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may consider the cell as a regulated cell. However, the carrier bandwidth may be a carrier bandwidth corresponding to the subcarrier interval of the initial downlink BWP set by the received SIB1. However, the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier interval common to a plurality of initial downlink subBWPs set in the received SIB1.

SIB1 may include uplinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one of the parameters for determining whether the terminal device 1 is regulated in a cell may be included in uplinkConfigCommon indicating the common uplink parameter of the cell. uplinkConfigCommon is a parameter that indicates the basic parameters for one uplink carrier and transmission (eg, referred to as frequencyInfoUL), a parameter that indicates the initial uplink BWP setting for a serving cell (eg, referred to as initialUplinkBWP), and / or multiple. It may include a parameter indicating the setting of the initial uplink sub-BWP (for example, referred to as initialUplinkBWP-rc).

The initialUplinkBWP contains information elements for BWP, PDCCH settings, and / or PDSCH settings. However, the initial uplink BWP may be configured in the network to include physical random access channel resources in the frequency domain.

The initialUplinkBWP-rc contains information indicating the settings of the sub BWP, information elements of the PUCCH settings, and / or information elements of the PUSCH settings. initialUplinkBWP-rc may be a parameter indicating the setting of each of the plurality of initial uplink sub-BWPs. However, each of the plurality of initial uplink sub-BWPs set by initialUplinkBWP-rc may be the initial uplink BWP (initial UL BWP). However, each of the plurality of uplink sub-BWPs may be configured by the network to include physical random access channel resources in the frequency domain. The initialUplinkBWP-rc may contain a list of information indicating the frequency position and bandwidth. Each entry in the list of frequency position and bandwidth information may correspond to each of a plurality of initial uplink sub-BWPs. Each entry in the list of information indicating frequency position and bandwidth may be an information element of the BWP (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). Multiple initial uplink sub-BWPs may have a common bandwidth and initialUplinkBWP-rc may indicate a common bandwidth with a list of frequency positions of the initial uplink sub-BWP. Multiple initial uplink sub-BWPs have a common subcarrierSpacing, a common cyclicPrefix, and initialUplinkBWP-rc shows a list of frequency locations of the initial uplink BWP and a common bandwidth, a common subcarrierSpacing, and a common cyclicPrefix. You may. Alternatively, the subcarrierSpacing and cyclicPrefix indicated by the initialUplinkBWP may be set in a plurality of initial uplink subBWPs. That is, the initialUplinkBWP-rc may be information for specifying the frequency position and bandwidth of each of the plurality of initial uplink sub-BWPs. However, the parameter indicating the setting of a plurality of initial uplink sub-BWPs may be set by the above-mentioned initialUplinkBWP. Parameters indicating the initial uplink BWP setting of a serving cell include parameters indicating the frequency position and bandwidth of the initial uplink BWP, subcarrierSpacing of the initial uplink BWP, and cyclicPrefix of the initial uplink BWP, and multiple initial uplink sub-BWPs. It may include a parameter indicating the setting of.

Terminal 1 does not support any of the frequency bands for the downlink of TDD and the uplink of FDD for the frequency bands shown in frequencyBandList contained in frequencyInfoDL and frequencyBandList contained in frequencyInfoUL. In addition, the cell may be regarded as a regulated cell. Terminal 1 supports one or more frequency bands for TDD downlink for the frequency band shown in frequencyBandList contained in frequencyInfoDL, or terminal 1 is included in frequencyInfoUL. Based on whether it supports one or more frequency bands for the FDD uplink for the frequency bands shown in frequencyBandList, terminal 1 determines if the cell is a regulated cell. You may. For example, based on the frequency band shown in frequencyBandList contained in frequencyInfoDL and / or the frequency band shown in frequencyBandList contained in frequencyInfoUL, and / or the capabilities of terminal device 1, terminal device 1 considers the cell to be a regulated cell. You may decide. For example, the terminal device 1 does not support any frequency band for the downlink of TDD for the frequency band shown in the frequencyBandList included in the frequencyInfoDL, and the terminal device 1 is included in the frequencyBandList included in the frequencyInfoUL. If no frequency band for the FDD uplink is supported for the indicated frequency band, the terminal device 1 may consider the cell to be a regulated cell.

In the terminal device 1, a plurality of initial uplink sub-BWPs may be set by the received SIB1. The terminal device 1 may determine whether the cell is a regulated cell based on the bandwidth of the initial uplink BWP set by the received SIB1 corresponding to the cell. Terminal 1 may determine if the cell is a regulated cell based on whether it supports the same or wider uplink bandwidth as the initial uplink BWP configured by SIB1. .. For example, if the terminal device 1 does not support an uplink bandwidth equal to or wider than the bandwidth of the initial uplink BWP set by SIB1, the terminal device 1 may consider the cell as a regulated cell. .. The terminal device 1 may determine whether the cell is a regulated cell based on the bandwidth of the plurality of initial uplink sub-BWPs set by the received SIB1 corresponding to the cell. The terminal device 1 supports the same or wider uplink bandwidth as the widest bandwidth of each of the plurality of initial uplink sub-BWPs set by SIB1. You may decide if it is a regulated cell. For example, if the terminal device 1 does not support the same or wider uplink bandwidth as the widest bandwidth of each of the plurality of initial uplink sub-BWPs set by SIB1, the terminal device 1 may use the terminal device 1. , The cell may be regarded as a regulated cell. Terminal device 1 is based on whether terminal device 1 supports the same or wider uplink bandwidth that is commonly set for multiple initial uplink sub-BWPs set by SIB1. May determine if is a regulated cell. For example, if the terminal device 1 does not support the same or wider uplink bandwidth as the bandwidth commonly set for the plurality of initial uplink sub-BWPs set by SIB1, the terminal device 1 will use the cell. May be regarded as a regulated cell. Terminal device 1 regulates the cell based on whether it supports the same or wider uplink bandwidth as specified by the parameters that configure multiple initial uplink sub-BWPs notified by SIB1. You may decide if it is a cell. For example, if terminal device 1 does not support the same or wider uplink bandwidth as specified by the parameters that configure multiple initial uplink sub-BWPs notified by SIB1, then terminal device 1 is said to be concerned. The cell may be regarded as a regulated cell. Terminal 1 determines if the cell is a regulated cell based on whether it supports uplink bandwidth equal to or wider than the reference bandwidth identified from the bandwidth notified by SIB1. It's okay. For example, if terminal device 1 does not support uplink bandwidth equal to or wider than the reference bandwidth identified from the bandwidth notified by SIB1, the terminal device 1 may consider the cell to be a regulated cell. good. However, the reference bandwidth may be the bandwidth specified by the bandwidth of one initial uplink BWP notified by SIB1 and the number of initial uplink sub-BWPs configured. However, the reference bandwidth may be the bandwidth specified by dividing one initial uplink BWP notified by SIB1 by a predetermined number.

The terminal device 1 may determine whether the cell is a regulated cell based on whether it supports uplink bandwidth equal to or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth equal to or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may consider the cell as a regulated cell. However, the carrier bandwidth may be a carrier bandwidth corresponding to the subcarrier interval of the initial uplink BWP set by the received SIB1. However, the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier interval common to a plurality of initial uplink subBWPs set in the received SIB1.

That is, the terminal device 1 has a bandwidth of the initial downlink BWP set by the received SIB1 corresponding to a certain cell, a bandwidth of a plurality of initial downlink sub-BWPs set by the received SIB1 corresponding to a certain cell, and the like. Bandwidth of the initial uplink BWP set by the received SIB1 corresponding to a cell, bandwidth of multiple initial uplink sub-BWPs set by the received SIB1 corresponding to a cell, received corresponding to a cell Based on the carrier bandwidth set by SIB1 and / or the capabilities of the terminal device 1, it may be determined whether the cell is a regulated cell.

However, the parameter set by SIB1 may be notified by SIB1 (or REDCAP SIB1), may be notified by another SIB (or REDCAP SIB), or may be notified by an RRC message.

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

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

Hereinafter, a random access procedure according to an embodiment of the present invention will be described.

Random access procedures are classified into two procedures: contention based (CB) and non-CB (non-CB) (CF: Contention Free). Conflict-based random access is also known as CBRA, and non-competitive-based random access is also known as CFRA.

The conflict-based random access procedure is initiated by PDCCH order, MAC entity, notification of beam failure from a lower layer, RRC, etc. If the beam failure notification is provided to the MAC entity of terminal device 1 from the physical layer of terminal device 1 and certain conditions are met, the MAC entity of terminal device 1 initiates a random access procedure. When the beam failure notification is provided to the MAC entity of terminal device 1 from the physical layer of terminal device 1, the procedure for determining whether a certain condition is satisfied and starting the random access procedure is called the beam failure recovery procedure. You may. This random access procedure is a random access procedure for a beam failure recovery request. Random access procedures initiated by a MAC entity include random access procedures initiated by a scheduling request procedure. The random access procedure for a beam failure recovery request may or may not be considered a random access procedure initiated by the MAC entity. Distinguish between a random access procedure for a beam failure recovery request and a scheduling request procedure because the random access procedure for a beam failure recovery request and the random access procedure initiated by the scheduling request procedure may have different procedures. You may do so. The random access procedure and scheduling request procedure for the beam failure recovery request may be a random access procedure initiated by the MAC entity. In one embodiment, the random access procedure initiated by the scheduling request procedure is referred to as the random access procedure initiated by the MAC entity, and the random access procedure for the beam failure recovery request is random access by notification of beam failure from the lower layer. It may be referred to as a procedure. Hereinafter, the start of the random access procedure when the notification of the beam failure from the lower layer is received may mean the start of the random access procedure for the beam failure recovery request.

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

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

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

The non-conflict-based random access procedure may be initiated when the terminal device 1 receives information from the base station apparatus 3 instructing the start of the random access procedure. The non-conflict-based random access procedure may be initiated when the MAC layer of terminal device 1 is notified of a beam failure by a lower layer. The terminal device 1 is instructed by the base station device 3 to perform non-conflict-based random access in the PDCCH order, and based on the information contained in the PDCCH order, the index of the non-conflict-based random access preamble and / or The time and frequency resources for transmitting the random access preamble (hereinafter referred to as PRACH opportunity (occasion)) may be selected, and the random access preamble corresponding to the selected index may be transmitted at the selected PRACH opportunity.

However, one PRACH opportunity may be a time / frequency resource in which one random access preamble format can be placed, and for terminal unit 1, the higher layer parameter that determines one or more PRACH opportunities is the base station. May be provided by device 3.

However, the terminal device 1 receives one or more reference signals (SS block and / or CSI-RS), is instructed to perform non-conflict-based random access in the PDCCH order, and 1 in the PDCCH order. The information contained in the PDCCH order when the index of one or more reference signals (SS block and / or CSI-RS) is shown and the index of the non-conflict-based random access preamble associated with the index of the reference signal and / Alternatively, you may select a PRACH opportunity to send a random access preamble and send the random access preamble corresponding to the selected index at the selected PRACH opportunity.

When the base station device 3 instructs the terminal device 1 to perform non-competitive base random access in the PDCCH order, the random access preamble transmitted from the terminal device 1 based on the information transmitted in the PDCCH order. You may receive it. When the base station device 3 instructs the terminal device 1 to perform non-conflict-based random access in the PDCCH order, the random access preamble transmitted from the terminal device 1 based on the information transmitted in the PDCCH order. The PRACH opportunity and / or random access preamble index used for may be identified / monitored.

Non-conflict-based random access is a quick way between the terminal device 1 and the base station device 3 when the base station device 3 and the terminal device 1 are connected but the handover or transmission timing of the mobile station device is not valid. It may be used to synchronize the uplink of. Non-conflict-based random access may be used to send a beam failure recovery request in the event of a beam failure in terminal device 1. However, the use of non-competitive random access is not limited to these.

The information instructing the start of the random access procedure may be referred to as message 0, Msg.0, PDCCH order, and the like.

The base station apparatus 3 assigns one or more non-competitive base random access preambles to the terminal apparatus 1 by dedicated signaling (also referred to as message 0 or Msg0) of the downlink. However, the non-conflict-based random access preamble may be a random access preamble that is not included in the set notified by broadcast signaling. When the base station apparatus 3 is transmitting a plurality of reference signals, the base station apparatus 3 is assigned a plurality of non-competitive base random access preambles corresponding to each of at least a part of the plurality of reference signals to the terminal apparatus 1. May be good.

Message 0 may be a handover (HO) command generated by the target base station device 3 and transmitted by the original base station device 3 for handover. Message 0 may be an SCG change command sent by base station apparatus 3 to change a secondary cell group (SCG). Handover commands and SCG change commands are also referred to as synchronous resets. This synchronization reconfiguration (such as reconfiguration with sync) is sent in an RRC message. Synchronous reconfiguration is used for RRC reconfiguration with synchronization to PCell (handover command, etc.) and RRC reconfiguration with synchronization with PSCell (SCG change command, etc.). Message 0 may be transmitted as an RRC signal and / or PDCCH. Message 0 sent by PDCCH may be referred to as PDCCH order. PDCCH orders may be sent in DCI in a DCI format. Message 0 may contain information to allocate a non-conflict-based random access preamble.

Even if the bit information notified in message 0 includes preamble index information, SSB index information, mask index information, uplink carrier index information, uplink BWP index information, and / or uplink sub-BWP index information. good.

The preamble index information is information indicating the value of the index ra-PreambleIndex of the random access preamble. If the preamble index information is a predetermined value (eg, 0b000000), terminal device 1 may randomly select one or more random access preambles available in the conflict-based random access procedure. ..

The SSB index information is information indicating an SS block used to determine a PRACH opportunity for PRACH transmission when the value indicated by the preamble index information is not 0 (corresponding bits are all 0). However, the SSB index information may be reserved if the value indicated by the preamble index information is 0.

The mask index information is information indicating the PRACH opportunities that can be used to send a random access preamble among the PRACH opportunities associated with the SS block indicated by the SSB index information when the value indicated by the preamble index information is not 0. .. However, the mask index information may be reserved when the value indicated by the preamble index information is 0.

The uplink carrier index information should send PRACH when the value indicated by the preamble index information is not 0 and the supplemental uplink (SUL) is set for terminal device 1 by the upper parameter in the cell. Information indicating whether the uplink carrier is a normal uplink (also called NUL or UL) or SUL. However, if the value indicated by the preamble index information is 0, or if the supplemental uplink (SUL) is not set for the terminal device 1 by the upper parameter in the cell, the uplink carrier index information is reserved. You may.

The uplink BWP index information is information indicating the index of the uplink BWP used for transmitting the random access preamble transmitted in the random access procedure starting from the message 0. If the uplink BWP index information is included in message 0, the PRACH opportunity available for random access preamble transmission identified by the same message 0 indicated by the SSB index information and mask index information is in the uplink BWP index information. The PRACH opportunity contained within the shown uplink BWP.

The uplink sub-BWP index information is information indicating the index of the uplink sub-BWP used for transmitting the random access preamble transmitted in the random access procedure starting from the message 0. If the uplink sub-BWP index information is included in message 0, the PRACH opportunity available for the first transmission of the random access preamble transmission identified by the same message 0 indicated by the SSB index information and mask index information is the uplink. The PRACH opportunity contained within the uplink sub-BWP indicated by the sub-BWP index information. However, if the same message 0 contains uplink BWP index information and uplink sub BWP index information, the PRACH opportunities available for PRACH transmission are within the uplink BWP and uplink sub indicated by the uplink BWP index information. It may be a PRACH opportunity within the uplink sub-BWP indicated by the BWP index information.

However, one common index information may be used for the uplink BWP index information and the uplink sub BWP index information. For example, if the common index information is the first value, the PRACH opportunity available for PRACH transmission is the PRACH opportunity that exists in the uplink sub-BWP in the uplink BWP corresponding to the first value. It may be there.

The terminal device 1 is a set of preambles available to the terminal device 1 when the random access preamble index specified in the PDCCH order is a predetermined value (for example, when all the bits indicating the index are 0). A conflict-based random access procedure may be performed in which one is randomly selected and transmitted.

FIG. 16 is a flow chart showing an example of a random access procedure using the PDCCH order in the terminal device 1 of the present embodiment. In step S1001 of FIG. 16, the terminal device 1 receives the PDCCH. In step S1002, the terminal device 1 determines whether the value of the preamble index information included in the received PDCCH order is 0b000000, and if it is not 0b000000 (S1002-No), proceeds to step S1003 and if it is 0b000000. (S1002-Yes) proceeds to step S1005. In step S1003, the terminal device 1 selects the uplink BWP corresponding to the uplink BWP index information included in the PDCCH order, and is specified in the uplink BWP by the SSB index and the mask index information included in the PDCCH order. Determine the available PRACH opportunities and proceed to step S1004. In step S1004, the terminal device 1 sets the preamble index indicated by the preamble index information, and proceeds to step S1007. In step S1005, terminal device 1 selects one of the received one or more SSBs, determines the next available PRACH opportunity corresponding to the selected SSB, and proceeds to step S1006. In step S1006, terminal device 1 randomly selects one or more random access preambles available in the conflict-based random access procedure, sets the preamble index, and proceeds to step S1007. In step S1007, the terminal device 1 transmits a random access preamble corresponding to the set preamble index at the determined PRACH opportunity.

[Initialize random access procedure]

The random access procedure satisfies the PDCCH order transmitted from the base station device 3 to the terminal device 1, the notification of the beam failure from the lower layer, the MAC entity itself of the terminal device 1, or a predetermined condition. If it is initiated by RRC.

The terminal device 1 receives the random access setting information via the upper layer before initiating the random access procedure. The random access setting information may include the following information / parameters or information / parameters for determining / setting the following information / parameters.

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

The prach-ConfigurationIndex is a parameter indicating a set of time and frequency resources (hereinafter referred to as PRACH opportunity (occasion)) available for transmission of one random access preamble. However, the prach-ConfigurationIndex may be given individually according to the type of terminal device 1 (for example, a REDCAP terminal device and other terminal devices). For example, the parameters may be given with different parameter names (eg prach-ConfigurationIndex and prach-ConfigurationIndex2) depending on the type of terminal device 1, and prach-ConfigurationIndex2 can be used to send a random access preamble for REDCAP. It may be a parameter indicating a set of PRACH opportunities. However, PRACH opportunities may also be referred to as random access channel (RACH) opportunities (RACH occasions) or random access channel transmission occasions (RACH transmission occasions). One or more sets of PRACH opportunities may be set for each reference signal (eg, SS block, CSI-RS or downlink transmit beam). For example, each of the one or more PRACH opportunities available for transmission of the random access preamble contained in the random access configuration information is the time for one random access preamble transmitted using the configured preamble format /. It may be a frequency resource. For example, each of the one or more PRACH opportunities available for transmission of the random access preamble contained in the random access configuration information is transmitted using one uplink transmit beam and using the configured preamble format. It may be a time / frequency resource for one random access preamble. Terminal 1 may select one or more sets of PRACH opportunities available for transmission of random access preambles based on the reference signal received (eg SS block, CSI-RS or downlink transmit beam). .. However, the PRACH opportunity may be associated with the configuration index prach-ConfigurationIndex notified by the random access configuration information. However, a set of one or more PRACH opportunities may be referred to as a random access resource or a random access channel resource (RACH resource).

preambleReceivedTargetPower is a parameter related to the initial power of the random access preamble. However, preambleReceivedTargetPower may be given individually depending on the type of terminal device 1. For example, the parameter may be given by a different parameter name (for example, preambleReceivedTargetPower and preambleReceivedTargetPower2) depending on the type of the terminal device 1, and preambleReceivedTargetPower2 may be a parameter related to the initial power of the random access preamble for REDCAP.

rsrp-Threshold SSB is a parameter indicating the threshold value of RSRP for selecting SSB. However, the rsrp-Threshold SSB may be individually given depending on the type of the terminal device 1. For example, the parameters may be given with different parameter names (eg, rsrp-ThresholdSSB and rsrp-ThresholdSSB2) depending on the type of terminal device 1, where rsrp-ThresholdSSB2 sets the RSRP threshold for REDCAP SSB selection. It may be the parameter shown.

RSRP-Threshold_ce is a parameter indicating the threshold value of RSRP for selecting one set from the plurality of random access resource sets when a plurality of random access resource sets are set in the uplink BWP. For example, the plurality of sets of random access resources may be assigned to the level of coverage enhancement (CE level) of the terminal device 1, respectively.

msgA-RSRP-Threshold is a 2-step random access type and 4 when both a set of random access resources for 2-step random access and a set of random access resources for 4-step random access are set in the uplink BWP. Step A parameter that indicates the RSRP threshold for selecting one of the random access types.

powerRampingStep is a parameter indicating the amplification value at the time of power ramping. However, the powerRampingStep may be individually given depending on the type of the terminal device 1. For example, the parameter may be given by a different parameter name (for example, powerRampingStep and powerRampingStep2) depending on the type of the terminal device 1, and powerRampingStep2 is a parameter indicating an amplification value during power ramping in a random access procedure for REDCAP. May be.

ra-PreambleIndex is a parameter indicating the index of the random access preamble.

ra-ssb-OccasionMaskIndex is a parameter that defines the PRACH opportunity assigned to an SSB for the MAC entity of terminal device 1 to send a random access preamble.

The msgA-SSB-SharedRO-MaskIndex is a parameter that indicates a subset of the 4-step random access type PRACH opportunities in each SSB that are shared with the 2-step random access type PRACH opportunities. If the 2-step random access type PRACH opportunity is shared with the 4-step random access type PRACH opportunity and the msgid-SSB-SharedRO-MaskIndex is not set, then all 4-step random access type PRACH opportunities are available. May be available for 2-step random access type.

SSB-SharedRO-MaskIndex_rc is a parameter that indicates a subset of the 4-step random access type PRACH opportunities in each SSB that are shared with the REDCAP PRACH opportunities. If the 2-step random access type PRACH opportunity is shared with the 4-step random access type PRACH opportunity and SSB-SharedRO-MaskIndex_rc is not set, then all 4-step random access type PRACH opportunities are REDCAP. It may be available for random access.

preambleTransMax is a parameter indicating the maximum number of random access preamble transmissions. However, preambleTransMax may be given individually according to the type of terminal device 1 (for example, a REDCAP terminal device and other terminal devices). For example, the parameter may be given with different parameter names (eg, preambleTransMax and preambleTransMax2) depending on the type of terminal device 1, where preambleTransMax2 may be a parameter indicating the maximum number of random access preamble transmissions for REDCAP. ..

ssb-perRACH-OccasionAndCB-PreamblesPerSSB is the number of SSBs mapped to each PRACH opportunity of 4-step random access type and the contention-based random access (CBRA) preambles mapped to each SSB. A parameter that defines the number of. However, ssb-perRACH-OccasionAndCB-PreamblesPerSSB may be individually given according to the type of terminal device 1 (for example, REDCAP terminal device and other terminal device). For example, the parameters may be given by different parameters (for example, ssb-perRACH-OccasionAndCB-PreamblesPerSSB and ssb-perRACH-OccasionAndCB-PreamblesPerSSB2) depending on the type of the terminal device 1, and ssb-perRACH-OccasionAndCB-PreamblesPerSSB2 is REDCAP. It may be a parameter that defines the number of SSBs mapped to each PRACH opportunity for and the number of CBRA preambles mapped to each SSB.

msgA-CB-PreamblesPerSSB-PerSharedRO is a CBRA preamble for the 2-step random access type that is mapped to each SSB when PRACH opportunities are shared between the 2-step random access type and the 4-step random access type. A parameter that defines a number.

CB-PreamblesPerSSB-PerSharedRO_rc is a parameter that defines the number of CBRA preambles for REDCAP that are mapped to each SSB when PRACH opportunities are shared by the 4-step random access type and REDCAP.

ra-ResponseWindow is a parameter indicating a time window for monitoring a random access response. However, the ra-ResponseWindow may be individually given depending on the type of the terminal device 1. For example, the parameters may be given with different parameter names (eg, ra-ResponseWindow and ra-ResponseWindow2) depending on the type of terminal device 1, where ra-ResponseWindow2 is for monitoring a random access response for REDCAP. It may be a parameter indicating a time window.

However, the random access setting information may include information common to the cells, or may include dedicated information that differs for each terminal.

In the random access procedure according to the embodiment of the present invention, some or all of the following variables may be used.

PREAMBLE_INDEX is a variable indicating the index of the random access preamble used in the terminal device 1.

PREAMBLE_TRANSMISSION_COUNTER is a variable indicating the counter value of the number of transmissions of the random access preamble transmitted by the terminal device 1 in the random access procedure.

PREAMBLE_POWER_RAMPING_COUNTER is a variable indicating the counter value of the number of times the terminal device 1 performs power ramping in the random access procedure.

PREAMBLE_POWER_RAMPING_STEP is a variable indicating the power amplification value in the power ramping performed by the terminal device 1 in the random access procedure.

PREAMBLE_RECEIVED_TARGET_POWER is a variable indicating the target received power when the terminal device 1 transmits a random access preamble.

PREAMBLE_BACKOFF is a variable indicating the backoff value when the terminal device 1 transmits a random access preamble.

PCMAX is a variable indicating the value of the maximum transmission power when the terminal device 1 transmits a random access preamble.

TEMPORARY_C-RNTI is a variable indicating the value of C-RNTI temporarily used by the terminal device 1 in the random access procedure.

RA_TYPE is a variable indicating whether the random access type used by the terminal device 1 in the random access procedure is 2-step random access or 4-step random access.

[Random access resource selection]

The MAC entity of terminal device 1 selects the resource to be used for random access by the following procedure. However, the procedure below may be applied if the random access procedure is not for beam failure recovery.

If the ra-PreambleIndex is provided in PDCCH to the terminal device 1 and the value of the ra-PreambleIndex is not 0b000000, the terminal device 1 sets the value of the ra-PreambleIndex provided in PREAMBLE_INDEX and the index notified by PDCCH. Select SSB.

When the terminal device 1 (which may be the MAC entity in the terminal device 1) transmits the random access preamble, the following processing is sequentially performed for each random access preamble. The terminal device 1 increments a counter (referred to as PREAMBLE_TRANSMISSION_COUNTER) that counts the number of random access preamble transmissions by 1 when at least all of the following conditions are satisfied.
(1) PREAMBLE_TRANSMISSION_COUNTER is greater than 1
(2) The suspension notification of the power ramping counter (called PREAMBLE_POWER_RAMPING_COUNTER) has not been received from the lower layer.
(3) LBT failure notification has not been received from the lower layer for the last random access preamble transmission.
(4) The selected SSB or CSI-RS has not changed since the last random access preamble transmission.

Next, the terminal device 1 sets the target received power (PREAMBLE_RECEIVED_TARGET_POWER) of the random access preamble. For example, terminal 1 selects the value of DELTA_PREAMBLE and sets PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER -1) * PREAMBLE_POWER_RAMPING_STEP.

Terminal 1 calculates the RA-RNTI associated with the PRACH opportunity to which the random access preamble is transmitted. However, the terminal device 1 does not have to calculate RA-RNTI if the random access preamble to be transmitted is a CFRA preamble for a beam failure recovery request.

The MAC entity of terminal unit 1 instructs the physical layer to send a random access preamble with the selected PRACH opportunity, the corresponding RA-RNTI, PREAMBLE_INDEX and PREAMBLE_RECEIVED_TARGET_POWER.

However, the RA-RNTI associated with the PRACH opportunity to which the random access preamble was sent has information / index about the time resource of the PRACH opportunity, information / index about the frequency resource, information / index about the type of uplink carrier, and uplink. Information / index about link BWP, information / index about uplink sub BWP,
It may be calculated based on the RSRP-based information / index and / or information / index on the type of terminal device 1 corresponding to the random access preamble. The terminal device 1 has information / index about time resource of PRACH opportunity, information / index about frequency resource, information / index about type of uplink carrier, information / index about uplink BWP, information / index about uplink sub-BWP, random. Calculate RA-RNTI based on the RSRP-based information / index and / or information / index of the terminal device 1 type of SSB corresponding to the access preamble. For example, RA-RNTI may be calculated as follows.

(Number 1)
RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id

However, s_id is the index of the first OFDM symbol of the PRACH opportunity (0 <= s_id <14).
T_id is the index (0 <= t_id <80) of the first slot of the PRACH opportunity in the system frame, and the subcarrier interval that determines t_id is based on the value of μ. f_id is the index of PRACH opportunities in the frequency domain (0 <= f_id <8) and ul_carrier_id is the index indicating the uplink carrier used for random access preamble transmission (eg 0 for normal uplink (NUL) carriers). , Use 1 for supplemental uplink (SUL) carriers).

However, in the terminal device 1 according to the embodiment of the present invention, RA-RNTI may be calculated by the following formula.

(Number 2)
RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id + 14 * 80 * 8 * 2 * 2 * r_id

As an example, r_id may be the index of the uplink BWP used to send the corresponding random access preamble. As another example, r_id may be the index of the uplink sub-BWP used to send the corresponding random access preamble. As another example, r_id may be an RSRP-based index of the SSB corresponding to the random access preamble. For example, r_id is an index based on the result of comparing the threshold with the RSRP of the SSB corresponding to the random access preamble (for example, 1 is used when RSRP is above the threshold and 0 is used when RSRP is below the threshold). good. An index based on the result of comparing the RSRP and the threshold value is called a CE (Coverage enhancement) level, an RSRP level, or the like. For example, r_id may be an index indicating the CE level. However, the number of thresholds to be compared with RSRP may be plural, and in that case, the value of r_id may be more than two values. As another example, r_id is an index corresponding to the type of terminal device 1 (for example, 1 is used when the terminal device 1 is a REDCAP terminal device, and 0 is used when the terminal device 1 is another terminal). good. However, the types of terminals may be more than two types, and r_id may be more than two values.

The RNTI associated with the PRACH opportunity to which the random access preamble is transmitted may use an RNTI with a different name / definition depending on the type of terminal device 1. For example, the RNTI associated with the PRACH opportunity used by REDCAP terminal 1 to send a random access preamble is R-RA-RNTI, and the PRACH opportunity used by other types of terminal 1 to send a random access preamble. The associated RNTI may be RA-RNTI shown in Equation 1 or RA-RNTI shown in Equation 2. For terminal device 1, R-RA-RNTI may be calculated by the following formula.

(Number 3)
R-RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id + 14 * 80 * 8 * 2 * 2

R-RA-RNTI may be applied to the treatment / description using RA-RNTI according to this embodiment.

However, RA-RNTI and / or R-RA-RNTI may be calculated based on the plurality of information exemplified above. For example, RA-RNTI and / R-RA-RNTI are s_id, t_id, f_id, ul_carrier_id, the index of the uplink BWP used to send the corresponding random access preamble, and the uplink sub BWP used to send the corresponding random access preamble. Index, index based on RSRP of SSB corresponding to random access preamble and / or index corresponding to type of terminal device 1 may be calculated.

FIG. 17 is a flow chart showing an example of a random access procedure using RNTI in the terminal device 1 of the present embodiment. In step S2001 of FIG. 17, terminal device 1 transmits a random access preamble at one or more PRACH opportunities and proceeds to step S2002. In step S2002, the terminal device 1 receives the DCI including the CRC bit scrambled by RNTI calculated based on the first information on the PDCCH, and proceeds to step S2003. However, the first information is, for example, an index of the uplink BWP used for transmitting the corresponding random access preamble, an index of the uplink sub-BWP used for transmitting the corresponding random access preamble, and an SSB corresponding to the random access preamble. It may be an index based on RSRP and / or an index corresponding to the type of terminal device 1. In step S2003, terminal device 1 receives the random access response scheduled by the received DCI and proceeds to step S2004. In step S2004, terminal device 1 transmits a PUSCH scheduled with the received random access response.

[Receive Random Access Response]

The terminal device 1 that has transmitted the random access preamble performs the following processing.

Terminal 1 starts the window (ra-ResponseWindow) set by the upper layer parameter (RACH-ConfigCommon) at the first PDCCH opportunity after a predetermined symbol or more from the last symbol that sent the random access preamble. However, the first PDCCH opportunity is the first symbol of the earliest CORESET configured to receive PDCCH for terminal device 1, one or more symbols after the last symbol of the PRACH opportunity that sent the random access preamble. It may be there. Terminal 1 monitors the PDCCH for the random access response identified by the calculated RA-RNTI while the window is running. However, the PDCCH specified by RA-RNTI may be a PDCCH that detects a DCI (which may be a specific DCI format) including a CRC scrambled by the RA-RNTI.

The terminal device 1 can receive the downlink assignment information (downlink assignment) valid in the PDCCH specified by the calculated RA-RNTI, and can decode the transport block including the received random access response, and further, the random access. If the response contains a MAC subPDU with a random access preamble index that corresponds to the random access preamble sent, then the random access response is considered successful.

However, the DCI received by the PDCCH specified by the calculated RA-RNTI contains fields related to frequency domain resource allocation, time domain resource allocation, MCS, SFN LSBs, SSB RSRP, and / or terminal device type. include.

The frequency domain resource allocation field indicates frequency resource allocation information for the transport block of the corresponding random access response.

The time domain resource allocation field indicates the time resource allocation information for the transport block of the corresponding random access response.

The MCS field indicates the MCS index corresponding to the modulation scheme and code rate applied to the corresponding random access response transport block.

The field for the LSBs of the SFN indicates the LSB (Least Significant Bit) s of one or more bits of the SFN of the radio frame to which the corresponding random access preamble was transmitted.

The field related to RSRP of SSB is an index based on the result of comparing the threshold value with the RSRP of the corresponding SSB used by the terminal device 1 to send the random access preamble (for example, 1 is used when RSRP is equal to or higher than the threshold value, and RSRP is the threshold value. If less than, 0 is used). However, the number of threshold values to be compared with RSRP may be plural, and in that case, the bit of the field may be 2 bits or more. However, the threshold value may be given to the terminal device 1 as an upper parameter.

The field related to the type of the terminal device indicates the index corresponding to the type of the terminal device 1 (for example, 1 is used when the terminal device 1 is a terminal device of REDCAP, and 0 is used when the terminal device 1 is another terminal). However, the type of terminal may be more than two types, and the size of the field may be 2 bits or more.

The terminal device 1 detects a DCI containing a CRC scrambled by RA-RNTI corresponding to the transmitted random access preamble, and one or more fields contained in the DCI satisfy a predetermined condition and the corresponding PDSCH. When the transport block is received in, the transport block is passed to the upper layer. However, the conditions that the DCI should satisfy are that the value indicated by the SFN LSBs field contained in the DCI matches the value of the SFN LSBs to which the terminal device 1 sent the random access preamble, and the RSRP of the SSB. The value indicated by the field matches the index based on the result of comparing the threshold with the RSRP selected by terminal device 1 when sending the random access preamble, and / or the value indicated by the field for the terminal device type. However, it may match the index corresponding to the type of the terminal device 1.

The upper layer of terminal device 1 analyzes the passed transport block, and if the ID of the transmitted random access preamble and the random access preamble ID included in the random access response message of the transport block match, the terminal device 1 Notify the uplink grant to the physical layer of.

The terminal device 1 that succeeds in receiving the random access response notifies the lower layer of the serving cell that transmitted the random access preamble of the value of preambleReceivedTargetPower applied to the last transmitted random access preamble and the amount of power ramping. , Notify the received uplink grant.

Beam management is the analog and / or digital beam in the transmitting device (base station device 3 in the case of downlink and terminal device 1 in the case of uplink) and the receiving device (terminal device 1 in the case of downlink). , In the case of uplink, it may be the procedure of the base station device 3 and / or the terminal device 1 for matching the directivity of the analog and / or digital beam in the base station device 3) and acquiring the beam gain.

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

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

Beam management may include beam selection and beam improvement. Beam recovery is also referred to as beam failure recovery, and beam recovery may include the following procedures.
-Detection of beam failure-Discovery of new beam-Send beam recovery request-Monitor response to beam recovery request

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

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

If the Long Term Property of a channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port, then the two antenna ports are said to be QCLs. .. The long interval characteristics of the channel include one or more of delay spreads, Doppler spreads, Doppler shifts, average gains, and average delays. For example, if antenna port 1 and antenna port 2 are QCL with respect to average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1.

This QCL can also be extended to beam management. Therefore, a QCL extended to space may be newly defined. For example, the long term property of a channel in the QCL assumption of a spatial domain includes the angle of arrival at a radio link or channel (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and / or angle spread. (Angle Spread, for example ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread)
of Arrival)), sending angle (AoD, ZoD, etc.) and its angle spread (Angle Spread, such as ASD (Angle Spread of Departure) and ZSD (Zenith angle Spread of Departure)), spatial correlation (Spatial Correlation), receiving spatial parameters. May be.

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

As the QCL type, a combination of long interval characteristics that can 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 space parameter

The QCL type described above sets and / or sets the QCL assumptions of one or two reference signals in the RRC and / or MAC layer and / or DCI with the PDCCH or PDSCH DMRS as a Transmission Configuration Indication (TCI). You may instruct. For example, if the SS / PBCH block index # 2 and QCL type A + QCL type B are set and / or instructed as one of the TCI states when terminal 1 receives PDCCH, terminal 1 will When receiving PDCCH DMRS, it is regarded as Doppler shift, Doppler spread, average delay, delay spread, reception space parameter and long interval characteristic of channel in reception of SS / PBCH block index # 2, and DMRS of PDCCH is received and synchronized. Propagation path estimation may be performed. At this time, the reference signal (SS / PBCH block in the above example) specified by TCI is the source reference signal, and the reference affected by the long section characteristics inferred from the long section characteristics of the channel when receiving the source reference signal. The signal (PDCCH DMRS in the above example) may be referred to as the target reference signal. Further, the TCI may be instructed to the terminal device 1 by the MAC layer or DCI by setting one or more TCI states and a combination of the source reference signal and the QCL type for each state by RRC.

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

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

Hereinafter, the configuration of the apparatus in this embodiment will be described.

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

The upper layer processing unit 14 outputs the uplink data (which may be referred to as a transport block) generated by the user's operation or the like to the wireless transmission / reception unit 10. The upper layer processing unit 14 includes a medium access control (MAC) layer, a packet data integration protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs some or all of the layer processing. The upper layer processing unit 14 has a function of acquiring bit information of a MIB (which may be a REDCAP MIB), an SIB1 (which may be a REDCAP SIB1), and other SIBs (which may be a REDCAP SIB). You may. Even if the upper layer processing unit 14 has a function of determining a PRACH opportunity based on the SSB index, the mask index, the downlink BWP index, the downlink sub BWP index, the uplink BWP index, and / or the uplink sub BWP index. good. The upper layer processing unit 14 may have a function of calculating the value of RNTI (including RA-RNTI and R-RA-RNTI). For example, the upper processing unit 14 uses the RNTI value as an index in the frequency domain of the PRACH opportunity, an index of the uplink BWP in which the PRACH opportunity is arranged, an index of the uplink sub-BWP in which the PRACH opportunity is arranged, and a terminal device 1. It may have a function to calculate based on the type of, the index of the downlink BWP, and / or the index of the downlink sub BWP.

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

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

The wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, coding, and decoding. The wireless transmission / reception unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The wireless transmission / reception unit 10 generates a transmission signal by modulating and encoding the data, and transmits the transmission signal to the base station device 3 and the like. The wireless transmission / reception unit 10 outputs an upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. Further, the wireless transmission / reception unit 10 generates and transmits an uplink signal (including PUCCH and / or PUSCH) based on an instruction from the upper layer processing unit 14. The wireless transmitter / receiver 10 may be provided with a function of receiving a random access response, PDCCH and / or PDSCH. The wireless transmitter / receiver 10 may have a function of transmitting PRACH (which may be a random access preamble), PUCCH and / or PUSCH. The wireless transmission / reception unit 10 may have a function of receiving DCI on the PDCCH. The wireless transmission / reception unit 10 may have a function of outputting the DCI received by the PDCCH to the upper layer processing unit 14. The radio transmitter / receiver 10 may have a function of receiving DMRS for SSB, PSS, SSS, PBCH, PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The wireless transmission / reception unit 10 may have a function of receiving the SS / PBCH block and / or the REDCAP PBCH block. The wireless transmission / reception unit 10 may have a function of receiving a system information block (SIB1, REDCAP SIB1, SIB and / or REDCAP SIB) corresponding to a predetermined cell.

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

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

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

The RF unit 12 removes excess frequency components from the analog signal input from the baseband unit 13 using a low-pass filter, up-converts the analog signal to the carrier frequency, and transmits it via the antenna unit 11. do. Further, the RF unit 12 amplifies the electric power. Further, the RF unit 12 may have a function of determining the transmission power of the uplink signal and / or the uplink channel to be transmitted in the service area cell. The RF unit 12 is also referred to as a transmission power control unit.

FIG. 20 is a schematic block diagram showing the configuration of the base station apparatus 3 of the present embodiment. As shown in the figure, the base station apparatus 3 includes a wireless transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transmission / reception unit 30 is also referred to as a transmission unit 30, a reception unit 30, a monitor unit 30, or a physical layer processing unit 30. Further, a control unit that controls the operation of each unit based on various conditions may be separately provided. The upper layer processing unit 34 is also referred to as a processing unit 34, a determination unit 34, or a control unit 34.

The upper layer processing unit 34 includes a medium access control (MAC) layer, a packet data integration protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio). Resource Control: RRC) Performs some or all of the layer processing. The upper layer processing unit 34 may have a function of generating DCI based on the upper layer signal transmitted to the terminal device 1 and the time resource for transmitting the PUSCH. The upper layer processing unit 34 may have a function of outputting the generated DCI or the like to the wireless transmission / reception unit 30. The upper layer processing unit 34 may have a function of generating bit information of the transport block of the MIB. The upper layer processing unit 34 may have a function of generating bit information of the transport block of the REDCAP MIB. The upper layer processing unit 34 has a function of identifying / determining a PRACH opportunity based on the SSB index, mask index, downlink BWP index, downlink sub BWP index, uplink BWP index, and / or uplink sub BWP index. May be. The upper layer processing unit 34 may have a function of calculating the value of RNTI (including RA-RNTI and R-RA-RNTI). For example, the upper processing unit 34 uses the RNTI value as an index in the frequency domain of the PRACH opportunity, an index of the uplink BWP in which the PRACH opportunity is arranged, an index of the uplink sub-BWP in which the PRACH opportunity is arranged, and a terminal device 1. It may have a function to calculate based on the type of, the index of the downlink BWP, and / or the index of the downlink sub BWP.

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

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 processes the RRC layer. The wireless resource control layer processing unit 36 generates a DCI (uplink grant, downlink grant) including resource allocation information in the terminal device 1. The radio resource control layer processing unit 36 generates downlink data (transport block (TB), random access response (RAR)), system information, RRC message, MAC CE (Control Element), etc., which are arranged in DCI and PDSCH. Or, acquire it from the upper node and output it to the wireless transmission / reception unit 30. Further, the wireless resource control layer processing unit 36 manages various setting information / parameters of each terminal device 1. The wireless resource control layer processing unit 36 may set various setting information / parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 transmits / notifies information indicating various setting information / parameters. The radio resource control layer processing unit 36 may transmit / notify information for identifying the setting of one or more reference signals in a cell.

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

The wireless transmission / reception unit 30 transmits a signal (RRC message) of an upper layer, DCI, and the like to the terminal device 1. Further, the wireless transmission / reception unit 30 receives the uplink signal transmitted from the terminal device 1 based on the instruction from the upper layer processing unit 34. The wireless transmitter / receiver 30 may have a function of transmitting PDCCH and / or PDSCH. The wireless transmitter / receiver 30 may have a function of receiving one or more PUCCHs and / or PUSCHs. The wireless transmission / reception unit 30 may have a function of transmitting DCI by PDCCH. The wireless transmission / reception unit 30 may have a function of transmitting the DCI output by the upper layer processing unit 34 by PDCCH. The radio transmitter / receiver 30 may have a function of transmitting DMRS for SSB, PSS, SSS, PBCH, PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The wireless transmission / reception unit 30 may have a function of transmitting an SS / PBCH block and / or a REDCAP PBCH block. The wireless transmission / reception unit 30 may have a function of transmitting an RRC message (which may be an RRC parameter). The wireless transmission / reception unit 30 may have a function of the terminal device 1 transmitting a system information block (SIB1, REDCAP SIB1, SIB and / or REDCAP SIB). Since some functions of the wireless transmission / reception unit 30 are the same as those of the wireless transmission / reception unit 10, the description thereof will be omitted. When the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless transmission / reception unit 30 may be included in each transmission / reception point 4.

Further, the upper layer processing unit 34 transmits (transfers) a control message or user data between the base station devices 3 or between the upper network device (MME, S-GW (Serving-GW)) and the base station device 3. ) Or receive. In FIG. 20, other components of the base station device 3 and the transmission path of data (control information) between the components are omitted, but other functions necessary for operating as the base station device 3 are provided. It is clear that it has a plurality of blocks as components. For example, the upper layer processing unit 34 includes a radio resource management layer processing unit and an application layer processing unit.

The "part" in the figure is an element that realizes the functions and procedures of the terminal device 1 and the base station device 3, which are also expressed by terms such as sections, circuits, constituent devices, devices, and units.

Each of the portions of reference numeral 10 to reference numeral 16 included in the terminal device 1 may be configured as a circuit. Each of the portions of reference numeral 30 to reference numeral 36 included in the base station apparatus 3 may be configured as a circuit.

(1) The terminal device 1 according to the first aspect of the present invention is a downlink including a transmitter 10 that transmits a random access preamble at a physical random access channel opportunity and a CRC bit scrambled by a wireless network temporary identifier (RNTI). A receiver 10 that receives control information (DCI) on a physical downlink control channel (PDCCH) and receives a random access response scheduled by said DCI is provided, and the value of the RNTI uses the first information. Is calculated.

(2) In the first aspect of the present invention, the first information may be at the RSRP level.

(3) In the first aspect of the present invention, the receiving unit 10 receives one or more synchronization signal blocks (SSBs), and the first information is the above-mentioned one or more SSBs. It may be determined based on the reference signal received power (RSRP) of the SSB corresponding to the random access preamble.

(4) In the first aspect of the present invention, the first information may be determined by comparing the RSRP with one or more thresholds indicated by higher parameters received from the base station apparatus 3.

(5) In the first aspect of the present invention, the first information may be information indicating the type of the terminal device 1.

(6) The base station device 3 according to the second aspect of the present invention temporarily connects the terminal device 1 to the receiving unit 30 that receives a random access preamble at the opportunity of a physical random access channel (PRACH) and the terminal device 1. A transmitter 30 that transmits downlink control information (DCI) including CRC bits scrambled by an identifier (RNTI) on a physical downlink control channel (PDCCH) and transmits a random access response scheduled by the DCI. The value of RNTI is calculated based on the first information.

(7) In the second aspect of the present invention, the first information may be the RSRP level in the terminal device 1.

(8) In the second aspect of the present invention, the first information may be information associated with the reference signal received power (RSRP) in the terminal device 1.

(9) In the second aspect of the present invention, the first information may be determined by the terminal device 1 in comparison with the RSRP and one or more thresholds transmitted to the terminal device.

(10) In the second aspect of the present invention, the first information may be information indicating the type of the terminal device 1.

(11) The terminal device 1 according to the third aspect of the present invention has a transmission unit 10 that transmits a random access preamble at the opportunity of a physical random access channel (PRACH) and a physical downlink control channel (DCI) that transmits downlink control information (DCI). A receiver 10 that receives on a PDCCH) and receives a random access response scheduled on the DCI, wherein the DCI includes a field of first information.

(12) In the third aspect of the present invention, the first information may be at the RSRP level.

(13) In the third aspect of the present invention, the receiving unit 10 receives one or more synchronization signal blocks (SSBs), and the first information is the above-mentioned one or more SSBs. It may be determined based on the reference signal received power (RSRP) of the SSB corresponding to the random access preamble.

(14) In the third aspect of the present invention, the first information may be determined by comparing the RSRP with one or more thresholds indicated by higher parameters received from the base station apparatus 3.

(15) In the third aspect of the present invention, the first information may be information indicating the type of the terminal device 1.

(16) The base station apparatus 3 according to the fourth aspect of the present invention receives a random access preamble from the terminal apparatus 1 at the opportunity of a physical random access channel (PRACH), and a downlink control information (DCI). A transmitter 30 that transmits on a downlink control channel (PDCCH) and transmits a random access response scheduled by said DCI, wherein said DCI includes a field of first information.

(17) In the fourth aspect of the present invention, the first information may be the RSRP level in the terminal device 1.

(18) In the fourth aspect of the present invention, the first information may be information associated with the reference signal received power (RSRP) in the terminal device 1.

(19) In a fourth aspect of the invention, the first information may be determined by the terminal device 1 in comparison to the RSRP and one or more thresholds transmitted to the terminal device 1. ..

(20) In the fourth aspect of the present invention, the first information may be information indicating the type of the terminal device 1.

(21) The terminal device 1 in the fifth aspect of the present invention has a transmitter 10 that transmits a random access preamble at the opportunity of a physical random access channel (PRACH) and a CRC bit scrambled by a wireless network temporary identifier (RNTI). A receiver 10 that receives downlink control information (DCI) including downlink control channel (PDCCH) and receives a random access response scheduled in said DCI, wherein the value of the RNTI is the PRACH opportunity. It is calculated using the index in the frequency region of the above and the index of the uplink BWP in which the PRACH opportunity is arranged.

(22) The base station apparatus 3 according to the sixth aspect of the present invention is a receiver 30 that receives a random access preamble from the terminal apparatus 1 at the opportunity of a physical random access channel (PRACH), and a wireless network temporary identifier (RNTI). A transmitter 30 that transmits downlink control information (DCI) including scrambled CRC bits on a physical downlink control channel (PDCCH) and transmits a random access response scheduled by the DCI, and the value of the RNTI is , The index in the frequency region of the PRACH opportunity and the index of the uplink BWP in which the PRACH opportunity is arranged are used for calculation.

(23) The terminal device 1 in the seventh aspect of the present invention receives one or more synchronization signal blocks (SSBs) and indicates downlink control information (DCI) indicating a PDCCH order instructing the start of a random access procedure. The receiver 10 receives the information on the physical downlink control channel (PDCCH), the control unit 14 starts the random access procedure in the PDCCH order, and the transmitter 10 transmits the random access preamble at the physical random access channel (PRACH) opportunity. The DCI includes an SSB index, a mask index, and an uplink BWP index indicating one of the one or more SSBs, and the control unit 14 has the SSB index, the mask index, and the like. , And the PRACH opportunity is determined based on the uplink BWP index.

(24) The base station apparatus 3 in the eighth aspect of the present invention transmits one or more synchronization signal blocks (SSBs) and indicates downlink control information (DCI) indicating a PDCCH order indicating the start of a random access procedure. ) Is transmitted on the physical downlink control channel (PDCCH), and the transmitter 30
A receiver 30 that receives a random access preamble on a physical random access channel (PRACH) opportunity, and the DCI has an SSB index, a mask index, and an uplink BWP indicating one of the one or more SSBs. The PRACH opportunity, including the index, is a time / frequency resource based on the SSB index, the mask index, and the uplink BWP index.

(25) The terminal device 1 in the ninth aspect of the present invention receives one or more synchronization signal blocks (SSBs) and indicates downlink control information (DCI) indicating a PDCCH order instructing the start of a random access procedure. The receiver 10 receives the information on the physical downlink control channel (PDCCH), the control unit 14 starts the random access procedure in the PDCCH order, and the transmitter 10 transmits the random access preamble at the physical random access channel (PRACH) opportunity. The DCI includes an SSB index, a mask index, and a downlink BWP index indicating one of the one or more SSBs, and the control unit 14 has the SSB index, the mask index, and the like. , And the PRACH opportunity is determined based on the downlink BWP index.

(26) The base station apparatus 3 in the tenth aspect of the present invention transmits one or more synchronization signal blocks (SSBs) and indicates downlink control information (DCI) indicating a PDCCH order indicating the start of a random access procedure. A transmitter 30 that transmits) on a physical downlink control channel (PDCCH) and a receiver 30 that receives a random access preamble on a physical random access channel (PRACH) opportunity. It includes an SSB index, a mask index, and a downlink BWP index indicating one of a plurality of SSBs, and the PRACH opportunity is a time / frequency resource based on the SSB index, the mask index, and the downlink BWP index.

As a result, the terminal device 1 and the base station device 3 can efficiently communicate with each other. For example, the terminal device 1 can perform a random access procedure based on its own terminal type or RSRP of SSB with the base station device 3.

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

The program for realizing the functions of the embodiments according to the present invention may be recorded on a computer-readable recording medium. It may be realized by loading a program recorded on this recording medium into a computer system and executing the program. The term "computer system" as used herein is a computer system built into a device and includes hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" is a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short time, or another recording medium that can be read by a computer. Is also good.

Also, each functional block or feature of the device used in the embodiments described above may be implemented or implemented in an electric circuit, eg, an integrated circuit or a plurality of integrated circuits. Electrical circuits designed to perform the functions described herein can be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or others. Programmable Logic Devices, Discrete Gate or Transistor Logic, Discrete Hardware Components, or Combinations thereof. The general purpose processor may be a microprocessor, a conventional processor, a controller, a microcontroller, or a state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or a plurality of aspects of the present invention can also use a new integrated circuit according to the technology.

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

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

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

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

Claims (4)

It ’s a terminal device,
A transmitter that sends a random access preamble on a physical random access channel (PRACH) opportunity,
With a receiver that receives downlink control information (DCI) containing CRC bits scrambled by the wireless network temporary identifier (RNTI) on the physical downlink control channel (PDCCH) and receives the random access response scheduled by the DCI. , Equipped with
The value of the RNTI is calculated using the index in the frequency domain of the PRACH opportunity and the index of the uplink BWP in which the PRACH opportunity is located.
Terminal device. It ’s a base station device,
A receiver that receives a random access preamble from a terminal device on a physical random access channel (PRACH) opportunity.
A transmitter that transmits downlink control information (DCI) including CRC bits scrambled by the wireless network temporary identifier (RNTI) on the physical downlink control channel (PDCCH) and transmits a random access response scheduled by the DCI. Prepare,
The value of the RNTI is calculated using the index in the frequency domain of the PRACH opportunity and the index of the uplink BWP in which the PRACH opportunity is located.
Base station equipment. It is a communication method of the terminal device.
Send a random access preamble at the Physical Random Access Channel (PRACH) opportunity,
The downlink control information (DCI) containing the CRC bits scrambled by the wireless network temporary identifier (RNTI) is received on the physical downlink control channel (PDCCH), and the random access response scheduled by the DCI is received.
The value of the RNTI is calculated using the index in the frequency domain of the PRACH opportunity and the index of the uplink BWP in which the PRACH opportunity is located.
Communication method. It is a communication method for base station equipment.
Receive a random access preamble from the terminal device at the physical random access channel (PRACH) opportunity
The downlink control information (DCI) containing the CRC bits scrambled by the wireless network temporary identifier (RNTI) is transmitted on the physical downlink control channel (PDCCH), and the random access response scheduled by the DCI is transmitted.
The value of the RNTI is calculated using the index in the frequency domain of the PRACH opportunity and the index of the uplink BWP in which the PRACH opportunity is located.
Communication method.

Images