Terminal device, base station device, and communication method

By employing a system information block and synchronization signal block with frequency domain offsets, the communication efficiency for REDCAP NR devices is enhanced, addressing the challenges of cost and battery life in wireless communication systems.

JP2024160194AInactive Publication Date: 2024-11-13SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2021160917
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2021-09-30
Publication Date
2024-11-13
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in efficiently supporting reduced capability (REDCAP) NR devices, particularly in scenarios requiring low cost and extended battery life, such as sensor networks and surveillance cameras, without compromising on communication efficiency.

Method used

The solution involves a terminal device and base station device that utilize a system information block and synchronization signal block with specified frequency positions, incorporating an offset in the frequency domain to enhance communication efficiency for REDCAP NR devices.

Benefits of technology

This approach enables efficient communication for REDCAP NR devices by optimizing frequency usage and reducing power consumption, thereby supporting low-cost and long-lasting devices in various applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024160194000001_ABST
    Figure 2024160194000001_ABST
Patent Text Reader

Abstract

To provide a terminal device, a base station device, and a communication method in which the terminal device and the base station device are synchronized to efficiently communicate with each other.SOLUTION: In a wireless communication system, a terminal device receives a system information block including first information in a first cell, identifies a frequency position of a synchronization signal block on the basis of the first information, and receives the synchronization signal block at the identified frequency position. The first information is information indicating an offset in the frequency domain from a first reference frequency position to the reference frequency position of the synchronization signal block.SELECTED DRAWING: Figure 8
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a terminal device, a base station device, and a communication method. [Background technology]

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

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

[0004] [Non-Patent Document 1] RP-161214, NTT DOCOMO, “Revision of SI: Study on New Radio Access Technology”, June 2016 [Non-Patent Document 2] RP-193238, Ericsson, “New SID on support of reduced capability NR devices”, December 2019 Summary of the Invention [Problem to be solved by the invention]

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

[0006] (1) In order to achieve the above object, the present invention provides the following means. That is, a terminal device according to one aspect of the present invention includes a receiver for receiving a system information block including first information in a first cell, and a frequency band for receiving a synchronization signal block based on the first information. and a control unit that identifies a wave number position, wherein the receiving unit receives the synchronization signal block at the identified frequency position, and the first information is information indicating an offset in the frequency domain from a first reference frequency position to the reference frequency position of the synchronization signal block.

[0007] (2) In addition, a base station device according to an aspect of the present invention includes: a control unit that generates first information; In a first cell, a system information block including the first information is transmitted, and a first frequency a transmitting unit that transmits a synchronization signal block at a first reference frequency position, the first frequency position being identified based on the first information, the first information being information indicating an offset in the frequency domain from a first reference frequency position to the reference frequency position of the synchronization signal block.

[0008] (3) In addition, a communication method according to one aspect of the present invention is a communication method of a base station device, which generates first information, and transmits a system information block including the first information in a first cell. and transmitting a synchronization signal block at a first frequency location, the first frequency location being The first information is determined based on information indicating an offset in the frequency domain from a first reference frequency position to the reference frequency position of the synchronization signal block. Effect of the Invention

[0009] According to the present invention, the terminal device and the base station device can communicate efficiently. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention. [Diagram 2] A figure showing an example of a schematic configuration of uplink and downlink slots according to an embodiment of the present invention. [Diagram 3] FIG. 2 is a diagram showing the relationship between subframes, slots, and minislots in the time domain according to an embodiment of the present invention. [Figure 4] A figure showing an example of an SS / PBCH block and SS burst set for an embodiment of the present invention. [Diagram 5] A diagram showing resources in which a PSS, an SSS, a PBCH and a DMRS for a PBCH are arranged within an SS / PBCH block according to an embodiment of the present invention. [Figure 6] FIG. 1 is a diagram illustrating an example of RF retuning according to an embodiment of the present invention. [Figure 7] A figure showing an example of the parameter configuration of the information element (IE) BWP-DownlinkCommon of the initialDownlinkBWP according to an embodiment of the present invention. [Figure 8]FIG. 2 is a diagram showing an overview of the frequency location of an additional synchronization signal block according to an embodiment of the present invention. [Figure 9] 1 is a flow diagram showing an example of a process relating to determining / specifying a frequency position of an additional synchronization signal block in a terminal device 1 according to an embodiment of the present invention. [Figure 10] 1 is a flow diagram showing an example of a process relating to determining / specifying a subcarrier interval of an additional synchronization signal block in a terminal device 1 according to an embodiment of the present invention. [Figure 11] 1 is a schematic block diagram showing a configuration of a terminal device 1 according to an embodiment of the present invention. [Figure 12] 1 is a schematic block diagram showing a configuration of a base station device 3 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[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), a 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 include 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 in 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 ranges (communication areas) controlled by one or more transmission / reception points 4. Furthermore, the base station device 3 may divide one cell into multiple partial areas (beamed areas) and serve the terminal device 1 in each partial area. Here, the partial area may be identified based on the index of the beam used in beamforming or the index of precoding.

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

[0015] In FIG. 1, in wireless communication between a terminal device 1 and a base station device 3, a cyclic prefix is ​​used. Alternatively, orthogonal frequency division multiplexing (OFDM) including a cyclic prefix (CP), single-carrier frequency division multiplexing (SC-FDM), or discrete Fourier transform spread OFDM (DFT-S-OFDM) may be used, or other transmission methods may be used.

[0016] In this embodiment, OFDM is used as the transmission method and OFDM symbols are used, but the present invention also includes cases where the above-mentioned other transmission methods are used.

[0017] In addition, in FIG. 1, the wireless communication between the terminal device 1 and the base station device 3 does not use a CP. Alternatively, the above-mentioned transmission method may be used in which zero padding is added instead of the CP. Also, the CP and / or zero padding may be added both in front and rear.

[0018] One aspect of the present embodiment is a wireless access technology (RAT) such as LTE, LTE-A, or LTE-A Pro. Carrier aggregation (CA) with LTE Access Technology (LTE) is operated in dual connectivity (DC) In this case, the SpCell may be used in some or all of the cells or cell groups, carriers or carrier groups (for example, 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, one aspect of the present embodiment may be used in a standalone manner that operates alone. In DC operation, the SpCell (Special Cell) is referred to as a PCell of an MCG or a PSCell of an SCG depending on whether the MAC (Medium Access Control) entity is associated with an MCG or an SCG, respectively. In the absence of DC operation, the SpCell (Special Cell) is referred to as a PCell. The SpCell (Special Cell) supports PUCCH transmission and contention based random access (CBRA).

[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 a serving cell where an initial connection establishment procedure has been performed, a serving cell where a connection re-establishment procedure has been started, or a cell designated as a primary cell in a handover procedure. One or more secondary cells may be configured at the time when an RRC (Radio Resource Control) connection is established or after that. 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 an uplink, among one or more secondary cells where the terminal device 1 is configured. In addition, a subset of two types of serving cells, an MCG and an SCG, may be configured for the terminal device 1. The MCG may be configured with one PCell and zero or more SCells. The SCG may be configured with one PScell ​​and zero or more SCells.

[0020] The wireless communication system of this embodiment is a TDD (Time Division Duplex) and / or FDD (Frequency Division Duplex) system. In the above, a frequency division duplex (FDD) scheme may be applied. A time division duplex (TDD) scheme or a frequency division duplex (FDD) scheme may be applied to all of the multiple cells. Furthermore, cells to which the TDD scheme is applied and cells to which the FDD scheme is applied may be aggregated. The TDD scheme may be referred to as an unpaired spectrum operation. The FDD scheme may be referred to as a paired spectrum operation.

[0021] The subframe will be described below. In this embodiment, the following 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 showing an example of a schematic configuration of uplink and downlink slots according to the first embodiment of the present invention. Each radio frame has a length of 10 ms. Each radio frame is made up of 10 subframes and W slots. One slot is made up of X OFDM symbols. In other words, the length of one subframe is 1 ms. For example, if the subcarrier spacing of the OFDM symbol is 15 kHz and NCP (Normal Cyclic Prefix) is used, the time length of each bit is defined by the subcarrier spacing. , which are 0.5 ms and 1 ms, respectively. Also, when the subcarrier spacing is 60 kHz, X=7 or X=14, which are 0.125 ms and 0.25 ms, respectively. Also, for example, when X=14, When the subcarrier spacing is 15 kHz, W=10, and when the subcarrier spacing is 60 kHz, W=40. Figure 2 shows an example where X=7. Note that the example in Figure 2 is for the case where X=14. can be expanded in the same way. The uplink slot is also defined in the same way, and the downlink slot and the uplink slot may be defined separately. Also, the bandwidth of the cell in FIG. 2 is a partial bandwidth. However, the BWP used in the downlink may be called the downlink BWP, and the BWP used in the uplink may be called the uplink BWP. A slot may also be defined as a Transmission Time Interval (TTI). A slot does not have to be defined as a TTI, which may be a 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 carriers depends on the downlink and uplink bandwidths of the cell, respectively. Each element in the resource grid is called a resource element (RE). An RE may be identified by a subcarrier number and an OFDM symbol number.

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

[0025] As the RB, a reference resource block (reference RB), a common resource block (CRB: Common RB), a PRB, and a virtual resource block (VRB: Virtual RB) are defined. One RB is defined as 12 consecutive subcarriers in the frequency domain. The reference resource block is common to all subcarriers, and may constitute a resource block at a subcarrier interval of, for example, 15 kHz, and may be numbered in ascending order. Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (or simply referred to as a "reference point"). Point A may be provided as a common reference point for the grid of resource blocks. The position of point A may be determined / specified by a parameter offsetToPointA included in SIB1. The parameter offsetToPointA is a parameter indicating a frequency offset between point A and the lowest frequency subcarrier of the lowest frequency resource block that overlaps with the synchronization signal block used by the terminal device 1 in the initial cell selection. However, the unit of the frequency offset is a resource block with a subcarrier spacing of 15 kHz in the case of frequency range (FR) 1, and a resource block with a subcarrier spacing of 60 kHz in the case of frequency range 2. However, the position of point A may be indicated by the frequency position ARFCN (Absolute radio-frequency channel number) by the RRC parameter absoluteFrequencyPointA. The CRBs are RBs numbered in ascending order from 0 in each subcarrier spacing setting μ from point A. Therefore, the number of the CRB is defined for each subcarrier spacing setting μ. The CRB corresponding to the subcarrier spacing setting μ may be referred to as CRB μ. The above-mentioned resource grid is defined by the CRB. However, the center of subcarrier index 0 of CRB μ numbered 0 in each subcarrier spacing setting μ is point A.A PRB is an RB numbered in ascending order starting from 0 included in a BWP of each subcarrier spacing setting μ, and a PRB is an RB numbered in ascending order starting from 0 included in a BWP that is a subcarrier spacing setting μ. A PRB corresponding to a subcarrier spacing setting μ may be referred to as a PRB μ. A physical uplink channel is first mapped to a VRB. Then, the VRB is mapped to a PRB. Hereinafter, an RB may be a VRB, a PRB, a CRB, or a reference resource block.

[0026] A BWP is a subset of consecutive RBs (which may be CRBs) 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. The active downlink BWP at a certain time (active The terminal device 1 may not expect to receive a PDSCH, a PDCCH, or a CSI-RS outside the band of the active downlink BWP. The terminal device 1 may be configured with up to four BWPs (uplink BWPs) in the uplink. At any given time, there may be only one active uplink BWP (active uplink BWP). The terminal device 1 does not transmit PUSCH and PUCCH outside the band of the active uplink BWP.

[0027] Next, we will explain the subcarrier spacing setting μ. As mentioned above, in NR, one or more Several OFDM numerologies are supported. The packet interval setting μ (μ=0,1,...,5) and the CP length are given by higher layers for the downlink BWP. , is given by higher layers in the uplink BWP. Here, given μ, The rear spacing Δf is given by Δf = 2^μ·15 (kHz).

[0028] In the subcarrier spacing setting μ, slots are numbered from 0 to N^{subframe, μ}_{slot}-1 in ascending order within a subframe, and from 0 to N^{frame, μ}_{slot}-1 in ascending order within a frame. Based on the slot setting and CP, N^{slot}_{symb} consecutive OFDM symbols are obtained. In the slot, N^{slot}_{symb} is 14. In the slot n^{μ}_{s} in the subframe The start of 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. This figure shows an example of the relationship between a subframe, a slot, and a minislot 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 interval, and the number of OFDM symbols included in a slot is 7 or 14 (however, each symbol (If the CP added to the subframe is an 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. The downlink slot may be referred to as PDSCH mapping type A. The uplink slot 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 a number of OFDM symbols fewer than the number of OFDM symbols contained in one slot. The figure shows an example in which a minislot consists of two OFDM symbols. The OFDM symbols in a slot may coincide with the OFDM symbol timing constituting the slot. The minimum unit of scheduling may be a slot or a minislot. Allocating a minislot may be referred to as non-slot based scheduling. Scheduling a minislot may be expressed as scheduling a resource in which the relative time positions of the start positions of the reference signal and data are fixed. A downlink minislot may be referred to as PDSCH mapping type B. An uplink minislot may be referred to as PUSCH mapping type B.

[0031] In the terminal device 1, the transmission direction of the symbol in each slot (uplink, downlink, The DCI format (uplink, downlink, or flexible) is set in a higher layer by using an RRC message including a predetermined higher layer parameter 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 each symbol in a slot to either uplink, downlink, or flexible is called a slot format. One slot format may include a downlink symbol, an uplink symbol, and a flexible symbol.

[0032] In this embodiment, the carrier corresponding to the serving cell is called a Component Carrier (CC) (or carrier). In this embodiment, in the downlink, the carrier corresponding to the serving cell is called a downlink CC (or downlink carrier). In this embodiment, in the uplink, the carrier corresponding to the serving cell is called an uplink CC (or uplink carrier). In this embodiment, in the sidelink, the carrier corresponding to the serving cell is called a sidelink CC (or sidelink carrier).

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

[0034] In FIG. 1, the following physical channels are used in wireless communication between the terminal device 1 and the base station device 3: It is okay to do so.

[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 a Master Information Block (MIB) that contains important system information required by the terminal device 1. It is used to broadcast the PBCH (Essential Information Block, Essential Information Block, Broadcast Channel). The MIB contains the radio frame (system information for identifying the System Frame Number (SFN), information for identifying the subcarrier spacing of the System Information Block 1 (SIB1), information for identifying the resource block grid and the SS / PBCH block (also called synchronization signal block, SS block, SSB) The SIB1 may include information indicating the setting of the PDCCH for the SIB1. , which contains information necessary for evaluating whether the terminal device 1 is allowed to connect to the cell, Information that determines the scheduling of other system information blocks (SIBs) However, the information indicating the PDCCH configuration for SIB1 includes the control resource set CORESET (Control Resource Set) 0 (CORESET0 is also called CORESET#0 or common CORESET), which is information for determining a common search space and / or necessary PDCCH parameters. Here, CORESET indicates a resource element of a PDCCH and is composed of a set of PRBs in a time period of a certain number of OFDM symbols (for example, 1 to 3 symbols). CORESET0 may be a CORESET for a PDCCH that schedules at least SIB1. CORESET0 is set in the MIB. SIB1 may be transmitted in CORESET0 or may be configured via RRC signaling. The terminal device 1 may be scheduled by the PDCCH received in CORESET0. Receive the SIB1 that was assigned to the

[0037] The PBCH may be used to broadcast information for identifying the number (SFN: System Frame Number) of the radio frame (also called a system frame) to which the PBCH is mapped and / or information for identifying a half radio frame (HRF: Half Radio Frame) (also called a half frame). 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 is also used to broadcast the time index within the period of the SS / PBCH block. Here, the time index is information indicating the index of the synchronization signal and the PBCH in the cell. The time index may be referred to as an SSB index or an SS / PBCH block index. For example, the SS / PBCH may be determined by using a quasi-co-location (QCL) assumption for multiple transmit beams, transmit filter settings, and / or receive spatial parameters. When transmitting the blocks, the time order within a predefined or set period may be indicated, and the terminal device may recognize the difference in time index as different QCL assumptions regarding transmit beams, transmit filter settings and / or receive spatial parameters.

[0039] The PDCCH is used in downlink wireless communication (wireless communication from the base station device 3 to the terminal device 1). , transmit (or carry) Downlink Control Information (DCI) ) is used. Here, one or more DCIs (which may be referred to as DCI formats) are defined for the transmission of downlink control information. That is, a field for downlink control information is defined as DCI and mapped to information bits. PDCCH is transmitted in PDCCH candidates. The terminal device 1 monitors a set of PDCCH candidates in the serving cell. However, monitoring may mean attempting to decode 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 is for scheduling PUSCH in a serving cell. DCI format 0_0 may be used for PUSCH scheduling information (frequency domain The DCI information may include information indicating the DCI domain resource allocation (domain resource allocation and time domain resource allocation). The DCI format 0_0 may be added with a Cyclic Redundancy Check (CRC) scrambled by any one of the Radio Network Temporary Identifiers (RNTIs), which are identifiers, Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI, MCS-C-RNTI, and / or Temporary C-RNTI (TC-RNTI). The DCI format 0_0 may be monitored in a common search space or a UE-specific search space.

[0042] DCI format 0_1 ​​is for scheduling PUSCH in a serving cell. DCI format 0_1 ​​may be used for scheduling information of PUSCH (frequency domain information indicating BWP, The DCI format 0_1 ​​may include a Channel State Information (CSI) request, a Sounding Reference Signal (SRS) request, and / or information on an antenna port. A CRC scrambled by any one of C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and / or MCS-C-RNTI among RNTIs may be added to the DCI format 0_1. The DCI format 0_1 ​​may be monitored in a UE-specific search space.

[0043] DCI format 0_2 is for scheduling PUSCH in a serving cell. DCI format 0_2 may be used for PUSCH scheduling information (frequency domain The information may include information indicating the BWP, a CSI request, an SRS request, and / or information regarding antenna ports. DCI format 0_2 uses the C-RNTI, CSI-RNTI, SP-CSI-RNTI, and / or A CRC scrambled by any of the MCS-C-RNTIs may be added to the DCI format 0_2. The DCI format 0_2 may be monitored in a UE-specific search space. may be referred to as DCI format 0_1A, etc.

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

[0045] DCI format 1_1 is for scheduling PDSCH in a serving cell. DCI format 1_1 may be used for PDSCH scheduling information (frequency domain information indicating BWP, information indicating transmission The DCI format 1_1 may include a transmission configuration indication (TCI) and / or information about an antenna port. A CRC scrambled by any one of the C-RNTI, CS-RNTI, and / or MCS-C-RNTI among the RNTIs may be added to the DCI format 1_1. The DCI format 1_1 may be monitored in a UE-specific search space.

[0046] DCI format 1_2 is for scheduling PDSCH in a serving cell. DCI format 1_2 may be used for PDSCH scheduling information (frequency domain DCI format 1_2 may include information indicating a UE-specific search space (domain resource allocation and time domain resource allocation), information indicating a BWP, a TCI, and / or information regarding 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 notify the slot format of one or more slots. The slot format is defined as a classification of each OFDM symbol in a slot as either downlink, flexible, or uplink. For example, when the slot format is 28, DDDDDDDDDDDDFU is applied to 14 OFDM symbols in a slot in which slot format 28 is specified. Here, D is a downlink symbol, F is a flexible symbol, and U is an uplink symbol. Slots will be described later.

[0048] The DCI format 2_1 is used to notify the terminal device 1 of the PRBs (or RBs) and OFDM symbols for which no transmission may be assumed. Note that this information may be called a preemption instruction (discontinuous transmission instruction).

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

[0050] The DCI format 2_3 is a format for transmitting a sounding reference signal (SRS) by one or more terminal devices 1. In addition, an SRS request may be transmitted together with the TPC command. In addition, in DCI format 2_3, an uplink without PUSCH and PUCCH, or an SRS transmission power control is linked to a PUSCH transmission power control, For the uplink where no SRS is present, SRS requests and TPC commands may be defined.

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

[0052] The CRC parity bits added to the DCI format transmitted on one PDCCH are 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 the terminal device 1 that transmitted the random access preamble during CBRA.

[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 given MCS table for grant-based transmission. The TC-RNTI is used to control the PDSCH or PUSCH transmission in one or more slots. The TC-RNTI is used to schedule the retransmission 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] The C-RNTI and / or other RNTIs may have different values ​​corresponding to the type of traffic of the PDSCH or PUSCH. The C-RNTI and other RNTIs correspond to the service type (eMBB, URLLC, and / or mMTC) of the data transmitted on the PDSCH or PUSCH. The base station device 3 may use a different value according to the service type of the 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 in uplink wireless communication (wireless communication from the terminal device 1 to the base station device 3). Used to transmit Uplink Control Information (UCI) Here, the uplink control information may include channel state information (CSI) used to indicate the state of a downlink channel. The uplink control information may also include a scheduling request (SR) used to request a UL-SCH resource. The uplink control information may also include a hybrid automatic repeat request ACKnowledgement (HARQ-ACK). is the downlink data (Transport block, Medium Access Control Protocol Data Unit: It may also indicate a HARQ-ACK for a MAC PDU, a 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: System Information) and random access response (RAR: Random Access Response) in the downlink.

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

[0059] The PDSCH or the PUSCH may be used to transmit RRC signaling and MAC control elements. may be common signaling for multiple terminal devices 1 in a cell. The RRC signaling transmitted from the base station device 3 is a signaling dedicated to a certain terminal device 1. In other words, terminal device specific information may be transmitted using dedicated signaling to a certain terminal device 1. In addition, the PUSCH may be used to transmit UE capabilities in the uplink.

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

[0061] The synchronization signal is the Primary Synchronization Signal (PSS) and the Sector Synchronization Signal (SES). 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 be called 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. The reference signal may also be used by the terminal device 1 to calculate the downlink CSI. The reference signal may also be used to calculate the downlink CSI, such as radio parameters, numerology such as subcarrier spacing, window synchronization of FFT, etc. This may be used for fine synchronization where

[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] DMRS is used to demodulate a modulated signal. Two types of DMRS may be defined: a reference signal for demodulating the PBCH and a reference signal for demodulating the PDSCH, and both may be called DMRS. CSI-RS is Channel State Information (CSI) The CSI-RS is used for measurement and beam management, and a periodic, semi-persistent, or aperiodic CSI reference signal transmission method is applied. For the CSI-RS, a non-zero power (NZP) CSI-RS and a zero power (ZP) CSI-RS with zero transmission power (or zero reception power) may be defined. 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 the frequency offset caused by phase noise. The TRS is used to compensate for the Doppler shift during high-speed movement. Note that the TRS may be used as one setting of the CSI-RS. For example, the radio resources may be set as the TRS for the CSI-RS of one port.

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

[0067] The DMRS is used to demodulate the modulated signal. Note that the DMRS includes Two types of reference signals may be defined: a reference signal for demodulating the PUSCH and a reference signal for demodulating the PUSCH, and both may be referred to as DMRS. The SRS is used for uplink Channel State Information (CSI) measurement, channel sounding, and beam management. The PTRS is used to track the phase in time to compensate for frequency offsets caused by phase noise.

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

[0069] BCH, UL-SCH and DL-SCH are transport channels. A channel used in the Medium Access Control (MAC) layer is called a transport channel. A 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] FIG. 4 shows the SS / PBCH block (also called the synchronization signal block, SS block, or SSB) according to this embodiment. FIG. 1 shows an example of a half frame (also referred to as a half frame with SS / PBCH block or SS burst set) in which one or more SS / PBCH blocks are transmitted. 4 shows an example in which two SS / PBCH blocks are included in an SS burst set that exists at a fixed period (which may be referred to as an SSB period), and the SS / PBCH block is composed of four consecutive OFDM symbols.

[0071] The SS / PBCH block is a block that contains the synchronization signals (PSS, SSS), the PBCH, and the DMRS for the PBCH. However, the SS / PBCH block may 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 the SS / PBCH block is expressed as transmitting the SS / PBCH block. In the case where one or more SS / PBCH blocks in an SS burst set are used to transmit a synchronization signal and / or a PBCH, an independent downlink transmission beam is used for each SS / PBCH block. It's fine.

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

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

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

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

[0076] Different SS / PBCH blocks in an SS burst set may be assigned different SSB indices. For example, the SS / PBCH block may be transmitted periodically based on the SSB period for which it is used for initial access and the SSB period for which it is connected (Connected or RRC_Connected). An SSB period to be set for the terminal device 1 may be defined. Also, the SSB period to be set for a connected (Connected or RRC_Connected) terminal device 1 may be set by an RRC parameter. Also, the SSB period to be set for a connected (Connected or RRC_Connected) terminal device 1 is a period of radio resources in the time domain that may potentially be transmitted, and the base station device 3 may actually decide whether to transmit or not. Also, the SSB period for which the SS / PBCH block is used for initial access may be defined in advance 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 is the time position contained in the PBCH. The SS / PBCH block may be determined based on information for determining a system frame number (SFN) and / or information for determining a half frame. Device 1 may determine the current system frame number and half frame based on the received SS / PBCH block.

[0078] The SS / PBCH block is assigned an SSB index (which may be referred to as an SS / PBCH block index) according to its time 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 the multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to average delay, Doppler shift, and spatial correlation.

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

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

[0082] SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assigned the same SSB index. SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL (or to have the same downlink transmit beam). Additionally, antenna ports with SS / PBCH blocks with the same relative time within each SS burst set in the multiple SS burst sets may be assumed to be QCL with respect to average 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 is in a certain cell, and is in a connected state and has a predetermined timer running. Based on the state, the information of the received MIB, and / or the information of the received SIB (which may be SIB1), it is determined whether to consider the cell as a "barred" cell. 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 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 (if the cell status is "not barred"), the terminal device 1 In this case, the cell may be treated as a candidate cell for cell selection and cell reselection.

[0086] When a cell is a barred cell (when the cell status is indicated as “barred”), the terminal device 1 When the terminal device 1 is in a state where a cell is not selected or the cell status is treated as being “barred”, the terminal device 1 is prohibited from selecting or reselecting the cell, and selects another cell. If the cell is a restricted cell, the terminal device 1 may select / reselect another cell based on the MIB. For example, if 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 treat them as candidates for reselection. It's okay if not.

[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 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. Note that timer T311 is a timer that is executed during a procedure for reestablishing an RRC connection, and when the timer expires, the terminal device 1 sets the connection state to the RRC idle state.

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

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

[0090] The base station device 3 according to this embodiment is configured to receive the following signal from the terminal device 1 in the cell in which the terminal device 1 is located: Transmit SIB1 (or any other SIB) containing parameters for determining whether the cell is barred or not.

[0091] The initial BWP, the initial downlink BWP, and the The initial uplink BWP (initial UL BWP) 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, initial downlink BWP and initial uplink BWP may be used after the RRC connection is established. However, the initial BWP, initial downlink BWP and initial uplink BWP are The BWPs may be BWPs with an index of 0 (#0), downlink BWPs, and uplink BWPs.

[0092] The initial downlink BWP is based on the parameters provided in the MIB, the parameters provided in SIB1, and the SI The initial downlink BWP may be set by a parameter provided in SIB1 and / or an RRC parameter. For example, the initial downlink BWP may be set by a parameter initialDownlinkBWP provided in SIB1. However, the initialDownlinkBWP may be a parameter indicating a UE-specific (dedicated) setting of the initial downlink BWP for a UE.

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

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

[0095] The initialDownlinkBWP includes a BWP information element, a PDCCH configuration information element, and / or a PDSCH configuration information element in 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 includes frequencyBandList, which indicates a list of one or more frequency bands to which the downlink carrier belongs, and 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 is a parameter that indicates the actual carrier position, bandwidth, and carrier bandwidth. More specifically, an information element SCS-SpecificCarrier in frequencyInfoDL indicates a setting for a specific carrier, and includes subcarrierSpacing, carrierbandwidth, and / or offsetToCarrier. subcarrierSpacing is a parameter indicating the subcarrier spacing of the carrier (for example, 15 kHz or 30 kHz in FR1, and 60 kHz or 120 kHz in FR2). carrierbandwidth is a parameter indicating the bandwidth of the carrier in terms of the number of PRBs (Physical Resource Blocks). offsetToCarrier is a parameter indicating the offset in the frequency domain between reference point A (the lowest subcarrier of common RB0) and the lowest usable subcarrier of the carrier in terms of the number of PRBs (where the subcarrier spacing is the subcarrier spacing of the carrier given by subcarrierSpacing). For example, for a downlink carrier, the carrier bandwidth is given by the higher layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval, and the start position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval. For example, for an uplink carrier, the carrier bandwidth is given by the higher layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval, and the start position on the frequency is given by the parameter offsetToCarrier in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval.

[0098] The 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 (total number). However, the information indicating the maximum allocated bandwidth may be set for each subcarrier spacing. The information indicating the maximum allocated bandwidth is the parameter subcarrierSpacing indicating the subcarrier spacing and the resource block number of the bandwidth. The number of locks may be indicated by an information element including a parameter allocationBandwidth. The allocated bandwidth may be the maximum bandwidth supported by the RF circuit of the terminal device 1. The large bandwidth may be the maximum bandwidth in which signals / channels transmitted in the downlink and / or the uplink can be scheduled simultaneously. When signals / channels are scheduled discretely on the frequency in the downlink and / or the uplink, the maximum allocated bandwidth may be the bandwidth of frequency resources in which the signals / channels can be discretely arranged 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 the allocationBandwidth includes the parameter. The information indicating the maximum allocated bandwidth may be information specifying the maximum allocated bandwidth by a ratio value with respect to the carrier bandwidth notified by the SCS-SpecificCarrier.

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

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

[0102] When the initialDownlinkBWP is not provided in the SIB1 (or may be another SIB or an RRC parameter) received by the terminal device 1, the initial downlink BWP may be determined / specified 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 (Physical Resource Blocks) of the CORESET (CORESET0, etc.) 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 the SIB1 received by the terminal device 1, the initial downlink BWP may be determined / specified by the initialDownlinkBWP.

[0103] However, the initialDownlinkBWP being provided may be a state in which the initialDownlinkBWP is received in the RRC parameters and the RRC connection is established (for example, RRCSetup, RRCResume, and / or RRCReestablishment are received). For example, when the terminal device 1 receives the initialDownlinkBWP in the 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 specifies the initial downlink BWP by CORESET0 until the RRC connection is established, and after the RRC connection is established, the terminal device 1 specifies the initial downlink BWP by the locationAndBandwidth included in the initialDownlinkBWP. The ISP may determine / identify the link BWP.

[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] 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] The 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). When the RRC connection with the terminal device 1 is re-established, the RRCReestablishment message may be transmitted to the terminal device 1.

[0107] The initial uplink BWP may be configured by a parameter provided in the MIB, a parameter provided in SIB1, a parameter provided in the SIB, or an RRC parameter. For example, the initial uplink BWP may be configured by a parameter initialUplinkBWP provided in SIB1. Here, 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 / set by the initialUplinkBWP provided in SIB1 (which may be REDCAP SIB1, other SIBs, or RRC parameters). 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 antenna and a signal processing unit that processes a baseband signal. An RF circuit is provided between the receiver and the receiver. The RF circuit mainly includes a signal processor, a power amplifier, an antenna switch, a filter, etc. When receiving a signal, the signal processor of the RF circuit The RF circuit demodulates the received RF signal and outputs the received signal to the signal processing unit. When transmitting a signal, the high-frequency signal processing unit of the RF circuit modulates the carrier signal, generates an RF signal, amplifies the power in the power amplifier, and outputs it to the antenna. The antenna switch connects the antenna and filter when receiving a signal, and connects the antenna and 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 of the terminal device 1 (which may be referred to as an allocated bandwidth), the terminal device 1 The frequency band to which the circuit is applied may be tuned / retuned. Adjusting / re-adjusting the frequency band to be used 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 applicable band of the RF circuit used in the terminal device 1 is outside the band of the downlink channel received in the initial downlink BWP, the terminal device 1 performs RF retuning so as to include the band of the downlink channel to receive the applicable band of the RF circuit. 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 / re-adjust the frequency band to be used by the RF circuit in 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 / re-adjust the frequency band to be used by the RF circuit in the downlink BWP. If the bandwidth of the set initial uplink BWP is wider than the bandwidth supported by the RF circuit of 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 a plurality of initial downlink sub-BWPs by the SIB1. At least one of the plurality of initial downlink sub-BWPs may be configured to include an SS / PBCH block. The terminal device 1 may operate by regarding an initial downlink sub-BWP including an SS / PBCH block (such as a cell-defining SSB) as an initial downlink BWP. At least one of the plurality of initial downlink sub-BWPs may be configured to include CORESET0. All of the plurality of initial downlink sub-BWPs may be configured to include their respective CORESET0. The terminal device 1 may operate by regarding an initial downlink sub-BWP including CORESET0 as an initial downlink BWP. The terminal device 1 may operate by regarding an initial downlink sub-BWP as an initial downlink BWP. The plurality of initial downlink sub-BWPs may be considered as a plurality of initial downlink BWPs. The plurality of initial downlink sub-BWPs may be designed to be included in a 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, "an initial downlink BWP is set / specified" may mean that a frequency position and / or a bandwidth of the initial downlink BWP is set / specified. However, for the terminal device 1, "multiple initial downlink BWPs are set / specified" may mean that multiple frequency positions and / or multiple bandwidths of the initial downlink BWP are set / specified. The base station device 3 may broadcast information including the setting of multiple frequency positions and / or multiple bandwidths of the initial downlink BWP, and the terminal device 1 may determine / specify / set the frequency position and bandwidth of the initial downlink BWP based on the information. .

[0112] The terminal device 1 according to the present invention performs the initial downlink transmission using the upper layer parameter initialDownlinkBWP. Receive / specify the configuration information for the initialDownlinkBWP. However, the initialDownlinkBWP may be included in SIB1. Alternatively, the initial downlink BWP configuration information may be included in any RRC message. For example, the initial downlink BWP configuration information may include information indicating a frequency location and a bandwidth of the initial downlink BWP. The terminal device 1 may receive the SIB1 including multiple pieces of configuration information of the initial downlink BWP or any RRC signaling. Multiple pieces of configuration information of the initial downlink BWP may be included in one parameter initialDownlinkBWP.

[0113] FIG. 7 shows the parameters of the information element (IE) BWP-DownlinkCommon of the initialDownlinkBWP according to this embodiment. 1 shows an example of a parameter configuration. The initialDownlinkBWP according to this embodiment may include generic parameters genericParameters of the initial downlink BWP, cell-specific parameters pdcch-ConfigCommon of the PDCCH, cell-specific parameters pdsch-ConfigCommon of the PDSCH, a parameter indicating second configuration information of the initial downlink BWP, and / or a parameter initialBwpTiming indicating a 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 indicating a second "frequency location and bandwidth" of the initial downlink BWP. However, the initial downlink BWP determined / specified by locationAndBandwidth-rc may be referred to as a separate initial downlink BWP (separate initial DL BWP / separated initial DL BWP) in distinction from the initial downlink BWP determined / specified by locationAndBandwidth. When multiple initial downlink BWPs are configured in a certain cell (or when multiple frequency locations and / or multiple bandwidths for the initial downlink BWP are broadcast in a certain cell), some of the information included in genericParameters in initialDownlinkBWP may be parameters common to the multiple initial downlink BWPs (or multiple frequency locations and / or multiple bandwidths for the initial downlink BWP). However, the parameter locationAndBandwidth-rc indicating the second "frequency location and bandwidth" of the initial downlink BWP may be included in any information element / parameter in SIB1. However, the parameter locationAndBandwidth-rc indicating the second "frequency location and bandwidth" of the initial downlink BWP may be included in any information element / parameter in other SIBs.Hereinafter, in this embodiment, the parameter locationAndBandwidth-rc will be described as a parameter included in the initialDownlinkBWP, but the same function can be realized when it is included in SIB1, other SIBs, or other information elements / parameters in RRC signaling. For example, locationAndBandwidth-rc may be a parameter included in the parameter separateInitialDownlinkBWP. separateInitialDownlinkBWP may be a parameter transmitted in SIB1. separateInitialDownlinkBWP may be a parameter transmitted in an SIB other than SIB1. separateInitialDownlinkBWP may be a parameter transmitted in RRC signaling. separateInitialDownlinkBWP may be a parameter including configuration information of the second initial downlink BWP (which may be a separate initial downlink BWP) identified by locationAndBandwidth-rc. separateInitialDownlinkBWP may be a parameter including part or all of the parameter configuration of initialDownlinkBWP, and each parameter may be configuration information for a second initial downlink BWP (which may be a separate initial downlink BWP) identified by locationAndBandwidth-rc.

[0114] The genericParameters included in the initialDownlinkBWP is composed of the information element (IE) BWP, and includes the parameters locationAndBandwidth, which indicate the frequency location and bandwidth of the initial downlink BWP, This indicates the subcarrier spacing used for all channels and reference signals in the forward link bandwidth planning (BWP). The initialDownlinkBWP includes a parameter subcarrierSpacing indicating whether an extended cyclic prefix (CP) is used 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 locations and bandwidths" of the initial downlink BWP are configured in a certain cell, the subcarrierSpacing included in the genericParameters in the initialDownlinkBWP may be a parameter indicating the subcarrier spacing used in all channels and reference signals in the initial downlink BWP configured in the first "frequency location and bandwidth", or may be a parameter indicating the subcarrier spacing used in all channels and reference signals in common to the initial downlink BWP configured in different "frequency locations and bandwidths". 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 the subcarrierSpacing included in the genericParameters in the initialDownlinkBWP, regardless of whether the SIB1 (which may be another SIB or RRC signaling) includes the setting information (locationAndBandwidth-rc) of the second "frequency location and bandwidth". However, when multiple "frequency locations and bandwidths" 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 in 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 in different "frequency locations and bandwidths".For example, the terminal device 1 may determine / identify 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 SIB1 (which may be another SIB or RRC signaling) includes or does not include the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0115] The value indicated by locationAndBandwidth included in the genericParameters 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 (total number) of consecutive resource blocks, and the frequency position and bandwidth of the initial downlink BWP can be specified by the value of the 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. When 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 indicating multiple "frequency positions and bandwidths" for the initial downlink BWP (locationAndBandwidth and locationAndBandwidth-rc) are the frequency location and / or The information may be information for setting multiple initial downlink BWPs with different bandwidths. The parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating a plurality of "frequency locations and bandwidths" for the initial downlink BWP may be information indicating a plurality of "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 generic parameters by configuring it so that it is not included in the genericParameters in the initialDownlinkBWP, which is the generic parameter of the initial downlink, but the locationAndBandwidth-rc may also be configured to be included in the genericParameters in the initialDownlinkBWP.

[0118] However, in the present invention, the initial downlink link set by the parameter locationAndBandwidth-rc is The separate initial downlink BWP may be called a separate initial downlink BWP to distinguish it from the initial downlink BWP set in the MIB or the parameter locationAndBandwidth.

[0119] The pdcch-ConfigCommon included in the initialDownlinkBWP may include the parameter controlResourceSetZero of CORESET0 used in the common search space or UE-specific search space, the parameter commonControlResourceSet of an additional common CORESET used in the common search space or UE-specific search space, the parameter searchSpaceZero of 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.

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

[0121] Terminal device 1 changes from controlResourceSetZero in pdcch-ConfigCommon to CORESET0. The terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols of the SS / PBCH block and the CORESET0. 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 repetitions of PDCCH.

[0122] The multiplexing pattern of PBCH and CORESET corresponds to the SS / PBCH block corresponding to the PBCH in which the MIB is detected. The frequency / time position relationship pattern of CORESET0 corresponding to the PBCH is shown. When the multiplexing pattern is 1, the PBCH and CORESET are time-multiplexed in different symbols.

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

[0124] The offset is the number of RBs from the lowest RB index of the resource blocks assigned to CORESET0 to the common resource block with which the first resource block of the corresponding REDCAP PBCH overlaps. Indicates the offset to the lowest RB index, where the offset is from the lowest RB index of the resource blocks assigned to CORESET0 to the highest RB index of the corresponding SS / PBCH block. The first resource block may indicate an offset to the lowest RB index of the overlapping common resource block.

[0125] The terminal device 1 receives the initialDownlinkBWP including the RRC parameter pdcch-ConfigCommon via SIB1 or RRC signaling, and monitors the PDCCH based on the parameter.

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

[0127] The terminal device 1 performs a type 0-PDCCH common search over two consecutive slots starting from slot n0. The terminal device 1 monitors the PDCCH with the space set (Type0-PDCCH CSS Set). In the SS / PBCH block with column i, n0 and the system frame number are determined based on the parameters O and M shown in the table.

[0128] Indicates multiple "frequency locations and bandwidths" for the initial downlink BWP in a cell. When the parameters (locationAndBandwidth and locationAndBandwidth-rc in initialDownlinkBWP) are set (multiple initial downlink BWPs may be set 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 an initial downlink BWP set at a first "frequency location and bandwidth", or may be a cell-specific parameter of a PDCCH that is common to initial downlink BWPs set at 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 SIB1 (which may be another SIB or RRC signaling) includes or does not include the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

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

[0130] Indicates multiple "frequency locations and bandwidths" for the initial downlink BWP in a cell. When the parameters (locationAndBandwidth and locationAndBandwidth-rc in initialDownlinkBWP) are set (multiple initial downlink BWPs may be set 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 set at a first "frequency position and bandwidth", or may be a cell-specific parameter of a PDSCH that is common to initial downlink BWPs set at different "frequency positions 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 SIB1 (which may be another SIB or RRC signaling) includes or does not include the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc).

[0131] The value indicated by locationAndBandwidth-rc is interpreted as a Resource Indicator Value (RIV). The RIV is an index indicating the start position of a resource block and the number (total number) of consecutive resource blocks, and the frequency location and bandwidth of the second initial downlink BWP (which may be a separate initial downlink BWP) can be specified by the value of the index.

[0132] When locationAndBandwidth-rc is not included in SIB1 (which may be another SIB or RRC signaling), 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 SIB1 (which may be another SIB or RRC signaling), the terminal device 1 may identify / determine the frequency location and bandwidth of the initial downlink BWP based on the locationAndBandwidth-rc.

[0133] A terminal device 1 that does not support the frequency location and / or bandwidth of the first initial downlink BWP can receive a downlink channel and a downlink signal transmitted from a base station device 3 by identifying / determining a second initial downlink BWP from the locationAndBandwidth-rc included in SIB1 (which may be another SIB or RRC signaling).

[0134] When the base station device 3 sets the initial downlink BWP of the frequency position and / or bandwidth not supported by a specific terminal device 1 by locationAndBandwidth, the base station device 3 can appropriately transmit the downlink channel and the downlink signal by setting the initial downlink BWP of the frequency position and / or bandwidth supported by the terminal device 1 by locationAndBandwidth-rc. By including locationAndBandwidth-rc in SIB1 (which may be another SIB or RRC signaling), the base station device 3 can transmit the downlink channel and the reference signal corresponding to the second initial downlink BWP to the terminal device 1 that does not support the frequency position and / or bandwidth of the first initial downlink BWP, and transmit the downlink channel and the reference signal corresponding to the first initial downlink BWP to the terminal device 1 that supports the frequency position and bandwidth of the first initial downlink BWP. When the base station device 3 sets the initial downlink BWP of the frequency location and / or bandwidth supported by all terminal devices 1 using locationAndBandwidth in initialDownlinkBWP, it does not need to include locationAndBandwidth-rc in SIB1 (which may be another SIB or RRC signaling).

[0135] The terminal device 1 may specify / determine a subcarrier spacing used in 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 SIB1 (which may be another SIB or RRC signaling).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 SIB1 (which may be another SIB or RRC signaling).

[0136] 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 SIB1 (which may be another SIB or RRC signaling), 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 SIB1 (which may be another SIB or RRC signaling), and receive the PDSCH.

[0137] The terminal device 1 receives locationAndBandwidth-rc included in SIB1 (or another SIB), and determines an initial downlink BWP (separate initial When identifying / determining the frequency location and bandwidth of the downlink BWP (which may be referred to as the downlink BWP), CORESET0 is the initial downlink BWP until the RRC connection is established, re-established or resumed (e.g., 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 (or other SIB). 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 the random access procedure using the initial downlink BWP determined / specified in CORESET0.

[0138] The terminal device 1 receives locationAndBandwidth-rc included in SIB1 (or another SIB), and determines an initial downlink BWP (separate initial When identifying / determining the frequency location and bandwidth of the downlink BWP, the SIB1 is Until reception, CORESET0 is set as the initial downlink BWP, and after reception of SIB1 (which may be another SIB), the initial downlink BWP may be determined / specified by locationAndBandwidth-rc included in the received SIB1. However, when the initial downlink BWP is determined / specified by locationAndBandwidth-rc at the time of reception of SIB1 (which may be another SIB), the terminal device 1 may perform a random access procedure using the initial downlink BWP determined / specified by locationAndBandwidth-rc.

[0139] The terminal device 1 may switch the timing for determining / specifying an initial downlink BWP (which may be referred to as a separate initial downlink BWP) based on the locationAndBandwidth-rc included in the SIB1, based on the information included in the SIB1 (or other SIB). The parameter initialBwpTiming indicating the timing to apply locationAndBandwidth-rc included in the SIB (or another SIB) may be 1-bit information.

[0140] initialBwpTiming specifies the frequency location and bandwidth indicated by locationAndBandwidth-rc for the initial downlink before the RRC connection is established (before RRCSetup / RRCResume / RRCReestablishment is received). Information indicating whether to determine / specify / apply as the frequency location and bandwidth of the link BWP However, when 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 at a frequency resource based on the frequency location and bandwidth indicated by locationAndBandwidth-rc.

[0141] initialBwpTiming determines / specifies the frequency location and bandwidth indicated by locationAndBandwidth-rc as the frequency location and bandwidth of the initial downlink BWP at the timing when the RRC connection is established. / Apply or receive SIB1 at the frequency location and band of the initial downlink BWP The information may indicate whether the width is applied.

[0142] The terminal device 1 may switch the timing for determining / specifying the initial downlink BWP based on the locationAndBandwidth-rc included in SIB1 (or other SIB) depending on the value of initialBwpTiming. For example, when initialBwpTiming is a first value, the terminal device 1 receives the SIB1. Until the SIB1 is received, CORESET0 is the initial downlink BWP, 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 the second value, the initial downlink BWP is determined / specified until the RRC connection is established, re-established or resumed ( For example, before receiving RRCSetup, RRCResume or RRCReestablishment, set CORESET0. The initial downlink BWP may be set as CORESET0, 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 (or may be another SIB) with a value of beforeerrc, CORESET0 may be set as 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, if initialBwpTiming is not included in SIB1 (or any other SIB), CORESET0 may be the initial downlink BWP until the RRC connection is established, re-established or resumed (e.g., before receiving RRCSetup, RRCResume or RRCReestablishment), and after the RRC connection is established, the initial downlink BWP may be determined / identified by the locationAndBandwidth-rc included in the received SIB1.

[0143] However, in this embodiment, although initialBwpTiming is described as a parameter that can be included in SIB1, it may be a parameter that can be included in other SIBs or RRC signaling. For example, initialBwpTiming may be a parameter that can be included in the RRC parameter initialDownlinkBWP, and the initialDownlinkBWP may be included in SIB1 (or may be another SIB or RRC parameter).

[0144] In a certain cell, SIB1 is received in a certain initial downlink BWP (first initial downlink BWP). When a separate initial downlink BWP (second initial downlink BWP) having a different frequency position and / or bandwidth from the first initial downlink BWP is set, The bandwidth of the rate initial downlink BWP is determined by the synchronous It may not contain a signal block. Separate initial downlink BWP for paging, la When a signal serving as a synchronization signal block is required for random access and / or other purposes, an additional synchronization signal block (hereinafter referred to as a The base station device 3 may then transmit an additional synchronization signal block (referred to as an additional SSB) within the band of a second initial downlink BWP (separate initial downlink BWP) specified / determined by locationAndBandwidth-rc. The terminal device 1 may receive an additional synchronization signal block transmitted within the band of the separate initial downlink BWP identified / determined from locationAndBandwidth-rc. Additional synchronization signal The block is called a Cell Defining SSB (CD-SSB). For example, the additional synchronization signal block may not have a center frequency of the synchronization raster.

[0145] However, in order to receive an additional synchronization signal block that is an NCD-SSB within the band of the separate initial downlink BWP, the terminal device 1 needs to identify the frequency position of the additional synchronization signal block. The base station device 3 determines the second initial downlink link specified / determined from locationAndBandwidth-rc. Information to identify the frequency location of the additional synchronization signal block transmitted within the band of the link BWP / Parameter ssbFrequencyOffset-rc in SIB1 (other SIB or RRC signaling) The terminal device 1 may transmit the SIB1 (or other SIB or RRC signaling). The frequency position of the additional synchronization signal block to be transmitted within the band of the separate initial downlink BWP specified / determined from locationAndBandwidth-rc may be specified based on information / parameter ssbFrequencyOffset-rc included in locationAndBandwidth-rc (or may be specified based on locationAndBandwidth-rc). For example, the amount of information of ssbFrequencyOffset-rc can be reduced by applying the range of frequency positions of the additional synchronization signal block indicated by ssbFrequencyOffset-rc only within the band of the separate initial downlink BWP specified / determined by locationAndBandwidth-rc.

[0146] ssbFrequencyOffset-rc is the second initial offset determined from locationAndBandwidth-rc. The frequency from the reference frequency position of the downlink BWP to the reference frequency position of the additional synchronization signal block However, the reference frequency position of the second initial downlink BWP is the PRB with the lowest frequency (the PRB with index 0) that includes the second initial downlink BWP. The lowest frequency CRB that contains the second initial downlink BWP (often referred to as PRB0) However, the reference frequency position of the second initial downlink BWP may be The reference frequency position of the second initial downlink BWP may be the lowest frequency subcarrier of the link BWP (which may be the subcarrier with index 0 in PRB0, which may also be referred to as subcarrier 0 of PRB0). However, the reference frequency position of the second initial downlink BWP may be a PRB or CRB including the center frequency of the second initial downlink BWP. However, the reference frequency position of the second initial downlink BWP may be the subcarrier of the center frequency of the second initial downlink BWP. However, The reference frequency position of the block may be the lowest frequency PRB or CRB including the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the lowest frequency subcarrier of the additional synchronization signal block. For example, when the 240 subcarriers constituting the additional synchronization signal block are indexed from 0 to 239 from the lowest frequency, the reference frequency position of the additional synchronization signal block may be the subcarrier of index 0 of the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the PRB or CRB including the center frequency of the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the subcarrier including the center frequency of the additional synchronization signal block. For example, when the 240 subcarriers constituting the additional synchronization signal block are indexed from 0 to 239 from the lowest frequency, the reference frequency position of the additional synchronization signal block may be the subcarrier of index 119 or 120 of the additional synchronization signal block.

[0147] ssbFrequencyOffset-rc is the offset from the reference frequency position in the carrier to the additional synchronization signal block. It may be a frequency offset to a reference frequency position. However, the reference frequency position in the carrier may be Point A (CRB (CRB0) with an index of 0). In this case, the value indicated by ssbFrequencyOffset-rc may be the number of the CRB. The value indicated by ssbFrequencyOffset-rc may be the number of the CRB with the smallest index that includes an additional synchronization signal block. In this case, the index of the CRB with the smallest index that includes an additional synchronization signal block may be interpreted as simply specifying the CRB number rather than an offset. ssbFrequencyOffset-rc may indicate a parameter indicating the index of the CRB with the smallest index that includes an additional synchronization signal block, and an index (0 to 11) of a subcarrier with a lower frequency among the subcarriers to which the additional synchronization signal block is assigned in the CRB (may be referred to as a subcarrier offset in the CRB). The index of the CRB indicated by ssbFrequencyOffset-rc is the index of the CRB μ corresponding to the subcarrier interval μ. When ssbFrequencyOffset-rc is indicated, this μ may be the subcarrier spacing setting of the synchronization signal block common to the cell. However, when a CRB number is indicated by ssbFrequencyOffset-rc, the subcarrier spacing setting μ corresponding to the CRB number may be the subcarrier spacing setting μ of the synchronization signal block common to the cell. For example, the CRB number indicated by ssbFrequencyOffset-rc may be the CRB μ number based on the subcarrier spacing setting μ of the synchronization signal block common to the cell. Alternatively, when a CRB number is indicated by ssbFrequencyOffset-rc, the subcarrier spacing setting μ corresponding to the CRB number may be the subcarrier spacing setting μ of the synchronization signal block common to the cell. The interval setting μ is the synchronization signal block (CD-SSB) transmitted within the band of the initial downlink BWP. Alternatively, when a CRB number is indicated by ssbFrequencyOffset-rc, the subcarrier spacing setting μ corresponding to the CRB number may be the subcarrier spacing setting μ of an additional synchronization signal block (which may be an NCD-SSB) received in a separate initial downlink BWP. However, when a CRB number is indicated by ssbFrequencyOffset-rc, information on the subcarrier spacing setting μ corresponding to the CRB number may be indicated in an MIB (which may be SIB1, other SIBs, or RRC signaling).

[0148] ssbFrequencyOffset-rc is the offset from the reference frequency position of the synchronization signal block transmitted within the band of the initial downlink BWP to the additional synchronization signal block transmitted within the separate initial downlink BWP. The reference frequency position of the additional synchronization signal block may be a frequency offset to the reference frequency position of the additional synchronization signal block. However, the reference frequency position of the synchronization signal block may be the lowest frequency PRB or CRB including the synchronization signal block. However, the reference frequency position of the synchronization signal block may be the lowest frequency subcarrier of the synchronization signal block. However, the reference frequency position of the synchronization signal block may be the PRB or CRB including the center frequency of the synchronization signal block. However, the reference frequency position of the synchronization signal block may be the subcarrier of the center frequency of the synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the lowest frequency PRB or CRB including the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the lowest frequency subcarrier of the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the PRB or CRB including the center frequency of the additional synchronization signal block. However, the reference frequency position of the additional synchronization signal block may be the subcarrier of the center frequency of the additional synchronization signal block.

[0149] FIG. 8 is a diagram showing an overview of the frequency position of the additional synchronization signal block according to this embodiment. In FIG. 8, two initial downlink BWPs, an initial DL BWP and a separate initial DL BWP, are set in a certain cell. However, the initial downlink BWP may be the band of CORESET0. In FIG. 8, the initial downlink BWP includes at least a synchronization signal block (SSB), CORESET0, and a PDSCH (PDSCH with SIB1) including SIB1 in the band. In FIG. 8, the separate initial downlink BWP includes at least an additional synchronization signal block (additional SSB) in the band. The terminal device 1 that has received the SIB1 identifies the frequency location of CORESET0, and identifies the frequency location and time location of the PDSCH including SIB1 by the PDCCH received in CORESET0. The terminal device 1 that has received the PDSCH including SIB1 identifies / determines the frequency location (including the bandwidth) of the separate initial downlink BWP by the parameter locationAndBandwidth-rc included in SIB1 (or may be another SIB identified by the SIB1). Having identified the frequency location of the separate initial downlink BWP, The terminal device 1 that has determined / decided the separate initial downlink link frequency is determined by the parameter ssbFrequencyOffset-rc included in SIB1 (or may be another SIB specified by the SIB1). Identifying / determining the frequency location of the additional synchronization signal block transmitted within the link BWP and A signal block can be received.

[0150] The value indicated by ssbFrequencyOffset-rc may be a frequency offset in subcarriers. The value indicated by ssbFrequencyOffset-rc may be a frequency offset in RB units. The value indicated by ssbFrequencyOffset-rc may be a frequency offset in ARFCN (Absolute Radio-Frequency Channel Number) units. ssbFrequencyOffset-rc is a parameter indicating a frequency offset in resource block units and a frequency offset in subcarrier units. For example, ssbFrequencyOffset-rc may be combined with a frequency offset of 100 MHz. The included rb-offset is a frequency offset in resource blocks of 12 or more subcarriers. The sc-offset included in ssbFrequencyOffset-rc may indicate a frequency offset in subcarrier units of less than 12 subcarriers. The frequency offset is expressed in subcarriers, or ssbFrequencyOffset-rc. The subcarrier spacing setting μ (the subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc) corresponding to the resource block which is the unit of the frequency offset is expressed as follows: The subcarrier spacing setting μ of the synchronization signal block common to the cells may be used. However, the subcarrier spacing setting μ (the subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc) associated with the subcarrier that is the unit of the frequency offset indicated by ssbFrequencyOffset-rc or the resource block that is the unit of the frequency offset indicated by ssbFrequencyOffset-rc may be the subcarrier spacing setting μ of the additional synchronization signal block transmitted in the separate initial downlink BWP.

[0151] The subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc is The frequency offset may be the subcarrier spacing of the additional synchronization signal block. The subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc may be the subcarrier spacing setting μ of the corresponding separate initial downlink BWP. The terminal device 1 may determine / specify the subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc based on the subcarrier spacing setting μ1 of the corresponding additional synchronization signal block and / or the subcarrier spacing setting μ2 of the separate initial downlink BWP. For example, the terminal device 1 may determine / specify the narrower subcarrier spacing between the subcarrier spacing setting μ1 of the corresponding additional synchronization signal block and the subcarrier spacing setting μ2 of the separate initial downlink BWP as the subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc. However, the subcarrier spacing setting μ of the additional synchronization signal block may be the same as the subcarrier spacing setting μ of the synchronization signal block (which may be CD-SSB) including the MIB including the scheduling information of the SIB1 including ssbFrequencyOffset-rc. For example, the terminal device 1 may determine / specify the subcarrier spacing setting μ of the frequency offset indicated by ssbFrequencyOffset-rc based on the subcarrier spacing setting μ3 of the synchronization signal block including the scheduling information of SIB1 and / or the subcarrier spacing setting μ4 of the separate initial downlink BWP.

[0152] It is also possible to use the parameter offsetToPointA as the information format used for ssbFrequencyOffset-rc. However, the parameter offsetToPointA used for a synchronization signal block that is CD-SSB specifies point A from the frequency position of the synchronization signal block using the parameter offsetToPointA, but when used for an additional synchronization signal block that is NCD-SSB, it specifies the frequency position of the additional synchronization signal block from the already specified point A.

[0153] 9 is a flow diagram showing an example of a process related to determining / specifying a frequency position of an additional synchronization signal block in the terminal device 1 of this embodiment. In step S1001 of FIG. 9, the terminal device 1 In step S1002, the terminal device 1 receives an SIB1 (or may receive another SIB) including offset information ssbFrequencyOffset-rc that specifies the frequency position of an additional synchronization signal block in the second initial downlink BWP. The frequency position of the synchronization signal block is identified. However, the terminal device 1 may receive locationAndBandwidth-rc in SIB1, identify the frequency position of the second initial downlink BWP based on the received locationAndBandwidth-rc, and identify the reference frequency position of the additional synchronization signal block by applying the received ssbFrequencyOffset-rc based on the reference frequency position of the second initial downlink BWP. In step S1003, the terminal device 1 receives the additional synchronization signal block at the identified frequency position.

[0154] The base station device 3 transmits information / parameters for the terminal device 1 to specify the subcarrier spacing (which may be the subcarrier spacing setting μ) of the additional synchronization signal block to the SIB1 (or other SIB or The terminal device 1 may transmit the base station 1 a base station 100 (or RRC signaling). The SIB1 (or other SIB or RRC signaling) received from the base station device 3 includes The subcarrier spacing of the additional synchronization signal block may be determined based on the information / parameters included in the additional synchronization signal block.

[0155] The information / parameter to specify the subcarrier spacing of the additional synchronization signal block is 1 bit. The ssbSubcarrierSpacing may be 1-bit information indicating 15 kHz or 30 kHz when the frequency range in which the parameter is received is frequency range 1 (FR1: Frequency Range 1), and may be 1-bit information indicating 120 kHz or 240 kHz when the frequency range is frequency range 2 (FR2).

[0156] The information / parameter for specifying the subcarrier spacing of the additional synchronization signal block may be subcarrierSpacing included in genericParameters in the initialDownlinkBWP. For example, the information / parameter for specifying the subcarrier spacing of the additional synchronization signal block may be a parameter specifying the subcarrier spacing used for all channels and reference signals in the initial downlink BWP. It may be a parameter subcarrierSpacing indicating the subcarrier spacing of all channels and reference signals in the second initial downlink BWP (which may be a separate initial downlink BWP).

[0157] The information / parameters for identifying the subcarrier spacing of the additional synchronization signal block are It may be a parameter subcarrierSpacing indicating the subcarrier spacing of all channels and reference signals within the initial downlink BWP (which may be a separate initial downlink BWP). For example, the information / parameter for specifying the subcarrier spacing of the additional synchronization signal block may be a parameter subcarrierSpacing included in a separateInitialDownlinkBWP that includes configuration information of the second initial downlink BWP.

[0158] The subcarrier spacing of the additional synchronization signal block may be the same as the subcarrier spacing of the synchronization signal block transmitted in the first initial downlink BWP. For example, the information / parameter for specifying the subcarrier spacing of the additional synchronization signal block may be a parameter subcarrierSpacing indicating the subcarrier spacing of all channels and reference signals in the first initial downlink BWP. For example, the information / parameter for specifying the subcarrier spacing of the additional synchronization signal block may be a parameter subcarrierSpacing included in the initialDownlinkBWP including configuration information of the first initial downlink BWP.

[0159] FIG. 10 shows the subcarrier interval of the additional synchronization signal block in the terminal device 1 of this embodiment. FIG. 10 is a flow diagram showing an example of a process related to determination / identification. The terminal device 1 determines the frequency position and bandwidth of the separate initial downlink BWP in the first cell. and a second information / parameter indicating a subcarrier interval of an additional synchronization signal block received in the separate initial downlink BWP. In step S1002, the terminal device 1 receives the received SIB. Identifying a frequency location of the separate initial downlink BWP based on the first information, and Sub-synchronization signal block received in separate initial downlink BWP based on information of In step S1003, the terminal device 1 receives an additional synchronization signal block at the specified subcarrier interval.

[0160] In this way, based on the information in SIB1, the separate initial downlink BWP is transmitted within the band. By identifying / determining the subcarrier spacing of the additional synchronization signal block, the terminal device 1 , it is possible to receive the additional synchronization signal block transmitted from the base station device 3 within the band of the separate initial downlink BWP.

[0161] The terminal device 1 may be configured with multiple initial uplink sub-BWPs by the SIB1. The terminal device 1 may determine one or more initial uplink sub-BWPs based on the initialUplinkBWP provided by the SIB1. At least one of the multiple initial uplink sub-BWPs may be configured to include resources of a physical random access channel. The terminal device 1 may be configured to operate by regarding the initial uplink sub-BWP as the initial uplink BWP. The multiple initial uplink sub-BWPs may be regarded as multiple initial uplink BWPs. The multiple initial uplink sub-BWPs may be designed to be included in the frequency band of one initial uplink BWP. The initial uplink sub-BWP may be rephrased as an uplink BWP or an uplink sub-BWP. However, for the terminal device 1, "the initial uplink BWP is set / specified" may mean that the frequency position and / or bandwidth of the initial uplink BWP is set / specified. However, for the terminal device 1, "the multiple initial uplink sub-BWPs" may mean that the frequency position and / or bandwidth of the initial uplink BWP is set / specified. The term "initial uplink BWP is set / specified" may mean that multiple frequency positions and / or multiple bandwidths of the initial uplink BWP are set / specified. The base station device 3 broadcasts information including the setting of multiple frequency positions and / or multiple bandwidths of the initial uplink BWP, and the terminal device 1 Based on the information, determine / specify / set the frequency location and bandwidth of the initial uplink BWP Good too.

[0162] The SIB1 may include uplinkConfigCommon, which is a common downlink configuration parameter for a certain cell. At least one of the parameters for the uplink configuration may be included in uplinkConfigCommon indicating common uplink parameters of a certain cell. uplinkConfigCommon may include a parameter indicating a basic parameter related to one uplink carrier and 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-rc), and / or a parameter indicating a configuration of multiple initial uplink sub-BWPs (e.g., referred to as initialUplinkBWP-rc). Information ulAllocationBandwidth indicating a maximum allocated bandwidth in the uplink may be included in uplinkConfigCommon.

[0163] The initialUplinkBWP contains the BWP information element, the PDCCH configuration information element, and / or the PDSCH However, the initial uplink BWP is a physical land area in the frequency domain. The network may be configured to include dumb access channel resources.

[0164] The terminal device 1 according to the present invention is configured to set the initial uplink B The terminal device 1 receives / specifies the configuration information of the initial uplink BWP. However, the initialUplinkBWP may be included in the SIB1 or in any RRC signaling. 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 the SIB1 or any RRC signaling 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.

[0165] However, parameters set in SIB1 are not broadcast in other SIBs (or REDCAP SIBs). Alternatively, the notification may be given by RRC signaling.

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

[0167] FIG. 11 is a schematic block diagram showing the configuration of a terminal device 1 according to the present embodiment. The terminal device 1 includes a radio transmission / reception unit 10 and an upper layer processing unit 14. The receiving 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 transceiver 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 processing unit 14, a measurement unit 14, a selection unit 14, a decision unit 14, or a control unit 14.

[0168] The upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user operation or the like to the radio transmission / reception unit 10. The upper layer processing unit 14 performs part or all of processing of a Medium Access Control (MAC) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, and a Radio Resource Control (RRC) layer. The upper layer processing unit 14 may have a function of acquiring bit information of an MIB (which may be a REDCAP MIB), an SIB1 (which may be a REDCAP SIB1), and other SIBs (which may be REDCAP SIBs). The upper layer processing unit 14 may have a function of determining / specifying a setting (e.g., a frequency position or a bandwidth) of an initial downlink BWP based on information of a system information block (SIB1 / SIB) or RRC signaling. The upper layer processing unit 14 may have a function of determining / specifying the configuration (e.g., frequency location and bandwidth) of the initial uplink BWP based on the system information block (SIB1 / SIB) or information of RRC signaling. The upper layer processing unit 14 may have a function of determining / specifying the configuration (e.g., frequency location and bandwidth) of the separate initial uplink BWP based on the system information block (SIB1 / SIB) or information of RRC signaling.

[0169] The upper layer processing unit 14 includes a media access control layer processing unit 15 that performs processing for a MAC layer (media access control The media access control layer processing unit 15 controls the transmission of the scheduling request based on various setting information / parameters managed by the radio resource control layer processing unit 16.

[0170] The radio resource control layer processing unit 16 included in the upper layer processing unit 14 controls the RRC layer (radio resource control The radio resource control layer processing unit 16 performs processing of the downlink control layer (downlink control information) for the base station device 3. 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 a higher layer signal 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.

[0171] The wireless transmission / reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding. The receiving unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and transmits the decoded information to a higher-level The radio transmission / reception unit 10 generates a transmission signal by modulating and encoding data, and transmits it to the base station device 3, etc. The radio transmission / reception unit 10 outputs higher layer signals (RRC messages), DCI, etc. received from the base station device 3 to the higher layer processing unit 14. Based on instructions from the higher layer processing unit 14, the radio transmission / reception unit 10 also outputs uplink signals (PUCCH and / or The radio transceiver 10 generates and transmits a synchronization signal block, an additional synchronization Signal block, PSS, SSS, PBCH, DMRS for PBCH, Random Access Response, PDCCH and The radio transceiver unit 10 may have a function of receiving a PDSCH and / or a PRACH (which may be a random access preamble), a PUCCH and / or a PUSCH. The radio transceiver unit 10 may have a function of monitoring a PDCCH. may have a function of receiving DCI on the PDCCH. The radio transceiver unit 10 may have a function of outputting the DCI received on the PDCCH to the higher layer processing unit 14. The radio transceiver unit 10 may have a function of receiving a system information block (SIB1 and / or SIB) corresponding to a predetermined cell.

[0172] 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 processed analog signal is output to the baseband section.

[0173] The baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal. The baseband unit 13 extracts a CP (Cyclic Prefix) from the converted digital signal. The part corresponding to is removed, and the signal from which the CP has been removed is subjected to a Fast Fourier Transform (FFT) to extract the signal in the frequency domain.

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

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

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

[0177] The RF unit 12 may have a function of tuning / retuning the frequency band to which the RF circuit is applied within the downlink BWP when the bandwidth of the set downlink BWP (for example, the initial downlink BWP) is wider than the bandwidth supported by the receiver of the own device (which may be called the allocated bandwidth). However, the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when down-converting the received signal to a baseband signal.

[0178] The RF unit 12 may have a function of adjusting / re-adjusting the frequency band to which the RF circuit is applied within the uplink BWP when the bandwidth of the set uplink BWP (for example, the initial downlink BWP) is wider than the bandwidth supported by the transmitter of the own device (which may be called the allocated bandwidth). The frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency applied when an analog signal is up-converted to the carrier frequency.

[0179] FIG. 12 is a schematic block diagram showing the configuration of a base station device 3 according to the present embodiment. The base station device 3 includes a radio transmission / reception unit 30 and an upper layer processing unit 34. The wireless transceiver unit 30 includes an antenna unit 31, an RF unit 32, and a baseband unit 33. The upper layer processing unit 34 includes a media access control layer processing unit 35 and a radio resource control layer processing unit 36. The wireless transceiver 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 be provided separately. The upper layer processing unit 34 is also referred to as a processing unit 34, a decision unit 34, or a control unit 34.

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

[0181] The medium 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.

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

[0183] When the base station device 3 transmits an RRC message, MAC CE, and / or PDCCH to the terminal device 1 and the terminal device 1 performs processing based on the reception of the RRC message, MAC CE, and / or PDCCH, 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. The base station device 3 sends RRC messages, MAC CEs, and / or PDCCHs to the terminal device 1 causing the terminal device to perform processing based on its reception.

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

[0185] The upper layer processing unit 34 also controls the transmission of control messages or user data between the base station devices 3 or between the upper network devices (MME, S-GW (Serving-GW)) and the base station device 3 ( In FIG. 12, other components of the base station device 3 and configuration elements Although the transmission path of data (control information) between the base stations is omitted, the base station device 3 It is clear that the upper layer processor 34 includes a plurality of blocks having other functions necessary for its operation as components. For example, the upper layer processor 34 includes a radio resource management layer processor and an application layer processor.

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

[0187] Each of the units denoted by reference numerals 10 to 16 in the terminal device 1 is configured as a circuit. Each of the units denoted by reference numerals 30 to 36 in the base station device 3 may be implemented as a circuit. It may be configured as follows.

[0188] The program that runs on the device according to the present invention may be a program that controls a Central Processing Unit (CPU) or the like to make a computer function so as to realize the functions of the embodiments according to 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) or a flash memory. The information is stored in the non-volatile memory of a hard disk drive (HDD), or in other storage devices.

[0189] A program for implementing the functions of the embodiments of the present invention may be recorded on a computer-readable recording medium. The program may be implemented by loading the program recorded on the recording medium into a computer system and executing it. The term "computer system" as used herein refers to a computer system built into an apparatus, and includes 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 holds a program for a short period of time, or any other computer-readable recording medium.

[0190] Also, each functional block or feature of the apparatus used in the above-described embodiments may be implemented or performed in an electrical circuit, for example, an integrated circuit or a plurality of integrated circuits. An electrical circuit designed to perform the functions described herein may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a microprocessor, a microcomputer ... The general purpose processor may include a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or a combination of these. The general purpose processor may be a microprocessor, or a conventional processor, controller, microcontroller, or state machine. The electrical circuits described above may be composed of digital circuits or analog circuits. In addition, advances in semiconductor technology may replace current integrated circuits. As new integrated circuit technologies emerge, one or more aspects of the present invention may be implemented using the new integrated circuits.

[0191] In the embodiment of the present invention, an example in which the present invention is applied to a communication system configured with a base station device and a terminal device has been described. However, the present invention may also be applied to a communication system in which terminals communicate with each other, such as D2D (Device to Device). The present invention is also applicable to systems in which

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

[0193] 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 changes and the like within the scope of the gist of the present invention are also included. Furthermore, the present invention can be modified in various ways 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 replaced with elements that have the same effect are also included. [Explanation of symbols]

[0194] 1(1A, 1B) Terminal equipment 3 Base station equipment 4 Transmit / Receive Point (TRP) 10 Radio transmitter / receiver 11 Antenna section 12 RF section 13 Baseband section 14 Upper layer processing unit 15 Media access control layer processing unit 16 Radio resource control layer processing unit 30 Radio transmitter / receiver 31 Antenna section 32 RF section 33 Baseband section 34 Upper layer processing unit 35 Media access control layer processing unit 36 Radio resource control layer processing unit 50 Transmitting Unit (TXRU) 51 Phase Shifter 52 Antenna Element

Claims

1. A terminal device, A receiver for receiving a system information block including first information in a first cell; a control unit that identifies a frequency position of a synchronization signal block based on the first information. 、 The receiving unit receives the synchronization signal block at the identified frequency position, A terminal device, wherein the first information is information indicating an offset in the frequency domain from a first reference frequency position to a reference frequency position of the synchronization signal block.

2. the system information block includes second information; The second information is information for identifying a number of resource blocks constituting a first downlink BWP in the first cell and an index of a resource block having a lowest frequency; the first reference frequency position is a reference frequency position of the first downlink BWP; Item 1. A terminal device according to item 1.

3. The reference frequency position of the first downlink BWP is the lowest frequency CRB including the first downlink BWP, and the reference frequency position of the synchronization signal block is the lowest frequency CRB including the synchronization signal block. The terminal device according to claim 2, wherein the subcarrier is the subcarrier with the highest frequency.

4. The first reference frequency position is a CRB with an index of 0, and the synchronization signal block The terminal device according to claim 1, wherein the reference frequency position of the block is the lowest frequency CRB that includes the synchronization signal block.

5. 2. The terminal device according to claim 1, wherein the offset is an offset in subcarrier units.

6. 2. The terminal device according to claim 1, wherein the subcarrier spacing of the offset is the subcarrier spacing of the synchronization signal block.

7. A base station device, A control unit that generates first information; In a first cell, a system information block including the first information is transmitted, and a first frequency band is transmitted. a transmitter for transmitting a synchronization signal block at a plurality of positions; the first frequency location is identified based on the first information; A base station device, wherein the first information is information indicating an offset in the frequency domain from a first reference frequency position to a reference frequency position of the synchronization signal block.

8. The control unit generates second information, the system information block includes the second information; The second information is information for identifying a number of resource blocks constituting a first downlink BWP in the first cell and an index of a resource block having a lowest frequency; the first reference frequency position is a reference frequency position of the first downlink BWP; Item 7. A base station device according to item 7.

9. The first reference frequency position is a CRB with an index of 0, and the synchronization signal block 8. The base station apparatus according to claim 7, wherein the reference frequency position of the block is a CRB having the lowest frequency that includes the synchronization signal block.

10. A communication method for a base station device, comprising: Generate first information; In a first cell, a system information block including the first information is transmitted, and a first frequency band is transmitted. Transmitting a synchronization signal block at each position; the first frequency location is identified based on the first information; A communication method, wherein the first information is information indicating an offset in the frequency domain from a first reference frequency position to the reference frequency position of the synchronization signal block.