WO2023054101A1 - Dispositif terminal, dispositif station de base et procédé de communication - Google Patents

Dispositif terminal, dispositif station de base et procédé de communication Download PDF

Info

Publication number
WO2023054101A1
WO2023054101A1 PCT/JP2022/035135 JP2022035135W WO2023054101A1 WO 2023054101 A1 WO2023054101 A1 WO 2023054101A1 JP 2022035135 W JP2022035135 W JP 2022035135W WO 2023054101 A1 WO2023054101 A1 WO 2023054101A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal device
bwp
downlink bwp
cell
Prior art date
Application number
PCT/JP2022/035135
Other languages
English (en)
Japanese (ja)
Inventor
宏樹 高橋
昇平 山田
麗清 劉
Original Assignee
シャープ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by シャープ株式会社 filed Critical シャープ株式会社
Publication of WO2023054101A1 publication Critical patent/WO2023054101A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management

Definitions

  • the present invention relates to a terminal device, a base station device, and a communication method.
  • This application claims priority to Japanese Patent Application No. 2021-160918 filed in Japan on September 30, 2021, the content of which is incorporated herein.
  • Non-Patent Document 1 LTE (Long Term Evolution)-Advanced Pro and NR (New Radio technology) are being studied and standards are being developed.
  • 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 as described above.
  • a terminal device includes a receiving unit that receives a system information block including first information and second information in a first cell; a control unit that identifies the frequency position of the first downlink BWP in one cell and identifies subcarrier intervals of synchronization signal blocks received by the first downlink BWP based on the second information; The receiving unit receives the synchronization signal blocks at the subcarrier intervals in the first downlink BWP.
  • the base station apparatus includes a control unit that generates first information and second information, and a first cell that generates the first information and the second information. and transmitting a synchronization signal block in a first downlink BWP, the first information identifying the frequency location of the first downlink BWP in the first cell information, and the second information is information specifying subcarrier intervals of the synchronization signal block to be transmitted in the first downlink BWP.
  • a communication method is a communication method of a base station apparatus, in which first information and second information are generated, and in a first cell, the first information and transmitting a system information block including the second information, transmitting a synchronization signal block in a first downlink BWP, wherein the first information is the frequency location of the first downlink BWP in the first cell; and the second information is information that specifies subcarrier intervals of the synchronization signal blocks to be transmitted in the first downlink BWP.
  • the terminal device and the base station device can communicate efficiently.
  • FIG. 1 is a diagram showing the concept of a wireless communication system according to an embodiment of the present invention
  • FIG. FIG. 2 is a diagram showing an example of schematic configurations of uplink and downlink slots according to an embodiment of the present invention
  • FIG. 4 is a diagram illustrating the relationship in the time domain of subframes, slots and minislots according to an embodiment of the present invention
  • FIG. 3 is a diagram showing examples of SS/PBCH blocks and SS burst sets according to embodiments of the present invention
  • FIG. 4 is a diagram illustrating resources in which PSS, SSS, PBCH and DMRS for PBCH are arranged in an SS/PBCH block according to an embodiment of the present invention
  • FIG. 4 is a diagram showing an example of RF retuning according to an embodiment of the invention
  • FIG. 4 is a diagram showing an example of a parameter configuration of an information element (IE) BWP-DownlinkCommon of initialDownlinkBWP according to an embodiment of the present invention
  • FIG. 4 is a diagram showing an overview of frequency positions of additional synchronization signal blocks according to an embodiment of the present invention
  • FIG. 4 is a flowchart showing an example of processing related to determination/specification of frequency positions of additional synchronization signal blocks in the terminal device 1 according to the embodiment of the present invention
  • FIG. 4 is a flowchart showing an example of processing related to determination/specification of subcarrier intervals for additional synchronization signal blocks in terminal device 1 according to the embodiment of the present invention.
  • 1 is a schematic block diagram showing the configuration of a terminal device 1 according to an embodiment of the present invention
  • FIG. 1 is a schematic block diagram showing the configuration of a base station device 3 according to an embodiment of the present invention
  • FIG. 1 is a conceptual diagram of a wireless communication system according to this embodiment.
  • the radio communication system includes a terminal device 1A, a terminal device 1B, and a base station device 3.
  • FIG. Terminal device 1A and terminal device 1B are also referred to as terminal device 1 hereinafter.
  • the terminal device 1 is also called a user terminal, mobile station device, communication terminal, mobile device, terminal, UE (User Equipment), and 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 includes a radio base station device, base station, radio base station, fixed station, NB (Node B), eNB (evolved Node B), BTS (Base Transceiver Station), BS (Base Station), NR NB ( NR Node B), NNB, TRP (Transmission and Reception Point), gNB.
  • the base station device 3 may include a core network device. Also, the base station device 3 may have one or more transmission reception points 4 .
  • the base station device 3 may serve the terminal device 1 with one or a plurality of cells in the communication coverage (communication area) controlled by the base station device 3 . Also, the base station device 3 may serve the terminal device 1 with one or a plurality of cells as a communication range (communication area) controlled by one or a plurality of transmission/reception points 4 . Also, the base station device 3 may divide one cell into a plurality of beamed areas and serve the terminal device 1 in each of the beamed areas. Here, the subregions may be identified based on a beam index or a precoding index used in beamforming.
  • the radio communication link from the base station device 3 to the terminal device 1 is called a downlink.
  • the radio communication link from the terminal device 1 to the base station device 3 is called an uplink.
  • Orthogonal Frequency Division Multiplexing including Cyclic Prefix (CP), Single Carrier Frequency Division Multiplexing (SC- FDM: Single-Carrier Frequency Division Multiplexing), Discrete Fourier Transform Spread OFDM (DFT-S-OFDM: Discrete Fourier Transform Spread OFDM), or other transmission schemes may be used.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP Cyclic Prefix
  • SC- FDM Single Carrier Frequency Division Multiplexing
  • DFT-S-OFDM Discrete Fourier Transform Spread OFDM
  • OFDM symbols are used as the transmission method, but the present invention also includes the case of using the other transmission methods described above.
  • wireless communication between the terminal device 1 and the base station device 3 may use the above-described transmission scheme that does not use the CP or uses zero padding instead of the CP.
  • CP and zero padding may be added both forward and backward.
  • One aspect of the present embodiment is operated in carrier aggregation (CA) or dual connectivity (DC) with a radio access technology (RAT: Radio Access Technology) such as LTE or LTE-A/LTE-A Pro.
  • RAT Radio Access Technology
  • LTE or LTE-A/LTE-A Pro may At this time, some or all cells or cell groups, carriers or carrier groups (e.g. Primary Cell (PCell), Secondary Cell (SCell), Primary Secondary Cell (PSCell), MCG (Master Cell Group) ), SCG (Secondary Cell Group), etc.).
  • PCell Primary Cell
  • SCell Secondary Cell
  • PSCell Primary Secondary Cell
  • MCG Master Cell Group
  • SCG Secondary Cell Group
  • one aspect of the present embodiment may be used in a standalone operation.
  • SpCells In DC operation, SpCells (Special Cells) are referred to as MCG PCells or SCG PSCells, depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG, respectively.
  • a SpCell (Special Cell) is called a PCell if it is not a DC operation.
  • SpCell (Special Cell) supports PUCCH transmission and Contention Based Random Access (CBRA).
  • CBRA Contention Based Random Access
  • one or more serving cells may be configured for the terminal device 1.
  • the configured serving cells may include one primary cell and one or more secondary cells.
  • the primary cell may be the serving cell where the initial connection establishment procedure was performed, the serving cell that initiated the connection re-establishment procedure, or the cell designated as the primary cell in the handover procedure. good.
  • One or a plurality of secondary cells may be configured at or after an RRC (Radio Resource Control) connection is established.
  • the configured multiple serving cells may include one primary secondary cell.
  • the primary secondary cell may be a secondary cell capable of transmitting control information in the uplink among one or more secondary cells in which the terminal device 1 is configured.
  • two types of serving cell subsets, MCG and SCG may be configured for the terminal device 1 .
  • An MCG may consist of one PCell and zero or more SCells.
  • An SCG may consist of one PScell and zero or more SCells.
  • TDD Time Division Duplex
  • FDD Frequency Division Duplex
  • a TDD (Time Division Duplex) scheme or an FDD (Frequency Division Duplex) scheme may be applied to all of the plurality of cells.
  • a cell to which the TDD scheme is applied and a cell to which the FDD scheme is applied may be aggregated.
  • the TDD scheme may be referred to as unpaired spectrum operation.
  • the FDD scheme may be referred to as paired spectrum operation.
  • subframes will be explained below. Although the following are referred to as subframes in the present embodiment, the subframes according to the present embodiment may also be referred to as resource units, radio frames, time intervals, time intervals, and the like.
  • FIG. 2 is a diagram showing an example of schematic configurations of uplink and downlink slots according to the first embodiment of the present invention.
  • Each radio frame is 10 ms long.
  • each radio frame consists of 10 subframes and W slots.
  • one slot is composed of X OFDM symbols. That is, the length of one subframe is 1ms.
  • NCP Normal Cyclic Prefix
  • BWP BandWidth Part
  • a slot may also be defined as a Transmission Time Interval (TTI).
  • TTI Transmission Time Interval
  • a slot may not be defined as a TTI.
  • a TTI may be the transmission period of a transport block.
  • a signal or physical channel transmitted in each of the slots may be represented by a resource grid.
  • a resource grid is defined by multiple subcarriers and multiple OFDM symbols for each numerology (subcarrier spacing and cyclic prefix length) and each carrier. The number of subcarriers forming one slot depends on the downlink and uplink bandwidths of the cell.
  • Each element in the resource grid is called a Resource Element (RE).
  • An RE may be identified using a subcarrier number and an OFDM symbol number.
  • PDSCH physical downlink channel
  • PUSCH uplink channel
  • reference RBs As RBs, reference RBs, common resource blocks (CRBs: Common RBs), PRBs, and virtual resource blocks (VRBs: Virtual RBs) are defined.
  • 1 RB is defined as 12 consecutive subcarriers in the frequency domain.
  • Reference resource blocks are common to all subcarriers, and may be numbered in ascending order, forming resource blocks at subcarrier intervals of 15 kHz, for example.
  • Subcarrier index 0 in reference resource block index 0 may be referred to as reference point A (point A) (simply referred to as "reference point").
  • Point A may serve as a common reference point for the grid of resource blocks. The position of point A may be determined/specified by the parameter offsetToPointA contained in SIB1.
  • the parameter offsetToPointA is a parameter that indicates the frequency offset between point A and the lowest frequency subcarrier of the lowest frequency resource block that overlaps the synchronization signal block used by the terminal device 1 in initial cell selection.
  • the unit of the frequency offset is a resource block with a subcarrier interval of 15 kHz for frequency range (FR) 1, and a resource block with a subcarrier interval of 60 kHz for frequency range 2.
  • the frequency position may be indicated by ARFCN (absolute radio-frequency channel number) by the RRC parameter absoluteFrequencyPointA.
  • CRBs are RBs numbered in ascending order from 0 at each subcarrier spacing setting ⁇ from point A.
  • a CRB number is defined for each subcarrier interval setting ⁇ .
  • a CRB corresponding to the subcarrier spacing setting ⁇ may be referred to as CRB ⁇ .
  • the resource grid mentioned above is defined by the CRB.
  • the center of subcarrier index 0 of CRB ⁇ of number 0 in each subcarrier spacing setting ⁇ is point A.
  • PRBs are RBs numbered in ascending order from 0 included in the BWP for each subcarrier spacing ⁇ , and PRBs are numbered in ascending order from 0 included in the BWP for the subcarrier spacing ⁇ .
  • PRB ⁇ is a RB with A PRB corresponding to the subcarrier spacing setting ⁇ may be referred to as PRB ⁇ .
  • a given physical uplink channel is first mapped to a VRB. The VRB is then mapped to the PRB.
  • an RB may be a VRB, a PRB, a CRB, or a reference resource block.
  • 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. There may be one active downlink BWP (active downlink BWP) at a certain time. Terminal device 1 may not expect to receive PDSCH, PDCCH or CSI-RS out of the band of the active downlink BWP.
  • the terminal device 1 may be configured with up to four BWPs (uplink BWPs) in the uplink. There may be one active uplink BWP (active uplink BWP) at a certain time. The terminal device 1 does not transmit PUSCH and PUCCH outside the active uplink BWP band.
  • the subcarrier interval setting ⁇ As mentioned above, NR supports one or more OFDM numerologies.
  • slots are numbered in ascending order from 0 to N ⁇ subframe, ⁇ _ ⁇ slot ⁇ -1 within a subframe, and from 0 to N ⁇ frame, ⁇ _ ⁇ slot ⁇ -1 within a frame. ⁇ -1 are counted in ascending order.
  • N ⁇ slot ⁇ _ ⁇ symb ⁇ consecutive OFDM symbols in a slot based on slot configuration and CP.
  • N ⁇ slot ⁇ _ ⁇ symb ⁇ is 14.
  • the start of slot n ⁇ _ ⁇ s ⁇ in a subframe is timed from the start of the n ⁇ _ ⁇ s ⁇ *N ⁇ slot ⁇ _ ⁇ symb ⁇ th OFDM symbol in the same subframe are aligned with
  • FIG. 3 is a diagram showing an example of the relationship between subframes, slots, and minislots in the time domain.
  • a subframe is 1ms regardless of the subcarrier interval, and the number of OFDM symbols included in a slot is 7 or 14 (however, if the CP attached to each symbol is an Extended CP, it can be 6 or 12). may be used), and the slot length varies depending on the subcarrier spacing.
  • the subcarrier interval is 15 kHz
  • 14 OFDM symbols are included in one subframe.
  • a downlink slot may be referred to as PDSCH mapping type A.
  • the uplink slot may be referred to as PUSCH mapping type A.
  • a minislot (which may also be referred to as a subslot) is a time unit composed of OFDM symbols less than the number of OFDM symbols contained in one slot.
  • the figure shows an example in which a minislot is composed of two OFDM symbols.
  • the OFDM symbols within a minislot may coincide with the OFDM symbol timings that make up the slot.
  • the minimum unit of scheduling may be a slot or a minislot.
  • Allocating minislots may also be referred to as non-slot-based scheduling.
  • scheduling a mini-slot may be expressed as scheduling a resource in which the relative time positions of the start positions of the reference signal and data are fixed.
  • a downlink minislot may be referred to as PDSCH mapping type B.
  • Uplink minislots may be referred to as PUSCH mapping type B.
  • the symbol transmission direction (uplink, downlink or flexible) in each slot is set in the upper layer using an RRC message containing predetermined upper layer parameters received from the base station device 3, or It is set by PDCCH of a specific DCI format (for example, DCI format 2_0) received from base station apparatus 3 .
  • a format in which each symbol in each slot is set to either uplink, downlink, or flexible is called a slot format.
  • One slot format may include downlink symbols, uplink symbols and flexible symbols.
  • a carrier corresponding to the serving cell of this embodiment is called a component carrier (CC: Component Carrier) (or carrier).
  • CC Component Carrier
  • a carrier corresponding to a serving cell is called a downlink CC (or a downlink carrier).
  • a carrier corresponding to a serving cell is called an uplink CC (or an uplink carrier).
  • a carrier corresponding to the serving cell is called a sidelink CC (or sidelink carrier).
  • the following physical channels may be used in wireless communication between the terminal device 1 and the base station device 3.
  • PBCH Physical Broadcast CHannel
  • PDCCH Physical Downlink Control CHannel
  • PDSCH Physical Downlink Shared CHannel
  • PUCCH Physical Uplink Control CHannel
  • PRACH Physical Random Access CHannel
  • the PBCH is used to broadcast important information blocks (MIB: Master Information Block, EIB: Essential Information Block, BCH: Broadcast Channel) containing important system information required by the terminal device 1.
  • MIB contains information for identifying the number (SFN: System Frame Number) of the radio frame (also called system frame) to which the PBCH is mapped, system information block type 1 (SIB1: System Information Block 1, system information block Information specifying the subcarrier spacing of 1), information indicating the frequency domain offset between the resource block grid and the SS/PBCH block (also referred to as synchronization signal block, SS block, SSB), PDCCH for SIB1 may include information indicating settings for.
  • SIB1 includes information necessary for evaluating whether the terminal device 1 is allowed to connect to the cell, and includes information for determining scheduling of other system information (SIB: System Information Block).
  • SIB System Information Block
  • the information indicating the PDCCH settings for SIB1 includes control resource set (CORESET: ControlResourceSet) 0 (CORESET0 is also called CORESET#0, common CORESET), common search space and/or required PDCCH parameters. It may be information to decide.
  • CORESET indicates a PDCCH resource element, and is composed of a set of PRBs in a time period of a certain number of OFDM symbols (eg, 1 to 3 symbols).
  • CORESET0 may be the CORESET for at least the PDCCH that schedules SIB1.
  • CORESET0 may be configured in the MIB or via RRC signaling.
  • SIB1 may be scheduled by PDCCH transmitted on CORESET0. The terminal device 1 receives SIB1 scheduled on the PDCCH received on CORESET0.
  • the PBCH contains information for specifying the number (SFN: System Frame Number) of the radio frame (also called system frame) to which the PBCH is mapped and/or half radio frame (HRF: Half Radio Frame) (half (also referred to as a frame) may be used to broadcast information identifying the frame.
  • SFN System Frame Number
  • HRF Half Radio Frame
  • the half radio frame is a 5 ms long time frame
  • the information specifying the half radio frame may be information specifying the first half 5 ms or the second half 5 ms of the 10 ms radio frame.
  • the PBCH may be used to report the time index within the period of the SS/PBCH block.
  • the time index is information indicating the index of the synchronization signal and PBCH within the cell.
  • the time index may be referred to as the SSB index or SS/PBCH block index.
  • transmit filter settings and/or Quasi Co-Location (QCL) assumptions about receive spatial parameters within a predetermined period or setting may indicate the time order within the selected period.
  • the terminal may also perceive differences in time index as differences in QCL assumptions regarding transmit beams, transmit filter settings, and/or receive spatial parameters.
  • the PDCCH is used to transmit (or carry) downlink control information (DCI) in downlink radio communication (radio communication from the base station device 3 to the terminal device 1).
  • DCI downlink control information
  • one or more DCIs (which may be referred to as DCI formats) are defined for transmission of downlink control information. That is, the 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 trying to decode the PDCCH according to a certain DCI format.
  • 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
  • DCI format 0_0 may be used for PUSCH scheduling in a serving cell.
  • DCI format 0_0 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
  • DCI format 0_0 is a Radio Network Temporary Identifier (RNTI), Cell-RNTI (C-RNTI), Configured Scheduling (CS)-RNTI), MCS-C-RNTI, and/or Temporary C-NRTI.
  • RNTI Radio Network Temporary Identifier
  • C-RNTI Cell-RNTI
  • CS-RNTI Configured Scheduling
  • MCS-C-RNTI MCS-C-RNTI
  • Temporary C-NRTI Temporary C-NRTI.
  • a CRC Cyclic Redundancy Check
  • TC-RNTI Cyclic Redundancy Check
  • DCI format 0_1 may be used for PUSCH scheduling in a serving cell.
  • DCI format 0_1 includes information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, channel state information (CSI: Channel State Information) request, sounding reference signal (SRS: Sounding Reference Signal ) requests and/or information about antenna ports.
  • DCI format 0_1 may be appended with a CRC scrambled by any of RNTIs: C-RNTI, CS-RNTI, Semi Persistent (SP)-CSI-RNTI, and/or MCS-C-RNTI .
  • DCI format 0_1 may be monitored in the UE specific search space.
  • DCI format 0_2 may be used for PUSCH scheduling in a serving cell.
  • DCI format 0_2 may include information indicating PUSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, CSI request, SRS request, and/or information about antenna ports.
  • DCI format 0_2 may be added with a CRC scrambled by any one of RNTI, C-RNTI, CSI-RNTI, SP-CSI-RNTI, and/or MCS-C-RNTI.
  • DCI format 0_2 may be monitored in the UE specific search space.
  • DCI format 0_2 may be referred to as DCI format 0_1A, and so on.
  • DCI format 1_0 may be used for PDSCH scheduling in a serving cell.
  • DCI format 1_0 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation).
  • DCI format 1_0 specifies, among identifiers, C-RNTI, CS-RNTI, MCS-C-RNTI, Paging RNTI (P-RNTI), System Information (SI)-RNTI, Random access (RA)-RNTI, and/or , TC-RNTI may be added.
  • DCI format 1_0 may be monitored in a common search space or a UE-specific search space.
  • DCI format 1_1 may be used for PDSCH scheduling in a serving cell.
  • DCI format 1_1 includes information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, transmission configuration indication (TCI: Transmission Configuration Indication), and/or information on antenna ports. OK.
  • DCI format 1_1 may be added with a CRC scrambled by any one of RNTI, C-RNTI, CS-RNTI, and/or MCS-C-RNTI. DCI format 1_1 may be monitored in the UE specific search space.
  • DCI format 1_2 may be used for PDSCH scheduling in a serving cell.
  • DCI format 1_2 may include information indicating PDSCH scheduling information (frequency domain resource allocation and time domain resource allocation), information indicating BWP, TCI, and/or information about antenna ports.
  • DCI format 1_2 may be added with a CRC scrambled by any one of RNTI, C-RNTI, CS-RNTI, and/or MCS-C-RNTI.
  • DCI format 1_2 may be monitored in the UE-specific search space.
  • DCI format 1_2 may be referred to as DCI format 1_1A, and so on.
  • DCI format 2_0 is used to notify the slot format of one or more slots.
  • a slot format is defined as each OFDM symbol in a slot classified as downlink, flexible or uplink. For example, if the slot format is 28, DDDDDDDDDDFU is applied to 14 OFDM symbols in a slot with slot format 28 indicated.
  • D is a downlink symbol
  • F is a flexible symbol
  • U is an uplink symbol. Note that slots will be described later.
  • DCI format 2_1 is used to notify terminal device 1 of PRBs (or RBs) and OFDM symbols that can be assumed to have no transmission. This information may be called a preemption instruction (intermittent transmission instruction).
  • DCI format 2_2 is used for transmitting PUSCH and Transmit Power Control (TPC) commands for PUSCH.
  • TPC Transmit Power Control
  • DCI format 2_3 is used to transmit a group of TPC commands for sounding reference signal (SRS) transmission by one or more terminal devices 1. Also, an SRS request may be sent along with the TPC command. Also, in DCI format 2_3, an SRS request and a TPC command may be defined for uplinks without PUSCH and PUCCH, or for uplinks in which SRS transmission power control is not associated with PUSCH transmission power control.
  • SRS sounding reference signal
  • a DCI for the downlink is also called a downlink grant or a downlink assignment.
  • DCI for uplink is also called uplink grant or uplink assignment.
  • DCI may also be referred to as DCI format.
  • the CRC parity bits added to the DCI format transmitted on one PDCCH are scrambled with SI-RNTI, P-RNTI, C-RNTI, CS-RNTI, RA-RNTI, or TC-RNTI.
  • SI-RNTI may be an identifier used for broadcasting system information.
  • P-RNTI may be an identifier used for paging and notification of system information changes.
  • C-RNTI, MCS-C-RNTI, and CS-RNTI are identifiers for identifying terminal devices within a cell.
  • TC-RNTI is an identifier for identifying the terminal device 1 that has transmitted the random access preamble during CBRA.
  • C-RNTI is used to control PDSCH or PUSCH in one or more slots.
  • CS-RNTI is used to periodically allocate PDSCH or PUSCH resources.
  • MCS-C-RNTI is used to indicate the use of a given MCS table for grant-based transmission.
  • TC-RNTI is used to control PDSCH or PUSCH transmission in one or more slots.
  • TC-RNTI is used to schedule the retransmission of random access message 3 and the transmission of random access message 4.
  • 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.
  • Different values may be used for the C-RNTI and/or other RNTIs depending on the type of PDSCH or PUSCH traffic. Different values may be used for C-RNTI and other RNTIs corresponding to service types (eMBB, URLLC and/or mMTC) of data transmitted on PDSCH or PUSCH.
  • the base station device 3 may use different values of RNTI depending on the service type of data to be transmitted.
  • the terminal device 1 may identify the service type of data transmitted on the associated PDSCH or PUSCH by the value of RNTI applied (used for scrambling) to the received DCI.
  • the PUCCH is used to transmit uplink control information (UCI) in uplink wireless communication (wireless communication from terminal device 1 to base station device 3).
  • the uplink control information may include channel state information (CSI: Channel State Information) used to indicate the state of the downlink channel.
  • the uplink control information may include a scheduling request (SR: Scheduling Request) used to request UL-SCH resources.
  • the uplink control information may include HARQ-ACK (Hybrid Automatic Repeat request ACKnowledgement).
  • HARQ-ACK may indicate HARQ-ACK for downlink data (Transport block, Medium Access Control Protocol Data Unit: MAC PDU, Downlink-Shared Channel: DL-SCH).
  • PDSCH is used to transmit downlink data (DL-SCH: Downlink Shared CHannel) from the Medium Access Control (MAC) layer.
  • PDSCH is also used for transmission of system information (SI: System Information) and random access response (RAR: Random Access Response) in the case of downlink.
  • SI System Information
  • RAR Random Access Response
  • PUSCH may be used to transmit HARQ-ACK and/or CSI together with uplink data (UL-SCH: Uplink Shared CHannel) or uplink data from the MAC layer.
  • PUSCH may also be used to transmit CSI only, or HARQ-ACK and CSI only. That is, PUSCH may be used to transmit UCI only.
  • the base station device 3 and the terminal device 1 exchange (transmit and receive) signals in a higher layer.
  • the base station device 3 and the terminal device 1 may transmit and receive RRC messages (also referred to as RRC message, RRC information, and RRC signaling) in the radio resource control (RRC) layer.
  • RRC radio resource control
  • the base station device 3 and the terminal device 1 may transmit and receive MAC control elements in the MAC (Medium Access Control) layer.
  • the RRC layer of the terminal device 1 acquires system information broadcast from the base station device 3 .
  • RRC messages, system information and/or MAC control elements are also referred to as higher layer signals (higher layer signaling) or higher layer parameters (higher layer parameters).
  • the upper layer here means the upper layer seen from the physical layer, so it may include one or more of a MAC layer, an RRC layer, an RLC layer, a PDCP layer, a NAS (Non Access Stratum) layer, and the like.
  • higher layers in MAC layer processing may include one or more of an RRC layer, an RLC layer, a PDCP layer, a NAS layer, and the like.
  • the meanings of “A is given (provided) by the upper layer” and “A is given (provided) by the upper layer” refer to the upper layers of the terminal device 1 (mainly the RRC layer and the MAC layer).
  • 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.
  • "provided with upper layer parameters" in the terminal device 1 means that an upper layer signal is received from the base station device 3, and the upper layer parameters included in the received upper layer signal are transmitted from the upper layer of the terminal device 1 to the terminal. It may mean provided in the physical layer of the device 1 .
  • Setting the upper layer parameters to the terminal device 1 may mean that the terminal device 1 is given (provided) with the higher layer parameters.
  • setting upper layer parameters in the terminal device 1 may mean that the terminal device 1 receives an upper layer signal from the base station device 3 and sets the received upper layer parameters in the upper layer.
  • the setting of the upper layer parameters in the terminal device 1 may include the setting of default parameters given in advance to the upper layers of the terminal device 1 .
  • PDSCH or PUSCH may be used to transmit RRC signaling and MAC control elements.
  • the RRC signaling transmitted from the base station apparatus 3 by PDSCH may be signaling common to multiple terminal apparatuses 1 within a cell.
  • the RRC signaling transmitted from the base station device 3 may be signaling dedicated to a certain terminal device 1 (also referred to as dedicated signaling). That is, terminal device-specific (UE-specific) information may be transmitted to a certain terminal device 1 using dedicated signaling.
  • PUSCH may also be used to transmit UE Capability in the uplink.
  • the following downlink physical signals are used in downlink radio communication.
  • the downlink physical signal is not used to transmit information output from higher layers, but is used by the physical layer.
  • SS Synchronization signal
  • RS Reference Signal
  • the synchronization signal may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS). Cell ID may be detected using PSS and SSS.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • the synchronization signal is used by the terminal device 1 to synchronize the downlink frequency domain and time domain.
  • 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 .
  • beams may also be referred to as transmit or receive filter settings, or spatial domain transmit filters or spatial domain receive filters.
  • the reference signal is used by the terminal device 1 to perform channel compensation for the physical channel.
  • the reference signal may also be used by the terminal device 1 to calculate the downlink CSI.
  • the reference signal may be used for fine synchronization to the extent that numerology such as radio parameters and subcarrier intervals and FFT window synchronization are possible.
  • 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
  • DMRS is used to demodulate the modulated signal.
  • CSI-RS is used for channel state information (CSI) measurement and beam management, and applies periodic or semi-persistent or aperiodic CSI reference signal transmission methods.
  • CSI-RS may be defined as Non-Zero Power (NZP) CSI-RS and Zero Power (ZP) CSI-RS in which the transmit power (or receive power) is zero.
  • NZP Non-Zero Power
  • ZP Zero Power
  • ZP CSI-RS may be defined as a CSI-RS resource with zero transmit power or no transmission
  • PTRS is used to track phase over time in order to compensate for frequency offsets caused by phase noise.
  • TRS is used to ensure Doppler shift when moving at high speed.
  • TRS may be used as one setting of CSI-RS.
  • CSI-RS of one port is wireless as TRS. Resources may be configured.
  • 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
  • DMRS is used to demodulate the modulated signal.
  • SRS is used for uplink channel state information (CSI) measurements, channel sounding, and beam management.
  • PTRS is used to track phase over time in order to compensate for frequency offsets due to phase noise.
  • downlink physical channels and/or downlink physical signals are collectively referred to as downlink signals.
  • uplink physical channels and/or uplink physical signals are collectively referred to as uplink signals.
  • downlink physical channels and/or uplink physical channels are collectively referred to as physical channels.
  • downlink physical signals and/or uplink physical signals are collectively referred to as physical signals.
  • BCH, UL-SCH and DL-SCH are transport channels.
  • Channels used in the Medium Access Control (MAC) layer are called transport channels.
  • a transport channel unit used in the MAC layer is also called a transport block (TB) and/or a MAC PDU (Protocol Data Unit).
  • HARQ Hybrid Automatic Repeat reQuest
  • a transport block is the unit of data that the MAC layer delivers to the physical layer.
  • the transport blocks are mapped to codewords and the encoding process is performed codeword by codeword.
  • FIG. 4 shows a half frame (Half frame with SS/PBCH
  • FIG. 10 is a diagram showing an example of a block or an SS burst set).
  • FIG. 4 shows an example in which two SS/PBCH blocks are included in an SS burst set that exists in a constant cycle (which may be referred to as an SSB cycle), and the SS/PBCH block is composed of 4 consecutive OFDM symbols. showing.
  • the SS/PBCH block may be a block containing synchronization signals (PSS, SSS), PBCH and DMRS for PBCH.
  • the SS/PBCH block may be a block containing synchronization signals (PSS, SSS), REDCAP PBCH and DMRS for REDCAP PBCH. Transmitting the signals/channels contained in the SS/PBCH block is referred to as transmitting the SS/PBCH block.
  • the base station apparatus 3 may use an independent downlink transmission beam for each SS/PBCH block. good.
  • PSS, SSS, PBCH and DMRS for PBCH are time/frequency multiplexed in one SS/PBCH block.
  • FIG. 5 is a table showing resources in which PSS, SSS, PBCH and DMRS for PBCH are allocated within the SS/PBCH block.
  • 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 start symbol of the SS/PBCH block).
  • the PSS sequence consists of 127 symbols, and the 57th to 183rd subcarriers in the SS/PBCH block (the subcarriers with subcarrier numbers 56 to 182 relative to the starting subcarrier of the SS/PBCH block) ).
  • 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 starting symbol of the SS/PBCH block).
  • the SSS sequence consists of 127 symbols, and 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).
  • the PBCH and DMRS are the OFDM symbol numbers 1, 2, 3 relative to the 2nd, 3rd, and 4th symbols in the SS/PBCH block (relative to the starting symbol of the SS/PBCH block). symbol).
  • the sequence of modulation symbols for PBCH consists of M symb symbols, the 1st to 240th subcarriers of the 2nd and 4th symbols in the SS/PBCH block (the start of the SS/PBCH block).
  • subcarriers whose subcarrier numbers are 0 to 239 for subcarriers and the 1st to 48th subcarriers and the 184th to 240th subcarriers of the 3rd symbol in the SS/PBCH block (subcarriers whose subcarrier numbers are 0 to 47 and 192 to 239 with respect to the starting subcarrier of the SS/PBCH block), and may be mapped to resources to which DMRS is not mapped.
  • the DMRS symbol sequence consists of 144 symbols, and the 1st to 240th subcarriers of the 2nd and 4th symbols in the SS/PBCH block (starting subcarrier of the SS/PBCH block) subcarriers whose subcarrier numbers are 0 to 239 for the SS/PBCH block), the 1st to 48th subcarriers and the 184th to 240th subcarriers of the 3rd symbol in the SS/PBCH block (SS /subcarriers with subcarrier numbers 0 to 47 and 192 to 239 with respect to the starting subcarrier of the PBCH block), and every four subcarriers may be mapped to one subcarrier. For example, for 240 subcarriers, 180 subcarriers may be mapped with the modulation symbols of the PBCH, and 60 subcarriers may be mapped with the DMRS for the PBCH.
  • Different SS/PBCH blocks within the SS burst set may be assigned different SSB indices.
  • An SS/PBCH block assigned with a certain SSB index may be periodically transmitted by the base station apparatus 3 based on the SSB period.
  • an SSB cycle for the SS/PBCH block to be used for initial access and an SSB cycle to be set for connected (Connected or RRC_Connected) terminal devices 1 may be defined.
  • the SSB cycle set for the connected (Connected or RRC_Connected) terminal device 1 may be set by the RRC parameter.
  • the SSB cycle set for the connected (Connected or RRC_Connected) terminal device 1 is the cycle of radio resources in the time domain that may potentially transmit, and actually the base station device 3 You can decide whether to send it or not.
  • the SSB cycle for using the SS/PBCH block for initial access may be predefined in specifications or the like.
  • the terminal device 1 making initial access may regard the SSB period as 20 milliseconds.
  • the time position of the SS burst set to which the SS/PBCH block is mapped is identified based on information identifying the System Frame Number (SFN) and/or information identifying the half-frame contained in the PBCH. good.
  • the terminal device 1 that has received the SS/PBCH block may identify the current system frame number and half frame based on the received SS/PBCH block.
  • An SS/PBCH block is assigned an SSB index (which may also be referred to as an SS/PBCH block index) according to its temporal position within the SS burst set.
  • the terminal device 1 identifies the SSB index based on the PBCH information and/or the reference signal information included in the detected SS/PBCH block.
  • SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assigned the same SSB index.
  • SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or have the same downlink transmit beam applied).
  • antenna ports in SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.
  • SS/PBCH blocks assigned the same SSB index may be assumed to be QCL in terms of mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation.
  • a configuration corresponding to one or more SS/PBCH blocks (or possibly reference signals) that is a QCL may be referred to as a QCL configuration.
  • the number of SS/PBCH blocks (which may also be referred to as the number of SS blocks or the number of SSBs) is, for example, the number of SS/PBCH blocks within an SS burst, or set of SS bursts, or within a period of SS/PBCH blocks. may be defined. Also, the number of SS/PBCH blocks may indicate the number of beam groups for cell selection within an SS burst, or within an SS burst set, or within a period of an SS/PBCH block.
  • a beam group may be defined as the number of different SS/PBCH blocks or the number of different beams contained within an SS burst, or within an SS burst set, or within a period of an SS/PBCH block (SSB period). .
  • SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assigned the same SSB index.
  • SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL (or have the same downlink transmit beam applied).
  • antenna ports in SS/PBCH blocks with the same relative time within each SS burst set in multiple SS burst sets may be assumed to be QCL with respect to mean delay, Doppler shift, and spatial correlation.
  • SS/PBCH blocks assigned the same SSB index may be assumed to be QCL in terms of mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation.
  • the terminal device 1 in a certain cell, based on the connection state, the execution state of a predetermined timer, received MIB information, and/or received SIB information (which may be SIB1), Determines whether the cell should be considered a "barred" cell.
  • a regulated cell may be a cell in which the terminal device 1 is not permitted to camp on. Cells are barred by indications in system information. For example, terminal device 1 does not camp on a regulated cell. When the terminal device 1 cannot acquire the MIB in a certain cell, the terminal device 1 may regard the cell as a restricted cell.
  • the terminal device 1 may treat a certain cell as a candidate cell in cell selection and cell reselection when the cell is not a regulated cell (the cell status may be indicated as "not barred”). .
  • the terminal device 1 selects and reselects the cell when a certain cell is a regulated cell (when the cell status is indicated as "barred” or when the cell status is treated as “barred”). It is forbidden to select other cells.
  • the terminal device 1 may select/reselect another cell based on the MIB. For example, if the field included in the MIB indicates that selection/reselection of the same frequency is prohibited, the terminal device 1 treats all other cells of the same frequency as regulated cells and does not make them candidates for reselection. can be
  • the terminal device 1 in a certain cell, when the connection state is the RRC idle state (RRC_IDLE), the RRC inactive state (RRC_INACTIVE), or the RRC connected state (RRC_CONNECTED) in which the timer T311 is running, Determine whether to consider the cell as a "barred" cell based on the received MIB.
  • the timer T311 is a timer that is executed during the RRC connection re-establishment procedure, and when the timer expires, the terminal device 1 changes the connection state to the RRC idle state.
  • the terminal device 1 When the value of the parameter cellBarred included in the received MIB in a certain cell is a predetermined value, the terminal device 1 considers the cell to be a regulated cell. However, the parameter cellBarred is a parameter indicating whether the corresponding cell is barred. However, the parameter cellBarred may be ignored when the terminal device 1 is a predetermined terminal device (eg, REDCAP UE). The terminal device 1 may consider the cell to be a regulated cell when the parameter cellBarred-rc different from the parameter cellBarred included in the received MIB has a predetermined value. However, the parameter cellBarred-rc is a parameter indicating whether or not the corresponding cell is barred for a given terminal device (eg, REDCAP UE).
  • the parameter cellBarred-rc may be ignored when the terminal device 1 is other than a predetermined terminal device (eg, REDCAP UE).
  • the information indicated by the parameter cellBarred-rc may be realized by other parameters included in the MIB.
  • the MIB includes a parameter related to setting CORESET0, and if the parameter indicates a predetermined value, the terminal device 1 may consider the cell to be a regulated cell. If none of the parameters included in the received MIB indicates that the terminal device 1 is a regulated cell, the terminal device 1 may apply other parameters included in the MIB (for example, information indicating SFN). good.
  • the terminal device 1 receives SIB1 (REDCAPSIB1, other SIBs may be ) to determine whether the cell is considered a “barred” cell.
  • SIB1 REDCAPSIB1, other SIBs may be
  • the base station device 3 provides the terminal device 1 with an SIB1 including a parameter for determining whether a certain cell of the terminal device 1 is restricted (even if it is another SIB, good).
  • the initial BWP (initial BWP), initial downlink BWP (initial DL BWP), and initial uplink BWP (initial UL BWP) are BWPs used at the time of initial access before RRC connection is established, It may be a downlink BWP and an uplink BWP. However, the initial BWP, initial downlink BWP and initial uplink BWP may be used after the RRC connection is established. However, the initial BWP, the initial downlink BWP, and the initial uplink BWP may be the BWP, downlink BWP, and uplink BWP whose index is 0 (#0), respectively.
  • the initial downlink BWP may be set by the parameters provided in MIB, the parameters provided in SIB1, the parameters provided in SIB and/or the RRC parameters.
  • the initial downlink BWP may be set by the parameter initialDownlinkBWP provided in SIB1.
  • the initialDownlinkBWP may be a parameter indicating the UE-specific (dedicated) setting of the initial downlink BWP for each UE.
  • SIB1 may include downlinkConfigCommon, which is a common downlink configuration parameter for a certain cell. At least one parameter for determining whether or not a certain cell is restricted by the terminal device 1 may be included in downlinkConfigCommon indicating common downlink parameters of a certain cell.
  • downlinkConfigCommon includes a parameter indicating basic parameters for one downlink carrier and transmission in the corresponding cell (for example, referred to as frequencyInfoDL), and a parameter indicating the initial downlink BWP configuration of a serving cell (for example, referred to as initialDownlinkBWP ).
  • SIB1 may include allocationBandwidth, which is a parameter indicating the maximum allocated bandwidth of a cell. allocationBandwidth may be included in any parameter in SIB1.
  • a BWP information element may be a parameter indicating the BWP frequency position and bandwidth.
  • the information elements of the BWP include the parameter subcarrierSpacing indicating the subcarrier spacing used in the BWP, the parameter locationAndBandwidth indicating the position and bandwidth (number of resource blocks (total number)) in the frequency domain of the BWP, and/or standardized in the BWP. It may include a parameter cyclicPrefix that indicates whether CP (cyclic prefix) is used or extended CP is used. That is, BWP may be defined by subcarrier spacing, CP, and location and bandwidth in the frequency domain.
  • the value indicated by locationAndBandwidth may be interpreted as a resource indicator value (RIV: Resource Indicator Value).
  • the resource indicator value indicates the starting PRB index of the BWP and the number of consecutive PRBs.
  • the first PRB that defines the region of the resource indicator value is the subcarrier interval given by subcarrierSpacing of the BWP, and FrequencyInfoDL (or FrequencyInfoDL-SIB) or FrequencyInfoUL (or FrequencyInfoUL-SIB) corresponding to the subcarrier interval.
  • FrequencyInfoDL or FrequencyInfoDL-SIB
  • FrequencyInfoUL or FrequencyInfoUL-SIB
  • the size defining the area of the resource indicator value may be 275.
  • the initialDownlinkBWP includes BWP information elements, PDCCH configuration information elements, and/or PDSCH configuration information elements in the corresponding cell.
  • the initial downlink BWP may be set in the network to include CORESET0 in the frequency domain.
  • the frequencyInfoDL may include a frequencyBandList indicating a list of one or more frequency bands to which the downlink carrier belongs and an SCS-SpecificCarrier list indicating a set of parameters related to the carrier for each subcarrier interval.
  • frequencyInfoUL may include a frequencyBandList indicating a list of one or more frequency bands to which the uplink carrier belongs and an SCS-SpecificCarrier list indicating a set of parameters related to carriers for each subcarrier interval.
  • the SCS-SpecificCarrier may contain parameters indicating the actual carrier position, bandwidth, and carrier bandwidth. More specifically, the information element SCS-SpecificCarrier in frequencyInfoDL indicates settings for a specific carrier and includes subcarrierSpacing, carrierbandwidth and/or offsetToCarrier.
  • subcarrierSpacing is a parameter that indicates the subcarrier spacing of the carrier (for example, FR1 indicates 15 kHz or 30 kHz, and FR2 indicates 60 kHz or 120 kHz).
  • carrierbandwidth is a parameter that indicates the bandwidth of the carrier in terms of the number of PRBs (Physical Resource Blocks).
  • offsetToCarrier is the offset in the frequency domain between reference point A (the lowest subcarrier of common RB0) and the lowest usable subcarrier of that carrier in the number of PRBs (where the subcarrier spacing is subcarrierSpacing is the subcarrier spacing of the carrier given by ).
  • the subcarrier spacing is subcarrierSpacing is the subcarrier spacing of the carrier given by .
  • its carrier bandwidth is given by the upper layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoDL for each subcarrier interval, and its starting position on the frequency is SCS in frequencyInfoDL for each subcarrier interval. It is given by the parameter offsetToCarrier in -SpecificCarrier.
  • an uplink carrier its carrier bandwidth is given by the upper layer parameter carrierbandwidth in SCS-SpecificCarrier in frequencyInfoUL for each subcarrier interval, and its starting position on the frequency is SCS in frequencyInfoUL for each subcarrier interval. It is given by the parameter offsetToCarrier in -SpecificCarrier.
  • 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 interval.
  • Information indicating the maximum allocated bandwidth may be indicated by an information element including a parameter subcarrierSpacing indicating subcarrier spacing and a parameter allocationBandwidth indicating the number of resource blocks of the bandwidth.
  • the maximum allocated bandwidth may be the maximum bandwidth supported by the RF circuit provided in the terminal device 1.
  • the maximum bandwidth may be the maximum bandwidth over which signals/channels transmitted on the downlink and/or uplink, respectively, can be scheduled simultaneously. When signals/channels are scheduled discretely on frequency in the downlink and/or uplink, the maximum allocated bandwidth is the bandwidth of frequency resources in which the signals/channels can be discretely allocated at a certain time. you can
  • allocationBandwidth may be a parameter included in the SCS-SpecificCarrier information element.
  • the information indicating the maximum allocation bandwidth indicated by allocationBandwidth may be the number (total number) of resource blocks corresponding to the subcarrier spacing indicated by subcarrierSpacing of the SCS-SpecificCarrier information element including 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 SCS-SpecificCarrier.
  • allocationBandwidth may be a parameter included in the BWP information element.
  • Information indicating the maximum allocation bandwidth indicated by allocationBandwidth may be the number (total number) of resource blocks corresponding to the subcarrier interval indicated by subcarrierSpacing of the information element of the BWP including the parameter.
  • the information indicating the maximum allocated bandwidth may be information specifying the maximum allocated bandwidth by a ratio value to the BWP bandwidth indicated by locationAndBandwidth included in the corresponding BWP information element.
  • allocationBandwidth may be a parameter set for each BWP.
  • the allocationBandwidth may be set as a common parameter for information indicating the maximum allocated bandwidth of the downlink in a certain cell and information indicating the maximum allocated bandwidth for the uplink, or may be set as individual parameters. (For example, they may be referred to as dlAllocationBandwidth and ulAllocationBandwidth, respectively).
  • the initial downlink BWP is the PRB (Physical Resource 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, and the SCS (SubCarrier Spacing) and cyclic prefix of the PDCCH received by CORESET of the Type0-PDCCH CSS Set.
  • the initial downlink BWP may be determined/identified by the initialDownlinkBWP.
  • initialDownlinkBWP may be a state in which initialDownlinkBWP is received in RRC parameters and an RRC connection is established (for example, RRCSetup, RRCResume and/or RRCReestablishment are received).
  • RRCSetup, RRCResume and/or RRCReestablishment are received.
  • the terminal device 1 may use CORESET0 as the initial downlink BWP until it receives RRCSetup, RRCResume, or RRCReestablishment.
  • making CORESET0 the initial downlink BWP means determining/identifying 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.
  • determining/identifying the initial downlink BWP may be determining/identifying the frequency position and/or the bandwidth of the initial downlink BWP.
  • the terminal device 1 may determine/identify the initial downlink BWP with locationAndBandwidth included in the received initialDownlinkBWP.
  • the terminal device 1 When the terminal device 1 receives the initialDownlinkBWP in SIB1, it specifies the initial downlink BWP in CORESET0 until the RRC connection is established, and after the RRC connection is established, the initial downlink BWP is specified in locationAndBandwidth included in the initialDownlinkBWP. May be determined/specified.
  • RRCSetup may be a message received from the base station device 3 (which may be the network) when the terminal device 1 transmits an RRCSetupRequest message to the base station device 3 (which may be the network).
  • the base station device 3 (which may be a network) may transmit an RRCSetup message to the terminal device 1 when the RRC connection with the terminal device 1 is established.
  • RRCResume is a message received from the base station device 3 (which may be the network) when the terminal device 1 transmits the RRCResumeRequest message or the RRCResumeRequest1 message to the base station device 3 (which may be the network). you can The base station device 3 (which may be a network) may transmit an RRC Resume message to the terminal device 1 when the RRC connection with the terminal device 1 is resumed.
  • RRCReestablishment may be a message received from the base station device 3 (which may be the network) when the terminal device 1 transmits an RRCReestablishmentRequest message to the base station device 3 (which may be the network).
  • the base station device 3 (which may be a network) may transmit an RRCReestablishment message to the terminal device 1 when the RRC connection with the terminal device 1 is reestablished.
  • the initial uplink BWP may be set by parameters provided in MIB, parameters provided in SIB1, parameters provided in SIB, or RRC parameters.
  • the initial uplink BWP may be set by the parameter initialUplinkBWP provided in SIB1.
  • the initialUplinkBWP is a parameter indicating the UE-specific (dedicated) setting of the initial uplink BWP for each UE.
  • the initial uplink BWP may be defined/configured in initialUplinkBWP provided in SIB1 (REDCAP SIB1, other SIBs, may be RRC parameters).
  • the terminal device 1 may determine the initial uplink BWP based on the initialUplinkBWP provided by the received SIB1.
  • the terminal device 1 has an RF circuit between its own antenna and a signal processing unit that processes the baseband signal.
  • the RF circuit mainly includes a signal processor, power amplifier, antenna switch, filter, and the like.
  • the signal processing section of the RF circuit demodulates the RF signal received through the filter and performs processing for outputting the received signal to the signal processing section.
  • the high-frequency signal processing section of the RF circuit modulates the carrier wave signal, generates the RF signal, amplifies the power with the power amplifier, and then outputs the signal to the antenna.
  • the antenna switch connects the antenna and the filter during signal reception, and connects the antenna and the power amplifier during signal transmission.
  • the RF circuit within the initial downlink BWP may be tuning/retuning the frequency band to which is applied. Adjusting/readjusting the frequency band to which RF circuitry is applied may be referred to as RF tuning/RF retuning.
  • FIG. 6 is a diagram showing an example of RF retuning. In FIG. 6, when the applicable band of the RF circuit used in the terminal device 1 is out of the band of the downlink channel received within the initial downlink BWP, the terminal device 1 receives the downlink channel that receives the applicable band of the RF circuit.
  • RF retuning is performed to include the band of
  • the RF circuit within the initial uplink BWP may be tuning/retuning the frequency band to which is applied.
  • the terminal device 1 applies the RF circuit within the downlink BWP. You may adjust/readjust the frequency band to be used.
  • the terminal device 1 uses the RF circuit within the uplink BWP.
  • the applied frequency band may be adjusted/readjusted.
  • Terminal device 1 may be configured with multiple initial downlink sub-BWPs by SIB1. At least one of the multiple initial downlink sub-BWPs may be configured to include the 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 SS/PBCH block (cell-defining SSB)) as an initial downlink BWP. At least one of the multiple initial downlink sub-BWPs may be configured to include CORESET0. All of the multiple initial downlink sub-BWPs may be configured to include their respective CORESET0. The terminal device 1 may operate considering the initial downlink sub-BWP including CORESET0 as the initial downlink BWP.
  • an initial downlink sub-BWP including an SS/PBCH block such as a cell-defining SS/PBCH block (cell-defining SSB)
  • All of the multiple initial downlink sub-BWPs may be configured to include their respective CORESET0.
  • the terminal device 1 may operate considering the initial downlink sub-BWP as the initial downlink BWP.
  • Multiple initial downlink sub-BWPs may be regarded as multiple initial downlink BWPs.
  • Multiple initial downlink sub-BWPs may be designed to be included in the frequency band of one initial downlink BWP.
  • the initial downlink sub-BWP may also be called a downlink BWP or a downlink sub-BWP.
  • "setting/identifying the initial downlink BWP" may mean setting/identifying the frequency position and/or the bandwidth of the initial downlink BWP.
  • the base station device 3 broadcasts information including setting of a plurality of frequency positions and/or a plurality of bandwidths of the initial downlink BWP, and the terminal device 1 sets the frequency position and bandwidth of the initial downlink BWP based on the information. may be determined/specified/set.
  • the terminal device 1 receives/identifies the setting information of the initial downlink BWP with the upper layer parameter initialDownlinkBWP.
  • the initialDownlinkBWP may be included in SIB1 or may be included in any RRC message.
  • initial downlink BWP configuration information may include information indicating the frequency position and bandwidth of the initial downlink BWP.
  • the terminal device 1 may receive SIB1 or any RRC signaling containing multiple configuration information for the initial downlink BWP. Multiple initial downlink BWP configuration information may be included in one parameter initialDownlinkBWP.
  • FIG. 7 shows an example of the parameter configuration of the initialDownlinkBWP information element (IE) BWP-DownlinkCommon according to this embodiment.
  • the initialDownlinkBWP includes general parameters genericParameters of the initial downlink BWP, cell-specific PDCCH cell-specific parameters pdcch-ConfigCommon, cell-specific PDSCH parameters pdsch-ConfigCommon, and the second initial downlink BWP.
  • a parameter indicating configuration information and/or a parameter initialBwpTiming indicating timing for applying the second configuration information of the initial downlink BWP may be included.
  • the parameter indicating the second setting information of the initial downlink BWP may be the parameter locationAndBandwidth-rc indicating the second "frequency position and bandwidth" of the initial downlink BWP.
  • the initial downlink BWP determined/identified by locationAndBandwidth-rc is called a separate initial downlink BWP (separate initial DL BWP/separated initial DL BWP) to distinguish it from the initial downlink BWP determined/identified by locationAndBandwidth. May be.
  • genericParameters in initialDownlinkBWP may be parameters common to the plurality of initial downlink BWPs (or configuration information of the plurality of frequency positions and/or the plurality of bandwidths of the initial downlink BWPs).
  • 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.
  • the parameter locationAndBandwidth-rc indicating the second “frequency location and bandwidth” of the initial downlink BWP may be included in any other information element/parameter within the SIB.
  • the parameter locationAndBandwidth-rc is described as a parameter included in the initialDownlinkBWP, but the same function is realized when included in SIB1, other SIBs, or other information elements/parameters in RRC signaling. can.
  • locationAndBandwidth-rc may be a parameter included in the parameter separateInitialDownlinkBWP.
  • separateInitialDownlinkBWP may be a parameter sent in SIB1.
  • separateInitialDownlinkBWP may be a parameter sent in an SIB other than SIB1.
  • separateInitialDownlinkBWP may be a parameter sent in RRC signaling.
  • separateInitialDownlinkBWP may be a parameter including configuration information for the second initial downlink BWP (which may be a separate initial downlink BWP) identified by locationAndBandwidth-rc.
  • separateInitialDownlinkBWP may be a parameter that includes some or all of the parameter configuration of the initialDownlinkBWP, and each parameter may be a second initial downlink BWP (which may be a separate initial downlink BWP) specified by locationAndBandwidth-rc. It may be setting information for
  • the genericParameters included in the initialDownlinkBWP consist of an information element (IE) BWP, the parameter locationAndBandwidth indicating the frequency position and bandwidth of the initial downlink BWP, and the subcarrier spacing used in all channels and reference signals in the initial downlink BWP.
  • parameter subcarrierSpacing to indicate
  • parameter cyclicPrefix to indicate whether an extended cyclic prefix (CP) is used in the initial downlink BWP.
  • CP extended cyclic prefix
  • the subcarrierSpacing included in genericParameters in the initialDownlinkBWP is set in the first "frequency position and bandwidth". It may be a parameter indicating the subcarrier spacing used in all channels and reference signals in the downlink BWP, or all channels and common to the initial downlink BWP set with different "frequency positions and bandwidths" It may be a parameter indicating the subcarrier spacing used in the reference signal.
  • the terminal device 1 regardless of whether or not SIB1 (which may be other SIBs or RRC signaling) includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc), Based on subcarrierSpacing included in genericParameters in the initialDownlinkBWP, the subcarrier spacing used in all channels (eg, PDCCH, PDSCH) and reference signals in the initial downlink BWP may be determined/specified. However, when multiple "frequency positions and bandwidths" of the initial downlink BWP are set in a certain cell, the cyclicPrefix included in genericParameters in the initialDownlinkBWP is set in the first "frequency position and bandwidth".
  • SIB1 which may be other SIBs or RRC signaling
  • the value indicated by locationAndBandwidth included in genericParameters in the initialDownlinkBWP is interpreted as a Resource Indicator Value (RIV).
  • RIV is an index indicating the starting 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 index value.
  • the subcarrier spacing of the initial downlink BWP indicated by subcarrierSpacing included in genericParameters in the initialDownlinkBWP may be set to the same value as the subcarrier spacing indicated by the MIB of the same cell. If cyclicPrefix is not included in genericParameters (is not set), terminal device 1 may use standard CP instead of extended CP.
  • the parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating multiple "frequency positions and bandwidths" for the initial downlink BWP are information for setting multiple initial downlink BWPs with different frequency positions and/or bandwidths. good too.
  • the parameters (locationAndBandwidth and locationAndBandwidth-rc) indicating multiple "frequency positions and bandwidths" for the initial downlink BWP may be information indicating multiple "frequency positions and bandwidths" for the initial downlink BWP. .
  • the parameter locationAndBandwidth-rc indicating the second “frequency position and bandwidth” of the initial downlink BWP is configured not to be included in the genericParameters in the initialDownlinkBWP, which is the general parameter of the initial downlink.
  • locationAndBandwidth-rc may be included in genericParameters in initialDownlinkBWP.
  • the initial downlink BWP set by the parameter locationAndBandwidth-rc may be called a separate initial downlink BWP to distinguish it from the MIB or the initial downlink BWP set by the parameter locationAndBandwidth.
  • the pdcch-ConfigCommon included in the initialDownlinkBWP contains the parameter controlResourceSetZero of CORESET0 used in the common search space or UE-specific search space, the parameter commonControlResourceSet of additional common CORESET used in the common search space or UE-specific search space, the common search space 0 (common parameter searchSpaceZero for search space #0), parameter commonSearchSpaceList indicating a list of common search spaces other than common search space 0, parameter searchSpaceSIB1 indicating the ID of the search space for SIB1 messages, ID of the search space for other system information , a parameter pagingSearchSpace indicating the ID of the search space for paging, and/or a parameter ra-SearchSpace indicating the ID of the search space for the random access procedure.
  • ControlResourceSetZero is set to a value between 0 and 15. However, the number of values that can be set in ControlResourceSetZero may be other than 16, and may be 32, for example. Any value from 0 to 15 is set to the information element SearchSpaceZero indicated by searchSpaceZero. However, the number of values that can be set for SearchSpaceZero may be other than 16, and may be 32, for example.
  • the terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET0 from controlResourceSetZero in pdcch-ConfigCommon. However, the value indicated by controlResourceSetZero is applied to a given table as an index. However, the terminal device 1 may determine the table to apply based on the supported UE category and/or UE Capability. However, the terminal device 1 may determine the table to apply based on the minimum channel bandwidth. However, the terminal device 1 may determine the table to apply based on the subcarrier interval of the SS/PBCH block and/or the subcarrier interval of CORESET0.
  • Each row of the table to which the value of controlResourceSetZero is applied as an index contains the index indicated by controlResourceSetZero, the multiplexing pattern of PBCH and CORESET, the number of RBs (which may be PRBs) in CORESET0, the number of symbols in CORESET0, the offset and/or the PDCCH. may be indicated.
  • the multiplex pattern of PBCH and CORESET shows the pattern of the frequency/time position relationship of the SS/PBCH block corresponding to the PBCH that detected the MIB and the corresponding CORESET0. For example, if the multiplexing pattern of PBCH and CORESET is 1, PBCH and CORESET are time-multiplexed in different symbols.
  • the number of RBs of CORESET0 indicates the number of resource blocks that are continuously allocated to CORESET0.
  • the number of symbols of CORESET0 indicates the number of symbols consecutively assigned to CORESET0.
  • Offset indicates the offset from the lowest RB index of the resource block assigned to CORESET0 to the lowest RB index of the common resource block where the first resource block of the corresponding REDCAP PBCH overlaps.
  • the offset may indicate the offset from the lowest RB index of the resource block assigned to CORESET0 to the lowest RB index of the common resource block where the first resource block of the corresponding SS/PBCH block overlaps.
  • Terminal device 1 receives initialDownlinkBWP including RRC parameter pdcch-ConfigCommon via SIB1 or RRC signaling, and monitors PDCCH based on the parameter.
  • Terminal device 1 determines PDCCH monitoring opportunities from searchSpaceZero in pdcch-ConfigCommon. However, the value indicated by searchSpaceZero is applied to a given table as an index. However, the terminal device 1 may determine the table to apply based on the supported UE category and/or UE Capability. However, the terminal device 1 may determine the table to apply based on the frequency range.
  • the terminal device 1 monitors PDCCH with the type 0-PDCCH common search space set (Type0-PDCCH CSS Set) over two consecutive slots starting from slot n0.
  • the terminal device 1 determines n0 and the system frame number based on the parameter O and the parameter M shown in the table in the SS/PBCH block whose index is i.
  • the pdcch-ConfigCommon included in the initialDownlinkBWP or each parameter of the pdcch-ConfigCommon is the cell-specific (cell -specific) parameters, or PDCCH cell-specific parameters that are common to initial downlink BWPs configured with different “frequency locations and bandwidths”.
  • the terminal device 1 regardless of whether or not SIB1 (which may be other SIBs or RRC signaling) includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc),
  • the cell-specific parameters of the PDCCH in the initial downlink BWP may be determined/specified based on the pdcch-ConfigCommon included in the initialDownlinkBWP or a partial parameter of the pdcch-ConfigCommon.
  • pdsch-ConfigCommon included in the initialDownlinkBWP may include the parameter pdsch-TimeDomainAllocationList that indicates a list of time domain settings for the timing of downlink allocation for downlink data.
  • pdsch-ConfigCommon included in the initialDownlinkBWP or each parameter of the pdsch-ConfigCommon is a PDSCH cell-specific (cell -specific) parameter, or it may be a PDSCH cell-specific parameter that is common to initial downlink BWPs configured with different “frequency locations and bandwidths”.
  • the terminal device 1 regardless of whether or not SIB1 (which may be other SIBs or RRC signaling) includes the second "frequency location and bandwidth" configuration information (locationAndBandwidth-rc), PDSCH cell-specific parameters in the initial downlink BWP may be determined/specified based on the pdsch-ConfigCommon included in the initialDownlinkBWP or a partial parameter of the pdsch-ConfigCommon.
  • SIB1 which may be other SIBs or RRC signaling
  • locationAndBandwidth-rc locationAndBandwidth-rc
  • RIV Resource Indicator Value
  • Bandwidth can be specified.
  • the terminal device 1 does not include locationAndBandwidth-rc in SIB1 (which may be other SIBs or RRC signaling), the frequency location and band of the initial downlink BWP based on locationAndBandwidth included in genericParameters in initialDownlinkBWP A width may be specified/determined. If locationAndBandwidth-rc is included in SIB1 (other SIBs or RRC signaling), terminal device 1 identifies/determines the frequency location and bandwidth of the initial downlink BWP based on locationAndBandwidth-rc. You may
  • the terminal device 1 that does not support the frequency position and / or bandwidth of the first initial downlink BWP, the second initial downlink from locationAndBandwidth-rc included in SIB1 (other SIBs, or may be RRC signaling) By identifying/determining the link BWP, the downlink channel and downlink signal transmitted from the base station device 3 can be received.
  • the base station apparatus 3 sets the initial downlink BWP of the frequency position and/or bandwidth not supported by the specific terminal apparatus 1 with locationAndBandwidth
  • the base station apparatus 3 sets the initial downlink BWP of the frequency position and/or bandwidth supported by the terminal apparatus 1.
  • the base station apparatus 3 includes locationAndBandwidth-rc in SIB1 (other SIBs or RRC signaling), so that the terminal apparatus does not support the frequency location and/or bandwidth of the first initial downlink BWP.
  • a downlink channel and a reference signal corresponding to the first initial downlink BWP can be transmitted.
  • SIB1 other SIBs, or may be RRC signaling
  • SIB1 may not include locationAndBandwidth-rc.
  • the terminal device 1 uses subcarrierSpacing included in genericParameters in the initialDownlinkBWP regardless of whether locationAndBandwidth-rc is included in SIB1 (which may be other SIBs or RRC signaling) to perform the initial downlink
  • the subcarrier spacing used for all channels and reference signals in the BWP may be specified/determined.
  • terminal device 1 uses cyclicPrefix included in genericParameters in initialDownlinkBWP to perform initial downlink It may be specified/determined if the extended cyclic prefix CP is used in the BWP.
  • the terminal device 1 uses pdcch-ConfigCommon included in the initialDownlinkBWP regardless of whether locationAndBandwidth-rc is included in SIB1 (which may be other SIBs or RRC signaling), the initial downlink BWP may identify/determine cell-specific parameters for the PDCCH in , and monitor/receive the PDCCH.
  • Terminal device 1 sets the initial downlink BWP using pdsch-ConfigCommon included in initialDownlinkBWP regardless of whether locationAndBandwidth-rc is included in SIB1 (which may be other SIBs or RRC signaling). may identify/determine the cell-specific parameters of the PDSCH in , and receive the PDSCH.
  • the terminal device 1 receives locationAndBandwidth-rc included in SIB1 (may be another SIB), and based on the locationAndBandwidth-rc, the initial downlink BWP (which may be referred to as a separate initial downlink BWP).
  • CORESET0 is the initial downlink BWP until the RRC connection is established, re-established or re-established (e.g. before receiving RRCSetup, RRCResume or RRCReestablishment) and the RRC connection is established.
  • the initial downlink BWP may be determined/identified by locationAndBandwidth-rc contained in the received SIB1 (which may be another SIB).
  • the terminal device 1 may perform the random access procedure using the initial downlink BWP determined/identified by CORESET0.
  • the terminal device 1 receives locationAndBandwidth-rc included in SIB1 (may be another SIB), and based on the locationAndBandwidth-rc, the initial downlink BWP (which may be referred to as a separate initial downlink BWP).
  • CORESET0 is the initial downlink BWP until the SIB1 is received, and after SIB1 (or other SIBs) is received, the received SIB1 is used.
  • the initial downlink BWP may be determined/specified in the included locationAndBandwidth-rc.
  • the terminal device 1 determines/identifies the initial downlink BWP determined/identified by locationAndBandwidth-rc.
  • a random access procedure may be performed using the BWP.
  • the terminal device 1 sets an initial downlink BWP (also referred to as separate initial downlink BWP) based on locationAndBandwidth-rc included in SIB1, based on information included in SIB1 (which may be another SIB). ) may be switched.
  • the parameter initialBwpTiming indicating the timing to apply locationAndBandwidth-rc included in SIB1 (or other SIBs) may be 1-bit information.
  • initialBwpTiming determines/specifies/applies the frequency location and bandwidth indicated by locationAndBandwidth-rc as the initial downlink BWP frequency location and bandwidth before RRC connection is established (before receiving RRCSetup/RRCResume/RRCReestablishment) It may be information indicating whether or not.
  • 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 , the initial access may be made at the frequency location and bandwidth indicated by the locationAndBandwidth-rc.
  • terminal device 1 is The PDCCH, random access response and/or PDSCH may be received on frequency resources based on the frequency location and bandwidth indicated by locationAndBandwidth-rc.
  • initialBwpTiming determines/identifies/applies the frequency position and bandwidth indicated by locationAndBandwidth-rc as the frequency position and bandwidth of the initial downlink BWP at the timing when the RRC connection is established, or at the timing when SIB1 is received.
  • the information may indicate whether to apply the downlink BWP frequency position and bandwidth.
  • the terminal device 1 may switch the timing for determining/identifying the initial downlink BWP based on locationAndBandwidth-rc included in SIB1 (or other SIBs), depending on the value of initialBwpTiming. For example, when initialBwpTiming is the first value, CORESET0 is set as the initial downlink BWP until the SIB1 is received, and after the SIB1 is received, locationAndBandwidth-rc included in the received SIB1 is used as the initial downlink BWP.
  • BWP may be determined/identified and CORESET0 is initialized until the RRC connection is established, re-established or resumed (e.g., before receiving RRCSetup, RRCResume or RRCReestablishment) if initialBwpTiming is a second value.
  • the locationAndBandwidth-rc included in the received SIB1 may be used to determine/identify the initial downlink BWP.
  • the terminal device 1 may switch the timing for determining/identifying the initial downlink BWP depending on whether the parameter initialBwpTiming is included in SIB1 or not (absent).
  • CORESET0 is set as the initial downlink BWP until the SIB1 is received, and after the SIB1 is received.
  • the initial downlink BWP may be determined/identified by locationAndBandwidth-rc included in the received SIB1.
  • CORESET0 will be set until the RRC connection is established, reestablished, or restarted (e.g., before receiving RRCSetup, RRCResume, or RRCReestablishment).
  • the locationAndBandwidth-rc included in the received SIB1 may be used to determine/identify the initial downlink BWP.
  • initialBwpTiming is described as a parameter that can be included in SIB1, but it may be a parameter that can be included in other SIBs or RRC signaling.
  • initialBwpTiming may be a parameter that may be included in the RRC parameter initialDownlinkBWP, which may be included in SIB1 (which may be other SIB or RRC parameters).
  • a separate initial downlink BWP having a different frequency position and/or bandwidth from the first initial downlink BWP When (second initial downlink BWP) is set, the band of the separate initial downlink BWP may not include the synchronization signal block transmitted within the band of the first initial downlink BWP. If a separate initial downlink BWP requires a signal that has the role of a synchronization signal block for paging, random access and/or other uses, an additional synchronization signal block (hereinafter referred to as additional synchronization signal blocks (referred to as additional SSBs).
  • additional synchronization signal blocks hereinafter referred to as additional synchronization signal blocks (referred to as additional SSBs).
  • the base station apparatus 3 may transmit additional synchronization signal blocks within the band of the second initial downlink BWP (separate initial downlink BWP) identified/determined by locationAndBandwidth-rc.
  • the terminal device 1 may receive additional synchronization signal blocks sent within the band of the separate initial downlink BWP identified/determined from locationAndBandwidth-rc.
  • the additional synchronization signal block may be a synchronization signal block (referred to as NCD-SSB: Non-Cell Defining SSB) that is not a synchronization signal block that defines a cell (referred to as CD-SSB: Cell Defining SSB).
  • the additional synchronization signal block may not be centered on the Synchronization Raster.
  • the terminal device 1 needs to identify the frequency position of the additional synchronization signal block.
  • the base station apparatus 3 sets the information/parameter ssbFrequencyOffset-rc for specifying the frequency position of the additional synchronization signal block to be transmitted within the band of the second initial downlink BWP specified/determined from locationAndBandwidth-rc to SIB1 ( other SIB or RRC signaling).
  • Terminal device 1 based on the information / parameter ssbFrequencyOffset-rc included in SIB1 (may be other SIB or RRC signaling), within the band of the separate initial downlink BWP identified / determined from locationAndBandwidth-rc
  • the frequency location of additional synchronization signal blocks to be transmitted may be identified. For example, by applying the frequency position range 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, the information amount of ssbFrequencyOffset-rc is reduced. be able to.
  • ssbFrequencyOffset-rc may be the frequency offset from the reference frequency position of the second initial downlink BWP identified/determined from locationAndBandwidth-rc to the reference frequency position of the additional synchronization signal block.
  • the reference frequency position of the second initial downlink BWP is the lowest frequency PRB containing the second initial downlink BWP (a PRB with an index of 0, which may be referred to as PRB0) or It may be the CRB with the lowest frequency including the second initial downlink BWP.
  • the reference frequency position of the second initial downlink BWP may be the subcarrier with the lowest frequency of the second initial downlink BWP (the subcarrier whose index in PRB0 is 0. The subcarrier of PRB0 0).
  • the reference frequency position of the second initial downlink BWP may be a PRB or CRB containing the center frequency of the second initial downlink BWP.
  • the reference frequency position of the second initial downlink BWP may be a subcarrier of the center frequency of the second initial downlink BWP.
  • the reference frequency position of the additional synchronization signal block may be the lowest frequency PRB or CRB that includes the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be the lowest frequency subcarrier of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be the subcarrier with index 0 of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be PRB or CRB containing the center frequency of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be a subcarrier containing the center frequency of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block is the subcarrier of index 119 or 120 of the additional synchronization signal block. good.
  • ssbFrequencyOffset-rc may be the frequency offset from the reference frequency position in the carrier to the reference frequency position of the additional synchronization signal block.
  • the reference frequency position within the carrier may be Point A (CRB whose index is 0 (CRB0)).
  • the value indicated by ssbFrequencyOffset-rc may be the CRB number.
  • the value indicated by ssbFrequencyOffset-rc may be the number of the CRB with the smallest index including the additional synchronization signal block. In this case, it can be interpreted that the index of the CRB with the smallest index including the additional synchronization signal block simply designates the CRB number instead of the offset.
  • ssbFrequencyOffset-rc is a parameter indicating the index of the CRB with the smallest index including the additional synchronization signal block, and the index of the subcarrier with the lowest frequency among the subcarriers to which the additional synchronization signal block is assigned within the CRB (0 to 11). (which may be referred to as the subcarrier offset within the CRB).
  • the CRB index indicated by ssbFrequencyOffset-rc is the CRB ⁇ index corresponding to the subcarrier interval ⁇ . When denoting ssbFrequencyOffset-rc, this ⁇ may be the subcarrier spacing setting of the synchronization signal block common in the cell.
  • the subcarrier interval setting ⁇ corresponding to the CRB number may be the subcarrier interval setting ⁇ of the synchronization signal block common to the cells.
  • the CRB number indicated by ssbFrequencyOffset-rc may be the number of CRB ⁇ based on the subcarrier interval setting ⁇ of the synchronization signal block common in the cell.
  • the subcarrier interval setting ⁇ corresponding to the CRB number is the synchronization signal block (which may be CD-SSB) transmitted within the band of the initial downlink BWP. subcarrier spacing setting ⁇ .
  • the subcarrier interval setting ⁇ corresponding to the CRB number is the subcarrier of the additional synchronization signal block (which may be NCD-SSB) received in the separate initial downlink BWP. It may be the carrier spacing setting ⁇ .
  • the CRB number is indicated by ssbFrequencyOffset-rc
  • information on the subcarrier interval setting ⁇ corresponding to the CRB number may be indicated by MIB (SIB1, other SIBs, or RRC signaling). .
  • ssbFrequencyOffset-rc may be a frequency offset from the reference frequency position of the synchronization signal block transmitted within the band of the initial downlink BWP to the reference frequency position of the additional synchronization signal block transmitted within the separate initial downlink BWP.
  • the reference frequency position of the synchronization signal block may be the lowest frequency PRB or CRB containing the synchronization signal block.
  • the reference frequency position of the synchronization signal block may be the lowest frequency subcarrier of the synchronization signal block.
  • the reference frequency position of the synchronization signal block may be PRB or CRB containing the center frequency of the synchronization signal block.
  • the reference frequency position of the synchronization signal block may be a subcarrier of the center frequency of the synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be the lowest frequency PRB or CRB that includes the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be the lowest frequency subcarrier of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be PRB or CRB containing the center frequency of the additional synchronization signal block.
  • the reference frequency position of the additional synchronization signal block may be a subcarrier of the center frequency of the additional synchronization signal block.
  • FIG. 8 is a diagram showing an overview of frequency positions of additional synchronization signal blocks according to this embodiment.
  • two initial downlink BWPs an initial downlink BWP (initial DL BWP) and a separate initial downlink BWP (separate initial DL BWP), are set in a certain cell.
  • the initial downlink BWP may be the CORESET0 band.
  • the initial downlink BWP includes PDSCH (PDSCH with SIB1) including at least a synchronization signal block (SSB), CORESET0, and SIB1 within the band.
  • the separate initial downlink BWP includes at least an additional synchronization signal block (additional SSB) within the band.
  • the terminal device 1 that has received the synchronization signal block identifies the frequency position of CORESET0, and identifies the frequency position and time position of the PDSCH including SIB1 from the PDCCH received on CORESET0.
  • the terminal device 1 that has received the PDSCH containing SIB1 uses the parameter locationAndBandwidth-rc included in SIB1 (or other SIBs specified by the SIB1) to set the frequency position (bandwidth ) to identify/determine
  • the terminal device 1 that has identified/determined the frequency position of the separate initial downlink BWP uses the parameter ssbFrequencyOffset-rc included in SIB1 (or another SIB identified by the SIB1) to use the separate initial downlink It can locate/determine the frequency of additional synchronization signal blocks transmitted within the BWP and receive the additional synchronization signal blocks.
  • the value indicated by ssbFrequencyOffset-rc may be the frequency offset in subcarrier units.
  • 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 units of ARFCN (Absolute radio-frequency channel number).
  • ssbFrequencyOffset-rc may be a combination of a parameter indicating a frequency offset in resource block units and a frequency offset in subcarrier units.
  • rb-offset included in ssbFrequencyOffset-rc indicates a frequency offset for each resource block of 12 or more subcarriers
  • sc-offset included in ssbFrequencyOffset-rc indicates a frequency offset for each subcarrier of less than 12 subcarriers.
  • the subcarrier spacing setting ⁇ ) may be the subcarrier spacing setting ⁇ of the synchronization signal block common to the cell.
  • subcarriers that are the unit of frequency offset indicated by ssbFrequencyOffset-rc or subcarrier interval setting ⁇ (of frequency offset that is indicated by ssbFrequencyOffset-rc) associated with resource blocks that are the unit of frequency offset indicated by ssbFrequencyOffset-rc
  • the subcarrier spacing setting ⁇ ) may be the subcarrier spacing setting ⁇ of the additional synchronization signal block transmitted in the separate initial downlink BWP.
  • the subcarrier spacing setting ⁇ of the frequency offset indicated by ssbFrequencyOffset-rc may be the subcarrier spacing of the corresponding additional synchronization signal block.
  • the subcarrier interval setting ⁇ of the frequency offset indicated by ssbFrequencyOffset-rc may be the subcarrier interval setting ⁇ of the corresponding separate initial downlink BWP.
  • the terminal device 1 determines 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. / may be specified.
  • the terminal device 1 selects the narrower subcarrier interval between the subcarrier interval setting ⁇ 1 of the corresponding additional synchronization signal block and the subcarrier interval setting ⁇ 2 of the separate initial downlink BWP as the subcarrier of the frequency offset indicated by ssbFrequencyOffset-rc. It may be determined/specified as an interval setting ⁇ .
  • 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) containing the MIB containing scheduling information for SIB1 including ssbFrequencyOffset-rc. do not have.
  • the terminal device 1 based on the subcarrier interval setting ⁇ 3 of the synchronization signal block containing the scheduling information of SIB1 and/or the subcarrier interval setting ⁇ 4 of the separate initial downlink BWP, subcarriers of the frequency offset indicated by ssbFrequencyOffset-rc A spacing setting ⁇ may be determined/specified.
  • parameter offsetToPointA As the information format used for ssbFrequencyOffset-rc.
  • the parameter offsetToPointA used for the sync signal block that is CD-SSB specifies point A from the frequency position of the sync signal block using the parameter offsetToPointA, but for the additional sync signal block that is NCD-SSB When used, the frequency position of the additional synchronization signal block is specified from point A already specified.
  • FIG. 9 is a flow diagram showing an example of processing related to determining/identifying the frequency position of the additional synchronization signal block in the terminal device 1 of this embodiment.
  • the terminal device 1 uses SIB1 (which may be another SIB) including offset information ssbFrequencyOffset-rc that identifies the frequency position of the additional synchronization signal block in the second initial downlink BWP. receive.
  • the terminal device 1 identifies the frequency position of the additional synchronization signal block based on the received ssbFrequencyOffset-rc.
  • the terminal device 1 receives locationAndBandwidth-rc in SIB1, identifies the frequency position of the second initial downlink BWP based on the received locationAndBandwidth-rc, and uses the reference frequency of the second initial downlink BWP.
  • the position-based received ssbFrequencyOffset-rc may be applied to identify the reference frequency position of the additional sync signal block.
  • the terminal device 1 receives an additional synchronization signal block at the identified frequency position.
  • the base station apparatus 3 sends information/parameters for the terminal apparatus 1 to specify the subcarrier spacing (which may be the subcarrier spacing setting ⁇ ) of the additional synchronization signal block to SIB1 (or other SIB or RRC signaling). may be sent to the terminal device 1.
  • the terminal device 1 may identify the subcarrier spacing of the additional synchronization signal block based on information/parameters included in SIB1 (which may be other SIBs or RRC signaling) received from the base station device 3. .
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be 1-bit information ssbSubcarrierSpacing.
  • ssbSubcarrierSpacing is a parameter that indicates 15 kHz or 30 kHz when the frequency range in which the parameter is received is frequency range 1 (FR1: Frequency Range 1), and 120 kHz when it is frequency range 2 (FR2). or 240kHz.
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be subcarrierSpacing included in genericParameters in the initialDownlinkBWP.
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be the 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).
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block indicates the subcarrier spacing of all channels and reference signals within the second initial downlink BWP (which may be a separate initial downlink BWP).
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be the parameter subcarrierSpacing included in the separateInitialDownlinkBWP containing the configuration information of the second initial downlink BWP.
  • the subcarrier spacing of additional synchronization signal blocks may be the same as the subcarrier spacing of synchronization signal blocks transmitted in the first initial downlink BWP.
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be the parameter subcarrierSpacing, which indicates the subcarrier spacing of all channels and reference signals within the first initial downlink BWP.
  • the information/parameter for specifying the subcarrier spacing of the additional synchronization signal block may be the parameter subcarrierSpacing included in the initialDownlinkBWP containing the configuration information of the first initial downlink BWP.
  • FIG. 10 is a flowchart showing an example of processing related to determination/specification of subcarrier intervals for additional synchronization signal blocks in terminal device 1 of the present embodiment.
  • the terminal device 1 receives first information/parameters indicating the frequency position and bandwidth of the separate initial downlink BWP in the first cell, and additional information/parameters received in the separate initial downlink BWP. a second information/parameter indicating subcarrier spacing of synchronization signal blocks;
  • the terminal device 1 identifies the frequency position of the separate initial downlink BWP based on the received first information, and the additional synchronization signal received by the separate initial downlink BWP based on the received second information. Identify the subcarrier spacing of the block.
  • the terminal device 1 receives additional synchronization signal blocks at specified subcarrier intervals.
  • the terminal device 1 uses the band of the separate initial downlink BWP.
  • An additional synchronization signal block transmitted from the base station apparatus 3 can be received within.
  • Terminal device 1 may be configured with multiple initial uplink sub-BWPs by SIB1.
  • the terminal device 1 may determine one or more initial uplink sub-BWPs based on the initialUplinkBWP provided by SIB1. At least one of the multiple initial uplink sub-BWPs may be configured to include physical random access channel resources.
  • the terminal device 1 may operate considering the initial uplink sub-BWP as the initial uplink BWP.
  • Multiple initial uplink sub-BWPs may be regarded as multiple initial uplink BWPs.
  • Multiple initial uplink sub-BWPs may be designed to be included in the frequency band of one initial uplink BWP.
  • the initial uplink sub-BWP may also be referred to as an uplink BWP or an uplink sub-BWP.
  • setting/identifying the initial uplink BWP may mean setting/identifying the frequency position and/or the bandwidth of the initial uplink BWP.
  • a plurality of initial uplink BWPs are set/identified means that a plurality of frequency positions and/or a plurality of bandwidths of the initial uplink BWP are set/identified. you can The base station device 3 broadcasts information including setting of a plurality of frequency positions and/or a plurality of bandwidths of the initial uplink BWP, and the terminal device 1 sets the frequency position and bandwidth of the initial uplink BWP based on the information. may be determined/specified/set.
  • SIB1 may include uplinkConfigCommon, which is a common downlink configuration parameter for a cell. At least one parameter for determining whether or not a certain cell is restricted by the terminal device 1 may be included in uplinkConfigCommon indicating common uplink parameters for a certain cell.
  • uplinkConfigCommon is a parameter indicating basic parameters for one uplink carrier and transmission (for example, called frequencyInfoUL), a parameter indicating the initial uplink BWP configuration of a serving cell (for example, called initialUplinkBWP), and/or multiple and a parameter indicating the configuration of the initial uplink sub-BWP (eg, called initialUplinkBWP-rc).
  • Information ulAllocationBandwidth indicating the maximum allocated bandwidth in the uplink may be included in uplinkConfigCommon.
  • the initialUplinkBWP includes BWP information elements, PDCCH setting information elements, and/or PDSCH setting information elements.
  • the initial uplink BWP may be configured in the network to include physical random access channel resources in the frequency domain.
  • the terminal device 1 receives/identifies the setting information of the initial uplink BWP with the upper layer parameter initialUplinkBWP.
  • the initialUplinkBWP may be included in SIB1 or may be included in any RRC signaling.
  • initial uplink BWP configuration information may include information indicating the frequency position and bandwidth of the initial uplink BWP.
  • the terminal device 1 may receive SIB1 or any RRC signaling containing multiple configuration information for the initial uplink BWP. Multiple initial uplink BWP configuration information may be included in one parameter initialUplinkBWP.
  • parameters set in SIB1 may be broadcast in other SIBs (or REDCAP SIB), or may be notified by RRC signaling.
  • FIG. 11 is a schematic block diagram showing the configuration of the terminal device 1 of this embodiment.
  • the terminal device 1 includes a radio transmitting/receiving section 10 and an upper layer processing section 14 .
  • the radio transmitting/receiving section 10 includes an antenna section 11 , an RF (Radio Frequency) section 12 and a baseband section 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 transmitting/receiving unit 10 is also called a transmitting unit 10, a receiving unit 10, a monitoring unit 10, or a physical layer processing unit 10.
  • the upper layer processing unit 14 is also called a processing unit 14, a measuring unit 14, a selecting unit 14, a determining unit 14, or a control unit 14.
  • the upper layer processing unit 14 outputs uplink data (which may be referred to as a transport block) generated by a user's operation or the like to the radio transmitting/receiving unit 10.
  • the upper layer processing unit 14 includes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a radio resource control (Radio Resource Control: Handles all or part of the RRC layer.
  • the upper layer processing unit 14 has a function of acquiring bit information of the MIB (which may be the REDCAP MIB), SIB1 (which may be the REDCAP SIB1), and other SIBs (which may be the REDCAP SIB).
  • the upper layer processing unit 14 may have a function of determining/identifying initial downlink BWP settings (for example, frequency position and bandwidth) based on system information blocks (SIB1/SIB) or RRC signaling information.
  • the upper layer processing unit 14 may have a function of determining/identifying initial uplink BWP settings (for example, frequency position and bandwidth) based on system information blocks (SIB1/SIB) or RRC signaling information.
  • the upper layer processing unit 14 may have a function of determining/identifying settings (for example, frequency locations and bandwidths) of separate initial uplink BWPs based on system information blocks (SIB1/SIB) or RRC signaling information.
  • the medium access control layer processing unit 15 provided in the upper layer processing unit 14 performs MAC layer (medium access control layer) processing.
  • the medium access control layer processing unit 15 controls transmission of scheduling requests based on various setting information/parameters managed by the radio resource control layer processing unit 16 .
  • a radio resource control layer processing unit 16 provided in the upper layer processing unit 14 performs processing of the RRC layer (radio resource control layer).
  • the radio resource control layer processing unit 16 manages various setting information/parameters of its own device.
  • the radio resource control layer processing unit 16 sets various setting information/parameters based on the upper 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 the 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 the downlink control information received from the base station device 3 .
  • the radio transmission/reception unit 10 performs physical layer processing such as modulation, demodulation, encoding, and decoding.
  • the radio transmitting/receiving unit 10 separates, demodulates, and decodes the signal received from the base station device 3, and outputs the decoded information to the upper layer processing unit .
  • the radio transmitting/receiving unit 10 modulates and encodes data to generate a transmission signal, and transmits the signal to the base station device 3 and the like.
  • the radio transmitting/receiving unit 10 outputs an upper layer signal (RRC message) received from the base station device 3, DCI, etc. to the upper layer processing unit 14.
  • RRC message upper layer signal
  • the radio transmitting/receiving unit 10 generates and transmits an uplink signal (including PUCCH and/or PUSCH) based on instructions from the upper layer processing unit 14 .
  • the radio transmitting/receiving unit 10 may have a function to receive synchronization signal blocks, additional synchronization signal blocks, PSS, SSS, PBCH, DMRS for PBCH, random access response, PDCCH and/or PDSCH.
  • the radio transmitting/receiving unit 10 may have a function of transmitting PRACH (which may be a random access preamble), PUCCH and/or PUSCH.
  • the radio transmitting/receiving unit 10 may have a function of monitoring PDCCH.
  • the radio transmitting/receiving unit 10 may have a function of receiving DCI on PDCCH.
  • the radio transmitting/receiving unit 10 may have a function of outputting the DCI received on the PDCCH to the upper layer processing unit 14 .
  • the radio transmitting/receiving unit 10 may have a function of receiving a system information block (SIB1 and/or SIB) corresponding to a given cell.
  • SIB1 and/or SIB system information block
  • the RF section 12 converts the signal received via the antenna section 11 into a baseband signal by orthogonal demodulation (down-convert) and removes unnecessary frequency components.
  • the RF section 12 outputs the processed analog signal to the baseband section.
  • the baseband unit 13 converts the analog signal input from the RF unit 12 into a digital signal.
  • the baseband unit 13 removes the portion corresponding to the CP (Cyclic Prefix) from the converted digital signal, performs Fast Fourier Transform (FFT) on the CP-removed signal, and converts the signal in the frequency domain to Extract.
  • FFT Fast Fourier Transform
  • the baseband unit 13 performs inverse fast Fourier transform (IFFT) on data to generate OFDM symbols, adds CPs to the generated OFDM symbols, generates baseband digital signals, and generates baseband digital signals. Converts band digital signals to analog signals. Baseband section 13 outputs the converted analog signal to RF section 12 .
  • IFFT inverse fast Fourier transform
  • 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 through the antenna unit 11. do. Also, the RF unit 12 amplifies power. Also, the RF unit 12 may have a function of determining transmission power of uplink signals and/or uplink channels to be transmitted in the serving cell.
  • the RF section 12 is also called a transmission power control section.
  • the RF unit 12 may use an antenna switch to connect the filters included in the antenna unit 11 and the RF unit 12 during signal reception, and connect the power amplifiers included in the antenna unit 11 and the RF unit 12 during signal transmission.
  • the downlink A function may be provided for tuning/retuning the frequency band to which the RF circuit is applied within the BWP.
  • the frequency band to which the RF circuit is applied may be the frequency band of the carrier frequency to be applied when down-converting the received signal to the baseband signal.
  • the uplink A function of adjusting/readjusting the frequency band to which the RF circuit is applied within the BWP may be provided.
  • the frequency band to which the RF circuit is applied may be the frequency band of the carrier wave frequency to be applied when up-converting the analog signal to the carrier wave frequency.
  • FIG. 12 is a schematic block diagram showing the configuration of the base station device 3 of this embodiment.
  • the base station device 3 includes a radio transmitting/receiving section 30 and an upper layer processing section .
  • the radio transmitting/receiving section 30 includes an antenna section 31 , an RF section 32 and a baseband section 33 .
  • the upper layer processing unit 34 includes a medium access control layer processing unit 35 and a radio resource control layer processing unit 36 .
  • the radio transmitting/receiving unit 30 is also called a transmitting unit 30, a receiving unit 30, a monitoring unit 30, or a physical layer processing unit 30.
  • a control unit may be provided separately for controlling the operation of each unit based on various conditions.
  • the upper layer processing unit 34 is also called a processing unit 34, a determining unit 34, or a control unit 34.
  • the upper layer processing unit 34 includes a medium access control (MAC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, a radio resource control (Radio Resource Control: Handles all or part of the 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) containing information for the terminal device 1 to identify the initial downlink BWP and/or RRC signaling.
  • SIB1/SIB system information block
  • the upper layer processing unit 34 may have a function of generating a system information block (SIB1/SIB) containing information for the terminal device 1 to identify the initial uplink BWP and/or RRC signaling.
  • the upper layer processing unit 34 may have a function to generate a system information block (SIB1/SIB) containing information for the terminal device 1 to identify frequency resources for one or more PRACH transmission opportunities and/or RRC signaling. good.
  • a medium access control layer processing unit 35 provided in the upper layer processing unit 34 performs MAC layer processing.
  • the medium access control layer processing unit 35 performs processing related to scheduling requests based on various setting information/parameters managed by the radio resource control layer processing unit 36 .
  • a radio resource control layer processing unit 36 provided in the upper layer processing unit 34 performs RRC layer processing.
  • the radio resource control layer processing unit 36 generates a 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 arranged in PDSCH (transport block (TB), random access response (RAR)), system information, RRC message, MAC CE (Control Element), etc. or obtained from an upper node and output to the radio transmitting/receiving unit 30.
  • the radio resource control layer processing unit 36 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 an upper layer signal. That is, the radio resource control layer processing unit 36 transmits/notifies information indicating various setting information/parameters.
  • the radio resource control layer processing unit 36 may transmit/broadcast information for specifying configuration of one or more reference signals in a certain cell.
  • the base station device 3 When an RRC message, MAC CE, and/or PDCCH is transmitted from the base station device 3 to the terminal device 1, and the terminal device 1 performs processing based on the reception, the base station device 3 causes the terminal device to perform the processing. Processing (control of the terminal device 1 and the system) is performed assuming what is being done. That is, the base station device 3 sends to the terminal device 1 an RRC message, a MAC CE, and/or a PDCCH that causes the terminal device to perform processing based on its reception.
  • the radio transmitting/receiving unit 30 transmits an upper layer signal (RRC message), DCI, etc. to the terminal device 1 . Also, the radio transmitting/receiving unit 30 receives an uplink signal transmitted from the terminal device 1 based on an instruction from the upper layer processing unit 34 .
  • the radio transmitting/receiving unit 30 may have a function of transmitting PDCCH and/or PDSCH.
  • the radio transceiver 30 may be capable of receiving one or more PUCCHs and/or PUSCHs.
  • the radio transmitting/receiving unit 30 may have a function of transmitting DCI on the PDCCH.
  • the radio transmitting/receiving unit 30 may have a function of transmitting the DCI output by the upper layer processing unit 34 on the PDCCH.
  • the radio transceiver 30 may have the capability to transmit SSB, PSS, SSS, PBCH and/or DMRS for PBCH.
  • the radio transmitting/receiving unit 30 may have a function of transmitting RRC messages (which may be RRC parameters).
  • the wireless transmission/reception unit 30 may have a function for the terminal device 1 to transmit the system information block (SIB1/SIB).
  • SIB1/SIB system information block
  • part of the functions of the radio transmitting/receiving unit 30 are the same as those of the radio transmitting/receiving unit 10, so description thereof will be omitted.
  • part or all of the functions of the radio transmission/reception section 30 may be included in each transmission/reception point 4.
  • the upper layer processing unit 34 transmits (transfers) control messages or user data between the base station devices 3 or between upper network devices (MME, S-GW (Serving-GW)) and the base station device 3. ) or receive.
  • MME mobile phone
  • S-GW Serving-GW
  • FIG. 12 other components of the base station device 3 and data (control information) transmission paths between the components are omitted, but other functions required to operate as the base station device 3 are omitted. It is clear that it has a plurality of blocks as constituents.
  • the upper layer processing unit 34 includes a radio resource management (Radio Resource Management) layer processing unit and an application layer processing unit.
  • the "parts" in the figure are elements that realize the functions and procedures of the terminal device 1 and the base station device 3, which are also expressed by terms such as sections, circuits, constituent devices, devices, and units.
  • Each of the units denoted by reference numerals 10 to 16 provided in the terminal device 1 may be configured as a circuit.
  • Each of the units denoted by reference numerals 30 to 36 provided in the base station device 3 may be configured as a circuit.
  • the program that runs on the device related to the present invention may be a program that controls the Central Processing Unit (CPU) and the like to make the computer function so as to realize the functions of the embodiments related to the present invention.
  • Programs or information handled by programs are temporarily stored in volatile memory such as random access memory (RAM), non-volatile memory such as flash memory, hard disk drives (HDD), or other storage systems.
  • volatile memory such as random access memory (RAM), non-volatile memory such as flash memory, hard disk drives (HDD), or other storage systems.
  • the program for realizing the functions of the embodiments related to the present invention may be recorded in a computer-readable recording medium. It may be realized by causing a computer system to read and execute the program recorded on this recording medium.
  • the "computer system” here is a computer system built in the device, and includes hardware such as an operating system and peripheral devices.
  • computer-readable recording medium means a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium that dynamically retains a program for a short period of time, or any other computer-readable recording medium. Also good.
  • each functional block or features of the apparatus used in the above-described embodiments may be implemented or performed in an electrical circuit, eg, an integrated circuit or multiple integrated circuits.
  • Electrical circuits designed to perform the functions described herein may be general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or combinations thereof.
  • a general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine.
  • the electric circuit described above may be composed of a digital circuit, or may be composed of an analog circuit.
  • one or more aspects of the present invention can use the new integrated circuit based on that technology.
  • the present invention is not limited to the above-described embodiments.
  • an example of the device is described, but the present invention is not limited to this, and stationary or non-movable electronic devices installed indoors and outdoors, such as AV equipment, kitchen equipment, It can be applied to terminal devices or communication devices such as cleaning/washing equipment, air conditioning equipment, office equipment, vending machines, and other household equipment.
  • the present invention can be used, for example, in communication systems, communication equipment (eg, mobile phone devices, base station devices, wireless LAN devices, or sensor devices), integrated circuits (eg, communication chips), or programs. .
  • communication equipment eg, mobile phone devices, base station devices, wireless LAN devices, or sensor devices
  • integrated circuits eg, communication chips
  • Terminal device 1 (1A, 1B) Terminal device 3 Base station device 4 Transmission/reception point (TRP) 10 Radio transmitting/receiving unit 11 Antenna unit 12 RF unit 13 Baseband unit 14 Upper layer processing unit 15 Medium access control layer processing unit 16 Radio resource control layer processing unit 30 Radio transmitting/receiving unit 31 Antenna unit 32 RF unit 33 Baseband unit 34 Upper layer Processing unit 35 Medium access control layer processing unit 36 Radio resource control layer processing unit 50 Transmission unit (TXRU) 51 phase shifter 52 antenna element

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce dispositif terminal : reçoit un bloc d'informations système dans une première cellule, le bloc d'informations système comprenant des premières informations et des secondes informations ; spécifie la position de fréquence d'une première BWP de liaison descendante dans la première cellule sur la base des premières informations ; spécifie l'intervalle de sous-porteuse d'un bloc de signaux de synchronisation reçu dans la première BWP de liaison descendante sur la base des secondes informations ; et reçoit le bloc de signaux de synchronisation à l'aide de la première BWP BWP de liaison descendante.
PCT/JP2022/035135 2021-09-30 2022-09-21 Dispositif terminal, dispositif station de base et procédé de communication WO2023054101A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021160918 2021-09-30
JP2021-160918 2021-09-30

Publications (1)

Publication Number Publication Date
WO2023054101A1 true WO2023054101A1 (fr) 2023-04-06

Family

ID=85780673

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/035135 WO2023054101A1 (fr) 2021-09-30 2022-09-21 Dispositif terminal, dispositif station de base et procédé de communication

Country Status (1)

Country Link
WO (1) WO2023054101A1 (fr)

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NORDIC SEMICONDUCTOR ASA: "On aspects related to reduced maximum UE BW", 3GPP TSG RAN WG1 #106-E, R1-2107040, 6 August 2021 (2021-08-06), XP052033370 *

Similar Documents

Publication Publication Date Title
JP7246874B2 (ja) 基地局装置、端末装置、および、通信方法
CN113475138B (zh) 用户设备、基站装置及通信方法
JP6917403B2 (ja) 基地局装置、端末装置および通信方法
WO2020170972A1 (fr) Dispositif de station de base, dispositif de terminal, procédé de communication, et circuit intégré
WO2020218529A1 (fr) Dispositif de station de base, dispositif terminal et procédé de communication
WO2020203427A1 (fr) Dispositif de station de base, dispositif terminal et procédé de communication
WO2020218355A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
CN112771825A (zh) 基站装置、终端装置以及通信方法
WO2021029367A1 (fr) Dispositif de station de base, dispositif terminal, et procédé de communication
JP2022025801A (ja) 端末装置、基地局装置、および、通信方法
WO2022239492A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2022196735A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2021162053A1 (fr) Appareil terminal, appareil de station de base, et procédé de communication
JP2022055393A (ja) 端末装置、基地局装置、および、通信方法
WO2020218348A1 (fr) Dispositif de station de base, dispositif terminal, procédé de communication, et circuit intégré
JP2022102123A (ja) 端末装置、基地局装置、および、通信方法
JP2022102124A (ja) 端末装置、基地局装置、および、通信方法
JP2022011324A (ja) 端末装置、基地局装置、および、通信方法
WO2023054101A1 (fr) Dispositif terminal, dispositif station de base et procédé de communication
WO2023054111A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2023013294A1 (fr) Dispositif terminal, dispositif station de base et procédé de communication
WO2023013293A1 (fr) Dispositif terminal, dispositif de station de base, et procédé de communication
WO2022239493A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2022196770A1 (fr) Équipement terminal, dispositif de station de base et procédé de communication
WO2022071278A1 (fr) Dispositif terminal, dispositif de station de base, et procédé de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22875968

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023551373

Country of ref document: JP