Terminal device, base station device, and communication method

Abstract

If this terminal device receives a first system information block corresponding to a first cell and does not support a downlink channel bandwidth that is the same as or wider than the maximum bandwidth from among a plurality of downlink BWP bandwidths set by the first system information block, the first cell is considered to be a regulation cell.

Description

Technical Field

[0001] 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 on September 29, 2020, the content of which is incorporated herein by reference.

Background Art

[0002] Currently, as a radio access method and radio network technology for the fifth-generation cellular system, in the Third Generation Partnership Project (3GPP), technical studies and standardization of LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) are being carried out (Non-Patent Document 1).

[0003] In the fifth-generation cellular system, three service assumed scenarios are required: eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-latency and high-reliability communication, and mMTC (massive Machine Type Communication) to which a large number of machine-type devices such as IoT (Internet of Things) are connected. Furthermore, in Release 17, which is a future release of NR, applications such as sensor networks, surveillance cameras, and / or wearable devices are assumed, and reduced capability (REDCAP) NR devices that do not require high requirements such as eMBB and URLLC while aiming to reduce costs and extend battery life are being studied (Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] An object of the present invention is to provide a terminal device, a base station device, and a communication method that enable efficient communication in a wireless communication system as described above.

Means for Solving the Problems

[0006] (1) In order to achieve the above object, an aspect of the present invention takes the following means. That is, a terminal device according to an aspect 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. When 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 a plurality of downlink BWPs set by the first system information block, the processing unit regards the first cell as a restricted cell.

[0007] (2) Further, the base station apparatus according to one aspect of the present invention includes a processing unit that generates a first system information block including information for determining whether a first cell is a restricted cell, and a transmission unit that transmits the first system information block. The information includes information for setting a plurality of downlink BWPs. When 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 plurality of downlink BWPs, the information is information that causes the terminal device to consider the first cell as a restricted cell.

[0008] (3) Further, a communication method according to one aspect of the present invention is a communication method of a terminal device. The method includes receiving a first system information block corresponding to a first cell, and considering the first cell as a restricted cell when 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 a plurality of downlink BWPs set by the first system information block.

[0009] (4) Further, a communication method according to one aspect of the present invention is a communication method of a base station apparatus. The method includes generating a first system information block including information for determining whether a first cell is a restricted cell, and transmitting the first system information block. The information includes information for setting a plurality of downlink BWPs. When 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 plurality of downlink BWPs, the information is information that causes the terminal device to consider the first cell as a restricted cell.

Advantages of the Invention

[0010] According to one aspect of this invention, a terminal device and a base station apparatus can communicate efficiently.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, embodiments of the present invention will be described.

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

[0014] 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 also 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, an 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. Further, the base station device 3 may include one or more transmission reception points 4 (transmission reception point). At least a part of the functions / processes of the base station device 3 described below may be functions / processes at each of the transmission reception points 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 with a communicable range (communication area) controlled by the base station device 3 as one or more cells. Further, the base station device 3 may serve the terminal device 1 with a communicable range (communication area) controlled by one or more transmission reception points 4 as one or more cells. Further, the base station device 3 may divide one cell into a plurality of partial areas (Beamed area) 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 for beamforming or the index of precoding.

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

[0016] In FIG. 1, in the wireless communication between the terminal device 1 and the base station device 3, 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) may be used.

[0017] Also, in FIG. 1, in the wireless communication between the terminal device 1 and the base station device 3, universal-filtered multi-carrier (UFMC), filtered OFDM (F-OFDM), OFDM multiplied by a window function (Windowed OFDM), or filter-bank multi-carrier (FBMC) may be used.

[0018] In this embodiment, OFDM is described as a transmission method using OFDM symbols. However, the cases of using the above-described other transmission methods are also included in one aspect of the present invention.

[0019] Also, in FIG. 1, in the wireless communication between the terminal device 1 and the base station device 3, the above-described transmission methods without using CP or with zero-padding instead of CP may be used. Also, CP or zero-padding may be added to both the front and the back.

[0020] One aspect of this embodiment may be operated in carrier aggregation or dual connectivity with a radio access technology (RAT) such as LTE, LTE-A / LTE-A Pro. At this time, it may be used in some or all cells or cell groups, carriers or carrier groups (e.g., Primary Cell (PCell), Secondary Cell (SCell), Primary Secondary Cell (PSCell), Master Cell Group (MCG), Secondary Cell Group (SCG), etc.). Also, one aspect of this embodiment may be used in a stand-alone operation that operates independently. In dual connectivity operation, the SpCell (Special Cell) is referred to as the PCell of the MCG or the PSCell of the SCG, respectively, depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG. If it is not 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.

[0021] In this embodiment, one or more serving cells may be configured for the terminal device 1. The plurality of configured serving cells may include one primary cell and one or more secondary cells. The primary cell may be a serving cell in which an initial connection establishment procedure has been performed, a serving cell that has initiated a connection re - establishment procedure, or a cell designated as the primary cell in a handover procedure. One or more secondary cells may be configured at the time when the RRC (Radio Resource Control) connection is established or later. However, the plurality of configured serving cells may include one primary - secondary cell. The primary - secondary cell may be a secondary cell among the one or more secondary cells configured for the terminal device 1 that can transmit control information on the uplink. Also, for the terminal device 1, two subsets of serving cells, namely a master cell group and a secondary cell group, may be configured. 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.

[0022] In the wireless communication system of this embodiment, TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) may be applied. The TDD (Time Division Duplex) mode or the FDD (Frequency Division Duplex) mode may be applied to all of the plurality of cells. Also, cells to which the TDD mode is applied and cells to which the FDD mode is applied may be aggregated. The TDD mode may be referred to as unpaired spectrum operation. The FDD mode may be referred to as paired spectrum operation.

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

[0024] FIG. 2 is a diagram showing an example of the schematic configuration of an uplink and a downlink slot according to the first embodiment of the present invention. Each of the radio frames is 10 ms long. Each of the radio frames is composed of 10 subframes and W slots. Also, 1 slot is composed of X OFDM symbols. That is, the length of 1 subframe is 1 ms. The length of each slot is defined by the subcarrier spacing. For example, when the subcarrier spacing of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix), X = 7 or X = 14, which are 0.5 ms and 1 ms, respectively. When the subcarrier spacing is 60 kHz, X = 7 or X = 14, which are 0.125 ms and 0.25 ms, respectively. Also, for example, when X = 14, when the subcarrier spacing is 15 kHz, W = 10, and when the subcarrier spacing is 60 kHz, W = 40. FIG. 2 shows the case of X = 7 as an example. Note that the example of FIG. 2 can be similarly extended to the case of X = 14. Also, the uplink slot is defined in the same manner, and the downlink slot and the uplink slot may be defined separately. Also, the cell bandwidth in FIG. 2 may be defined as a part of the bandwidth (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 the transmission period of the transport block.

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

[0026] The resource grid is used to represent the mapping of resource elements of a certain physical downlink channel (such as PDSCH) or uplink channel (such as PUSCH). For example, when the subcarrier spacing is 15 kHz, the number of OFDM symbols X = 14 included in a subframe. 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. That is, the resource grid is composed of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended CP), it is only supported at a subcarrier spacing of 60 kHz. Therefore, one physical resource block is defined by, for example, 12 (the number of OFDM symbols included in one slot) * 4 (the 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 is composed of (48 * 12 * Nmax, μ) resource elements.

[0027] As resource blocks (RBs), 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. For example, resource blocks may be configured with a subcarrier spacing of 15 kHz and numbered in ascending order. The subcarrier index 0 at reference resource block index 0 may be referred to as reference point A (point A) (simply referred to as "reference point"). The common resource block is a resource block numbered in ascending order from 0 at each subcarrier spacing 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 later-described bandwidth part (BWP: BandWidth Part). A certain physical uplink channel is first mapped to a virtual resource block. Thereafter, the virtual resource block is mapped to a physical resource block. Hereinafter, the resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

[0028] Next, the subcarrier spacing setting μ will be described. As described above, in NR, one or more OFDM numerologies are supported. In a certain BWP, the subcarrier spacing setting μ (μ = 0, 1,..., 5) and the cyclic prefix length are given by the upper layer for the downlink BWP and given by the upper layer in the uplink BWP. Here, when μ is given, the subcarrier spacing Δf is given by Δf = 2^μ·15 (kHz).

[0029] In the sub - carrier spacing setting μ, the slots are numbered in ascending order from 0 to \(N^{subframe,\mu}_{slot}-1\) within a sub - frame and from 0 to \(N^{frame,\mu}_{slot}-1\) within a frame. Based on the slot configuration and the cyclic prefix, \(N^{slot}_{symb}\) consecutive OFDM symbols are within a slot. \(N^{slot}_{symb}\) is 14. The start of slot \(n^{μ}_{s}\) in a sub - frame is time - aligned with the start of the \(n^{μ}_{s}*N^{slot}_{symb}\) - th OFDM symbol in the same sub - frame.

[0030] Next, sub - frames, slots, and mini - slots will be described. FIG. 3 is a diagram showing an example of the relationship in the time domain of sub - frames, slots, and mini - slots. As shown in the figure, three types of time units are defined. A sub - frame is 1 ms regardless of the sub - carrier spacing. The number of OFDM symbols included in a slot is 7 or 14 (however, when the cyclic prefix (CP) added to each symbol is Extended CP, it may be 6 or 12), and the slot length varies depending on the sub - carrier spacing. Here, when the sub - carrier spacing is 15 kHz, a sub - frame 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.

[0031] A mini-slot (which may also be referred to as a subslot) is a time unit composed of a number of OFDM symbols less than the number of OFDM symbols included in one slot. The figure shows, as an example, the case where a mini-slot is composed of 2 OFDM symbols. The OFDM symbols within a mini-slot may coincide with the OFDM symbol timing that constitutes a slot. Note that the minimum unit of scheduling may be a slot or a mini-slot. Also, allocating a mini-slot may be referred to as non-slot-based scheduling. Also, scheduling a mini-slot may 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 mini-slot may be referred to as PDSCH mapping type B. An uplink mini-slot may be referred to as PUSCH mapping type B.

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

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

[0034] The physical channels and physical signals of this embodiment will be described.

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

[0036] ·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)

[0037] The PBCH is used to notify an important information block (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) that contains important system information necessary for the terminal device 1. The MIB may include information for specifying 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 specifying the subcarrier spacing of the System Information Block 1 (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 related to the PDCCH for SIB1. However, SIB1 contains information necessary when evaluating whether the terminal device 1 is allowed to connect to the cell and information for determining the scheduling of other system information (SIB: System Information Block). However, the information indicating the settings related to the PDCCH for SIB1 may be information for determining CORESET (Control Resource Set) 0 (also referred to as the common CORESET), the common search space, and / or the necessary PDCCH parameters. However, CORESET indicates the resource elements of the PDCCH, and CORESET0 is the CORESET for the PDCCH that schedules SIB1.

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

[0039] Also, the PBCH may be used to notify a time index within the period of the SS / PBCH block. Here, the time index is information indicating the index of the synchronization signal and PBCH within the cell. The time index may be referred to as the SSB index or the SS / PBCH block index. For example, when transmitting the SS / PBCH block using an assumption of quasi co-location (QCL) regarding a plurality of transmission beams, transmission filter settings, and / or reception spatial parameters, it may indicate the time order within a predetermined period or a set period. Further, the terminal device may recognize the difference in the time index as the difference in the assumption of QCL regarding the transmission beam, transmission filter settings, and / or reception spatial parameters.

[0040] The REDCAP PBCH is used to notify the REDCAP important information block (also referred to as REDCAP MIB, REDCAP EIB, REDCAP BCH, R-MIB) that contains important system information required by the terminal device 1. However, the REDCAP MIB may be used only for the terminal device 1 that meets specific conditions (for example, indicating specific parameters such as UE Capability and / or UE Category). However, the REDCAP MIB may include information for specifying the SFN to which the REDCAP PBCH is mapped or the SFN to which the SS / PBCH block corresponding to the REDCAP PBCH is mapped, information for specifying the subcarrier spacing of the REDCAP system information block 1 (also referred to as REDCAP SIB1, R-SIB1), information indicating the frequency domain offset between the resource block grid and the SS / PBCH block (also referred to as the synchronization signal block, SS block, SSB), and information indicating the settings related to the PDCCH for REDCAP SIB1. However, REDCAP SIB1 includes information necessary when evaluating whether the terminal device 1 is allowed to connect to the cell and includes information for determining the scheduling of other REDCAP system information blocks (also referred to as REDCAP SIB, R-SIB). However, REDCAP SIB1 may include information necessary when evaluating whether the terminal device 1 that meets specific conditions (for example, indicating specific parameters such as UE Capability and / or UE Category) is allowed to connect to the cell and may include information for determining the scheduling of other REDCAP SIBs. However, part or all of the information contained in the REDCAP MIB may be the same as part or all of the information contained in the MIB notified by the PBCH. For example, the above REDCAP SIB1 may be SIB1. However, part or all of the information of the REDCAP MIB may be notified by the PBCH. However, the REDCAP PBCH may notify 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 associated with the REDCAP PBCH. However, the processing related to the MIB described hereinafter may be similarly applied to the processing related to the REDCAP MIB.

[0041] In addition, the information transmitted by the REDCAP PBCH may include information for identifying the number of the radio frame to which the REDCAP PBCH is mapped and / or information for identifying the half radio frame. However, the information transmitted by the REDCAP PBCH may include information for identifying the number of the radio frame to which the (associated) PSS and / or SSS associated with the REDCAP PBCH is mapped and / or information for identifying the half radio frame. However, the information transmitted by the REDCAP PBCH may include information for identifying the number of the radio frame to which the (associated) SS / PBCH block is mapped and / or information for identifying the half radio frame.

[0042] In addition, the information transmitted by the REDCAP PBCH may include the time index within the period of the associated SS / PBCH block. This time index may be referred to as the SSB index or the SS / PBCH block index. For example, when the base station device 3 transmits the SS / PBCH block using the assumption of QCL regarding a plurality of transmission beams, transmission filter settings, and / or reception space parameters, it may indicate the time order within a predetermined period or a set period. Also, the terminal device 1 may recognize the difference in the time index as the difference in the assumption of QCL regarding the transmission beam, transmission filter settings, and / or reception space parameters. In addition, the information transmitted by the REDCAP PBCH may include the time index of the REDCAP PBCH.

[0043] The information indicating the settings related to the PDCCH for REDCAP SIB1 transmitted by the REDCAP PBCH may be information for determining CORESET0, the common search space, and / or the necessary PDCCH parameters for the PDCCH that schedules REDCAP SIB1. However, the information for determining the information related to CORESET0, the common search space, and / or the necessary PDCCH parameters indicated in the REDCAP MIB may be the same as the information for determining the information related to CORESET0, the common search space, and / or the necessary PDCCH parameters indicated in the MIB.

[0044] 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. A value from 0 to 15 is set in the information element (IE: Information Element) ControlResourceSetZero indicated by controlResourceSetZero. However, the number of values that can be set in ControlResourceSetZero may be other than 16, for example, it may be 32. A value from 0 to 15 is set in the information element SearchSpaceZero indicated by searchSpaceZero. However, the number of values that can be set in SearchSpaceZero may be other than 16, for example, it may be 32.

[0045] The terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET0 from controlResourceSetZero within PDCCH-ConfigSIB1-RC. However, the value indicated by controlResourceSetZero is applied to a predetermined table as an index. However, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE Capability. However, the terminal device 1 may determine the table to be applied based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier spacing of the SS / PBCH block, the subcarrier spacing of the REDCAP PBCH, and / or the subcarrier spacing of CORESET0. Fig. 5 shows an example of a table to which the value of controlResourceSetZero is applied as an index. As shown in the table shown in 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 the REDCAP PBCH and CORESET, the number of RBs (which may be PRBs) of CORESET0, the number of symbols of CORESET0, the offset, and / or the number of repetitions of the PDCCH.

[0046] The multiplexing pattern of the 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 the REDCAP PBCH and CORESET is 1, the REDCAP PBCH and CORESET are time-division multiplexed in different symbols. However, the multiplexing pattern of the REDCAP PBCH and CORESET may indicate the pattern of the relationship between the SS / PBCH block corresponding to the REDCAP PBCH that detected the REDCAP MIB and CORESET0. However, the multiplexing pattern of the REDCAP PBCH and CORESET may not be defined in a table and may always be a fixed pattern (e.g., pattern 1).

[0047] The number of RBs in CORESET0 indicates the number of resource blocks continuously allocated to CORESET0. The number of symbols in CORESET0 indicates the number of symbols continuously allocated to CORESET0.

[0048] The offset indicates the offset from the minimum RB index of the resource blocks allocated to CORESET0 to the minimum RB index of the common resource blocks where the first resource block of the corresponding REDCAP PBCH overlaps. However, the offset may indicate the offset from the minimum RB index of the resource blocks allocated to CORESET0 to the minimum RB index of the common resource blocks where the first resource block of the SS / PBCH block corresponding to the REDCAP PBCH overlaps.

[0049] The number of repetitions of the PDCCH indicates the number of repeated transmissions of the PDCCH that schedules REDCAP SIB1. When the number of repetitions of the PDCCH shown in the table is greater than 1, the terminal device 1 considers that the PDCCH that schedules REDCAP SIB1 is repeatedly transmitted.

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

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

[0052] The terminal device 1 monitors the PDCCH in a Type0-PDCCH common search space set over 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 indicated in the table in the REDCAP PBCH with index i and / or the corresponding SS / PBCH block.

[0053] However, when it is indicated that REDCAP SIB1 is absent in the field within REDCAP MIB, the information indicating the setting regarding the PDCCH for REDCAP SIB1 transmitted in the REDCAP PBCH may indicate the frequency position 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.

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

[0055] The terminal device 1 receives the REDCAP MIB including the RRC parameter PDCCH-repetitions by the REDCAP PBCH, determines the number of repeated transmissions of the PDCCH indicating the scheduling information of the REDCAP SIB1 based on the PDCCH-repetitions, and considers that the PDCCH is not transmitted when the PDCCH-repetitions is a predetermined value.

[0056] The PDCCH is used to transmit (or carry) downlink control information (Downlink Control Information: DCI) in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). Here, one or more DCIs (which may also be referred to as DCI formats) are defined for the transmission of downlink control information. That is, the fields for downlink control information are defined as DCIs 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.

[0057] 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

[0058] DCI format 0_0 may be used for scheduling of 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 CRC (Cyclic Redundancy Check) scrambled by any one of Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI, MCS-C-RNTI, and / or Temporary C-NRTI (TC-RNTI) among the Radio Network Temporary Identifiers (RNTIs) which are identifiers. DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

[0059] DCI format 0_1 may be used for scheduling of 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 one of C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and / or MCS-C-RNTI among the RNTIs. DCI format 0_1 may be monitored in a UE-specific search space.

[0060] DCI format 0_2 may be used for scheduling of 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 port. DCI format 0_2 may be added with a CRC scrambled by any one of C-RNTI, CSI-RNTI, SP-CSI-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 0_2 may be monitored in the UE-specific search space. DCI format 0_2 may be referred to as DCI format 0_1A or the like.

[0061] DCI format 1_0 may be used for scheduling of 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 one of C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random access (RA)-RNTI, and / or TC-RNTI among identifiers. DCI format 1_0 may be monitored in the common search space or the UE-specific search space.

[0062] DCI format 1_1 may be used for scheduling of 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, transmission configuration indication (TCI), and / or information regarding antenna ports. DCI format 1_1 may be added with a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_1 may be monitored in the UE-specific search space.

[0063] DCI format 1_2 may be used for scheduling of 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 one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_2 may be monitored in the UE-specific search space. DCI format 1_2 may be referred to as DCI format 1_1A or the like.

[0064] DCI format 2_0 is used to notify the slot format of one or more slots. The slot format is defined such that each OFDM symbol in the slot is classified as either downlink, flexible, or uplink. For example, when the slot format is 28, DDDDDDDDDDDDFU is applied to the 14-symbol OFDM symbols in the slot where slot format 28 is indicated. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Note that the slot will be described later.

[0065] DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks (PRBs or RBs) and OFDM symbols that may be assumed to have no transmission. Note that this information may be referred to as a preemption indication (discontinuous transmission indication).

[0066] DCI format 2_2 is used for the transmission of PUSCH and transmit power control (TPC) commands for PUSCH.

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

[0068] 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.

[0069] The CRC parity bits added to the DCI format transmitted by 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 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.

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

[0071] For the C-RNTI and / or other RNTIs, different values may be used corresponding to the type of traffic of the PDSCH or PUSCH. For the C-RNTI and other RNTIs, different values may be used corresponding to 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 RNTIs corresponding to 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 based on the value of the RNTI applied to the received DCI (used for scrambling).

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

[0073] The PDSCH is used for transmitting downlink data (DL-SCH: Downlink Shared Channel) from the Medium Access Control (MAC) layer. Also, in the case of the downlink, the PDSCH is also used for transmitting system information (SI) and random access response (RAR).

[0074] The PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer or to transmit HARQ-ACK and / or CSI together with the uplink data. Also, the PUSCH may be used to transmit only CSI, or only HARQ-ACK and CSI. That is, the PUSCH may be used to transmit only UCI.

[0075] Here, the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in the upper layer (higher layer). For example, the base station device 3 and the terminal device 1 may transmit and receive RRC messages (also referred to as RRC messages, RRC information, or RRC signalling) in the Radio Resource Control (RRC) layer. Also, the base station device 3 and the terminal device 1 may transmit and receive MAC control elements in the Medium Access Control (MAC) layer. Further, the RRC layer of the terminal device 1 acquires system information notified from the base station device 3. Here, RRC messages, system information, and / or MAC control elements are also referred to as upper layer signals (higher layer signaling) or upper layer parameters (higher layer parameter). Each parameter included in the upper layer signal received by the terminal device 1 may be referred to as an upper layer parameter. The upper layer here means the upper layer as seen from the physical layer, and thus may include one or more of the MAC layer, RRC layer, RLC layer, PDCP layer, Non-Access Stratum (NAS) layer, etc. For example, in the processing of the MAC layer, the upper layer may include one or more of the RRC layer, RLC layer, PDCP layer, NAS layer, etc. Hereinafter, the meaning of "A is provided in the upper layer" or "A is provided by the upper layer" may mean that the upper layer (mainly the RRC layer, MAC layer, etc.) of the terminal device 1 receives A from the base station device 3, and the received A is provided from the upper layer of the terminal device 1 to the physical layer of the terminal device 1. For example, in the terminal device 1, "an upper layer parameter is provided" may mean that the terminal device 1 receives an upper layer signal from the base station device 3, and the upper layer parameter included in the received upper layer signal is provided from the upper layer of the terminal device 1 to the physical layer of the terminal device 1. That the upper layer parameter is set in the terminal device 1 may also mean that the upper layer parameter is provided to the terminal device 1.For example, the setting of the upper layer parameters in the terminal device 1 may mean that the terminal device 1 receives an upper layer signal from the base station device 3 and sets the received upper layer parameters in the upper layer. However, the setting of the upper layer parameters in the terminal device 1 may include the setting of default parameters pre - given to the upper layer of the terminal device 1.

[0076] 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 a plurality of terminal devices 1 within the cell. Also, the RRC signaling transmitted from the base station device 3 may be dedicated signaling (also referred to as dedicated signaling) for a certain terminal device 1. That is, UE - specific information may be transmitted using dedicated signaling for a certain terminal device 1. Also, the PUSCH may be used to transmit the UE's capability in the uplink.

[0077] In FIG. 1, in downlink wireless communication, the following downlink physical signals are used. Here, the downlink physical signals are not used to transmit information output from the upper layer, but are used by the physical layer. · Synchronization signal (SS) · Reference Signal (RS)

[0078] The synchronization signal may include a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS). The cell ID may be detected using the PSS and SSS.

[0079] The synchronization signal is used for the terminal device 1 to achieve synchronization in the downlink frequency domain and time domain. Here, the synchronization signal may be used by the terminal device 1 for precoding or beam selection in precoding or beamforming by the base station device 3. Note that the beam may also be referred to as a transmission or reception filter setting, or a spatial domain transmission filter or spatial domain reception filter.

[0080] The reference signal is used for 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. Further, the reference signal may be used for fine synchronization such as numerology like radio parameters and subcarrier spacing, and window synchronization of FFT.

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

[0082] DMRS is used to demodulate the modulated signal. Note that two types of reference signals may be defined for DMRS, i.e., the reference signal for demodulating PBCH and the reference signal for demodulating PDSCH, or both may be referred to as DMRS. CSI-RS is used for the measurement of channel state information (CSI) and beam management, and the transmission method of periodic or semi-persistent or aperiodic CSI reference signals is applied. For CSI-RS, non-zero power (NZP) CSI-RS and CSI-RS with zero transmission power (or reception power) (zero power (ZP) CSI-RS) may be defined. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or not transmitted. PTRS is used to track the phase on the time axis for the purpose of guaranteeing the frequency offset caused by phase noise. TRS is used to guarantee the Doppler shift during high-speed movement. Note that TRS may be used as one setting of CSI-RS. For example, the radio resource of 1-port CSI-RS may be set as TRS.

[0083] 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)

[0084] DMRS is used to demodulate the modulated signal. Note that two types of reference signals may be defined for DMRS, i.e., the reference signal for demodulating PUCCH and the reference signal for demodulating PUSCH, or both may be referred to as DMRS. SRS is used for the measurement of uplink channel state information (CSI), channel sounding, and beam management. PTRS is used to track the phase on the time axis for the purpose of guaranteeing the frequency offset caused by phase noise.

[0085] In this embodiment, the downlink physical channel and / or the downlink physical signal are generally referred to as the downlink signal. In this embodiment, the uplink physical channel and / or the uplink physical signal are generally referred to as the uplink signal. In this embodiment, the downlink physical channel and / or the uplink physical channel are generally referred to as the physical channel. In this embodiment, the downlink physical signal and / or the uplink physical signal are generally referred to as the physical signal.

[0086] BCH, UL-SCH, and DL-SCH are transport channels. The channels used in the Medium Access Control (MAC) layer are referred to as transport channels. The unit of the transport channel used in the MAC layer is also referred to as 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 the unit of data that the MAC layer delivers to the physical layer. In the physical layer, the transport block is mapped to codewords, and channel coding is performed for each codeword.

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

[0088] The SS / PBCH block may be a block including synchronization signals (PSS, SSS), PBCH, and DMRS for PBCH. However, the SS / PBCH block may also be a block including synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for REDCAP PBCH. Transmitting the signals / channels included in the SS / PBCH block is expressed as transmitting the SS / PBCH block. When the base station device 3 transmits synchronization signals and / or PBCH using one or more SS / PBCH blocks within the SS burst set, independent downlink transmission beams may be used for each SS / PBCH block.

[0089] The base station device 3 according to this embodiment transmits the REDCAP PBCH and the DMRS for the REDCAP PBCH in time resources different from and / or frequency resources different from those of the SS / PBCH block. However, in this 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 the signal / channel included in the REDCAP PBCH block may be expressed as transmitting the REDCAP PBCH block. When the base station device 3 transmits the REDCAP PBCH using one or more REDCAP PBCH blocks within a predetermined time interval (which may also be referred to as a REDCAP PBCH burst set), independent downlink transmission beams may be used for each REDCAP PBCH block. However, the REDCAP PBCH block according to this embodiment may be the REDCAP PBCH and / or the DMRS itself for the REDCAP PBCH. For example, transmitting / receiving / processing the REDCAP PBCH block may be transmitting / receiving / processing the REDCAP PBCH and / or the DMRS for the REDCAP PBCH. However, the REDCAP PBCH and / or the DMRS for the REDCAP PBCH according to this embodiment may be the REDCAP PBCH and / or the DMRS for the REDCAP PBCH transmitted outside the SS / PBCH block. For example, the REDCAP PBCH and / or the DMRS for the REDCAP PBCH may be the REDCAP PBCH and / or the DMRS for the REDCAP PBCH transmitted in time and / or frequency resources different from those of the SS / PBCH block transmitted periodically in the SSB period. However, the REDCAP PBCH block according to this embodiment may be an SS / PBCH block without PSS and / or SSS.

[0090] The REDCAP PBCH block and / or REDCAP PBCH according to this embodiment is associated with one SS / PBCH block transmitted within an SS burst set (Half frame with SS / PBCH block). The transport block transmitted by the REDCAP PBCH and the transport block transmitted by the PBCH within the corresponding SS / PBCH block may be the same.

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

[0092] However, a block including the synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for REDCAP PBCH may be defined as a different block distinct from the SS / PBCH block. For example, a block including the synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for 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 regarding the SS / PBCH block according to this embodiment may also be applied to the REDCAP SS / PBCH block.

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

[0094] PSS may be mapped to the first symbol within the SS / PBCH block (the OFDM symbol with an OFDM symbol number of 0 relative to the start symbol of the SS / PBCH block). The sequence of PSS consists of 127 symbols and may be mapped to the 57th subcarrier to the 183rd subcarrier within the SS / PBCH block (subcarriers with subcarrier numbers of 56 to 182 relative to the start subcarrier of the SS / PBCH block).

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

[0096] PBCH and DMRS may be mapped to the second, third, and fourth symbols within the SS / PBCH block (the OFDM symbols with OFDM symbol numbers of 1, 2, and 3 relative to the start symbol of the SS / PBCH block). The sequence of modulation symbols of PBCH is M symbIt may be mapped to a resource where DMRS is not mapped among the symbols, from the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 with respect to the start sub - carrier of the SS / PBCH block) of the second and fourth symbols in the SS / PBCH block, and from the first sub - carrier to the 48th sub - carrier and from the 184th to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 47 and from 192 to 239 with respect to the start sub - carrier of the SS / PBCH block) of the third symbol in the SS / PBCH block. The series of symbols of DMRS is composed of 144 symbols, and may be mapped one sub - carrier every 4 sub - carriers to the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 with respect to the start sub - carrier of the SS / PBCH block) of the second and fourth symbols in the SS / PBCH block, and from the first sub - carrier to the 48th sub - carrier and from the 184th to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 47 and from 192 to 239 with respect to the start sub - carrier of the SS / PBCH block) of the third symbol in the SS / PBCH block. For example, for 240 sub - carriers, modulation symbols of PBCH may be mapped to 180 of them, and DMRS for the PBCH may be mapped to 60 of them.

[0097] Different SSB indexes may be assigned to different SS / PBCH blocks within an SS burst set. The SS / PBCH block to which a certain SSB index is assigned 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 set for the connected (Connected or RRC_Connected) terminal device 1 may be defined. Also, the SSB period set for the connected (Connected or RRC_Connected) terminal device 1 may be set by an RRC parameter. Also, the SSB period set for the connected (Connected or RRC_Connected) terminal device 1 is the period of radio resources in the time domain where transmission may potentially occur, and actually, the base station device 3 may decide whether to transmit or not. Also, 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 regard the SSB period as 20 milliseconds.

[0098] The time position of the SS burst set to which the SS / PBCH block is mapped may be specified based on information specifying the system frame number (SFN: System Frame Number) included in the PBCH and / or information specifying the half frame. The terminal device 1 that has received the SS / PBCH block may specify the current system frame number and the half frame based on the received SS / PBCH block.

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

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

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

[0102] 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 of SS / PBCH blocks (quantity) within an SS burst, or within an SS burst set, or within the period of an SS / PBCH block. Also, the number of SS / PBCH blocks may indicate the number of beam groups for cell selection within an SS burst, or within an SS burst set, or within the period of an SS / PBCH block. Here, a beam group may be defined as the number of different SS / PBCH blocks or the number of different beams included within an SS burst, or within an SS burst set, or within the period (SSB period) of an SS / PBCH block.

[0103] The REDCAP PBCH according to this embodiment is transmitted in OFDM symbols associated with the corresponding SS / PBCH block or the corresponding synchronization signal (PSS, SSS).

[0104] The time position relationship between the REDCAP PBCH according to this embodiment and the corresponding SS / PBCH block may be determined by the time position relationship between the half-frame including the REDCAP PBCH and the 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 within the half-frame including the REDCAP PBCH and the time position of the SS / PBCH block within the half-frame including the corresponding SS / PBCH block may be the same.

[0105] The starting sub-carrier of the REDCAP PBCH according to this embodiment may be a sub-carrier with a predetermined frequency offset added to the starting sub-carrier of the corresponding SS / PBCH block. However, when the value obtained by adding the frequency offset exceeds a certain value, the value obtained by subtracting the certain value may be used as the starting sub-carrier of the REDCAP PBCH. For example, when the value obtained by adding a predetermined frequency offset to the starting sub-carrier of the corresponding SS / PBCH block exceeds the bandwidth available for allocating the REDCAP PBCH, the value obtained by subtracting the bandwidth of the REDCAP PBCH allocable band from the value may be used as the starting sub-carrier of the REDCAP PBCH.

[0106] FIG. 11 is a diagram showing an example of a half frame in which a REDCAP PBCH block 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 an SS / PBCH block existing at a fixed period (SSB period), and the REDCAP PBCH block is composed of three consecutive OFDM symbols. The REDCAP PBCH block is transmitted in a resource corresponding to one SS / PBCH block, and REDCAP PBCH or DMRS for REDCAP PBCH exists in all resources within the REDCAP PBCH block. FIG. 12 is a table showing an example of resources in which REDCAP PBCH and DMRS for REDCAP PBCH are arranged within the REDCAP PBCH block. For example, the series of modulation symbols of REDCAP PBCH is M symb2It may be mapped to resources where DMRS for REDCAP PBCH is not mapped among the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 relative to the start sub - carrier of the REDCAP PBCH block) of each of the three symbols within the REDCAP PBCH block, which is composed of symbols. The symbol sequence of DMRS for REDCAP PBCH is composed of 180 symbols and may be mapped one sub - carrier at a time for every 4 sub - carriers with respect to the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 relative to the start sub - carrier of the REDCAP PBCH block) of the three symbols within the REDCAP PBCH block. However, the number of symbols constituting the REDCAP PBCH block may not be 3 symbols. For example, the REDCAP PBCH block may be composed of 4 symbols, and for the 240 sub - carriers of each symbol, REDCAP PBCH or DMRS for REDCAP PBCH may exist. However, the number of sub - carriers constituting the REDCAP PBCH block may not be 240 sub - carriers. For example, the REDCAP PBCH block may be composed of 180 sub - carriers and 4 OFDM symbols, and for the 180 sub - carriers of each symbol, REDCAP PBCH or DMRS for REDCAP PBCH may exist.

[0107] FIG. 13 is a diagram showing an example of a REDCAP PBCH block according to this embodiment. FIG. 13 shows an example where a REDCAP PBCH block exists within a half - frame including an SS / PBCH block that exists at a fixed period (SSB period), and the REDCAP PBCH block is composed of 4 consecutive OFDM symbols. The REDCAP PBCH block is transmitted in the resources corresponding to one SS / PBCH block, and REDCAP PBCH or DMRS for REDCAP PBCH exists in all resources within the REDCAP PBCH block. For example, the modulation symbol sequence of REDCAP PBCH is M symb2It may be mapped to a resource composed of symbols and not mapped with DMRS for REDCAP PBCH among the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 with respect to the start sub - carrier of the REDCAP PBCH block) of each of the 4 symbols within the REDCAP PBCH block. The symbol sequence of DMRS for REDCAP PBCH is composed of 240 symbols and may be mapped one sub - carrier at a time for every 4 sub - carriers with respect to the first sub - carrier to the 240th sub - carrier (sub - carriers with sub - carrier numbers from 0 to 239 with respect to the start sub - carrier of the REDCAP PBCH block) of the 4 symbols within the REDCAP PBCH block. However, neither REDCAP PBCH nor DMRS for REDCAP PBCH may exist for all resources within the REDCAP PBCH block. For example, the REDCAP PBCH block may be composed of 4 symbols, and 1 of them may be set to 0.

[0108] FIG. 14 is a diagram showing another example of the REDCAP PBCH block according to this embodiment. FIG. 14 shows an example where the REDCAP PBCH block exists in some slots within a half - frame including SS / PBCH blocks existing at a fixed period (SSB period), and the REDCAP PBCH block is composed of 4 consecutive OFDM symbols. However, the slot where the REDCAP PBCH block is arranged may be a slot that does not include candidate resources for the SS / PBCH block. The REDCAP PBCH block is transmitted in the resources corresponding to one SS / PBCH block, and REDCAP PBCH or DMRS for REDCAP PBCH exists for all resources within the REDCAP PBCH block. For example, the modulation symbol sequence of REDCAP PBCH is M symb2It may be mapped to the resources composed of symbols and not mapped with DMRS for REDCAP PBCH among the 1st sub-carrier to the 240th sub-carrier (sub-carriers with sub-carrier numbers from 0 to 239 with respect to the start sub-carrier of the REDCAP PBCH block) of each of the 4 symbols within the REDCAP PBCH block. The symbol sequence of DMRS for REDCAP PBCH is composed of 240 symbols and may be mapped one by one for every 4 sub-carriers to the 1st sub-carrier to the 240th sub-carrier (sub-carriers with sub-carrier numbers from 0 to 239 with respect to the start sub-carrier of the REDCAP PBCH block) of the 4 symbols within the REDCAP PBCH block. However, there may be no REDCAP PBCH or DMRS for REDCAP PBCH for all the resources within the REDCAP PBCH block. For example, the REDCAP PBCH block is composed of 4 symbols, 1 of which is set to 0, and REDCAP PBCH and DMRS for REDCAP PBCH may exist in the remaining 3 symbols.

[0109] One or more REDCAP PBCH blocks within the half-frame (REDCAP PBCH burst set) containing REDCAP PBCH may be assigned different SSB indexes. The REDCAP PBCH block assigned with a certain SSB index is associated with the SS / PBCH block of the said SSB index and may be transmitted periodically by the base station device 3. However, there may be multiple REDCAP PBCH blocks assigned with the same SSB index for one SS / PBCH block. For example, within the SSB period, the REDCAP PBCH blocks assigned with the same SSB index may be transmitted multiple times.

[0110] The time position of the half-frame in which the REDCAP PBCH block is mapped may be determined based on information identifying the SFN included in the PBCH of the corresponding SS / PBCH block and / or the REDCAP PBCH of the REDCAP PBCH block and / or information identifying the half-frame, and the time offset between the corresponding SS / PBCH block and the REDCAP PBCH block. However, the information identifying the SFN included in the REDCAP PBCH of the REDCAP PBCH block and / or the information identifying the half-frame 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 identify the SFN and half-frame in which the corresponding SS / PBCH block is transmitted based on the received REDCAP PBCH block.

[0111] The SSB index is assigned to the REDCAP PBCH block according to its temporal position within the transmitted half-frame. The terminal device 1 identifies the SSB index based on the information of the REDCAP PBCH and / or the information of the reference signal included in the detected REDCAP PBCH block.

[0112] SS / PBCH blocks with the same relative time within each SS burst set in a plurality of SS burst sets may be assigned the same SSB index. It may be assumed that SS / PBCH blocks with the same relative time within each SS burst set in a plurality of SS burst sets are QCL (or the same downlink transmission beam is applied). Also, it may be assumed that the antenna ports of SS / PBCH blocks with the same relative time within each SS burst set in a plurality of SS burst sets are QCL with respect to average delay, Doppler shift, and spatial correlation.

[0113] Within the period of a certain SS burst set, the SS / PBCH blocks and REDCAP PBCH blocks to which the same SSB index is assigned may be assumed to be QCL with respect to average delay, average gain, Doppler spread, Doppler shift, and spatial correlation.

[0114] The terminal device 1 according to this embodiment receives PSS and SSS in the SS / PBCH block, and receives PBCH within 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 the terminal device 1 having a predetermined capability. For example, a terminal device 1 having a limited capability for purposes such as cost reduction and / or power consumption reduction of the device is referred to as corresponding to REDCAP (Reduction Capability). The terminal device 1 corresponding to REDCAP receives the SS / PBCH block and / or the REDCAP PBCH, and the terminal device 1 not corresponding to REDCAP may receive only the SS / PBCH block and not receive the REDCAP PBCH block.

[0115] The terminal device 1 according to this embodiment may receive an SS / PBCH block in which PSS, SSS, PBCH, and DMRS for PBCH are mapped in a certain radio frame, receive REDCAP PBCH and DMRS for REDCAP PBCH in the same or a different radio frame from the certain radio frame, and acquire the MIB of the transport block transmitted by PBCH and REDCAP PBCH. However, 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 specified based on the MIB and additional bit information.

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

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

[0118] In a certain cell, when the connection state of the terminal device 1 is in the RRC idle state (RRC_IDLE), the RRC inactive state (RRC_INACTIVE), or the RRC connected state (RRC_CONNECTED) in which the timer T311 is running, the terminal device 1 determines whether to consider the cell as a "barred" cell based on the received MIB. However, the 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.

[0119] The terminal device 1 determines that the cell is a restricted 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 restricted (barred). However, the parameter cellBarred may be ignored when the terminal device 1 is a predetermined terminal device (for example, a REDCAP UE). The terminal device 1 determines that the cell is a restricted 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 restricted (barred) for a predetermined terminal device (for example, a REDCAP UE). However, the parameter cellBarred-rc may be ignored when the terminal device 1 is other than a predetermined terminal device (for example, a REDCAP UE). However, the information indicated by the parameter cellBarred-rc may be realized by other parameters included in the MIB. For example, the MIB includes a parameter related to the setting of CORESET0, and when the parameter indicates a predetermined value, the terminal device 1 may determine that the cell is a restricted cell. When none of the parameters included in the received MIB indicates that the cell is a restricted cell, the terminal device 1 may apply other parameters included in the MIB (for example, information indicating the SFN).

[0120] When the terminal device 1 according to this embodiment is not in the RRC connection state (in RRC_CONNECTED while T311 is not running) where the connection state is not during the execution of the timer T311, it determines whether to regard the cell as a "barred" cell based on the parameters of the received SIB1 (which may be REDCAP SIB1).

[0121] The base station apparatus 3 according to the present embodiment transmits SIB1 (which may be REDCAP SIB1) including parameters for determining whether or not the cell in which the terminal device 1 is located is restricted to the terminal device 1.

[0122] When the initial downlink BWP is not provided to the terminal device 1, the initial downlink BWP (initial DL BWP) may be defined by the position and number of consecutive PRBs starting from the PRB with the lowest index to the PRB with the highest index among the PRBs of the CORESET (such as CORESET0) of the Type0-PDCCH CSS Set, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received by the CORESET of the Type0-PDCCH CSS Set. When the initial downlink BWP is provided to the terminal device 1, the initial downlink BWP may be defined by the initial downlink BWP. The terminal device 1 may be configured with a plurality of initial downlink sub-BWPs by SIB1. At least one of the plurality of initial downlink sub-BWPs may be configured to include the SS / PBCH block. The terminal device 1 may operate by regarding the initial downlink sub-BWP including the SS / PBCH block (such as the cell-defining SSB) as the initial downlink BWP. At least one of the plurality of initial downlink sub-BWPs may be configured to include CORESET0. All of the plurality of initial downlink sub-BWPs may be configured to include their respective CORESET0s. The terminal device 1 may operate by regarding the initial downlink sub-BWP including CORESET0 as the initial downlink BWP. The terminal device 1 may operate by regarding the initial downlink sub-BWP as the initial downlink BWP. The plurality of initial downlink sub-BWPs may be regarded as a plurality of initial downlink BWPs. The plurality of initial downlink sub-BWPs may be designed to be included within the frequency band of one initial downlink BWP. The initial downlink sub-BWP may be referred to as the downlink sub-BWP.

[0123] The initial uplink BWP may be defined by initialUplinkBWP. The terminal device 1 may be configured with a plurality of initial uplink sub-BWPs by means of SIB1. At least one of the plurality of initial uplink sub-BWPs may be configured to include resources of the physical random access channel. The terminal device 1 may operate by regarding the initial uplink sub-BWP as the initial uplink BWP. The plurality of initial uplink sub-BWPs may be regarded as a plurality of initial uplink BWPs. The plurality of 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 referred to as the uplink sub-BWP.

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

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

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

[0127] SIB1 may include downlinkConfigCommon, which is the common downlink configuration parameter of a certain cell. At least one of the parameters for determining whether a certain cell is restricted in a certain cell may be included in downlinkConfigCommon, which indicates the common downlink parameters of a certain cell. downlinkConfigCommon may include a parameter indicating the basic parameters related to transmission with one downlink carrier (for example, a parameter called frequencyInfoDL), a parameter indicating the initial downlink BWP configuration of a certain serving cell (for example, a parameter called initialDownlinkBWP), and / or a parameter indicating the configuration of a plurality of initial downlink sub-BWPs (for example, a parameter called initialDownlinkBWP-rc).

[0128] The information element of a BWP may be a parameter indicating the frequency position 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 position and bandwidth (number of resource blocks) in the frequency domain of the BWP, and / or a parameter cyclicPrefix indicating whether a standard CP (cyclic prefix) or an extended CP is used in the BWP. That is, the BWP is defined by the subcarrier spacing, CP, and the position and bandwidth in the frequency domain. However, the value indicated by locationAndBandwidth may be interpreted as a resource indicator value (RIV: Resource Indicator Value). The resource indicator value indicates the starting PRB index of the BWP and the number of consecutive PRBs. However, the first PRB defining the region of the resource indicator value may be a PRB determined by the subcarrier spacing given by the subcarrierSpacing of the BWP and an offsetToCarrier set in the SCS-SpecificCarrier included in the 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.

[0129] Similar to the BWP, the sub-BWP may be defined by the subcarrier spacing, CP, and the position and bandwidth in the frequency domain (such as the number of consecutive resource blocks). The sub-BWP may also be defined by the position and bandwidth in the frequency domain.

[0130] The initialDownlinkBWP includes information elements such as the information element of the BWP, the information element of the PDCCH configuration, and / or the information element of the PDSCH configuration. However, the initial downlink BWP may be configured by the network to include CORESET0 in the frequency domain.

[0131] The initialDownlinkBWP-rc includes information indicating the configuration of the sub-BWP, information elements of the PDCCH configuration, and / or information elements of the PDSCH configuration. The initialDownlinkBWP-rc may be a parameter indicating the configuration of each of a plurality of initial downlink sub-BWPs. However, each of the plurality of initial downlink sub-BWPs configured by the initialDownlinkBWP-rc may be an initial downlink BWP (initial DL BWP). However, each of the plurality of downlink sub-BWPs may be set by the network such that it includes CORESET0 in the frequency domain. The initialDownlinkBWP-rc may include a list of information indicating the position in the frequency domain and the bandwidth in the frequency domain (such as the number of consecutive resource blocks). Each entry in the list of information indicating the frequency position and the bandwidth may correspond to each of the plurality of 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 (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). The plurality of initial downlink sub-BWPs may have a common bandwidth, and the initialDownlinkBWP-rc may indicate a list of the frequency positions of the initial downlink sub-BWPs and the common bandwidth. The plurality of initial downlink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and the initialDownlinkBWP-rc may indicate a list of the frequency positions of the initial downlink BWP, the common bandwidth, the common subcarrierSpacing, and the common cyclicPrefix. Alternatively, the subcarrierSpacing and the cyclicPrefix indicated by the initialDownlinkBWP may be set for the plurality of initial downlink sub-BWPs. That is, the initialDownlinkBWP-rc may be information for specifying the frequency position and the bandwidth of each of the plurality of initial downlink sub-BWPs. However, the parameter indicating the configuration of the plurality of initial downlink sub-BWPs may also be set by the aforementioned initialDownlinkBWP.The parameters indicating the initial downlink BWP configuration of a serving cell may include parameters indicating the frequency position and bandwidth of the initial downlink BWP, the subcarrierSpacing of the initial downlink BWP, the cyclicPrefix of the initial downlink BWP, and parameters indicating the configurations of a plurality of initial downlink sub-BWPs.

[0132] 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 regarding carriers for each subcarrier spacing. 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 regarding carriers for each subcarrier spacing.

[0133] The SCS-SpecificCarrier may include parameters indicating the actual carrier position, bandwidth, and carrier bandwidth. More specifically, the SCS-SpecificCarrier, which is an information element within frequencyInfoDL, indicates 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., indicating 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 the 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, its carrier bandwidth is given by the upper-layer parameter carrierbandwidth within SCS-SpecificCarrier in frequencyInfoDL for each subcarrier spacing, and its starting position in frequency is given by the parameter offsetToCarrier within SCS-SpecificCarrier in frequencyInfoDL for each subcarrier spacing. For example, for an uplink carrier, its carrier bandwidth is given by the upper-layer parameter carrierbandwidth within SCS-SpecificCarrier in frequencyInfoUL for each subcarrier spacing, and its starting position in frequency is given by the parameter offsetToCarrier within SCS-SpecificCarrier in frequencyInfoUL for each subcarrier spacing.

[0134] The terminal device 1 may have a plurality of initial downlink sub-BWPs (initial downlink sub-BWPs) configured by the received SIB1. The terminal device 1 may determine whether the 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 set 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 set by SIB1, the terminal device 1 may regard the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on the bandwidths of the plurality of 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 plurality of initial downlink sub-BWPs set by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth that is the same as or wider than the widest bandwidth among the respective bandwidths of the plurality of initial downlink sub-BWPs set by SIB1, the terminal device 1 may regard 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 that is the same as or wider than the bandwidth commonly set for the plurality of initial downlink sub-BWPs set 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 commonly set for the plurality of initial downlink sub-BWPs set by SIB1, the terminal device 1 may regard 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 that is the same as or wider than the bandwidth specified by the parameters for setting the plurality of initial downlink sub-BWPs notified 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 specified by the parameters for setting a plurality of initial downlink sub - BWPs notified by SIB1, the terminal device 1 may regard 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 that is the same as 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 that is the same as or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may regard the cell as a restricted cell. However, the reference bandwidth may be the bandwidth of one initial downlink BWP notified by SIB1 and the bandwidth specified from the number of multiple - set initial downlink sub - BWPs. However, the reference bandwidth may be the bandwidth specified by dividing one initial downlink BWP notified by SIB1 by a predetermined number.

[0135] 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 regard the cell as a restricted cell. However, the carrier bandwidth may be the carrier bandwidth corresponding to the sub - carrier spacing of the initial downlink BWP set in the received SIB1. However, the carrier bandwidth may be the carrier bandwidth corresponding to the sub - carrier spacing common to a plurality of initial downlink sub - BWPs set in the received SIB1.

[0136] FIG. 16 is a flowchart showing an example of a determination process of a regulated cell based on a plurality of initial downlink sub BWPs in the terminal device 1 of the present embodiment. In step S1001 of FIG. 16, the terminal device 1 determines whether it is in an RRC connected state (RRC_CONNECTED) where the connection state is not during the execution of timer T311. If the determination is negative (S1001-No), in step S1002, it is determined whether it supports a downlink channel bandwidth that is the same as or wider than the widest bandwidth among the plurality of initial downlink sub BWPs set in SIB1. If the determination is negative, the terminal device 1 regards the cell as a regulated cell (S1003).

[0137] SIB1 may include uplinkConfigCommon, which is a common downlink configuration parameter of a certain cell. At least one of the parameters for the terminal device 1 to determine whether a certain cell is regulated may be included in uplinkConfigCommon, which indicates the common uplink parameter of a certain cell. uplinkConfigCommon may include a parameter (for example, referred to as frequencyInfoUL) indicating basic parameters related to transmission with one uplink carrier, a parameter (for example, referred to as initialUplinkBWP) indicating the initial uplink BWP setting of a certain serving cell, and / or a parameter (for example, referred to as initialUplinkBWP-rc) indicating the settings of a plurality of initial uplink sub BWPs.

[0138] The initialUplinkBWP includes information elements of the BWP, information elements of the PDCCH setting, and / or information elements of the PDSCH setting, etc. However, the initial uplink BWP may be set by the network to include physical random access channel resources in the frequency domain.

[0139] The initialUplinkBWP-rc includes information indicating the configuration of the sub-BWP, information elements of PUCCH configuration, and / or information elements of PUSCH configuration. The initialUplinkBWP-rc may be a parameter indicating the configuration of each of a plurality of initial uplink sub-BWPs. However, each of the plurality of initial uplink sub-BWPs configured by the initialUplinkBWP-rc may be an initial uplink BWP (initial UL BWP). However, each of the plurality of uplink sub-BWPs may be configured by the network such that it includes physical random access channel resources in the frequency domain. The initialUplinkBWP-rc may include a list of information indicating frequency positions and bandwidths. Each entry in the list of information indicating frequency positions and bandwidths may correspond to each of the plurality of initial uplink sub-BWPs. Each entry in the list of information indicating frequency positions and bandwidths may be an information element of the BWP (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). The plurality of initial uplink sub-BWPs may have a common bandwidth, and the initialUplinkBWP-rc may indicate a list of frequency positions of the initial uplink sub-BWPs and the common bandwidth. The plurality of initial uplink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and the initialUplinkBWP-rc may indicate a list of frequency positions of the initial uplink BWP, the common bandwidth, the common subcarrierSpacing, and the common cyclicPrefix. Alternatively, the subcarrierSpacing and the cyclicPrefix indicated by the initialUplinkBWP may be set for the plurality of initial uplink sub-BWPs. That is, the initialUplinkBWP-rc may be information for specifying the frequency position and bandwidth of each of the plurality of initial uplink sub-BWPs. However, the parameter indicating the configuration of the plurality of initial uplink sub-BWPs may also be set by the aforementioned initialUplinkBWP.The parameters indicating the initial uplink BWP configuration of a serving cell may include parameters indicating the frequency position and bandwidth of the initial uplink BWP, the subcarrier spacing of the initial uplink BWP, the cyclic prefix of the initial uplink BWP, and parameters indicating the configurations of a plurality of initial uplink sub-BWPs.

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

[0141] The terminal device 1 may have a plurality of initial uplink sub-BWPs (initial uplink sub-BWP) set by the received SIB1. The terminal device 1 may determine whether the cell is a restricted cell based on the bandwidth of the initial uplink BWP set 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 an uplink bandwidth that is the same as or wider than the bandwidth of the initial uplink BWP 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 of the initial uplink BWP set by SIB1, the terminal device 1 may regard the cell as a restricted cell. The terminal device 1 may determine whether the cell is a restricted cell based on the bandwidths of the plurality of initial uplink sub-BWPs set 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 an uplink bandwidth that is the same as or wider than the widest bandwidth among the respective bandwidths of the plurality of 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 respective bandwidths of the plurality of initial uplink sub-BWPs set by SIB1, the terminal device 1 may regard 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 the same as or wider than the bandwidth commonly set for the plurality of 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 plurality of initial uplink sub-BWPs set by SIB1, the terminal device 1 may regard 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 the same as or wider than the bandwidth specified by the parameters for setting the plurality of initial uplink sub-BWPs notified 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 specified by the parameters for setting a plurality of initial uplink sub-BWPs notified by SIB1, the terminal device 1 may regard 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 the same as 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 the same as or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may regard the cell as a restricted cell. However, the reference bandwidth may be the bandwidth of one initial uplink BWP notified by SIB1 and the bandwidth specified from the number of multiple configured initial uplink sub-BWPs. However, the reference bandwidth may be the bandwidth specified by dividing one initial uplink BWP notified by SIB1 by a predetermined number.

[0142] 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 regard the cell as a restricted cell. However, the carrier bandwidth may be the carrier bandwidth corresponding to the sub-carrier spacing of the initial uplink BWP set in the received SIB1. However, the carrier bandwidth may be the carrier bandwidth corresponding to the sub-carrier spacing common to a plurality of initial uplink sub-BWPs set in the received SIB1.

[0143] 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 certain cell, the bandwidths of a plurality of initial downlink sub-BWPs set by the received SIB1 corresponding to a certain cell, the bandwidth of the initial uplink BWP set by the received SIB1 corresponding to a certain cell, the bandwidths of a plurality of initial uplink sub-BWPs set by the received SIB1 corresponding to a certain cell, the carrier bandwidth set by the received SIB1 corresponding to a certain cell, and / or the capabilities of the terminal device 1.

[0144] However, the parameters set in SIB1 may be notified in SIB1 (or REDCAP SIB1), may be notified in other SIBs (or REDCAP SIBs), or may be notified in an RRC message.

[0145] FIG. 17 is a flowchart showing an example of the determination process of a restricted cell based on a plurality of initial uplink sub-BWPs in the terminal device 1 of the present embodiment. In step S2001 of FIG. 17, the terminal device 1 determines whether it is in an RRC connection state (RRC_CONNECTED) where the connection state is not during the execution of timer T311. If the determination is negative (S2001-No), in step S2002, it is determined whether it supports an uplink channel bandwidth that is the same as or wider than the widest bandwidth among the plurality of initial uplink sub-BWPs set in SIB1. If the determination is negative, the terminal device 1 regards the cell as a restricted cell (S2003).

[0146] Hereinafter, the reference signals described in this embodiment include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DMRS, CSI-RS, uplink reference signals, SRS, and / or uplink DMRS. For example, in this embodiment, the downlink reference signals, synchronization signals, and / or SS / PBCH blocks may be referred to as reference signals. The reference signals used in the downlink include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DMRS, CSI-RS, etc. The reference signals used in the uplink include uplink reference signals, SRS, and / or uplink DMRS, etc.

[0147] Also, the reference signals may be used for Radio Resource Measurement (RRM). Also, the reference signals may be used for beam management.

[0148] Beam management may be a procedure of the base station device 3 (in the case of the downlink) or the terminal device 1 (in the case of the uplink) to align the directivities of analog and / or digital beams at the transmitting device with those of analog and / or digital beams at the receiving device (the terminal device 1 in the case of the downlink and the base station device 3 in the case of the uplink) to obtain beam gain.

[0149] Note that the procedures for configuring, setting, or establishing a beam pair link may include the following procedures. · Beam selection · Beam refinement · Beam recovery

[0150] For example, beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1. Further, beam improvement may be a procedure for selecting a beam with a higher gain or changing the beam between the optimal base station device 3 and the terminal device 1 due to the movement of the terminal device 1. Beam recovery may be a procedure for reselecting a beam when the quality of the communication link deteriorates due to blockage caused by a shielding object or the passage of a person in communication between the base station device 3 and the terminal device 1.

[0151] Beam management may include beam selection and beam improvement. Beam recovery may include the following procedures. · Detection of beam failure · Discovery of a new beam · Transmission of a beam recovery request · Monitoring of the response to the beam recovery request

[0152] For example, when selecting the 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 the SS / PBCH block may be used, or CSI may be used. Also, as a report to the base station device 3, a CSI-RS resource index (CRI: CSI-RS Resource Index) may be used, or an index indicated by a sequence of a demodulation reference signal (DMRS) used for demodulation of the PBCH and / or PBCH included in the SS / PBCH block may be used.

[0153] In addition, when the base station device 3 instructs the terminal device 1 to use a beam, it indicates the time index of the CRI or SS / PBCH, and the terminal device 1 receives based on the indicated time index of the CRI or SS / PBCH. At this time, the terminal device 1 may set and receive a spatial filter based on the indicated time index of the CRI or SS / PBCH. Also, the terminal device 1 may receive using the assumption of Quasi Co-Location (QCL). That a certain signal (such as an antenna port, synchronization signal, reference signal, etc.) is "QCL with" or "the assumption of QCL is used for" another signal (such as an antenna port, synchronization signal, reference signal, etc.) may be interpreted as meaning that a certain signal is associated with another signal.

[0154] If the long-term properties of the channel carried by a certain symbol at one antenna port can be inferred from the channel carried by a certain symbol at the other antenna port, the two antenna ports are said to be QCL. 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, when antenna port 1 and antenna port 2 are QCL with respect to the average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1.

[0155] This QCL can also be extended to beam management. For this purpose, a spatially extended QCL may be newly defined. For example, as the long-term property of a channel in the assumption of a spatial-domain QCL, the angle of arrival (AoA, ZoA, etc.) and / or angle spread (such as ASA, ZSA) in a wireless link or channel, the angle of departure (AoD, ZoD, etc.) and its angle spread (such as ASD, ZSD), spatial correlation, and received spatial parameters may be considered.

[0156] For example, when it can be considered that there is QCL with respect to received spatial parameters between antenna port 1 and antenna port 2, it means that the receive beam (receive spatial filter) for receiving the signal from antenna port 1 can infer the receive beam for receiving the signal from antenna port 2.

[0157] As QCL types, combinations of long-term properties that may be considered as QCL may be defined. For example, the following types may be defined. · Type A: Doppler shift, Doppler spread, average delay, delay spread · Type B: Doppler shift, Doppler spread · Type C: Average delay, Doppler shift · Type D: Received spatial parameters

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

[0159] In this way, as beam management and beam indication / reporting, the operations of the base station device 3 and the terminal device 1 equivalent to beam management may be defined by the assumption of QCL in the spatial domain and radio resources (time and / or frequency).

[0160] FIG. 18 is a diagram showing an example of beamforming. A plurality of antenna elements are connected to one transmission unit (TXRU: Transceiver unit) 50, and the phase is controlled by a phase shifter 51 for each antenna element, and a beam can be directed in an arbitrary direction with respect to the transmission signal 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 an arbitrary direction by controlling the phase shifter 51, the base station device 3 can communicate with the terminal device 1 using a beam with high gain.

[0161] Hereinafter, the configuration of the device in the present embodiment will be described.

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

[0163] The upper layer processing unit 14 outputs uplink data (which may also be referred to as a transport block) generated by a user operation or the like to the wireless transceiver unit 10. The upper layer processing unit 14 performs part or all of the processing of the Medium Access Control (MAC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function of acquiring bit information of the Master Information Block (which may be the REDCAP MIB), System Information Block Type 1 (which may be the REDCAP SIB1), and other System Information Blocks (which may be the REDCAP SIB). The upper layer processing unit 14 may have a function of determining the number of repeated transmissions of the Physical Downlink Control Channel (PDCCH) transmitted in the common search space set. The upper layer processing unit 14 may have a function of determining whether a cell is a restricted cell based on the information of the System Information Block (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB).

[0164] The Medium Access Control layer processing unit 15 included in the upper layer processing unit 14 performs the 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.

[0165] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 performs the processing of the RRC layer (radio resource control layer). The radio resource control layer processing unit 16 manages various setting information / parameters of the own device. The radio resource control layer processing unit 16 sets various setting information / parameters based on the upper layer 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 the information indicating various setting information / parameters received from the base station device 3. The radio resource control layer processing unit 16 controls (specifies) resource allocation based on the downlink control information received from the base station device 3.

[0166] The radio transceiver unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The radio transceiver unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The radio transceiver unit 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3 or the like. The radio transceiver unit 10 outputs the upper layer signals (RRC messages), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. Further, the radio transceiver unit 10 generates and transmits an uplink signal (including PUCCH and / or PUSCH) based on an instruction from the upper layer processing unit 14. The radio transceiver unit 10 may have a function of receiving PDCCH and / or PDSCH. The radio transceiver unit 10 may have a function of transmitting one or more PUCCH and / or PUSCH. The radio transceiver unit 10 may have a function of receiving DCI by PDCCH. The radio transceiver unit 10 may have a function of outputting the DCI received by PDCCH to the upper layer processing unit 14. The radio transceiver unit 10 may have a function of receiving PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The radio transceiver unit 10 may have a function of receiving an SS / PBCH block and / or a REDCAP PBCH block. The radio transceiver unit 10 may have a function of receiving a system information block (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB) corresponding to a predetermined cell.

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

[0168] The baseband unit 13 converts the analog signal input from the RF unit 12 from an analog signal to a digital signal. The baseband unit 13 removes the portion corresponding to the CP (Cyclic Prefix) from the converted digital signal, performs a Fast Fourier Transform (FFT) on the signal with the CP removed, and extracts the signal in the frequency domain.

[0169] The baseband unit 13 performs an Inverse Fast Fourier Transform (IFFT) on the data to generate an OFDM symbol, adds a CP to the generated OFDM symbol to generate 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.

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

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

[0172] The upper layer processing unit 34 performs part 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 and the like to the radio transmission / reception unit 30. The upper layer processing unit 34 may have a function of generating the bit information of the transport block of the MIB. The upper layer processing unit 34 may have a function of generating the 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 determining whether a predetermined cell is a restricted cell for the terminal device.

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

[0174] The radio resource control layer processing unit 36 included in the upper layer processing unit 34 performs the 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, or obtains from an upper node, DCI, downlink data (transport block (TB), random access response (RAR)) arranged in the PDSCH, system information, RRC message, MAC CE (Control Element), etc., and outputs them to the radio transceiver unit 30. Further, the radio resource control layer processing unit 36 manages various setting information / parameters of each of the terminal devices 1. The radio resource control layer processing unit 36 may set various setting information / parameters for each of the terminal devices 1 via a signal from the upper layer. That is, the radio resource control layer processing unit 36 transmits / informs information indicating various setting information / parameters. The radio resource control layer processing unit 36 may transmit / inform information for specifying the setting of one or more reference signals in a certain cell.

[0175] When the base station device 3 transmits an RRC message, MAC CE, and / or PDCCH to the terminal device 1 and the terminal device 1 performs processing based on the reception, the base station device 3 performs processing (control of the terminal device 1 and the system) assuming that the terminal device is performing the processing. That is, the base station device 3 sends an RRC message, MAC CE, and / or PDCCH to the terminal device 1 to cause the terminal device to perform processing based on the reception.

[0176] The radio transceiver unit 30 transmits signals at the upper layer (RRC messages), DCI, etc. to the terminal device 1. Also, the radio transceiver unit 30 receives the uplink signal transmitted from the terminal device 1 based on an instruction from the upper layer processing unit 34. The radio transceiver unit 30 may have a function of transmitting PDCCH and / or PDSCH. The radio transceiver unit 30 may have a function of receiving one or more PUCCHs and / or PUSCHs. The radio transceiver unit 30 may have a function of transmitting DCI by PDCCH. The radio transceiver unit 30 may have a function of transmitting the DCI output by the upper layer processing unit 34 by PDCCH. The radio transceiver unit 30 may have a function of transmitting PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The radio transceiver unit 30 may have a function of transmitting an SS / PBCH block and / or a REDCAP PBCH block. The radio transceiver unit 30 may have a function of transmitting an RRC message (which may be an RRC parameter). The radio transceiver unit 30 may have a function of the terminal device 1 transmitting a system information block (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB). In addition, some functions of the radio transceiver unit 30 are the same as those of the radio transceiver unit 10, so the description is omitted. 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 radio transceiver unit 30 may be included in each transmission / reception point 4.

[0177] Also, the upper layer processing unit 34 transmits (forwards) or receives control messages or user data between base station devices 3 or between a higher-level network device (MME, S-GW (Serving-GW)) and the base station device 3. In FIG. 20, other components of the base station device 3 and the data (control information) transmission paths between the components are omitted, but it is obvious that the base station device 3 has a plurality of blocks having other functions necessary for operating as the base station device 3 as components. For example, in the upper layer processing unit 34, there are a radio resource management layer processing unit and an application layer processing unit.

[0178] Note that the "section" in the figure is an element that realizes the functions and respective procedures of the terminal device 1 and the base station device 3, which can also be expressed by terms such as section, circuit, constituent device, device, unit, etc.

[0179] Each of the sections labeled with reference numerals 10 to 16 included in the terminal device 1 may be configured as a circuit. Each of the sections labeled with reference numerals 30 to 36 included in the base station device 3 may be configured as a circuit.

[0180] (1) The terminal device 1 in the 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 the information in the first system information block. The processing unit 14 determines that the first cell is 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 the bandwidths of a plurality of downlink BWPs (initial DL BWPs) set by the first system information block.

[0181] (2) In the first aspect of the present invention, the processing unit 14 may determine that the first cell is a barred 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.

[0182] (3) In the first aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set with respect to a subcarrier interval commonly set for the plurality of downlink BWPs.

[0183] (4) The base station apparatus 3 in the second aspect of the present invention includes a processing unit 34 that generates a first system information block (SIB1) including information for determining whether the first cell is a barred cell by the terminal device 1, and a transmission unit 30 that transmits the first system information block. The information includes information for setting a plurality of downlink BWPs (initial DL BWPs), and when the terminal device 1 does not support a downlink channel bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the plurality of downlink BWPs, the information is information that causes the terminal device 1 to consider the first cell as a barred cell.

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

[0185] (6) In the second aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set with respect to a subcarrier spacing commonly set for the plurality of downlink BWPs.

[0186] (7) The terminal device 1 in the 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 the information in the first system information block. When the terminal device 1 does not support an uplink channel bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the plurality of uplink BWPs (initial UL BWPs) set by the first system information block, the processing unit 14 considers the first cell as a barred cell.

[0187] (8) In a third aspect of the present invention, 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, the processing unit 14 may regard the first cell as a restricted cell.

[0188] (9) In a third aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set with respect to a subcarrier spacing that is commonly set for the plurality of uplink BWPs.

[0189] (10) The 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 determining whether the first cell is a barred cell for the terminal device 1, and a transmission unit 30 that transmits the first system information block. The information includes information for setting a plurality of uplink BWPs (initial UL BWPs). When the terminal device 1 does not support an uplink channel bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of the plurality of uplink BWPs, the information is information for which the first cell is regarded as a barred cell for the terminal device 1.

[0190] (11) In a fourth aspect of the present invention, the information may include information for setting the carrier bandwidth of the first cell, and when the terminal device 1 does not support an uplink channel bandwidth that is the same as or narrower than the carrier bandwidth, the information is information for which the first cell is regarded as a barred cell.

[0191] (12) In a fourth aspect of the present invention, the carrier bandwidth may be a carrier bandwidth set with respect to a subcarrier spacing that is commonly set for the plurality of uplink BWPs.

[0192] As a result, the terminal device 1 and the base station device 3 can communicate efficiently. For example, when the terminal device 1 receives a system information block for a cell in which a downlink channel bandwidth and / or an uplink channel bandwidth that it does not support is set, it can be regarded as a restricted cell and avoid camping.

[0193] A program that operates on a device according to an aspect of the present invention may be a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the embodiments according to an aspect of the present invention. The program or information handled by the program may be 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 other storage device systems.

[0194] In addition, a program for realizing the functions of the embodiments according to an aspect of the present invention may be recorded on a computer-readable recording medium. The functions may be realized by reading the program recorded on this recording medium into a computer system and executing it. Here, the "computer system" refers to a computer system built in a device and including hardware such as an operating system and peripheral devices. Further, the "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that temporarily holds a program, or any other recording medium readable by a computer.

[0195] In addition, each functional block or various features of the apparatus used in the above-described embodiments can be implemented or executed by an electric circuit, for example, an integrated circuit or a plurality of integrated circuits. The electric circuit designed to execute the functions described in this specification may include a general-purpose use processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose use processor may be a microprocessor, or may be a conventional type processor, controller, microcontroller, or state machine. The above-described electric circuit may be composed of a digital circuit or an analog circuit. Further, when an integrated circuit technology that replaces the current integrated circuit appears due to the progress of semiconductor technology, one or more aspects of the present invention can also use a new integrated circuit based on such technology.

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

[0197] Note that the present invention is not limited to the above-described embodiments. In the embodiments, an example of the apparatus has been described, but the present invention is not limited thereto, and it can also be applied to a stationary or non-mobile electronic device installed indoors or outdoors, for example, a terminal device or a communication device such as an AV device, a kitchen device, a cleaning / washing device, an air conditioning device, an office device, a vending machine, or other living devices.

[0198] As described above in detail with reference to the drawings regarding the embodiments of the present invention, the specific configuration is not limited to this embodiment, and design changes and the like within the scope not departing from the gist of the present invention are also included. Further, one aspect of the present invention can be variously modified within the scope shown in 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, a configuration in which elements described in the above embodiments and having the same effects are replaced with each other is included.

Industrial Applicability

[0199] One aspect of the present invention can be used, for example, in a communication system, communication equipment (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.

Description of Reference Numerals

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

Claims

1. A terminal device, comprising: a receiving unit that receives 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 the information in the first system information block, wherein the processing unit regards the first cell as a restricted cell when 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 a plurality of downlink BWP set by the first system information block.

2. The terminal device according to claim 1, wherein the processing unit regards the first cell as 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. The terminal device according to claim 2, wherein the carrier bandwidth is a carrier bandwidth set with respect to a subcarrier spacing commonly set for the plurality of downlink BWP.

4. A base station device, comprising: a processing unit that generates a first system information block including information for determining whether a first cell is a restricted cell for a terminal device; a transmitting unit that transmits the first system information block, wherein the information includes information for setting a plurality of downlink BWP, and is information for the terminal device to regard the first cell as a restricted cell when 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 plurality of downlink BWP.

5. The base station device according to claim 4, wherein the information includes information for setting the carrier bandwidth of the first cell, and is information for regarding the first cell as 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.

6. The base station device according to claim 5, wherein the carrier bandwidth is a carrier bandwidth set with respect to a subcarrier spacing commonly set for the plurality of downlink BWP.

7. A communication method of a base station device, comprising: generating a first system information block including information for determining whether a first cell is a restricted cell for a terminal device; transmitting the first system information block. The communication method, wherein the information includes information for setting a plurality of downlink BWPs, and when 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 plurality of downlink BWPs, the information causes the terminal device to consider that the first cell is a restricted cell.

Images