Terminal equipment, base station equipment, and communication method

Abstract

This terminal devices receives a SIB including first information of a first cell, said first information containing a parameter indicating the carrier bandwidth, a parameter indicating the bandwidth of the initial UL BWP, and a parameter indicating the maximum allocated bandwidth. The terminal device also determines whether or not the first cell is a restricted cell, on the basis of whether or not there is support for a UL channel bandwidth which is no greater than the carrier bandwidth and no less than the initial UL BWP bandwidth, and whether or not there is support for an allocated bandwidth which is equal to or greater than the maximum allocated bandwidth.

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. 2021-45413, filed on Mar. 19, 2021, 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 standardizations of LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) are being conducted (Non-Patent Document 1).

[0003] In the fifth-generation cellular system, three service assumed scenarios are required: eMBB (enhanced Mobile BroadBand) for realizing high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) for realizing low latency and high reliability communication, and mMTC (massive Machine Type Communication) for connecting a large number of machine-type devices such as IoT (Internet of Things). 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] RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016. [Non-Patent Document 2] RP-193238, Ericsson, “New SID on support of reduced capability NR devices”, December 2019 [Overview of the project] [Problems that the invention aims to solve]

[0005] The object of the present invention is to provide a terminal device, a base station device, and a communication method that enable efficient communication in the above-described wireless communication system. [Means for solving the problem]

[0006] (1) To achieve the above objectives, aspects of the present invention employ the following means. That is, a terminal device in one aspect of the present invention includes a receiving unit that receives a system information block containing first information for setting parameters of a first cell, and a processing unit, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell, the processing unit determines whether the first cell is a restricted cell based on whether the terminal device supports an uplink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial uplink BWP, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of uplink channel bandwidth scheduled by the base station device, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive in the first cell by adjusting the frequency position of the transmitter of the terminal device.

[0007] (2) A base station device in one aspect of the present invention comprises a processing unit that generates a system information block including first information for setting parameters of a first cell, and a transmitting unit that transmits the system information block to a terminal device, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell, and is information that causes the terminal device to determine whether the first cell is a restricted cell based on whether the terminal device supports an uplink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial uplink BWP, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of the uplink channel bandwidth scheduled by the base station device, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive by adjusting the frequency position of the transmitter of the terminal device.

[0008] (3) Furthermore, a communication method in one aspect of the present invention is a communication method for a terminal device, which receives a system information block including first information for setting parameters of a first cell, the first information including a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell, and determines whether the first cell is a restricted cell based on whether the terminal device supports an uplink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial uplink BWP, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of uplink channel bandwidth scheduled by the base station device, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive in the first cell by adjusting the frequency position of the transmitter of the terminal device.

[0009] (4) Another communication method in one aspect of the present invention is a communication method for a base station device, comprising generating a system information block including first information for setting parameters of a first cell, transmitting the system information block to a terminal device, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell, and is information that causes the terminal device to determine whether the first cell is a restricted cell based on whether the terminal device supports an uplink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial uplink BWP, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of the uplink channel bandwidth scheduled by the base station device, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive by adjusting the frequency position of the transmitter of the terminal device. [Effects of the Invention]

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

[0011] [Figure 1] This figure shows a concept of a wireless communication system according to an embodiment of the present invention. [Figure 2] This figure shows an example of a schematic configuration of the uplink and downlink slots according to an embodiment of the present invention. [Figure 3] This figure shows the time-domain relationship between the subframe, slot, and minislot according to an embodiment of the present invention. [Figure 4] This figure shows an example of the configuration of the RRC parameter PDCCH-ConfigSIB1-RC, which is information indicating the settings for PDCCH for REDCAP SIB1 according to an embodiment of the present invention. [Figure 5] FIG. 1 is a diagram showing an example of a table in which the value of controlResourceSetZero according to an embodiment of the present invention is applied as an index. [Figure 6] FIG. 2 is a diagram showing an example of a table in which the value of searchSpaceZero according to an embodiment of the present invention is applied as an index. [Figure 7] FIG. 3 is a diagram showing an example of a table of the index indicated by the 2-bit parameter PDCCH-repetitions in the REDCAP MIB according to an embodiment of the present invention and the number of repetition transmissions of PDCCH. [Figure 8] FIG. 4 is a diagram showing an example of an SS / PBCH block and an SS burst set according to an embodiment of the present invention. [Figure 9] FIG. 5 is a diagram showing an example of a half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks according to an embodiment of the present invention are transmitted. [Figure 10] FIG. 6 is a diagram showing resources in which PSS, SSS, PBCH, and DMRS for PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. [Figure 11] FIG. 7 is a diagram showing an example of a half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks according to an embodiment of the present invention are transmitted. [Figure 12] FIG. 8 is a diagram showing resources in which REDCAP PBCH and DMRS for REDCAP PBCH are arranged within a REDCAP PBCH block according to an embodiment of the present invention. [Figure 13] FIG. 9 is a diagram showing an example of a REDCAP PBCH block according to an embodiment of the present invention. [Figure 14] FIG. 10 is a diagram showing another example of a REDCAP PBCH block according to an embodiment of the present invention. [[ID=!30]] [Figure 15] FIG. 11 is a diagram showing an example of RF tuning according to an embodiment of the present invention. [Figure 16]This is a diagram showing an example of downlink transmission using a plurality of initial downlink sub - BWPs according to an embodiment of the present invention. [Figure 17] This is a diagram showing an example of the relationship between the carrier bandwidth, the initial downlink BWP, and the maximum allocated bandwidth in a certain cell according to an embodiment of the present invention, and the downlink channel bandwidth and the downlink allocated bandwidth supported by the terminal device 1. [Figure 18] This is a flowchart showing an example of the determination process of a restricted cell in the terminal device 1 according to an embodiment of the present invention. [Figure 19] This is a diagram showing an example of the relationship between the carrier bandwidth, the initial uplink BWP, and the maximum allocated bandwidth in a certain cell according to an embodiment of the present invention, and the uplink channel bandwidth and the uplink allocated bandwidth supported by the terminal device 1. [Figure 20] This is a flowchart showing another example of the determination process of a restricted cell in the terminal device 1 according to an embodiment of the present invention. [Figure 21] This is a diagram showing an example of beamforming according to an embodiment of the present invention. [Figure 22] This is a schematic block diagram showing the configuration of the terminal device 1 according to an embodiment of the present invention. [Figure 23] This is a schematic block diagram showing the configuration of the base station device 3 according to an embodiment of the present invention.

Embodiments for Carrying Out 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 this embodiment. In FIG. 1, the wireless communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3. Hereinafter, the terminal device 1A and the terminal device 1B are also referred to as the terminal device 1.

[0014] Terminal device 1 is also referred to as a user terminal, mobile station equipment, communication terminal, mobile device, terminal, UE (User Equipment), and MS (Mobile Station). However, terminal device 1 may also be a REDCAP NR device and may be referred to as a REDCAP UE. Base station equipment 3 is also referred to as a radio base station equipment, base station, radio base station, fixed station, NB (Node B), eNB (evolved Node B), BTS (Base Transceiver Station), BS (Base Station), NR NB (NR Node B), NNB, TRP (Transmission and Reception Point), and gNB. Base station equipment 3 may include core network equipment. Base station equipment 3 may also have one or more transmission reception points 4. At least some of the functions / processes of base station equipment 3 described below may also be functions / processes of each transmission reception point 4 provided by base station equipment 3. Base station equipment 3 may serve terminal device 1 as one or more cells within the communication range (communication area) controlled by base station equipment 3. Furthermore, the base station device 3 may serve terminal devices 1 as one or more cells, each comprising a communication range (communication area) controlled by one or more transmission / reception points 4. Alternatively, the base station device 3 may divide one cell into multiple sub-regions (Beamed areas) and serve terminal devices 1 in each sub-region. Here, the sub-regions may be identified based on the beam index used for beamforming or the pre-coding index.

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

[0016] In Figure 1, the wireless communication between terminal device 1 and base station device 3 may use orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), discrete Fourier transform spread OFDM (DFT-S-OFDM), or multi-carrier code division multiplexing (MC-CDM).

[0017] Furthermore, in Figure 1, universal-filtered multi-carrier (UFMC), filtered OFDM (F-OFDM), windowed OFDM, and filtered-bank multi-carrier (FBMC) may be used for wireless communication between terminal device 1 and base station device 3.

[0018] In this embodiment, OFDM is described using OFDM symbols as the transmission method, but the use of other transmission methods as described above is also included as one aspect of the present invention.

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

[0020] One aspect of this embodiment may be operated in carrier aggregation or dual connectivity with radio access technologies (RATs) such as LTE or LTE-A / LTE-A Pro. In this case, 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), MCG (Master Cell Group), SCG (Secondary Cell Group), etc.). Another aspect of this embodiment may be used in a standalone operation. In dual connectivity operation, SpCell (Special Cell) is referred to as MCG PCell or SCG PSCell, depending on whether the MAC (Medium Access Control) entity is associated with an MCG or an SCG, respectively. If not in dual connectivity operation, SpCell (Special Cell) is referred to as PCell. SpCell (Special Cell) supports PUCCH transmission and competition-based random access.

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

[0022] The wireless communication system of this embodiment may apply TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). Either the TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of the multiple cells. Furthermore, cells to which the TDD method is applied and cells to which the FDD method is applied may be aggregated. The TDD method may also be referred to as Unpaired spectrum operation. The FDD method may also be referred to as Paired spectrum operation.

[0023] The following describes subframes. In this embodiment, the following are referred to as subframes, but subframes in this embodiment may also be referred to as resource units, wireless frames, time intervals, time segments, etc.

[0024] Figure 2 shows an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each wireless frame is 10 ms long. Each wireless frame consists of 10 subframes and W slots. Each slot consists of X OFDM symbols. That is, the length of one subframe is 1 ms. The time length of each slot is defined by the subcarrier interval. For example, if the subcarrier interval of OFDM symbols is 15 kHz and NCP (Normal Cyclic Prefix), then X=7 or X=14, which are 0.5 ms and 1 ms, respectively. If the subcarrier interval is 60 kHz, then X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. Also, for example, if X=14, then W=10 when the subcarrier interval is 15 kHz, and W=40 when the subcarrier interval is 60 kHz. Figure 2 shows the case where X=7 as an example. Note that the example in Figure 2 can be similarly extended to the case where X=14. Uplink slots may be defined similarly, and downlink and uplink slots may be defined separately. Furthermore, the cell bandwidth in Figure 2 may be defined as a Bandwidth Part (BWP). Slots may also be defined as Transmission Time Intervals (TTI). Slots do not necessarily have to be defined as TTIs. TTI may also be the transmission period of a transport block.

[0025] Each signal or physical channel transmitted in each slot may be represented by a resource grid. The resource grid is defined by multiple subcarriers and multiple OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers constituting a single slot depends on the bandwidth of the cell's downlink and uplink, respectively. Each element within the resource grid is referred to as a resource element. Resource elements may be identified by their subcarrier numbers and OFDM symbol numbers.

[0026] A resource grid is used to represent the mapping of resource elements for a given physical downlink channel (such as a PDSCH) or uplink channel (such as a PUSCH). For example, if the subcarrier spacing is 15 kHz, the number of OFDM symbols in a subframe is X = 14. In the case of NCP, one physical resource block is defined by 14 consecutive OFDM symbols in the time domain and 12 * Nmax consecutive subcarriers in the frequency domain. Nmax is the maximum number of resource blocks (RBs) determined by the subcarrier spacing setting μ, which will be described later. In other words, a resource grid consists of (14 * 12 * Nmax, μ) resource elements. In the case of ECP (Extended CP), which is only supported at a subcarrier spacing of 60 kHz, one physical resource block is defined, for example, by 12 (number of OFDM symbols in one slot) * 4 (number of slots in one subframe) = 48 consecutive OFDM symbols in the time domain and 12 * Nmax, μ consecutive subcarriers in the frequency domain. In other words, the resource grid consists of (48 * 12 * Nmax, μ) resource elements.

[0027] Resource blocks (RBs) are defined as reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks. One resource block is defined as 12 consecutive subcarriers in the frequency domain. Reference resource blocks are common to all subcarriers and may be configured with, for example, a subcarrier interval of 15 kHz and numbered in ascending order. Subcarrier index 0 at reference resource block index 0 may be called reference point A (point A) (or simply called "reference point"). Common resource blocks are resource blocks numbered in ascending order from 0 at each subcarrier interval setting μ starting from reference point A. The resource grid described above is defined by these common resource blocks. Physical resource blocks are resource blocks numbered in ascending order from 0 that are included in a Bandwidth Part (BWP), which will be described later. A physical uplink channel is first mapped to a virtual resource block. Then, the virtual resource block is mapped to a physical resource block. In the following, resource blocks may be virtual resource blocks, physical resource blocks, common resource blocks, or reference resource blocks.

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

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

[0030] Next, we will explain subframes, slots, and minislots. Figure 3 shows an example of the time-domain relationship between subframes, slots, and minislots. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier interval, and the number of OFDM symbols contained in a slot is 7 or 14 (however, if the cyclic prefix (CP) attached to each symbol is an Extended CP, it may be 6 or 12), and the slot length differs depending on the subcarrier interval. Here, if the subcarrier interval is 15 kHz, one subframe contains 14 OFDM symbols. Downlink slots may be referred to as PDSCH mapping type A. Uplink slots may be referred to as PUSCH mapping type A.

[0031] A minislot (which may also be called a subslot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols contained in a single slot. The figure shows an example where a minislot consists of 2 OFDM symbols. The OFDM symbols in a minislot may coincide with the timing of the OFDM symbols that make up the slot. The smallest unit of scheduling may be a slot or a minislot. Assigning a minislot may also be called non-slot-based scheduling. Scheduling a minislot may also be described as scheduling a resource where the relative time position of the reference signal and the data start position is fixed. Downlink minislots may be called PDSCH mapping type B. Uplink minislots may be called PUSCH mapping type B.

[0032] In terminal device 1, the transmission direction (uplink, downlink, or flexible) of symbols within each slot is set at the upper layer using an RRC message containing predetermined upper-layer parameters received from base station device 3, or by a PDCCH in a specific DCI format (e.g., DCI format 2_0) received from base station device 3. In this embodiment, a slot format is defined as the format in which each symbol within a slot is set to either uplink, downlink, or flexible. A single 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 the downlink component carrier (or downlink carrier). In the uplink of this embodiment, the carrier corresponding to the serving cell is referred to as the uplink component carrier (or uplink carrier). In the sidelink of this embodiment, the carrier corresponding to the serving cell is referred to as the sidelink component carrier (or sidelink carrier). The downlink component carrier, uplink component carrier, and / or sidelink component carrier are collectively referred to as the component carrier (or carrier).

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

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

[0036] • PBCH (Physical Broadcast Channel) • REDCAP PBCH (REDCAP 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 broadcast a Master Information Block (MIB, Essential Information Block, BCH: Broadcast Channel) containing important system information required by the terminal device 1. The MIB may include information to identify the System Frame Number (SFN) of the radio frame (also called a system frame) to which the PBCH is mapped, information to identify the subcarrier spacing of System Information Block 1 (SIB1), information indicating the frequency domain offset between the resource block grid and the SS / PBCH block (also called a synchronization signal block, SS block, or SSB), and information indicating the settings for the PDCCH for SIB1. However, SIB1 includes information necessary for evaluating whether the terminal device 1 is permitted to connect to a cell, and information that determines the scheduling of other system information (SIB: System Information Block). However, the information indicating the settings for the PDCCH for SIB1 may include information that determines CORESET (ControlResourceSet) 0 (also called a common CORESET), the common search space, and / or the required PDCCH parameters. However, CORESET refers to a resource element of PDCCH, and CORESET0 is the CORESET for the PDCCH that schedules SIB1.

[0038] Furthermore, the PBCH may be used to broadcast information to identify the System Frame Number (SFN) of the radio frame (also called a system frame) to which the PBCH is mapped, and / or information to identify a Half Radio Frame (HRF) (also called a half frame). However, a half radio frame is a 5ms time frame, and the information to identify a half radio frame may be information to identify whether it is the first 5ms or the last 5ms of a 10ms radio frame.

[0039] Furthermore, the PBCH may be used to announce the time index within the period of the SS / PBCH block. Here, the time index is information indicating the synchronization signal and PBCH index within the cell. This time index may also be called the SSB index or SS / PBCH block index. For example, when transmitting an SS / PBCH block using a quasi-co-location (QCL) assumption for multiple transmit beams, transmit filter settings and / or receive spatial parameters, the time sequence within a predetermined or set period may be indicated. Also, the terminal equipment may recognize differences in the time index as differences in the QCL assumption for the transmit beams, transmit filter settings and / or receive spatial parameters.

[0040] The REDCAP PBCH may be used to broadcast a REDCAP critical information block (also referred to as REDCAP MIB, REDCAP EIB, REDCAP BCH, or R-MIB) containing important system information required by terminal device 1. However, the REDCAP MIB may only be used for terminal device 1 that meets certain conditions (e.g., indicating specific parameters in UE Capability and / or UE Category). However, the REDCAP MIB may include information for identifying the SFN to which the REDCAP PBCH is mapped or for identifying the SFN to which the SS / PBCH block corresponding to the REDCAP PBCH is mapped, information for identifying the subcarrier spacing of the REDCAP system information block 1 (also referred to as REDCAP SIB1 or 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, or SSB), and information indicating the settings for the PDCCH for REDCAP SIB1. However, REDCAP SIB1 includes information necessary for evaluating whether terminal device 1 is permitted to connect to the cell, and includes information that determines the scheduling of other REDCAP system information blocks (REDCAP SIB, also referred to as R-SIB). However, REDCAP SIB1 may include information necessary for evaluating whether terminal device 1 that meets certain conditions (e.g., indicating certain parameters in UE Capability and / or UE Category, etc.) is permitted to connect to the cell, and may include information that determines the scheduling of other REDCAP SIBs. However, some or all of the information contained in the REDCAP MIB may be the same as some or all of the information contained in the MIB broadcast by the PBCH. For example, the above REDCAP SIB1 may be SIB1. However, some or all of the information in the REDCAP MIB may be broadcast by the PBCH. However, the REDCAP PBCH may broadcast the MIB.For example, the REDCAP MIB included in the information transmitted by a REDCAP PBCH may be the same as the MIB included in the information transmitted by the PBCH in the SS / PBCH block to which the REDCAP PBCH is associated. However, the MIB processing described below may also be applied to the REDCAP MIB processing.

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

[0042] Furthermore, the information transmitted by REDCAP PBCH may include a time index within the period of the associated SS / PBCH block. This time index may be referred to as the SSB index or SS / PBCH block index. For example, when base station device 3 transmits SS / PBCH blocks using QCL assumptions regarding multiple transmit beams, transmit filter settings, and / or receive spatial parameters, it may indicate a predetermined or set time sequence within a period. Terminal device 1 may also recognize differences in time indices as differences in QCL assumptions regarding transmit beams, transmit filter settings, and / or receive spatial parameters. Additionally, the information transmitted by REDCAP PBCH may include a time index for the REDCAP PBCH.

[0043] The information indicating the settings for the PDCCH for REDCAP SIB1 transmitted by REDCAP PBCH may be information that determines CORESET0, common search space, and / or required PDCCH parameters for the PDCCH that schedules REDCAP SIB1. However, the information that determines CORESET0, common search space, and / or required PDCCH parameters shown in the REDCAP MIB may be the same as the information that determines CORESET0, common search space, and / or required PDCCH parameters shown 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 for PDCCH for REDCAP SIB1. The RRC parameter PDCCH-ConfigSIB1-RC consists of the parameter controlResourceSetZero, which is used to set CORESET0, and the parameter searchSpaceZero, which is used to set the common search space. The information element (IE) ControlResourceSetZero, indicated by controlResourceSetZero, can be set to a value between 0 and 15. However, the number of values ​​that can be set for ControlResourceSetZero is not limited to 16; for example, it could be 32. The information element SearchSpaceZero, indicated by searchSpaceZero, can be set to a value between 0 and 15. However, the number of values ​​that can be set for SearchSpaceZero is not limited to 16; for example, it could be 32.

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

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

[0047] The RB count for CORESET0 indicates the number of resource blocks that are continuously allocated to CORESET0. The symbol count for CORESET0 indicates the number of symbols that are continuously allocated to CORESET0.

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

[0049] The PDCCH repetition count indicates the number of times the PDCCH scheduling REDCAP SIB1 has been repeatedly transmitted. If the PDCCH repetition count shown in the table is greater than 1, terminal device 1 considers that the PDCCH scheduling REDCAP SIB1 has been repeatedly transmitted.

[0050] Terminal device 1 receives a REDCAP MIB containing the RRC parameter controlResourceSetZero via REDCAP PBCH, and monitors the PDCCH, which shows the scheduling information of REDCAP SIB1, based on the controlResourceSetZero and a table that shows the index, the multiplexing pattern of REDCAP PBCH and CORESET, the number of RBs in CORESET0, the number of symbols in CORESET0, the offset, and / or the number of repetitions of PDCCH.

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

[0052] Terminal device 1 monitors the PDCCH using the Type0-PDCCH Common Search Space Set (Type0-PDCCH CSS Set) across two consecutive slots starting from slot n0. Terminal device 1 determines n0 and the system frame number based on parameters O and M shown in the table for the REDCAP PBCH and / or corresponding SS / PBCH block where index i.

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

[0054] Furthermore, the information transmitted by the REDCAP PBCH may include a field called PDCCH-repetitions, which indicates the number of repetitions of the PDCCH that schedules REDCAP SIB1. For example, the number of repetitions of the PDCCH may be indicated by two bits in the REDCAP MIB. Figure 7 shows an example of a table of the number of repetitions of the PDCCH and the index indicated by the two-bit parameter PDCCH-repetitions in the REDCAP MIB. In the table in Figure 7, indices 0, 1, 2, and 3 indicated in the REDCAP MIB correspond to PDCCH repetitions of N / A, 1, 2, and 4, respectively. However, a value of N / A for the number of repetitions of the PDCCH may indicate that the PDCCH and / or REDCCAP SIB1 that schedules REDCAP SIB1 have not been transmitted. In this case, terminal device 1 considers that the PDCCH and / or REDCCAP SIB1 that schedules REDCAP SIB1 have not been transmitted when the index indicated by the two bits in the REDCAP MIB is 0. However, a value of N / A for the number of PDCCH repetitions may indicate that the cell in question is prohibited (barred).

[0055] Terminal device 1 receives a REDCAP MIB containing the RRC parameter PDCCH-repetitions via REDCAP PBCH, determines the number of repetitions of PDCCH indicating scheduling information of REDCAP SIB1 based on PDCCH-repetitions, and considers that PDCCH has not been transmitted if PDCCH-repetitions is a predetermined value.

[0056] PDCCH is used in downlink radio communication (radio communication from base station 3 to terminal 1) to transmit (or carry) Downlink Control Information (DCI). Here, one or more DCIs (which may also be called 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. PDCCH is transmitted in PDCCH candidates. Terminal 1 monitors a set of PDCCH candidates in the serving cell. Monitoring may mean attempting to decode the PDCCH according to a certain DCI format.

[0057] For example, the following DCI format may be defined. DCI format 0_0 • DCI Format 0_1 • DCI Format 0_2 • DCI Format 1_0 DCI Format 1_1 • DCI Format 1_2 • DCI Format 2_0 • DCI Format 2_1 • DCI Format 2_2 • DCI Format 2_3

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

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

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

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

[0062] DCI format 1_1 may be used for scheduling a 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 have a CRC added, which is scrambled by any of the RNTIs: C-RNTI, CS-RNTI, and / or MCS-C-RNTI. DCI format 1_1 may be monitored in a UE-specific search space.

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

[0064] DCI format 2_0 is used to indicate the slot format for one or more slots. The slot format is defined as classifying each OFDM symbol within a slot as either a downlink, flexible, or uplink. For example, if the slot format is 28, then DDDDDDDDDDDDFU is applied to the 14 OFDM symbols within the slot that specifies slot format 28. Here, D represents a downlink symbol, F represents a flexible symbol, and U represents an uplink symbol. Slots will be discussed later.

[0065] DCI format 2_1 is used to notify terminal device 1 of physical resource blocks (PRB or RB) and OFDM symbols that can be assumed not to be transmitted. This information may be referred to as a preemption instruction (intermittent transmission instruction).

[0066] DCI format 2_2 is used for transmitting PUSCH and Transmit Power Control (TPC) commands for PUSCH.

[0067] DCI format 2_3 is used to transmit a group of TPC commands for sounding reference signal (SRS) transmission by one or more terminal devices 1. An SRS request may also be transmitted along with the TPC commands. Furthermore, DCI format 2_3 may define SRS requests and TPC commands for uplinks without PUSCH and PUCCH, or for uplinks where SRS transmit power control is not tied to PUSCH transmit power control.

[0068] A DCI for a downlink is also called a downlink grant or downlink assignment. Similarly, a DCI for an uplink is also called an uplink grant or uplink assignment. DCI may also be referred to as the DCI format.

[0069] The CRC parity bits added to the DCI format transmitted by a single 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 notifying paging and 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 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 PDSCH or PUSCH resources. 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 or PUSCH transmission in one or more slots. TC-RNTI is used to schedule the retransmission of random access message 3 and the transmission of random access message 4. RA-RNTI is determined based on the frequency and time position information of the physical random access channel that transmitted the random access preamble.

[0071] C-RNTI and / or other RNTI values ​​may be used differently depending on the type of traffic in the PDSCH or PUSCH. C-RNTI and other RNTI values ​​may be used differently depending on the service type (eMBB, URLLC, and / or mMTC) of the data transmitted in the PDSCH or PUSCH. Base station device 3 may use different RNTI values ​​depending on the service type of the data it transmits. Terminal device 1 may identify the service type of the data transmitted in the relevant PDSCH or PUSCH by the value of the RNTI applied to the received DCI (used for scrambling).

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

[0073] PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared Channel) from the Medium Access Control (MAC) layer. In the case of downlinks, PDSCH is also used to transmit system information (SI: System Information) and random access responses (RAR: Random Access Response).

[0074] PUSCH may be used to transmit uplink data (UL-SCH: Uplink Shared Channel) from the MAC layer, or HARQ-ACK and / or CSI along with uplink data. Alternatively, PUSCH may be used to transmit CSI only, or HARQ-ACK and CSI only. In other words, PUSCH may be used to transmit UCI only.

[0075] Here, the base station device 3 and the terminal device 1 exchange signals (send and receive) at the higher layer. For example, the base station device 3 and the terminal device 1 may send and receive RRC messages (also called RRC message, RRC information, or RRC signalling) at the Radio Resource Control (RRC) layer. The base station device 3 and the terminal device 1 may also send and receive MAC control elements at the MAC (Medium Access Control) layer. Furthermore, the RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3. Here, RRC messages, system information, and / or MAC control elements are also called higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters). Each of the parameters included in the higher layer signal received by the terminal device 1 may also be called a higher layer parameter. Here, "upper layer" refers to the layer above the physical layer, and may include one or more layers such as the MAC layer, RRC layer, RLC layer, PDCP layer, and NAS (Non-Access Stratum) layer. For example, in MAC layer processing, the upper layer may include one or more layers such as the RRC layer, RLC layer, PDCP layer, and NAS layer. Hereafter, "A is provided in the upper layer" or "A is provided by the upper layer" may mean that the upper layer of terminal device 1 (mainly the RRC layer or MAC layer, etc.) receives A from base station device 3, and that received A is provided from the upper layer of terminal device 1 to the physical layer of terminal device 1. For example, "being provided with upper layer parameters" in terminal device 1 may mean that it receives an upper layer signal from base station device 3, and the upper layer parameters included in the received upper layer signal are provided from the upper layer of terminal device 1 to the physical layer of terminal device 1. Setting upper layer parameters in terminal device 1 may mean that upper layer parameters are provided to terminal device 1.For example, setting upper-layer parameters in terminal device 1 may mean that terminal device 1 receives upper-layer signals from base station device 3 and sets the received upper-layer parameters in the upper layer. However, setting upper-layer parameters in terminal device 1 may also include setting default parameters that have been pre-assigned to the upper layer of terminal device 1.

[0076] PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements. The RRC signaling transmitted from base station equipment 3 via PDSCH may be a common signaling for multiple terminal devices 1 within a cell. Alternatively, the RRC signaling transmitted from base station equipment 3 may be dedicated signaling (also called dedicated signaling) for a particular terminal device 1. That is, terminal device-specific information may be transmitted using dedicated signaling for a particular terminal device 1. Furthermore, PUSCH may be used to transmit UE capability on the uplink.

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

[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 by terminal device 1 to synchronize the frequency domain and time domain of the downlink. Here, the synchronization signal may be used by terminal device 1 for precoding by base station device 3 or for precoding or beam selection in beamforming. The beam may also be called transmit or receive filter settings, or spatial domain transmit filter or spatial domain receive filter.

[0080] The reference signal is used by terminal device 1 to perform propagation path compensation for the physical channel. Here, the reference signal may also be used by terminal device 1 to calculate the CSI of the downlink. Furthermore, the reference signal may be used for fine synchronization, such as numerology of radio parameters and subcarrier spacing, or window synchronization of the FFT.

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

[0082] DMRS is used to demodulate modulated signals. Note that DMRS may be defined as having two types of reference signals: one for demodulating PBCH and another for demodulating PDSCH, or both may be referred to simply as DMRS. CSI-RS is used for measuring Channel State Information (CSI) and beam management, and a periodic, semi-persistent, or aperiodic transmission method of the CSI reference signal is applied. CSI-RS may be defined as Non-Zero Power (NZP) CSI-RS and Zero Power (ZP) CSI-RS, where the transmit power (or receive power) is zero. Here, ZP CSI-RS may be defined as a CSI-RS resource with zero transmit power or no transmit power. PTRS is used to track the phase in the time domain to compensate for frequency offsets caused by phase noise. TRS is used to compensate for Doppler shift during high-speed movement. Note that TRS may be used as one setting of CSI-RS. For example, a single-port CSI-RS may be configured as a radio resource with TRS.

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

[0084] DMRS is used to demodulate modulated signals. Note that DMRS may be defined as two types of reference signals: one for demodulating PUCCH and another for demodulating PUSCH, or both may be referred to as DMRS. SRS is used for measuring uplink channel status information (CSI), channel sounding, and beam management. PTRS is used to track phase in the time domain to compensate for frequency offsets caused by phase noise.

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

[0086] BCH, UL-SCH, and DL-SCH are transport channels. Channels used in the Medium Access Control (MAC) layer are called transport channels. The unit of transport channel used in the MAC layer is also called a transport block (TB) and / or MAC PDU (Protocol Data Unit). 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, transport blocks are mapped to codewords, and encoding processing is performed for each codeword.

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

[0088] An SS / PBCH block may be a block containing synchronization signals (PSS, SSS), a PBCH, and a DMRS for the PBCH. However, an SS / PBCH block may also be a block containing synchronization signals (PSS, SSS), a REDCAP PBCH, and a DMRS for the REDCAP PBCH. Transmitting the signals / channels contained in an SS / PBCH block is expressed as transmitting an SS / PBCH block. When base station equipment 3 transmits synchronization signals and / or PBCH using one or more SS / PBCH blocks in an SS burst set, it may use an independent downlink transmit beam 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 using different time resources and / or different frequency resources than the SS / PBCH block. However, in this embodiment, transmitting / receiving / processing the REDCAP PBCH may be equivalent to transmitting / receiving / processing the REDCAP PBCH and the DMRS for the REDCAP PBCH. A block containing the REDCAP PBCH and the DMRS for the REDCAP PBCH may be referred to as a REDCAP PBCH block. However, transmitting the signals / channels contained in a REDCAP PBCH block may be expressed as transmitting a 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 be referred to as a REDCAP PBCH burst set), it may use an independent downlink transmit beam for each REDCAP PBCH block. However, the REDCAP PBCH block according to this embodiment may refer to the REDCAP PBCH and / or the DMRS for the REDCAP PBCH itself. For example, transmitting / receiving / processing a REDCAP PBCH block may be equivalent to transmitting / receiving / processing a REDCAP PBCH and / or DMRS for a REDCAP PBCH. However, the REDCAP PBCH and / or DMRS for a REDCAP PBCH in this embodiment may be a REDCAP PBCH and / or DMRS for a REDCAP PBCH transmitted outside of an SS / PBCH block. For example, the REDCAP PBCH and / or DMRS for a REDCAP PBCH may be a REDCAP PBCH and / or DMRS for a REDCAP PBCH transmitted using different time and / or frequency resources than an SS / PBCH block that is periodically transmitted in an SSB period. However, the REDCAP PBCH block in 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 are associated with one SS / PBCH block transmitted within an SS burst set (Half frame with SS / PBCH block). The transport block transmitted in the REDCAP PBCH and the transport block transmitted in the PBCH within the corresponding SS / PBCH block may be the same.

[0091] Figure 9 shows an example of a half frame (which may be referred to as a REDCAP PBCH block or REDCAP PBCH burst set) in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted according to this embodiment. Figure 9 shows an example in which two REDCAP PBCH blocks are contained within a REDCAP PBCH burst set that exists at a fixed period (which may be referred to as an SSB period), and the REDCAP PBCH block consists of four consecutive OFDM symbols. In the REDCAP PBCH block, the REDCAP PBCH modulation symbol and the DMRS for REDCAPPBCH are frequency multiplexed at each OFDM symbol.

[0092] However, a block containing the synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for REDCAP PBCH may be defined as a separate block, distinct from the SS / PBCH block. For example, a block containing the synchronization signals (PSS, SSS), REDCAP PBCH, and DMRS for REDCAP PBCH may be called a REDCAPSS / PBCH block, a REDCAP synchronization signal block, a REDCAP SS block, or a REDCAP SSB. However, the description of the SS / PBCH block in this embodiment may also apply to the REDCAP SS / PBCH block.

[0093] In Figure 8, a single SS / PBCH block has time / frequency multiplexed DMRS for PSS, SSS, PBCH, and PBCH. Figure 10 is a table showing the resources where DMRS for PSS, SSS, PBCH, and PBCH are located within the SS / PBCH block.

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

[0095] The SSS may be mapped to the third symbol in the SS / PBCH block (an OFDM symbol whose OFDM symbol number is 2 relative to the start symbol of the SS / PBCH block). The SSS sequence consists of 127 symbols and may be mapped to subcarriers 57 through 183 in the SS / PBCH block (subcarriers whose subcarrier numbers are 56 through 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 (OFDM symbols whose OFDM symbol numbers are 1, 2, and 3 relative to the starting symbol of the SS / PBCH block). The sequence of modulation symbols for PBCH is M symbIt consists of symbols and may be mapped to resources that are not mapped to DMRS, among the 1st to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the SS / PBCH block) and the 1st to 48th subcarriers and 184th to 240th subcarriers of the third symbol in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 47 and 192 to 239 relative to the start subcarrier of the SS / PBCH block). The DMRS symbol sequence consists of 144 symbols and may be mapped one subcarrier for every four subcarriers to the 1st to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the SS / PBCH block), and to the 1st to 48th subcarriers and the 184th to 240th subcarriers of the third symbol in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 47 and 192 to 239 relative to the start subcarrier of the SS / PBCH block). For example, of the 240 subcarriers, 180 subcarriers may be mapped to the modulation symbols of the PBCH, and 60 subcarriers may be mapped to the DMRS for the PBCH.

[0097] Different SS / PBCH blocks within an SS burst set may be assigned different SSB indices. An SS / PBCH block assigned a certain SSB index may be transmitted periodically by the base station device 3 based on an SSB period. For example, an SSB period for the SS / PBCH block to be used for initial access and an SSB period to be set for the connected (Connected or RRC_Connected) terminal device 1 may be defined. The SSB period to be set for the connected (Connected or RRC_Connected) terminal device 1 may be set by an RRC parameter. The SSB period to be set for the connected (Connected or RRC_Connected) terminal device 1 is also the period of a radio resource in the time domain that may potentially be transmitted, and whether or not the base station device 3 actually transmits it may be determined. The SSB period for the SS / PBCH block to be used for initial access may be predefined in a specification or similar document. For example, terminal device 1 performing initial access may consider the SSB period to be 20 milliseconds.

[0098] The time position of the SS burst set to which the SS / PBCH block is mapped may be determined based on information that identifies the System Frame Number (SFN) and / or half frame included in the PBCH. Terminal device 1, upon receiving the SS / PBCH block, may determine the current System Frame Number and half frame based on the received SS / PBCH block.

[0099] An SS / PBCH block is assigned an SSB index (which may also be called an SS / PBCH block index) according to its temporal position within the SS burst set. Terminal device 1 identifies the SSB index based on the PBCH information and / or reference signal information contained in the detected SS / PBCH block.

[0100] SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assumed to be QCL (or have the same downlink transmit beam applied). Furthermore, antenna ports in SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

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

[0102] The SS / PBCH block number (which may also be referred to as the SS block number or SSB number) may be defined, for example, as the number of SS / PBCH blocks within an SS burst, an SS burst set, or a period of an SS / PBCH block. Alternatively, the SS / PBCH block number may represent the number of beam groups for cell selection within an SS burst, an SS burst set, or a period of an SS / PBCH block. Here, a beam group may be defined as the number of different SS / PBCH blocks or different beams contained within an SS burst, an SS burst set, or a period of an SS / PBCH block (SSB period).

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

[0104] The temporal relationship between the REDCAP PBCH and the corresponding SS / PBCH block according to this embodiment may be determined by the temporal relationship between the half-frame containing the REDCAP PBCH and the half-frame containing the corresponding SS / PBCH block. For example, the half-frame containing the REDCAP PBCH may be a half-frame that is offset by a predetermined time from the half-frame containing the corresponding SS / PBCH block. For example, the temporal position of the REDCAP PBCH within the half-frame containing the REDCAP PBCH and the temporal position of the SS / PBCH block within the half-frame containing the corresponding SS / PBCH block may be the same.

[0105] The start subcarrier of the REDCAP PBCH according to this embodiment may be a subcarrier to which a predetermined frequency offset has been added to the start subcarrier of the corresponding SS / PBCH block. However, if 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 start subcarrier of the REDCAP PBCH. For example, if the value obtained by adding a predetermined frequency offset to the start subcarrier of the corresponding SS / PBCH block exceeds the bandwidth to which the REDCAP PBCH can be assigned, the value obtained by subtracting the bandwidth of the band to which the REDCAP PBCH can be assigned from that value may be used as the start subcarrier of the REDCAP PBCH.

[0106] Figure 11 shows an example of a half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted according to this embodiment. Figure 11 shows an example in which a half-frame containing a REDCAP PBCH block exists between half-frames containing SS / PBCH blocks that exist at a fixed period (SSB period), and the REDCAP PBCH block consists of consecutive 3 OFDM symbols. The REDCAP PBCH block is transmitted using a resource corresponding to one SS / PBCH block, and a REDCAP PBCH or DMRS for the REDCAP PBCH exists in all resources within the REDCAP PBCH block. Figure 12 is a table showing an example of resources in which a REDCAP PBCH and DMRS for the REDCAP PBCH are located within the REDCAP PBCH block. For example, the sequence of modulation symbols for the REDCAP PBCH is M symb2The DMRS for REDCAP PBCH consists of symbols and may be mapped to resources that are not mapped to the 1st to 240th subcarriers (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block) of each of the three symbols in the REDCAP PBCH block. The symbol sequence for the DMRS for REDCAP PBCH consists of 180 symbols and may be mapped one subcarrier for every four subcarriers (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block) from the 1st to 240th subcarriers of the three symbols in the REDCAP PBCH block. However, the number of symbols constituting the REDCAP PBCH block does not have to be three. For example, the REDCAP PBCH block may consist of four symbols, and a REDCAP PBCH or a DMRS for REDCAP PBCH may exist for each of the 240 subcarriers of each symbol. However, the number of subcarriers constituting the REDCAP PBCH block does not have to be 240. For example, a REDCAP PBCH block consists of 180 subcarriers and 4 OFDM symbols, and for each of the 180 subcarriers of a symbol, there may be a REDCAP PBCH or a DMRS for the REDCAP PBCH.

[0107] Figure 13 shows an example of a REDCAP PBCH block according to this embodiment. Figure 13 shows an example in which a REDCAP PBCH block exists within a half frame containing SS / PBCH blocks that exist at a fixed period (SSB period), and the REDCAP PBCH block consists of a sequence of 4 OFDM symbols. The REDCAP PBCH block is transmitted with a resource corresponding to one SS / PBCH block, and all resources within the REDCAP PBCH block have a REDCAP PBCH or DMRS for the REDCAP PBCH. For example, the sequence of modulation symbols for REDCAP PBCH is M symb2The DMRS for REDCAP PBCH consists of symbols and may be mapped to resources that are not mapped to REDCAP PBCH, from the 1st to the 240th subcarrier of each of the four symbols in the REDCAP PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block). The symbol sequence for DMRS for REDCAP PBCH consists of 240 symbols and may be mapped one subcarrier for every four subcarriers from the 1st to the 240th subcarrier of each of the four symbols in the REDCAP PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block). However, REDCAP PBCH or DMRS for REDCAP PBCH may not exist for all resources in the REDCAP PBCH block. For example, the REDCAP PBCH block may consist of four symbols, one of which may be set to 0.

[0108] Figure 14 shows another example of a REDCAP PBCH block according to this embodiment. Figure 14 shows an example in which a REDCAP PBCH block exists in some slots within a half frame that contains SS / PBCH blocks that exist at a fixed period (SSB period), and the REDCAP PBCH block consists of consecutive 4 OFDM symbols. However, the slot in which the REDCAP PBCH block is placed may not contain candidate resources for an SS / PBCH block. The REDCAP PBCH block is transmitted with a resource corresponding to one SS / PBCH block, and all resources within the REDCAP PBCH block have a REDCAP PBCH or DMRS for the REDCAP PBCH. For example, the sequence of modulation symbols for REDCAP PBCH is M symb2The DMRS for REDCAP PBCH consists of symbols and may be mapped to resources that are not mapped to REDCAP PBCH among the subcarriers from the 1st to the 240th subcarrier of each of the four symbols in the REDCAP PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block). The symbol sequence for DMRS for REDCAP PBCH consists of 240 symbols and may be mapped one subcarrier for every four subcarriers from the 1st to the 240th subcarrier of the four symbols in the REDCAP PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the start subcarrier of the REDCAP PBCH block). However, REDCAP PBCH or DMRS for REDCAP PBCH may not exist for all resources in the REDCAPPBCH block. For example, the REDCAP PBCH block may consist of four symbols, one of which may be set to 0, and the remaining three symbols may have REDCAP PBCH and DMRS for REDCAP PBCH.

[0109] One or more REDCAP PBCH blocks within a half-frame containing a REDCAP PBCH (REDCAP PBCH burst set) may be assigned different SSB indices. A REDCAP PBCH block assigned a particular SSB index may be associated with the SS / PBCH block of that SSB index and transmitted periodically by the base station device 3. However, multiple REDCAP PBCH blocks assigned the same SSB index may exist for a single SS / PBCH block. For example, a REDCAP PBCH block assigned the same SSB index may be transmitted multiple times within an SSB period.

[0110] The time position of the half-frame to which the REDCAP PBCH block is mapped may be determined based on information identifying the SFN and / or half-frame contained in the PBCH of the corresponding SS / PBCH block and / or the REDCAP PBCH of the REDCAP PBCH block, and the time offset between the corresponding SS / PBCH block and the REDCAP PBCH block. However, the information identifying the SFN and / or half-frame contained in the REDCAP PBCH of the REDCAP PBCH block may be information identifying the SFN and half-frame to which the corresponding SS / PBCH block is transmitted. A terminal device 1 that receives a REDCAP PBCH block may determine the SFN and half-frame to which the corresponding SS / PBCH block is transmitted based on the received REDCAPPBCH block.

[0111] A REDCAP PBCH block is assigned an SSB index based on its temporal position within the transmitted half-frame. Terminal device 1 identifies the SSB index based on the REDCAP PBCH information and / or reference signal information contained in the detected REDCAP PBCH block.

[0112] SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assumed to be QCL (or have the same downlink transmit beam applied). Furthermore, antenna ports in SS / PBCH blocks with the same relative time within each SS burst set across multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.

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

[0114] In this embodiment, terminal device 1 receives PSS and SSS in an 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, terminal device 1 can improve the detection accuracy of MIB or REDCAP MIB and expand the cell coverage over which terminal device 1 can receive MIB or REDCAP MIB. However, terminal device 1 that receives REDCAP PBCH may be limited to terminal device 1 with a predetermined capability. For example, terminal device 1 with limited capability for purposes such as reducing device costs and / or power consumption may be referred to as corresponding to REDCAP (Reduction Capability), and terminal device 1 corresponding to REDCAP receives SS / PBCH blocks and / or REDCAP PBCHs, while terminal device 1 that does not correspond to REDCAP may only receive SS / PBCH blocks and not receive REDCAP PBCH blocks.

[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 a REDCAP PBCH and DMRS for REDCAP PBCH in the same or a different radio frame as the certain radio frame, and obtain the MIB of the transport block transmitted in the PBCH and REDCAP PBCH. However, the PBCH and REDCAP PBCH carry at least the MIB and additional bit information, and the radio frame in which the SS / PBCH block was transmitted may be identified 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 wireless frame, receive REDCAP PBCH and DMRS for REDCAP PBCH in the same or a different wireless frame as the certain wireless frame, and obtain the MIB of the transport block transmitted in PBCH and REDCAP PBCH.

[0117] In this embodiment, terminal device 1 determines whether to consider a cell as a "barred" cell based on the connection status, the execution status of a predetermined timer, the information of a received MIB (which may be a REDCAP MIB), and / or the information of a received SIB (which may be a REDCAP SIB, SIB1, or REDCAP SIB1). However, a barred cell may be a cell in which terminal device 1 is not permitted to camp on. A cell is barred by instructions in the system information. For example, terminal device 1 does not camp on a barred cell. Terminal device 1 may consider a cell as a barred cell if it cannot obtain an MIB from that cell.

[0118] Terminal device 1 may treat a cell as a candidate cell for cell selection and cell re-selection if that cell is not a restricted cell (even if the cell status is indicated as "not barred").

[0119] Terminal device 1 is prohibited from selecting and re-selecting a cell if that cell is a restricted cell (when the cell status is indicated as "barred" or treated as if the cell status is "barred"), and instead selects another cell. If a cell is a restricted cell, terminal device 1 may select / re-select other cells based on the MIB. For example, if a field in the MIB indicates that selection / re-selection of the same frequency is prohibited, terminal device 1 may designate all other cells of the same frequency as restricted cells and not consider them as candidates for re-selection.

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

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

[0122] In this embodiment, terminal device 1 determines whether to consider a cell as a "barred" cell based on the parameters of the received SIB1 (REDCAPSIB1, or any other SIB) when the connection state is not in the RRC connection state (in RRC_CONNECTED while T311 is not running) where timer T311 is not running.

[0123] In this embodiment, the base station device 3 transmits an SIB1 (REDCAP SIB1, or other SIBs) to the terminal device 1 that includes parameters for determining whether the cell in which the terminal device 1 is located is restricted.

[0124] The initial BWP, initial DL BWP, and initial UL BWP according to this embodiment may be, at least, the BWP, DL BWP, and UW BWP used during the initial access before the RRC connection is established.

[0125] If an initialDownlinkBWP is not provided in the SIB1 (REDCAP SIB1, or any other SIB) received by terminal device 1, the initial downlink BWP may be defined by the position and number of consecutive PRBs (Physical Resource Blocks) in the CORESET (CORESET0, etc.) of the Type0-PDCCH CSS Set, starting from the lowest index PRB and ending with the highest index PRB, and by the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received by the CORESET of the Type0-PDCCH CSS Set. If an initialDownlinkBWP is provided in the SIB1 received by terminal device 1, the initial downlink BWP may be defined by that initialDownlinkBWP.

[0126] The initial uplink BWP may be defined / set by the initialUplinkBWP provided in SIB1 (REDCAP SIB1, or any other SIB). Terminal device 1 may determine the initial uplink BWP based on the initialUplinkBWP provided by the received SIB1.

[0127] Terminal device 1 includes an RF circuit between its own antenna and a signal processing unit that processes baseband signals. The RF circuit mainly includes a signal processing unit, a power amplifier, an antenna switch, a filter, etc. When receiving a signal, the signal processing unit of the RF circuit demodulates the RF signal received through the filter and outputs the received signal to the signal processing unit. When transmitting a signal, the high-frequency signal processing unit of the RF circuit modulates the carrier signal, generates an RF signal, amplifies the power with a power amplifier, and then outputs it to the antenna. The antenna switch connects the antenna and the filter when receiving a signal, and connects the antenna and the power amplifier when transmitting a signal.

[0128] If the bandwidth of the initial downlink BWP set by terminal device 1 is wider than the bandwidth supported by the RF circuit provided by the device (which may be called the allocated bandwidth), terminal device 1 may adjust / retune (tune / retune) the frequency band to which the RF circuit is applied within the initial downlink BWP. Adjusting / retuning the frequency band to which the RF circuit is applied may be called RF tuning / RF retuning. Figure 15 shows an example of RF retuning. In Figure 15, if the application bandwidth of the RF circuit used by terminal device 1 is outside the bandwidth of the downlink channel received within the initial downlink BWP, terminal device 1 performs RF retuning so that the application bandwidth of the RF circuit includes the bandwidth of the receiving downlink channel. If the bandwidth of the initial uplink BWP set by terminal device 1 is wider than the bandwidth supported by the RF circuit provided by the device (which may be called the allocated bandwidth), terminal device 1 may adjust / retune (tune / retune) the frequency band to which the RF circuit is applied within the initial uplink BWP. If the bandwidth of the set downlink BWP is wider than the bandwidth supported by the RF circuit provided by the device (which may be called the allocated bandwidth), terminal device 1 may adjust / readjust the frequency band to which the RF circuit is applied within the downlink BWP. If the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit provided by the device (which may be called the allocated bandwidth), terminal device 1 may adjust / readjust the frequency band to which the RF circuit is applied within the uplink BWP.

[0129] Terminal device 1 may configure multiple initial downlink sub-BWPs using SIB1. At least one of these multiple initial downlink sub-BWPs may be configured to include an SS / PBCH block. Terminal device 1 may operate by treating an initial downlink sub-BWP containing an SS / PBCH block (such as a cell-defining SS / PBCH block (SSB)) as an initial downlink BWP. At least one of these multiple initial downlink sub-BWPs may be configured to include a CORESET0. All of the multiple initial downlink sub-BWPs may be configured to include their respective CORESET0s. Terminal device 1 may operate by treating an initial downlink sub-BWP containing a CORESET0 as an initial downlink BWP. Terminal device 1 may operate by treating an initial downlink sub-BWP as an initial downlink BWP. Multiple initial downlink sub-BWPs may be considered as multiple initial downlink BWPs. Multiple initial downlink sub-BWPs may be designed to be contained within the frequency band of a single initial downlink BWP. The initial downlink sub-BWP may also be referred to as the downlink BWP or downlink sub-BWP.

[0130] Terminal device 1 may have multiple initial uplink sub-BWPs configured by SIB1. Terminal device 1 may determine one or more initial uplink sub-BWPs based on the initialUplinkBWP provided by SIB1. At least one of these multiple initial uplink sub-BWPs may be configured to include resources for a physical random access channel. Terminal device 1 may operate as if an initial uplink sub-BWP were an initial uplink BWP. Multiple initial uplink sub-BWPs may be considered as multiple initial uplink BWPs. Multiple initial uplink sub-BWPs may be designed to be contained within the frequency band of a single initial uplink BWP. An initial uplink sub-BWP may be rephrased as an uplink BWP or an uplink sub-BWP.

[0131] However, sub-BWP (which may include uplink sub-BWP, downlink sub-BWP, initial uplink sub-BWP, and initial downlink sub-BWP) may also refer to the bandwidth to which the RF circuit provided by terminal device 1 is applied. For example, if the bandwidth of the initial downlink BWP is greater than the bandwidth of the RF circuit provided by terminal device 1, terminal device 1 may determine an initial downlink sub-BWP with a bandwidth less than or equal to the bandwidth supported by its own RF circuit. For example, if the bandwidth of the initial uplink BWP is greater than the bandwidth of the RF circuit provided by terminal device 1, terminal device 1 may determine an initial uplink sub-BWP with a bandwidth less than or equal to the bandwidth supported by its own RF circuit.

[0132] The base station device 3 may transmit a downlink signal (for example, PDSCH, PDCCH, PBCH, synchronization signal, Msg2 in the random access procedure, and / or Msg4 in the random access procedure) with frequency hopping applied using at least two of the multiple initial downlink sub-BWPs. However, the initial downlink sub-BWPs are frequency resources that can be used at least during initial access before the RRC connection is established. The terminal device 1 may receive a downlink signal with frequency hopping applied using at least two of the multiple initial downlink sub-BWPs. However, the multiple initial downlink sub-BWPs in this embodiment may be downlink BWPs to which the same identifier (BWP ID) is assigned. However, the multiple initial downlink sub-BWPs in this embodiment may be multiple downlink BWPs to which different identifiers (BWP IDs) are assigned. The multiple initial downlink sub-BWPs may be multiple frequency bands consisting of multiple sets of multiple resource blocks set by the SIB1. Each of the initial downlink sub-BWPs may consist of multiple resource blocks that are contiguous in the frequency domain. For example, multiple initial downlink sub-BWPs may be multiple downlink sub-BWPs configured within an initial downlink BWP whose BWP ID set by SIB1 is 0. For example, each downlink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0a, 0b, etc.). In this case, the settings for the initial downlink BWP and the settings for the multiple downlink sub-BWPs are configured by SIB1.

[0133] Figure 16 shows an example of downlink transmission using multiple initial downlink sub-BWPs according to this embodiment. Figure 16 shows a case where four initial downlink sub-BWPs (initial DL sub BWP#0, #1, #2, #3) are set up in a carrier within a certain frequency band. Terminal device 1 supports a wider channel bandwidth than each of the four initial downlink sub-BWPs. In the example in Figure 16, terminal device 1 repeatedly transmits one downlink signal while frequency hopping using initial downlink sub-BWP#0 and initial downlink sub-BWP#2.

[0134] Base station device 3 may transmit downlink signals (e.g., PDSCH, PDCCH, PBCH, synchronization signals, Msg2 and / or Msg4 in random access procedures) using one of the multiple initial downlink sub-BWPs. Terminal device 1 may receive downlink signals using one of the multiple initial downlink sub-BWPs. An initial downlink sub-BWP may be a frequency band consisting of multiple sets of multiple resource blocks set by SIB1. An initial downlink sub-BWP may consist of multiple resource blocks that are consecutive in the frequency domain. For example, an initial downlink sub-BWP may be one of multiple downlink sub-BWPs set within an initial downlink BWP whose BWP ID set by SIB1 is 0. For example, each downlink sub-BWP may be assigned a different BWPID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.). In this case, the initial downlink BWP and the downlink sub-BWP settings are set by SIB1.

[0135] Terminal device 1 may transmit an uplink signal (e.g., PUSCH, PUCCH, PRACH, and / or Msg3 in a random access procedure) with frequency hopping applied using at least two of a plurality of initial uplink sub-BWPs. However, the initial uplink sub-BWPs are frequency resources that can be used at least during initial access before the RRC connection is established. Base station device 3 may receive an uplink signal with frequency hopping applied using at least two of a plurality of initial uplink sub-BWPs. However, the plurality of initial uplink sub-BWPs in this embodiment may be set within the frequency band of uplink BWPs to which the same identifier (BWP ID) is assigned. However, the plurality of initial uplink BWPs in this 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 consisting of a plurality of sets of a plurality of resource blocks set by SIB1. Each of the initial uplink sub-BWPs may consist of a plurality of resource blocks that are contiguous in the frequency domain. For example, multiple initial uplink BWPs may be multiple uplink sub-BWPs configured within an initial uplink BWP whose BWP ID, set by SIB1, is 0. For example, each uplink sub-BWP may be assigned a different BWP ID (e.g., ID: 0a, 0b) or sub-BWP ID (e.g., ID: 0, 1). In this case, the settings for the initial uplink BWP and the multiple uplink sub-BWPs are configured by SIB1.

[0136] Terminal device 1 may transmit an uplink signal (e.g., PUSCH, PUCCH, PRACH, and / or Msg3 in a random access procedure) with frequency hopping applied using one of a plurality of initial uplink sub-BWPs. Base station device 3 may receive an uplink signal with frequency hopping applied using one of a plurality of initial uplink sub-BWPs. An initial uplink sub-BWP may be a frequency band consisting of multiple sets of multiple resource blocks set by SIB1. An initial uplink sub-BWP may consist of multiple resource blocks that are consecutive in the frequency domain. For example, multiple initial uplink BWPs may be multiple uplink sub-BWPs set within an initial uplink BWP whose BWP ID set by SIB1 is 0. For example, each uplink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.). In that case, the initial uplink BWP setting and the uplink sub-BWP setting are configured by SIB1.

[0137] SIB1 may include downlinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one parameter for determining whether a cell is restricted in a cell where terminal device 1 is located may be included in downlinkConfigCommon, which indicates the common downlink parameters for a cell. downlinkConfigCommon may include a parameter indicating basic parameters for one downlink carrier and transmission in the corresponding cell (e.g., referred to as frequencyInfoDL), a parameter indicating the initial downlink BWP setting for a serving cell (e.g., referred to as initialDownlinkBWP), and / or a parameter indicating the settings for multiple initial downlink sub-BWPs (e.g., referred to as initialDownlinkBWP-rc). SIB1 may also include allocationBandwidth, a parameter indicating the maximum allocated bandwidth for a cell. allocationBandwidth may be included in any parameter within SIB1.

[0138] The information elements of a BWP may be parameters indicating the frequency location and bandwidth of the BWP. The information elements of a BWP may include a parameter subcarrierSpacing indicating the subcarrier spacing used in the BWP, a parameter locationAndBandwidth indicating the location and bandwidth (number of resource blocks) of the BWP in the frequency domain, and / or a parameter cyclicPrefix indicating whether a standard CP (cyclic prefix) or an extended CP is used in the BWP. In other words, a BWP is defined by the subcarrier spacing, CP, and location and bandwidth in the frequency domain. However, the value indicated by locationAndBandwidth may be interpreted as a Resource Indicator Value (RIV). The Resource Indicator Value indicates the starting PRB index and the number of consecutive PRBs of the BWP. However, the first PRB defining the region of the resource indicator value may be the PRB determined by the subcarrier spacing given by the BWP's subcarrierSpacing and the offsetToCarrier set in the SCS-SpecificCarrier included in the FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier spacing. Furthermore, the size defining the region of the resource indicator value may be 275.

[0139] Sub-BWPs (e.g., uplink sub-BWPs and downlink sub-BWPs) may be defined, like BWPs, by subcarrier spacing, CP, and location in the frequency domain and bandwidth in the frequency domain (such as the number of consecutive resource blocks).

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

[0141] The initialDownlinkBWP-rc contains information indicating the settings of the sub-BWP in the corresponding cell, information elements for the PDCCH setting, and / or information elements for the PDSCH setting. The initialDownlinkBWP-rc may be a parameter indicating the settings of each of several initial downlink sub-BWPs. However, each of the several initial downlink sub-BWPs set in initialDownlinkBWP-rc may be the initial downlink BWP (initial DL BWP). However, each of the several downlink sub-BWPs may be configured by the network to include CORESET0 in the frequency domain. The initialDownlinkBWP-rc may include a list of information indicating the location 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 location and bandwidth may correspond to each of the several initial downlink sub-BWPs. Each entry in the list of information indicating the frequency location and bandwidth may be a BWP information element (such as subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). Multiple initial downlink sub-BWPs may have a common bandwidth, and initialDownlinkBWP-rc may indicate a list of the frequency locations of the initial downlink sub-BWPs and the common bandwidth. Multiple initial downlink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and initialDownlinkBWP-rc may indicate a list of the frequency locations of the initial downlink BWPs and the common bandwidth, common subcarrierSpacing, and common cyclicPrefix. Alternatively, the subcarrierSpacing and cyclicPrefix indicated in initialDownlinkBWP may be set for multiple initial downlink sub-BWPs. In other words, initialDownlinkBWP-rc may be information for identifying the respective frequency locations and bandwidths of multiple initial downlink sub-BWPs.However, parameters indicating the settings for multiple initial downlink sub-BWPs may be set in the aforementioned initialDownlinkBWP. Parameters indicating the initial downlink BWP settings for 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 settings for multiple initial downlink sub-BWPs.

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

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

[0144] `allocationBandwidth` is information indicating the maximum allocated bandwidth for the downlink and / or uplink that terminal device 1 should support in the corresponding cell. The information indicating the maximum allocated bandwidth may be information that specifies the bandwidth by the number of resource blocks. However, the information indicating the maximum allocated bandwidth may be set for each subcarrier interval. The information indicating the maximum allocated bandwidth may be represented by an information element that includes a parameter `subcarrierSpacing` indicating the subcarrier interval and a parameter `allocationBandwidth` indicating the number of resource blocks of bandwidth. The maximum allocated bandwidth may be the maximum bandwidth supported by the RF circuit provided by terminal device 1. The maximum bandwidth may be the maximum bandwidth in which signals / channels transmitted on the downlink and / or uplink can each be scheduled simultaneously. If signals / channels are scheduled discretely on frequency on the downlink and / or uplink, the maximum allocated bandwidth may be the bandwidth of frequency resources in which the signals / channels can be discretely placed at a given time.

[0145] allocationBandwidth may be a parameter included in the information element of SCS-SpecificCarrier. The information indicating the maximum allocated bandwidth indicated by allocationBandwidth may be the number of resource blocks corresponding to the subcarrier interval indicated by subcarrierSpacing in the information element of SCS-SpecificCarrier that includes the parameter. The information indicating the maximum allocated bandwidth may also be information that identifies the maximum allocated bandwidth as a percentage value relative to the carrier bandwidth notified by SCS-SpecificCarrier.

[0146] allocationBandwidth may be a parameter included in the BWP information element. The information indicating the maximum allocated bandwidth indicated by allocationBandwidth may be the number of resource blocks corresponding to the subcarrier interval indicated by subcarrierSpacing in the BWP information element containing the parameter. The information indicating the maximum allocated bandwidth may also be information that identifies the maximum allocated bandwidth by a ratio value to the BWP bandwidth indicated by locationAndBandwidth included in the corresponding BWP information element. allocationBandwidth may be a parameter set for each BWP.

[0147] The allocationBandwidth parameter may be set as a common parameter to indicate the maximum allocated bandwidth for downlinks and uplinks in a given cell, or it may be set as separate parameters (for example, they may be called dlAllocationBandwidth and ulAllocationBandwidth, respectively).

[0148] Terminal device 1 may determine whether a cell is a restricted cell based on the bandwidth of the initial downlink BWP set for that cell. Terminal device 1 may also determine whether a cell is a restricted cell based on whether it supports a downlink channel bandwidth that is the same as or wider than the bandwidth of the initial downlink BWP set for that cell. For example, if terminal device 1 does not support a downlink channel bandwidth that is the same as or wider than the bandwidth of the initial downlink BWP set by SIB1, terminal device 1 may consider that cell to be a restricted cell. However, for terminal device 1 to support a certain bandwidth may mean that it is possible to tune / restune the bandwidth of its RF circuitry within that bandwidth and transmit / receive signals / channels within that bandwidth. For example, the downlink channel bandwidth supported by terminal device 1 may be the downlink channel bandwidth from which signals / channels can be received using RF tuning / RF retuning. Terminal device 1 may also determine whether a cell is a restricted cell based on the bandwidths of multiple initial downlink sub-BWPs set for that cell. Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports a downlink bandwidth equal to or greater than the widest bandwidth among the configured initial downlink sub-BWPs. For example, if terminal device 1 does not support a downlink bandwidth equal to or greater than the widest bandwidth among the configured initial downlink sub-BWPs, terminal device 1 may consider the cell to be a restricted cell. Terminal device 1 may also determine whether a cell is a restricted cell based on whether it supports a downlink bandwidth equal to or greater than the bandwidth commonly configured for the configured initial downlink sub-BWPs. For example, if terminal device 1 does not support a downlink bandwidth equal to or greater than the bandwidth commonly configured for the configured initial downlink sub-BWPs, terminal device 1 may consider the cell to be a restricted cell.Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports a downlink bandwidth equal to or greater than the bandwidth specified by the parameters that set up multiple initial downlink sub-BWPs notified by SIB1. For example, if terminal device 1 does not support a downlink bandwidth equal to or greater than the bandwidth specified by the parameters that set up multiple initial downlink sub-BWPs notified by SIB1, terminal device 1 may consider the cell to be a restricted cell. Terminal device 1 may also determine whether a cell is a restricted cell based on whether it supports a downlink bandwidth equal to or greater than the reference bandwidth specified by the bandwidth notified by SIB1. For example, if terminal device 1 does not support a downlink bandwidth equal to or greater than the reference bandwidth specified by the bandwidth notified by SIB1, terminal device 1 may consider the cell to be a restricted cell. However, the reference bandwidth may be the bandwidth specified by the bandwidth of one initial downlink BWP notified by SIB1 and the number of initial downlink sub-BWPs that are set up. However, the reference bandwidth may be the bandwidth determined by dividing one initial downlink BWP notified by SIB1 by a predetermined number.

[0149] In this embodiment, terminal device 1 receives information indicating the maximum allocated bandwidth in the SIB1 corresponding to a certain cell, and may determine whether the cell is a restricted cell based on the information indicating the maximum allocated bandwidth. However, the information indicating the maximum allocated bandwidth may be information indicating the maximum allocated bandwidth for the downlink. However, the information indicating the maximum allocated bandwidth may be information indicating the maximum allocated bandwidth for the uplink. However, the information indicating the maximum allocated bandwidth may be information indicating the maximum allocated bandwidth common to both the downlink and the uplink.

[0150] In this embodiment, terminal device 1 receives carrier bandwidth information, initial downlink BWP bandwidth information, and information indicating the maximum allocated bandwidth (which may also be information indicating the maximum allocated bandwidth for downlinks) in an SIB1 corresponding to a certain cell, and may determine whether the cell is a restricted cell based on whether the device supports a downlink channel bandwidth setting that is less than or equal to the carrier bandwidth and greater than or equal to the initial downlink BWP bandwidth, and whether the device supports a downlink allocated bandwidth greater than or equal to the maximum allocated bandwidth.

[0151] Terminal device 1 may determine whether a 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 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, terminal device 1 may consider the cell to be a restricted cell. However, the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier interval of the initial downlink BWP set in the received SIB1. However, the carrier bandwidth may be the carrier bandwidth corresponding to a common subcarrier interval of multiple initial downlink sub-BWPs set in the received SIB1.

[0152] Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports a downlink allocated bandwidth that is equal to or wider than the maximum allocated bandwidth (or greater than or equal to the maximum allocated bandwidth) indicated by SIB1 (which may be the maximum allocated bandwidth for downlinks). However, the downlink allocated bandwidth may be the maximum number of resource blocks of bandwidth for downlink signals and / or downlink channels scheduled by base station device 3. However, if downlink signals and / or downlink channels are discretely arranged in the frequency domain by base station device 3, the downlink channel allocated bandwidth may be the bandwidth from the lowest frequency to the highest frequency of one or more discretely arranged downlink signals and / or downlink channels. Figure 17 shows an example of the relationship between the carrier bandwidth, initial downlink BWP and maximum allocated bandwidth in a cell and the downlink channel bandwidth and downlink allocated bandwidth supported by terminal device 1, according to an embodiment of the present invention. In Figure 17, the downlink channel bandwidth supported by terminal device 1 is narrower than the carrier bandwidth in the cell and wider than the initial downlink BWP bandwidth in the cell, and the downlink allocation bandwidth supported by terminal device 1 is wider than the maximum allocation bandwidth in the cell. In such cases, terminal device 1 does not need to consider the cell as a restricted cell based on the downlink channel bandwidth and downlink allocation bandwidth that it supports. However, if the downlink channel bandwidth supported by terminal device 1 is not less than or equal to the carrier bandwidth and greater than or equal to the initial downlink BWP bandwidth, terminal device 1 may consider the cell as a restricted cell. However, if the downlink channel allocation bandwidth supported by terminal device 1 is narrower than the maximum allocation bandwidth, terminal device 1 may consider the cell as a restricted cell.

[0153] Figure 18 is a flowchart showing an example of the process for determining a restricted cell in terminal device 1 of this embodiment. In step S1001 of Figure 18, terminal device 1 determines whether it supports a downlink channel bandwidth that is less than or equal to the carrier bandwidth indicated by the SIB and greater than or equal to the bandwidth of the initial downlink BWP. If the determination is yes (S1001-Yes), in step S1002 it determines whether it supports a downlink allocated bandwidth greater than or equal to the maximum allocated bandwidth for the cell set in SIB1. If the determination in step S1001 or step S1002 is no (S1001-No or S1002-No), terminal device 1 considers the cell to be a restricted cell (S1003).

[0154] SIB1 may include uplinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one parameter for determining whether a cell is restricted in a cell may be included in uplinkConfigCommon, which indicates a common uplink parameter for a cell. uplinkConfigCommon may include a parameter indicating basic parameters for one uplink carrier and transmission (e.g., called frequencyInfoUL), a parameter indicating the initial uplink BWP setting for a serving cell (e.g., called initialUplinkBWP), and / or parameters indicating the settings for multiple initial uplink sub-BWPs (e.g., called initialUplinkBWP-rc). Information indicating the maximum allocated bandwidth on the uplink, ulAllocationBandwidth, may be included in uplinkConfigCommon.

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

[0156] The initialUplinkBWP-rc contains information indicating the settings of sub-BWPs, PUCCH setting information elements, and / or PUSCH setting information elements. initialUplinkBWP-rc may be parameters indicating the settings of each of several initial uplink sub-BWPs. However, each of the several initial uplink sub-BWPs set in initialUplinkBWP-rc may be an initial uplink BWP (initial UL BWP). However, each of the several uplink sub-BWPs may be configured by the network to include a physical random access channel resource in the frequency domain. initialUplinkBWP-rc may also include a list of information indicating frequency location and bandwidth. Each entry in the list of information indicating frequency location and bandwidth may correspond to each of the several initial uplink sub-BWPs. Each entry in the list of information indicating frequency location and bandwidth may be a BWP information element (such as subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). Multiple initial uplink sub-BWPs may have a common bandwidth, and initialUplinkBWP-rc may show a list of the frequency locations of the initial uplink sub-BWPs and the common bandwidth. Multiple initial uplink sub-BWPs may have a common subcarrierSpacing and a common cyclicPrefix, and initialUplinkBWP-rc may show a list of the frequency locations of the initial uplink BWPs and the common bandwidth, common subcarrierSpacing, and common cyclicPrefix. Alternatively, the subcarrierSpacing and cyclicPrefix shown in initialUplinkBWP may be set for multiple initial uplink sub-BWPs. That is, initialUplinkBWP-rc may be information for identifying the respective frequency locations and bandwidths of multiple initial uplink sub-BWPs. However, the parameters indicating the settings for multiple initial uplink sub-BWPs may be set in the aforementioned initialUplinkBWP.The parameters indicating the initial uplink BWP settings for a serving cell may include parameters indicating the frequency position and bandwidth of the initial uplink BWP, the subcarrierSpacing of the initial uplink BWP, the cyclicPrefix of the initial uplink BWP, and parameters indicating the settings for multiple initial uplink sub-BWPs.

[0157] Terminal device 1 may consider a cell to be a restricted cell if it does not support any frequency bands for the TDD downlink or FDD uplink for the frequency bands shown in the frequencyBandList included in frequencyInfoDL and the frequencyBandList included in frequencyInfoUL. Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports one or more frequency bands for the TDD downlink for the frequency bands shown in the frequencyBandList included in frequencyInfoDL, or whether it supports one or more frequency bands for the FDD uplink for the frequency bands shown in the frequencyBandList included in frequencyInfoUL. For example, terminal device 1 may determine whether a cell is a restricted cell based on the frequency bands shown in the frequencyBandList included in frequencyInfoDL and / or the frequency bands shown in the frequencyBandList included in frequencyInfoUL, and / or the capabilities of terminal device 1. For example, if terminal device 1 does not support any frequency bands for the TDD downlink in the frequencyBandList included in frequencyInfoDL, and terminal device 1 does not support any frequency bands for the FDD uplink in the frequencyBandList included in frequencyInfoUL, terminal device 1 may consider that cell to be a restricted cell.

[0158] Terminal device 1 may have multiple initial uplink sub-BWPs (initial uplink sub-BWPs) configured by the received SIB1. Terminal device 1 may determine whether a cell is a restricted cell based on the bandwidth of the initial uplink BWP configured by the received SIB1 corresponding to that cell. Terminal device 1 may also determine whether a cell is a restricted cell based on whether it supports an uplink bandwidth equal to or wider than the bandwidth of the initial uplink BWP configured by the SIB1. For example, if terminal device 1 does not support an uplink bandwidth equal to or wider than the bandwidth of the initial uplink BWP configured by the SIB1, terminal device 1 may consider that cell to be a restricted cell. Terminal device 1 may also determine whether a cell is a restricted cell based on the bandwidth of multiple initial uplink sub-BWPs configured by the received SIB1 corresponding to that cell. Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports an uplink bandwidth equal to or greater than the widest bandwidth among the multiple initial uplink sub-BWPs set by SIB1. For example, if terminal device 1 does not support an uplink bandwidth equal to or greater than the widest bandwidth among the multiple initial uplink sub-BWPs set by SIB1, terminal device 1 may consider the cell to be a restricted cell. Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports an uplink bandwidth equal to or greater than the bandwidth commonly set for multiple initial uplink sub-BWPs set by SIB1. For example, if terminal device 1 does not support an uplink bandwidth equal to or greater than the bandwidth commonly set for multiple initial uplink sub-BWPs set by SIB1, terminal device 1 may consider the cell to be a restricted cell. Terminal device 1 may determine whether a 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 that set up a plurality of initial uplink sub-BWPs notified by SIB1.For example, if terminal device 1 does not support an uplink bandwidth that is the same as or wider than the bandwidth specified by the parameters that configure multiple initial uplink sub-BWPs notified by SIB1, terminal device 1 may consider the cell to be a restricted cell. Terminal device 1 may determine whether a 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 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, terminal device 1 may consider the cell to be a restricted cell. However, the reference bandwidth may be the bandwidth specified by the SIB1 that is the same as or wider than the bandwidth of one initial uplink BWP and the number of initial uplink sub-BWPs configured. However, the reference bandwidth may be the bandwidth specified by the SIB1 that is the same as or wider than the bandwidth of one initial uplink BWP and a predetermined number.

[0159] Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports an uplink channel bandwidth that is the same as or narrower than the carrier bandwidth indicated by SIB1. However, for terminal device 1 to support a certain bandwidth, it may mean that it can tune / retune the bandwidth of its RF circuitry within that bandwidth and transmit / receive signals / channels within that bandwidth. For example, the uplink channel bandwidth supported by terminal device 1 may be the channel bandwidth of the uplink that can transmit signals / channels using RF tuning / RF retuning. For example, if terminal device 1 does not support an uplink channel bandwidth that is the same as or narrower than the carrier bandwidth indicated by the received SIB1, terminal device 1 may consider the cell to be a restricted cell. However, the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier interval of the initial uplink BWP set in the received SIB1. However, the carrier bandwidth may be the carrier bandwidth corresponding to the common subcarrier interval of multiple initial uplink sub-BWPs set in the received SIB1.

[0160] In this embodiment, terminal device 1 receives carrier bandwidth information, initial uplink BWP bandwidth information, and information indicating the maximum allocated bandwidth (which may be information indicating the maximum allocated bandwidth of the uplink) from an SIB1 corresponding to a certain cell, and may determine whether the cell is a restricted cell based on whether the device supports an uplink channel bandwidth that is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the initial uplink BWP bandwidth, and whether the device supports an uplink allocated bandwidth greater than or equal to the maximum allocated bandwidth.

[0161] Terminal device 1 may determine whether a 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 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, terminal device 1 may consider the cell to be a restricted cell. However, the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier interval of the initial uplink BWP set in the received SIB1. However, the carrier bandwidth may be the carrier bandwidth corresponding to a common subcarrier interval of multiple initial uplink sub-BWPs set in the received SIB1.

[0162] Terminal device 1 may determine whether a cell is a restricted cell based on whether it supports an uplink allocated bandwidth that is equal to or wider than (greater than or equal to) the maximum allocated bandwidth indicated by SIB1 (which may be the maximum allocated bandwidth for the uplink). However, the uplink allocated bandwidth may be the maximum number of resource blocks of bandwidth for uplink signals and / or uplink channels scheduled by base station device 3. However, if the uplink signals and / or uplink channels are discretely arranged in the frequency domain by base station device 3, the uplink channel allocated bandwidth may be the bandwidth from the lowest frequency to the highest frequency of one or more discretely arranged uplink signals and / or uplink channels. Figure 19 shows an example of the relationship between the carrier bandwidth, initial uplink BWP and maximum allocated bandwidth in a cell and the uplink channel bandwidth and uplink allocated bandwidth supported by terminal device 1, according to an embodiment of the present invention. In Figure 19, the uplink channel bandwidth supported by terminal device 1 is narrower than the carrier bandwidth in the cell and wider than the initial uplink BWP bandwidth in the cell, and the uplink allocation bandwidth supported by terminal device 1 is wider than the maximum allocation bandwidth in the cell. In such cases, terminal device 1 does not need to consider the cell as a restricted cell based on the uplink channel bandwidth and uplink allocation bandwidth that it supports. However, if the uplink channel bandwidth supported by terminal device 1 is not less than or equal to the carrier bandwidth and less than or equal to the initial uplink BWP bandwidth, terminal device 1 may consider the cell as a restricted cell. However, if the uplink channel allocation bandwidth supported by terminal device 1 is narrower than the maximum allocation bandwidth, terminal device 1 may consider the cell as a restricted cell.

[0163] Figure 20 is a flowchart showing another example of the process for determining a restricted cell in terminal device 1 of this embodiment. In step S2001 of Figure 20, terminal device 1 determines whether it supports an uplink channel bandwidth that is less than or equal to the carrier bandwidth indicated by the SIB and greater than or equal to the bandwidth of the initial uplink BWP. If the determination is yes (S2001-Yes), in step S2002 it determines whether it supports an uplink allocated bandwidth greater than or equal to the maximum allocated bandwidth for the cell set in SIB1. If the determination in step S2001 or step S2002 is no (S2001-No or S2002-No), terminal device 1 considers the cell to be a restricted cell (S2003).

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

[0165] However, the parameters set in SIB1 may be announced in SIB1 (or REDCAP SIB1), in other SIBs (or REDCAP SIBs), or notified via RRC messages.

[0166] The reference signals described below 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, downlink reference signals, synchronization signals, and / or SS / PBCH blocks may be referred to as reference signals. Reference signals used in the downlink include downlink reference signals, synchronization signals, SS / PBCH blocks, downlink DMRS, CSI-RS, etc. Reference signals used in the uplink include uplink reference signals, SRS, and / or uplink DMRS, etc.

[0167] Furthermore, the reference signal may be used for radio resource measurement (RRM). The reference signal may also be used for beam management.

[0168] Beam management may be a procedure performed by base station 3 and / or terminal 1 to match the directivity of the analog and / or digital beams at the transmitting device (base station 3 in the case of a downlink, and terminal 1 in the case of an uplink) with the directivity of the analog and / or digital beams at the receiving device (terminal 1 in the case of a downlink, and base station 3 in the case of an uplink) in order to obtain beam gain.

[0169] The following procedures may be included as part of the procedure for configuring, setting up, or establishing a beam pair link. Beam selection • Beam refinement Beam recovery

[0170] For example, beam selection may be a procedure for selecting a beam in communication between base station equipment 3 and terminal equipment 1. Beam improvement may be a procedure for selecting a beam with higher gain, or for changing the optimal beam between base station equipment 3 and terminal equipment 1 by moving terminal equipment 1. Beam recovery may be a procedure for re-selecting a beam when the quality of the communication link deteriorates due to blockage caused by obstacles or the passage of people in communication between base station equipment 3 and terminal equipment 1.

[0171] Beam management may include beam selection and beam improvement. Beam recovery, also known as beam failure recovery, may include the following procedures. • Detection of beam failure • Discovery of a new beam • Sending a beam recovery request • Monitoring responses to beam recovery requests

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

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

[0174] Two antenna ports are said to be QCL (Quick Chain Relation) if the long-term property of a channel carrying a symbol at one antenna port can be inferred from the channel carrying a symbol at the other antenna port. The long-term property of a channel includes one or more of the following: delay spread, Doppler spread, Doppler shift, mean gain, and mean delay. For example, if antenna port 1 and antenna port 2 are QCL with respect to mean delay, it means that the reception timing at antenna port 2 can be inferred from the reception timing at antenna port 1.

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

[0176] For example, if the receiving spatial parameters between antenna port 1 and antenna port 2 can be considered QCL, it means that the receiving beam receiving the signal from antenna port 2 can be inferred from the receiving beam (receiving spatial filter) receiving the signal from antenna port 1.

[0177] A combination of long-interval characteristics that can be considered a QCL type may be defined. For example, the following types may be defined: Type A: Doppler shift, Doppler spread, mean delay, delay spread Type B: Doppler shift, Doppler spread • Type C: Mean delay, Doppler shift • Type D: Receiving spatial parameters

[0178] The above-mentioned QCL types may be set and / or indicated as a Transmission Configuration Indication (TCI) that assumes a QCL between one or two reference signals and PDCCH or PDSCH DMRS in the RRC and / or MAC layer and / or DCI. For example, if one state of the TCI when terminal device 1 receives a PDCCH is set and / or indicated as SS / PBCH block index #2 and QCL type A + QCL type B, then when terminal device 1 receives the PDCCH DMRS, it may receive the PDCCH DMRS by considering the Doppler shift, Doppler spread, mean delay, delay spread, received spatial parameters, and channel long-interval characteristics at the reception of SS / PBCH block index #2, and perform synchronization and propagation path estimation. In this case, the reference signal indicated by the TCI (SS / PBCH block in the above example) may be called the source reference signal, and the reference signal affected by the long-interval characteristics inferred from the channel long-interval characteristics at the reception of the source reference signal (PDCCH DMRS in the above example) may be called the target reference signal. Furthermore, the TCI may be configured in RRC with one or more TCI states and a combination of a source reference signal and a QCL type for each state, and this may be instructed to terminal device 1 by the MAC layer or DCI.

[0179] In this method, the operation of base station equipment 3 and terminal equipment 1, which are equivalent to beam management, may be defined by the assumption of a QCL in the spatial domain and radio resources (time and / or frequency) as beam management and beam direction / reporting.

[0180] Figure 21 shows an example of beamforming. Multiple antenna elements are connected to a single transceiver unit (TXRU) 50, and the phase is controlled by a phase shifter 51 for each antenna element. By transmitting from the antenna element 52, the beam can be directed in any direction relative to the transmitted signal. Typically, the TXRU may be defined as an antenna port, and in terminal device 1, only the antenna port may be defined. Because the directivity can be directed in any direction by controlling the phase shifter 51, the base station device 3 can communicate with terminal device 1 using a high-gain beam.

[0181] The configuration of the apparatus in this embodiment will be described below.

[0182] Figure 22 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment. As shown in the figure, the terminal device 1 is composed of a wireless transceiver unit 10 and a higher-layer processing unit 14. The wireless transceiver unit 10 is composed of an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The higher-layer processing unit 14 is composed of a media access control layer processing unit 15 and a wireless resource control layer processing unit 16. The wireless transceiver unit 10 is also referred to as the transmitting unit 10, receiving unit 10, monitoring unit 10, or physical layer processing unit 10. The higher-layer processing unit 14 is also referred to as the processing unit 14, measurement unit 14, selection unit 14, determination unit 14, or control unit 14.

[0183] The upper layer processing unit 14 outputs the uplink data (which may be called a transport block) generated by user operations, etc., to the wireless transceiver unit 10. The upper layer processing unit 14 performs some 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 also have a function to acquire bit information of MIB (which may be a REDCAP MIB), SIB1 (which may be a REDCAP SIB1), and other SIBs (which may be a REDCAP SIB). The upper layer processing unit 14 may also have a function to determine whether a cell is a restricted cell based on the information in the system information block (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB).

[0184] The media access control layer processing unit 15, located in the upper layer processing unit 14, performs MAC layer (media access control layer) processing. The media access control layer processing unit 15 controls the transmission of scheduling requests based on various setting information / parameters managed by the wireless resource control layer processing unit 16.

[0185] The wireless resource control layer processing unit 16, located within the upper layer processing unit 14, performs processing at the RRC layer (wireless resource control layer). The wireless resource control layer processing unit 16 manages various setting information / parameters of its own device. The wireless resource control layer processing unit 16 sets various setting information / parameters based on the upper layer signals received from the base station device 3. In other words, the wireless resource control layer processing unit 16 sets various setting information / parameters based on information indicating the various setting information / parameters received from the base station device 3. The wireless resource control layer processing unit 16 controls (specifies) resource allocation based on the downlink control information received from the base station device 3.

[0186] The wireless transceiver 10 performs physical layer processing such as modulation, demodulation, coding, and decoding. The wireless transceiver 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit 14. The wireless transceiver 10 generates a transmission signal by modulating and coding the data, and transmits it to the base station device 3, etc. The wireless transceiver 10 outputs upper layer signals (RRC messages), DCI, etc. received from the base station device 3 to the upper layer processing unit 14. The wireless transceiver 10 also generates and transmits uplink signals (including PUCCH and / or PUSCH) based on instructions from the upper layer processing unit 14. The wireless transceiver 10 may also have a function to receive random access responses, PDCCH, and / or PDSCH. The wireless transceiver 10 may also have a function to transmit PRACH (which may be a random access preamble), PUCCH, and / or PUSCH. The wireless transceiver 10 may also have a function to receive DCI with PDCCH. The wireless transceiver 10 may have a function to output the DCI received by the PDCCH to the upper layer processing unit 14. The wireless transceiver 10 may have a function to receive SSB, PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The wireless transceiver 10 may have a function to receive SS / PBCH blocks and / or REDCAP PBCH blocks. The wireless transceiver 10 may have a function to receive system information blocks (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB) corresponding to a predetermined cell.

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

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

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

[0190] The RF unit 12 removes extraneous frequency components from the analog signal input from the baseband unit 13 using a low-pass filter, upconverts the analog signal to the carrier frequency, and transmits it via the antenna unit 11. The RF unit 12 also amplifies the power. The RF unit 12 may also have a function to determine the transmission power of the uplink signal and / or uplink channel to be transmitted in the cell in service. The RF unit 12 is also referred to as the transmission power control unit.

[0191] The RF unit 12 may use an antenna switch to connect the filter provided by the antenna unit 11 and the RF unit 12 when receiving a signal, and to connect the power amplifier provided by the antenna unit 11 and the RF unit 12 when transmitting a signal.

[0192] The RF unit 12 may also have a function to adjust / retune (tune / retune) the frequency band to which the RF circuit is applied within the downlink BWP if the bandwidth of the set downlink BWP (e.g., initial downlink BWP) is wider than the bandwidth supported by the receiver of the device (which may be called the allocated bandwidth). However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when downconverting the received signal to a baseband signal.

[0193] The RF unit 12 may also have a function to adjust / readjust the frequency band to which the RF circuit is applied within the uplink BWP if the bandwidth of the set uplink BWP (e.g., initial downlink BWP) is wider than the bandwidth supported by the transmitter of the device (which may be called the allocated bandwidth). However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when upconverting an analog signal to the carrier frequency.

[0194] Figure 23 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment. As shown in the figure, the base station device 3 is composed of a wireless transceiver unit 30 and a higher layer processing unit 34. The wireless transceiver unit 30 is composed of an antenna unit 31, an RF unit 32, and a baseband unit 33. The higher layer processing unit 34 is composed of a media access control layer processing unit 35 and a wireless resource control layer processing unit 36. The wireless transceiver unit 30 is also referred to as the transmitting unit 30, receiving unit 30, monitoring unit 30, or physical layer processing unit 30. A control unit that controls the operation of each unit based on various conditions may also be provided separately. The higher layer processing unit 34 is also referred to as the processing unit 34, determination unit 34, or control unit 34.

[0195] The upper layer processing unit 34 performs some or all of the processing in 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 34 may also have a function to generate DCI based on the upper layer signals transmitted to the terminal device 1 and the time resources for transmitting PUSCH. The upper layer processing unit 34 may also have a function to output the generated DCI, etc., to the radio transceiver unit 30. The upper layer processing unit 34 may also have a function to generate bit information for the transport block of the MIB. The upper layer processing unit 34 may also have a function to generate bit information for the transport block of the REDCAP MIB. The upper layer processing unit 34 may also have a function to generate system information blocks (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB) that include information for the terminal device to determine whether a given cell is a regulated cell.

[0196] The media access control layer processing unit 35, located in the upper layer processing unit 34, performs MAC layer processing. The media access control layer processing unit 35 processes scheduling requests based on various configuration information / parameters managed by the wireless resource control layer processing unit 36.

[0197] The wireless resource control layer processing unit 36, located in the upper layer processing unit 34, performs RRC layer processing. The wireless resource control layer processing unit 36 ​​generates DCI (uplink grant, downlink grant) containing resource allocation information for the terminal device 1. The wireless resource control layer processing unit 36 ​​generates or obtains from the upper layer node DCI, downlink data (transport block (TB), random access response (RAR)) placed in the PDSCH, system information, RRC messages, MAC CE (Control Element), etc., and outputs them to the wireless transceiver 30. The wireless resource control layer processing unit 36 ​​also manages various setting information / parameters for each terminal device 1. The wireless resource control layer processing unit 36 ​​may set various setting information / parameters for each terminal device 1 via signals from the upper layer. That is, the wireless resource control layer processing unit 36 ​​transmits / notifies information indicating various setting information / parameters. The wireless resource control layer processing unit 36 ​​may transmit / notify information to identify the setting of one or more reference signals in a certain cell.

[0198] When base station device 3 sends an RRC message, MAC CE, and / or PDCCH to terminal device 1, and terminal device 1 processes based on its reception, base station device 3 performs its processing (controlling terminal device 1 and the system) assuming that the terminal device is performing that processing. In other words, base station device 3 sends an RRC message, MAC CE, and / or PDCCH to terminal device 1 to cause the terminal device to perform processing based on its reception.

[0199] The wireless transceiver 30 transmits higher-layer signals (RRC messages), DCI, etc., to the terminal device 1. The wireless transceiver 30 also receives uplink signals transmitted from the terminal device 1 based on instructions from the higher-layer processing unit 34. The wireless transceiver 30 may have a function to transmit PDCCH and / or PDSCH. The wireless transceiver 30 may have a function to receive one or more PUCCH and / or PUSCH. The wireless transceiver 30 may have a function to transmit DCI in PDCCH. The wireless transceiver 30 may have a function to transmit DCI output by the higher-layer processing unit 34 in PDCCH. The wireless transceiver 30 may have a function to transmit SSB, PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and / or DMRS for REDCAP PBCH. The wireless transceiver 30 may have a function to transmit SS / PBCH blocks and / or REDCAP PBCH blocks. The wireless transceiver 30 may have a function to transmit RRC messages (which may also be RRC parameters). The wireless transceiver 30 may also have a function to transmit system information blocks (SIB1, REDCAP SIB1, SIB, and / or REDCAP SIB) from the terminal device 1. Some other functions of the wireless transceiver 30 are the same as those of the wireless transceiver 10 and are therefore not described. Note that if the base station device 3 is connected to one or more transmission / reception points 4, some or all of the functions of the wireless transceiver 30 may be included in each transmission / reception point 4.

[0200] Furthermore, the upper layer processing unit 34 transmits (transfers) or receives control messages or user data between base station devices 3 or between higher-level network devices (MME, S-GW (Serving-GW)) and base station devices 3. In Figure 23, other components of base station device 3 and the transmission paths of data (control information) between components are omitted, but it is clear that it has multiple blocks as components that have other functions necessary to operate as base station device 3. For example, the upper layer processing unit 34 includes a radio resource management layer processing unit and an application layer processing unit.

[0201] In the diagram, "parts" can also be expressed by terms such as section, circuit, component, device, or unit, and represent elements that realize the functions and procedures of terminal device 1 and base station device 3.

[0202] Each of the parts designated by reference numerals 10 to 16 in the terminal device 1 may be configured as a circuit. Each of the parts designated by reference numerals 30 to 36 in the base station device 3 may be configured as a circuit.

[0203] (1) A terminal device 1 in a first aspect of the present invention comprises a receiving unit 10 that receives a system information block containing first information for setting parameters of a first cell, and a processing unit 14, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell (carrierbandwidth), a parameter indicating the bandwidth of the initial uplink BWP of the first cell (initialUplinkBWP / locationAndBandwidth), and a parameter indicating the maximum allocated bandwidth of the first cell (allocationBandwidth), and the processing unit 14 determines whether the first cell is a barred cell based on whether the terminal device supports an uplink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial uplink BWP, and whether the terminal device 1 supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth. The system determines whether it is a cell, the allocated bandwidth is the maximum number of resource blocks of bandwidth for the uplink channel scheduled by the base station device 3, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that can be received in the first cell by the terminal device 1 adjusting the frequency position of the transmitter of the terminal device 1.

[0204] (2) The base station device 3 in the second aspect of the present invention comprises a processing unit 34 that generates a system information block including first information for setting parameters of a first cell, and a transmitting unit 30 that transmits the system information block to a terminal device 1, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell (carrierbandwidth), a parameter indicating the bandwidth of the initial uplink BWP of the first cell (initialUplinkBWP / locationAndBandwidth), and a parameter indicating the maximum allocated bandwidth of the first cell (allocationBandwidth), and the terminal This information causes terminal device 1 to determine whether the first cell is a restricted cell, based on whether device 1 supports an uplink channel bandwidth setting which is less than or equal to the carrier bandwidth and greater than or equal to the initial uplink BWP bandwidth, and whether terminal device 1 supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of uplink channel bandwidth scheduled by base station device 3, and the maximum transmit bandwidth setting indicates the number of resource blocks of bandwidth that terminal device 1 can receive by adjusting the frequency position of the transmitter of terminal device 1.

[0205] (3) The terminal device 1 in the third aspect of the present invention comprises a receiving unit 10 that receives a system information block including first information for setting parameters of a first cell, and a processing unit 14, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell (carrierbandwidth), a parameter indicating the bandwidth of the initial downlink BWP of the first cell (initialDownlinkBWP, locationAndBandwidth), and a parameter indicating the maximum allocated bandwidth of the first cell (allocationBandwidth), and the processing unit 14 determines whether the first cell is a restricted cell based on whether the terminal device supports a downlink channel bandwidth which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the bandwidth of the initial downlink BWP, and whether the terminal device 1 supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of the downlink channel bandwidth scheduled by the base station device 3, and the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device 1 can receive by adjusting the frequency position of the receiver of the terminal device 1 in the first cell.

[0206] (4) The base station device 3 in the fourth aspect of the present invention comprises a processing unit 34 that generates a system information block including first information for setting parameters of a first cell, and a transmitting unit 30 that transmits the system information block to a terminal device 1, wherein the first information includes a parameter indicating the carrier bandwidth of the first cell (carrierbandwidth), a parameter indicating the bandwidth of the initial downlink BWP of the first cell (initialDownlinkBWP, locationAndBandwidth), and a parameter indicating the maximum allocated bandwidth of the first cell (allocationBandwidth), and the terminal This information causes the terminal device 1 to determine whether the first cell is a restricted cell, based on whether the terminal device 1 supports a downlink channel bandwidth setting that is less than or equal to the carrier bandwidth and greater than or equal to the initial downlink BWP bandwidth, and whether the terminal device 1 supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, wherein the allocated bandwidth is the maximum number of resource blocks of the downlink channel bandwidth scheduled by the base station device 3, and the maximum transmit bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device 1 can receive by adjusting the frequency position of the receiver of the terminal device 1.

[0207] This enables efficient communication between terminal device 1 and base station device 3. For example, terminal device 1 can perform random access procedures with base station device 3 based on its terminal type or the RSRP of SSB.

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

[0209] Furthermore, a program for realizing the functions of an embodiment relating to one aspect of the present invention may be recorded on a computer-readable recording medium. This can also be realized by loading the program recorded on this recording medium into a computer system and executing it. Here, "computer system" refers to a computer system built into the device, and includes hardware such as an operating system and peripheral devices. Also, "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically holds a program for a short period of time, or any other computer-readable recording medium.

[0210] Furthermore, each functional block or feature of the apparatus used in the embodiments described above may be implemented or executed by an electrical circuit, such as an integrated circuit or a combination of integrated circuits. An electrical circuit designed to perform the functions described herein may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, a conventional processor, controller, microcontroller, or state machine. The aforementioned electrical circuits may consist of digital circuits or analog circuits. Also, if advances in semiconductor technology lead to the emergence of integrated circuit technologies that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on such technologies.

[0211] In one embodiment of the present invention, an example of its application to a communication system consisting of a base station device and a terminal device was described, but it is also applicable to systems where terminals communicate with each other, such as D2D (Device to Device).

[0212] It should be noted that the present invention is not limited to the embodiments described above. Although the embodiments describe an example of a device, the present invention is not limited thereto and can be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0213] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, various modifications are possible within the scope of the claims for one aspect of the present invention, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Industrial applicability]

[0214] One aspect of the present invention can be used, for example, in communication systems, communication equipment (e.g., mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (e.g., communication chips), or programs. [Explanation of symbols]

[0215] 1 (1A, 1B) Terminal device 3 Base station equipment 4. Transmit / Receive Point (TRP) 10 Wireless Transceiver Unit 11 Antenna section 12 RF section 13. Baseband section 14. Upper Layer Processing Unit 15. Media Access Control Layer Processing Unit 16 Wireless Resource Control Layer Processing Unit 30 Wireless Transceiver Unit 31 Antenna section 32 RF section 33. Baseband section 34 Upper Layer Processing Unit 35. Media Access Control Layer Processing Unit 36 Wireless Resource Control Layer Processing Unit 50 Transmitter Unit (TXRU) 51 Phase Shifter 52 Antenna Elements

Claims

1. A terminal device, A receiving unit that receives a system information block containing first information for setting the parameters of the first cell, A processing unit, and The first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell. The processing unit determines whether the first cell is a restricted cell based on whether the terminal device supports an uplink channel bandwidth setting which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the initial uplink BWP bandwidth, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth. The allocated bandwidth is the maximum number of resource blocks of bandwidth for the uplink channel scheduled by the base station equipment. The maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that can be received by the terminal device in the first cell by adjusting the frequency position of the terminal device's transmitter.

2. Base station equipment, A processing unit that generates a system information block containing first information for setting the parameters of the first cell, The system comprises a transmitting unit that transmits the system information block to a terminal device, The first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell. This information causes the terminal device to determine whether the first cell is a restricted cell, based on whether the terminal device supports an uplink channel bandwidth setting which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the initial uplink BWP bandwidth, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth. The allocated bandwidth is the maximum number of resource blocks of bandwidth for the uplink channel scheduled by the base station equipment. The maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive by adjusting the frequency position of the transmitter of the terminal device, for the base station device.

3. A communication method for base station equipment, A system information block is generated that contains first information for setting the parameters of the first cell. The system information block is transmitted to the terminal device. The first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial uplink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell. This information causes the terminal device to determine whether the first cell is a restricted cell, based on whether the terminal device supports an uplink channel bandwidth setting which is a maximum transmission bandwidth setting of a bandwidth less than or equal to the carrier bandwidth and greater than or equal to the initial uplink BWP bandwidth, and whether the terminal device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth. The allocated bandwidth is the maximum number of resource blocks of bandwidth for the uplink channel scheduled by the base station equipment. A communication method in which the maximum transmission bandwidth setting indicates the number of resource blocks of bandwidth that the terminal device can receive by adjusting the frequency position of the transmitter of the terminal device.

Images