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

Description

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. 2020-162796, filed in Japan on September 29, 2020, the contents of which are incorporated herein by reference.

Currently, the Third Generation Partnership Project (3GPP) is conducting technical studies and formulating standards for LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) as radio access methods and wireless network technologies for the fifth-generation cellular system (Non-Patent Document 1).

In the fifth generation cellular system, three expected service scenarios are required: eMBB (enhanced Mobile BroadBand), which realizes high-speed and large-capacity transmission; URLLC (Ultra-Reliable and Low Latency Communication), which realizes low-latency and highly reliable communication; and mMTC (massive Machine Type Communication), which connects a large number of machine-type devices such as IoT (Internet of Things). Furthermore, in Release 17, a future release of NR, reduced capability (REDCAP) NR devices are being considered for use in sensor networks, surveillance cameras, and/or wearable devices, which do not require the high requirements of eMBB and URLLC, while at the same time reducing costs and extending battery life (Non-Patent Document 2).

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

The 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 such as the one described above.

(1) In order to achieve the above object, an embodiment of the present invention takes the following measures. That is, a terminal device in one embodiment of the present invention includes a receiving unit that receives a first system information block corresponding to a first cell, and a processing unit that determines whether the first cell is a restricted cell based on information in the first system information block, and the processing unit considers the first cell to be a restricted cell when the terminal device does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among multiple downlink BWP bandwidths set by the first system information block.

(2) In addition, a base station device in one embodiment of the present invention includes a processing unit that generates a first system information block including information for a terminal device to determine whether a first cell is a restricted cell, and a transmitting unit that transmits the first system information block, the information including information for setting multiple downlink BWPs, and the information causing the terminal device to consider the first cell to be a restricted cell when the terminal device does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the multiple downlink BWPs.

(3) Also, a communication method in one embodiment of the present invention is a communication method of a terminal device, which receives a first system information block corresponding to a first cell, and considers the first cell to be a restricted cell if the terminal device does not support a downlink channel bandwidth that is the same as or wider than the widest bandwidth among multiple downlink BWP bandwidths set by the first system information block.

(4) Also, a communication method in one embodiment of the present invention is a communication method of a base station device, in which a terminal device generates a first system information block including information for determining whether a first cell is a restricted cell and transmits the first system information block, the information including information for setting multiple downlink BWPs, and the information causing the terminal device to consider the first cell to be a restricted cell if the terminal device does not support a downlink channel bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the multiple downlink BWPs.

According to one aspect of the present 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. A figure showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. FIG. 2 is a diagram showing the relationship between subframes, slots, and minislots in the time domain according to an embodiment of the present invention. A figure showing an example of the configuration of an RRC parameter PDCCH-ConfigSIB1-RC, which is information indicating settings related to a PDCCH for a REDCAP SIB1 according to an embodiment of the present invention. FIG. 13 is a diagram illustrating an example of a table to which the value of controlResourceSetZero is applied as an index according to an embodiment of the present invention. FIG. 13 is a diagram illustrating an example of a table to which the value of searchSpaceZero is applied as an index according to an embodiment of the present invention. A figure showing an example of a table of indexes indicated by a 2-bit parameter PDCCH-repetitions in a REDCAP MIB according to an embodiment of the present invention and the number of repeated transmissions of PDCCH. A figure showing an example of an SS/PBCH block and SS burst set for an embodiment of the present invention. FIG. 2 illustrates an example of a REDCAP PBCH block and a half-frame in which one or more REDCAP PBCH blocks are transmitted according to an embodiment of the present invention. A diagram showing resources in which a PSS, an SSS, a PBCH and a DMRS for a PBCH are arranged within an SS/PBCH block according to an embodiment of the present invention. FIG. 2 illustrates an example of a REDCAP PBCH block and a half-frame in which one or more REDCAP PBCH blocks are transmitted according to an embodiment of the present invention. FIG. 2 is a diagram showing resources in which a REDCAP PBCH and a DMRS for the REDCAP PBCH are arranged within a REDCAP PBCH block according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of a REDCAP PBCH block according to an embodiment of the present invention. FIG. 13 is a diagram illustrating another example of a REDCAP PBCH block according to an embodiment of the present invention. A figure showing an example of downlink transmission using multiple initial downlink sub-BWPs according to an embodiment of the present invention. FIG. 11 is a flow diagram showing an example of a process of determining a restricted cell based on a plurality of initial downlink sub-BWPs in a terminal device 1 according to an embodiment of the present invention. FIG. 11 is a flow diagram showing an example of a process of determining a restricted cell based on a plurality of initial uplink sub-BWPs in a terminal device 1 according to an embodiment of the present invention. FIG. 2 is a diagram illustrating an example of beamforming according to an embodiment of the present invention. 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an embodiment of the present invention. 1 is a schematic block diagram showing a configuration of a base station device 3 according to an embodiment of the present invention.

The following describes an embodiment of the present invention.

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

The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). 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 is also referred to as a radio base station device, a base station, a radio base station, a fixed station, a NB (Node B), an eNB (evolved Node B), a BTS (Base Transceiver Station), a BS (Base Station), an NR NB (NR Node B), an NNB, a TRP (Transmission and Reception Point), or a gNB. The base station device 3 may include a core network device. The base station device 3 may also have one or more transmission and reception points 4. At least some of the functions/processing of the base station device 3 described below may be functions/processing at each transmission and reception point 4 of the base station device 3. The base station device 3 may serve the terminal device 1 with a communication range (communication area) controlled by the base station device 3 as one or more cells. Furthermore, the base station device 3 may serve the terminal device 1 as one or more cells, which are communication ranges (communication areas) controlled by one or more transmission/reception points 4. Furthermore, the base station device 3 may divide one cell into multiple partial areas (beamed areas) and serve the terminal device 1 in each partial area. Here, the partial area may be identified based on the index of the beam used in beamforming or the index of precoding.

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 FIG. 1, wireless communication between terminal device 1 and base station device 3 may use orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), discrete Fourier transform spread OFDM (DFT-S-OFDM), or multi-carrier code division multiplexing (MC-CDM).

In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 may use Universal Filtered Multi-Carrier (UFMC), Filtered OFDM (F-OFDM), OFDM multiplied by a window function (Windowed OFDM), or Filter-Bank Multi-Carrier (FBMC).

In this embodiment, OFDM is used as the transmission method and is described using OFDM symbols, but the use of the other transmission methods mentioned above is also included in one aspect of the present invention.

In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 may use the above-mentioned transmission method without using a CP or with zero padding instead of a CP. Also, a CP or zero padding may be added to both the front and back.

An aspect of the present embodiment may be operated in carrier aggregation or dual connectivity with radio access technologies (RATs) such as LTE and LTE-A/LTE-A Pro. In this case, some or all of the cells or cell groups, carriers or carrier groups (e.g., primary cell (PCell), secondary cell (SCell), primary secondary cell (PSCell), MCG (Master Cell Group), SCG (Secondary Cell Group), etc.) may be used. Also, an aspect of the present embodiment may be used in standalone operation. In dual connectivity operation, the SpCell (Special Cell) is referred to as the PCell of the MCG or the PSCell of the SCG depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG, respectively. If not in dual connectivity operation, the SpCell (Special Cell) is referred to as the PCell. The SpCell (Special Cell) supports PUCCH transmission and contention-based random access.

In this embodiment, one or more serving cells may be configured for the terminal device 1. The configured multiple serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell where an initial connection establishment procedure has been performed, a serving cell where a connection re-establishment procedure has been started, or a cell designated as a primary cell in a handover procedure. One or more secondary cells may be configured at the time when an RRC (Radio Resource Control) connection is established or after. However, the configured multiple serving cells may include one primary secondary cell. The primary secondary cell may be a secondary cell capable of transmitting control information in the uplink among one or more secondary cells where the terminal device 1 is configured. In addition, two types of subsets of serving cells, a master cell group and a secondary cell group, may be configured for the terminal device 1. The master cell group may be composed of one primary cell and zero or more secondary cells. The secondary cell group may be composed of one primary secondary cell and zero or more secondary cells.

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

The following describes subframes. In this embodiment, the following is referred to as a subframe, but the subframe in this embodiment may also be referred to as a resource unit, radio frame, time period, time interval, etc.

Figure 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 10 ms long. Each radio frame is composed of 10 subframes and W slots. One slot is composed of X OFDM symbols. That is, one subframe has a length of 1 ms. Each slot has a time length defined by the subcarrier interval. For example, when the subcarrier interval of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X=7 or X=14, which are 0.5 ms and 1 ms, respectively. When the subcarrier interval is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. When X=14, for example, when the subcarrier interval is 15 kHz, W=10, and when the subcarrier interval is 60 kHz, W=40. Figure 2 shows the case of X=7 as an example. Note that the example of Figure 2 can be similarly extended to the case of X=14. Also, the uplink slot may be defined similarly, and the downlink slot and the uplink slot may be defined separately. Also, the bandwidth of the cell in FIG. 2 may be defined as a part of the band (BWP: BandWidth Part). Also, the slot may be defined as a transmission time interval (TTI: Transmission Time Interval). The slot may not be defined as a TTI. The TTI may be a transmission period of a transport block.

The signals or physical channels transmitted in each slot may be represented by a resource grid. The resource grid is defined by a number of subcarriers and a number of 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 called a resource element. A resource element may be identified by the subcarrier number and the OFDM symbol number.

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

As resource blocks (RB), reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined. One resource block is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may be numbered in ascending order, for example, constituting a resource block at a subcarrier interval of 15 kHz. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or simply referred to as a "reference point"). The common resource block is a resource block numbered in ascending order from 0 at each subcarrier interval setting μ from reference point A. The above-mentioned resource grid is defined by this common resource block. The physical resource block is a resource block numbered in ascending order from 0 included in a band part (BWP: BandWidth Part) described later, and the physical resource block is a resource block numbered in ascending order from 0 included in the BWP. A certain physical uplink channel is first mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. Hereinafter, a resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

Next, we explain the subcarrier spacing setting μ. As mentioned above, NR supports one or more OFDM numerologies. For a given BWP, the subcarrier spacing setting μ (μ=0,1,...,5) and the cyclic prefix length are given by higher layers for the downlink BWP and by higher layers for the uplink BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf=2^μ・15 (kHz).

For subcarrier spacing setting μ, slots are numbered from 0 to N^{subframe,μ}_{slot}-1 in ascending order within a subframe and from 0 to N^{frame,μ}_{slot}-1 in ascending order within a frame. Based on the slot setting and cyclic prefix, there are N^{slot}_{symb} consecutive OFDM symbols in a slot, where N^{slot}_{symb} is 14. The start of slot n^{μ}_{s} in a subframe is aligned in time with the start of the n^{μ}_{s}*N^{slot}_{symb}th OFDM symbol in the same subframe.

Next, subframes, slots, and minislots are described. Figure 3 shows an example of the relationship between 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 spacing, the number of OFDM symbols included in a slot is 7 or 14 (however, if the cyclic prefix (CP) added to each symbol is Extended CP, it may be 6 or 12), and the slot length differs depending on the subcarrier spacing. Here, when the subcarrier spacing 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 (which may also be called a subslot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols contained in one slot. The figure shows an example in which a minislot is composed of two OFDM symbols. The OFDM symbols in a minislot may coincide with the OFDM symbol timing that constitutes the slot. The smallest unit of scheduling may be a slot or a minislot. Allocating a minislot may also be called non-slot-based scheduling. Scheduling a minislot may also be expressed as scheduling a resource in which the relative time positions of the start positions of the reference signal and data are fixed. A downlink minislot may be called PDSCH mapping type B. An uplink minislot may be called PUSCH mapping type B.

In the terminal device 1, the transmission direction (uplink, downlink or flexible) of the symbol in each slot is set in the higher layer using an RRC message including predetermined higher layer parameters received from the base station device 3, or is set by the PDCCH of a specific DCI format (e.g. DCI format 2_0) received from the base station device 3. In this embodiment, a slot format that sets each symbol in a slot to either uplink, downlink or flexible is called a slot format. One slot format may include a downlink symbol, an uplink symbol and a flexible symbol.

In the downlink of this embodiment, the carrier corresponding to the serving cell is referred to as the downlink component carrier (or downlink carrier). In the uplink of this embodiment, the carrier corresponding to the serving cell is referred to as the uplink component carrier (or uplink carrier). In the sidelink of this embodiment, the carrier corresponding to the serving cell is referred to as the sidelink component carrier (or sidelink carrier). The downlink component carrier, the uplink component carrier, and/or the sidelink component carrier are collectively referred to as the component carrier (or carrier).

The physical channels and physical signals of this embodiment are described below.

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

・PBCH (Physical Broadcast CHannel)
- REDCAP PBCH (REDuction CAPability Physical Broadcast Channel, R-PBCH)
・PDCCH (Physical Downlink Control CHannel)
・PDSCH (Physical Downlink Shared CHannel)
・PUCCH (Physical Uplink Control CHannel)
・PUSCH (Physical Uplink Shared CHannel)
・PRACH (Physical Random Access CHannel)

The PBCH is used to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1. The MIB may include information for identifying the number (SFN: System Frame Number) of the radio frame (also referred to as the system frame) to which the PBCH is mapped, information for identifying the subcarrier spacing of the system information block 1 (SIB1: System Information Block 1), information indicating the frequency domain offset between the grid of resource blocks and the SS/PBCH block (also referred to as the synchronization signal block, SS block, SSB), and information indicating the setting of the PDCCH for SIB1. However, SIB1 includes information required when evaluating whether the terminal device 1 is allowed to connect to the cell, and includes information for determining the scheduling of other system information (SIB: System Information Block). However, the information indicating the setting of the PDCCH for SIB1 may be information for determining the CORESET (Control Resource Set) 0 (also referred to as the common CORESET), the common search space, and/or the required PDCCH parameters. where CORESET indicates resource elements of a PDCCH, and CORESET0 is the CORESET for the PDCCH that schedules SIB1.

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

The PBCH may also be used to broadcast a time index within a period of the SS/PBCH block. Here, the time index is information indicating the index of the synchronization signal and the 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 an SS/PBCH block using Quasi Co-Location (QCL) assumptions regarding multiple transmit beams, transmit filter settings, and/or receive spatial parameters, the time order within a predetermined period or within a set period may be indicated. Furthermore, the terminal device may recognize the difference in time index as a difference in the QCL assumptions regarding the transmit beam, transmit filter settings, and/or receive spatial parameters.

The REDCAP PBCH is used to notify the REDCAP important information block (also referred to as REDCAP MIB, REDCAP EIB, REDCAP BCH, R-MIB) including important system information required by the terminal device 1. However, the REDCAP MIB may be used only for terminal devices 1 that satisfy certain conditions (for example, UE Capability and/or UE Category, etc., indicating certain parameters). However, the REDCAP MIB may include information for identifying the SFN to which the REDCAP PBCH is mapped or information for identifying the SFN to which the SS/PBCH block corresponding to the REDCAP PBCH is mapped, information for identifying the subcarrier spacing of the REDCAP system information block 1 (REDCAP SIB1, also referred to as R-SIB1), information indicating the frequency domain offset between the grid of resource blocks and the SS/PBCH block (also referred to as the synchronization signal block, SS block, SSB), and information indicating the settings regarding the PDCCH for the REDCAP SIB1. However, the REDCAP SIB1 includes information necessary for evaluating whether the terminal device 1 is permitted to connect to a cell, and includes information for determining the scheduling of other REDCAP system information blocks (REDCAP SIB, also referred to as R-SIB). However, the REDCAP SIB1 includes information necessary for evaluating whether the terminal device 1 that satisfies a specific condition (for example, indicates a specific parameter such as UE Capability and/or UE Category) is permitted to connect to a cell, and may include information for determining the scheduling of other REDCAP SIBs. However, some or all of the information included in the REDCAP MIB may be the same as some or all of the information included in the MIB broadcasted by the PBCH. For example, the above REDCAP SIB1 may be SIB1. However, some or all of the information in the REDCAP MIB may be broadcasted by the PBCH. However, the REDCAP PBCH may broadcast the MIB. For example, the REDCAP MIB included in the information transmitted by the REDCAP PBCH may be the same as the MIB included in the information transmitted by the PBCH included in the SS/PBCH block to which the REDCAP PBCH is associated. However, the MIB-related processing described below may be similarly applied to the REDCAP MIB-related processing.

The information transmitted on the REDCAP PBCH may also include information specifying the number of a radio frame to which the REDCAP PBCH is mapped and/or information specifying a half radio frame. However, the information transmitted on the REDCAP PBCH may also include information specifying the number of a radio frame to which an associated PSS and/or SSS is mapped and/or information specifying a half radio frame. However, the information transmitted on the REDCAP PBCH may also include information specifying the number of a radio frame to which an associated SS/PBCH block is mapped and/or information specifying a half radio frame.

The information transmitted in the REDCAP PBCH may also include a time index within the period of the associated SS/PBCH block. The time index may be referred to as an SSB index or an SS/PBCH block index. For example, when the base station device 3 transmits SS/PBCH blocks using QCL assumptions regarding multiple transmit beams, transmit filter settings, and/or receive spatial parameters, the time order within a predetermined period or a set period may be indicated. The terminal device 1 may also recognize the difference in time index as a difference in QCL assumptions regarding the transmit beam, transmit filter settings, and/or receive spatial parameters. The information transmitted in the REDCAP PBCH may also include a time index of the REDCAP PBCH.

The information indicating the configuration regarding the PDCCH for the REDCAP SIB1 transmitted on the REDCAP PBCH may be information determining the CORESET0, the common search space, and/or the required PDCCH parameters for the PDCCH that schedules the REDCAP SIB1. However, the information regarding the CORESET0, the common search space, and/or the required PDCCH parameters indicated in the REDCAP MIB may be the same as the information regarding the CORESET0, the common search space, and/or the required PDCCH parameters indicated in the MIB.

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

The terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET0 from controlResourceSetZero in PDCCH-ConfigSIB1-RC. However, the value indicated by controlResourceSetZero is applied as an index to a predetermined table. However, the terminal device 1 may determine the table to be applied based on the supported UE category and/or UE capability. However, the terminal device 1 may determine the table to be applied based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier spacing of the SS/PBCH block, the subcarrier spacing of the REDCAP PBCH and/or the subcarrier spacing of CORESET0. Figure 5 shows an example of a table to which the value of controlResourceSetZero is applied as an index. As shown in the table in FIG. 5, each row of the table to which the value of controlResourceSetZero is applied as an index may indicate the index indicated by controlResourceSetZero, the multiplexing pattern of REDCAP PBCH and CORESET, the number of RBs (which may be PRBs) of CORESET0, the number of symbols of CORESET0, an offset and/or the number of repetitions of PDCCH.

The multiplexing pattern of REDCAP PBCH and CORESET indicates the pattern of the relationship between the frequency/time position of the REDCAP PBCH that detected the REDCAP MIB and the corresponding CORESET0. For example, when the multiplexing pattern of REDCAP PBCH and CORESET is 1, the REDCAP PBCH and CORESET are time-multiplexed into different symbols. However, the multiplexing pattern of REDCAP PBCH and CORESET may also indicate the pattern of the relationship between the SS/PBCH block corresponding to the REDCAP PBCH that detected the REDCAP MIB and the frequency/time position of CORESET0. However, the multiplexing pattern of REDCAP PBCH and CORESET is not defined in a table and may always be a fixed pattern (e.g., pattern 1).

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

The offset indicates the offset from the smallest RB index of the resource blocks assigned to CORESET0 to the smallest RB index of the common resource block that overlaps with the first resource block of the corresponding REDCAP PBCH. However, the offset may also indicate the offset from the smallest RB index of the resource blocks assigned to CORESET0 to the smallest RB index of the common resource block that overlaps with the first resource block of the SS/PBCH block corresponding to the REDCAP PBCH.

The number of PDCCH repetitions indicates the number of times the PDCCH that schedules REDCAP SIB1 is repeatedly transmitted. If the number of PDCCH repetitions shown in the table is greater than 1, the terminal device 1 assumes that the PDCCH that schedules REDCAP SIB1 is repeatedly transmitted.

The terminal device 1 receives a REDCAP MIB including the RRC parameter controlResourceSetZero via the REDCAP PBCH, and monitors the PDCCH indicating scheduling information of REDCAP SIB1 based on the controlResourceSetZero and a table indicating the index, the multiplexing pattern of REDCAP PBCH and CORESET, the number of RBs of CORESET0, the number of symbols of CORESET0, the offset and/or the number of repetitions of PDCCH.

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

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

However, if a field in the REDCAP MIB indicates that a REDCAP SIB1 is absent, the information indicating the settings regarding the PDCCH for the REDCAP SIB1 transmitted on the REDCAP PBCH may indicate the frequency location where the terminal device 1 finds the REDCAP PBCH with REDCAP SIB1 and/or the corresponding SS/PBCH block or the frequency range where the network does not provide the REDCAP PBCH with REDCAP SIB1 and/or the corresponding SS/PBCH block.

The information transmitted in the REDCAP PBCH may also include a field PDCCH-repetitions indicating the number of repetitions of the PDCCH that schedules the REDCAP SIB1. For example, the number of repetitions of the PDCCH may be indicated by two bits in the REDCAP MIB. FIG. 7 is a diagram showing an example of a table of indexes indicated by the two-bit parameter PDCCH-repetitions in the REDCAP MIB and the number of repetitions of the PDCCH. In the table of FIG. 7, indexes 0, 1, 2, and 3 indicated in the REDCAP MIB correspond to the number of repetitions of the PDCCH, N/A, 1, 2, and 4, respectively. However, the value of the number of repetitions of the PDCCH may indicate that the PDCCH and/or the REDCCAP SIB1 that schedules the REDCAP SIB1 have not been transmitted. In this case, when the index indicated by the two bits in the REDCAP MIB is 0, the terminal device 1 considers that the PDCCH and/or the REDCCAP SIB1 that schedules the REDCAP SIB1 have not been transmitted. However, a value of N/A for the PDCCH repetition transmission count may indicate that the cell is barred.

The terminal device 1 receives a REDCAP MIB including the RRC parameter PDCCH-repetitions via the REDCAP PBCH, determines the number of times to repeat transmission of the PDCCH indicating the scheduling information of the REDCAP SIB1 based on the PDCCH-repetitions, and assumes that the PDCCH is not being transmitted if the PDCCH-repetitions is a predetermined value.

The PDCCH is used to transmit (or carry) downlink control information (DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (which may be referred to as DCI formats) are defined for the transmission of downlink control information. That is, a field for the downlink control information is defined as DCI and mapped to information bits. The PDCCH is transmitted in 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 formats may be defined:
・DCI Format 0_0
・DCI format 0_1
・DCI format 0_2
・DCI Format 1_0
・DCI Format 1_1
・DCI Format 1_2
・DCI Format 2_0
DCI Format 2_1
DCI Format 2_2
DCI Format 2_3

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

DCI format 0_1 may be used for scheduling PUSCH in a serving cell. DCI format 0_1 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, a Channel State Information (CSI) request, a Sounding Reference Signal (SRS) request, and/or information regarding antenna ports. DCI format 0_1 may be added with a CRC scrambled by any of the C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and/or MCS-C-RNTI among RNTIs. DCI format 0_1 may be monitored in a UE-specific search space.

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

DCI format 1_0 may be used for scheduling PDSCH in a serving cell. DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation). DCI format 1_0 may be added with a CRC scrambled by any of 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. DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

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

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

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

DCI format 2_1 is used to notify the terminal device 1 of the physical resource blocks (PRBs or RBs) and OFDM symbols for which no transmission may be assumed. This information may be referred to as a preemption instruction (discontinuous 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. An SRS request may also be transmitted together with the TPC command. DCI format 2_3 may also define an SRS request and a TPC command for an uplink without PUSCH and PUCCH, or for an uplink where the transmission power control of SRS is not linked to the transmission power control of PUSCH.

DCI for the downlink is also referred to as a downlink grant or a downlink assignment. Here, DCI for the uplink is also referred to as an uplink grant or an uplink assignment. DCI may also be referred to as a 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 notifying 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 a random access preamble during a contention based random access procedure.

The C-RNTI is used to control the PDSCH or PUSCH in one or more slots. The CS-RNTI is used to periodically allocate resources for the PDSCH or PUSCH. The MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission. The TC-RNTI is used to control the PDSCH or PUSCH transmission in one or more slots. The TC-RNTI is used to schedule retransmissions of the random access message 3 and the transmission of the random access message 4. The 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 traffic on the PDSCH or PUSCH. Different values may be used for the C-RNTI and other RNTIs depending on the service type (eMBB, URLLC, and/or mMTC) of the data transmitted on the PDSCH or PUSCH. The base station device 3 may use different values of RNTI depending on the service type of the data to be transmitted. The terminal device 1 may identify the service type of the data transmitted on the associated PDSCH or PUSCH depending on 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 terminal device 1 to base station device 3). Here, the uplink control information may include channel state information (CSI) used to indicate the state of the downlink channel. The uplink control information may also include a scheduling request (SR) used to request UL-SCH resources. The uplink control information may also include a hybrid automatic repeat request ACKnowledgement (HARQ-ACK). The HARQ-ACK may indicate a 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. In the downlink, the PDSCH is also used to transmit System Information (SI) and Random Access Response (RAR), etc.

The PUSCH may be used to transmit uplink data from the MAC layer (UL-SCH: Uplink Shared CHannel) or HARQ-ACK and/or CSI together with uplink data. The PUSCH may also be used to transmit only CSI, or only HARQ-ACK and CSI. That is, the 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 an RRC message (also referred to as an RRC message, RRC information, or RRC signaling) in the Radio Resource Control (RRC) layer. The base station device 3 and the terminal device 1 may also transmit and receive a MAC control element in the Medium Access Control (MAC) layer. The RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3. Here, the RRC message, the system information, and/or the MAC control element are also referred to as a higher layer signal (higher layer signaling) or a higher layer parameter (higher layer parameter). Each of the parameters included in the higher layer signal received by the terminal device 1 may be referred to as a higher layer parameter. The upper layer here means an upper layer seen from the physical layer, and may include one or more of the MAC layer, the RRC layer, the RLC layer, the PDCP layer, the NAS (Non Access Stratum) layer, etc. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, the RLC layer, the PDCP layer, the NAS layer, etc. Hereinafter, the meaning of "A is given (provided) by the upper layer" or "A is given (provided) by the upper layer" may mean that the upper layer (mainly the RRC layer or the MAC layer, etc.) of the terminal device 1 receives A from the base station device 3, and the received A is given (provided) to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. For example, in the terminal device 1, "upper layer parameters are provided" may mean that the upper layer signal is received from the base station device 3, and the upper layer parameters included in the received upper layer signal are provided to the physical layer of the terminal device 1 from the upper layer of the terminal device 1. Setting the 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 an upper layer parameter 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 parameter in an upper layer. However, setting an upper layer parameter in the terminal device 1 may also include setting a default parameter that is given in advance to the upper layer of the terminal device 1.

The PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. The RRC signaling transmitted from the base station device 3 by the PDSCH may be common signaling for multiple terminal devices 1 in the cell. Furthermore, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also called dedicated signaling) for a certain terminal device 1. In other words, terminal device-specific (UE-specific) information may be transmitted using dedicated signaling for a certain terminal device 1. Furthermore, the PUSCH may be used to transmit UE capabilities in the uplink.

In Fig. 1, the following downlink physical signals are used in downlink wireless communication: Here, the downlink physical signals are not used to transmit information output from higher layers, but are used by the physical layer.
・Synchronization signal (SS)
・Reference Signal (RS)

The synchronization signals may include a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The PSS and SSS may be used to detect the cell ID.

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

The reference signal is used by the terminal device 1 to perform propagation path compensation of the physical channel. Here, the reference signal may also be used by the terminal device 1 to calculate the downlink CSI. In addition, the reference signal may be used for fine synchronization to the extent that numerology such as radio parameters and subcarrier spacing and FFT window synchronization can be performed.

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 modulated signals. 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 measuring channel state information (CSI) and beam management, and applies a periodic, semi-persistent, or aperiodic CSI reference signal transmission method. For CSI-RS, non-zero power (NZP) CSI-RS and zero power (ZP) CSI-RS with zero transmission power (or zero reception power) may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or no transmission. PTRS is used to track the phase on the time axis for the purpose of compensating for frequency offset caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. Note that TRS may be used as one setting of CSI-RS. For example, radio resources may be configured as TRS for one-port CSI-RS.

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

DMRS is used to demodulate modulated signals. Two types of DMRS may be defined: a reference signal for demodulating PUCCH and a reference signal for demodulating PUSCH, and both may be called DMRS. SRS is used for measuring uplink channel state information (CSI), channel sounding, and beam management. PTRS is used to track phase in time to compensate for frequency offsets caused by phase noise.

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

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

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

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

The base station device 3 according to the present embodiment transmits the REDCAP PBCH and the DMRS for the REDCAP PBCH with time resources and/or frequency resources different from the SS/PBCH block. However, in the present embodiment, transmitting/receiving/processing the REDCAP PBCH may be transmitting/receiving/processing the REDCAP PBCH and the DMRS for the REDCAP PBCH. A block including the REDCAP PBCH and the DMRS for the REDCAP PBCH may be referred to as a REDCAP PBCH block. However, transmitting a signal/channel included in a REDCAP PBCH block may be expressed as transmitting a REDCAP PBCH block. When transmitting the REDCAP PBCH using one or more REDCAP PBCH blocks within a predetermined time period (which may be referred to as a REDCAP PBCH burst set), the base station device 3 may use an independent downlink transmission beam for each REDCAP PBCH block. However, the REDCAP PBCH block according to the present embodiment may be the REDCAP PBCH and/or the DMRS for the REDCAP PBCH itself. For example, transmitting/receiving/processing a REDCAP PBCH block may be transmitting/receiving/processing a REDCAP PBCH and/or a DMRS for the REDCAP PBCH. However, the DMRS for the REDCAP PBCH and/or the REDCAP PBCH according to this embodiment may be a DMRS for the REDCAP PBCH and/or the REDCAP PBCH transmitted in a location other than the SS/PBCH block. For example, the DMRS for the REDCAP PBCH and/or the REDCAP PBCH may be a DMRS for the REDCAP PBCH and/or the REDCAP PBCH transmitted in a time and/or frequency resource different from the SS/PBCH block periodically transmitted in an SSB period. However, the REDCAP PBCH block according to this embodiment may be an SS/PBCH block without a PSS and/or an SSS.

In this embodiment, the REDCAP PBCH block and/or the REDCAP PBCH is associated with one SS/PBCH block transmitted in an SS burst set (Half frame with SS/PBCH block). The transport block transmitted in the REDCAP PBCH and the transport block transmitted in the PBCH in the corresponding SS/PBCH block may be the same.

Figure 9 is a diagram showing an example of a REDCAP PBCH block according to this embodiment and a half frame (which may be referred to as a Half frame with REDCAP PBCH block or a REDCAP PBCH burst set) in which one or more REDCAP PBCH blocks are transmitted. Figure 9 shows an example in which two REDCAP PBCH blocks are included in a REDCAP PBCH burst set that exists at a constant period (which may be referred to as an SSB period), and the REDCAP PBCH block is composed of four consecutive OFDM symbols. In the REDCAP PBCH block, a REDCAP PBCH modulation symbol and a DMRS for the REDCAP PBCH are frequency-multiplexed in each OFDM symbol.

However, a block including a synchronization signal (PSS, SSS), a REDCAP PBCH, and a DMRS for the REDCAP PBCH may be defined as a separate block, distinct from the SS/PBCH block. For example, a block including a synchronization signal (PSS, SSS), a REDCAP PBCH, and a DMRS for the REDCAP PBCH may be referred to as a REDCAP SS/PBCH block, a REDCAP synchronization signal block, a REDCAP SS block, or a REDCAP SSB. However, the description of the REDCAP SS/PBCH block according to this embodiment may also be applied to the REDCAP SS/PBCH block.

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

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

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

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

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

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

An 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 contained in the detected SS/PBCH block.

SS/PBCH blocks with the same relative time within each SS burst set in the 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 the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS/PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

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

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

In this embodiment, the REDCAP PBCH is transmitted in an OFDM symbol associated with the corresponding SS/PBCH block or the corresponding synchronization signal (PSS, SSS).

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

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

Fig. 11 is a diagram showing an example of a half frame in which a REDCAP PBCH block according to the present embodiment and one or more REDCAP PBCH blocks are transmitted. Fig. 11 shows an example in which a half frame including a REDCAP PBCH block exists between half frames including SS/PBCH blocks that exist at a constant period (SSB period), and the REDCAP PBCH block is composed of three consecutive OFDM symbols. The REDCAP PBCH block is transmitted using resources corresponding to one SS/PBCH block, and the REDCAP PBCH or the DMRS for the REDCAP PBCH exists in all resources in the REDCAP PBCH block. Fig. 12 is a table showing an example of resources in which the REDCAP PBCH and the DMRS for the REDCAP PBCH are arranged in the REDCAP PBCH block. For example, the sequence of modulation symbols for the REDCAP PBCH is composed of M _symb2 symbols, and may be mapped to resources in which the DMRS for the REDCAP PBCH is not mapped among the 1st subcarrier to the 240th subcarrier (subcarriers with subcarrier numbers from 0 to 239 with respect to the start subcarrier of the REDCAP PBCH block) of each of the three symbols in the REDCAP PBCH block. The sequence of symbols for the DMRS for the REDCAP PBCH is composed of 180 symbols, and may be mapped to one subcarrier for every four subcarriers among the 1st subcarrier to the 240th subcarrier (subcarriers with subcarrier numbers from 0 to 239 with respect to the start subcarrier of the REDCAP PBCH block). However, the number of symbols constituting the REDCAP PBCH block does not have to be three symbols. For example, the REDCAP PBCH block is composed of four symbols, and the REDCAP PBCH or the DMRS for the REDCAP PBCH may exist for the 240 subcarriers of each symbol. However, the number of subcarriers constituting the REDCAP PBCH block does not have to be 240 subcarriers. For example, a REDCAP PBCH block is composed of 180 subcarriers and 4 OFDM symbols, and a REDCAP PBCH or a DMRS for the REDCAP PBCH may exist for the 180 subcarriers of each symbol.

FIG. 13 is a diagram showing an example of a REDCAP PBCH block according to the present embodiment. FIG. 13 shows an example in which a REDCAP PBCH block exists in a half frame including an SS/PBCH block that exists at a constant period (SSB period), and the REDCAP PBCH block is composed of four consecutive OFDM symbols. The REDCAP PBCH block is transmitted using a resource corresponding to one SS/PBCH block, and the REDCAP PBCH or the DMRS for the REDCAP PBCH exists in all resources in the REDCAP PBCH block. For example, the sequence of modulation symbols of the REDCAP PBCH is composed of M _symb2 symbols, and may be mapped to resources in which the DMRS for the REDCAP PBCH is not mapped among the 1st subcarrier to the 240th subcarrier (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block) of each of the four symbols in the REDCAP PBCH block. The symbol sequence of the DMRS for the REDCAP PBCH may be composed of 240 symbols and may be mapped to the 1st to 240th subcarriers (subcarriers with subcarrier numbers from 0 to 239 relative to the start subcarrier of the REDCAP PBCH block) of the four symbols in the REDCAP PBCH block, one subcarrier at a time for every four subcarriers. However, the REDCAP PBCH or the DMRS for the REDCAP PBCH may not exist for all resources in the REDCAP PBCH block. For example, the REDCAP PBCH block may be composed of four symbols, one of which may be set to 0.

FIG. 14 is a diagram showing another example of a REDCAP PBCH block according to the present embodiment. FIG. 14 shows an example in which a REDCAP PBCH block exists in some slots in a half frame including an SS/PBCH block that exists at a constant period (SSB period), and the REDCAP PBCH block is composed of four consecutive OFDM symbols. However, the slot in which the REDCAP PBCH block is arranged may be a slot that does not include a candidate resource for the SS/PBCH block. The REDCAP PBCH block is transmitted in a resource corresponding to one SS/PBCH block, and the REDCAP PBCH or the DMRS for the REDCAP PBCH exists in all resources in the REDCAP PBCH block. For example, the sequence of modulation symbols of the REDCAP PBCH is composed of M _symb2 symbols, and may be mapped to a resource in which the DMRS for the REDCAP PBCH is not mapped, among the 1st subcarrier to the 240th subcarrier (subcarriers with subcarrier numbers 0 to 239 with respect to the start subcarrier of the REDCAP PBCH block) of each of the four symbols in the REDCAP PBCH block. The symbol sequence of the DMRS for the REDCAP PBCH may be composed of 240 symbols, and may be mapped to the 1st to 240th subcarriers (subcarriers with subcarrier numbers from 0 to 239 relative to the start subcarrier of the REDCAP PBCH block) of the four symbols in the REDCAP PBCH block, one subcarrier at a time for every four subcarriers. However, the REDCAP PBCH or the DMRS for the REDCAP PBCH may not exist for all resources in the REDCAP PBCH block. For example, the REDCAP PBCH block may be composed of four symbols, one of which may be set to 0, and the REDCAP PBCH and the DMRS for the REDCAP PBCH may exist in the remaining three symbols.

One or more REDCAP PBCH blocks in a half frame (REDCAP PBCH burst set) including a REDCAP PBCH may be assigned different SSB indices. A REDCAP PBCH block assigned a certain SSB index may be associated with the SS/PBCH block of that SSB index and transmitted periodically by the base station device 3. However, there may be multiple REDCAP PBCH blocks assigned the same SSB index for one SS/PBCH block. For example, REDCAP PBCH blocks assigned the same SSB index may be transmitted multiple times within an SSB period.

The time position of the half frame to which the REDCAP PBCH block is mapped may be determined based on information identifying the SFN and/or information identifying the half frame included in the PBCH of the corresponding SS/PBCH block and/or the REDCAP PBCH of the REDCAP PBCH block, and the time offset between the corresponding SS/PBCH block and the REDCAP PBCH block. However, the information identifying the SFN and/or information identifying the half frame included in the REDCAP PBCH of the REDCAP PBCH block may be information identifying the SFN and half frame in which the corresponding SS/PBCH block is transmitted. The terminal device 1 that has received the REDCAP PBCH block may determine the SFN and half frame in which the corresponding SS/PBCH block is transmitted based on the received REDCAP PBCH block.

REDCAP PBCH blocks are assigned SSB indices according to their time positions within the transmitted half frame. The terminal device 1 identifies the SSB index based on the REDCAP PBCH information and/or reference signal information contained in the detected REDCAP PBCH block.

SS/PBCH blocks with the same relative time within each SS burst set in the 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 the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS/PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

Within a period of an SS burst set, SS/PBCH blocks and REDCAP PBCH blocks 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 terminal device 1 according to this embodiment receives the PSS and SSS in the SS/PBCH block, and receives the PBCH in the SS/PBCH block and/or one or more REDCAP PBCHs corresponding to the SS/PBCH block. By receiving one or more REDCAP PBCHs, the terminal device 1 can improve the detection accuracy of the MIB or REDCAP MIB, and can expand the cell coverage in which the terminal device 1 can receive the MIB or REDCAP MIB. However, the terminal device 1 that receives the REDCAP PBCH may be only a terminal device 1 having a predetermined capability. For example, a terminal device 1 having a limited capability for the purpose of reducing the cost and/or power consumption of the device is referred to as being compatible with REDCAP (Reduction Capability), and the terminal device 1 compatible with REDCAP may receive the SS/PBCH block and/or the REDCAP PBCH, and the terminal device 1 that does not support REDCAP may receive only the SS/PBCH block and not receive the REDCAP PBCH block.

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

The terminal device 1 in this embodiment may receive an SS/PBCH block to which PSS, SSS, PBCH and DMRS for PBCH are mapped in a certain radio frame, receive a REDCAP PBCH and DMRS for REDCAP PBCH in the same or different radio frame as the certain radio frame, and acquire the MIB of the transport block transmitted on the PBCH and REDCAP PBCH.

The terminal device 1 according to this embodiment determines whether to consider a certain cell as a "barred" cell based on the connection state, the execution state of a predetermined timer, information in a received MIB (which may be a REDCAP MIB), and/or information in a received SIB (which may be a REDCAP SIB, SIB1, or REDCAP SIB1). However, a barred cell may be a cell on which the terminal device 1 is not allowed to camp. For example, the terminal device 1 does not camp on a barred cell.

In the present embodiment, when the connection state of a cell is the RRC idle state (RRC_IDLE), the RRC inactive state (RRC_INACTIVE), or the RRC connected state (RRC_CONNECTED) with timer T311 running, the terminal device 1 determines whether to consider the cell as a "barred" cell based on the received MIB. However, timer T311 is a timer that is executed during the RRC connection reestablishment procedure, and when the timer expires, the terminal device 1 sets the connection state to the RRC idle state.

The terminal device 1 considers a cell to be a barred cell when the value of the parameter cellBarred included in the received MIB is a predetermined value. However, the parameter cellBarred is a parameter indicating whether the corresponding cell is barred (barred). However, the parameter cellBarred may be ignored when the terminal device 1 is a predetermined terminal device (e.g., REDCAP UE). The terminal device 1 considers a cell to be a barred cell when a parameter cellBarred-rc different from the parameter cellBarred included in the received MIB is a predetermined value. However, the parameter cellBarred-rc is a parameter indicating whether the corresponding cell is barred (barred) for a predetermined terminal device (e.g., REDCAP UE). However, the parameter cellBarred-rc may be ignored when the terminal device 1 is other than the predetermined terminal device (e.g., REDCAP UE). However, the information indicated by the parameter cellBarred-rc may be realized by other parameters included in the MIB. For example, when the MIB includes a parameter related to the setting of CORESET0 and the parameter indicates a predetermined value, the terminal device 1 may consider the cell to be a barred cell. If none of the parameters contained in the received MIB indicate that the cell is a restricted cell, the terminal device 1 may apply other parameters contained in the MIB (e.g., information indicating the SFN).

In this embodiment, when the connection state is not an RRC connected state in which timer T311 is not running (in RRC_CONNECTED while T311 is not running), the terminal device 1 determines whether to consider the cell as a "barred" cell based on the parameters of the received SIB1 (which may be REDCAPSIB1).

In this embodiment, the base station device 3 transmits to the terminal device 1 a SIB1 (which may be a REDCAP SIB1) including parameters for determining whether the cell in which the terminal device 1 is located is restricted.

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

The initial uplink BWP may be defined in initialUplinkBWP. The terminal device 1 may be configured with multiple initial uplink sub-BWPs by SIB1. At least one of the multiple initial uplink sub-BWPs may be configured to include resources of a physical random access channel. The terminal device 1 may operate by regarding the initial uplink sub-BWP as the initial uplink BWP. The multiple initial uplink sub-BWPs may be regarded as multiple initial uplink BWPs. The multiple initial uplink sub-BWPs may be designed to be included within the frequency band of one initial uplink BWP. The initial uplink sub-BWP may be rephrased as an uplink sub-BWP.

When multiple initial downlink sub-BWPs are set by SIB1, the base station device 3 may transmit a downlink signal to which frequency hopping is applied using at least two of the multiple initial downlink sub-BWPs. However, the initial downlink sub-BWP is a frequency resource that can be used at least at the time of initial access before the RRC connection is established. When multiple initial downlink sub-BWPs are set by SIB1, the terminal device 1 may receive a downlink signal to which frequency hopping is applied using at least two of the multiple initial downlink sub-BWPs. However, the multiple initial downlink sub-BWPs according to this embodiment may be downlink BWPs to which the same identifier (BWP ID) is assigned. However, the multiple initial downlink sub-BWPs according to this embodiment may be multiple downlink BWPs to which different identifiers (BWP IDs) are assigned. The multiple initial downlink sub-BWPs may be multiple frequency bands composed of multiple sets of multiple resource blocks set by SIB1. Each of the initial downlink sub-BWPs may be composed of multiple resource blocks that are continuous in the frequency domain. For example, the initial downlink sub-BWPs may be sub-BWPs configured within the initial downlink BWP whose BWP ID configured by SIB1 is 0. For example, each sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0a, 0b, etc.). In this case, the configuration of the initial downlink BWP and the configuration of the sub-BWPs are configured by SIB1.

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

When multiple initial uplink sub-BWPs are set by SIB1, the terminal device 1 may transmit an uplink signal to which frequency hopping is applied using at least two of the multiple initial uplink sub-BWPs. However, the initial uplink sub-BWP is a frequency resource that can be used at least at the time of initial access before the RRC connection is established. When multiple initial uplink sub-BWPs are set by SIB1, the base station device 3 may receive an uplink signal to which frequency hopping is applied using at least two of the multiple initial uplink sub-BWPs. However, the multiple initial uplink sub-BWPs according to this embodiment may be set in the frequency band of the uplink BWP to which the same identifier (BWP ID) is assigned. However, the multiple initial uplink BWPs according to this embodiment may be multiple uplink BWPs to which different identifiers (BWP IDs) are assigned. The multiple initial uplink sub-BWPs may be multiple frequency bands composed of multiple sets of multiple resource blocks set by SIB1. Each of the initial uplink sub-BWPs may be composed of multiple resource blocks that are contiguous in the frequency domain. For example, the multiple initial uplink BWPs may be multiple sub-BWPs configured in the initial uplink BWP whose BWP ID configured by SIB1 is 0. For example, each sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0a, 0b, etc.). In this case, the configuration of the initial uplink BWP and the configuration of the multiple sub-BWPs are configured by SIB1. In this case, the configuration of the initial uplink BWP and the configuration of the multiple sub-BWPs are configured by SIB1.

SIB1 may include downlinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one of the parameters for determining whether a cell is barred in a cell by the terminal device 1 may be included in downlinkConfigCommon indicating the common downlink parameters of a cell. downlinkConfigCommon may include a parameter indicating one downlink carrier and basic parameters related to transmission (e.g., referred to as frequencyInfoDL), a parameter indicating an initial downlink BWP configuration of a serving cell (e.g., referred to as initialDownlinkBWP), and/or a parameter indicating the configuration of multiple initial downlink sub-BWPs (e.g., referred to as initialDownlinkBWP-rc).

The information element of the BWP may be a parameter indicating the frequency location and bandwidth of the BWP. The information element of the BWP may include a parameter subcarrierSpacing indicating the subcarrier spacing used in the BWP, a parameter locationAndBandwidth indicating the location in the frequency domain and bandwidth (number of resource blocks) of the BWP, and/or a parameter cyclicPrefix indicating whether the standard CP (cyclic prefix) or extended CP is used in the BWP. That is, the BWP is defined by the subcarrier spacing, the CP, and the location 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 starting PRB index and the number of consecutive PRBs of the BWP. However, the first PRB defining the region of the resource indicator value may be a PRB determined by the subcarrier spacing given by subcarrierSpacing of the BWP and offsetToCarrier set in SCS-SpecificCarrier included in FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier spacing. Also, the size defining the region of the resource indicator value is 275.

Similar to the BWP, the sub-BWP may be defined by the subcarrier spacing, CP, and frequency domain location and frequency domain bandwidth (e.g., number of contiguous resource blocks). The sub-BWP may be defined by the frequency domain location and frequency domain bandwidth.

The initialDownlinkBWP includes a BWP information element, a PDCCH configuration information element, and/or a PDSCH configuration information element. However, the initial downlink BWP may be configured by the network to include CORESET0 in the frequency domain.

The initialDownlinkBWP-rc includes information indicating the setting of the sub-BWP, an information element for PDCCH setting, and/or an information element for PDSCH setting. The initialDownlinkBWP-rc may be a parameter indicating the setting of each of the multiple initial downlink sub-BWPs. However, each of the multiple initial downlink sub-BWPs set by the initialDownlinkBWP-rc may be an initial downlink BWP (initial DL BWP). However, each of the multiple downlink sub-BWPs may be set by the network to include CORESET0 in the frequency domain. The initialDownlinkBWP-rc may include a list of information indicating a position in the frequency domain and a bandwidth in the frequency domain (e.g., the number of consecutive resource blocks). Each entry in the list of information indicating the frequency position and the bandwidth may correspond to each of the multiple initial downlink sub-BWPs. Each entry in the list of information indicating the frequency position and the bandwidth may be an information element of the BWP (e.g., subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). A plurality of initial downlink sub-BWPs may have a common bandwidth, and initialDownlinkBWP-rc may indicate a common bandwidth as well as a list of frequency locations of the initial downlink sub-BWPs. A plurality of initial downlink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and initialDownlinkBWP-rc may indicate a common bandwidth, a common subcarrierSpacing, and a common cyclicPrefix as well as a list of frequency locations of the initial downlink BWPs. Alternatively, the subcarrierSpacing and cyclicPrefix indicated by initialDownlinkBWP may be set to the plurality of initial downlink sub-BWPs. That is, initialDownlinkBWP-rc may be information for identifying the frequency locations and bandwidths of each of the plurality of initial downlink sub-BWPs. However, a parameter indicating the setting of the plurality of initial downlink sub-BWPs may be set in the above-mentioned initialDownlinkBWP. Parameters indicating the initial downlink BWP configuration of a serving cell may include parameters indicating the frequency location and bandwidth of the initial downlink BWP, subcarrierSpacing of the initial downlink BWP, and cyclicPrefix of the initial downlink BWP, as well as parameters indicating the configuration of multiple initial downlink sub-BWPs.

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

SCS-SpecificCarrier may include parameters indicating the actual carrier location, bandwidth, and carrier bandwidth. More specifically, SCS-SpecificCarrier, which is an information element in frequencyInfoDL, indicates the settings for a specific carrier and includes subcarrierSpacing, carrierbandwidth, and/or offsetToCarrier. subcarrierSpacing is a parameter indicating the subcarrier spacing of the carrier (e.g., 15 kHz or 30 kHz in FR1, and 60 kHz or 120 kHz in FR2). carrierbandwidth is a parameter indicating the bandwidth of the carrier in terms of the number of PRBs (Physical Resource Blocks). offsetToCarrier is a parameter indicating 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 terms of the number of PRBs (where the subcarrier spacing is the subcarrier spacing of the carrier given by subcarrierSpacing). For example, for a downlink carrier, the carrier bandwidth is given by the higher layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval, and the start position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval. For example, for an uplink carrier, the carrier bandwidth is given by the higher layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval, and the start position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval.

The terminal device 1 may be configured with multiple initial downlink sub-BWPs by the received SIB1. The terminal device 1 may determine whether a cell is a restricted cell based on the bandwidth of the initial downlink BWP configured by the received SIB1 corresponding to a certain cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports a downlink bandwidth that is the same as or wider than the bandwidth of the initial downlink BWP configured by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth that is the same as or wider than the bandwidth of the initial downlink BWP configured by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on the bandwidth of multiple initial downlink sub-BWPs configured by the received SIB1 corresponding to a certain cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports a downlink bandwidth that is the same as or wider than the widest bandwidth among the respective bandwidths of the multiple initial downlink sub-BWPs configured by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the multiple initial downlink sub-BWPs set by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether the terminal device 1 supports a downlink bandwidth that is equal to or wider than the bandwidth commonly set for the multiple initial downlink sub-BWPs set by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth that is equal to or wider than the bandwidth commonly set for the multiple initial downlink sub-BWPs set by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether the terminal device 1 supports a downlink bandwidth that is equal to or wider than the bandwidth specified by the parameters for setting the multiple initial downlink sub-BWPs notified by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth equal to or wider than the bandwidth specified by the parameters for setting the multiple initial downlink sub-BWPs notified by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports a downlink bandwidth equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may consider the cell as a restricted cell. However, the reference bandwidth may be a bandwidth specified from the bandwidth of one initial downlink BWP notified by SIB1 and the number of multiple initial downlink sub-BWPs set. However, the reference bandwidth may be a bandwidth specified by dividing one initial downlink BWP notified by SIB1 by a predetermined number.

The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports a downlink bandwidth that is the same as or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth that is the same as or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may consider the cell to be a restricted cell. However, the carrier bandwidth may be a carrier bandwidth corresponding to the subcarrier spacing of the initial downlink BWP set in the received SIB1. However, the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier spacing common to multiple initial downlink sub-BWPs set in the received SIB1.

Figure 16 is a flow diagram showing an example of a process for determining a restricted cell based on multiple initial downlink sub-BWPs in the terminal device 1 of this embodiment. In step S1001 of Figure 16, the terminal device 1 determines whether the connection state is an RRC connected state (RRC_CONNECTED) in which timer T311 is not running. If the determination is No (S1001-No), in step S1002, it is determined whether the terminal device 1 supports a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the multiple initial downlink sub-BWPs set in SIB1. If the determination is No, the terminal device 1 considers the cell to be a restricted cell (S1003).

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

The initialUplinkBWP includes a BWP information element, a PDCCH configuration information element, and/or a PDSCH configuration information element, etc. However, the initial uplink BWP may be configured by the network to include physical random access channel resources in the frequency domain.

The initialUplinkBWP-rc includes information indicating the setting of the sub-BWP, an information element for PUCCH setting, and/or an information element for PUSCH setting. The initialUplinkBWP-rc may be a parameter indicating the setting of each of the multiple initial uplink sub-BWPs. However, each of the multiple initial uplink sub-BWPs set by the initialUplinkBWP-rc may be an initial uplink BWP (initial UL BWP). However, each of the multiple uplink sub-BWPs may be configured by the network to include a physical random access channel resource in the frequency domain. The initialUplinkBWP-rc may include a list of information indicating a frequency location and a bandwidth. Each entry of the list of information indicating the frequency location and the bandwidth may correspond to each of the multiple initial uplink sub-BWPs. Each entry of the list of information indicating the frequency location and the bandwidth may be an information element of the BWP (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). A plurality of initial uplink sub-BWPs may have a common bandwidth, and initialUplinkBWP-rc may indicate a list of frequency locations of the initial uplink sub-BWPs and a common bandwidth. A plurality of initial uplink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and initialUplinkBWP-rc may indicate a list of frequency locations of the initial uplink BWPs and a common bandwidth, a common subcarrierSpacing, and a common cyclicPrefix. Alternatively, the subcarrierSpacing and cyclicPrefix indicated by initialUplinkBWP may be set to the plurality of initial uplink sub-BWPs. That is, initialUplinkBWP-rc may be information for identifying the frequency locations and bandwidths of each of the plurality of initial uplink sub-BWPs. However, a parameter indicating the setting of the plurality of initial uplink sub-BWPs may be set in the above-mentioned initialUplinkBWP. The parameters indicating the initial uplink BWP configuration of a serving cell may include parameters indicating the frequency location and bandwidth of the initial uplink BWP, the subcarrierSpacing of the initial uplink BWP, and the cyclicPrefix of the initial uplink BWP, as well as parameters indicating the configuration of multiple initial uplink sub-BWPs.

The terminal device 1 may consider the cell as a restricted cell if the cell does not support any frequency band for the TDD downlink and any frequency band for the FDD uplink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoDL and the frequencyBandList included in the frequencyInfoUL. The terminal device 1 may determine whether the cell is a restricted cell based on whether the terminal device 1 supports one or more frequency bands for the TDD downlink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoDL, or whether the terminal device 1 supports one or more frequency bands for the FDD uplink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoUL. For example, the terminal device 1 may determine whether to consider the cell as a restricted cell based on the frequency bands indicated in the frequencyBandList included in the frequencyInfoDL and/or the frequency bands indicated in the frequencyBandList included in the frequencyInfoUL, and/or the capabilities of the terminal device 1. For example, if the terminal device 1 does not support any frequency band for the TDD downlink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoDL, and if the terminal device 1 does not support any frequency band for the FDD uplink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoUL, the terminal device 1 may regard the cell as a restricted cell.

The terminal device 1 may be configured with multiple initial uplink sub-BWPs by the received SIB1. The terminal device 1 may determine whether a cell is a restricted cell based on the bandwidth of the initial uplink BWP configured by the received SIB1 corresponding to a cell. The terminal device 1 may determine whether a cell is a restricted cell based on whether the cell supports an uplink bandwidth that is the same as or wider than the bandwidth of the initial uplink BWP configured by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is the same as or wider than the bandwidth of the initial uplink BWP configured by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether a cell is a restricted cell based on the bandwidth of multiple initial uplink sub-BWPs configured by the received SIB1 corresponding to a cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports an uplink bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the multiple initial uplink sub-BWPs set by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the multiple initial uplink sub-BWPs set by SIB1, the terminal device 1 may consider the cell to be a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether the terminal device 1 supports an uplink bandwidth that is the same as or wider than the bandwidth commonly set for the multiple initial uplink sub-BWPs set by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is the same as or wider than the bandwidth commonly set for the multiple initial uplink sub-BWPs set by SIB1, the terminal device 1 may consider the cell to be a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports an uplink bandwidth that is equal to or wider than the bandwidth specified by the parameters for setting the multiple initial uplink sub-BWPs notified by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is equal to or wider than the bandwidth specified by the parameters for setting the multiple initial uplink sub-BWPs notified by SIB1, the terminal device 1 may consider the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports an uplink bandwidth that is equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may consider the cell as a restricted cell. However, the reference bandwidth may be a bandwidth specified from the bandwidth of one initial uplink BWP notified by SIB1 and the number of multiple initial uplink sub-BWPs set. However, the reference bandwidth may be a bandwidth determined by dividing one initial uplink BWP notified by SIB1 by a predetermined number.

The terminal device 1 may determine whether the cell is a restricted cell based on whether it supports an uplink bandwidth that is the same as or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth that is the same as or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may consider the cell to be a restricted cell. However, the carrier bandwidth may be a carrier bandwidth corresponding to the subcarrier spacing of the initial uplink BWP set in the received SIB1. However, the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier spacing common to multiple initial uplink sub-BWPs set in the received SIB1.

That is, the terminal device 1 may determine whether the cell is a restricted cell based on the bandwidth of the initial downlink BWP set by the received SIB1 corresponding to a cell, the bandwidths of multiple initial downlink sub-BWPs set by the received SIB1 corresponding to a cell, the bandwidth of the initial uplink BWP set by the received SIB1 corresponding to a cell, the bandwidths of multiple initial uplink sub-BWPs set by the received SIB1 corresponding to a cell, the carrier bandwidth set by the received SIB1 corresponding to a cell, and/or the capabilities of the terminal device 1.

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

Figure 17 is a flow diagram showing an example of a process for determining a restricted cell based on multiple initial uplink sub-BWPs in the terminal device 1 of this embodiment. In step S2001 of Figure 17, the terminal device 1 determines whether the connection state is an RRC connected state (RRC_CONNECTED) in which timer T311 is not running. If the determination is No (S2001-No), in step S2002, it determines whether the terminal device 1 supports an uplink channel bandwidth that is the same as or wider than the widest bandwidth among the multiple initial uplink sub-BWPs set in SIB1. If the determination is No, the terminal device 1 considers the cell to be a restricted cell (S2003).

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

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

Beam management may be a procedure in base station device 3 and/or terminal device 1 to align the directivity of an analog and/or digital beam in a transmitting device (base station device 3 in the case of downlink and terminal device 1 in the case of uplink) with the directivity of an analog and/or digital beam in a receiving device (terminal device 1 in the case of downlink and base station device 3 in the case of uplink) to obtain beam gain.

In addition, procedures for configuring, setting up or establishing a beam pair link may include the following procedures.
・Beam selection
・Beam refinement
・Beam recovery

For example, beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Beam improvement may be a procedure for selecting a beam with a higher gain, or for changing the beam between the base station device 3 and the terminal device 1 to an optimal one due to movement of the terminal device 1. Beam recovery may be a procedure for reselecting a beam when the quality of the communication link is degraded due to blockage caused by the passage of an obstruction or a person in communication between the base station device 3 and the terminal device 1.

Beam management may include beam selection, beam improvement. Beam recovery may include the following procedures:
Detecting beam failures, discovering new beams, sending beam recovery requests, and monitoring responses to beam recovery requests.

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

Furthermore, when instructing the terminal device 1 to direct a beam, the base station device 3 instructs the time index of the CRI or SS/PBCH, and the terminal device 1 receives based on the time index of the instructed CRI or SS/PBCH. At this time, the terminal device 1 may set a spatial filter based on the time index of the instructed CRI or SS/PBCH and receive. Furthermore, the terminal device 1 may receive using the assumption of quasi co-location (QCL). When a signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" with another signal (antenna port, synchronization signal, reference signal, etc.) or when "the assumption of QCL is used," it may be interpreted that a signal is associated with another signal.

Two antenna ports are said to be QCL if the long term properties of the channel over which a symbol at one antenna port is carried can be inferred from the channel over which a symbol at the other antenna port is carried. The long term properties of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna port 1 and antenna port 2 are QCL with respect to average delay, this means that the receive timing of antenna port 2 can be inferred from the receive timing of antenna port 1.

This QCL can also be extended to beam management. For this purpose, a new QCL extended to space may be defined. For example, the long term properties of the channel in the spatial domain QCL may be the angle of arrival (AoA (Angle of Arrival), ZoA (Zenith angle of Arrival), etc.) and/or the angle spread (e.g. ASA (Angle Spread of Arrival) and ZSA (Zenith angle Spread of Arrival)) of the radio link or channel, the angle of departure (AoD, ZoD, etc.) and its angle spread (e.g. ASD (Angle Spread of Departure) and ZSD (Zenith angle Spread of Departure)), spatial correlation, and reception spatial parameters.

For example, if antenna port 1 and antenna port 2 can be considered as a QCL in terms of receive spatial parameters, this means that the receive beam for receiving a signal from antenna port 2 can be inferred from the receive beam (receive spatial filter) for receiving a signal from antenna port 1.

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

The above-mentioned QCL types may be set and/or indicated as a transmission configuration indication (TCI) in the RRC and/or MAC layer and/or DCI, assuming a QCL between one or two reference signals and the PDCCH or PDSCH DMRS. For example, if SS/PBCH block index #2 and QCL type A+QCL type B are set and/or indicated as one state of the TCI when the terminal device 1 receives the PDCCH, the terminal device 1 may receive the PDCCH DMRS and perform synchronization and propagation path estimation by considering the Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters, and long-range characteristics of the channel when receiving the SS/PBCH block index #2. At this time, a reference signal indicated by the TCI (SS/PBCH block in the above example) may be referred to as a source reference signal, and a reference signal influenced by long-term characteristics inferred from the long-term characteristics of the channel when receiving the source reference signal (PDCCH DMRS in the above example) may be referred to as a target reference signal. In addition, the TCI may be set by RRC as one or more TCI states and a combination of a source reference signal and a QCL type for each state, and may be indicated to the terminal device 1 by the MAC layer or DCI.

With this method, the operation of the base station device 3 and terminal device 1 equivalent to beam management may be defined as beam management and beam instruction/reporting based on the assumption of QCL in the spatial domain and radio resources (time and/or frequency).

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

The configuration of the device in this embodiment is described below.

Figure 19 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. As shown in the figure, the terminal device 1 is configured to include a wireless transceiver unit 10 and an upper layer processing unit 14. The wireless transceiver unit 10 is configured to include an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 is configured to include a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The wireless transceiver unit 10 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. The upper layer processing unit 14 is also referred to as a processing unit 14, a measuring unit 14, a selecting unit 14, a determining unit 14, or a control unit 14.

The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by user operation or the like to the radio transmission/reception unit 10. The upper layer processing unit 14 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function of acquiring bit information of the MIB (which may be the REDCAP MIB), the SIB1 (which may be the REDCAP SIB1), and other SIBs (which may be the REDCAP SIBs). The upper layer processing unit 14 may have a function of determining the number of repetitions of the PDCCH transmitted in the common search space set. The upper layer processing unit 14 may have a function of determining whether the cell is a restricted cell based on information of the system information block (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB).

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

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

The wireless transceiver 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The wireless transceiver 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 transceiver 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3, etc. The wireless transceiver 10 outputs the upper layer signal (RRC message), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. In addition, the wireless transceiver 10 generates and transmits an uplink signal (including PUCCH and/or PUSCH) based on an instruction from the upper layer processing unit 14. The wireless transceiver 10 may have a function of receiving PDCCH and/or PDSCH. The wireless transceiver 10 may have a function of transmitting one or more PUCCHs and/or PUSCHs. The wireless transceiver 10 may have a function of receiving DCI on the PDCCH. The radio transceiver 10 may have a function of outputting DCI received on the PDCCH to the higher layer processing unit 14. The radio transceiver 10 may have a function of receiving a PSS, an SSS, a PBCH, a DMRS for the PBCH, a REDCAP PBCH, and/or a DMRS for the REDCAP PBCH. The radio transceiver 10 may have a function of receiving an SS/PBCH block and/or a REDCAP PBCH block. The radio transceiver 10 may have a function of receiving a system information block (SIB1, REDCAP SIB1, SIB, and/or REDCAP SIB) corresponding to a predetermined cell.

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

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

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

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

Figure 20 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As shown in the figure, the base station device 3 is configured to include a radio transmission/reception unit 30 and an upper layer processing unit 34. The radio transmission/reception unit 30 is configured to include an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 is configured to include a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The radio transmission/reception unit 30 is also referred to as a transmitting unit, a receiving unit, a monitoring unit, or a physical layer processing unit. A control unit that controls the operation of each unit based on various conditions may also be provided separately. The upper layer processing unit 34 is also referred to as a processing unit 34, a determining unit 34, or a control unit 34.

The upper layer processing unit 34 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of generating DCI based on the upper layer signal transmitted to the terminal device 1 and the time resource for transmitting the PUSCH. The upper layer processing unit 34 may have a function of outputting the generated DCI, etc. to the radio transceiver unit 30. The upper layer processing unit 34 may have a function of generating bit information of the transport block of the MIB. The upper layer processing unit 34 may have a function of generating bit information of the transport block of the REDCAP MIB. The upper layer processing unit 34 may have a function of generating a system information block (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB) including information for the terminal device to determine whether a specific cell is a restricted cell.

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

The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs processing of the RRC layer. 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 DCI, downlink data (transport block (TB), random access response (RAR)) arranged in the PDSCH, system information, RRC message, MAC CE (Control Element), etc., or acquires them from the upper node, and outputs them to the radio transmission/reception unit 30. The radio resource control layer processing unit 36 also manages various setting information/parameters for each terminal device 1. The radio resource control layer processing unit 36 may set various setting information/parameters for each terminal device 1 via a signal of the upper layer. That is, the radio resource control layer processing unit 36 transmits/reports information indicating various setting information/parameters. The radio resource control layer processing unit 36 may transmit/report information for identifying 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 of the message, the base station device 3 performs processing (control of the terminal device 1 and the system) assuming that the terminal device is performing the processing. In other words, the base station device 3 transmits an RRC message, MAC CE, and/or PDCCH to the terminal device 1 that causes the terminal device to perform processing based on the reception of the message.

The wireless transmission/reception unit 30 transmits higher layer signals (RRC messages), DCI, etc. to the terminal device 1. The wireless transmission/reception unit 30 also receives uplink signals transmitted from the terminal device 1 based on instructions from the higher layer processing unit 34. The wireless transmission/reception unit 30 may have a function of transmitting a PDCCH and/or a PDSCH. The wireless transmission/reception unit 30 may have a function of receiving one or more PUCCHs and/or PUSCHs. The wireless transmission/reception unit 30 may have a function of transmitting DCI on a PDCCH. The wireless transmission/reception unit 30 may have a function of transmitting DCI output by the higher layer processing unit 34 on a PDCCH. The wireless transmission/reception unit 30 may have a function of transmitting a PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and/or DMRS for REDCAP PBCH. The wireless transmission/reception unit 30 may have a function of transmitting an SS/PBCH block and/or a REDCAP PBCH block. The wireless transmission/reception unit 30 may have a function of transmitting an RRC message (which may be an RRC parameter). The wireless transceiver unit 30 may have a function of transmitting system information blocks (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB) from the terminal device 1. Other than that, some of the functions of the wireless transceiver unit 30 are similar to those of the wireless transceiver unit 10, and therefore will not be described. Note that when the base station device 3 is connected to one or more transmission/reception points 4, some or all of the functions of the wireless transceiver unit 30 may be included in each transmission/reception point 4.

The upper layer processing unit 34 also transmits (transfers) or receives control messages or user data between base station devices 3 or between higher-level network devices (MME, S-GW (Serving-GW)) and base station device 3. In FIG. 20, other components of base station device 3 and transmission paths for data (control information) between the components are omitted, but it is clear that the base station device 3 has multiple blocks as components having other functions necessary for operating as a base station device 3. For example, the upper layer processing unit 34 includes a Radio Resource Management layer processing unit and an application layer processing unit.

Note that the "parts" in the diagram refer to elements that realize the functions and procedures of the terminal device 1 and base station device 3, and can also be expressed by terms such as section, circuit, component equipment, device, and unit.

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

(1) A terminal device 1 in a first aspect of the present invention includes a receiving unit 10 that receives a first system information block (SIB1) corresponding to a first cell, and a processing unit 14 that determines whether the first cell is a barred cell based on information in the first system information block, and the processing unit 14 considers the first cell to be a barred cell when the terminal device 1 does not support a downlink channel bandwidth that is the same as or wider than the widest bandwidth among multiple downlink BWPs (initial DL BWPs) set by the first system information block.

(2) In a first aspect of the present invention, the processing unit 14 may consider the first cell to be a restricted cell when the terminal device does not support a downlink channel bandwidth that is the same as or narrower than the carrier bandwidth of the first cell set by the first system information block.

(3) In the first aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set for a subcarrier spacing that is set commonly to the multiple downlink BWPs.

(4) In a second aspect of the present invention, a base station device 3 comprises a processing unit 34 that generates a first system information block (SIB1) including information for a terminal device 1 to determine whether a first cell is a barred cell, and a transmitting unit 30 that transmits the first system information block, the information including information for setting multiple downlink BWPs (initial DL BWPs), and the information causing the terminal device 1 to consider the first cell to be a barred cell when the terminal device 1 does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the multiple downlink BWPs.

(5) In a second aspect of the present invention, the information may include information for setting a carrier bandwidth of the first cell, and may be information for considering the first cell to be a restricted cell if the terminal device 1 does not support a downlink channel bandwidth that is the same as or narrower than the carrier bandwidth.

(6) In a second aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set for a subcarrier spacing that is set commonly to the multiple downlink BWPs.

(7) A terminal device 1 in a third aspect of the present invention includes a receiving unit 10 that receives a first system information block (SIB1) corresponding to a first cell, and a processing unit 14 that determines whether the first cell is a barred cell based on information in the first system information block, and the processing unit 14 considers the first cell to be a barred cell when the terminal device 1 does not support an uplink channel bandwidth that is the same as or wider than the widest bandwidth among multiple uplink BWPs (initial UL BWPs) set by the first system information block.

(8) In a third aspect of the present invention, the processing unit 14 may consider the first cell to be a restricted cell when the terminal device does not support an uplink channel bandwidth that is the same as or narrower than the carrier bandwidth of the first cell set by the first system information block.

(9) In a third aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set for a subcarrier spacing that is set commonly to the multiple uplink BWPs.

(10) A base station device 3 in a fourth aspect of the present invention includes a processing unit 34 that generates a first system information block (SIB1) including information for a terminal device 1 to determine whether a first cell is a barred cell, and a transmitting unit 30 that transmits the first system information block, the information including information for setting multiple uplink BWPs (initial UL BWPs), and the information causing the terminal device 1 to consider the first cell to be a barred cell when the terminal device 1 does not support an uplink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the multiple uplink BWPs.

(11) In a fourth aspect of the present invention, the information may include information for setting a carrier bandwidth of the first cell, and may be information for considering the first cell to be a restricted cell if the terminal device 1 does not support an uplink channel bandwidth that is the same as or narrower than the carrier bandwidth.

(12) In a fourth aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set for a subcarrier spacing that is set commonly to the multiple uplink BWPs.

This allows the terminal device 1 and the base station device 3 to communicate efficiently. For example, when the terminal device 1 receives a system information block from a cell in which an unsupported downlink channel bandwidth and/or an uplink channel bandwidth is set, the terminal device 1 can avoid camping by considering the cell as a restricted cell.

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

A program for implementing the functions of an embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used here refers to a computer system built into a device, and includes hardware such as an operating system and peripheral devices. Furthermore, the term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other recording medium that is readable by a computer.

In addition, each functional block or feature of the device used in the above-mentioned embodiment may be implemented or performed by an electric circuit, for example, an integrated circuit or multiple integrated circuits. The electric circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electric circuit may be composed of digital circuits or analog circuits. In addition, if a technology for integrated circuitization that replaces current integrated circuits 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.

In an embodiment relating to one aspect of the present invention, an example has been described in which the present invention is applied to a communication system consisting of a base station device and a terminal device, but it can also be applied to a system in which terminals communicate with each other, such as D2D (Device to Device).

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

Although an embodiment of the present invention has been described above in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and design modifications and the like that do not depart from the gist of the present invention are also included. Furthermore, various modifications of one aspect of the present invention are possible within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. Also included are configurations in which elements described in the above embodiments are substituted for elements that have the same effect.

One aspect of 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), or a program.

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

Claims (7)

A terminal device,
a receiver for receiving a first system information block corresponding to a first cell;
A processing unit that determines whether the first cell is a restricted cell based on information of the first system information block,
The processing unit, when the terminal device does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of a plurality of downlink BWPs set by the first system information block, considers the first cell to be a restricted cell. A terminal device. The terminal device of claim 1, wherein the processing unit considers the first cell to be a restricted cell when the terminal device does not support a downlink channel bandwidth that is the same as or narrower than the carrier bandwidth of the first cell set by the first system information block. A terminal device as described in claim 2, wherein the carrier bandwidth is set for a subcarrier spacing that is set commonly to the multiple downlink BWPs. A base station device,
A processing unit for generating a first system information block including information for the terminal device to determine whether the first cell is a restricted cell;
a transmitter for transmitting the first system information block;
The information includes information for setting a plurality of downlink BWPs, and is information that causes the terminal device to consider the first cell to be a restricted cell if the terminal device does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the plurality of downlink BWPs. The base station device of claim 4, wherein the information includes information for setting the carrier bandwidth of the first cell, and information for regarding the first cell as a restricted cell if the terminal device does not support a downlink channel bandwidth that is the same as or narrower than the carrier bandwidth. A base station device as described in claim 5, wherein the carrier bandwidth is set for a subcarrier spacing that is set commonly to the multiple downlink BWPs. A communication method for a base station device, comprising:
A terminal device generates a first system information block including information for determining whether the first cell is a restricted cell;
transmitting the first system information block;
The information includes information for setting a plurality of downlink BWPs, and if the terminal device does not support a downlink channel bandwidth that is equal to or wider than the widest bandwidth among the bandwidths of the plurality of downlink BWPs, the terminal device is caused to regard the first cell as a restricted cell.