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

Abstract

Provided is a terminal device that receives UL setting information in an SIB and uses the UL setting information to set an initial UL BWP, sets, when the UL setting information includes first setting information, the initial UL BWP using information about a bandwidth indicated by the first setting information, sets, when the UL setting information does not include the first setting information and includes second setting information and a bandwidth indicated by the second setting information is not more than the maximum bandwidth supported by the terminal device, the initial UL BWP using information about the bandwidth indicated by the second setting information, and sets, when the UL setting information includes none of the first setting information and the second setting information, the initial UL BWP using information about a bandwidth indicated by third setting information included in the UL setting information.

Description

Terminal device, base station device, and communication method

The present invention relates to a terminal device, a base station device, and a communication method.
This application claims priority to Japanese Patent Application No. 2022-49390 filed in Japan on March 25, 2022, the contents of which are incorporated herein.

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

In the 5th generation cellular system, machines such as eMBB (enhanced MobileBroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-latency and highly reliable communication, and IoT (Internet of Things) Three possible service scenarios are required: mmTC (massive Machine Type Communication) where many type devices connect. Additionally, NR's future release, Release 17, is intended for applications such as sensor networks, surveillance cameras, and/or wearable devices, and will not require the high requirements of eMBB or URLLC, but will reduce costs and save battery life. A reduced capability (REDCAP) NR device with a long lifespan is being studied (Non-Patent Document 2).

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 a wireless communication system as described above.

(1) In order to achieve the above object, aspects of the present invention take the following measures. That is, a terminal device according to one aspect of the present invention includes a receiving unit that receives uplink configuration information in a system information block, and a control unit that configures an initial uplink BWP using the uplink configuration information, When the uplink configuration information includes first configuration information, the control unit configures the initial uplink BWP using bandwidth information indicated by the first configuration information, and configures the initial uplink BWP so that the uplink configuration information If the first configuration information is not included, the second configuration information is included, and the bandwidth indicated by the second configuration information is less than or equal to the maximum bandwidth supported by the terminal device, the second configuration information When the initial uplink BWP is configured using the bandwidth information indicated by the configuration information, and the uplink configuration information does not include the first configuration information and the second configuration information, the uplink configuration information The initial uplink BWP is configured using the bandwidth information indicated by the third configuration information included in the.

(2) Furthermore, the base station device in one aspect of the present invention configures a first initial uplink BWP, and includes uplink configuration information that includes first configuration information indicating a bandwidth of the first initial uplink BWP. a control unit that generates information; and a transmission unit that transmits the uplink configuration information in a system information block, the control unit configured to generate a second initial uplink BWP different from the first initial uplink BWP. If configured, the uplink configuration information includes second configuration information indicating a bandwidth of the second initial uplink BWP, which is different from the first initial uplink BWP and the second initial uplink BWP. When configuring the third initial uplink BWP, the uplink configuration information includes third configuration information indicating the bandwidth of the third initial uplink BWP.

(3) Further, a communication method according to an aspect of the present invention is a communication method for a terminal device, in which uplink setting information is received in a system information block, and an initial uplink BWP is set using the uplink setting information. If the uplink configuration information includes first configuration information, the initial uplink BWP is configured using the bandwidth information indicated by the first configuration information, and the uplink configuration information includes the first configuration information. 1 does not include configuration information, but includes second configuration information, and the bandwidth indicated by the second configuration information is less than or equal to the maximum bandwidth supported by the terminal device, the second configuration information The initial uplink BWP is configured using the bandwidth information indicated by , and if the uplink configuration information does not include the first configuration information and the second configuration information, the uplink configuration information includes the first configuration information and the second configuration information. The initial uplink BWP is configured using the bandwidth information indicated by the third configuration information.

According to this invention, a terminal device and a base station device can communicate efficiently.

1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. FIG. 3 is a diagram showing the relationship in the time domain among subframes, slots, and minislots according to an embodiment of the present invention. FIG. 3 is a diagram showing an example of an SS/PBCH block and an SS burst set according to an embodiment of the present invention. FIG. 3 is a diagram showing resources in which PSS, SSS, PBCH, and DMRS for PBCH are arranged in an SS/PBCH block according to an embodiment of the present invention. Parameter configuration of DownlinkConfigCommonSIB, which is an information element of downlink configuration information according to an embodiment of the present invention, parameter information element of BWP-DownlinkCommon, which is a parameter information element that is downlink BWP configuration information, and parameter information element that is BWP configuration information FIG. 3 is a diagram showing an example of a parameter configuration of BWP. FIG. 3 is a diagram showing an overview of frequency positions of additional synchronization signal blocks according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of PDSCH mapping types according to an embodiment of the present invention. Parameter configuration of UplinkConfigCommonSIB, which is an information element of uplink configuration information according to an embodiment of the present invention, parameter information element of parameter BWP-UplinkCommon, which is configuration information of uplink BWP, information element of parameter which is configuration information of BWP FIG. 3 is a diagram showing an example of a parameter configuration of BWP. FIG. 3 is a flow diagram showing an example of initial downlink BWP determination processing in the terminal device 1 according to the embodiment of the present invention. FIG. 3 is a flow diagram showing an example of an initial uplink BWP determination process in the terminal device 1 according to the embodiment of the present invention. 1 is a schematic block diagram showing the configuration of a terminal device 1 according to an embodiment of the present invention. 1 is a schematic block diagram showing the configuration of a base station device 3 according to an embodiment of the present invention. FIG.

Hereinafter, embodiments of the present invention will be described.

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

The terminal device 1 is also referred to as a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), or 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 device 3 includes a wireless base station device, base station, wireless base station, fixed station, NB (Node B), eNB (evolved Node B), BTS (Base Transceiver Station), BS (Base Station), NR NB ( Also referred to as NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. Base station device 3 may include a core network device. Furthermore, the base station device 3 may include one or more transmission/reception points 4 (transmission reception points). At least some of the functions/processing of the base station device 3 described below may be functions/processing at each transmission/reception point 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 by using one or more cells as a communicable range (communication area) controlled by the base station device 3. Furthermore, the base station device 3 may serve the terminal device 1 with a communication range (communication area) controlled by one or more transmission/reception points 4 as one or more cells. Furthermore, 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 a beam index used in beamforming or a precoding index.

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

In Figure 1, wireless communication between a terminal device 1 and a base station device 3 uses orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single carrier frequency division multiplexing (SC- Single-Carrier Frequency Division Multiplexing (FDM), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM), or other transmission methods may be used.

Note that in this embodiment, OFDM is used as the transmission method and will be explained using OFDM symbols, but the present invention also includes cases where the other transmission methods described above are used.

Furthermore, in FIG. 1, the above-described transmission method that does not use CP or uses zero padding instead of CP may be used in wireless communication between terminal device 1 and base station device 3. Further, CP and zero padding may be added to both the front and rear.

One aspect of this embodiment operates in carrier aggregation (CA) or dual connectivity (DC) with radio access technology (RAT) such as LTE and LTE-A/LTE-A Pro. It's okay. At this time, some or all cells or cell groups, carriers or carrier groups (for example, primary cell (PCell), secondary cell (SCell), primary secondary cell (PSCell), MCG (Master Cell Group ), SCG (Secondary Cell Group), etc.). Further, one aspect of the present embodiment may be used in a stand-alone system that operates independently. In DC operation, SpCell (Special Cell) is referred to as MCG's PCell or SCG's PSCell, depending on whether the MAC (Medium Access Control) entity is associated with MCG or SCG, respectively. If it is not a DC operation, SpCell (Special Cell) is called PCell. SpCell (Special Cell) supports PUCCH transmission and Contention Based Random Access (CBRA).

In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured serving cells may include one primary cell and one or more secondary cells. The primary cell may be the serving cell on which the initial connection establishment procedure was performed, the serving cell that initiated the connection re-establishment procedure, or the cell designated as the primary cell in the handover procedure. good. One or more secondary cells may be configured at the time or after the RRC (Radio Resource Control) connection is established. However, the plurality of configured serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information on the uplink, among one or more secondary cells in which the terminal device 1 is configured. Furthermore, two types of serving cell subsets, MCG and SCG, may be configured for the terminal device 1. MCG may consist of one PCell and zero or more SCells. The SCG may be composed of one PScell and zero or more SCells.

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

The subframe will be explained below. In this embodiment, the following is called a subframe, but the subframe according to this embodiment may also be called a resource unit, a radio frame, a time section, a time interval, etc.

FIG. 2 is a diagram showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each radio frame is 10ms long. Furthermore, each radio frame is composed of 10 subframes and W slots. Furthermore, one slot is composed of X OFDM symbols. In other words, the length of one subframe is 1ms. The time length of each slot is defined by the subcarrier spacing. For example, when the OFDM symbol subcarrier interval is 15 kHz and NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. Furthermore, 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, when X=14, when the subcarrier interval is 15kHz, W=10, and when the subcarrier interval is 60kHz, W=40. FIG. 2 shows the case where X=7 as an example. Note that the example in FIG. 2 can be similarly extended to the case where X=14. Further, uplink slots may be defined similarly, and downlink slots and uplink slots may be defined separately. Further, the bandwidth of the cell in FIG. 2 may be defined as a partial band (BWP: BandWidth Part). However, the BWP used in the downlink may be referred to as the downlink BWP, and the BWP used in the uplink may be referred to as the uplink BWP. Further, a slot may be defined as a transmission time interval (TTI). A slot may not be defined as a TTI. The TTI may be a transport block transmission period.

The signal or physical channel transmitted in each of the slots may be represented by a resource grid. A resource grid is defined by multiple subcarriers and multiple OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers constituting one slot depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is referred to as a resource element (RE). REs may be identified using subcarrier numbers and OFDM symbol numbers.

A resource grid is used to express the mapping of resource elements of a certain physical downlink channel (PDSCH, etc.) or uplink channel (PUSCH, etc.). For example, when the subcarrier spacing is 15kHz, the number of OFDM symbols included in a subframe is 14, and in the case of NCP, one physical resource block (PRB) consists of 14 consecutive OFDM symbols in the time domain. OFDM symbol and 12*Nmax consecutive subcarriers in the frequency domain. Nmax is the maximum number of resource blocks (RB) determined by subcarrier interval setting μ, which will be described later. In other words, the resource grid is composed of (14*12*Nmax,μ) REs. In the case of ECP (Extended CP), it is supported only at a subcarrier spacing of 60 kHz, so one PRB is, for example, 12 (number of OFDM symbols included in 1 slot) * 4 (slots included in 1 subframe) in the time domain. = 48 consecutive OFDM symbols and 12*Nmax,μ consecutive subcarriers in the frequency domain. In other words, the resource grid is composed of (48*12*Nmax,μ) REs.

As RBs, reference resource blocks (reference RBs), common resource blocks (CRBs), PRBs, and virtual resource blocks (VRBs) are defined. 1 RB is defined as 12 consecutive subcarriers in the frequency domain. The reference resource blocks are common to all subcarriers, constitute resource blocks at subcarrier intervals of 15 kHz, for example, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (point A) (or simply referred to as "reference point"). Point A may be provided as a common reference point for the grid of resource blocks. The position of point A may be determined/specified by the parameter offsetToPointA included in SIB1. The parameter offsetToPointA is a parameter indicating the frequency offset between point A and the lowest frequency subcarrier of the lowest frequency resource block that overlaps with the synchronization signal block used by the terminal device 1 in initial cell selection. However, the unit of the frequency offset is a resource block with a subcarrier interval of 15 kHz when the frequency range (FR) is 1, and a resource block with a subcarrier interval of 60 kHz when the frequency range is 2. However, the frequency position of point A may be indicated by ARFCN (Absolute radio-frequency channel number) using the RRC parameter absoluteFrequencyPointA. The CRBs are RBs that are numbered in ascending order starting from 0 in each subcarrier interval setting μ from point A. Therefore, the CRB number is defined for each subcarrier interval setting μ. The CRB corresponding to the subcarrier interval setting μ may be referred to as CRB μ. The resource grid mentioned above is defined by the CRB. However, the center of subcarrier index 0 of CRB μ with number 0 in each subcarrier interval setting μ is point A. PRB is an RB numbered in ascending order from 0 included in BWP of each subcarrier spacing setting μ, and PRB is numbered in ascending order from 0 included in BWP with subcarrier spacing setting μ. It is RB with . The PRB corresponding to the subcarrier interval setting μ may be referred to as PRBμ. A certain physical uplink channel is first mapped to a VRB. VRBs are then mapped to PRBs. Hereinafter, the RB may be a VRB, a PRB, a CRB, or a reference resource block.

A BWP is a subset of consecutive RBs (which may be CRBs) with a certain subcarrier spacing in a certain carrier. In the terminal device 1, up to four BWPs (downlink BWPs) may be configured in the downlink. There may be one active downlink BWP (active downlink BWP) at a certain time. The terminal device 1 may not expect to receive PDSCH, PDCCH or CSI-RS outside the active downlink BWP band. In the terminal device 1, up to four BWPs (uplink BWPs) may be configured on the uplink. There may be one active uplink BWP (active uplink BWP) at a certain time. The terminal device 1 does not transmit PUSCH and PUCCH outside the active uplink BWP band.

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

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

Next, subframes, slots, and minislots will be explained. FIG. 3 is a diagram showing an example of the relationship among subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier interval, and the number of OFDM symbols included in a slot is 7 or 14 (however, if the CP added to each symbol is Extended CP, it is 6 or 12). ), the slot length varies depending on the subcarrier spacing. Here, when the subcarrier interval is 15 kHz, one subframe includes 14 OFDM symbols. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot may be referred to as PUSCH mapping type A.

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

In the terminal device 1, the transmission direction (uplink, downlink, or flexible) of symbols in each slot is set in an upper layer using an RRC message containing predetermined upper layer parameters received from the base station device 3; It is set by a PDCCH of a specific DCI format (for example, DCI format 2_0) received from the base station device 3. In this embodiment, a format in which each symbol in each slot is set to be uplink, downlink, or flexible is called a slot format. One slot format may include downlink symbols, uplink symbols, and flexible symbols.

The carrier corresponding to the serving cell of this embodiment is called a component carrier (CC) (or carrier). In the downlink of this embodiment, the carrier corresponding to the serving cell is called a downlink CC (or downlink carrier). In the uplink of this embodiment, the carrier corresponding to the serving cell is called an uplink CC (or uplink carrier). In the sidelink of this embodiment, the carrier corresponding to the serving cell is called a sidelink CC (or sidelink carrier).

The physical channel and physical signal of this embodiment will be explained.

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)
・PDCCH (Physical Downlink Control CHannel)
・PDSCH (Physical Downlink Shared CHannel)
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PBCH is used by the terminal device 1 to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) that include important system information. The MIB contains information for identifying the radio frame number (SFN: System Frame Number) to which the PBCH is mapped, and system information block type 1 (SIB1: System Information Block 1). 1) Information specifying the subcarrier spacing, information indicating the frequency domain offset between the grid of resource blocks and the SS/PBCH block (also referred to as synchronization signal block, SS block, SSB), PDCCH for SIB1 It may include information indicating settings related to. However, SIB1 includes information necessary for evaluating whether terminal device 1 is allowed to connect to a cell, and includes information for determining scheduling of other system information (SIB: System Information Block). However, the information indicating settings related to PDCCH for SIB1 includes control resource set (CORESET: ControlResourceSet) #0 (CORESET#0 is also referred to as CORESET0, common CORESET), common search space, and/or necessary PDCCH parameters. It may be information that determines the However, CORESET indicates a PDCCH resource element and is composed of a set of PRBs in a time period of a certain number of OFDM symbols (for example, 1 to 3 symbols). CORESET#0 may be a CORESET for a PDCCH that schedules at least SIB1. CORESET#0 may be set by MIB or via RRC signaling. SIB1 may be scheduled by PDCCH transmitted in CORESET#0. Terminal device 1 receives SIB1 scheduled on PDCCH received in CORESET #0. However, the PDCCH that schedules SIB1 may be Downlink Control Information (DCI) with a scrambled CRC in the SI-RNTI (Scheduling information - Radio Network Temporary Identifier) transmitted on the PDCCH. . DCI and SI-RNTI will be described later. The terminal device 1 may receive a DCI with a CRC scrambled with SI-RNTI on a PDCCH, and may receive a PDSCH including SIB1 scheduled on the DCI. However, the PDCCH on which SIB1 is scheduled may be a PDCCH with a CRC scrambled with the SI-RNTI transmitted on the PDCCH.

The PBCH also includes information for identifying the number (SFN: System Frame Number) and/or Half Radio Frame (HRF) to which the PBCH is mapped. (also referred to as a frame) may be used to broadcast information specifying the frame. However, a half radio frame is a time frame with a length of 5 ms, and the information specifying the half radio frame may be information specifying whether it is the first half 5 ms or the second half 5 ms of a 10 ms radio frame.

Additionally, the PBCH may be used to broadcast the time index within the period of the SS/PBCH block. Here, the time index is information indicating the index of the synchronization signal and PBCH within the cell. The time index may be referred to as an SSB index or an SS/PBCH block index. For example, when transmitting SS/PBCH blocks using quasi co-location (QCL) assumptions regarding multiple transmit beams, transmit filter settings and/or receive spatial parameters, within a predetermined period or set may indicate the chronological order within the specified period. Furthermore, the terminal device may recognize the difference in time index as a difference in QCL assumptions regarding transmission beams, transmission filter settings, and/or reception spatial parameters.

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

For example, the following DCI format may be defined:
・DCI format 0_0
・DCI format 0_1
・DCI format 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 PUSCH scheduling in a certain 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 either (TC-RNTI) may be added. DCI format 0_0 may be monitored in the common search space or the UE-specific search space.

DCI format 0_1 may be used for PUSCH scheduling in a certain serving cell. DCI format 0_1 includes 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) ) request and/or information regarding the antenna port. DCI format 0_1 may have a CRC scrambled by any of RNTI, 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 PUSCH scheduling in a certain 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 antenna ports. DCI format 0_2 may have a CRC scrambled by any one of C-RNTI, CSI-RNTI, SP-CSI-RNTI, and/or MCS-C-RNTI among RNTIs. DCI format 0_2 may be monitored in the UE specific search space. DCI format 0_2 may also be referred to as DCI format 0_1A, etc.

DCI format 1_0 may be used for PDSCH scheduling in a certain 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 includes the following identifiers: C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random access (RA)-RNTI, and/or , TC-RNTI may be added. DCI format 1_0 may be monitored in the common search space or the UE-specific search space.

DCI format 1_1 may be used for PDSCH scheduling in a certain serving cell. DCI format 1_1 includes 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. That's fine. DCI format 1_1 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, and/or MCS-C-RNTI among RNTIs. DCI format 1_1 may be monitored in the UE specific search space.

DCI format 1_2 may be used for PDSCH scheduling in a certain 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 have a CRC scrambled by any one of C-RNTI, CS-RNTI, and/or MCS-C-RNTI among RNTIs. DCI format 1_2 may be monitored in the UE specific search space. DCI format 1_2 may also be referred to as DCI format 1_1A, etc.

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

DCI format 2_1 is used to notify the terminal device 1 of PRBs (or RBs) and OFDM symbols that can be assumed not to be transmitted. Note that this information may be referred to as a preemption instruction (intermittent transmission instruction).

DCI format 2_2 is used for transmitting 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. Additionally, an SRS request may be sent along with the TPC command. Furthermore, an SRS request and a TPC command may be defined in DCI format 2_3 for uplinks without PUSCH and PUCCH, or for uplinks in which SRS transmission power control is not linked to PUSCH transmission power control.

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

The CRC parity bits added to the DCI format transmitted on one PDCCH are scrambled with SI-RNTI, P-RNTI, C-RNTI, CS-RNTI, RA-RNTI, or TC-RNTI. SI-RNTI may be an identifier used for broadcasting 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 terminal devices within a cell. TC-RNTI is an identifier for identifying the terminal device 1 that transmitted the random access preamble during CBRA.

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 location information of the physical random access channel that transmitted the random access preamble.

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

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

The PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the Medium Access Control (MAC) layer. Additionally, in the case of downlink, the PDSCH is also used to transmit system information (SI), paging information, random access response (RAR), and the like.

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. Furthermore, PUSCH may be used to transmit only CSI or only HARQ-ACK and CSI. That is, PUSCH may be used to transmit only UCI.

Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in a higher layer. For example, the base station device 3 and the terminal device 1 may transmit and receive RRC messages (also referred to as RRC messages, RRC information, and RRC signaling) in a radio resource control (RRC) layer. Furthermore, the base station device 3 and the terminal device 1 may transmit and receive MAC control elements in the MAC (Medium Access Control) layer. Further, the RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3. Here, the RRC message, system information, and/or MAC control element is also referred to as a higher layer signal (higher layer signal) or a higher layer parameter (higher layer parameter). 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. The upper layer here means an upper layer seen from the physical layer, and may therefore include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, and the like. Hereinafter, "A is given (provided) by the upper layer" and "A is given (provided) by the upper layer" mean the upper layers of the terminal device 1 (mainly the RRC layer and MAC layer, etc.) receives A from the base station device 3, and the received A is given (provided) from an upper layer of the terminal device 1 to the physical layer of the terminal device 1. For example, in the terminal device 1, “being provided with upper layer parameters” means that the terminal device 1 receives an upper layer signal from the base station device 3, and the upper layer parameters included in the received upper layer signal are transmitted from the upper layer of the terminal device 1 to the terminal device. It may also mean that it is provided to the physical layer of the device 1. Setting upper layer parameters to the terminal device 1 may mean that the upper layer parameters are given (provided) to the terminal device 1. For example, setting upper layer parameters in the terminal device 1 may mean that the terminal device 1 receives an upper layer signal from the base station device 3 and sets the received upper layer parameters in the upper layer. . However, setting upper layer parameters to the terminal device 1 may include setting default parameters 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 using PDSCH may be common signaling to multiple terminal devices 1 within a cell. Further, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, the terminal device-specific (UE-specific) information may be transmitted to a certain terminal device 1 using dedicated signaling. Furthermore, PUSCH may be used to transmit UE Capability in the uplink.

In FIG. 1, the following downlink physical signals are used in downlink wireless communication. Here, the downlink physical signal is not used to transmit 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). Cell ID may be detected using PSS and SSS.

The synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and time domain. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that a beam may also 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 perform propagation path compensation for 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 spacing, and window synchronization of FFT.

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

DMRS is used to demodulate the modulated signal. Note that two types of DMRS may be defined: a reference signal for demodulating PBCH and a reference signal for demodulating PDSCH, and both may be referred to as DMRS. CSI-RS is used for channel state information (CSI) measurement and beam management, and periodic, semi-persistent or aperiodic CSI reference signal transmission methods are applied. CSI-RS may be defined as Non-Zero Power (NZP) CSI-RS and Zero Power (ZP) CSI-RS with zero transmission power (or reception power). , ZP CSI-RS may be defined as a CSI-RS resource with zero transmit power or no transmission. PTRS is used to track phase in time with the purpose of guaranteeing frequency offsets due to phase noise. TRS is used to guarantee Doppler shift during high-speed movement. Note that TRS may be used as one setting for CSI-RS. For example, 1-port CSI-RS can be used as a wireless 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 the modulated signal. Note that two types of DMRS may be defined: a reference signal for demodulating PUCCH and a reference signal for demodulating PUSCH, and 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 phase in time to account for frequency offsets due to phase noise.

In this embodiment, the downlink physical channels and/or downlink physical signals are collectively referred to as downlink signals. In this embodiment, uplink physical channels and/or uplink physical signals are collectively referred to as uplink signals. In this embodiment, downlink physical channels and/or uplink physical channels are collectively referred to as physical channels. In this embodiment, downlink physical signals and/or uplink physical signals are collectively 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 units of transport channels used in the MAC layer are also referred to as transport blocks (TB) and/or MAC PDUs (Protocol Data Units). HARQ (Hybrid Automatic Repeat reQuest) control is performed 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. At the physical layer, transport blocks are mapped to codewords, and encoding processing is performed for each codeword.

FIG. 4 shows an SS/PBCH block (also referred to as a synchronization signal block, SS block, or SSB) according to this embodiment and a half frame with SS/PBCH block in which one or more SS/PBCH blocks are transmitted. FIG. 3 is a diagram illustrating an example of a block or SS burst set. Figure 4 shows an example in which two SS/PBCH blocks are included in an SS burst set that exists at a constant period (also called an SSB period), and each SS/PBCH block is composed of four consecutive OFDM symbols. It shows.

The SS/PBCH block may be a block containing synchronization signals (PSS, SSS), PBCH, and DMRS for PBCH. However, the SS/PBCH block may be a block including synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for REDCAP PBCH. Transmitting the signals/channels included in the SS/PBCH block is expressed as transmitting the SS/PBCH block. When transmitting a synchronization signal and/or PBCH using one or more SS/PBCH blocks in the SS burst set, the base station device 3 may use an independent downlink transmission beam for each SS/PBCH block. good.

In FIG. 4, PSS, SSS, PBCH, and DMRS for PBCH are time/frequency multiplexed in one SS/PBCH block. FIG. 5 is a table showing resources in which PSS, SSS, PBCH, and DMRS for PBCH are arranged in an SS/PBCH block.

The PSS may be mapped to the first symbol in the SS/PBCH block (the OFDM symbol whose OFDM symbol number is 0 relative to the starting symbol of the SS/PBCH block). The PSS sequence consists of 127 symbols, and the 57th to 183rd subcarriers in the SS/PBCH block (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS/PBCH block) ) may be mapped to

SSS may be mapped to the third symbol in the SS/PBCH block (the OFDM symbol whose OFDM symbol number is 2 relative to the starting symbol of the SS/PBCH block). The SSS sequence consists of 127 symbols, and the 57th to 183rd subcarriers in the SS/PBCH block (subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS/PBCH block) ) may be mapped to

PBCH and DMRS are OFDM symbols whose OFDM symbol numbers are 1, 2, and 3 in the second, third, and fourth symbols in the SS/PBCH block (relative to the starting symbol of the SS/PBCH block). symbol). The sequence of modulation symbols for PBCH consists of M _symb symbols, from the 1st subcarrier to the 240th subcarrier (start of SS/PBCH block) of the 2nd and 4th symbols in the SS/PBCH block. subcarriers with subcarrier numbers from 0 to 239), and the 1st to 48th subcarriers and 184th to 240th subcarriers of the third symbol in the SS/PBCH block. (Subcarriers whose subcarrier numbers are 0 to 47 and 192 to 239 with respect to the starting subcarrier of the SS/PBCH block) may be mapped to resources to which DMRS is not mapped. The DMRS symbol sequence consists of 144 symbols, from the 1st subcarrier to the 240th subcarrier (the starting subcarrier of the SS/PBCH block) of the second and fourth symbols in the SS/PBCH block. subcarriers with subcarrier numbers 0 to 239), the 1st to 48th subcarriers and the 184th to 240th subcarriers of the third symbol in the SS/PBCH block (SS /PBCH block starting subcarrier, subcarriers with subcarrier numbers 0 to 47 and 192 to 239), and one subcarrier for every four subcarriers may be mapped. For example, for 240 subcarriers, modulation symbols of the PBCH may be mapped to 180 subcarriers, and DMRS for the PBCH may be mapped to 60 subcarriers.

Different SS/PBCH blocks within the SS burst set may be assigned different SSB indices. The SS/PBCH block to which a certain SSB index is assigned may be periodically transmitted by the base station device 3 based on the SSB cycle. For example, an SSB cycle for the SS/PBCH block to be used for initial access and an SSB cycle to be set for the connected (Connected or RRC_Connected) terminal device 1 may be defined. Furthermore, the SSB cycle set for the connected (Connected or RRC_Connected) terminal device 1 may be set using the RRC parameter. In addition, 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 in reality, the SSB cycle is set for the connected (Connected or RRC_Connected) terminal device 1. You can decide whether to send it or not. Furthermore, the SSB cycle for using the SS/PBCH block for initial access may be defined in advance in specifications or the like. For example, the terminal device 1 that performs initial access may consider the SSB cycle to be 20 milliseconds.

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

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

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

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

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

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

Within a period of a given SS burst set, SS/PBCH blocks that are assigned the same SSB index may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation.

The initial BWP (initial BWP), initial downlink BWP (initial DL BWP), and initial uplink BWP (initial UL BWP) according to this embodiment are the BWP used at the time of initial access before the RRC connection is established, respectively. It may be a downlink BWP and an uplink BWP. However, the initial BWP, initial downlink BWP and initial uplink BWP may be used after the RRC connection is established. However, the initial BWP, initial downlink BWP, and initial uplink BWP are BWP with index 0 (#0), downlink BWP with index 0 (#0), and initial uplink BWP with index 0 (#0), respectively. It may be some uplink BWP.

The initial downlink BWP may be set by parameters provided in MIB, parameters provided in SIB1, parameters provided in SIB, and/or RRC parameters. For example, the initial downlink BWP may be set by the parameter initialDownlinkBWP included in the parameter downlinkConfigCommon provided in SIB1. For example, the initial downlink BWP may be configured by the parameter initialDownlinkBWP-forRedCap-r17 included in the parameter downlinkConfigCommon provided in SIB1. For example, the initial downlink BWP may be configured by the parameter initialDownlinkBWP-forRedCap-r18 included in the parameter downlinkConfigCommon provided in SIB1. The parameter downlinkConfigCommon provided in SIB1 includes initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18, and any one of these parameters included in the downlinkConfigCommon is used to configure the initial downlink BWP. May be set. However, initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and initialDownlinkBWP-forRedCap-r18 may be parameters indicating the settings of the initial downlink BWP for each UE (UE-specific, dedicated).

FIG. 6 shows the parameter configuration of DownlinkConfigCommonSIB (or DownlinkConfigCommon), which is an information element (IE: Information Element) of parameter downlinkConfigCommon, which is downlink configuration information according to this embodiment, and the parameter information element BWP, which is configuration information of downlink BWP. - Parameter configuration of DownlinkCommon, parameter information element that is BWP setting information An example of the parameter configuration of BWP is shown.

downlinkConfigCommon is a parameter that indicates basic parameters related to one downlink carrier and transmission in the corresponding cell (for example, called frequencyInfoDL), a parameter that indicates the first setting of the initial downlink BWP of a certain serving cell (for example, called initialDownlinkBWP). ), a parameter indicating the second configuration of the initial downlink BWP of a certain serving cell (for example, referred to as initialDownlinkBWP-forRedCap-r17), and a parameter indicating the third configuration of the initial downlink BWP of a certain serving cell ( For example, initialDownlinkBWP-forRedCap-r18) may be included. However, initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18 included in downlinkConfigCommon may have a parameter configuration indicated by the same information element (BWP-DownlinkCommon) as initialDownlinkBWP included in downlinkConfigCommon. However, initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18 may be included in SIB and/or RRC parameters other than SIB1. However, initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18 may be parameters that include part or all of the parameter configuration of initialDownlinkBWP included in downlinkConfigCommon, and each is the configuration information for the second initial downlink BWP. and configuration information for the third initial downlink BWP. However, when downlinkConfigCommon is transmitted by SIB, it may necessarily include initialDownlinkBWP, and may not include initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18. initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and initialDownlinkBWP-forRedCap-r18 according to the present embodiment include general parameters genericParameters of initial downlink BWP, cell-specific parameters pdcch-ConfigCommon of PDCCH, and cell-specific parameters of PDSCH. pdsch-ConfigCommon and/or other parameters.

initialDownlinkBWP is a parameter that sets the initial downlink BWP which is the first bandwidth (e.g. up to 100MHz), and initialDownlinkBWP-forRedCap-r17 is the second bandwidth (e.g. up to 20MHz) which is narrower than the first bandwidth. It may be a parameter for setting the initial downlink BWP. initialDownlinkBWP-forRedCap-r17 may be a parameter that terminal device 1 that supports a bandwidth larger than the third bandwidth (for example, 20MHz) does not refer to, and only terminal device 1 that supports only the third bandwidth or less It may be a parameter to be referenced. initialDownlinkBWP-forRedCap-r18 may be a parameter for setting an initial downlink BWP that is a fourth bandwidth (for example, a maximum of 5 MHz) that is narrower than the second bandwidth. initialDownlinkBWP-forRedCap-r18 may be a parameter that terminal device 1 that supports a bandwidth larger than the fifth bandwidth (for example, 5MHz) does not refer to, and only terminal device 1 that supports only the fifth bandwidth or less It may be a parameter to be referenced. In this way, by setting one or more parameters that set different bandwidths as the initial downlink BWP in downlinkConfigCommon, the initial downlink BWP can be set according to the maximum bandwidth supported by each of the multiple terminal devices 1. Can be set. For example, the bandwidth of the initial downlink BWP set by initialDownlinkBWP is 50MHz, the bandwidth of the initial downlink BWP set by initialDownlinkBWP-forRedCap-r17 is 10MHz, and the initial downlink BWP set by initialDownlinkBWP-forRedCap-r18. If the bandwidth of is 5MHz and downlinkConfigCommon contains these three parameters, terminal device 1 that supports a bandwidth of up to 100MHz will configure an initial downlink BWP with a bandwidth of 50MHz based on initialDownlinkBWP and up to 20MHz Terminal device 1 that supports a bandwidth of up to 5MHz sets an initial downlink BWP with a bandwidth of 10MHz based on initialDownlinkBWP-forRedCap-r17, and terminal device 1 that supports a bandwidth of up to 5MHz sets an initial Downlink BWP based on initialDownlinkBWP-forRedCap-r18. The initial downlink BWP with a bandwidth of 5MHz may be set using

If initialDownlinkBWP-forRedCap-r18 is included in downlinkConfigCommon, the terminal device 1 may identify/set/determine the initial downlink BWP based on the parameters included in the initialDownlinkBWP-forRedCap-r18. For example, when the terminal device 1 receives the initialDownlinkBWP-forRedCap-r18 in SIB1, it may identify/set/determine the initial downlink BWP based on the parameters of the initialDownlinkBWP-forRedCap-r18.

If there are multiple initial downlink BWP configuration parameters (or multiple frequency positions and/or multiple If the bandwidth configuration information is broadcast), part of the information included in the genericParameters in the initialDownlinkBWP is the configuration parameters of the plurality of initial downlink BWPs (or the plurality of frequency positions and/or of the initial downlink BWPs). or setting information of multiple bandwidths).

The information element BWP of the parameter genericParameters may be a parameter indicating the frequency position and bandwidth of the corresponding BWP. The information element BWP includes a parameter subcarrierSpacing that indicates the subcarrier spacing used in the corresponding BWP, a parameter locationAndBandwidth that indicates the position and bandwidth (number of resource blocks (total number)) in the frequency domain of the corresponding BWP, and/or the corresponding BWP. may include a parameter cyclicPrefix indicating whether a standard CP (cyclic prefix) or an extended CP is used. That is, the corresponding BWP may be defined by the 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 consecutive PRBs from the starting PRB index of the corresponding BWP. However, the first PRB that defines the region of the resource indicator value is based on the subcarrier spacing given by subcarrierSpacing of the corresponding BWP and the FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier spacing. ) may be the PRB determined by offsetToCarrier set in SCS-SpecificCarrier. Further, the size defining the region of the resource indicator value may be 275. The subcarrier spacing of the initial downlink BWP indicated by subcarrierSpacing included in genericParameters may be set to have the same value as the subcarrier spacing indicated by the MIB of the same cell. If cyclicPrefix is not included in the genericParameters (not set), the terminal device 1 may use the standard CP instead of the extended CP.

The frequencyInfoDL may include a frequencyBandList that indicates a list of one or more frequency bands to which the relevant downlink carrier belongs, and a list of SCS-SpecificCarrier that indicates a set of carrier-related parameters for each subcarrier interval. frequencyInfoUL may include a frequencyBandList that indicates a list of one or more frequency bands to which the uplink carrier belongs, and a list of SCS-SpecificCarrier that indicates a set of parameters regarding carriers for each subcarrier interval.

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

Terminal device 1 sets the initial downlink BWP bandwidth set by initialDownlinkBWP and initialDownlinkBWP-forRedCap-r17 provided in downlinkConfigCommon included in SIB1 (which may be other SIB or RRC parameters) received by terminal device 1. If not supported, terminal device 1 performs initial downlink BWP in a continuous manner starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs (Physical Resource Blocks) of CORESET (CORESET #0, etc.) of Type 0-PDCCH CSS Set. It may be determined/specified by the position and number of PRBs to be used, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received in CORESET of Type0-PDCCH CSS Set.

If initialDownlinkBWP-forRedCap-r18 is provided in the downlinkConfigCommon included in the SIB1 received by the terminal device 1, the terminal device 1 may determine/specify the initial downlink BWP using the initialDownlinkBWP-forRedCap-r18.

initialDownlinkBWP-forRedCap-r18 is not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, initialDownlinkBWP-forRedCap-r17 is provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and the corresponding If the terminal device 1 supports the BWP bandwidth set in the initialDownlinkBWP-forRedCap-r17, the terminal device 1 may determine/specify the initial downlink BWP using the initialDownlinkBWP-forRedCap-r17.

If initialDownlinkBWP-forRedCap-r18 is not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and initialDownlinkBWP-forRedCap-r17 is provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, The terminal device 1 may determine/specify the initial downlink BWP using the initialDownlinkBWP-forRedCap-r17.

initialDownlinkBWP-forRedCap-r18 is not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, initialDownlinkBWP-forRedCap-r17 is provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and the corresponding If the terminal device 1 does not support the BWP bandwidth set in initialDownlinkBWP-forRedCap-r17, the terminal device 1 may consider the cell to be a barred cell.

If initialDownlinkBWP-forRedCap-r18 and initialDownlinkBWP-forRedCap-r17 are not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, terminal device 1 sets initial downlink BWP to initialDownlinkBWP provided in downlinkConfigCommon in SIB1. It may be determined/specified by .

If initialDownlinkBWP-forRedCap-r18 and initialDownlinkBWP-forRedCap-r17 are not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and terminal device 1 supports the BWP bandwidth set in initialDownlinkBWP. , the terminal device 1 may determine/specify the initial downlink BWP using the initialDownlinkBWP.

If initialDownlinkBWP-forRedCap-r18 is not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, terminal device 1 may determine/specify the initial downlink BWP with initialDownlinkBWP instead of initialDownlinkBWP-forRedCap-r17. do not have. However, due to the relationship between the bandwidths set in each of initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and initialDownlinkBWP-forRedCap-r18, if initialDownlinkBWP-forRedCap-r18 is not used, the bandwidth will be closer to initialDownlinkBWP-forRedCap-r18. By using initialDownlinkBWP-forRedCap-r17, which is expected to be set, it may be possible to obtain the advantage of providing flexibility in the bandwidth set for terminal device 1. However, if it is assumed that the base station device 3 sets the initial downlink BWP with a bandwidth that can be set by all the terminal devices 1 in the cell, which of initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18 By not setting either, all terminal devices 1 may set/specify the initial downlink BWP band in initialDownlinkBWP. By preparing three parameters as the initial downlink BWP bandwidth in this way, when three or more types of terminal devices 1 with different supported bandwidths coexist in a cell, the initial It is possible to provide flexibility in the bandwidth of downlink BWP. Note that although this embodiment shows a case where three parameters are used to set three initial downlink BWPs with different bandwidths, it is also possible to use four or more parameters.

If initialDownlinkBWP-forRedCap-r18 and initialDownlinkBWP-forRedCap-r17 are not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and terminal device 1 does not support the BWP bandwidth set in initialDownlinkBWP. , the terminal device 1 may regard the cell as a barred cell.

initialDownlinkBWP-forRedCap-r18 is not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, initialDownlinkBWP-forRedCap-r17 is provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and the corresponding If terminal device 1 does not support the BWP bandwidth set in initialDownlinkBWP-forRedCap-r17, terminal device 1 uses the initial downlink BWP as PRB (Physical Determined by the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the Resource Blocks, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received in the CORESET of the Type0-PDCCH CSS Set. May be specified.

initialDownlinkBWP-forRedCap-r18 and initialDownlinkBWP-forRedCap-r17 are not provided/set in downlinkConfigCommon in SIB1 received by terminal device 1, and initialDownlinkBWP provided in downlinkConfigCommon in SIB1 received by terminal device 1 is not set. If terminal device 1 does not support the BWP bandwidth that is used for It may be determined/specified by the position and number of consecutive PRBs starting from the PRB and ending with the PRB with the highest index, and the SCS and cyclic prefix of the PDCCH received in the CORESET of the Type0-PDCCH CSS Set.

However, if initialDownlinkBWP (initialDownlinkBWP-forRedCap-r17 or initialDownlinkBWP-forRedCap-r18) is provided in downlinkConfigCommon, receiving initialDownlinkBWP (initialDownlinkBWP-forRedCap-r17/initialDownlinkBWP-forRedCap-r18) in RRC parameter However, the RRC connection may be established (for example, RRCSetup, RRCResume, and/or RRCReestablishment is being received). For example, when terminal device 1 receives initialDownlinkBWP (which may be initialDownlinkBWP-forRedCap-r17 or initialDownlinkBWP-forRedCap-r18) in downlinkConfigCommon in SIB1, CORESET#0 is used until it receives RRCSetup, RRCResume, or RRCReestablishment. may be used as the initial downlink BWP. However, to set CORESET#0 as the initial downlink BWP, the initial downlink BWP is determined/specified by the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs in CORESET#0. It's fine. However, determining/identifying the initial downlink BWP may also mean determining/identifying the frequency position and/or bandwidth of the initial downlink BWP. When terminal device 1 receives initialDownlinkBWP (which may be initialDownlinkBWP-forRedCap-r17 or initialDownlinkBWP-forRedCap-r18) in downlinkConfigCommon in SIB1, after receiving RRCSetup, RRCResume, and/or RRCReestablishment, terminal device 1 uses the received initialDownlinkBWP The initial downlink BWP may be determined/specified using locationAndBandwidth included in (initialDownlinkBWP-forRedCap-r17 or initialDownlinkBWP-forRedCap-r18). When terminal device 1 receives initialDownlinkBWP (which may be initialDownlinkBWP-forRedCap-r17 or initialDownlinkBWP-forRedCap-r18) in SIB1, it specifies the initial downlink BWP in CORESET#0 until the RRC connection is established. , after the RRC connection is established, the initial downlink BWP may be determined/specified using locationAndBandwidth included in initialDownlinkBWP (initialDownlinkBWP-forRedCap-r17/initialDownlinkBWP-forRedCap-r18).

RRCSetup may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCSetupRequest message to the base station device 3 (which may be a network). The base station device 3 (which may be a network) may transmit an RRCSetup message to the terminal device 1 when an RRC connection is established with the terminal device 1.

RRCResume is a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCResumeRequest message or an RRCResumeRequest1 message to the base station device 3 (which may be a network). It's fine. When base station device 3 (which may be a network) resumes the RRC connection with terminal device 1, base station device 3 (which may be a network) may transmit an RRCResume message to terminal device 1.

RRCReestablishment may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCReestablishmentRequest message to the base station device 3 (which may be a network). When the base station device 3 (which may be a network) reestablishes the RRC connection with the terminal device 1, it may transmit an RRCReestablishment message to the terminal device 1.

The terminal device 1 according to the present invention receives/specifies initial downlink BWP configuration information using upper layer parameters initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon. However, initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18 may be included in SIB1 or in any RRC message. For example, the initial downlink BWP configuration information may include information indicating the frequency position and bandwidth of the initial downlink BWP. The terminal device 1 may receive SIB1 or arbitrary RRC signaling including multiple pieces of initial downlink BWP configuration information.

pdcch-ConfigCommon, which can be included in initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17 and/or initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon, is the CORESET#0 used in the common search space or UE-specific search space in the corresponding initial downlink BWP. Parameter controlResourceSetZero, parameter commonControlResourceSet of additional common CORESET used in common search space or UE-specific search space, parameter searchSpaceZero of common search space 0 (common search space #0), indicates a list of common search spaces other than common search space 0 Parameter commonSearchSpaceList, parameter searchSpaceSIB1 indicating the ID of the search space for SIB1 messages, parameter searchSpaceOtherSystemInformation indicating the ID of the search space for other system information, parameter pagingSearchSpace indicating the ID of the search space for paging, and/or It may contain the parameter ra-SearchSpace indicating the ID of the search space for the random access procedure.

Information element (IE: Information Element) indicated by controlResourceSetZero Any value from 0 to 15 is set for ControlResourceSetZero. However, the number of values that can be set for ControlResourceSetZero may be other than 16, and may be 32, for example. Any value from 0 to 15 is set to the information element SearchSpaceZero indicated by searchSpaceZero. However, the number of values that can be set for SearchSpaceZero may be other than 16, and may be 32, for example.

The terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET #0 from controlResourceSetZero in pdcch-ConfigCommon. However, the value indicated by controlResourceSetZero is applied to a predetermined table as an index. However, the terminal device 1 may decide which table to apply based on the supported UE category and/or UE Capability. However, the terminal device 1 may decide which table to apply based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier spacing of the SS/PBCH block and/or the subcarrier spacing of CORESET #0. Each row of the table to which the value of controlResourceSetZero is applied as an index includes the index indicated by controlResourceSetZero, the multiplex pattern of PBCH and CORESET, the number of RBs (which may be PRBs) of CORESET#0, the number of symbols of CORESET#0, and the offset. and/or the number of times the PDCCH is repeated may be indicated.

commonSearchSpaceList is a parameter that indicates a list of additional common search spaces (CSS), and sets common search spaces with search space IDs other than 0. The parameter SearchSpace included in commonSearchSpaceList includes at least a parameter searchSpaceId indicating a search space ID used to identify a search space, and a parameter controlResourceSetId indicating a CORESET ID used to identify one CORESET in the serving cell. may be included.

searchSpaceSIB1 includes an information element SearchSpaceId indicating the ID of the search space for the SIB1 message. The terminal device 1 identifies the CSS used to monitor the PDCCH that schedules the PDSCH including the SIB1 message from the search space ID indicated by searchSpaceSIB1 and the common search space list indicated by commonSearchSpaceList, and The CORESET used to monitor the PDCCH on which messages are scheduled and the settings (eg, frequency location) of the CORESET may be specified.

searchSpaceOtherSystemInformation includes an information element SearchSpaceId that indicates the ID of the search space for other system information (OSI). Terminal device 1 specifies the CSS to be used for monitoring the PDCCH that schedules the PDSCH including the OSI from the search space ID indicated by searchSpaceOtherSystemInformation and the list of common search spaces indicated by commonSearchSpaceList, and further specifies the CSS to be used for monitoring the PDCCH that schedules the PDSCH including the OSI. The CORESET used to monitor the PDCCH that schedules the included PDSCH and the settings (eg, frequency location) of the CORESET may be specified.

pagingSearchSpace includes an information element SearchSpaceId that indicates the ID of the search space for paging. The terminal device 1 specifies the CSS to be used for monitoring the PDCCH that schedules the PDSCH including paging information from the search space ID indicated by pagingSearchSpace and the list of common search spaces indicated by commonSearchSpaceList, and further specifies the CSS used for monitoring the PDCCH that schedules the PDSCH that includes paging information, The CORESET used to monitor the PDCCH that schedules the PDSCH containing information and the settings (eg, frequency location) of the CORESET may be specified.

ra-SearchSpace contains an information element SearchSpaceId indicating the ID of the search space for the random access procedure. Terminal device 1 schedules a PDSCH that includes a random access response (RAR) based on the search space ID indicated by ra-SearchSpace and the common search space list indicated by commonSearchSpaceList. In addition, the CORESET used for monitoring the PDCCH that schedules the PDSCH including RAR and the settings (for example, frequency position) of the CORESET may be specified.

The multiplex pattern of PBCH and CORESET indicates the pattern of the frequency/time position relationship between the SS/PBCH block corresponding to the PBCH where the MIB was detected and the corresponding CORESET #0. For example, if the multiplexing pattern for PBCH and CORESET is 1, PBCH and CORESET #0 are time-multiplexed on different symbols.

The number of RBs for CORESET #0 indicates the number of resource blocks that are consecutively allocated to CORESET #0. The number of symbols of CORESET #0 indicates the number of symbols consecutively allocated to CORESET #0.

The terminal device 1 receives initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18 including the RRC parameter pdcch-ConfigCommon in SIB1, other SIB, or RRC signaling, and monitors the PDCCH based on the parameter. .

The terminal device 1 determines the PDCCH monitoring opportunity from searchSpaceZero in pdcch-ConfigCommon. However, the value indicated by searchSpaceZero is applied to a predetermined table as an index. However, the terminal device 1 may decide which table to apply based on the supported UE category and/or UE Capability. However, the terminal device 1 may decide which table to apply based on the frequency range.

Terminal device 1 monitors PDCCH using Type 0-PDCCH common search space set (Type 0-PDCCH CSS Set) over two consecutive slots starting from slot n0. The terminal device 1 determines n0 and the system frame number in the SS/PBCH block whose index is i based on the parameter O and the parameter M shown in the table.

Parameters indicating multiple "frequency positions and bandwidths" for multiple initial downlink BWPs in a certain cell (locationAndBandwidth in initialDownlinkBWP in downlinkConfigCommon, locationAndBandwidth in initialDownlinkBWP-forRedCap-r17 in downlinkConfigCommon, and initialDownlinkBWP-forRedCap in downlinkConfigCommon) - locationAndBandwidth in r18) is set (this may be the case when multiple initial downlink BWPs are set in a certain cell), pdcch-ConfigCommon that can be included in initialDownlinkBWP in downlinkConfigCommon or the pdcch-ConfigCommon Each parameter may be a cell-specific parameter of the PDCCH in the initial downlink BWP configured in the initialDownlinkBWP in downlinkConfigCommon, or the initial downlink BWP configured in the initialDownlinkBWP in downlinkConfigCommon, in the downlinkConfigCommon. This is a cell-specific parameter of the PDCCH that is common to the initial downlink BWP configured in initialDownlinkBWP-forRedCap-r17 of It's okay.

pdsch-ConfigCommon (which may be referred to as PDSCH-ConfigCommon) which may be included in initialDownlinkBWP in downlinkConfigCommon, pdsch-ConfigCommon which may be included in initialDownlinkBWP-forRedCap-r17 in downlinkConfigCommon and initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon The pdsch-ConfigCommon that may be configured may include a parameter pdsch-TimeDomainAllocationList that indicates a list of time domain settings for the timing of downlink allocation for downlink data.

Parameters indicating multiple "frequency positions and bandwidths" for the initial downlink BWP in a certain cell (locationAndBandwidth in initialDownlinkBWP in downlinkConfigCommon, locationAndBandwidth in initialDownlinkBWP-forRedCap-r17 in downlinkConfigCommon, and initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon) locationAndBandwidth) is set (this may be the case when multiple initial downlink BWPs are set in a certain cell), pdsch-ConfigCommon that can be included in initialDownlinkBWP in downlinkConfigCommon or each parameter of the pdsch-ConfigCommon may be a cell-specific parameter of the PDSCH in the initial downlink BWP configured with initialDownlinkBWP in downlinkConfigCommon, or the initial downlink BWP configured with initialDownlinkBWP in downlinkConfigCommon, initialDownlinkBWP in downlinkConfigCommon. -Even if it is a cell-specific parameter of PDSCH that is common to the initial downlink BWP configured with forRedCap-r17 and the initial downlink BWP configured with initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon. good.

Terminal device 1 that does not support the frequency location and/or bandwidth of the initial downlink BWP (first initial downlink BWP) configured in initialDownlinkBWP in downlinkConfigCommon is By identifying/determining the initial downlink BWP (second initial downlink BWP) configured in initialDownlinkBWP-forRedCap-r17 in downlinkConfigCommon that can be included in and can receive downlink signals. Terminal device 1 that does not support the frequency location and/or bandwidth of the initial downlink BWP (second initial downlink BWP) configured in initialDownlinkBWP-forRedCap-r17 in downlinkConfigCommon is configured using SIB1 (other SIB or RRC signaling). By identifying/determining the initial downlink BWP (third initial downlink BWP) configured in initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon that may be included in can receive downlink channels and downlink signals.

When setting the initial downlink BWP of a frequency location and/or bandwidth that is not supported by a specific terminal device 1 in locationAndBandwidth in initialDownlinkBWP, the base station device 3 sets the frequency location and/or bandwidth that the specific terminal device 1 supports. By configuring the initial downlink BWP with locationAndBandwidth included in initialDownlinkBWP-forRedCap-r17 or locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon, it is possible to appropriately transmit the downlink channel and downlink signal. The base station device 3 determines the frequency position and/or Alternatively, for the terminal device 1 that does not support the bandwidth, the downlink channel and reference signal corresponding to the second initial downlink BWP are transmitted, and the frequency position and bandwidth of the first initial downlink BWP are supported. The downlink channel and reference signal corresponding to the first initial downlink BWP can be transmitted to the terminal device 1. Furthermore, the base station device 3 includes locationAndBandwidth in initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling), thereby controlling the first initial downlink BWP and the second downlink BWP. The downlink channel and reference signal corresponding to the third initial downlink BWP can be transmitted to the terminal device 1 that does not support the frequency position and/or bandwidth of the third initial downlink BWP. When setting the initial downlink BWP of the frequency location and/or bandwidth supported by all terminal devices 1 in locationAndBandwidth in the initialDownlinkBWP, the base station device 3 sets the initial downlink BWP of the frequency location and/or bandwidth supported by all the terminal devices 1. ) does not need to include initialDownlinkBWP-forRedCap-r17 and initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon. The base station device 3 sets the initial downlink BWP of the frequency location and/or bandwidth supported by some of the terminal devices 1 in locationAndBandwidth in the initialDownlinkBWP, and sets the initial downlink BWP of the frequency location and/or bandwidth supported by the other terminal devices 1. When setting the initial downlink BWP width with initialDownlinkBWP-r17, it is not necessary to include initialDownlinkBWP-forRedCap-r18 in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling).

Terminal device 1 includes genericParameters in initialDownlinkBWP in downlinkConfigCommon regardless of whether initialDownlinkBWP-forRedCap-r17 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). The subcarrier spacing used in all channels and reference signals in the initial downlink BWP may be identified/determined using subcarrierSpacing. Terminal device 1 includes genericParameters in initialDownlinkBWP in downlinkConfigCommon regardless of whether initialDownlinkBWP-forRedCap-r18 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). The subcarrier spacing used in all channels and reference signals in the initial downlink BWP may be identified/determined using subcarrierSpacing.

Terminal device 1 includes genericParameters in initialDownlinkBWP in downlinkConfigCommon regardless of whether initialDownlinkBWP-forRedCap-r17 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). cyclicPrefix may be used to identify/determine whether an extended cyclic prefix CP is used in the initial downlink BWP. Terminal device 1 includes genericParameters in initialDownlinkBWP in downlinkConfigCommon regardless of whether initialDownlinkBWP-forRedCap-r18 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). cyclicPrefix may be used to identify/determine whether an extended cyclic prefix CP is used in the initial downlink BWP.

Terminal device 1 uses pdcch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether initialDownlinkBWP-forRedCap-r17 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). may be used to identify/determine cell-specific parameters of the PDCCH in the initial downlink BWP and monitor/receive the PDCCH. Terminal device 1 uses pdcch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether initialDownlinkBWP-forRedCap-r18 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). may be used to identify/determine cell-specific parameters of the PDCCH in the initial downlink BWP and monitor/receive the PDCCH.

Terminal device 1 uses pdsch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether initialDownlinkBWP-forRedCap-r17 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). may be used to identify/determine cell-specific parameters of the PDSCH in the initial downlink BWP and receive the PDSCH. Terminal device 1 uses pdsch-ConfigCommon included in initialDownlinkBWP in downlinkConfigCommon, regardless of whether initialDownlinkBWP-forRedCap-r18 is included in downlinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling). may be used to identify/determine cell-specific parameters of the PDSCH in the initial downlink BWP and receive the PDSCH.

Terminal device 1 receives locationAndBandwidth included in initialDownlinkBWP-forRedCap-r17 in SIB1 (or other SIBs), and identifies/determines the frequency position and bandwidth of the initial downlink BWP based on the locationAndBandwidth. and the initial downlink BWP specified/determined by the locationAndBandwidth includes the entire CORESET#0, then until the RRC connection is established, re-established or resumed (e.g. before receiving RRCSetup, RRCResume or RRCReestablishment), The CORESET#0 is set as the initial downlink BWP, and after the RRC connection is established, the initial downlink BWP is set using the locationAndBandwidth included in the initialDownlinkBWP-forRedCap-r17 in the received SIB1 (or other SIBs). May be determined/specified. However, if the initial downlink BWP is set to CORESET#0 until the RRC connection is established, re-established, or restarted, the terminal device 1 performs the random access procedure using the initial downlink BWP determined/specified by CORESET#0. It's okay.

Terminal device 1 receives locationAndBandwidth included in initialDownlinkBWP-forRedCap-r17 in SIB1 (or other SIBs), and identifies/determines the frequency position and bandwidth of the initial downlink BWP based on the locationAndBandwidth. and if the initial downlink BWP specified/determined by the locationAndBandwidth does not include the entire CORESET#0, the received SIB1 (other SIB The initial downlink BWP specified/determined by locationAndBandwidth included in initialDownlinkBWP-forRedCap-r17 may be used.

Terminal device 1 receives locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 in SIB1 (or other SIBs), and identifies/determines the frequency position and bandwidth of the initial downlink BWP based on the locationAndBandwidth. and the initial downlink BWP specified/determined by the locationAndBandwidth includes the entire CORESET#0, then until the RRC connection is established, re-established or resumed (e.g. before receiving RRCSetup, RRCResume or RRCReestablishment), The CORESET#0 is set as the initial downlink BWP, and after the RRC connection is established, the initial downlink BWP is set using the locationAndBandwidth included in the initialDownlinkBWP-forRedCap-r18 in the received SIB1 (or other SIBs). May be determined/specified. However, if the initial downlink BWP is set to CORESET#0 until the RRC connection is established, re-established, or restarted, the terminal device 1 performs the random access procedure using the initial downlink BWP determined/specified by CORESET#0. It's okay.

Terminal device 1 receives locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 in SIB1 (or other SIBs), and identifies/determines the frequency position and bandwidth of the initial downlink BWP based on the locationAndBandwidth. and if the initial downlink BWP specified/determined by the locationAndBandwidth does not include the entire CORESET#0, the received SIB1 (other SIB The initial downlink BWP specified/determined by locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 may be used.

Based on the information included in SIB1 (which may be other SIBs), terminal device 1 performs initial downlink BWP (separate initial downlink BWP) based on locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 in SIB1. It is also possible to switch the timing for determining/identifying the The parameter initialBwpTiming, which indicates the timing to apply locationAndBandwidth included in initialDownlinkBWP-forRedCap-r18 in SIB1 (or other SIBs), may be 1-bit information.

In a certain cell, when receiving SIB1 with a certain initial downlink BWP (first initial downlink BWP), an initial downlink BWP (with a frequency position and/or bandwidth different from the first initial downlink BWP) If a second initial downlink BWP) is configured, the band of the second initial downlink BWP may not include a synchronization signal block transmitted within the band of the first initial downlink BWP. . An additional synchronization signal within the band of the second initial downlink BWP when the second initial downlink BWP requires a signal with the role of a synchronization signal block for paging, random access and/or other uses. block (hereinafter referred to as additional synchronization signal block (additional SSB)). The base station device 3 may transmit the additional synchronization signal block within the band of the second initial downlink BWP specified/determined by locationAndBandwidth in the initialDownlinkBWP-forRedCap-r17. The terminal device 1 may receive an additional synchronization signal block transmitted within the band of the second initial downlink BWP specified/determined from locationAndBandwidth in the initialDownlinkBWP-forRedCap-r17. The additional synchronization signal block may be a synchronization signal block (referred to as NCD-SSB: Non-Cell Defining SSB) that is not a cell-defining synchronization signal block (referred to as CD-SSB: Cell Defining SSB). . For example, additional synchronization signal blocks may not be centered around the Synchronization Raster.

In a certain cell, when receiving SIB1 with a certain initial downlink BWP (first initial downlink BWP), a frequency position and/or band different from the first initial downlink BWP and the second initial downlink BWP When an initial downlink BWP (third initial downlink BWP) with a width of May not contain signal blocks. If the third initial downlink BWP requires a signal with the role of a synchronization signal block for paging, random access, and/or other purposes, an additional synchronization signal block within the band of the third initial downlink BWP. may be sent. The base station device 3 may transmit the additional synchronization signal block within the band of the third initial downlink BWP specified/determined by locationAndBandwidth in the initialDownlinkBWP-forRedCap-r18. The terminal device 1 may receive an additional synchronization signal block transmitted within the band of the third initial downlink BWP specified/determined from the locationAndBandwidth in the initialDownlinkBWP-forRedCap-r18. The additional synchronization signal block may be NCD-SSB:. For example, additional synchronization signal blocks may not be centered around the Synchronization Raster.

FIG. 7 is a diagram showing an overview of the frequency positions of additional synchronization signal blocks according to the present embodiment. In FIG. 7, two initial downlink BWPs, a first initial downlink BWP (initial DL BWP) and a second initial downlink BWP (separate initial DL BWP), are set in a certain cell. However, the initial downlink BWP may be the band of CORESET #0. In FIG. 7, the initial downlink BWP includes a PDSCH (PDSCH with SIB1) that includes at least a synchronization signal block (SSB), CORESET #0, and SIB1 in the band. In FIG. 7, the second initial downlink BWP includes at least an additional synchronization signal block (additional SSB) in the band. The terminal device 1 that has received the synchronization signal block specifies the frequency position of CORESET #0, and specifies the frequency position and time position of the PDSCH including SIB1 based on the PDCCH received in CORESET #0. The terminal device 1 that has received the PDSCH including SIB1 uses the second initial downlink BWP according to the parameter locationAndBandwidth included in the initialDownlinkBWP-forRedCap-r18 in the SIB1 (or may be another SIB specified by the SIB1). Identify/determine the frequency location (including bandwidth) of The terminal device 1 that has specified/determined the frequency position of the second initial downlink BWP uses the parameter ssbFrequencyOffset included in the initialDownlinkBWP-forRedCap-r18 in the SIB1 (or may be another SIB specified by the SIB1). -rc may identify/determine the frequency location of an additional synchronization signal block transmitted within the separate initial downlink BWP and receive the additional synchronization signal block.

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

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

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

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

The initial uplink BWP may be configured by parameters provided in MIB, parameters provided in SIB1, parameters provided in SIB, and/or RRC parameters. For example, the initial uplink BWP may be configured by the parameter initialUplinkBWP included in the parameter uplinkConfigCommon provided in SIB1. For example, the initial downlink BWP may be configured by the parameter initialUplinkBWP-forRedCap-r17 included in the parameter UplinkConfigCommon provided in SIB1. For example, the initial downlink BWP may be configured by the parameter initialUplinkBWP-forRedCap-r18 included in the parameter uplinkConfigCommon provided in SIB1. The parameter uplinkConfigCommon provided in SIB1 includes initialUplinkBWP, initialUplinkBWP-forRedCap-r17, and/or initialUplinkBWP-forRedCap-r18, and any one of these parameters included in the uplinkConfigCommon is used to configure the initial uplink BWP. May be set. However, initialUplinkBWP, initialUplinkBWP-forRedCap-r17, and initialUplinkBWP-forRedCap-r18 may be parameters that indicate UE-specific (UE-specific, dedicated) settings for the initial uplink BWP.

FIG. 9 shows the parameter configuration of UplinkConfigCommonSIB (or UplinkConfigCommon), which is an information element (IE: Information Element) of parameter uplinkConfigCommon, which is uplink configuration information according to this embodiment, and the parameter information element BWP, which is configuration information of uplink BWP. - Parameter configuration of UplinkCommon, parameter information element that is BWP setting information An example of the parameter configuration of BWP is shown.

uplinkConfigCommon is a parameter that indicates the basic parameters regarding one uplink carrier and transmission in the corresponding cell (for example, called frequencyInfoUL), a parameter that indicates the configuration of the first initial uplink BWP of a certain serving cell (for example, called initialUplinkBWP). ), a parameter indicating the setting of the second initial uplink BWP of a certain serving cell (for example, referred to as initialUplinkBWP-forRedCap-r17), and a parameter indicating the setting of the third initial uplink BWP of a certain serving cell ( For example, initialUplinkBWP-forRedCap-r18) may be included. However, initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 included in uplinkConfigCommon may have a parameter configuration indicated by the same information element (BWP-UplinkCommon) as initialUplinkBWP included in uplinkConfigCommon. However, initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 may be included in SIB and/or RRC parameters other than SIB1. However, initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 may be parameters that include part or all of the parameter configuration of initialUplinkBWP included in uplinkConfigCommon, and each is the configuration information for the second initial uplink BWP. and configuration information for the third initial uplink BWP. However, when uplinkConfigCommon is transmitted by SIB, initialUplinkBWP may always be included, and initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 may not be included. initialUplinkBWP, initialUplinkBWP-forRedCap-r17, and initialUplinkBWP-forRedCap-r18 according to this embodiment include general parameters genericParameters of initial uplink BWP, cell-specific parameters rach-ConfigCommon of random access, and cell-specific parameters of PUSCH. It may include the parameter pushch-ConfigCommon, the PUCCH cell-specific parameter pucch-ConfigCommon, and/or other parameters.

initialUplinkBWP is a parameter that sets the initial uplink BWP which is the first bandwidth (e.g. up to 100MHz), and initialUplinkBWP-forRedCap-r17 is the second bandwidth (e.g. up to 20MHz) which is narrower than the first bandwidth. It may be a parameter for setting the initial uplink BWP. initialUplinkBWP-forRedCap-r17 may be a parameter that terminal device 1 that supports a bandwidth greater than the third bandwidth (for example, 20MHz) does not refer to, and only terminal device 1 that supports only the third bandwidth or less It may be a parameter to be referenced. initialUplinkBWP-forRedCap-r18 may be a parameter for setting an initial uplink BWP that is a fourth bandwidth narrower than the second bandwidth (for example, a maximum of 5 MHz). initialUplinkBWP-forRedCap-r18 may be a parameter that terminal device 1 that supports a bandwidth larger than the fifth bandwidth (for example, 5MHz) does not refer to, and only terminal device 1 that supports only the fifth bandwidth or less It may be a parameter to be referenced. In this way, by setting one or more parameters that set different bandwidths as the initial uplink BWP in uplinkConfigCommon, the initial uplink BWP can be set according to the maximum bandwidth supported by each of the multiple terminal devices 1. Can be set. For example, the bandwidth of the initial uplink BWP set by initialUplinkBWP is 50MHz, the bandwidth of the initial uplink BWP set by initialUplinkBWP-forRedCap-r17 is 10MHz, and the initial uplink BWP set by initialUplinkBWP-forRedCap-r18 is 10MHz. If the bandwidth of is 5MHz and uplinkConfigCommon contains these three parameters, terminal device 1 that supports a bandwidth of up to 100MHz will set an initial uplink BWP with a bandwidth of 50MHz based on initialUplinkBWP, and up to 20MHz Terminal device 1 that supports a bandwidth of up to 5MHz sets an initial uplink BWP with a bandwidth of 10MHz based on initialUplinkBWP-forRedCap-r17, and terminal device 1 that supports a bandwidth of up to 5MHz sets an initial uplink BWP with a bandwidth of 10MHz based on initialUplinkBWP-forRedCap-r18. An initial uplink BWP with a bandwidth of 5MHz may be set.

If initialUplinkBWP-forRedCap-r18 is included in uplinkConfigCommon, the terminal device 1 may identify/set/determine the initial uplink BWP based on the parameters included in the initialUplinkBWP-forRedCap-r18. For example, when the terminal device 1 receives the initialUplinkBWP-forRedCap-r18 in SIB1, it may identify/set/determine the initial uplink BWP based on the parameters of the initialuplinkBWP-forRedCap-r18.

If there are multiple initial uplink BWP configuration parameters (or multiple frequency positions and/or multiple If bandwidth configuration information is broadcast), part of the information included in the genericParameters in the initialUplinkBWP is the configuration parameters of the plurality of initial uplink BWPs (or the plurality of frequency positions and/or of the initial uplink BWPs). or setting information of multiple bandwidths).

The information element BWP of the parameter genericParameters is the same as the information element BWP in the above-mentioned downlink BWP.

Terminal device 1 sets the initial uplink BWP bandwidth set by initialUplinkBWP and initialUplinkBWP-forRedCap-r17 provided in uplinkConfigCommon included in SIB1 (other SIB and RRC parameters may be possible) received by terminal device 1. If not supported, the terminal device 1 does not need to set the initial uplink BWP.

If the initialUplinkBWP-forRedCap-r18 is provided in the uplinkConfigCommon included in the SIB1 received by the terminal device 1, the terminal device 1 may determine/specify the initial downlink BWP using the initialUplinkBWP-forRedCap-r18.

initialUplinkBWP-forRedCap-r18 is not provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, initialUplinkBWP-forRedCap-r17 is provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, and the corresponding If the terminal device 1 supports the BWP bandwidth set in the initialUplinkBWP-forRedCap-r17, the terminal device 1 may determine/specify the initial uplink BWP using the initialUplinkBWP-forRedCap-r17.

If initialUplinkBWP-forRedCap-r18 is not provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, and initialUplinkBWP-forRedCap-r17 is provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, The terminal device 1 may determine/specify the initial uplink BWP using the initialUplinkBWP-forRedCap-r17.

If initialUplinkBWP-forRedCap-r18 and initialUplinkBWP-forRedCap-r17 are not provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, terminal device 1 sets initial uplink BWP to initialUplinkBWP provided in uplinkConfigCommon in SIB1. It may be determined/specified by .

If initialUplinkBWP-forRedCap-r18 and initialUplinkBWP-forRedCap-r17 are not provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, and terminal device 1 supports the BWP bandwidth set in initialUplinkBWP. , the terminal device 1 may determine/specify the initial uplink BWP with the initialUplinkBWP provided in uplinkConfigCommon in SIB1.

If initialUplinkBWP-forRedCap-r18 is not provided/set in uplinkConfigCommon in SIB1 received by terminal device 1, terminal device 1 may determine/specify the initial uplink BWP with initialUplinkBWP instead of initialUplinkBWP-forRedCap-r17. do not have. However, due to the relationship between the bandwidths set in each of initialUplinkBWP, initialUplinkBWP-forRedCap-r17, and initialUplinkBWP-forRedCap-r18, if initialUplinkBWP-forRedCap-r18 is not used, the bandwidth will be closer to initialUplinkBWP-forRedCap-r18. By using initialUplinkBWP-forRedCap-r17, which is expected to be set, it may be possible to obtain the advantage of having flexibility in the bandwidth set for terminal device 1. However, if it is assumed that the base station device 3 sets the initial uplink BWP with a bandwidth that can be set by all terminal devices 1 in the cell, which of initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 By not setting also, all terminal devices 1 may set/specify the initial uplink BWP band in initialUplinkBWP. By preparing three parameters for the initial uplink BWP bandwidth in this way, when three or more types of terminal devices 1 that support different bandwidths coexist within a cell, the initial The bandwidth of uplink BWP can be made flexible. Note that although this embodiment shows a case where three parameters are used to set three initial uplink BWPs with different bandwidths, it is also possible to use four or more parameters.

When setting the initial uplink BWP of a frequency location and/or bandwidth that is not supported by a specific terminal device 1 in locationAndBandwidth in initialUplinkBWP, the base station device 3 sets the frequency location and/or bandwidth that the specific terminal device 1 supports. By setting the initial uplink BWP of with locationAndBandwidth included in initialUplinkBWP-forRedCap-r17 or locationAndBandwidth included in initialUplinkBWP-forRedCap-r18 in uplinkConfigCommon, uplink channels and uplink signals can be appropriately received. The base station device 3 determines the frequency position and/or Alternatively, from the terminal device 1 that does not support the bandwidth, the uplink channel corresponding to the second initial uplink BWP is received, and from the terminal device 1 that supports the frequency position and bandwidth of the first initial uplink BWP, the uplink channel corresponding to the second initial uplink BWP is received. , an uplink channel corresponding to a first initial uplink BWP may be received. Furthermore, the base station device 3 includes locationAndBandwidth in initialUplinkBWP-forRedCap-r18 in uplinkConfigCommon in SIB1 (which may be other SIBs or RRC signaling), thereby controlling the first initial uplink BWP and the second uplink BWP. The uplink channel corresponding to the third initial uplink BWP can be received from the terminal device 1 that does not support the frequency position and/or bandwidth of the initial uplink BWP. When setting the initial uplink BWP of the frequency location and/or bandwidth supported by all terminal devices 1 in locationAndBandwidth in the initialUplinkBWP, the base station device 3 configures SIB1 (other SIB or RRC signaling may be used) ) does not need to include initialUplinkBWP-forRedCap-r17 and initialUplinkBWP-forRedCap-r18 in uplinkConfigCommon. The base station device 3 sets the initial uplink BWP of the frequency location and/or bandwidth supported by some of the terminal devices 1 in locationAndBandwidth in the initialUplinkBWP, and sets the initial uplink BWP of the frequency location and/or bandwidth supported by the other terminal devices 1. When setting the initial uplink BWP for the width using initialUplinkBWP-r17, it is not necessary to include initialUplinkBWP-forRedCap-r18 in uplinkConfigCommon in SIB1 (which may be other SIB or RRC signaling).

The random access procedure of this embodiment will be explained.

Random access procedures are classified into two procedures: contention-based (CB) and non-contention-based (non-CB) (also referred to as contention free). Contention-based random access is also called CBRA, and non-contention-based random access is also called CFRA.

The random access procedure is initiated by a PDCCH order, a MAC entity, a notification of beam failure from a lower layer, or RRC, etc.

The contention-based random access procedure is initiated by a PDCCH order, a MAC entity, a notification of beam failure from a lower layer, or RRC, etc. When a beam failure notification is provided to the MAC entity of the terminal device 1 from the physical layer of the terminal device 1 and a certain condition is met, the MAC entity of the terminal device 1 starts a random access procedure. When a beam failure notification is provided to the MAC entity of terminal device 1 from the physical layer of terminal device 1, the procedure of determining whether a certain condition is satisfied and starting a random access procedure is called a beam failure recovery procedure. It's okay. This random access procedure is a random access procedure for beam failure recovery requests. Random access procedures initiated by the MAC entity include random access procedures initiated by a scheduling request procedure. The random access procedure for beam failure recovery request may or may not be considered a random access procedure initiated by the MAC entity. A random access procedure for a beam failure recovery request and a random access procedure initiated by a scheduling request procedure may perform different procedures, so a random access procedure for a beam failure recovery request and a scheduling request procedure are distinguished. You can do it like this. The random access procedure for beam failure recovery request and the scheduling request procedure may be random access procedures initiated by the MAC entity. In some embodiments, 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 beam failure recovery request is referred to as random access procedure initiated by the beam failure notification from lower layers. It may also be called a procedure. Hereinafter, starting a random access procedure upon receiving a beam failure notification from a lower layer may mean starting a random access procedure for a beam failure recovery request.

At the time of initial access from a state where the terminal device 1 is not connected (communicating) with the base station device 3, and/or while connected to the base station device 3, uplink data or transmission that can be transmitted to the terminal device 1 is transmitted. A contention-based random access procedure is performed, such as during a scheduling request when possible sidelink data occurs. However, the applications of contention-based random access are not limited to these.

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

Non-contention-based random access allows for quick access between the terminal device 1 and the base station device 3 when the base station device 3 and the terminal device 1 are connected but the handover or the transmission timing of the mobile station device is not valid. may be used for uplink synchronization. Non-contention-based random access may be used to send a beam failure recovery request when a beam failure occurs at the terminal device 1. However, the uses of non-contention-based random access are not limited to these.

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

The terminal device 1 of this embodiment receives random access setting information via an upper layer before initiating a random access procedure.

The base station device 3 transmits RRC parameters including random access configuration information to the terminal device 1 as an RRC message.

The terminal device 1 uses one or more available random access preambles and/or one or more available physical random access preambles to be used for the random access procedure based on the propagation path characteristics between the terminal device 1 and the base station device 3. A physical random access channel (PRACH) opportunity (also referred to as a random access channel (RACH) opportunity, PRACH transmission opportunity, RACH transmission opportunity) may be selected. The terminal device 1 transmits a signal based on the propagation path characteristics (for example, it may be the reference signal received power (RSRP)) measured by the reference signal (for example, SS/PBCH block and/or CSI-RS) received from the base station device 3. may select one or more available random access preambles and/or one or more PRACH opportunities for use in the random access procedure.

The random access procedure is realized by sending and receiving multiple types of messages between the terminal device 1 and the base station device 3. For example, in 4-step random access, the following four messages are sent and received.

<Message 1>
The terminal device 1 that has generated transmittable uplink data or transmittable sidelink data transmits a preamble for random access (referred to as a random access preamble) to the base station device 3 using PRACH. This transmitted random access preamble may be referred to as message 1 or Msg1. The random access preamble is configured to notify information to the base station device 3 using a plurality of sequences. For example, if 64 types of sequences are prepared, 6 bits of information can be shown to the base station device 3. This information is designated as a Random Access Preamble Identifier. A preamble sequence is selected from a preamble sequence set using a preamble index. The selected random access preamble is transmitted on the designated PRACH resource.

<Message 2>
The base station device 3 that received the random access preamble generates a random access response (RAR) including an uplink grant to instruct the terminal device 1 to transmit, and sends the generated random access response to the terminal on the PDSCH. Send to device 1. The random access response may be referred to as message 2 or Msg2. The base station device 3 also calculates the transmission timing shift between the terminal device 1 and the base station device 3 from the received random access preamble, and provides transmission timing adjustment information (Timing Advance Command) for adjusting the shift. Include in message 2. Furthermore, the base station device 3 includes in the message 2 a random access preamble identifier corresponding to the received random access preamble. The base station device 3 also scrambles the random access preamble with RA-RNTI (Random Access-Radio Network Temporary Identity) to indicate that the response is addressed to the terminal device 1 that transmitted the random access preamble. The DCI with the added CRC is sent on the PDCCH. RA-RNTI is determined according to the frequency and time location information of the PRACH that transmitted the random access preamble.

<Message 3>
The terminal device 1 that transmitted the random access preamble monitors the PDCCH for the random access response identified by the RA-RNTI within multiple subframe periods (referred to as RAR windows) after transmitting the random access preamble. . When the terminal device 1 that transmitted the random access preamble detects the corresponding RA-RNTI, it decodes the random access response allocated to the PDSCH. The terminal device 1 that has successfully decoded the random access response checks whether the random access response includes a random access preamble identifier corresponding to the transmitted random access preamble. If a random access preamble identifier is included, the transmission timing adjustment information indicated in the random access response is used to correct the synchronization shift. Furthermore, the terminal device 1 uses the uplink grant included in the received random access response to transmit the data stored in the buffer to the base station device 3. The data transmitted using the uplink grant at this time is referred to as message 3 or Msg3.

In addition, if the successfully decoded random access response is the first one successfully received in a series of random access procedures, the terminal device 1 sends message 3 containing information for identifying the terminal device 1 (C- RNTI) and sends it to the base station device 3.

<Message 4>
When the base station device 3 receives uplink transmission using the resource allocated to the message 3 of the terminal device 1 in the random access response, it detects the C-RNTI MAC CE included in the received message 3. Then, when establishing a connection with the terminal device 1, the base station device 3 transmits the PDCCH to the detected C-RNTI. When transmitting a PDCCH to the detected C-RNTI, the base station device 3 includes an uplink grant in the PDCCH. These PDCCHs transmitted by the base station device 3 are called message 4, Msg4, or contention resolution message.

The terminal device 1 that has transmitted the message 3 starts a contention resolution timer that defines a period for monitoring the message 4 from the base station device 3, and attempts to receive the PDCCH transmitted from the base station within the timer. Terminal device 1, which sent C-RNTI MAC CE in message 3, received the PDCCH addressed to the sent C-RNTI from base station device 3, and the PDCCH included an uplink grant for new transmission. If so, it is assumed that contention resolution with the other terminal device 1 has been successful, the contention resolution timer is stopped, and the random access procedure is ended. If the reception of the PDCCH addressed to C-RNTI sent by the terminal device in message 3 cannot be confirmed within the timer period, it is assumed that contention resolution was not successful, and the terminal device 1 transmits the random access preamble again. Make the transmission and continue with the random access procedure. However, if the transmission of the random access preamble is repeated a predetermined number of times and contention resolution is not successful, it is determined that there is a problem with random access, and the upper layer is notified of the random access problem. For example, higher layers may reset the MAC entity based on random access issues. When requested to reset the MAC entity by the upper layer, the terminal device 1 stops the random access procedure.

By transmitting and receiving the above four messages, the terminal device 1 can synchronize with the base station device 3 and perform uplink data transmission to the base station device 3. However, two-step random access may be used in which four messages are shortened and the terminal device 1 and base station device 3 are synchronized by sending and receiving two messages, message A and message B.

FIG. 10 is a flow diagram illustrating an example of the initial downlink BWP determination process in the terminal device 1 of this embodiment. In step S1001, the terminal device 1 receives downlink configuration information (downlinkConfigCommon) including the parameter initialDownlinkBWP in a system information block (SIB) transmitted from the base station device 3. In step S1002, the terminal device 1 determines whether the received downlink configuration information includes the parameter initialDownlinkBWP-forRedCap-r18. If yes in step S1002 (S1002-Yes), in step S1003, the terminal device 1 sets the initial downlink BWP using the bandwidth information (locationAndBandwidth) indicated by the parameter initialDownlinkBWP-forRedCap-r18. If the determination in step S1002 is negative (S1002-No), the terminal device 1 determines in step S1004 whether the parameter initialDownlinkBWP-forRedCap-r17 is included in the received downlink configuration information. If yes in step S1004 (S1004-Yes), in step S1005, the terminal device 1 sets the initial downlink BWP using the bandwidth information (locationAndBandwidth) indicated by the parameter initialDownlinkBWP-forRedCap-r17. If the determination in step S1004 is negative (S1004-No), in step S1006, the terminal device 1 sets the initial downlink BWP using the bandwidth information (locationAndBandwidth) indicated by the parameter initialDownlinkBWP. However, the determination in step S1004 is whether the received downlink configuration information includes the parameter initialDownlinkBWP-forRedCap-r17 and whether the bandwidth indicated by initialDownlinkBWP-forRedCap-r17 is less than or equal to the maximum bandwidth supported by the terminal device. No, it may be. The terminal device 1 may receive a downlink signal and a downlink channel using the set initial downlink BWP. The terminal device 1 may monitor the PDCCH using the CORESET and/or search space in the configured initial downlink BWP. Even if the base station device 3 transmits a downlink signal and a downlink channel in each of one or more initial downlink BWPs configured in initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18, good. The base station device 3 uses the CORESET and/or search space included in each of the one or more initial downlink BWPs configured in initialDownlinkBWP, initialDownlinkBWP-forRedCap-r17, and/or initialDownlinkBWP-forRedCap-r18. One or more PDCCHs may be transmitted. In this way, by setting the initial downlink BWP using information on different bandwidths depending on the presence or absence of parameters included in the downlink configuration information, terminal device 1 can set the initial downlink BWP according to the bandwidth supported by the device itself. Downlink BWP can be used. By including a plurality of parameters included in the downlink configuration information, the base station device 3 can configure initial downlink BWPs of different bandwidths for different terminal devices 1 that support different bandwidths. By not including some of the parameters among the plurality of parameters in the downlink configuration information, the base station device 3 provides an initial downlink BWP of the same bandwidth to different terminal devices 1 that support different bandwidths. Can be set.

FIG. 11 is a flow diagram illustrating an example of the initial uplink BWP determination process in the terminal device 1 of this embodiment. In step S2001, the terminal device 1 receives uplink configuration information (uplinkConfigCommon) in a system information block (SIB) transmitted from the base station device 3. In step S2002, the terminal device 1 determines whether the received uplink configuration information includes the parameter initialUplinkBWP-forRedCap-r18. If yes in step S2002 (S2002-Yes), in step S2003, the terminal device 1 sets the initial uplink BWP using the bandwidth information (locationAndBandwidth) indicated by the parameter initialUplinkBWP-forRedCap-r18. If the determination in step S2002 is negative (S2002-No), the terminal device 1 determines in step S2004 whether the parameter initialUplinkBWP-forRedCap-r17 is included in the received uplink configuration information. If yes in step S2004 (S2004-Yes), in step S2005, the terminal device 1 sets the initial uplink BWP using the bandwidth information (locationAndBandwidth) indicated by the parameter initialUplinkBWP-forRedCap-r17. If the determination in step S2004 is negative (S2004-No), in step S2006, the terminal device 1 uses the bandwidth information (locationAndBandwidth) indicated by the parameter initialUplinkBWP included in the received uplink configuration information to configure the initial uplink BWP. Set. However, the determination in step S2004 is whether the parameter initialUplinkBWP-forRedCap-r17 is included in the received uplink configuration information and the bandwidth indicated by initialUplinkBWP-forRedCap-r17 is less than or equal to the maximum bandwidth supported by the terminal device. No, it may be. However, in step 2006, if the received uplink configuration information does not include any parameters, the terminal device 1 may not configure the initial uplink BWP. The terminal device 1 may transmit an uplink signal and an uplink channel using the set initial uplink BWP. The terminal device 1 and the base station device 3 transmit uplink signals and uplink channels in each of one or more initial uplink BWPs configured in initialUplinkBWP, initialUplinkBWP-forRedCap-r17, and/or initialUplinkBWP-forRedCap-r18. You may receive. In this way, by setting the initial uplink BWP using information on different bandwidths depending on the presence or absence of parameters included in the uplink configuration information, terminal device 1 can set the initial uplink BWP according to the bandwidth supported by the device itself. Uplink BWP can be used. By including a plurality of parameters included in the uplink configuration information, the base station device 3 can configure initial uplink BWPs of different bandwidths for different terminal devices 1 that support different bandwidths. By not including some of the parameters among the plurality of parameters in the uplink configuration information, the base station device 3 provides an initial uplink BWP of the same bandwidth to different terminal devices 1 that support different bandwidths. Can be set.

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

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

The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by user operations etc. to the wireless transmitting/receiving unit 10. The upper layer processing unit 14 processes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio resource control) layer. Processes part or all of the Resource Control (RRC) layer. The upper layer processing unit 14 has a function of acquiring bit information of MIB (which may be REDCAP MIB), SIB1 (which may be REDCAP SIB1), and other SIBs (which may be REDCAP SIB). It's okay. The upper layer processing unit 14 may have a function of determining/specifying initial downlink BWP settings (eg, frequency position and bandwidth) based on system information block (SIB1/SIB) or RRC signaling information. The upper layer processing unit 14 may have a function of determining/specifying initial uplink BWP settings (eg, frequency position and bandwidth) based on system information block (SIB1/SIB) or RRC signaling information.

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

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

The wireless transmitter/receiver 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transmitting/receiving 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 transmitter/receiver 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3 and the like. The wireless transmitter/receiver 10 outputs the upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processor 14. Furthermore, the radio transmitter/receiver 10 generates and transmits uplink signals (including PUCCH and/or PUSCH) based on instructions from the upper layer processor 14. The radio transceiver 10 may have a function of receiving a synchronization signal block, an additional synchronization signal block, PSS, SSS, PBCH, DMRS for PBCH, random access response, PDCCH and/or PDSCH. The radio transmitter/receiver 10 may have a function of transmitting PRACH (which may be a random access preamble), PUCCH, and/or PUSCH. The wireless transmitter/receiver 10 may have a function of monitoring PDCCH. The wireless transmitter/receiver 10 may have a function of receiving DCI on PDCCH. The wireless transmitting/receiving unit 10 may have a function of outputting the DCI received on the PDCCH to the upper layer processing unit 14. The wireless transmitter/receiver 10 may have a function of receiving a system information block (SIB1 and/or SIB) corresponding to a predetermined cell. The radio transmitting/receiving unit 10 may have a function of receiving DCI with a CRC scrambled with a predetermined RNTI (eg, SI-RNTI, RA-RNTI, P-RNTI, etc.) in a certain BWP of a certain cell. The radio transceiver 10 may have a function of receiving an SIB (which may be SIB1) or a random access response in a certain BWP of a certain cell via a PDSCH scheduled for a predetermined time resource.

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

The baseband section 13 converts the analog signal input from the RF section 12 into a digital signal. The baseband unit 13 removes a portion corresponding to the CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the signal from which the CP has been removed, and transforms the 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 generates a baseband digital signal. Convert band digital signals to analog signals. Baseband section 13 outputs the converted analog signal to RF section 12.

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

The RF unit 12 may use an antenna switch to connect the antenna unit 11 and the filter included in the RF unit 12 when receiving a signal, and to connect the power amplifier included in the antenna unit 11 and the RF unit 12 when transmitting a signal.

If the bandwidth of the configured downlink BWP (for example, initial downlink BWP) is wider than the bandwidth supported by the receiver of its own device (which may be referred to as allocated bandwidth), the RF unit 12 configures the downlink A function for adjusting/retuning the frequency band to which the RF circuit is applied within the BWP may be provided. However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when down-converting the received signal to a baseband signal.

If the bandwidth of the configured uplink BWP (for example, initial downlink BWP) is wider than the bandwidth supported by the transmitter of its own device (which may be referred to as allocated bandwidth), the RF unit 12 A function may be provided to adjust/readjust the frequency band to which the RF circuit is applied within the BWP. However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier wave frequency applied when upconverting an analog signal to the carrier wave frequency.

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

The upper layer processing unit 34 processes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a radio resource control (Radio resource control) layer. Processes part or all of the Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of generating the 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 and the like to the wireless transmitting/receiving unit 30. The upper layer processing unit 34 may have a function of generating a system information block (SIB1/SIB) containing information for the terminal device 1 to specify the initial downlink BWP and/or RRC signaling. The upper layer processing unit 34 may have a function of generating a system information block (SIB1/SIB) containing information for the terminal device 1 to specify the initial uplink BWP and/or RRC signaling.

The medium access control layer processing unit 35 included in the upper layer processing unit 34 performs MAC layer processing. The medium access control layer processing unit 35 performs processing related to scheduling requests 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 performs RRC layer processing. The radio resource control layer processing unit 36 generates DCI (uplink grant, downlink grant) including resource allocation information for 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. to be placed in DCI and PDSCH. or obtain it from a higher-level node and output it to the wireless transmitter/receiver 30. Furthermore, the radio resource control layer processing unit 36 manages various setting information/parameters of each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via upper layer signals. That is, the radio resource control layer processing unit 36 transmits/broadcasts information indicating various setting information/parameters. The radio resource control layer processing unit 36 may transmit/broadcast information for specifying the setting of one or more reference signals in a certain cell.

When the base station device 3 transmits an RRC message, MAC CE, and/or PDCCH to the terminal device 1, and the terminal device 1 performs processing based on the reception, the base station device 3 Processing (controlling the terminal device 1 and the system) is performed assuming that the terminal device 1 and the system are being executed. That is, the base station device 3 sends to the terminal device 1 an RRC message, a MAC CE, and/or a PDCCH that causes the terminal device to perform processing based on the reception thereof.

The wireless transmitting/receiving unit 30 transmits upper layer signals (RRC messages), DCI, etc. to the terminal device 1. Furthermore, the wireless transmitting/receiving unit 30 receives the uplink signal transmitted from the terminal device 1 based on an 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 PUCCH and/or PUSCH. The wireless transmitter/receiver 30 may have a function of transmitting DCI on PDCCH. The wireless transmitter/receiver 30 may have a function of transmitting the DCI output by the upper layer processor 34 on the PDCCH. The wireless transmitter/receiver 30 may have a function of transmitting SSB, PSS, SSS, PBCH, and/or DMRS for PBCH. The wireless transmitter/receiver 30 may have a function of transmitting an RRC message (which may be an RRC parameter). The wireless transmitter/receiver 30 may have a function for the terminal device 1 to transmit the system information block (SIB1/SIB). The radio transmitting/receiving unit 30 may have a function of transmitting DCI with a CRC scrambled with a predetermined RNTI (eg, SI-RNTI, RA-RNTI, P-RNTI, etc.) in a certain BWP of a certain cell. The radio transmitter/receiver 30 may have a function of transmitting an SIB (which may be SIB1) or a random access response via a PDSCH scheduled at a predetermined time resource in a certain BWP of a certain cell. Some other functions of the wireless transmitter/receiver 30 are the same as those of the wireless transmitter/receiver 10, so description thereof will be omitted. Note that when the base station device 3 is connected to one or more transmitting/receiving points 4, part or all of the functions of the wireless transmitting/receiving section 30 may be included in each transmitting/receiving point 4.

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

Note that the "unit" in the figure is an element that realizes the functions and procedures of the terminal device 1 and the base station device 3, which is also expressed by terms such as section, circuit, component device, device, and unit.

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

The program that runs on the device related to the present invention may be a program that controls the Central Processing Unit (CPU) and the like to make the computer function so as to realize the functions of the embodiments related to the present invention. Programs, or the information handled by them, are temporarily stored in volatile memory such as Random Access Memory (RAM), non-volatile memory such as flash memory, hard disk drives (HDD), or other storage systems.

Incidentally, a program for realizing the functions of the embodiments related to the present invention may be recorded on a computer-readable recording medium. The program recorded on this recording medium may be read into a computer system and executed. The "computer system" herein refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Furthermore, a "computer-readable recording medium" refers to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium. Also good.

Additionally, each functional block or feature of the device used in the embodiments described above may be implemented or executed in an electrical circuit, such as an integrated circuit or multiple integrated circuits. An electrical circuit designed to perform the functions described herein may be a general purpose processor, digital signal processor (DSP), application specific integrated circuit (ASIC), field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof. A general purpose processor may be a microprocessor or a conventional processor, controller, microcontroller, or state machine. The electric circuit described above may be composed of a digital circuit or an analog circuit. Furthermore, if an integrated circuit technology that replaces the current integrated circuit emerges due to advances in semiconductor technology, one or more aspects of the present invention may use a new integrated circuit based on that technology.

Note that in the embodiments related to the present invention, an example has been described in which the present invention is applied to a communication system composed of a base station device and a terminal device. is also applicable.

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

Although the embodiments of the present invention have been described above in detail with reference to the drawings, the specific configuration is not limited to these embodiments, and may include design changes without departing from the gist of the present invention. Further, the present invention can be modified in various ways within the scope shown in the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments are also included within the technical scope of the present invention. It will be done. Also included are configurations in which the elements described in each of the above embodiments are replaced with each other and have similar effects.

The present invention can be used, for example, in a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), a program, etc. .

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

Claims (4)

1. A terminal device,
   a receiving unit that receives uplink configuration information in a system information block;
   a control unit that configures an initial uplink BWP using the uplink configuration information,
   The control unit includes:
   When the uplink configuration information includes first configuration information, setting the initial uplink BWP using bandwidth information indicated by the first configuration information,
   The uplink configuration information does not include the first configuration information, but includes second configuration information, and the bandwidth indicated by the second configuration information is less than or equal to the maximum bandwidth supported by the terminal device. If so, configure the initial uplink BWP using bandwidth information indicated by the second configuration information,
   If the uplink configuration information does not include the first configuration information and the second configuration information, the initial uplink configuration is performed using the bandwidth information indicated by the third configuration information included in the uplink configuration information. Terminal device for setting link BWP.
2. The receiving section includes:
   The terminal device according to claim 1, wherein the terminal device transmits an uplink channel using the set initial uplink BWP.
3. A base station device,
   a control unit that configures a first initial uplink BWP and generates uplink configuration information including first configuration information indicating a bandwidth of the first initial uplink BWP;
   a transmitter that transmits the uplink configuration information in a system information block,
   The control unit includes:
   When setting a second initial uplink BWP different from the first initial uplink BWP, the uplink configuration information includes second configuration information indicating a bandwidth of the second initial uplink BWP,
   When setting a third initial uplink BWP different from the first initial uplink BWP and the second initial uplink BWP, the bandwidth of the third initial uplink BWP is indicated in the uplink configuration information. A base station device that includes third configuration information.
4. A communication method for a terminal device, the method comprising:
   Receive uplink configuration information in the system information block,
   Setting an initial uplink BWP using the uplink configuration information,
   When the uplink configuration information includes first configuration information, setting the initial uplink BWP using bandwidth information indicated by the first configuration information,
   The uplink configuration information does not include the first configuration information, but includes second configuration information, and the bandwidth indicated by the second configuration information is less than or equal to the maximum bandwidth supported by the terminal device. If so, configure the initial uplink BWP using bandwidth information indicated by the second configuration information,
   If the uplink configuration information does not include the first configuration information and the second configuration information, the initial uplink configuration is performed using the bandwidth information indicated by the third configuration information included in the uplink configuration information. Communication method for setting link BWP.

Images