Terminal equipment, base station equipment, and communication method

Abstract

This terminal device receives first information which includes second information expressing an initial UL BWP parameter and third information expressing a PUSCH parameter. The second information includes fourth information expressing the bandwidth and the first frequency position of the initial UL BWP, and fifth information which expresses the sub-carrier interval. The initial UL BWP frequency position and the bandwidth are expressed by sixth information when the first information includes sixth information, which expresses the bandwidth and the second frequency position of the initial UL BWP, and are expressed by the fourth information when the first information does not contain the sixth information. The PUSCH is transmitted on the basis of the third information regardless of whether the first information contains or does not contain the sixth information.

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-79579, filed on May 10, 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 standardization 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) to which a large number of machine-type devices such as IoT (Internet of Things) are connected. Furthermore, in Release 17, which is a future release of NR, applications such as sensor networks, surveillance cameras, and / or wearable devices are assumed, and reduced capability (REDCAP) NR devices that do not require high requirements such as eMBB and URLLC while aiming to reduce costs and extend battery life are being studied (Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004] [Non-Patent Document 1] 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 Initiative] [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) In order to achieve the above objective, an aspect of the present invention has taken the following measures. That is, a terminal device in one aspect of the present invention comprises a receiving unit that receives first information and a transmitting unit that transmits a physical uplink shared channel on the initial uplink BWP, wherein the first information includes common parameters of the initial uplink BWP of a certain cell, second information that includes general-purpose parameters of the initial uplink BWP, and third information that includes common cell parameters of the physical uplink shared channel of the initial uplink BWP, the second information includes fourth information that includes the first frequency position and bandwidth of the initial uplink BWP, and the initial uplink B The first information includes a fifth piece of information indicating the subcarrier spacing of the channel used in the WP, and if the first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, the frequency position and bandwidth of the initial uplink BWP are indicated by the sixth piece of information; if the first information does not include the sixth piece of information, the frequency position and bandwidth of the initial uplink BWP are indicated by the fourth piece of information; and the transmitter transmits the physical uplink shared channel based on the third piece of information, regardless of whether the first information includes the sixth piece of information or not.

[0007] (2) Furthermore, a base station device in one aspect of the present invention includes a broadcasting unit that broadcasts first information, and a receiving unit that receives a first physical uplink shared channel from a first terminal device and a second physical uplink shared channel from a second terminal device, wherein the first information includes common parameters of the initial uplink BWP of a cell, second information that includes general-purpose parameters of the initial uplink BWP, and third information that includes common cell parameters of the physical uplink shared channel of the initial uplink BWP, and the second information includes the first frequency position and bandwidth of the initial uplink BWP. The first information includes a fourth piece of information and a fifth piece of information indicating the subcarrier spacing of the channel used in the initial uplink BWP, the first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, the frequency position and bandwidth of the initial uplink BWP for the first terminal device is indicated by the sixth piece of information, and the frequency position and bandwidth of the initial uplink BWP for the second terminal device is indicated by the fourth piece of information, and the transmitting unit transmits the first physical uplink shared channel and the second physical uplink shared channel based on the third piece of information.

[0008] (3) Furthermore, a communication method in one aspect of the present invention is a communication method for a terminal device, which receives first information, transmits a physical uplink shared channel on an initial uplink BWP, the first information includes common parameters of an initial uplink BWP of a certain cell, second information including general-purpose parameters of the initial uplink BWP, and third information including common cell parameters of the physical uplink shared channel of the initial uplink BWP, the second information includes fourth information indicating a first frequency position and bandwidth of the initial uplink BWP, and the initial uplink The first information includes a fifth piece of information indicating the subcarrier spacing of the channel used in the BWP, and if the first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, the frequency position and bandwidth of the initial uplink BWP are indicated by the sixth piece of information; if the first information does not include the sixth piece of information, the frequency position and bandwidth of the initial uplink BWP are indicated by the fourth piece of information; and the transmitter transmits the physical uplink shared channel based on the third piece of information, regardless of whether the first information includes the sixth piece of information or not.

[0009] (4) Furthermore, a communication method in one aspect of the present invention is a communication method for a base station device, comprising: broadcasting first information; receiving a first physical uplink shared channel from a first terminal device; receiving a second physical uplink shared channel from a second terminal device; the first information including common parameters of an initial uplink BWP of a cell; second information including general-purpose parameters of the initial uplink BWP; and third information including cell common parameters of the physical uplink shared channel of the initial uplink BWP; and the second information including a first frequency position and bandwidth of the initial uplink BWP. The first information includes a fourth piece of information and a fifth piece of information indicating the subcarrier spacing of the channel used in the initial uplink BWP, the first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, the frequency position and bandwidth of the initial uplink BWP for the first terminal device is indicated by the sixth piece of information, and the frequency position and bandwidth of the initial uplink BWP for the second terminal device is indicated by the fourth piece of information, and the transmitting unit transmits the first physical uplink shared channel and the second physical uplink shared channel based on the third piece of information. [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 examples of SS / PBCH blocks and SS burst sets according to embodiments of the present invention. [Figure 5]A diagram showing resources where PSS, SSS, PBCH, and DMRS for PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. [Figure 6] A diagram showing an example of RF tuning according to an embodiment of the present invention. [Figure 7] A diagram showing an example of the parameter configuration of the information element (IE) BWP-DownlinkCommon of initialDownlinkBWP according to an embodiment of the present invention. [Figure 8] A flowchart showing an example of processing related to the determination of the initial downlink BWP and the monitoring of PDCCH in the terminal device 1 according to an embodiment of the present invention. [Figure 9] A diagram showing an example of the parameter configuration of the information element (IE) BWP-UplinkCommon of initialUplinkBWP according to an embodiment of the present invention. [Figure 10] A flowchart showing an example of processing related to the determination of the initial uplink BWP and the transmission of PUSCH in the terminal device 1 according to an embodiment of the present invention. [Figure 11] 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 12] A schematic block diagram showing the configuration of the terminal device 1 according to an embodiment of the present invention. [Figure 13] 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] The terminal device 1 is also referred to as a user terminal, a mobile station device, a communication terminal, a mobile device, a terminal, a UE (User Equipment), or an MS (Mobile Station). However, the terminal device 1 may be a REDCAP NR device and may also be referred to as a REDCAP UE. The base station device 3 is also referred to as a radio base station device, a base station, a radio base station, a fixed station, a NB (Node B), an eNB (evolved Node B), a BTS (Base Transceiver Station), a BS (Base Station), a NR NB (NR Node B), a NNB, a TRP (Transmission and Reception Point), or a gNB. The base station device 3 may include a core network device. Further, the base station device 3 may include one or more transmission reception points 4 (transmission reception point). At least a part of the functions / processes of the base station device 3 described below may be functions / processes at each of the transmission reception points 4 included in the base station device 3. The base station device 3 may serve the terminal device 1 with the communication range (communication area) controlled by the base station device 3 as one or more cells. Further, the base station device 3 may serve the terminal device 1 with the communication range (communication area) controlled by one or more transmission reception points 4 as one or more cells. Further, the base station device 3 may divide one cell into a plurality of sub-areas (Beamed area) and serve the terminal device 1 in each sub-area. Here, the sub-area may be identified based on the index of the beam used in beamforming or the index of precoding.

[0015] In the present embodiment, the radio communication link from the base station device 3 to the terminal device 1 is referred to as a downlink. In the present embodiment, the radio communication link from the terminal device 1 to the base station device 3 is referred to as an 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). However, a BWP used in the downlink may be called a downlink BWP, and a BWP used in the uplink may be called an uplink BWP. Also, a slot may be defined as a Transmission Time Interval (TTI). A slot does not have to be defined as a TTI. A 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 (PRB) 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 (CRBs), 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 contained within a Bandwidth Part (BWP), and physical resource blocks are resource blocks numbered in ascending order from 0 that are contained within a BWP. A physical uplink channel is first mapped to a virtual resource block. Subsequently, the virtual resource block is mapped to a physical resource block. Hereafter, the resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

[0028] A BWP is a subset of consecutive resource blocks (which may be common resource blocks) of a given subcarrier spacing setting in a given carrier. Terminal device 1 may have up to four BWPs (downlink BWPs) configured on the downlink. There may be only one active downlink BWP (active downlink BWP) at any given time. Terminal device 1 may not expect to receive PDSCH, PDCCH, or CSI-RS outside the bandwidth of the active downlink BWP. Terminal device 1 may have up to four BWPs (uplink BWPs) configured on the uplink. There may be only one active uplink BWP (active uplink BWP) at any given time. Terminal device 1 does not transmit PUSCH or PUCCH outside the bandwidth of the active uplink BWP.

[0029] 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 both the downlink BWP and the uplink BWP. Here, given μ, the subcarrier spacing Δf is given by Δf = 2^μ·15 (kHz).

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

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

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

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

[0034] 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).

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

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

[0037] • PBCH (Physical Broadcast Channel) • PDCCH (Physical Downlink Control Channel) • PDSCH (Physical Downlink Shared Channel) • PUCCH (Physical Uplink Control Channel) PUSCH (Physical Uplink Shared Channel) PRACH (Physical Random Access Channel)

[0038] 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 Blocks (SIBs). However, the information indicating the settings for the PDCCH for SIB1 may be the information determining the control resource set (CORESET) 0 (CORESET0 is also called CORESET#0 or common CORESET), the common search space, and / or the required PDCCH parameters. However, CORESET indicates the resource elements of the PDCCH and consists of a set of PRBs for a certain number of OFDM symbols (e.g., 1 to 3 symbols) over a time period. CORESET0 may be the CORESET for at least the PDCCH that schedules SIB1. CORESET0 may be set in the MIB or via RRC signaling.

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

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

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

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

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

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

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

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

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

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

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

[0050] 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).

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

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

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

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

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

[0056] 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).

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

[0058] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0072] Figure 4 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 referred to as 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 4 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 referred to as an SSB period), and the SS / PBCH blocks consist of consecutive 4 OFDM symbols.

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

[0074] In Figure 4, a single SS / PBCH block has time / frequency multiplexing for PSS, SSS, PBCH, and DMRS for PBCH. Figure 5 is a table showing the resources where DMRS for PSS, SSS, PBCH, and PBCH are located within the SS / PBCH block.

[0075] 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).

[0076] 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).

[0077] 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 symb It 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.

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

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

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

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

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

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

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

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

[0086] 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 received MIB information, and / or the received SIB (which may be SIB1) information. 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.

[0087] 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").

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

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

[0090] 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).

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

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

[0093] The initial BWP, initial DL BWP, and initial UL BWP according to this embodiment may be, at least, a BWP, a DL BWP, and an UW BWP used during initial access before the RRC connection is established. However, the initial BWP, initial DL BWP, and initial UW BWP may be used after the RRC connection is established. However, the initial BWP, initial DL BWP, and initial UW BWP may be a BWP, a DL BWP, and an UW BWP with index 0 (#0), respectively.

[0094] The initial downlink BWP may be set by parameters provided in the MIB, parameters provided in SIB1, parameters provided in the SIB, and / or RRC parameters. For example, the initial downlink BWP may be set by the parameter initialDownlinkBWP provided in SIB1, however initialDownlinkBWP may be a parameter indicating the setting of the initial downlink BWP for a UE-specific (dedicated) UE.

[0095] 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 may be included in downlinkConfigCommon, which indicates the common downlink parameters for a cell. downlinkConfigCommon may include a parameter (e.g., called frequencyInfoDL) indicating the basic parameters for a single downlink carrier and transmission in the corresponding cell, and a parameter (e.g., called initialDownlinkBWP) indicating the initial downlink BWP setting for a serving cell. SIB1 may also include allocationBandwidth, which is a parameter indicating the maximum allocated bandwidth for a cell. allocationBandwidth may be included in any parameter within SIB1.

[0096] The information element (IE) of a BWP may be a parameter indicating the frequency location and bandwidth of the BWP. The information element 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 may be 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.

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

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

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

[0100] `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.

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

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

[0103] 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).

[0104] If the initialDownlinkBWP is not provided in the SIB1 (which may be another SIB or RRC parameter) 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 (such as CORESET0) 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 the initialDownlinkBWP is provided in the SIB1 received by terminal device 1, the initial downlink BWP may be defined by the initialDownlinkBWP.

[0105] The initial uplink BWP may be set by parameters provided in the MIB, parameters provided in SIB1, parameters provided in the SIB, and / or RRC parameters. For example, the initial uplink BWP may be set by the parameter initialUplinkBWP provided in SIB1, where initialUplinkBWP is a parameter that indicates the setting of the initial uplink BWP for a UE-specific (dedicated) UE.

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

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

[0108] 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 6 shows an example of RF retuning. In Figure 6, 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.

[0109] 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 be rephrased as the downlink BWP or downlink sub-BWP. However, "multiple initial downlink BWPs are set" for terminal device 1 may mean that multiple frequency positions and / or multiple bandwidths of the initial downlink BWP are set. Base station device 3 broadcasts information including the setting of multiple frequency positions and / or multiple bandwidths of the initial downlink BWP, and terminal device 1 may determine / identify / set the frequency positions and bandwidths of the initial downlink BWP based on this information.

[0110] A terminal device 1 according to one aspect of the present invention receives / identifies initial downlink BWP configuration information using the upper layer parameter initialDownlinkBWP. However, initialDownlinkBWP may be included in SIB1 or in any RRC message. For example, initial downlink BWP configuration information may include information indicating the frequency position and bandwidth of the initial downlink BWP. Terminal device 1 may receive SIB1 or any RRC message containing multiple configuration information for the initial downlink BWP. Multiple configuration information for the initial downlink BWP may be included in a single parameter initialDownlinkBWP.

[0111] Figure 7 shows an example of the parameter configuration of the information element (IE) BWP-DownlinkCommon of initialDownlinkBWP according to this embodiment. initialDownlinkBWP according to this embodiment may include genericParameters for the initial downlink BWP, cell-specific parameters pdcch-ConfigCommon for the PDCCH, cell-specific parameters pdsch-ConfigCommon for the PDSCH, and / or parameters indicating second configuration information for the initial downlink BWP. However, the parameter indicating second configuration information for the initial downlink BWP may be the parameter locationAndBandwidth-rc within initialDownlinkBWP that indicates the second "frequency location and bandwidth" of the initial downlink BWP. If multiple initial downlink BWPs are configured in a cell (or if multiple frequency position and / or bandwidth configuration information for an initial downlink BWP is broadcast in a cell), some of the information included in genericParameters within initialDownlinkBWP may be parameters common to those multiple initial downlink BWPs (or the multiple frequency position and / or bandwidth configuration information for those initial downlink BWPs).

[0112] The genericParameters included in initialDownlinkBWP consist of information element (IE)BWPs and include the parameter locationAndBandwidth, which indicates the frequency location and bandwidth of the initial downlink BWP; the parameter subcarrierSpacing, which indicates the subcarrier spacing used for all channels and reference signals in the initial downlink BWP; and the parameter cyclicPrefix, which indicates whether an extended cyclic prefix (CP) is used in the initial downlink BWP. However, if multiple "frequency location and bandwidth" values ​​for the initial downlink BWP are set in a given cell, the locationAndBandwidth parameter included in genericParameters within initialDownlinkBWP may be the parameter indicating the first "frequency location and bandwidth" of the initial downlink BWP. However, if multiple "frequency location and bandwidth" settings are configured for an initial downlink BWP in a given cell, the subcarrierSpacing included in genericParameters within initialDownlinkBWP may be a parameter indicating the subcarrier spacing used for all channels and reference signals in the initial downlink BWP configured with the first "frequency location and bandwidth," or it may be a parameter common to initial downlink BWPs configured with different "frequency location and bandwidth" settings, indicating the subcarrier spacing used for all channels and reference signals. For example, terminal device 1 may determine / specify the subcarrier spacing used for all channels (e.g., PDCCH, PDSCH) and reference signals in the initial downlink BWP based on the subcarrierSpacing included in genericParameters within initialDownlinkBWP, regardless of whether initialDownlinkBWP includes the setting information (locationAndBandwidth-rc) for the second "frequency location and bandwidth."However, if multiple "frequency location and bandwidth" settings are configured for an initial downlink BWP in a given cell, the cyclicPrefix included in genericParameters within initialDownlinkBWP may be a parameter indicating whether an extended cyclic prefix (CP) is used in the initial downlink BWP configured for the first "frequency location and bandwidth," or it may be a parameter indicating whether an extended CP is used in common for initial downlink BWPs configured for different "frequency location and bandwidth" settings. For example, terminal device 1 may determine / specify whether an extended CP is used in the initial downlink BWP based on the cyclicPrefix included in genericParameters within initialDownlinkBWP, regardless of whether initialDownlinkBWP includes the configuration information (locationAndBandwidth-rc) for the second "frequency location and bandwidth."

[0113] The value indicated by locationAndBandwidth in genericParameters within initialDownlinkBWP is interpreted as a Resource Indicator Value (RIV). RIV is an index that indicates the starting position of a resource block and the number of consecutive resource blocks, and the frequency position and bandwidth of the initial downlink BWP can be determined by the value of this index. The subcarrier spacing of the initial downlink BWP indicated by subcarrierSpacing in genericParameters within initialDownlinkBWP may be set to the same value as the subcarrier spacing indicated by the MIB of the same cell. If cyclicPrefix is ​​not included (not set) in genericParameters, terminal device 1 may use a standard CP instead of an extended CP.

[0114] However, different parameters indicating different frequency locations and / or bandwidths for the initial downlink BWP (locationAndBandwidth and locationAndBandwidth-rc within initialDownlinkBWP) may also be information that sets up initial downlink BWPs with different frequency locations and / or bandwidths. For example, terminal device 1 that does not support RedCap may identify / determine the frequency location and bandwidth of the initial downlink BWP using locationAndBandwidth in initialDownlinkBWP, while terminal device 1 that supports RedCap may identify / determine the frequency location and bandwidth of the initial downlink BWP using locationAndBandwidth-rc if locationAndBandwidth-rc is included in initialDownlinkBWP, or identify / determine the frequency location and bandwidth of the initial downlink BWP using locationAndBandwidth in initialDownlinkBWP if locationAndBandwidth-rc is not included in initialDownlinkBWP.

[0115] However, in this embodiment, the parameter locationAndBandwidth-rc, which indicates the second "frequency location and bandwidth" of the initial downlink BWP, can be treated as an additional parameter to the generic parameters by configuring it so that it is not included in the genericParameters within initialDownlinkBWP, which is a generic parameter of the initial downlink. Alternatively, locationAndBandwidth-rc may be configured to be included in the genericParameters within initialDownlinkBWP.

[0116] The pdcch-ConfigCommon included in initialDownlinkBWP may include the controlResourceSetZero parameter for CORESET0 used in the common search space or UE-specific search space, the commonControlResourceSet parameter for an additional common CORESET used in the common search space or UE-specific search space, the searchSpaceZero parameter for common search space 0 (common search space #0), the commonSearchSpaceList parameter indicating a list of common search spaces other than common search space 0, the searchSpaceSIB1 parameter indicating the ID of the search space for SIB1 messages, the searchSpaceOtherSystemInformation parameter indicating the ID of the search space for other system information, the pagingSearchSpace parameter indicating the ID of the search space for paging, and / or the ra-SearchSpace parameter indicating the ID of the search space for random access procedures.

[0117] The information element (IE) ControlResourceSetZero is set to a value between 0 and 15. However, the number of values ​​that can be set to ControlResourceSetZero is not limited to 16; for example, it could be 32. The information element SearchSpaceZero is set to a value between 0 and 15. However, the number of values ​​that can be set to SearchSpaceZero is not limited to 16; for example, it could be 32.

[0118] Terminal device 1 determines the number of consecutive resource blocks and consecutive symbols for CORESET0 from controlResourceSetZero in pdcch-ConfigCommon. 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 it to based on the supported UE category and / or UE Capability. However, terminal device 1 may determine the table to apply it to based on the minimum channel bandwidth. However, terminal device 1 may determine the table to apply it to based on the subcarrier interval of the SS / PBCH block and / or the subcarrier interval of CORESET0. Each row of the table to which the value of controlResourceSetZero is applied as an index may indicate the index indicated by controlResourceSetZero, the multiplexing pattern of 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.

[0119] The PBCH and CORESET multiplexing pattern indicates the frequency / time position relationship between the SS / PBCH block corresponding to the PBCH that detected the MIB and the corresponding CORESET0. For example, if the PBCH and CORESET multiplexing pattern is 1, the PBCH and CORESET are time-multiplexed into different symbols.

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

[0121] 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 corresponding SS / PBCH block overlaps.

[0122] Terminal device 1 receives an initialDownlinkBWP containing the RRC parameter pdcch-ConfigCommon in an SIB1 or RRC message, and monitors PDCCH based on this parameter.

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

[0124] 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. In the SS / PBCH block where index i, terminal device 1 determines n0 and the system frame number based on parameters O and M shown in the table.

[0125] If a cell has multiple parameters (locationAndBandwidth and locationAndBandwidth-rc in initialDownlinkBWP) indicating the "frequency location and bandwidth" for an initial downlink BWP (which may also be the case if multiple initial downlink BWPs are set in a cell), then the pdcch-ConfigCommon included in initialDownlinkBWP or each parameter of said pdcch-ConfigCommon may be cell-specific parameters of the PDCCH in the initial downlink BWP set with the first "frequency location and bandwidth", or they may be cell-specific parameters of the PDCCH that are common to initial downlink BWPs set with different "frequency locations and bandwidths". For example, terminal device 1 may determine / identify cell-specific parameters of the PDCCH in the initial downlink BWP based on pdcch-ConfigCommon or some parameters of said pdcch-ConfigCommon included in initialDownlinkBWP, regardless of whether initialDownlinkBWP includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0126] The pdsch-ConfigCommon included in initialDownlinkBWP may contain the parameter pdsch-TimeDomainAllocationList, which indicates a list of time domain settings for the timing of downlink allocation for downlink data.

[0127] If a cell has multiple parameters (locationAndBandwidth and locationAndBandwidth-rc in initialDownlinkBWP) indicating the "frequency location and bandwidth" for an initial downlink BWP (which may also be the case if multiple initial downlink BWPs are set in a cell), then the pdsch-ConfigCommon included in initialDownlinkBWP or each parameter of said pdsch-ConfigCommon may be cell-specific parameters of the PDSCH for the initial downlink BWP set with the first "frequency location and bandwidth", or they may be cell-specific parameters of the PDSCH that are common to initial downlink BWPs set with different "frequency locations and bandwidths". For example, terminal device 1 may determine / identify cell-specific parameters of the PDSCH in the initial downlink BWP based on pdsch-ConfigCommon or some parameters of said pdsch-ConfigCommon included in initialDownlinkBWP, regardless of whether initialDownlinkBWP includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0128] The value indicated by locationAndBandwidth-rc in initialDownlinkBWP is interpreted as a Resource Indicator Value (RIV). The RIV is an index that indicates the starting position of a resource block and the number of consecutive resource blocks. The value of this index allows us to identify the frequency position and bandwidth of the initial downlink BWP.

[0129] If locationAndBandwidth-rc is not included in initialDownlinkBWP, terminal device 1 may determine the frequency location and bandwidth of the initial downlink BWP based on locationAndBandwidth included in genericParameters within initialDownlinkBWP. If locationAndBandwidth-rc is included in initialDownlinkBWP, terminal device 1 may determine the frequency location and bandwidth of the initial downlink BWP based on locationAndBandwidth-rc.

[0130] Terminal device 1, which does not support the frequency location and / or bandwidth of the first initial downlink BWP, can receive the downlink channel and downlink signal transmitted from base station device 3 by identifying / determining the second initial downlink BWP from locationAndBandwidth-rc included in initialDownlinkBWP.

[0131] When the base station device 3 sets the initial downlink BWP for a frequency location and / or bandwidth that a particular terminal device 1 does not support using locationAndBandwidth, it can appropriately transmit downlink channels and downlink signals by setting the initial downlink BWP for a frequency location and / or bandwidth that the terminal device 1 does support using locationAndBandwidth-rc. By including locationAndBandwidth-rc in initialDownlinkBWP, the base station device 3 can transmit the downlink channel and reference signal corresponding to the second initial downlink BWP to terminal devices 1 that do not support the frequency location and / or bandwidth of the first initial downlink BWP, and transmit the downlink channel and reference signal corresponding to the first initial downlink BWP to terminal devices 1 that support the frequency location and bandwidth of the first initial downlink BWP. When the base station device 3 sets the initial downlink BWP for a frequency location and / or bandwidth that all terminal devices 1 support using locationAndBandwidth in initialDownlinkBWP, it is not necessary to include locationAndBandwidth-rc in initialDownlinkBWP.

[0132] Terminal device 1 may use subcarrierSpacing, included in genericParameters within initialDownlinkBWP, to identify / determine the subcarrier spacing used for all channels and reference signals in the initial downlink BWP, regardless of whether locationAndBandwidth-rc is included in initialDownlinkBWP. Terminal device 1 may also use cyclicPrefix, included in genericParameters within initialDownlinkBWP, to identify / determine whether an extended cyclic prefix CP is used in the initial downlink BWP, regardless of whether locationAndBandwidth-rc is included in initialDownlinkBWP.

[0133] Terminal device 1 may use pdcch-ConfigCommon included in initialDownlinkBWP to identify / determine the cell-specific parameters of the PDCCH in the initial downlink BWP, and monitor / receive the PDCCH, regardless of whether locationAndBandwidth-rc is included in initialDownlinkBWP. Terminal device 1 may use pdsch-ConfigCommon included in initialDownlinkBWP to identify / determine the cell-specific parameters of the PDSCH in the initial downlink BWP, and receive the PDSCH, regardless of whether locationAndBandwidth-rc is included in initialDownlinkBWP.

[0134] Figure 8 is a flowchart showing an example of the process for determining the initial downlink BWP and monitoring the PDCCH in the terminal device 1 of this embodiment. In step S1001 of Figure 8, the terminal device 1 receives the initialDownlinkBWP, which is a common parameter (information) for the initial downlink BWP of a certain cell, and includes the parameter (information) genericParameters, which indicates the general parameters of the initial downlink BWP, and the parameter (information) pdcch-ConfigCommon, which indicates the cell common parameters of the physical downlink control channel of the initial downlink BWP. In step S1002, the terminal device 1 determines whether the received initialDownlinkBWP includes the parameter (information) locationAndBandwidth-rc, which indicates the second frequency location and bandwidth of the initial downlink BWP. If the determination is yes (S1002-Yes), in step S1003, the terminal device 1 determines / specifies the frequency location and bandwidth of the initial downlink BWP based on locationAndBandwidth-rc in initialDownlinkBWP. If the determination in step S1002 is negative (S1002-No), in step S1004, terminal device 1 determines / identifies the frequency location and bandwidth of the initial downlink BWP based on the parameter (information) locationAndBandwidth, which is included in genericParameters in initialDownlinkBWP and indicates the first frequency location and bandwidth of the initial downlink BWP. In step S1005, terminal device 1 monitors PDCCH based on pdcch-ConfigCommon, regardless of whether locationAndBandwidth-rc is included in initialDownlinkBWP.

[0135] By sharing and using BWP parameters across multiple initial downlink BWPs in this way, it becomes possible to reduce the overhead of SIB1.

[0136] 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. However, for terminal device 1, "multiple initial uplink BWPs are configured" may mean that multiple frequency positions and / or multiple bandwidths of an initial uplink BWP are configured. The base station device 3 broadcasts information including the settings of multiple frequency positions and / or multiple bandwidths for the initial uplink BWP, and the terminal device 1 may determine / identify / set the frequency position and bandwidth of the initial uplink BWP based on this information.

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

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

[0139] A terminal device 1 according to one aspect of the present invention receives / identifies initial uplink BWP configuration information using the upper layer parameter initialUplinkBWP. However, initialUplinkBWP may be included in SIB1 or in any RRC message. For example, initial uplink BWP configuration information may include information indicating the frequency position and bandwidth of the initial uplink BWP. Terminal device 1 may receive SIB1 or any RRC message containing multiple initial uplink BWP configuration information. Multiple initial uplink BWP configuration information may be included in a single parameter initialUplinkBWP.

[0140] Figure 9 shows an example of the parameter configuration of the information element (IE) BWP-UplinkCommon of initialUplinkBWP according to this embodiment. initialUplinkBWP according to this embodiment may include genericParameters for the initial uplink BWP, cell-specific parameters for random access, push-ConfigCommon for PUSCH, push-ConfigCommon for PUCCH, and / or parameters indicating second configuration information for the initial uplink BWP. However, the parameter indicating second configuration information for the initial uplink BWP may be locationAndBandwidth-rc, which indicates the second "frequency location and bandwidth" of the initial uplink BWP. If multiple initial uplink BWPs are configured in a cell (or if multiple frequency position and / or bandwidth configuration information for an initial uplink BWP is broadcast in a cell), some of the information included in genericParameters may be parameters common to those multiple initial uplink BWPs (or the multiple frequency position and / or bandwidth configuration information for those initial uplink BWPs).

[0141] The genericParameters included in initialUplinkBWP consist of an Information Element (IE)BWP and include the parameter locationAndBandwidth, which indicates the frequency location and bandwidth of the initial uplink BWP; the parameter subcarrierSpacing, which indicates the subcarrier spacing used for all channels and reference signals in the initial uplink BWP; and the parameter cyclicPrefix, which indicates whether an extended cyclic prefix (CP) is used in the initial uplink BWP. However, if multiple "frequency location and bandwidth" values ​​for the initial uplink BWP are set in a given cell, the locationAndBandwidth parameter included in genericParameters may be the parameter indicating the first "frequency location and bandwidth" of the initial uplink BWP. However, if multiple "frequency location and bandwidth" settings are configured for an initial uplink BWP in a given cell, the subcarrierSpacing included in genericParameters may be a parameter indicating the subcarrier spacing used for all channels and reference signals in the initial uplink BWP configured for the first "frequency location and bandwidth," or it may be a parameter indicating the subcarrier spacing used for all channels and reference signals in common to initial uplink BWPs configured for different "frequency location and bandwidth" settings. For example, terminal device 1 may determine / specify the subcarrier spacing used for all channels (e.g., PUCCH, PUSCH, PRACH) and reference signals in the initial uplink BWP based on the subcarrierSpacing included in genericParameters within initialUplinkBWP, regardless of whether initialUplinkBWP includes the setting information (locationAndBandwidth-rc) for the second "frequency location and bandwidth."However, if multiple "frequency location and bandwidth" settings are configured for an initial uplink BWP in a given cell, the cyclicPrefix included in genericParameters within initialUplinkBWP may be a parameter indicating whether an extended cyclic prefix (CP) is used in the initial uplink BWP configured for the first "frequency location and bandwidth," or it may be a parameter indicating whether an extended CP is used in common for initial uplink BWPs configured for different "frequency location and bandwidth" settings. For example, terminal device 1 may determine / specify whether an extended CP is used in the initial uplink BWP based on the cyclicPrefix included in genericParameters within initialUplinkBWP, regardless of whether initialUplinkBWP includes the setting information (locationAndBandwidth-rc) for the second "frequency location and bandwidth."

[0142] The value indicated by locationAndBandwidth in genericParameters within initialUplinkBWP is interpreted as a Resource Indicator Value (RIV). RIV is an index that indicates the starting position of a resource block and the number of consecutive resource blocks, and the frequency position and bandwidth of the initial uplink BWP can be determined by the value of this index. The subcarrier spacing of the initial uplink BWP indicated by subcarrierSpacing in genericParameters within initialUplinkBWP may be set to the same value as the subcarrier spacing indicated by the MIB of the same cell. If cyclicPrefix is ​​not included (not set) in genericParameters within initialUplinkBWP, terminal device 1 may use a standard CP instead of an extended CP.

[0143] However, different parameters indicating different frequency locations and bandwidths for the initial uplink BWP (locationAndBandwidth and locationAndBandwidth-rc within initialUplinkBWP) may also be information for setting initial uplink BWPs with different frequency locations and / or bandwidths. For example, the initial uplink BWP set by locationAndBandwidth may be the initial uplink BWP used by terminal device 1 that does not support RedCap, and the initial uplink BWP set by locationAndBandwidth-rc may be the initial uplink BWP used by terminal device 1 that supports RedCap. However, different parameters indicating different frequency locations and bandwidths for the initial uplink BWP (locationAndBandwidth and locationAndBandwidth-rc within initialUplinkBWP) may also be information for setting different frequency locations and bandwidths for the initial uplink BWP. For example, terminal device 1 that does not support RedCap may identify / determine the frequency location and bandwidth of the initial uplink BWP using locationAndBandwidth in initialUplinkBWP, while terminal device 1 that supports RedCap may identify / determine the frequency location and bandwidth of the initial uplink BWP using locationAndBandwidth-rc if locationAndBandwidth-rc is included in initialUplinkBWP, or identify / determine the frequency location and bandwidth of the initial uplink BWP using locationAndBandwidth in initialUplinkBWP if locationAndBandwidth-rc is not included in initialUplinkBWP.

[0144] However, in this embodiment, the parameter locationAndBandwidth-rc in initialUplinkBWP, which indicates the second "frequency location and bandwidth" of the initial uplink BWP, can be treated as an additional parameter to the generic parameters by not including it in genericParameters, which are the general parameters of the initial uplink. Alternatively, locationAndBandwidth-rc may be included in genericParameters within initialUplinkBWP.

[0145] The pucch-ConfigCommon included in initialUplinkBWP may include the parameter pucch-ResourceCommon, which indicates an index for configuring a cell-specific set of PUCCH resources / parameters; the parameter pucch-GroupHopping, which indicates the configuration of group hopping and sequence hopping in PUCCH formats 0, 1, 3, and 4; the parameter hoppingId, which indicates a cell-specific scrambling ID in group hopping and sequence hopping; and / or the parameter p0-nominal, which indicates a power control parameter (P0) for PUCCH transmission.

[0146] If a cell has multiple parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating "frequency location and bandwidth" for an initial uplink BWP (or if a cell has multiple initial uplink BWPs), then the pucch-ConfigCommon included in initialUplinkBWP, or each parameter of said pucch-ConfigCommon, may be a cell-specific parameter of the PDCCH in the initial uplink BWP set with the first "frequency location and bandwidth," or it may be a cell-specific parameter of the PUCCH common to initial uplink BWPs set with different "frequency location and bandwidth." For example, terminal device 1 may determine / identify cell-specific parameters of PUCCH in the initial uplink BWP based on pucch-ConfigCommon or some parameters of said pucch-ConfigCommon included in initialUplinkBWP, regardless of whether initialUplinkBWP includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0147] The push-ConfigCommon included in initialUplinkBWP may include the parameter push-TimeDomainAllocationList, which indicates a list of time domain settings for the timing of uplink allocation for uplink data; the cell-specific parameter groupHoppingEnabledTransformPrecoding, which indicates whether DMRS group hopping is enabled; the parameter msg3-DeltaPreamble, which indicates the power offset between msg3 and RACH preamble transmission; and / or the parameter p0-NominalWithGrant, which indicates the value of the target received power P0 for PUSCH with grant.

[0148] If a cell has multiple parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating "frequency location and bandwidth" for an initial uplink BWP (or if a cell has multiple initial uplink BWPs), then the push-ConfigCommon included in initialUplinkBWP, or each parameter of said push-ConfigCommon, may be a cell-specific parameter of PUSCH for the initial uplink BWP set with the first "frequency location and bandwidth", or it may be a cell-specific parameter of PUSCH common to initial uplink BWPs set with different "frequency location and bandwidth". For example, terminal device 1 may determine / identify cell-specific parameters of PUSCH in the initial uplink BWP based on push-ConfigCommon or some parameters of said push-ConfigCommon included in initialUplinkBWP, regardless of whether initialUplinkBWP includes second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0149] The value indicated by locationAndBandwidth-rc in initialUplinkBWP is interpreted as a Resource Indicator Value (RIV). The RIV is an index that indicates the starting position of a resource block and the number of consecutive resource blocks. The value of this index allows us to identify the frequency position and bandwidth of the initial uplink BWP.

[0150] If locationAndBandwidth-rc is not included in initialUplinkBWP, terminal device 1 may determine / determine the frequency location and bandwidth of the initial uplink BWP based on locationAndBandwidth included in genericParameters within initialUplinkBWP. If locationAndBandwidth-rc is included in initialUplinkBWP, terminal device 1 may determine / determine the frequency location and bandwidth of the initial uplink BWP based on locationAndBandwidth-rc.

[0151] Terminal device 1, which does not support the frequency location and / or bandwidth of the first initial uplink BWP, can receive the uplink channel and uplink signals transmitted from base station device 3 by identifying / determining the second initial uplink BWP from locationAndBandwidth-rc included in initialUplinkBWP.

[0152] When the base station device 3 sets an initial uplink BWP with a frequency location and / or bandwidth that a particular terminal device 1 does not support using locationAndBandwidth, it can appropriately transmit the uplink channel and uplink signal by setting an initial uplink BWP with a frequency location and / or bandwidth that the terminal device 1 does support using locationAndBandwidth-rc in initialUplinkBWP. By including locationAndBandwidth-rc in initialUplinkBWP, the base station device 3 can transmit the uplink channel and reference signal corresponding to the second initial uplink BWP to terminal devices 1 that do not support the frequency location and / or bandwidth of the first initial uplink BWP, and transmit the uplink channel and reference signal corresponding to the first initial uplink BWP to terminal devices 1 that support the frequency location and bandwidth of the first initial uplink BWP. If base station device 3 sets the initial uplink BWP for the frequency location and / or bandwidth supported by all terminal devices 1 using locationAndBandwidth in initialUplinkBWP, it does not need to include locationAndBandwidth-rc in initialUplinkBWP.

[0153] Terminal device 1 may use subcarrierSpacing, included in genericParameters within initialUplinkBWP, to identify / determine the subcarrier spacing used for all channels and reference signals in the initial uplink BWP, regardless of whether locationAndBandwidth-rc is included in initialUplinkBWP. Terminal device 1 may also use cyclicPrefix, included in genericParameters within initialUplinkBWP, to identify / determine whether an extended cyclic prefix CP is used in the initial uplink BWP, regardless of whether locationAndBandwidth-rc is included in initialUplinkBWP.

[0154] Terminal device 1 may use push-ConfigCommon included in initialUplinkBWP to identify / determine the cell-specific parameters of PUCCH in the initial uplink BWP, regardless of whether locationAndBandwidth-rc is included in initialUplinkBWP, and then transmit PUCCH. Terminal device 1 may use push-ConfigCommon included in initialUplinkBWP to identify / determine the cell-specific parameters of PUSCH in the initial uplink BWP, regardless of whether locationAndBandwidth-rc is included in initialUplinkBWP, and then transmit PUSCH.

[0155] Figure 10 is a flowchart showing an example of the process for determining the initial uplink BWP and transmitting a PUSCH in the terminal device 1 of this embodiment. In step S2001 of Figure 10, the terminal device 1 receives the initialUplinkBWP common parameter (information) initialUplinkBWP for a certain cell, which includes the parameter (information) genericParameters indicating the general parameters of the initial uplink BWP and the parameter (information) push-ConfigCommon indicating the cell common parameters of the physical uplink shared channel of the initial uplink BWP. In step S2002, the terminal device 1 determines whether the received initialUplinkBWP includes the parameter (information) locationAndBandwidth-rc indicating the second frequency location and bandwidth of the initial uplink BWP. If the determination is positive (S2002-Yes), in step S2003, the terminal device 1 determines / specifies the frequency location and bandwidth of the initial uplink BWP based on locationAndBandwidth-rc in initialUplinkBWP. If the determination in step S2002 is negative (S2002-No), in step S2004, terminal device 1 determines / identifies the frequency location and bandwidth of the initial uplink BWP based on the parameter (information) locationAndBandwidth, which is included in genericParameters in initialUplinkBWP and indicates the first frequency location and bandwidth of the initial uplink BWP. In step S2005, terminal device 1 sends a PUSCH based on push-ConfigCommon, regardless of whether locationAndBandwidth-rc is included in initialUplinkBWP.

[0156] By sharing and using BWP parameters across multiple initial uplink BWPs in this way, it becomes possible to reduce the overhead of SIB1 or RRC messages.

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

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

[0159] Figure 11 shows an example of downlink transmission using multiple initial downlink sub-BWPs according to this embodiment. Figure 11 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 11, terminal device 1 repeatedly transmits one downlink signal while frequency hopping using initial downlink sub-BWP#0 and initial downlink sub-BWP#2.

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

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

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

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

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

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

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

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

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

[0169] Figure 12 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.

[0170] The upper layer processing unit 14 outputs the uplink data (which may also 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 / specify the initial downlink BWP settings (e.g., frequency position and bandwidth) based on the information in the system information block (SIB1 / SIB) and / or RRC messages. The upper layer processing unit 14 may also have a function to determine / specify the initial uplink BWP settings (e.g., frequency position and bandwidth) based on the information in the system information block (SIB1 / SIB) and / or RRC messages.

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

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

[0173] 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 monitor PDCCH. The wireless transceiver 10 may have a function to receive DCI on the PDCCH. The wireless transceiver 10 may have a function to output the DCI received on the PDCCH to the upper layer processing unit 14. The wireless transceiver 10 may have a function to receive DMRS for SSB, PSS, SSS, PBCH and / or PBCH. The wireless transceiver 10 may have a function to receive SS / PBCH blocks. The wireless transceiver 10 may have a function to receive system information blocks (SIB1 and / or SIB) corresponding to a predetermined cell. The wireless transceiver 10 may have a function to receive information including information that determines / specifies the initial downlink BWP settings (e.g., frequency position and bandwidth). The wireless transceiver 10 may have a function to receive information including information that determines / specifies the initial uplink BWP settings (e.g., frequency position and bandwidth).

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

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

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

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

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

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

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

[0181] Figure 13 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.

[0182] 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 a 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 a system information block (SIB1 / SIB) and / or an RRC message containing information for the terminal device 1 to identify the initial downlink BWP. The upper layer processing unit 34 may also have a function to generate a system information block (SIB1 / SIB) and / or an RRC message containing information for the terminal device 1 to identify the initial uplink BWP.

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

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

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

[0186] 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, and / or DMRS for PBCH. The wireless transceiver 30 may have a function to transmit SS / 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 the function of transmitting a system information block (SIB1 / SIB) to the terminal device 1. Furthermore, some functions of the wireless transceiver 30 are the same as those of the wireless transceiver 10 and are therefore omitted from the explanation. 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.

[0187] 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 13, 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.

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

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

[0190] (1) The terminal device 1 in the first aspect of the present invention comprises a receiving unit 10 that receives first information (initialDownlinkBWP), and a monitoring unit 10 that monitors the physical downlink control channel (PDCCH) in the initial downlink BWP, wherein the first information indicates common parameters of the initial downlink BWP of a cell, and includes second information (genericParameters) that indicates general-purpose parameters of the initial downlink BWP, and third information (pdcch-ConfigCommon) that indicates cell common parameters of the physical downlink control channel of the initial downlink BWP, and the second information includes fourth information (location) that indicates the first frequency position and bandwidth of the initial downlink BWP The first information includes locationAndBandwidth-rc and a fifth piece of information (subcarrierSpacing) indicating the subcarrier spacing of the channel used in the initial downlink BWP. If the first information includes locationAndBandwidth-rc indicating the second frequency location and bandwidth of the initial downlink BWP, the frequency location and bandwidth of the initial downlink BWP are indicated by the sixth piece of information. If the first information does not include the sixth piece of information, the frequency location and bandwidth of the initial downlink BWP are indicated by the fourth piece of information. The monitor unit 10 monitors the physical downlink control channel based on the third piece of information, regardless of whether the first information includes the sixth piece of information or not.

[0191] (2) In a first embodiment of the present invention, the physical downlink control channel may be monitored based on the fifth information, regardless of whether the first information includes the sixth information or not.

[0192] (3) In the first embodiment of the present invention, the sixth information may be information that is not included in the second information.

[0193] (4) In a first embodiment of the present invention, the third information may include information that identifies a search space for monitoring the physical downlink control channel and information that identifies a set of control resources for monitoring the physical downlink control channel.

[0194] (5) The base station device 3 in the second aspect of the present invention comprises a broadcasting unit 30 that broadcasts first information (initialDownlinkBWP), and a transmitting unit 30 that transmits a first physical downlink control channel (PDCCH) to a first terminal device and a second physical downlink control channel to a second terminal device, wherein the first information indicates common parameters of the initial downlink BWP of a cell, and includes second information (genericParameters) that indicates general-purpose parameters of the initial downlink BWP, and third information (pdcch-ConfigCommon) that indicates cell common parameters of the physical downlink control channel of the initial downlink BWP, wherein the second information indicates the first frequency position and bandwidth of the initial downlink BWP and The first information includes a fourth piece of information (locationAndBandwidth) indicating the location and a fifth piece of information (subcarrierSpacing) indicating the subcarrier spacing of the channel used in the initial downlink BWP, the first information includes a sixth piece of information (locationAndBandwidth-rc) indicating the second frequency location and bandwidth of the initial downlink BWP, the frequency location and bandwidth of the initial downlink BWP for the first terminal device is indicated by the sixth piece of information, and the frequency location and bandwidth of the initial downlink BWP for the second terminal device is indicated by the fourth piece of information, and the transmitting unit 30 transmits the first physical downlink control channel and the second physical downlink control channel based on the third piece of information.

[0195] (6) In a second embodiment of the present invention, the physical downlink control channel may be transmitted based on the fifth information, regardless of whether the first information includes the sixth information or not.

[0196] (7) In a second embodiment of the present invention, the sixth information may be information not included in the second information.

[0197] (8) In a second embodiment of the present invention, the third information may include information that identifies a search space in which the first terminal device and the second terminal device monitor the physical downlink control channel, and information that identifies a set of control resources in which the first terminal device and the second terminal device monitor the physical downlink control channel.

[0198] (9) The terminal device 1 in the third aspect of the present invention comprises a receiving unit 10 that receives first information (initialUplinkBWP), and a transmitting unit 10 that transmits a physical uplink shared channel (PUSCH) on the initial uplink BWP, wherein the first information indicates common parameters of the initial uplink BWP of a certain cell, and includes second information (genericParameters) indicating general-purpose parameters of the initial uplink BWP, and third information (pusch-ConfigCommon) indicating cell common parameters of the physical uplink shared channel of the initial uplink BWP, and the second information includes fourth information (locationA) indicating the first frequency position and bandwidth of the initial uplink BWP. The first information includes locationAndBandwidth-rc, which indicates the second frequency location and bandwidth of the initial uplink BWP. If the first information includes locationAndBandwidth-rc, which indicates the second frequency location and bandwidth of the initial uplink BWP, then the frequency location and bandwidth of the initial uplink BWP are indicated by the sixth information. If the first information does not include the sixth information, then the frequency location and bandwidth of the initial uplink BWP are indicated by the fourth information. The transmitting unit 10 transmits the physical uplink shared channel based on the third information, regardless of whether the first information includes the sixth information or not.

[0199] (10) In a third embodiment of the present invention, the physical uplink shared channel may be transmitted based on the fifth information, regardless of whether the first information includes the sixth information or not.

[0200] (11) In a third embodiment of the present invention, the sixth information may be information not included in the second information.

[0201] (12) In a third aspect of the present invention, the third information may include information that identifies a list of time domain allocations for the timing of transmitting the physical uplink shared channel.

[0202] (13) A base station device 3 in a fourth aspect of the present invention comprises a broadcasting unit 30 that broadcasts first information (initialUplinkBWP), and a receiving unit 30 that receives a first physical uplink shared channel (PUSCH) from a first terminal device and a second physical uplink shared channel from a second terminal device, wherein the first information includes common parameters of the initial uplink BWP of a cell, second information (genericParameters) that indicates general-purpose parameters of the initial uplink BWP, and third information (pusch-ConfigCommon) that indicates cell common parameters of the physical uplink shared channel of the initial uplink BWP, wherein the second information includes a first frequency position and bandwidth of the initial uplink BWP and The first information includes a fourth piece of information (locationAndBandwidth) indicating the location and a fifth piece of information (subcarrierSpacing) indicating the subcarrier spacing of the channel used in the initial uplink BWP, the first information includes a sixth piece of information (locationAndBandwidth-rc) indicating the second frequency location and bandwidth of the initial uplink BWP, the frequency location and bandwidth of the initial uplink BWP for the first terminal device is indicated by the sixth piece of information, and the frequency location and bandwidth of the initial uplink BWP for the second terminal device is indicated by the fourth piece of information, and the transmitting unit 30 transmits the first physical uplink shared channel and the second physical uplink shared channel based on the third information.

[0203] (14) In a fourth embodiment of the present invention, the physical uplink shared channel may be transmitted based on the fifth information, regardless of whether the first information includes the sixth information or not.

[0204] (15) In a fourth embodiment of the present invention, the sixth information may be information not included in the second information.

[0205] (16) In a fourth aspect of the present invention, the third information may include information that identifies a list of time domain allocations for the timing of transmitting the physical uplink shared channel.

[0206] This allows terminal device 1 and base station device 3 to communicate efficiently.

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

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

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

[0210] 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).

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

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

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

[0214] 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 the first information, A transmitting unit that transmits on the physical uplink shared channel using the initial uplink BWP, Equipped with, The first information includes common parameters of the initial uplink BWP of a cell, second information including general parameters of the initial uplink BWP, and third information including cell common parameters of the physical uplink shared channel of the initial uplink BWP. The second information includes a fourth piece of information indicating the first frequency position and bandwidth of the initial uplink BWP, and a fifth piece of information indicating the subcarrier spacing of the channels used in the initial uplink BWP. If the first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, the transmitting unit uses the sixth piece of information to transmit the physical uplink shared channel based on the third piece of information within the initial uplink BWP where the frequency position and bandwidth are determined. If the first information does not include the sixth information, the transmitting unit transmits the physical uplink shared channel based on the third information within the initial uplink BWP where the frequency position and bandwidth are determined using the fourth information. Terminal device.

2. Regardless of whether the first information includes the sixth information or not, the physical uplink shared channel is transmitted based on the fifth information. The terminal device according to claim 1.

3. The sixth piece of information is not included in the second piece of information. The terminal device according to claim 1.

4. The third piece of information includes information that identifies a list of time domain allocations for the timing of transmitting the physical uplink shared channel, The terminal device according to claim 1.

5. Base station equipment, The first information is disseminated by the information dissemination department, A receiving unit that receives a first physical uplink shared channel from a first terminal device and a second physical uplink shared channel from a second terminal device, Equipped with, The first information includes common parameters of the initial uplink BWP of a cell, second information including general parameters of the initial uplink BWP, and third information including cell common parameters of the physical uplink shared channel of the initial uplink BWP. The second information includes a fourth piece of information indicating the first frequency position and bandwidth of the initial uplink BWP, and a fifth piece of information indicating the subcarrier spacing of the channels used in the initial uplink BWP. The first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, The frequency position and bandwidth of the initial uplink BWP for the first terminal device are shown in the sixth piece of information. The frequency position and bandwidth of the initial uplink BWP for the second terminal device are shown in the fourth piece of information. The receiving unit receives the first physical uplink shared channel and the second physical uplink shared channel based on the third information. Base station equipment.

6. Regardless of whether the first information includes the sixth information or not, the physical uplink shared channel is received based on the fifth information. The base station device according to claim 5.

7. The sixth piece of information is not included in the second piece of information. The base station device according to claim 5.

8. The third information includes information that identifies a list of time domain allocations for the timing of receiving the physical uplink shared channel, The base station device according to claim 5.

9. A communication method for base station equipment, The first piece of information was reported, The first terminal device receives the first physical uplink shared channel, and the second terminal device receives the second physical uplink shared channel. The first information includes common parameters of the initial uplink BWP of a cell, second information including general parameters of the initial uplink BWP, and third information including cell common parameters of the physical uplink shared channel of the initial uplink BWP. The second information includes a fourth piece of information indicating the first frequency position and bandwidth of the initial uplink BWP, and a fifth piece of information indicating the subcarrier spacing of the channels used in the initial uplink BWP. The first information includes a sixth piece of information indicating the second frequency position and bandwidth of the initial uplink BWP, The frequency position and bandwidth of the initial uplink BWP for the first terminal device are shown in the sixth piece of information. The frequency position and bandwidth of the initial uplink BWP for the second terminal device are shown in the fourth piece of information. Based on the third information, the first physical uplink shared channel and the second physical uplink shared channel are received. Communication method.

Images