Terminal device, base station device, and communication method

Abstract

This terminal device: receives an SIB1 including first offset information; identifies a frequency resource of one or more PRACH transmission opportunity on the basis of the SIB1; uses one of the one or more PRACH transmission opportunities to transmit a random access preamble; if the SIB1 does not include second offset information, identifies a frequency resource of the one or more PRACH transmission opportunities on the basis of the first offset information; and if the SIB1 does include second offset information, identifies a frequency resource of the one or more PRACH transmission opportunities on the basis of the second offset information.

Description

Terminal device, base station device, and communication method

[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-128921, filed on August 5, 2021, the contents of which are incorporated herein by reference.

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

[0003] The fifth-generation cellular system requires three expected service scenarios: eMBB (enhanced Mobile BroadBand) that realizes high-speed and large-capacity transmission, URLLC (Ultra-Reliable and Low Latency Communication) that realizes low-latency and highly reliable communication, and mMTC (massive Machine Type Communication) that connects a large number of machine-type devices such as IoT (Internet of Things). Furthermore, in Release 17, a future release of NR, studies are being conducted on reduced capability (REDCAP) NR devices that do not require the high requirements of eMBB and URLLC but aim to reduce costs and extend battery life, for applications such as sensor networks, surveillance cameras, and / or wearable devices (Non-Patent Document 2).

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

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

[0006] (1) To achieve the above object, an embodiment of the present invention provides the following: That is, a terminal device according to one embodiment of the present invention includes: a receiving unit that receives system information block 1 (SIB1) including first offset information, a control unit that identifies frequency resources of one or more physical random access channel (PRACH) transmission opportunities based on the SIB1, and a transmitting unit that transmits a random access preamble using one of the one or more PRACH transmission opportunities, wherein the control unit identifies the frequency resources of the one or more PRACH transmission opportunities based on the first offset information when second offset information is not included in the SIB1, and identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information when the SIB1 includes second offset information.

[0007] (2) In addition, a base station device in one embodiment of the present invention includes a transmitter that transmits system information block 1 (SIB1) including first offset information to a terminal device, a control unit that identifies frequency resources of one or more physical random access channel (PRACH) transmission opportunities based on the SIB1, and a receiver that receives a random access preamble transmitted by the terminal device using one of the one or more PRACH transmission opportunities, wherein the control unit identifies the frequency resources of the one or more PRACH transmission opportunities based on the first offset information when the SIB1 does not include second offset information, and identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information when the SIB1 includes second offset information.

[0008] (3) Also, a communication method according to one aspect of the present invention is a communication method for a terminal device, which receives a system information block 1 (SIB1) including first offset information, identifies frequency resources of one or more physical random access channel (PRACH) transmission opportunities based on the SIB1, transmits a random access preamble using one of the one or more PRACH transmission opportunities, and, if the SIB1 does not include second offset information, identifies frequency resources of the one or more PRACH transmission opportunities based on the first offset information, and, if the SIB1 includes second offset information, identifies frequency resources of the one or more PRACH transmission opportunities based on the second offset information.

[0009] According to one aspect of the present invention, a terminal device and a base station device can communicate efficiently.

[0010] 1 is a diagram illustrating the concept of a wireless communication system according to an embodiment of the present invention. FIG. 1 is a diagram illustrating an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. FIG. 2 is a diagram illustrating a relationship in the time domain between subframes, slots, and minislots according to an embodiment of the present invention. FIG. 3 is a diagram illustrating an example of an SS / PBCH block and an SS burst set according to an embodiment of the present invention. FIG. 4 is a diagram illustrating resources in which PSS, SSS, PBCH, and DMRS for PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. FIG. 5 is a diagram illustrating an example of RF retuning according to an embodiment of the present invention. FIG. 6 is a diagram illustrating an example of a parameter configuration of an information element (IE) BWP-DownlinkCommon of an initialDownlinkBWP according to an embodiment of the present invention. FIG. 7 is a flow diagram illustrating an example of a process related to determining / specifying an initial downlink BWP in a terminal device 1 according to an embodiment of the present invention. FIG. 8 is a diagram illustrating an example of a parameter configuration of an information element (IE) BWP-UplinkCommon of an initialUplinkBWP according to an embodiment of the present invention. FIG. 9 is a diagram illustrating an example of a parameter configuration of an information element (IE) BWP-UplinkCommon of a parameter rach-ConfigGeneric included in the parameter configuration RACH-ConfigCommon of an information element (IE) RACH-ConfigCommon of an embodiment of the present invention. Fig. 1 is a diagram showing the concept of frequency locations of one or more PRACH transmission opportunities indicated by msg1-FrequencyStart and msg1-FrequencyStart-rc according to an embodiment of the present invention. Fig. 2 is a flow diagram showing an example of processing related to identification / determination of frequency locations of one or more PRACH transmission opportunities in a terminal device 1 according to an embodiment of the present invention. Fig. 3 is a schematic block diagram showing the configuration of a terminal device 1 according to an embodiment of the present invention. Fig. 4 is a schematic block diagram showing the configuration of a base station device 3 according to an embodiment of the present invention.

[0011] Hereinafter, an embodiment of the present invention will be described.

[0012] 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 terminal devices 1.

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

[0014] In this embodiment, the wireless communication link from the base station device 3 to the terminal device 1 is called a downlink. In this embodiment, the wireless communication link from the terminal device 1 to the base station device 3 is called an uplink.

[0015] In FIG. 1, wireless communication between the terminal device 1 and the 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 other transmission methods.

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

[0017] 1, the above-described transmission method may be used in which a CP is not used or zero padding is used instead of a CP in wireless communication between the terminal device 1 and the base station device 3. Furthermore, a CP or zero padding may be added to both the front and rear ends.

[0018] An aspect of this embodiment may be operated in carrier aggregation or dual connectivity with a radio access technology (RAT) 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., a primary cell (PCell), a secondary cell (SCell), a primary secondary cell (PSCell), a master cell group (MCG), a secondary cell group (SCG), etc.). Also, an aspect of this embodiment may be used in standalone operation. In dual connectivity operation, a special cell (SpCell) is referred to as a PCell of an MCG or a PSCell of an SCG depending on whether the medium access control (MAC) entity is associated with an MCG or an SCG, respectively. When not operating in dual connectivity, the special cell (SpCell) is referred to as a PCell. The special cell (SpCell) supports PUCCH transmission and contention-based random access.

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

[0020] The wireless communication system of this embodiment may employ TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex). The TDD (Time Division Duplex) method or the FDD (Frequency Division Duplex) method may be applied to all of a plurality of cells. Furthermore, cells employing the TDD method and cells employing the FDD method may be aggregated. The TDD method may be referred to as unpaired spectrum operation. The FDD method may be referred to as paired spectrum operation.

[0021] In the following, a subframe will be described. In this embodiment, the subframe will be referred to as a subframe, but the subframe according to this embodiment may also be referred to as a resource unit, a radio frame, a time period, a time interval, etc.

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

[0023] The signals or physical channels transmitted in each slot may be represented by a resource grid. The resource grid is defined by a number of subcarriers and a number of OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers constituting one slot depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is called a resource element. A resource element may be identified by a subcarrier number and an OFDM symbol number.

[0024] A resource grid is used to represent the mapping of resource elements of a physical downlink channel (e.g., PDSCH) or uplink channel (e.g., PUSCH). For example, when the subcarrier spacing is 15 kHz and the number of OFDM symbols included in a subframe is 14, in the case of NCP, one physical resource block (PRB) is defined as 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, the resource grid consists of (14*12*Nmax,μ) resource elements. In the case of ECP (Extended CP), only a subcarrier spacing of 60 kHz is supported. Therefore, one physical resource block is defined as, for example, 12 (the number of OFDM symbols included in one slot) * 4 (the number of slots included in one subframe) = 48 consecutive OFDM symbols in the time domain and 12*Nmax,μ consecutive subcarriers in the frequency domain. That is, the resource grid consists of (48*12*Nmax,μ) resource elements.

[0025] 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. The reference resource block is common to all subcarriers and may be numbered in ascending order, for example, at a subcarrier spacing of 15 kHz. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or simply referred to as the "reference point"). Common resource blocks are resource blocks numbered in ascending order from 0 at each subcarrier spacing setting μ 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 within a bandwidth part (BWP), and physical resource blocks are resource blocks numbered in ascending order from 0 within the BWP. A physical uplink channel is first mapped to virtual resource blocks. Then, the virtual resource blocks are mapped to physical resource blocks. Hereinafter, a resource block may be a virtual resource block, a physical resource block, a common resource block, or a reference resource block.

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

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

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

[0029] Next, we will explain subframes, slots, and minislots. Figure 3 shows an example of the relationship between subframes, slots, and minislots in the time domain. As shown in the figure, three types of time units are defined. A subframe is 1 ms regardless of the subcarrier spacing, and the number of OFDM symbols included in a slot is 7 or 14 (however, if the cyclic prefix (CP) added to each symbol is Extended CP, it may be 6 or 12), and the slot length varies depending on the subcarrier spacing. Here, if the subcarrier spacing 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.

[0030] A minislot (which may also be called a subslot) is a time unit consisting of fewer OFDM symbols than the number of OFDM symbols included in one slot. The figure shows an example in which a minislot consists of two OFDM symbols. The OFDM symbols within a minislot may coincide with the OFDM symbol timing that constitutes the slot. The smallest unit of scheduling may be a slot or a minislot. Allocating a minislot may also be referred to as non-slot-based scheduling. Scheduling a minislot may also be expressed as scheduling a resource in which the relative time positions of the start positions of the reference signal and data are fixed. Downlink minislots may be referred to as PDSCH mapping type B. Uplink minislots may be referred to as PUSCH mapping type B.

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

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

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

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

[0035] ・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)

[0036] The PBCH is used to broadcast an important information block (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) including important system information required by the terminal device 1. The MIB may include information for identifying the number (SFN: System Frame Number) of the radio frame (also referred to as the system frame) to which the PBCH is mapped, information for identifying the subcarrier spacing of the system information block type 1 (SIB1: System Information Block 1), information indicating the frequency domain offset between the resource block grid and the SS / PBCH block (also referred to as the synchronization signal block, SS block, or SSB), and information indicating the PDCCH configuration for SIB1. However, SIB1 includes information required to evaluate whether the terminal device 1 is allowed to connect to a cell and includes information for determining the scheduling of other system information (SIB: System Information Block). Here, the information indicating the PDCCH configuration for SIB1 may be information determining a control resource set (CORESET) 0 (CORESET0 is also referred to as CORESET#0 or common CORESET), a common search space, and / or required PDCCH parameters. Here, CORESET indicates resource elements of the PDCCH and is composed of a set of PRBs in a time period of a certain number of OFDM symbols (e.g., 1 to 3 symbols). CORESET0 may be a CORESET for the PDCCH that schedules at least SIB1. CORESET0 may be configured in the MIB or via RRC signaling. SIB1 may be scheduled by the PDCCH transmitted in CORESET0. The terminal device 1 receives SIB1 scheduled by the PDCCH received in CORESET0.

[0037] The PBCH may also be used to broadcast information for identifying the number (SFN: System Frame Number) of the radio frame (also referred to as a system frame) to which the PBCH is mapped and / or information for identifying a half radio frame (HRF: Half Frame) (also referred to as a half frame). Note that a half radio frame is a time frame with a length of 5 ms, and the information for identifying a half radio frame may be information for identifying whether it is the first 5 ms or the last 5 ms of a 10 ms radio frame.

[0038] The PBCH may also be used to broadcast a time index within a period of the SS / PBCH block. Here, the time index is information indicating the index of a synchronization signal and a PBCH within a cell. The time index may also be referred to as an SSB index or an SS / PBCH block index. For example, when SS / PBCH blocks are transmitted using a quasi-co-location (QCL) assumption for multiple transmit beams, transmit filter settings, and / or receive spatial parameters, the time index may indicate a time order within a predetermined period or a set period. Furthermore, the terminal device 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.

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

[0040] For example, the following DCI formats may be defined: DCI format 0_0, DCI format 0_1, DCI format 0_2, DCI format 1_0, DCI format 1_1, DCI format 1_2, DCI format 2_0, DCI format 2_1, DCI format 2_2, DCI format 2_3

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

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

[0043] DCI format 0_2 may be used for scheduling the 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, a CSI request, an SRS request, and / or information regarding an antenna port. DCI format 0_2 may include a CRC scrambled by any of the RNTIs, 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 also be referred to as DCI format 0_1A, etc.

[0044] DCI format 1_0 may be used for scheduling a PDSCH in a serving cell. DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation). DCI format 1_0 may be added with a CRC scrambled by any of the following identifiers: C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random access (RA)-RNTI, and / or TC-RNTI. DCI format 1_0 may be monitored in a common search space or a UE-specific search space.

[0045] 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 a BWP, a Transmission Configuration Indication (TCI), and / or information related to an antenna port. DCI format 1_1 may be added with a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_1 may be monitored in a UE-specific search space.

[0046] DCI format 1_2 may be used for scheduling a 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 a BWP, a TCI, and / or information related to an antenna port. DCI format 1_2 may include a CRC scrambled by any one of C-RNTI, CS-RNTI, and / or MCS-C-RNTI among RNTIs. DCI format 1_2 may be monitored in a UE-specific search space. DCI format 1_2 may be referred to as DCI format 1_1A, etc.

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

[0048] DCI format 2_1 is used to notify the terminal device 1 of physical resource blocks (PRBs or RBs) and OFDM symbols for which no transmission may be assumed. This information may be referred to as a preemption instruction (discontinuous transmission instruction).

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

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

[0051] DCI for downlink is also referred to as a downlink grant or a downlink assignment. Here, DCI for uplink is also referred to as an uplink grant or an uplink assignment. DCI may also be referred to as a DCI format.

[0052] The CRC parity bits added to the DCI format transmitted on one PDCCH are scrambled with the SI-RNTI, P-RNTI, C-RNTI, CS-RNTI, RA-RNTI, or TC-RNTI. The SI-RNTI may be an identifier used for broadcasting system information. The P-RNTI may be an identifier used for paging and notifying of system information changes. The C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying a terminal device within a cell. The TC-RNTI is an identifier for identifying a terminal device 1 that transmitted a random access preamble during a contention-based random access procedure.

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

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

[0055] The PUCCH is used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Here, the uplink control information may include channel state information (CSI) used to indicate the state of the downlink channel. The uplink control information may also include a scheduling request (SR) used to request UL-SCH resources. The uplink control information may also include a hybrid automatic repeat request ACKnowledgement (HARQ-ACK). The HARQ-ACK may indicate a HARQ-ACK for downlink data (transport block, medium access control protocol data unit (MAC PDU), downlink-shared channel (DL-SCH)).

[0056] The PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the Medium Access Control (MAC) layer, and is also used to transmit system information (SI) and random access responses (RAR) in the downlink.

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

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

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

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

[0061] The synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). The PSS and SSS may be used to detect the cell ID.

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

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

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

[0065] The DMRS is used to demodulate modulated signals. Two types of DMRS may be defined: a reference signal for demodulating the PBCH and a reference signal for demodulating the PDSCH. Both may be referred to as DMRS. The CSI-RS is used for measuring channel state information (CSI) and beam management, and applies periodic, semi-persistent, or aperiodic CSI reference signal transmission methods. The CSI-RS may be defined as a non-zero power (NZP) CSI-RS and a zero power (ZP) CSI-RS with zero transmission power (or zero reception power). Here, the ZP CSI-RS may be defined as a CSI-RS resource with zero transmission power or no transmission. The PTRS is used to track the phase on the time axis in order to compensate for frequency offset caused by phase noise. The TRS is used to compensate for Doppler shift during high-speed movement. Note that the TRS may be used as one configuration of the CSI-RS. For example, the radio resources may be configured as a TRS for one-port CSI-RS.

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

[0067] The DMRS is used to demodulate modulated signals. Two types of DMRS may be defined: a reference signal for demodulating the PUCCH and a reference signal for demodulating the PUSCH. Both may be referred to as DMRS. The SRS is used for measuring uplink channel state information (CSI), channel sounding, and beam management. The PTRS is used to track the phase on the time axis to compensate for frequency offsets caused by phase noise.

[0068] In this embodiment, downlink physical channels and / or downlink physical signals are collectively referred to as downlink signals. In this embodiment, uplink physical channels and / or uplink physical signals are collectively referred to as uplink signals. In this embodiment, downlink physical channels and / or uplink physical channels are collectively referred to as physical channels. In this embodiment, downlink physical signals and / or uplink physical signals are collectively referred to as physical signals.

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

[0070] 4 is a diagram showing an example of an SS / PBCH block (also referred to as a synchronization signal block, SS block, or SSB) according to this embodiment and a half frame (which may also be referred to as an SS burst set) in which one or more SS / PBCH blocks are transmitted. Fig. 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 also be referred to as an SSB period), and the SS / PBCH block is composed of four consecutive OFDM symbols.

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

[0072] In Fig. 4, the PSS, SSS, PBCH, and DMRS for the PBCH are time / frequency multiplexed in one SS / PBCH block. Fig. 5 is a table showing resources in which the PSS, SSS, PBCH, and DMRS for the PBCH are allocated within the SS / PBCH block.

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

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

[0075] The PBCH and DMRS may be mapped to the second, third, and fourth symbols in the SS / PBCH block (OFDM symbols with OFDM symbol numbers 1, 2, and 3 relative to the start symbol of the SS / PBCH block). The sequence of modulation symbols for the PBCH is M symb The SS / PBCH block is composed of symbols, and may be mapped to resources to which a DMRS is not mapped, including the 1st subcarrier to the 240th subcarrier of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the starting subcarrier of the SS / PBCH block), and the 1st subcarrier to the 48th subcarrier and the 184th to 240th subcarriers of the third symbol in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 47 and 192 to 239 relative to the starting subcarrier of the SS / PBCH block). The DMRS symbol sequence is composed of 144 symbols, and may be mapped to the first to 240th subcarriers of the second and fourth symbols in the SS / PBCH block (subcarriers with subcarrier numbers 0 to 239 relative to the starting subcarrier of the SS / PBCH block), and to the first 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 starting subcarrier of the SS / PBCH block), with one subcarrier for every four subcarriers. For example, of the 240 subcarriers, PBCH modulation symbols may be mapped to 180 of the subcarriers, and DMRS for the PBCH may be mapped to 60 of the subcarriers.

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

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

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

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

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

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

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

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

[0084] The terminal device 1 according to this embodiment determines whether to consider a certain cell as a "barred" cell based on the connection state, the execution state of a predetermined timer, information in the received MIB, and / or information in the received SIB (which may be SIB1). However, a barred cell may be a cell on which the terminal device 1 is not allowed to camp. A cell is barred by an instruction in the system information. For example, the terminal device 1 does not camp on a barred cell. The terminal device 1 may consider a certain cell as a barred cell if it is unable to acquire an MIB for the cell.

[0085] If a cell is not a barred cell (it may be the case that the cell status is indicated as "not barred"), the terminal device 1 may treat the cell as a candidate cell in cell selection and cell reselection.

[0086] When a cell is a restricted cell (when the cell status is indicated as "barred" or when the cell status is treated as "barred"), the terminal device 1 is prohibited from selecting and reselecting the cell and selects another cell. When a cell is a restricted cell, the terminal device 1 may select / reselect another cell based on the MIB. For example, when a field included in the MIB indicates that selection / reselection of the same frequency is prohibited, the terminal device 1 may treat all other cells of the same frequency as restricted cells and not as candidates for reselection.

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

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

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

[0090] The base station device 3 of this embodiment transmits to the terminal device 1 an SIB1 (or any other SIB) containing parameters for determining whether the cell in which the terminal device 1 is located is restricted.

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

[0092] The initial downlink BWP may be configured by a parameter provided in an MIB, a parameter provided in SIB1, a parameter provided in an SIB, and / or an RRC parameter. For example, the initial downlink BWP may be configured by a parameter initialDownlinkBWP provided in SIB1. However, initialDownlinkBWP may be a parameter indicating a UE-specific (dedicated) configuration of the initial downlink BWP for a UE.

[0093] SIB1 may include downlinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one parameter for determining whether a cell is barred in a certain cell by the terminal device 1, may be included in downlinkConfigCommon, which indicates the common downlink parameters for a certain cell. downlinkConfigCommon may include a parameter (e.g., referred to as frequencyInfoDL) indicating a basic parameter related to one downlink carrier and transmission in the corresponding cell, and a parameter (e.g., referred to as initialDownlinkBWP) indicating an initial downlink BWP setting of a certain serving cell. SIB1 may also include allocationBandwidth, which is a parameter indicating the maximum allocated bandwidth of a certain cell. AllocationBandwidth may be included in any parameter in SIB1.

[0094] The information element (IE) of a BWP may be a parameter indicating the frequency location and bandwidth of the BWP. The information element of the BWP may include a parameter "subcarrierSpacing" indicating the subcarrier spacing used in the BWP, a parameter "locationAndBandwidth" indicating the location and bandwidth (number of resource blocks) of the BWP in the frequency domain, and / or a parameter "cyclicPrefix" indicating whether the BWP uses a standard cyclic prefix (CP) or an extended CP. That is, a BWP may be defined by the subcarrier spacing, the CP, and the location and bandwidth in the frequency domain. However, the value indicated by "locationAndBandwidth" may be interpreted as a resource indicator value (RIV). The resource indicator value indicates the starting PRB index and the number of consecutive PRBs of the BWP. However, the first PRB defining the region of the resource indicator value may be a PRB determined by the subcarrier spacing given by subcarrierSpacing of the BWP and the offsetToCarrier set in SCS-SpecificCarrier included in FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier spacing. Also, the size defining the region of the resource indicator value may be 275.

[0095] The initial Downlink BWP includes a BWP information element, a PDCCH configuration information element, and / or a PDSCH configuration information element for the corresponding cell, etc. However, the initial Downlink BWP may be configured by the network to include CORESET0 in the frequency domain.

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

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

[0098] allocationBandwidth is information indicating the maximum allocated bandwidth of the downlink and / or uplink that the terminal device 1 should support in the corresponding cell. The information indicating the maximum allocated bandwidth may be information specifying the bandwidth by the number of resource blocks. However, the information indicating the maximum allocated bandwidth may be set for each subcarrier spacing. The information indicating the maximum allocated bandwidth may be indicated by an information element including a parameter subcarrierSpacing indicating the subcarrier spacing and a parameter allocationBandwidth indicating the number of resource blocks in the bandwidth. The maximum allocated bandwidth may be the maximum bandwidth supported by the RF circuit provided in the terminal device 1. The maximum bandwidth may be the maximum bandwidth at which signals / channels transmitted on the downlink and / or uplink can be scheduled simultaneously. When signals / channels are scheduled discretely on the 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 allocated at a certain time.

[0099] The allocationBandwidth may be a parameter included in the information element of SCS-SpecificCarrier. The information indicating the maximum allocation bandwidth indicated by allocationBandwidth may be the number of resource blocks corresponding to the subcarrier spacing indicated by subcarrierSpacing of the information element of SCS-SpecificCarrier including the parameter. The information indicating the maximum allocation bandwidth may be information specifying the maximum allocation bandwidth by a percentage value of the carrier bandwidth notified by SCS-SpecificCarrier.

[0100] The allocationBandwidth may be a parameter included in an information element of a BWP. The information indicating the maximum allocated bandwidth indicated by allocationBandwidth may be the number of resource blocks corresponding to the subcarrier spacing indicated by subcarrierSpacing in the information element of the BWP including the parameter. The information indicating the maximum allocated bandwidth may be information specifying the maximum allocated bandwidth by a percentage value relative to the bandwidth of the BWP indicated by locationAndBandwidth included in the information element of the corresponding BWP. The allocationBandwidth may be a parameter set for each BWP.

[0101] The allocationBandwidth may be set as a common parameter that includes information indicating the maximum allocated bandwidth for the downlink and information indicating the maximum allocated bandwidth for the uplink in a cell, or may be set as separate parameters (for example, they may be called dlAllocationBandwidth and ulAllocationBandwidth, respectively).

[0102] When the initialDownlinkBWP is not provided in SIB1 (or may be another SIB or RRC parameter) received by the terminal device 1, the initial downlink BWP may be determined / specified by the positions and number of consecutive PRBs (Physical Resource Blocks) starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs of a CORESET (such as CORESET0) of the Type0-PDCCH CSS Set, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received in the CORESET of the Type0-PDCCH CSS Set. When the initialDownlinkBWP is provided in SIB1 received by the terminal device 1, the initial downlink BWP may be determined / specified by the initialDownlinkBWP.

[0103] However, "initialDownlinkBWP being provided" may mean a state in which initialDownlinkBWP is received in the RRC parameters and an RRC connection is established (for example, RRCSetup, RRCResume, and / or RRCReestablishment are received). For example, when the terminal device 1 receives initialDownlinkBWP in SIB1, it may set CORESET0 as the initial downlink BWP until it receives RRCSetup, RRCResume, or RRCReestablishment. However, setting CORESET0 as the initial downlink BWP may mean determining / specifying the initial downlink BWP by the position and number of consecutive PRBs starting from the PRB with the lowest index and ending with the PRB with the highest index among the PRBs of CORESET0. However, determining / specifying the initial downlink BWP may mean determining / specifying the frequency position and / or bandwidth of the initial downlink BWP. When the terminal device 1 receives the initialDownlinkBWP in SIB1, after receiving RRCSetup, RRCResume, and / or RRCReestablishment, the terminal device 1 may determine / specify the initial downlink BWP by the locationAndBandwidth included in the received initialDownlinkBWP. When the terminal device 1 receives the initialDownlinkBWP in SIB1, the terminal device 1 may specify the initial downlink BWP by CORESET0 until the RRC connection is established, and after the RRC connection is established, the terminal device 1 may determine / specify the initial downlink BWP by the locationAndBandwidth included in the initialDownlinkBWP.

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

[0105] The RRCResume may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCResumeRequest message or an RRCResumeRequest1 message to the base station device 3 (which may be a network). The base station device 3 (which may be a network) may transmit the RRCResume message to the terminal device 1 when the RRC connection with the terminal device 1 is resumed.

[0106] RRCReestablishment may be a message received from the base station device 3 (which may be a network) when the terminal device 1 transmits an RRCReestablishmentRequest message to the base station device 3 (which may be a network). The base station device 3 (which may be a network) may transmit the RRCReestablishment message to the terminal device 1 when re-establishing an RRC connection with the terminal device 1.

[0107] The initial uplink BWP may be configured 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 configured by a parameter initialUplinkBWP provided in SIB1, where initialUplinkBWP is a parameter indicating a UE-specific (dedicated) setting of the initial uplink BWP for each UE.

[0108] The initial uplink BWP may be defined / configured by initialUplinkBWP provided in SIB1 (which may be REDCAP SIB1, another SIB, or an RRC parameter). The terminal device 1 may determine the initial uplink BWP based on the initialUplinkBWP provided by the received SIB1.

[0109] The terminal device 1 has 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 via 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 to generate an RF signal, amplifies the power with the power amplifier, and then outputs the signal 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.

[0110] When the bandwidth of the set initial downlink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as the allocated bandwidth), the terminal device 1 may adjust / retune (tuning / retuning) 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 referred to as RF tuning / RF retuning. FIG. 6 is a diagram showing an example of RF retuning. In FIG. 6, when the applied band of the RF circuit used in the terminal device 1 is outside the band of the downlink channel received within the initial downlink BWP, the terminal device 1 performs RF retuning so that the applied band of the RF circuit includes the band of the downlink channel to be received. When the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as the allocated bandwidth), the terminal device 1 may adjust / retune (tuning / retuning) the frequency band to which the RF circuit is applied within the initial uplink BWP. When the bandwidth of the set downlink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as the allocated bandwidth), the terminal device 1 may adjust / readjust the frequency band to which the RF circuit is applied within the downlink BWP.When the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit included in the terminal device 1 (which may be referred to as the allocated bandwidth), the terminal device 1 may adjust / readjust the frequency band to which the RF circuit is applied within the uplink BWP.

[0111] The terminal device 1 may be configured with multiple initial downlink sub-BWPs by the SIB1. At least one of the multiple initial downlink sub-BWPs may be configured to include an SS / PBCH block. The terminal device 1 may operate by regarding an initial downlink sub-BWP including an SS / PBCH block (such as a cell-defining SSB) as the initial downlink BWP. At least one of the multiple initial downlink sub-BWPs may be configured to include CORESET0. All of the multiple initial downlink sub-BWPs may be configured to include their respective CORESET0. The terminal device 1 may operate by regarding an initial downlink sub-BWP including CORESET0 as the initial downlink BWP. The terminal device 1 may operate by regarding an initial downlink sub-BWP as the initial downlink BWP. Multiple initial downlink sub-BWPs may be considered as multiple initial downlink BWPs. The multiple initial downlink sub-BWPs may be designed to be included in the frequency band of one initial downlink BWP. The initial downlink sub-BWP may be referred to as a downlink BWP or a downlink sub-BWP. However, for the terminal device 1, "multiple initial downlink BWPs are configured" may mean that multiple frequency positions and / or multiple bandwidths of the initial downlink BWP are configured. The base station device 3 may broadcast information including the configuration of multiple frequency positions and / or multiple bandwidths of the initial downlink BWP, and the terminal device 1 may determine / identify / configure the frequency positions and bandwidths of the initial downlink BWP based on the information.

[0112] A terminal device 1 according to one embodiment of the present invention receives / specifies configuration information of an initial downlink BWP using an upper layer parameter initialDownlinkBWP. However, the initialDownlinkBWP may be included in an SIB1 or in any RRC message. For example, the configuration information of the initial downlink BWP may include information indicating the frequency location and bandwidth of the initial downlink BWP. The terminal device 1 may receive an SIB1 or any RRC message including multiple pieces of configuration information of the initial downlink BWP. Multiple pieces of configuration information of the initial downlink BWP may be included in one parameter initialDownlinkBWP.

[0113] 7 shows an example of a parameter configuration of an information element (IE) BWP-DownlinkCommon of the initialDownlinkBWP according to this embodiment. The initialDownlinkBWP according to this embodiment may include genericParameters, a generic parameter of the initial downlink BWP, a cell-specific parameter pdcch-ConfigCommon of the PDCCH, a cell-specific parameter pdsch-ConfigCommon of the PDSCH, a parameter indicating second configuration information of the initial downlink BWP, and / or a parameter initialBwpTiming indicating the timing for applying the second configuration information of the initial downlink BWP. However, the parameter indicating the second configuration information of the initial downlink BWP may be a parameter locationAndBandwidth-rc in the initialDownlinkBWP indicating a second "frequency location and bandwidth" of the initial downlink BWP. When multiple initial downlink BWPs are configured in a cell (or when multiple frequency positions and / or multiple bandwidth configuration information for the initial downlink BWPs is broadcast in a cell), some of the information included in genericParameters in initialDownlinkBWP may be parameters common to the multiple initial downlink BWPs (or the multiple frequency positions and / or multiple bandwidth configuration information for the initial downlink BWPs).

[0114] The genericParameters included in the initialDownlinkBWP is configured with an information element (IE) BWP, and includes a parameter "locationAndBandwidth" indicating the frequency location and bandwidth of the initial downlink BWP, a parameter "subcarrierSpacing" indicating the subcarrier spacing used for all channels and reference signals in the initial downlink BWP, and a parameter "cyclicPrefix" indicating whether an extended cyclic prefix (CP) is used in the initial downlink BWP. However, when multiple "frequency locations and bandwidths" of the initial downlink BWP are configured in a certain cell, the "locationAndBandwidth" included in the genericParameters in the initialDownlinkBWP may be a parameter indicating the first "frequency location and bandwidth" of the initial downlink BWP. However, when multiple "frequency location and bandwidth" of the initial downlink BWP are configured in a certain cell, subcarrierSpacing included in genericParameters in initialDownlinkBWP may be a parameter indicating the subcarrier spacing used in all channels and reference signals in the initial downlink BWP configured with a first "frequency location and bandwidth," or may be a parameter indicating the subcarrier spacing used in all channels and reference signals that is common to initial downlink BWPs configured with different "frequency location and bandwidth." For example, the terminal device 1 may determine / specify the subcarrier spacing used in all channels (e.g., PDCCH, PDSCH) and reference signals in the initial downlink BWP based on subcarrierSpacing included in genericParameters in initialDownlinkBWP, regardless of whether the initialDownlinkBWP includes configuration information (locationAndBandwidth-rc) of the second "frequency location and bandwidth."However, when multiple "frequency location and bandwidth" of the initial downlink BWP are configured in a certain cell, the cyclicPrefix included in the genericParameters in the initialDownlinkBWP may be a parameter indicating whether an extended cyclic prefix (CP) is used in the initial downlink BWP configured with the first "frequency location and bandwidth", or may be a parameter indicating whether an extended CP is used in common for the initial downlink BWPs configured with different "frequency location and bandwidth". For example, the terminal device 1 may determine / specify whether an extended CP is used in the initial downlink BWP based on the cyclicPrefix included in the genericParameters in the initialDownlinkBWP, regardless of whether the initialDownlinkBWP includes configuration information (locationAndBandwidth-rc) of the second "frequency location and bandwidth".

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

[0116] However, the parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating multiple "frequency locations and bandwidths" for the initial downlink BWP may be information for setting multiple initial downlink BWPs with different frequency locations and / or bandwidths. However, the parameters (locationAndBandwidth and locationAndBandwidth-rc in initialDownlinkBWP) indicating multiple "frequency locations and bandwidths" for the initial downlink BWP may be information for indicating multiple "frequency locations and bandwidths" of the initial downlink BWP.

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

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

[0119] The information element (IE) ControlResourceSetZero indicated by controlResourceSetZero is set to any value between 0 and 15. However, the number of values ​​that can be set to ControlResourceSetZero may be other than 16, for example, 32. The information element SearchSpaceZero indicated by searchSpaceZero is set to any value between 0 and 15. However, the number of values ​​that can be set to SearchSpaceZero may be other than 16, for example, 32.

[0120] The terminal device 1 determines the number of consecutive resource blocks and the number of 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, the terminal device 1 may determine the table to be applied based on the supported UE category and / or UE capability. However, the terminal device 1 may determine the table to be applied based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to be applied based on the subcarrier spacing of the SS / PBCH block and / or the subcarrier spacing 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 (which may be PRBs) of CORESET0, the number of symbols of CORESET0, the offset and / or the number of PDCCH repetitions.

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

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

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

[0124] The terminal device 1 receives the initialDownlinkBWP including the RRC parameter pdcch-ConfigCommon in the SIB1 or an RRC message, and monitors the PDCCH based on the parameter.

[0125] The terminal device 1 determines a PDCCH monitoring opportunity from searchSpaceZero in pdcch-ConfigCommon. The value indicated by searchSpaceZero is applied as an index to a predetermined table. The terminal device 1 may determine the table to be applied based on the supported UE category and / or UE capability. The terminal device 1 may determine the table to be applied based on the frequency range.

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

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

[0128] The pdsch-ConfigCommon included in the initialDownlinkBWP may include a parameter pdsch-TimeDomainAllocationList indicating a list of time domain configurations for timing of downlink allocation for downlink data.

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

[0130] The value indicated by locationAndBandwidth-rc included in the initialDownlinkBWP is interpreted as a Resource Indicator Value (RIV). The RIV is an index indicating the start position of a resource block and the number of consecutive resource blocks, and the frequency location and bandwidth of the initial downlink BWP can be identified by the value of this index.

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

[0132] A terminal device 1 that 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 the base station device 3 by identifying / determining the second initial downlink BWP from the locationAndBandwidth-rc included in the initialDownlinkBWP.

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

[0134] The terminal device 1 may specify / determine the subcarrier spacing used for all channels and reference signals in the initial downlink BWP by using subcarrierSpacing included in genericParameters in the initialDownlinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialDownlinkBWP.The terminal device 1 may specify / determine whether an extended cyclic prefix CP is used in the initial downlink BWP by using cyclicPrefix included in genericParameters in the initialDownlinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialDownlinkBWP.

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

[0136] When the terminal device 1 receives locationAndBandwidth-rc included in SIB1 and specifies / determines the frequency location and bandwidth of the initial downlink BWP based on the locationAndBandwidth-rc, CORESET0 may be used as the initial downlink BWP until the RRC connection is established, re-established, or resumed (for example, before receiving RRCSetup, RRCResume, or RRCReestablishment), and after the RRC connection is established, the initial downlink BWP may be determined / specified using locationAndBandwidth-rc included in the received SIB1. However, when the initial downlink BWP is set to CORESET0 until the RRC connection is established, re-established, or resumed, the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified using CORESET0.

[0137] When the terminal device 1 receives locationAndBandwidth-rc included in SIB1 and specifies / determines the frequency location and bandwidth of the initial downlink BWP based on the locationAndBandwidth-rc, CORESET0 may be the initial downlink BWP until the SIB1 is received, and after SIB1 is received, the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1. However, if the initial downlink BWP is determined / specified by locationAndBandwidth-rc at the time of receiving SIB1, the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified by locationAndBandwidth-rc.

[0138] Based on the information included in SIB 1, the terminal device 1 may switch the timing for determining / specifying the initial downlink BWP based on locationAndBandwidth-rc included in SIB 1. The parameter initialBwpTiming indicating the timing for applying locationAndBandwidth-rc included in SIB 1 may be 1-bit information.

[0139] initialBwpTiming may be information indicating whether to determine / specify / apply the frequency location and bandwidth indicated by locationAndBandwidth-rc as the frequency location and bandwidth of the initial downlink BWP before the RRC connection is established (before receiving RRCSetup / RRCResume / RRCReestablishment). However, if the terminal device 1 determines / specifies / applies the frequency location and bandwidth indicated by locationAndBandwidth-rc as the frequency location and bandwidth of the initial downlink BWP before the RRC connection is established, the terminal device 1 may perform initial access at the frequency location and bandwidth indicated by locationAndBandwidth-rc. For example, the terminal device 1 may receive a PDCCH, a random access response, and / or a PDSCH on frequency resources based on the frequency location and bandwidth indicated by locationAndBandwidth-rc.

[0140] initialBwpTiming may be information indicating whether the frequency location and bandwidth indicated by locationAndBandwidth-rc are determined / identified / applied as the frequency location and bandwidth of the initial downlink BWP at the time when the RRC connection is established, or whether they are applied as the frequency location and bandwidth of the initial downlink BWP at the time when SIB1 is received.

[0141] Depending on the value of initialBwpTiming, the terminal device 1 may switch the timing for determining / specifying the initial downlink BWP based on locationAndBandwidth-rc included in SIB1. For example, when initialBwpTiming is a first value, CORESET0 may be the initial downlink BWP until the SIB1 is received, and after the SIB1 is received, the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1. When initialBwpTiming is a second value, CORESET0 may be the initial downlink BWP until the RRC connection is established, re-established, or resumed (for example, before receiving RRCSetup, RRCResume, or RRCReestablishment), and after the RRC connection is established, the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1. However, the terminal device 1 may switch the timing for determining / specifying the initial downlink BWP depending on whether the parameter initialBwpTiming is included in SIB1 or not (absent). For example, when initialBwpTiming is included in SIB1 with a value of beforeerrc, CORESET0 may be the initial downlink BWP until the SIB1 is received, and after the SIB1 is received, the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1. For example, when initialBwpTiming is not included in SIB1, CORESET0 may be the initial downlink BWP until the RRC connection is established, re-established, or resumed (for example, before receiving RRCSetup, RRCResume, or RRCReestablishment), and after the RRC connection is established, the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1.

[0142] However, although the present embodiment describes initialBwpTiming as a parameter that can be included in SIB1, it may be a parameter that can be included in other SIBs or RRC parameters. For example, initialBwpTiming may be a parameter that can be included in the RRC parameter initialDownlinkBWP, and the initialDownlinkBWP may be included in SIB1, other SIBs, and / or RRC parameters.

[0143] 8 is a flow chart showing an example of a process related to determining / specifying an initial downlink BWP in the terminal device 1 of this embodiment. In step S1001 of FIG. 8, the terminal device 1 receives, in SIB1, a common parameter (information) initialDownlinkBWP of an initial downlink BWP of a certain cell, including a parameter locationAndBandwidth-rc indicating the frequency location and bandwidth of the initial downlink BWP. In step S1002, the terminal device 1 determines whether initialBwpTiming is included in the received initialDownlinkBWP. If initialBwpTiming is included in the initialDownlinkBWP (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 the initialDownlinkBWP from the time of receiving SIB1. If initialBwpTiming is not included in the initialDownlinkBWP in step S1002 (S1002-No), in step S1004, the terminal device 1 determines / identifies / maintains CORESET0 as the initial downlink BWP until the RRC connection is established, and determines / identifies the frequency location and bandwidth of the initial downlink BWP based on locationAndBandwidth-rc in the initialDownlinkBWP at the time the RRC connection is established.

[0144] In this way, by changing the timing for determining the frequency location and bandwidth of the initial downlink BWP based on the information in SIB1, the base station device 1 can appropriately set the initial downlink BWP for the terminal device 1 to which locationAndBandwidth-rc is applicable.

[0145] The terminal device 1 may be configured with multiple initial uplink sub-BWPs by SIB1. The terminal device 1 may determine one or more initial uplink sub-BWPs based on the initialUplinkBWP provided by SIB1. At least one of the multiple initial uplink sub-BWPs may be configured to include physical random access channel resources. The terminal device 1 may operate by regarding the initial uplink sub-BWP as the 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 included in the frequency band of one initial uplink BWP. The initial uplink sub-BWP may also be referred to as an uplink BWP or an uplink sub-BWP. However, for the terminal device 1, "configuring multiple initial uplink BWPs" may mean configuring multiple frequency positions and / or multiple bandwidths of the initial uplink BWP. The base station device 3 may broadcast information including the setting of multiple frequency positions and / or multiple bandwidths of 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 the information.

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

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

[0148] A terminal device 1 according to one embodiment of the present invention receives / specifies configuration information of an initial uplink BWP using an upper layer parameter initialUplinkBWP. However, initialUplinkBWP may be included in SIB1 or any RRC message. For example, the configuration information of the initial uplink BWP may include information indicating the frequency location and bandwidth of the initial uplink BWP. The terminal device 1 may receive SIB1 or any RRC message including multiple pieces of configuration information of the initial uplink BWP. Multiple pieces of configuration information of the initial uplink BWP may be included in one parameter initialUplinkBWP.

[0149] 9 shows an example of a parameter configuration of an information element (IE) BWP-UplinkCommon of the initialUplinkBWP according to this embodiment. The initialUplinkBWP according to this embodiment may include generic parameters of the initial uplink BWP (genericParameters), cell-specific parameters for random access (rach-ConfigCommon), cell-specific parameters for PUSCH (pusch-ConfigCommon), cell-specific parameters for PUCCH (pusch-ConfigCommon), and / or parameters indicating second configuration information of the initial uplink BWP. However, the parameter indicating the second configuration information of the initial uplink BWP may be a parameter (locationAndBandwidth-rc) indicating a second "frequency location and bandwidth" of the initial uplink BWP. When multiple initial uplink BWPs are configured in a cell (or when multiple frequency locations and / or multiple bandwidth configuration information for the initial uplink BWPs is broadcast in a cell), some of the information included in genericParameters may be parameters common to the multiple initial uplink BWPs (or the multiple frequency locations and / or multiple bandwidth configuration information for the initial uplink BWPs).

[0150] The genericParameters included in the initialUplinkBWP is configured with an information element (IE) BWP and includes a parameter "locationAndBandwidth" indicating the frequency location and bandwidth of the initial uplink BWP, a parameter "subcarrierSpacing" indicating the subcarrier spacing used in all channels and reference signals in the initial uplink BWP, and a parameter "cyclicPrefix" indicating whether an extended cyclic prefix (CP) is used in the initial uplink BWP. However, when multiple "frequency locations and bandwidths" of the initial uplink BWP are configured in a certain cell, the "locationAndBandwidth" included in the genericParameters may be a parameter indicating the first "frequency location and bandwidth" of the initial uplink BWP. However, when multiple "frequency location and bandwidth" of the initial uplink BWP are configured in a certain cell, subcarrierSpacing included in genericParameters may be a parameter indicating the subcarrier spacing used in all channels and reference signals in the initial uplink BWP configured with a first "frequency location and bandwidth," or may be a parameter indicating the subcarrier spacing used in all channels and reference signals that is common to initial uplink BWPs configured with different "frequency location and bandwidth." For example, the terminal device 1 may determine / specify the subcarrier spacing used in all channels (e.g., PUCCH, PUSCH, PRACH) and reference signals in the initial uplink BWP based on subcarrierSpacing included in genericParameters in the initialUplinkBWP, regardless of whether the initialUplinkBWP includes configuration information (locationAndBandwidth-rc) of the second "frequency location and bandwidth."However, when multiple "frequency location and bandwidth" of the initial uplink BWP are configured in a certain cell, the cyclicPrefix included in the genericParameters in the initialUplinkBWP may be a parameter indicating whether an extended cyclic prefix (CP) is used in the initial uplink BWP configured with the first "frequency location and bandwidth", or may be a parameter indicating whether an extended CP is used in common for the initial uplink BWPs configured with different "frequency location and bandwidth". For example, the terminal device 1 may determine / specify whether an extended CP is used in the initial uplink BWP based on the cyclicPrefix included in the genericParameters in the initialUplinkBWP, regardless of whether the initialUplinkBWP includes configuration information (locationAndBandwidth-rc) of the second "frequency location and bandwidth".

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

[0152] However, the parameters indicating multiple "frequency locations and bandwidths" for the initial uplink BWP (locationAndBandwidth and locationAndBandwidth-rc in initialUplinkBWP) may be information for setting multiple initial uplink BWPs with different frequency locations and / or bandwidths. However, the parameters indicating multiple "frequency locations and bandwidths" for the initial uplink BWP (locationAndBandwidth and locationAndBandwidth-rc in initialUplinkBWP) may be information for indicating multiple "frequency locations and bandwidths" for the initial uplink BWP.

[0153] However, in this embodiment, the parameter locationAndBandwidth-rc in initialUplinkBWP indicating the second "frequency location and bandwidth" of the initial uplink BWP can be treated as an additional parameter to the generic parameters by configuring it so that it is not included in genericParameters, which are generic parameters of the initial uplink, but locationAndBandwidth-rc may also be configured to be included in genericParameters in initialUplinkBWP.

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

[0155] When multiple parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating "frequency location and bandwidth" for an initial uplink BWP are configured in a cell (multiple initial uplink BWPs may be configured in a cell), pucch-ConfigCommon included in initialUplinkBWP or each parameter of the pucch-ConfigCommon may be a cell-specific parameter of a PDCCH in the initial uplink BWP configured with a first "frequency location and bandwidth", or may be a cell-specific parameter of a PUCCH that is common to initial uplink BWPs configured with different "frequency locations and bandwidths". For example, the terminal device 1 may determine / identify cell-specific parameters of the PUCCH in the initial uplink BWP based on pucch-ConfigCommon included in the initialUplinkBWP or some of the parameters of the pucch-ConfigCommon, regardless of whether the initialUplinkBWP includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

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

[0157] When multiple parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating "frequency location and bandwidth" for an initial uplink BWP are configured in a certain cell (multiple initial uplink BWPs may be configured in a certain cell), pusch-ConfigCommon included in initialUplinkBWP or each parameter of the pusch-ConfigCommon may be a cell-specific parameter of a PUSCH in the initial uplink BWP configured with a first "frequency location and bandwidth", or may be a cell-specific parameter of a PUSCH that is common to initial uplink BWPs configured with different "frequency locations and bandwidths". For example, the terminal device 1 may determine / identify cell-specific parameters of the PUSCH in the initial uplink BWP based on pusch-ConfigCommon included in the initialUplinkBWP or some of the parameters of the pusch-ConfigCommon, regardless of whether the initialUplinkBWP includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0158] The value indicated by locationAndBandwidth-rc included in initialUplinkBWP is interpreted as a Resource Indicator Value (RIV). RIV is an index indicating the start position of a resource block and the number of consecutive resource blocks, and the frequency location and bandwidth of the initial uplink BWP can be identified by the value of this index.

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

[0160] A terminal device 1 that does not support the frequency location and / or bandwidth of the first initial uplink BWP can receive the uplink channel and uplink signal transmitted from the base station device 3 by identifying / determining the second initial uplink BWP from the locationAndBandwidth-rc included in the initialUplinkBWP.

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

[0162] The terminal device 1 may specify / determine the subcarrier spacing used in all channels and reference signals in the initial uplink BWP by using subcarrierSpacing included in genericParameters in the initialUplinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialUplinkBWP.The terminal device 1 may specify / determine whether an extended cyclic prefix CP is used in the initial uplink BWP by using cyclicPrefix included in genericParameters in the initialUplinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialUplinkBWP.

[0163] The terminal device 1 may identify / determine cell-specific parameters of the PUCCH in the initial uplink BWP using pucch-ConfigCommon included in the initialUplinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialUplinkBWP, and transmit the PUCCH. The terminal device 1 may identify / determine cell-specific parameters of the PUSCH in the initial uplink BWP using pusch-ConfigCommon included in the initialUplinkBWP, regardless of whether locationAndBandwidth-rc is included in the initialUplinkBWP, and transmit the PUSCH.

[0164] rach-ConfigCommon included in initialUplinkBWP is a setting of cell-specific random access parameters used by the terminal device 1 for contention-based or contention-free random access. Fig. 10 shows an example of the parameter configuration of an information element RACH-ConfigGeneric of a parameter rach-ConfigGeneric included in the parameter configuration RACH-ConfigCommon of an information element (IE) RACH-ConfigCommon according to this embodiment.

[0165] rach-ConfigCommon may include a parameter rach-ConfigGeneric used to specify random access parameters used in regular random access and beam failure recovery, a parameter totalNumberOfRA-Preambles indicating the total number of preambles used in collision-based random access and collision-free random access in the RACH resources defined in RACH-ConfigCommon, a parameter ssb-perRACH-OccasionAndCB-PreamblesPerSSB indicating the number of SSBs per PRACH transmission opportunity and / or the number of PRACH transmission opportunities consecutively assigned to one SSB, and / or a parameter msg1-SubcarrierSpacing indicating the subcarrier spacing of the PRACH.

[0166] RACH-ConfigGeneric may include a parameter prach-ConfigurationIndex indicating the index of the PRACH configuration, a parameter msg1-FDM indicating the number of PRACH transmission opportunities that are frequency division multiplexed per time, a parameter msg1-FrequencyStart indicating the first offset of the lowest PRACH transmission opportunity in the frequency domain for the PRB with index 0, and a parameter msg1-FrequencyStart-rc indicating the second offset of the lowest RACH opportunity in the frequency domain for the PRB with index 0.

[0167] 11 is a diagram showing the concept of the frequency locations of one or more PRACH transmission opportunities indicated by msg1-FrequencyStart and msg1-FrequencyStart-rc. In FIG. 11, two consecutive PRACH transmission opportunities (ROs) (where msg1-FDM is 2) are arranged in an uplink BWP consisting of eight PRBs. In FIG. 11, msg1-FrequencyStart is 2, and the PRACH transmission opportunity with the lowest frequency is arranged in PRB2, which is the second PRB from uplink BWP index 0, and the second PRACH transmission opportunity is arranged consecutively. In FIG. 11, msg1-FrequencyStart-rc is 6, and the PRACH transmission opportunity with the lowest frequency is arranged in PRB6, which is the sixth PRB from uplink BWP index 0, and the second PRACH transmission opportunity is arranged consecutively.

[0168] In this way, by setting different offset values ​​for the two parameters msg1-FrequencyStart and msg1-FrequencyStart-rc, different sets of PRACH transmission opportunities can be assigned to terminal devices 1 that support msg1-FrequencyStart-rc and terminal devices 1 that do not support msg1-FrequencyStart-rc.

[0169] However, when allocating the same set of PRACH transmission opportunities to a terminal device 1 that supports msg1-FrequencyStart-rc and a terminal device 1 that does not support msg1-FrequencyStart-rc, msg1-FrequencyStart-rc does not have to be included. For example, when msg1-FrequencyStart-rc is not included in the received SIB1, the terminal device 1 may identify / determine one or more PRACH transmission opportunities using msg1-FrequencyStart included in SIB1, and when msg1-FrequencyStart-rc is included in the received SIB1, the terminal device 1 may identify / determine one or more PRACH transmission opportunities using the msg1-FrequencyStart-rc. In this way, depending on the presence or absence of msg1-FrequencyStart-rc, the base station device 3 can switch between allocating a different set of PRACH transmission opportunities to a specific terminal device 1 and allocating the same set of PRACH transmission opportunities to all terminal devices 1.

[0170] 12 is a flow chart showing an example of processing related to identifying / determining frequency locations of one or more PRACH transmission opportunities in the terminal device 1 of this embodiment. In step S2001 of FIG. 12, the terminal device 1 receives SIB1 including first offset information msg1-FrequencyStart. In step S2002, the terminal device 1 determines whether the received SIB1 includes second offset information msg1-FrequencyStart-rc. If SIB1 includes msg1-FrequencyStart-rc (S2002-Yes), in step S2003, the terminal device 1 identifies / determines frequency resources of one or more PRACH transmission opportunities based on msg1-FrequencyStart-rc. If SIB1 does not include msg1-FrequencyStart-rc (S2002-No), in step S2004, the terminal device 1 identifies / determines frequency resources of one or more PRACH transmission opportunities based on msg1-FrequencyStart. In step S2005, the terminal device 1 transmits a random access preamble using one of the one or more identified / determined PRACH transmission opportunities.

[0171] However, the parameters set in SIB1 may be broadcast in another SIB (or REDCAP SIB) or may be notified in an RRC message.

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

[0173] 13 is a schematic block diagram showing the configuration of a terminal device 1 of this embodiment. As shown in the figure, the terminal device 1 includes a radio transmission / reception unit 10 and an upper layer processing unit 14. The radio transmission / reception unit 10 includes an antenna unit 11, an RF (Radio Frequency) unit 12, and a baseband unit 13. The upper layer processing unit 14 includes a medium access control layer processing unit 15 and a radio resource control layer processing unit 16. The radio transmission / reception unit 10 is also referred to as a transmitter unit 10, a receiver unit 10, a monitor unit 10, or a physical layer processing unit 10. The upper layer processing unit 14 is also referred to as a processor unit 14, a measurement unit 14, a selector unit 14, a decision unit 14, or a control unit 14.

[0174] The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by user operation or the like to the radio transceiver unit 10. The upper layer processing unit 14 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function to acquire bit information of the MIB (which may be the REDCAP MIB), SIB1 (which may be the REDCAP SIB1), and other SIBs (which may be the REDCAP SIBs). The upper layer processing unit 14 may have a function to determine / specify the initial downlink BWP configuration (e.g., frequency location and bandwidth) based on information in the system information block (SIB1 / SIB) and / or an RRC message. The higher layer processing unit 14 may be configured to determine / specify the initial uplink BWP configuration (e.g., frequency location and bandwidth) based on information in the system information block (SIB1 / SIB) and / or RRC message. The higher layer processing unit 14 may be configured to determine / specify frequency resources for one or more PRACH transmission opportunities based on information in the system information block (SIB1 / SIB) and / or RRC message.

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

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

[0177] The radio transceiver 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The radio transceiver 10 separates, demodulates, and decodes signals received from the base station device 3 and outputs the decoded information to the upper layer processing unit 14. The radio transceiver 10 generates transmission signals by modulating and encoding data and transmits them to the base station device 3, etc. The radio 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 radio transceiver 10 also generates and transmits uplink signals (including PUCCH and / or PUSCH) based on instructions from the upper layer processing unit 14. The radio transceiver 10 may be equipped with a function to receive SSB, PSS, SSS, PBCH, DMRS for PBCH, random access response, PDCCH, and / or PDSCH. The radio transceiver 10 may be equipped with a function to transmit PRACH (which may be a random access preamble), PUCCH, and / or PUSCH. The radio transceiver 10 may have a function of monitoring the PDCCH. The radio transceiver 10 may have a function of receiving DCI on the PDCCH. The radio transceiver 10 may have a function of outputting the DCI received on the PDCCH to the upper layer processing unit 14. The radio transceiver 10 may have a function of receiving a system information block (SIB1 and / or SIB) corresponding to a predetermined cell.

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

[0179] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 removes a portion corresponding to a 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 a frequency domain signal.

[0180] The baseband unit 13 performs an inverse fast Fourier transform (IFFT) on the data to generate OFDM symbols, adds a CP to the generated OFDM symbols, generates baseband digital signals, and converts the baseband digital signals into analog signals. The baseband unit 13 outputs the converted analog signals to the RF unit 12.

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

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

[0183] The RF unit 12 may have a function of adjusting / retuning a frequency band to which the RF circuit is applied within the downlink BWP when the bandwidth of the set downlink BWP (e.g., initial downlink BWP) is wider than the bandwidth supported by the receiver of the device itself (which may be referred to as allocated bandwidth). Note that the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when downconverting a received signal to a baseband signal.

[0184] The RF unit 12 may have a function of adjusting / readjusting the frequency band to which the RF circuit is applied within the uplink BWP when the bandwidth of the set uplink BWP (e.g., initial downlink BWP) is wider than the bandwidth supported by the transmitter of the own device (which may be referred to as allocated bandwidth). Note that 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.

[0185] 14 is a schematic block diagram showing the configuration of a base station device 3 according to this embodiment. As shown in the figure, the base station device 3 includes a radio transmission / reception unit 30 and an upper layer processing unit 34. The radio transmission / reception unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36. The radio transmission / reception unit 30 is also referred to as a transmitter unit 30, a receiver unit 30, a monitor unit 30, or a 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 upper layer processing unit 34 is also referred to as a processing unit 34, a determination unit 34, or a control unit 34.

[0186] The upper layer processing unit 34 performs some or all of the processing of the Medium Access Control (MAC) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Radio Resource Control (RRC) layer. The upper layer processing unit 34 may have a function of generating DCI based on the upper layer signal transmitted to the terminal device 1 and the time resource for transmitting the PUSCH. The upper layer processing unit 34 may have a function of outputting the generated DCI, etc. to the radio transceiver unit 30. The upper layer processing unit 34 may have a function of generating a system information block (SIB1 / SIB) and / or an RRC message including information for the terminal device 1 to specify an initial downlink BWP. The upper layer processing unit 34 may have a function of generating a system information block (SIB1 / SIB) and / or an RRC message including information for the terminal device 1 to specify an initial uplink BWP. The upper layer processing unit 34 may also have the functionality to generate a system information block (SIB1 / SIB) and / or an RRC message containing information for the terminal device 1 to identify frequency resources for one or more PRACH transmission opportunities.

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

[0188] The radio resource control layer processing unit 36 ​​included in the upper layer processing unit 34 performs processing of the RRC layer. The radio resource control layer processing unit 36 ​​generates DCI (uplink grant, downlink grant) including resource allocation information for the terminal device 1. The radio resource control layer processing unit 36 ​​generates or acquires from an upper node DCI, downlink data (transport block (TB), random access response (RAR)) allocated to the PDSCH, system information, RRC messages, MAC Control Elements (CEs), and the like, and outputs them to the radio transceiver unit 30. The radio resource control layer processing unit 36 ​​also manages various setting information / parameters for each terminal device 1. The radio resource control layer processing unit 36 ​​may set various setting information / parameters for each terminal device 1 via upper layer signaling. That is, the radio resource control layer processing unit 36 ​​transmits / reports information indicating various setting information / parameters. The radio resource control layer processing unit 36 ​​may also transmit / report information for identifying the setting of one or more reference signals in a certain cell.

[0189] When the base station device 3 transmits an RRC message, a MAC CE, and / or a PDCCH to the terminal device 1 and the terminal device 1 performs processing based on the reception thereof, the base station device 3 performs processing (control of the terminal device 1 and the system) assuming that the terminal device is performing the processing. In other words, the base station device 3 sends an RRC message, a MAC CE, and / or a PDCCH to the terminal device 1 that causes the terminal device to perform processing based on the reception thereof.

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

[0191] Furthermore, the upper layer processing unit 34 transmits (transfers) or receives control messages or user data between base station devices 3 or between upper network devices (MME, S-GW (Serving-GW)) and the base station device 3. In Fig. 14, other components of the base station device 3 and transmission paths of data (control information) between the components are omitted, but it is clear that the upper layer processing unit 34 has, as its components, multiple blocks having other functions necessary for operating as the 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.

[0192] Note that the "parts" in the figure are elements that realize the functions and procedures of the terminal device 1 and the base station device 3, and may also be expressed by terms such as section, circuit, component, device, and unit.

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

[0194] (1) A terminal device 1 in a first aspect of the present invention includes a receiving unit 10 that receives a PDCCH in CORESET0 and receives SIB1 scheduled in the PDCCH, and a control unit 14 that identifies the frequency location and bandwidth of an initial downlink BWP, wherein the SIB1 includes first information (locationAndBandwidth-rc) indicating a first frequency location and a first bandwidth, and second information (initialBwpTiming), and the second information is information indicating whether or not the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP before establishing an RRC connection.

[0195] (2) In the first aspect of the present invention, the second information may be information indicating whether the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP at the time of establishing an RRC connection, or whether the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP at the time of receiving the SIB1.

[0196] (3) In the first aspect of the present invention, until the first frequency location and the first bandwidth are applied as the frequency location and bandwidth of the initial downlink BWP, one or more consecutive PRBs starting from the PRB with the lowest index of the PRBs of CORESET0 and ending with the PRB with the highest index of the PRBs of CORESET0 may be applied as the frequency location and bandwidth of the initial downlink BWP.

[0197] (4) A base station device 3 in a second aspect of the present invention includes a transmitter 30 that transmits a PDCCH in CORESET0 and transmits SIB1 scheduled in the PDCCH, and a controller 34 that determines the frequency location and bandwidth of an initial downlink BWP, wherein the SIB1 includes first information (locationAndBandwidth-rc) indicating a first frequency location and a first bandwidth, and second information (initialBwpTiming), and the second information is information indicating whether or not the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP before establishing an RRC connection.

[0198] (5) In a second aspect of the present invention, the second information may be information indicating whether the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP at the time of establishing an RRC connection, or whether the first frequency location and the first bandwidth are to be applied as the frequency location and bandwidth of the initial downlink BWP at the time of receiving the SIB1.

[0199] (6) In the second aspect of the present invention, until the first frequency location and the first bandwidth are applied as the frequency location and bandwidth of the initial downlink BWP, one or more consecutive PRBs starting from the PRB with the lowest index of the PRBs of CORESET0 and ending with the PRB with the highest index of the PRBs of CORESET0 may be applied as the frequency location and bandwidth of the initial downlink BWP.

[0200] (7) A terminal device 1 in a third aspect of the present invention includes a receiving unit 10 that receives SIB1 including first offset information (msg1-FrequencyStart), a control unit 14 that identifies frequency resources of one or more PRACH transmission opportunities based on the SIB1, and a transmitting unit 10 that transmits a random access preamble using one of the one or more PRACH transmission opportunities, wherein the control unit 14 identifies the frequency resources of the one or more PRACH transmission opportunities based on the first offset information when the SIB1 does not include second offset information (msg1-FrequencyStart-rc), and identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information when the SIB1 includes second offset information.

[0201] (8) In a third aspect of the present invention, the offset information used for the first offset information and the second offset information may be information indicating an offset value in the frequency domain from a PRB having an index of 0 in an uplink BWP to a PRACH transmission opportunity with the lowest frequency among the one or more PRACH transmission opportunities.

[0202] (9) A base station device 3 in a fourth aspect of the present invention comprises a transmitter 30 that transmits an SIB1 including first offset information (msg1-FrequencyStart) to a terminal device 1, a controller 34 that identifies frequency resources of one or more PRACH transmission opportunities based on the SIB1, and a receiver 30 that receives a random access preamble transmitted by the terminal device using one of the one or more PRACH transmission opportunities, wherein the controller 34 identifies the frequency resources of the one or more PRACH transmission opportunities based on the first offset information when the SIB1 does not include second offset information (msg1-FrequencyStart-rc), and identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information when the SIB1 includes second offset information.

[0203] (10) In a fourth aspect of the present invention, the offset information used for the first offset information and the second offset information may be information indicating, in the frequency domain, an offset value from a PRB having an index of 0 in an uplink BWP to a PRACH transmission opportunity with the lowest frequency among the one or more PRACH transmission opportunities.

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

[0205] A program running on an apparatus according to one aspect of the present invention may be a program that controls a central processing unit (CPU) or the like to cause a computer to function so as to realize the functions of an embodiment according to one aspect of the present invention. The program or information handled by the program is temporarily stored in a volatile memory such as a random access memory (RAM), a non-volatile memory such as a flash memory, a hard disk drive (HDD), or another storage device system.

[0206] A program for implementing the functions of an embodiment according to one aspect of the present invention may be recorded on a computer-readable recording medium. The program may be loaded into a computer system and executed. The term "computer system" as used herein refers to a computer system built into a device, including hardware such as an operating system and peripheral devices. The term "computer-readable recording medium" may refer to a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically stores a program for a short period of time, or any other computer-readable recording medium.

[0207] Additionally, each functional block or feature of the device used in the above-described embodiments may be implemented or performed by an electrical circuit, such as an integrated circuit or multiple integrated circuits. The 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, or a conventional processor, controller, microcontroller, or state machine. The electrical circuit may be composed of digital circuits or analog circuits. Furthermore, as advances in semiconductor technology emerge that replace current integrated circuits, one or more aspects of the present invention may also utilize new integrated circuits based on that technology.

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

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

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

[0211] One aspect of the present invention can be used, for example, in a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program.

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

Claims

1. A terminal device, comprising: a receiving unit that receives a System Information Block 1 (SIB1) including first offset information and receives a second system information block in which scheduling is determined based on the information included in the SIB1; a control unit that specifies frequency resources of one or more Physical Random Access Channel (PRACH) transmission opportunities; a transmission unit that transmits a random access preamble using one of the one or more PRACH transmission opportunities; wherein the control unit: when the second system information block does not include second offset information, specifies the frequency resources of the one or more PRACH transmission opportunities based on the first offset information; when the second system information block includes the second offset information, specifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information.

2. The terminal device according to claim 1, wherein the offset information used for the first offset information and the second offset information indicates an offset value from a Physical Resource Block (PRB) having an index of 0 in the uplink BWP to the lowest frequency PRACH transmission opportunity among the one or more PRACH transmission opportunities in the frequency domain.

3. A base station device, comprising: a transmission unit that transmits a System Information Block 1 (SIB1) including first offset information to a terminal device and transmits a second system information block in which scheduling is determined based on the information included in the SIB1; a control unit that specifies frequency resources of one or more Physical Random Access Channel (PRACH) transmission opportunities; a receiving unit that receives a random access preamble transmitted by the terminal device using one of the one or more PRACH transmission opportunities; wherein the control unit: When the second offset information is not included in the second system information block, identify the frequency resources of the one or more PRACH transmission opportunities based on the first offset information, A base station apparatus that, when the second offset information is included in the second system information block, identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information.

4. The offset information used for the first offset information and the second offset information is information indicating an offset value from a physical resource block (PRB) with an index of 0 in the uplink BWP to the lowest frequency PRACH transmission opportunity among the one or more PRACH transmission opportunities. The base station apparatus according to claim 3.

5. A communication method for a terminal device, Receive a system information block 1 (SIB1) including first offset information, and receive a second system information block whose scheduling is determined based on the information included in the SIB1, Identify the frequency resources of one or more physical random access channel (PRACH) transmission opportunities, Transmit a random access preamble using one of the one or more PRACH transmission opportunities, When the second offset information is not included in the second system information block, identify the frequency resources of the one or more PRACH transmission opportunities based on the first offset information, A communication method that, when the second offset information is included in the second system information block, identifies the frequency resources of the one or more PRACH transmission opportunities based on the second offset information.