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

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

Info

Publication number
WO2022196735A1
WO2022196735A1 PCT/JP2022/012022 JP2022012022W WO2022196735A1 WO 2022196735 A1 WO2022196735 A1 WO 2022196735A1 JP 2022012022 W JP2022012022 W JP 2022012022W WO 2022196735 A1 WO2022196735 A1 WO 2022196735A1
Authority
WO
WIPO (PCT)
Prior art keywords
bandwidth
terminal device
cell
pbch
redcap
Prior art date
Application number
PCT/JP2022/012022
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 シャープ株式会社
Priority to JP2023507160A priority Critical patent/JPWO2022196735A1/ja
Publication of WO2022196735A1 publication Critical patent/WO2022196735A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

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-45414 filed in Japan on March 19, 2021, the contents of which are 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 in one aspect of the present invention comprises a receiving unit for receiving a system information block including first information for setting parameters of a first cell, and a processing unit, wherein the first information is , a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial downlink BWP of the first cell, and a parameter indicating the maximum allocated bandwidth of the first cell.
  • the processing unit determines whether the terminal device supports a downlink channel bandwidth that is a maximum transmission bandwidth setting of a bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP; determining whether the first cell is a regulated cell based on whether the device supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, and the allocated bandwidth is scheduled by a base station device; is the maximum number of resource blocks in a downlink channel band, and the maximum transmission bandwidth setting is a band that can be received by the terminal device by adjusting the frequency position of the receiver of the terminal device in the first cell indicates the number of resource blocks in
  • the base station apparatus in one aspect of the present invention includes a processing unit that generates a system information block including first information for setting parameters of the first cell, and transmits the system information block to the terminal apparatus.
  • the first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial downlink BWP of the first cell, and the first and a parameter indicating the maximum allocated bandwidth of a cell, wherein the terminal device sets a maximum transmission bandwidth setting of a bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP. and whether the terminal device supports an allocated bandwidth equal to or greater than the maximum allocated bandwidth, and information for causing the terminal device to determine whether the first cell is a regulated cell.
  • the allocated bandwidth is the maximum number of resource blocks in a downlink channel band scheduled by the base station apparatus
  • the maximum transmission bandwidth setting is the frequency of the receiver of the terminal apparatus. It indicates the number of resource blocks in the band that can be received by adjusting the position.
  • a communication method is a communication method for a terminal device, receiving a system information block including first information for setting parameters of a first cell,
  • the information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial downlink BWP of the first cell, a parameter indicating the maximum allocated bandwidth of the first cell, and whether the terminal device supports a downlink channel bandwidth that is a maximum transmission bandwidth setting of a bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP; determining whether the first cell is a regulated cell based on whether it supports an allocated bandwidth greater than or equal to the maximum allocated bandwidth, and the allocated bandwidth is a downlink channel scheduled by a base station apparatus; is the maximum number of resource blocks in the band, and the maximum transmission bandwidth setting is a resource block of a band that the terminal device can receive by adjusting the frequency position of the receiver of the terminal device in the first cell indicate the number.
  • a communication method is a communication method for a base station apparatus, in which a system information block including first information for setting parameters of a first cell is generated, and the terminal apparatus The system information block is transmitted, and the first information includes a parameter indicating the carrier bandwidth of the first cell, a parameter indicating the bandwidth of the initial downlink BWP of the first cell, and the first and a parameter indicating the maximum allocated bandwidth of a cell, wherein the terminal device sets a maximum transmission bandwidth setting of a bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP.
  • the terminal device determines whether the first cell is a regulated cell.
  • the allocated bandwidth is the maximum number of resource blocks in a downlink channel band scheduled by the base station apparatus
  • the maximum transmission bandwidth setting is the frequency of the receiver of the terminal apparatus. It indicates the number of resource blocks in the band that can be received by adjusting the position.
  • 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. 4 is a diagram showing an example of the configuration of an RRC parameter PDCCH-ConfigSIB1-RC, which is information indicating PDCCH configuration for REDCAP SIB1 according to the embodiment of the present invention
  • FIG. 4 is a diagram showing an example of a table to which a value of controlResourceSetZero is applied as an index according to an embodiment of the present invention
  • FIG. 4 is a diagram showing an example of a table to which the value of searchSpaceZero is applied as an index according to the embodiment of the present invention
  • FIG. 4 is a diagram showing an example of a table of indexes indicated by a 2-bit parameter PDCCH-repetitions in the REDCAP MIB according to the embodiment of the present invention and the number of repetition transmissions of PDCCH
  • FIG. 3 is a diagram showing examples of SS/PBCH blocks and SS burst sets according to embodiments of the present invention
  • FIG. 4 illustrates an example half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted according to embodiments of the 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. 3 illustrates an example half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted in accordance with embodiments of the present invention
  • FIG. 4 is a diagram showing a REDCAP PBCH and a resource where DMRS for REDCAP PBCH are arranged in a REDCAP PBCH block according to an embodiment of the present invention
  • FIG. 10 illustrates an example of a REDCAP PBCH block according to an embodiment of the invention
  • FIG. 10 illustrates another example of a REDCAP PBCH block according to embodiments of the 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 downlink transmission using multiple initial downlink sub-BWPs according to the embodiment of the present invention
  • FIG. 4 is a diagram showing an example of the relationship between carrier bandwidth, initial downlink BWP, maximum allocated bandwidth, downlink channel bandwidth supported by terminal device 1, and downlink allocated bandwidth in a certain cell according to the embodiment of the present invention.
  • FIG. 4 is a flow chart showing an example of a regulated cell determination process in the terminal device 1 according to the embodiment of the present invention
  • FIG. 4 is a diagram showing an example of the relationship between carrier bandwidth, initial uplink BWP, maximum allocated bandwidth, and uplink channel bandwidth and uplink allocated bandwidth supported by terminal device 1 in a certain cell according to the embodiment of the present invention; .
  • FIG. 10 is a flow chart showing another example of the restricted cell determination process in the terminal device 1 according to the embodiment of the present invention. It is a figure showing an example of beamforming concerning an 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 comprise 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 .
  • the base station apparatus 3 may serve the terminal apparatus 1 with one or a plurality of cells as a communicable range (communication area) controlled by one or a plurality of transmission/reception points 4 .
  • 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.
  • 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), and Multi-Carrier Code Division Multiplexing (MC-CDM) are used. good too.
  • OFDM Orthogonal Frequency Division Multiplexing
  • CP Cyclic Prefix
  • SC- FDM Single Carrier Frequency Division Multiplexing
  • DFT-S-OFDM Discrete Fourier Transform Spread OFDM
  • MC-CDM Multi-Carrier Code Division Multiplexing
  • UMB Universal-Filtered Multi-Carrier
  • F-OFDM Filtered OFDM
  • window functions are Multiplied OFDM (Windowed OFDM)
  • Filter-Bank Multi-Carrier (FBMC) may be used.
  • OFDM symbols are used as the transmission method in the present embodiment, a case of using the other transmission method described above is also included in one aspect of the present invention.
  • 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 may be operated in carrier aggregation or dual connectivity with radio access technologies (RAT: Radio Access Technology) such as LTE and LTE-A/LTE-A Pro.
  • RAT Radio Access Technology
  • 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.
  • RAT Radio Access Technology
  • 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.
  • MCG's PCell In dual connectivity operation, the SpCell (Special Cell) is referred to as MCG's PCell or SCG's PSCell, depending on whether the MAC (Medium Access Control) entity is associated with the MCG or the SCG, respectively.
  • 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, a master cell group and a secondary cell group may be configured for the terminal device 1 .
  • a master cell group may consist of one primary cell and zero or more secondary cells.
  • a secondary cell group may consist of one primary secondary cell and zero or more secondary cells.
  • 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
  • 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.
  • a resource element may be identified using a subcarrier number and an OFDM symbol number.
  • PDSCH physical downlink channel
  • PUSCH uplink channel
  • resource blocks As resource blocks (RB), reference resource blocks, common resource blocks, physical resource blocks, and virtual resource blocks are defined.
  • One resource block 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”).
  • Common resource blocks are resource blocks numbered in ascending order from 0 at each subcarrier spacing setting ⁇ from reference point A. The resource grid described above is defined by this common resource block.
  • Physical resource blocks are resource blocks numbered in ascending order from 0 included in the band width part (BWP: BandWidth Part) described later, and physical resource blocks are numbered in ascending order from 0 included in the BWP is a resource block with A given physical uplink channel is first mapped to a virtual resource block. The virtual resource blocks are then mapped to physical resource blocks.
  • resource blocks may be virtual resource blocks, physical resource blocks, common resource blocks, or reference resource blocks.
  • 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 cyclic prefix.
  • 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 1 ms regardless of subcarrier spacing, and the number of OFDM symbols included in a slot is 7 or 14 (however, if the cyclic prefix (CP) added to each symbol is Extended CP, 6 or 12), the slot length depends on the subcarrier spacing.
  • CP cyclic prefix
  • 6 or 12 Extended CP, 6 or 12
  • the slot length depends 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.
  • the carrier corresponding to the serving cell is called a downlink component carrier (or downlink carrier).
  • a carrier corresponding to a serving cell is called an uplink component carrier (or an uplink carrier).
  • the carrier corresponding to the serving cell is called a sidelink component carrier (or sidelink carrier).
  • Downlink component carriers, uplink component carriers, and/or sidelink component carriers are collectively referred to as component carriers (or carriers).
  • 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
  • REDCAP PBCH REDCAP Physical Broadcast Channel: REduction CAPability Physical Broadcast Channel, R-PBCH
  • PDCCH Physical Downlink Control CHannel
  • PDSCH Physical Downlink Shared CHannel
  • PUCCH Physical Uplink Control CHannel
  • PRACH Physical Uplink Control 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, and the subcarrier interval of the system information block 1 (SIB1: System Information Block 1). , information indicating the frequency domain offset between the resource block grid and the SS/PBCH block (also referred to as synchronization signal block, SS block, or SSB), and information indicating PDCCH configuration for SIB1. may be included.
  • SIB1 System Information Block 1
  • 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 configuration for SIB1 may be CORESET (ControlResourceSet) 0 (also referred to as common CORESET), common search space and/or information that determines the required PDCCH parameters.
  • CORESET indicates the resource element of PDCCH and CORESET0 is the CORESET for the PDCCH that schedules SIB1.
  • 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 REDCAP PBCH may be used to broadcast a REDCAP important information block (also called REDCAP MIB, REDCAP EIB, REDCAP BCH, R-MIB) containing important system information required by the terminal device 1.
  • REDCAP MIB may be used only for the terminal device 1 that satisfies specific conditions (for example, indicates specific parameters in UE Capability and/or UE Category).
  • the REDCAP MIB contains information for identifying the SFN to which the REDCAP PBCH is mapped or information for identifying the SFN to which the SS/PBCH block corresponding to the REDCAP PBCH is mapped, the REDCAP system information block 1 (also called REDCAP SIB1, R-SIB1), the frequency between the grid of resource blocks and the SS/PBCH block (also called synchronization signal block, SS block, SSB) Information indicating a region offset and information indicating PDCCH configuration for REDCAP SIB1 may be included.
  • the REDCAP system information block 1 also called REDCAP SIB1, R-SIB1
  • the frequency between the grid of resource blocks and the SS/PBCH block also called synchronization signal block, SS block, SSB
  • Information indicating a region offset and information indicating PDCCH configuration for REDCAP SIB1 may be included.
  • REDCAP SIB1 contains the information necessary for evaluating whether terminal equipment 1 is allowed to connect to the cell and the scheduling of other REDCAP system information blocks (REDCAP SIB, also called R-SIB). contains information that determines
  • REDCAP SIB1 is used when evaluating whether a terminal device 1 meeting certain conditions (e.g. indicating certain parameters in UE Capability and/or UE Category) is allowed to connect to the cell. It contains necessary information and may contain information that determines the scheduling of other REDCAP SIBs. However, part or all of the information contained in the REDCAP MIB may be the same as part or all of the information contained in the MIB broadcasted on the PBCH. For example, the REDCAP SIB1 may be SIB1.
  • REDCAP MIB may be broadcast on the PBCH.
  • REDCAP PBCH may broadcast the MIB.
  • the REDCAP MIB included in the information sent on the REDCAP PBCH may be the same as the MIB included in the information sent on the PBCH included in the SS/PBCH block with which the REDCAP PBCH is associated.
  • the MIB-related processing described below may be similarly applied to the REDCAP MIB-related processing.
  • the information transmitted by the REDCAP PBCH may include information specifying the number of the radio frame to which the REDCAP PBCH is mapped and/or information specifying the half radio frame.
  • the information transmitted in the REDCAP PBCH includes information identifying the number of the radio frame to which the PSS and/or SSS associated with the REDCAP PBCH is mapped and/or information identifying the half radio frame may be included.
  • the information transmitted on the REDCAPPBCH may include information identifying the number of the radio frame to which the associated SS/PBCH block is mapped and/or information identifying the half radio frame. .
  • the information transmitted on the REDCAP PBCH may include the time index within the period of the associated SS/PBCH block.
  • the time index may be referred to as the SSB index or SS/PBCH block index.
  • the base station apparatus 3 transmits SS/PBCH blocks using multiple transmit beams, transmit filter settings, and/or QCL assumptions about receive spatial parameters, within a predetermined period or within a set period May indicate chronological order.
  • the terminal device 1 may recognize a difference in time index as a difference in QCL assumptions regarding transmit beams, transmit filter settings and/or receive spatial parameters.
  • the information transmitted on the REDCAP PBCH may include the time index of the REDCAP PBCH.
  • the information indicating the configuration of PDCCH for REDCAP SIB1 transmitted on REDCAP PBCH may be information that determines CORESET0, common search space and/or required PDCCH parameters for PDCCH that schedules REDCAP SIB1.
  • CORESET0, information on common search space and/or information to determine the required PDCCH parameters indicated in REDCAP MIB is not CORESET0, information on common search space and/or information to decide required PDCCH parameters indicated in MIB. They may be identical.
  • Fig. 4 shows an example of the configuration of the RRC parameter PDCCH-ConfigSIB1-RC, which is information indicating PDCCH settings for REDCAP SIB1.
  • the RRC parameter PDCCH-ConfigSIB1-RC is composed of the parameter controlResourceSetZero used to set CORESET0 and the parameter searchSpaceZero used to set the common search space.
  • An information element (IE: Information Element) indicated by controlResourceSetZero A value between 0 and 15 is set to ControlResourceSetZero.
  • 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.
  • the number of values that can be set for SearchSpaceZero may be other than 16, and may be 32, for example.
  • Terminal device 1 determines the number of consecutive resource blocks and the number of consecutive symbols for CORESET0 from controlResourceSetZero in PDCCH-ConfigSIB1-RC. 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, the subcarrier interval of the REDCAP PBCH, and/or the subcarrier interval of CORESET0. FIG.
  • each row in the table to which the value of controlResourceSetZero is applied as an index contains the index indicated by controlResourceSetZero, the multiple pattern of REDCAP PBCH and CORESET, and the number of RBs (which may be PRBs) of CORESET0. , the number of symbols of CORESET0, the offset and/or the number of repetitions of the PDCCH may be indicated.
  • the multiplex pattern of REDCAP PBCH and CORESET indicates the pattern of the frequency/time position relationship between the REDCAP PBCH that detected the REDCAP MIB and the corresponding CORESET0. For example, if the multiplexing pattern of REDCAP PBCH and CORESET is 1, then REDCAP PBCH and CORESET are time multiplexed into different symbols. However, the multiplex pattern of REDCAP PBCH and CORESET may indicate the pattern of the frequency/time position relationship between the SS/PBCH block corresponding to REDCAPPBCH that detected the REDCAP MIB and CORESET0. However, the REDCAP PBCH and CORESET multiplexing patterns are not defined in the table and may always be a fixed pattern (eg pattern 1).
  • 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 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 SS/PBCH block corresponding to REDCAP PBCH overlaps. good.
  • the number of repetitions of PDCCH indicates the number of repetition transmissions of PDCCH that schedules REDCAP SIB1. If the number of PDCCH repetitions indicated in the table is greater than 1, the terminal device 1 considers that the PDCCH that schedules REDCAP SIB1 is repeatedly transmitted.
  • the terminal device 1 receives the REDCAP MIB including the RRC parameter controlResourceSetZero on the REDCAP PBCH, the controlResourceSetZero, the index, the multiplexing pattern of REDCAP PBCH and CORESET, the number of RBs of CORESET0, the number of symbols of CORESET0, the offset and/or repetition of PDCCH.
  • the PDCCH indicating the scheduling information of REDCAP SIB1 is monitored based on the table indicating the number of times.
  • Terminal device 1 determines PDCCH monitoring opportunities from searchSpaceZero in PDCCH-ConfigSIB1-RC. 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. However, the terminal device 1 may determine the table to apply based on the multiplexing pattern of REDCAP PBCH and CORESET. FIG. 6 shows an example of a table to which the value of searchSpaceZero is applied as an index.
  • 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 REDCAP PBCH and/or the corresponding SS/PBCH block whose index is i.
  • the information indicating the PDCCH setting for REDCAP SIB1 transmitted on REDCAP PBCH is May indicate frequency locations to find REDCAP PBCH and/or corresponding SS/PBCH blocks with REDCAP SIB1 or frequency ranges where the network does not provide REDCAP PBCH and/or corresponding SS/PBCH blocks with REDCAP SIB1 .
  • the information transmitted by REDCAP PBCH may include a field PDCCH-repetitions indicating the number of repetition transmissions of PDCCH for scheduling REDCAP SIB1.
  • 2 bits in the REDCAP MIB may indicate the number of repeated PDCCH transmissions.
  • FIG. 7 is a diagram showing an example of a table of the index indicated by the 2-bit parameter PDCCH-repetitions in the REDCAP MIB and the number of repetition transmissions of PDCCH. Indexes 0, 1, 2, and 3 indicated by REDCAP MIB in the table of FIG. 7 correspond to N/A, 1, 2, and 4 as the number of PDCCH repetition transmissions, respectively.
  • a PDCCH repetition transmission count value of N/A may indicate that the PDCCH that schedules the REDCAP SIB1 and/or the REDCCAP SIB1 has not been transmitted.
  • the terminal device 1 considers that the PDCCH that schedules the REDCAP SIB1 and/or the REDCCAP SIB1 has not been transmitted when the index indicated by the 2 bits in the REDCAP MIB is 0.
  • the value of the PDCCH repetition transmission count is N/A, it may indicate that the cell is barred (barred).
  • the terminal device 1 receives the REDCAP MIB including the RRC parameter PDCCH-repetitions on the REDCAP PBCH, determines the number of repetition transmissions of the PDCCH indicating the scheduling information of the REDCAP SIB1 based on the PDCCH-repetitions, and the PDCCH-repetitions is predetermined. , it is considered that the PDCCH has not been transmitted.
  • 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 physical resource blocks (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 the contention based random access procedure.
  • 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. 8 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. 8 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 blocks are composed of 4 continuous 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.
  • the base station device 3 transmits REDCAP PBCH and DMRS for REDCAP PBCH using time resources and/or frequency resources different from those of the SS/PBCH block.
  • transmitting/receiving/processing REDCAP PBCH in this embodiment may be transmitting/receiving/processing REDCAP PBCH and DMRS for REDCAP PBCH.
  • a block containing a REDCAP PBCH and a DMRS for the REDCAP PBCH may be referred to as a REDCAP PBCH block.
  • transmitting the signals/channels contained in the REDCAP PBCH block may be referred to as transmitting the REDCAP PBCH block.
  • the base station device 3 transmits REDCAP PBCH using one or more REDCAP PBCH blocks within a predetermined time interval (which may be referred to as a REDCAP PBCH burst set), an independent downlink for each REDCAP PBCH block A transmit beam may also be used.
  • the REDCAP PBCH block may be the REDCAP PBCH and/or the DMRS itself for the REDCAP PBCH.
  • transmitting/receiving/processing a REDCAP PBCH block may be transmitting/receiving/processing a REDCAP PBCH and/or a DMRS for a REDCAP PBCH.
  • the REDCAP PBCH and/or DMRS for REDCAP PBCH may be DMRS for REDCAP PBCH and/or REDCAP PBCH transmitted outside the SS/PBCH block.
  • the DMRS for REDCAP PBCH and/or REDCAP PBCH is for REDCAP PBCH and/or REDCAP PBCH transmitted on different time and/or frequency resources than the SS/PBCH blocks that are transmitted periodically with the SSB period. of DMRS.
  • the REDCAP PBCH blocks according to this embodiment may be SS/PBCH blocks without PSS and/or SSS.
  • a REDCAP PBCH block and/or a REDCAP PBCH according to the present embodiment is associated with one SS/PBCH block transmitted within an SS burst set (Half frame with SS/PBCH block).
  • the transport block sent on the REDCAP PBCH and the transport block sent on the PBCH in the corresponding SS/PBCH block may be identical.
  • FIG. 9 shows an example of a half frame (Half frame with REDCAP PBCH block or REDCAP PBCH burst set) in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted according to the present embodiment. It is a diagram.
  • FIG. 9 shows an example in which two REDCAP PBCH blocks are included in a REDCAP PBCH burst set that exists in a constant cycle (which may be referred to as an SSB cycle), and a REDCAP PBCH block is composed of 4 consecutive OFDM symbols. ing.
  • REDCAP PBCH modulation symbols and DMRS for REDCAPPBCH are frequency-multiplexed in each OFDM symbol.
  • blocks containing synchronization signals may be distinguished from the SS/PBCH block and defined as separate blocks.
  • a block containing synchronization signals (PSS, SSS), REDCAP PBCH and DMRS for REDCAP PBCH may be referred to as a REDCAPSS/PBCH block, a REDCAP synchronization signal block, a REDCAP SS block, or a REDCAP SSB.
  • the description regarding the SS/PBCH block according to this embodiment may also be applied to the REDCAP SS/PBCH block.
  • PSS, SSS, PBCH and DMRS for PBCH are time/frequency multiplexed in one SS/PBCH block.
  • FIG. 10 is a table showing resources in which PSS, SSS, PBCH, and DMRS for PBCH are allocated within the SS/PBCH block.
  • the PSS may be mapped to the first symbol in the SS/PBCH block (the OFDM symbol whose OFDM symbol number is 0 relative to the 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). .
  • the REDCAP PBCH according to this embodiment is transmitted in OFDM symbols associated with corresponding SS/PBCH blocks or corresponding synchronization signals (PSS, SSS).
  • the temporal positional relationship between the REDCAP PBCH and the corresponding SS/PBCH block may be determined by the temporal positional relationship between the half-frame including the REDCAP PBCH and the half-frame including the corresponding SS/PBCH block.
  • the half-frame containing the REDCAP PBCH may be the half-frame after a predetermined time offset from the half-frame containing the corresponding SS/PBCH block.
  • the temporal position of the REDCAP PBCH within the half-frame containing the REDCAP PBCH and the temporal position of the SS/PBCH block within the half-frame containing the corresponding SS/PBCH block may be the same.
  • the start subcarrier of the REDCAP PBCH may be a subcarrier obtained by adding a predetermined frequency offset to the start subcarrier of the corresponding SS/PBCH block.
  • the value obtained by adding the frequency offset exceeds a fixed value
  • the value obtained by subtracting the fixed value may be used as the starting subcarrier of the REDCAP PBCH.
  • the bandwidth of the band to which the REDCAP PBCH can be assigned from the value may be used as the starting subcarrier of the REDCAP PBCH.
  • FIG. 11 is a diagram illustrating an example of a half-frame in which a REDCAP PBCH block and one or more REDCAP PBCH blocks are transmitted according to this embodiment.
  • FIG. 11 shows an example in which half-frames including REDCAP PBCH blocks exist between half-frames including SS/PBCH blocks that exist in a constant cycle (SSB cycle), and the REDCAP PBCH blocks are composed of 3 consecutive OFDM symbols. showing.
  • a REDCAP PBCH block is transmitted on resources corresponding to one SS/PBCH block, and all resources in the REDCAP PBCH block have a REDCAP PBCH or a DMRS for the REDCAP PBCH.
  • FIG. 11 shows an example in which half-frames including REDCAP PBCH blocks exist between half-frames including SS/PBCH blocks that exist in a constant cycle (SSB cycle), and the REDCAP PBCH blocks are composed of 3 consecutive OFDM symbols. showing.
  • a REDCAP PBCH block is transmitted on
  • the sequence of modulation symbols for the REDCAP PBCH consists of M symb2 symbols, each of the 1st subcarrier to the 240th subcarrier (relative to the starting subcarrier of the REDCAP PBCH block) of each of the three symbols in the REDCAP PBCH block. (subcarriers with carrier numbers 0 to 239) may be mapped to resources to which the DMRS for the REDCAP PBCH is not mapped.
  • the sequence of DMRS symbols for the REDCAP PBCH consists of 180 symbols, starting from the first subcarrier to the 240th subcarrier of the three symbols in the REDCAP PBCH block (subcarriers relative to the starting subcarrier of the REDCAP PBCH block). subcarriers numbered 0 to 239) may be mapped one subcarrier every four subcarriers. However, the number of symbols forming the REDCAP PBCH block does not have to be 3 symbols. For example, a REDCAP PBCH block consists of 4 symbols, and for 240 subcarriers of each symbol, there may be a REDCAP PBCH or a DMRS for the REDCAP PBCH.
  • a REDCAP PBCH block consists of 180 subcarriers and 4 OFDM symbols, and for 180 subcarriers of each symbol there may be a REDCAP PBCH or a DMRS for the REDCAP PBCH.
  • FIG. 13 is a diagram showing an example of a REDCAP PBCH block according to this embodiment.
  • FIG. 13 shows an example in which a REDCAP PBCH block exists within a half frame containing SS/PBCH blocks that exist in a constant cycle (SSB cycle), and the REDCAP PBCH block is composed of 4 continuous OFDM symbols.
  • a REDCAP PBCH block is transmitted on resources corresponding to one SS/PBCH block, and all resources in the REDCAP PBCH block have REDCAP PBCH or DMRS for REDCAP PBCH.
  • the sequence of modulation symbols for the REDCAP PBCH consists of M symb2 symbols, each of the four symbols in the REDCAP PBCH block from the first subcarrier to the 240th subcarrier (relative to the starting subcarrier of the REDCAP PBCH block). (subcarriers with carrier numbers 0 to 239) may be mapped to resources to which the DMRS for the REDCAP PBCH is not mapped.
  • the sequence of DMRS symbols for the REDCAP PBCH consists of 240 symbols, starting from the first subcarrier to the 240th subcarrier of the four symbols in the REDCAP PBCH block (subcarriers relative to the starting subcarrier of the REDCAP PBCH block).
  • REDCAP PBCH or DMRS for REDCAP PBCH may not exist for all resources in the REDCAP PBCH block.
  • the REDCAP PBCH block consists of 4 symbols, one of which may be set to zero.
  • FIG. 14 is a diagram showing another example of the REDCAP PBCH block according to this embodiment.
  • FIG. 14 shows an example in which REDCAP PBCH blocks exist in some slots in a half frame containing SS/PBCH blocks that exist in a constant cycle (SSB cycle), and the REDCAP PBCH blocks are composed of 4 consecutive OFDM symbols. is shown.
  • slots in which REDCAP PBCH blocks are allocated may be slots that do not contain candidate resources for SS/PBCH blocks.
  • a REDCAP PBCH block is transmitted on resources corresponding to one SS/PBCH block, and all resources in the REDCAP PBCH block have a REDCAP PBCH or a DMRS for the REDCAP PBCH.
  • the sequence of modulation symbols for the REDCAP PBCH consists of M symb2 symbols, each of the four symbols in the REDCAP PBCH block from the first subcarrier to the 240th subcarrier (relative to the starting subcarrier of the REDCAP PBCH block). (subcarriers with carrier numbers 0 to 239) may be mapped to resources to which the DMRS for the REDCAP PBCH is not mapped.
  • the sequence of DMRS symbols for the REDCAP PBCH consists of 240 symbols, starting from the first subcarrier to the 240th subcarrier of the four symbols in the REDCAP PBCH block (subcarriers relative to the starting subcarrier of the REDCAP PBCH block).
  • REDCAP PBCH or DMRS for REDCAP PBCH may not exist for all resources in the REDCAPPBCH block.
  • the REDCAP PBCH block may consist of 4 symbols, of which 1 symbol may be set to 0, and the remaining 3 symbols may contain the REDCAP PBCH and the DMRS for the REDCAP PBCH.
  • One or more REDCAP PBCH blocks within a half-frame (REDCAP PBCH burst set) containing REDCAP PBCH may be assigned different SSB indices.
  • a REDCAP PBCH block assigned a certain SSB index may be associated with the SS/PBCH block of that SSB index and periodically transmitted by the base station apparatus 3 .
  • a plurality of REDCAP PBCH blocks assigned the same SSB index may exist for one SS/PBCH block.
  • a REDCAP PBCH block assigned the same SSB index may be transmitted multiple times within an SSB period.
  • the time position of the half-frame to which the REDCAP PBCH block is mapped is combined with information identifying the SFN and/or information identifying the half-frame contained in the PBCH of the corresponding SS/PBCH block and/or the REDCAP PBCH of the REDCAP PBCH block. It may be identified based on the time offsets of the corresponding SS/PBCH blocks and REDCAP PBCH blocks. However, the information identifying the SFN and/or the information identifying the half-frame included in the REDCAP PBCH of the REDCAP PBCH block may be the information identifying the SFN and half-frame in which the corresponding SS/PBCH block is transmitted.
  • a terminal device 1 that receives a REDCAP PBCH block may identify the SFN and half-frame in which the corresponding SS/PBCH block is transmitted based on the received REDCAPPBCH block.
  • a REDCAP PBCH block is assigned an SSB index according to its temporal position within the transmitted half-frame.
  • the terminal device 1 identifies the SSB index based on REDCAP PBCH information and/or reference signal information included in the detected REDCAP 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 and REDCAP PBCH blocks assigned the same SSB index are assumed to be QCL in terms of mean delay, mean gain, Doppler spread, Doppler shift, and spatial correlation. good.
  • the terminal device 1 receives the PSS and SSS in the SS/PBCH block, and receives the PBCH in the SS/PBCH block and/or one or more REDCAP PBCHs corresponding to the SS/PBCH block. do.
  • the terminal device 1 can improve the detection accuracy of the MIB or the REDCAP MIB, and can expand the cell coverage in which the terminal device 1 can receive the MIB or the REDCAP MIB.
  • the terminal device 1 that receives the REDCAP PBCH may be only the terminal device 1 having a predetermined capability.
  • the terminal device 1 having limited capabilities for the purpose of reducing the cost and / or power consumption of the device is called REDCAP (Reduction Capability) compatible
  • the terminal device 1 compatible with REDCAP is an SS / PBCH block and /
  • the terminal device 1 that receives the REDCAP PBCH and does not support REDCAP may receive only the SS/PBCH block and not the REDCAP PBCH block.
  • the terminal device 1 receives PSS, SSS, PBCH, and SS/PBCH block in which DMRS for PBCH is mapped in a certain radio frame, and REDCAP PBCH in the same or different radio frame as the certain radio frame. and DMRS for REDCAP PBCH and may obtain MIBs for transport blocks sent on PBCH and REDCAP PBCH.
  • the PBCH and REDCAP PBCH carry at least the MIB and the additional bit information, and the radio frame in which the SS/PBCH block was transmitted may be identified based on the MIB and the additional bit information.
  • the terminal device 1 receives PSS, SSS, PBCH, and SS/PBCH block in which DMRS for PBCH is mapped in a certain radio frame, and REDCAP PBCH in the same or different radio frame as the certain radio frame. and DMRS for REDCAP PBCH and may obtain MIBs for transport blocks sent on PBCH and REDCAP PBCH.
  • the terminal device 1 in a certain cell, the connection state, the execution state of the predetermined timer, the received MIB (which may be the REDCAP MIB) information, and / or the received SIB (REDCAP SIB, SIB1, REDCAP SIB1), it decides whether to consider the cell as 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 SIB1 (REDCAP SIB1, other SIBs) including parameters for determining whether the cell is restricted in a certain cell of the terminal device 1. may be).
  • SIB1 REDCAP SIB1, other SIBs
  • the initial BWP (initial BWP), the initial downlink BWP (initial DL BWP) and the initial uplink BWP (initial UL BWP) according to the present embodiment are at least used during initial access before the RRC connection is established.
  • BWP, downlink BWP and uplink BWP are at least used during initial access before the RRC connection is established.
  • initialDownlinkBWP is not provided in SIB1 (REDCAP SIB1, other SIBs are acceptable) received by terminal device 1
  • the initial downlink BWP is PRB (Physical Resource Block), 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. good too.
  • the initialDownlinkBWP is provided in the SIB1 received by the terminal device 1, the initialDownlinkBWP may be defined by the initialDownlinkBWP.
  • the initial uplink BWP may be defined/configured in the initialUplinkBWP provided in SIB1 (REDCAP SIB1, or other SIBs).
  • 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. 15 is a diagram showing an example of RF retuning. In FIG. 15, 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.
  • 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.
  • the sub BWP (which may include an uplink sub BWP, a downlink sub BWP, an initial uplink sub BWP and an initial downlink sub BWP) is a band to which the terminal device 1 applies its own RF circuit. There may be.
  • the bandwidth of the initial downlink BWP is larger than the bandwidth of the RF circuit provided in the terminal device 1
  • the terminal device 1 uses the initial downlink sub-BWP with a bandwidth equal to or less than the bandwidth supported by the RF circuit of the device itself. may be determined.
  • the terminal device 1 uses the initial uplink sub-BWP with a bandwidth equal to or less than the bandwidth supported by the RF circuit of the device itself. may be determined.
  • the base station apparatus 3 uses at least two of a plurality of initial downlink sub-BWPs to apply frequency hopping downlink signals (for example, PDSCH, PDCCH, PBCH, synchronization signals, Msg2 in the random access procedure and/or random access may be Msg4 in the procedure).
  • the initial downlink sub-BWP is at least a frequency resource that can be used during initial access before RRC connection is established.
  • the terminal device 1 may receive downlink signals to which frequency hopping is applied using at least two of the plurality of initial downlink sub-BWPs.
  • multiple initial downlink sub-BWPs according to the present embodiment may be downlink BWPs to which the same identifier (BWP ID) is assigned.
  • the multiple initial downlink sub-BWPs may be multiple downlink BWPs to which mutually different identifiers (BWP IDs) are assigned.
  • the multiple initial downlink sub-BWPs may be multiple frequency bands configured with multiple sets of multiple resource blocks configured by SIB1.
  • Each initial downlink sub-BWP may be composed of a plurality of resource blocks that are continuous in the frequency domain.
  • the multiple initial downlink sub-BWPs may be multiple downlink sub-BWPs set within the initial downlink BWP whose BWP ID is 0 set by SIB1.
  • each downlink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0a, 0b, etc.).
  • the configuration of the initial downlink BWP and the configuration of multiple downlink sub-BWPs are configured by SIB1.
  • FIG. 16 is a diagram showing an example of downlink transmission using multiple initial downlink sub-BWPs according to this embodiment.
  • FIG. 16 shows a case where four initial downlink sub BWPs (initial DL sub BWP#0, #1, #2, #3) are set in carriers existing within a certain frequency band.
  • the terminal device 1 supports channel bandwidths wider than each of the four initial downlink sub-BWPs.
  • the terminal device 1 repeatedly transmits one downlink signal while performing frequency hopping using initial downlink sub-BWP#0 and initial downlink sub-BWP#2.
  • the base station apparatus 3 uses one of a plurality of initial downlink sub-BWPs to transmit a downlink signal (for example, PDSCH, PDCCH, PBCH, synchronization signal, Msg2 in a random access procedure and/or Msg4 in a random access procedure. may also be sent).
  • the terminal device 1 may receive downlink signals using one of a plurality of initial downlink sub-BWPs.
  • the initial downlink sub-BWP may be a frequency band composed of multiple resource block sets configured by SIB1.
  • the initial downlink sub-BWP may be composed of multiple resource blocks that are continuous in the frequency domain.
  • the initial downlink sub-BWP may be one of a plurality of downlink sub-BWPs set within the initial downlink BWP whose BWP ID is 0 set by SIB1.
  • each downlink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.).
  • the setting of the initial downlink BWP and the setting of the downlink sub-BWP are set by SIB1.
  • the terminal device 1 transmits an uplink signal to which frequency hopping is applied using at least two of a plurality of initial uplink sub-BWPs (for example, it may be PUSCH, PUCCH, PRACH and/or Msg3 in a random access procedure). may be performed.
  • the initial uplink sub-BWP is a frequency resource that can be used at least during initial access before RRC connection is established.
  • the base station apparatus 3 may receive uplink signals to which frequency hopping is applied using at least two of the plurality of initial uplink sub-BWPs.
  • multiple initial uplink sub-BWPs according to the present embodiment may be set in the frequency band of uplink BWPs to which the same identifier (BWP ID) is assigned.
  • the multiple initial uplink BWPs may be multiple uplink BWPs to which mutually different identifiers (BWP IDs) are assigned.
  • the multiple initial uplink sub-BWPs may be multiple frequency bands composed of multiple sets of multiple resource blocks configured by SIB1.
  • Each initial uplink sub-BWP may be composed of a plurality of resource blocks that are continuous in the frequency domain.
  • the multiple initial uplink BWPs may be multiple uplink sub-BWPs set within the initial uplink BWP whose BWP ID is 0 set by SIB1.
  • each uplink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.).
  • the configuration of the initial uplink BWP and the configuration of multiple uplink sub-BWPs are configured by SIB1.
  • Terminal device 1 transmits an uplink signal to which frequency hopping is applied using one of a plurality of initial uplink sub-BWPs (for example, it may be PUSCH, PUCCH, PRACH and/or Msg3 in a random access procedure). you can do it
  • the base station apparatus 3 may receive an uplink signal to which frequency hopping is applied using one of a plurality of initial uplink sub-BWPs.
  • the initial uplink sub-BWP may be a frequency band composed of multiple sets of multiple resource blocks configured by SIB1.
  • the initial uplink sub-BWP may be composed of multiple resource blocks that are continuous in the frequency domain.
  • the multiple initial uplink BWPs may be multiple uplink sub-BWPs set within the initial uplink BWP whose BWP ID is 0 set by SIB1.
  • each uplink sub-BWP may be assigned a different BWP ID (ID: 0a, 0b, etc.) or sub-BWP ID (ID: 0, 1, etc.).
  • the setting of the initial uplink BWP and the setting of the uplink sub-BWP are set by SIB1.
  • 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 is a parameter indicating basic parameters for one downlink carrier and transmission in the corresponding cell (for example, referred to as frequencyInfoDL), a parameter indicating the initial downlink BWP configuration of a serving cell (for example, referred to as initialDownlinkBWP); and/or a parameter indicating the configuration of multiple initial downlink sub-BWPs (eg, called initialDownlinkBWP-rc).
  • 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.
  • the BWP information element may be a parameter indicating the frequency position and bandwidth of the BWP.
  • 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) of the BWP in the frequency domain, and/or the standard CP (cyclic prefix) is used or extended CP is used. That is, BWP is 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.
  • Sub-BWP (e.g., uplink sub-BWP and downlink sub-BWP) is similar to BWP, depending on subcarrier spacing, CP, and frequency domain position and frequency domain bandwidth (number of consecutive resource blocks, etc.) may be defined.
  • a sub-BWP may be defined by a location in the frequency domain and a bandwidth in the frequency domain.
  • 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 initialDownlinkBWP-rc includes information indicating sub-BWP settings, PDCCH setting information elements, and/or PDSCH setting information elements in the corresponding cell.
  • initialDownlinkBWP-rc may be a parameter indicating the configuration of each of the multiple initial downlink sub-BWPs.
  • each of a plurality of initial downlink sub-BWPs configured in initialDownlinkBWP-rc may be an initial downlink BWP (initial DL BWP).
  • each of the multiple downlink sub-BWPs may be configured by the network to include CORESET0 in the frequency domain.
  • initialDownlinkBWP-rc may contain a list of information indicating the position in the frequency domain and the bandwidth in the frequency domain (eg, the number of consecutive resource blocks). Each entry in the list of information indicating frequency locations and bandwidths may correspond to each of a plurality of initial downlink sub-BWPs. Each entry in the list of information indicating frequency location and bandwidth may be a BWP information element (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.). The multiple initial downlink sub-BWPs have a common bandwidth, and initialDownlinkBWP-rc may indicate the list of frequency locations of the initial downlink sub-BWPs and the common bandwidth.
  • a plurality of initial downlink sub-BWPs have a common subcarrierSpacing and a common cyclicPrefix
  • initialDownlinkBWP-rc indicates a list of frequency positions of the initial downlink BWPs, a common bandwidth, a common subcarrierSpacing and a common cyclicPrefix.
  • subcarrierSpacing and cyclicPrefix indicated by initialDownlinkBWP may be set in a plurality of initial downlink sub-BWPs. That is, initialDownlinkBWP-rc may be information for specifying the frequency position and bandwidth of each of the multiple initial downlink sub-BWPs.
  • parameters indicating settings of a plurality of initial downlink sub-BWPs may be set in the aforementioned initialDownlinkBWP.
  • the parameters indicating the initial downlink BWP configuration of a certain serving cell are the parameters indicating the frequency position and bandwidth of the initial downlink BWP, the subcarrierSpacing of the initial downlink BWP, the cyclicPrefix of the initial downlink BWP, and a plurality of initial downlink sub-BWPs. may include a parameter indicating the setting of
  • 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.
  • Information indicating the maximum allocated bandwidth may be information specifying the bandwidth in terms of the number of resource blocks. 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 of resource blocks corresponding to the subcarrier interval 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 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 terminal device 1 may determine whether a certain cell is a regulated cell based on the bandwidth of the initial downlink BWP set for the cell.
  • the terminal device 1 may determine whether the cell is a regulated cell based on whether it supports a downlink channel bandwidth that is the same as or wider than the bandwidth of the set initial downlink BWP. For example, if the terminal device 1 does not support a downlink channel bandwidth equal to or wider than the bandwidth of the initial downlink BWP set by SIB1, the terminal device 1 may regard the cell as a regulated cell. good.
  • the terminal device 1 supports a certain bandwidth, it means that it is possible to tune/retune the band of the RF circuit of the terminal device within that bandwidth, and transmit and receive signals/channels within that bandwidth.
  • the downlink channel bandwidth supported by the terminal device 1 may be a downlink channel bandwidth in which signals/channels can be received using RF tuning/RF retuning.
  • the terminal device 1 may determine whether a certain cell is a regulated cell based on the bandwidths of a plurality of set initial downlink sub-BWPs corresponding to the cell.
  • the cell is a regulated cell may determine whether For example, if the terminal device 1 does not support a downlink bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of each of the set multiple initial downlink sub-BWPs, the terminal device 1 A cell may be regarded as a regulation cell. The terminal device 1 determines whether the cell is regulated based on whether the terminal device 1 supports a downlink bandwidth that is the same as or wider than the bandwidth set in common for the set multiple initial downlink sub-BWPs. It may be determined whether it is a cell.
  • the terminal device 1 determines whether it is a cell.
  • the terminal device 1 A cell may be considered a regulatory cell.
  • Terminal device 1 determines whether the cell is a regulated cell based on whether it supports a downlink bandwidth that is the same as or wider than the reference bandwidth identified from the bandwidth notified by SIB1. you can For example, if the terminal device 1 does not support a downlink bandwidth equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may regard the cell as a regulated cell. good.
  • the reference bandwidth may be the bandwidth of one initial downlink BWP notified by SIB1 and the bandwidth specified from the number of initial downlink sub-BWPs set.
  • the reference bandwidth may be a bandwidth specified by dividing one initial downlink BWP signaled by SIB1 by a predetermined number.
  • the terminal device 1 receives information indicating the maximum allocated bandwidth in SIB1 corresponding to a certain cell, and determines whether the cell is a regulated cell based on the information indicating the maximum allocated bandwidth.
  • the information indicating the maximum allocated bandwidth may be information indicating the maximum allocated bandwidth of the downlink.
  • the information indicating the maximum allocated bandwidth may be information indicating the maximum allocated bandwidth of the uplink.
  • the information indicating the maximum allocated bandwidth may be information indicating a common maximum allocated bandwidth for downlink and uplink.
  • the terminal device 1 includes carrier bandwidth information, initial downlink BWP bandwidth information, and information indicating the maximum allocated bandwidth in SIB1 corresponding to a certain cell (maximum allocated downlink bandwidth may be information indicating), and whether the device supports the downlink channel bandwidth that is the maximum transmission bandwidth setting of the bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP It may be determined whether the cell is a regulated cell based on whether or not and whether or not the device supports a downlink allocated bandwidth equal to or greater than the maximum allocated bandwidth.
  • the terminal device 1 may determine whether the cell is a regulated cell based on whether it supports a downlink bandwidth equal to or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support a downlink bandwidth equal to or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may regard the cell as a regulated cell.
  • the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier spacing of the initial downlink BWP set in the received SIB1.
  • the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier interval common to multiple initial downlink sub-BWPs set in the received SIB1.
  • the terminal device 1 supports a downlink allocated bandwidth equal to or wider than the maximum allocated bandwidth (which may be the maximum allocated bandwidth of the downlink) indicated by SIB1 (greater than or equal to the maximum allocated bandwidth) Based on this, it may be determined whether the cell is a regulated cell.
  • the downlink allocated bandwidth may be the maximum number of resource blocks for the downlink signal and/or downlink channel band scheduled by the base station device 3 .
  • the downlink channel allocation bandwidth is the one or more discretely arranged downlink It may be the bandwidth from the lowest frequency to the highest frequency of the link signal and/or downlink channel.
  • the downlink channel bandwidth supported by the terminal device 1 is narrower than the carrier bandwidth in the cell and wider than the initial downlink BWP bandwidth in the cell.
  • the allocated bandwidth is wider than the maximum allocated bandwidth in the cell.
  • the terminal device 1 does not have to regard the cell as a regulated cell based on the downlink channel bandwidth supported by the terminal device 1 and the downlink allocated bandwidth.
  • the terminal device 1 may regard the cell as a restricted cell. However, if the downlink channel allocation bandwidth supported by the terminal device 1 is narrower than the maximum allocated bandwidth, the terminal device 1 may regard the cell as a restricted cell.
  • FIG. 18 is a flow chart showing an example of a regulated cell determination process in the terminal device 1 of this embodiment.
  • the terminal device 1 determines whether or not it supports a downlink channel band equal to or less than the carrier bandwidth indicated by the SIB and equal to or greater than the initial downlink BWP bandwidth. If the determination is yes (S1001-Yes), in step S1002, it is determined whether or not a downlink allocated bandwidth equal to or greater than the maximum allocated bandwidth in the cell set in SIB1 is supported. If the determination in step S1001 or step S1002 is negative (S1001-No or S1002-No), the terminal device 1 considers the cell to be a restricted cell (S1003).
  • 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.
  • initialUplinkBWP-rc includes information indicating sub-BWP settings, information elements for PUCCH settings, and/or information elements for PUSCH settings.
  • initialUplinkBWP-rc may be a parameter indicating settings for each of a plurality of initial uplink sub-BWPs.
  • each of the multiple initial uplink sub-BWPs set in initialUplinkBWP-rc may be the initial uplink BWP (initial UL BWP).
  • each of the multiple uplink sub-BWPs may be configured by the network to include physical random access channel resources in the frequency domain.
  • initialUplinkBWP-rc may contain a list of information indicating frequency locations and bandwidths.
  • Each entry in the list of information indicating frequency locations and bandwidths may correspond to each of a plurality of initial uplink sub-BWPs.
  • Each entry in the list of information indicating frequency location and bandwidth may be a BWP information element (subcarrierSpacing, locationAndBandwidth, cyclicPrefix, etc.).
  • the multiple initial uplink sub-BWPs have a common bandwidth, and initialUplinkBWP-rc may indicate a list of frequency locations of the initial uplink sub-BWPs and the common bandwidth.
  • the multiple initial uplink sub-BWPs have a common subcarrierSpacing, a common cyclicPrefix, and initialUplinkBWP-rc indicates a list of frequency locations of the initial uplink BWPs, a common bandwidth, a common subcarrierSpacing, and a common cyclicPrefix.
  • subcarrierSpacing and cyclicPrefix indicated by initialUplinkBWP may be set in a plurality of initial uplink sub-BWPs. That is, initialUplinkBWP-rc may be information for specifying the frequency position and bandwidth of each of the multiple initial uplink sub-BWPs.
  • parameters indicating the setting of multiple initial uplink sub-BWPs may be set in the above-mentioned initialUplinkBWP.
  • the parameters indicating the initial uplink BWP configuration of a certain serving cell are the parameters indicating the frequency position and bandwidth of the initial uplink BWP, the subcarrierSpacing of the initial uplink BWP, the cyclicPrefix of the initial uplink BWP, and a plurality of initial uplink sub-BWPs. may include a parameter indicating the setting of
  • the terminal device 1 When the terminal device 1 does not support any frequency band for the TDD downlink and the frequency band for the FDD uplink for the frequency bands indicated in the frequencyBandList included in the frequencyInfoDL and the frequencyBandList included in the frequencyInfoUL.
  • the cell may be regarded as a regulation cell.
  • the terminal device 1 supports one or more frequency bands for the TDD downlink for the frequency bands indicated in frequencyBandList included in frequencyInfoDL, or the terminal device 1 is included in frequencyInfoUL
  • the terminal device 1 determines whether the cell is a regulated cell based on whether one or more frequency bands for the FDD uplink are supported for the frequency bands indicated in frequencyBandList.
  • the terminal device 1 may For example, based on the frequency band indicated in the frequencyBandList included in frequencyInfoDL and/or the frequency band indicated in the frequencyBandList included in frequencyInfoUL and/or the capability of the terminal device 1, the terminal device 1 regards the cell as a regulated cell. You may decide whether For example, the terminal device 1 does not support even one frequency band for the downlink of TDD for the frequency bands indicated in the frequencyBandList included in frequencyInfoDL, and the terminal device 1 does not support the frequency band listed in the frequencyBandList included in frequencyInfoUL. If the indicated frequency band does not support any frequency band for uplink of FDD, the terminal device 1 may regard the cell as a regulated cell.
  • a plurality of initial uplink sub-BWPs may be set in the terminal device 1 by the received SIB1.
  • the terminal device 1 may determine whether the cell is a regulated cell based on the bandwidth of the initial uplink BWP set by the received SIB1 corresponding to the cell.
  • the terminal device 1 may determine whether the cell is a regulated cell based on whether it supports an uplink bandwidth equal to or wider than the bandwidth of the initial uplink BWP set by SIB1. . For example, if the terminal device 1 does not support an uplink bandwidth equal to or wider than the bandwidth of the initial uplink BWP set by SIB1, the terminal device 1 may regard the cell as a regulated cell. .
  • the terminal device 1 may determine whether a cell is a regulated cell based on the bandwidths of a plurality of initial uplink sub-BWPs set by the received SIB1 corresponding to the cell. Based on whether the terminal device 1 supports an uplink bandwidth that is the same as or wider than the widest bandwidth among the bandwidths of each of the multiple initial uplink sub-BWPs set by SIB1, the cell is It may determine whether it is a regulated cell. For example, if the terminal device 1 does not support an uplink bandwidth equal to or wider than the widest bandwidth among the bandwidths of each of the multiple initial uplink sub-BWPs set by SIB1, the terminal device 1 , the cell may be regarded as a regulation cell.
  • the cell Based on whether the terminal device 1 supports an uplink bandwidth that is the same as or wider than the bandwidth set in common for multiple initial uplink sub-BWPs set by SIB1, the cell is a regulated cell. For example, if the terminal device 1 does not support an uplink bandwidth that is the same as or wider than the bandwidth set in common for multiple initial uplink sub-BWPs set by SIB1, the terminal device 1 is in the cell may be regarded as a regulation cell. Based on whether the terminal device 1 supports an uplink bandwidth that is the same as or wider than the bandwidth specified by the parameters that configure a plurality of initial uplink sub-BWPs notified by SIB1, the cell is regulated. It may be determined whether it is a cell.
  • the terminal device 1 A cell may be regarded as a regulation cell.
  • Terminal device 1 determines whether the cell is a regulated cell based on whether it supports an uplink bandwidth that is the same as or wider than the reference bandwidth identified from the bandwidth notified by SIB1. you can For example, if the terminal device 1 does not support an uplink bandwidth equal to or wider than the reference bandwidth specified from the bandwidth notified by SIB1, the terminal device 1 may regard the cell as a regulated cell. good.
  • the reference bandwidth may be the bandwidth of one initial uplink BWP notified by SIB1 and the bandwidth identified from the number of initial uplink sub-BWPs set.
  • the reference bandwidth may be a bandwidth specified by dividing one initial uplink BWP signaled by SIB1 by a predetermined number.
  • the terminal device 1 may determine whether the cell is a regulated cell based on whether it supports an uplink channel bandwidth equal to or narrower than the carrier bandwidth indicated by SIB1. However, when the terminal device 1 supports a certain bandwidth, it means that it is possible to tune/retune the band of the RF circuit of the terminal device within that bandwidth, and transmit and receive signals/channels within that bandwidth. It can mean something.
  • the uplink channel bandwidth supported by the terminal device 1 may be an uplink channel bandwidth in which signals/channels can be transmitted using RF tuning/RF retuning. For example, if the terminal device 1 does not support an uplink channel bandwidth equal to or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may regard the cell as a restricted cell.
  • the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier spacing of the initial uplink BWP set in the received SIB1.
  • the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier interval common to multiple initial uplink sub-BWPs set in the received SIB1.
  • the terminal device 1 in SIB1 corresponding to a certain cell, carrier bandwidth information, initial uplink BWP bandwidth information, and information indicating the maximum allocated bandwidth (uplink maximum allocated bandwidth may be information indicating), and whether the device supports the uplink channel bandwidth that is the maximum transmission bandwidth setting of the bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial uplink BWP It may be determined whether the cell is a regulated cell based on whether or not and whether or not the device supports an uplink allocated bandwidth equal to or greater than the maximum allocated bandwidth.
  • the terminal device 1 may determine whether the cell is a regulated cell based on whether it supports an uplink bandwidth equal to or narrower than the carrier bandwidth indicated by SIB1. For example, if the terminal device 1 does not support an uplink bandwidth equal to or narrower than the carrier bandwidth indicated by the received SIB1, the terminal device 1 may regard the cell as a regulated cell.
  • the carrier bandwidth may be the carrier bandwidth corresponding to the subcarrier spacing of the initial uplink BWP set in the received SIB1.
  • the carrier bandwidth may be a carrier bandwidth corresponding to a subcarrier interval common to multiple initial uplink sub-BWPs set in the received SIB1.
  • the terminal device 1 supports an uplink allocated bandwidth equal to or wider (greater than or equal to the maximum allocated bandwidth) as the maximum allocated bandwidth indicated by SIB1 (which may be the maximum allocated uplink bandwidth) may determine whether the cell is a regulated cell.
  • the uplink allocated bandwidth may be the maximum number of resource blocks for the band of uplink signals and/or uplink channels scheduled by the base station device 3 .
  • the uplink channel allocation bandwidth is It may be the bandwidth from the lowest frequency to the highest frequency of the link signal and/or uplink channel.
  • the uplink channel bandwidth supported by the terminal device 1 is narrower than the carrier bandwidth in the cell and wider than the initial uplink BWP bandwidth in the cell.
  • the allocated bandwidth is wider than the maximum allocated bandwidth in the cell.
  • the terminal device 1 does not have to regard the cell as a regulated cell based on the uplink channel bandwidth supported by the terminal device 1 and the uplink allocated bandwidth.
  • the terminal device 1 may regard the cell as a regulated cell. However, if the uplink channel allocation bandwidth supported by the terminal device 1 is narrower than the maximum allocated bandwidth, the terminal device 1 may regard the cell as a restricted cell.
  • FIG. 20 is a flow chart showing another example of the regulated cell determination process in the terminal device 1 of the present embodiment.
  • the terminal device 1 determines whether it supports an uplink channel band that is equal to or less than the carrier bandwidth indicated by SIB and equal to or greater than the initial uplink BWP bandwidth. If the determination is yes (S2001-Yes), in step S2002, it is determined whether or not the cell supports an uplink allocation bandwidth equal to or greater than the maximum allocation bandwidth in the cell set in SIB1. If the determination in step S2001 or step S2002 is negative (S2001-No or S2002-No), the terminal device 1 regards the cell as a restricted cell (S2003).
  • the terminal device 1 the bandwidth of the initial downlink BWP set by the received SIB1 corresponding to a certain cell, the bandwidth of a plurality of initial downlink sub-BWP set by the received SIB1 corresponding to a certain cell, The bandwidth of the initial uplink BWP set by the received SIB1 corresponding to a cell, the bandwidth of multiple initial uplink sub-BWPs set by the received SIB1 corresponding to a cell, the received Based on the carrier bandwidth set by SIB1 and/or the terminal equipment 1 capabilities, it may be determined whether the cell is a regulated cell.
  • parameters set in SIB1 may be broadcast in SIB1 (or REDCAP SIB1), may be broadcast in another SIB (or REDCAP SIB), or may be notified in an RRC message.
  • the reference signals described below in this embodiment include downlink reference signals, synchronization signals, SS/PBCH blocks, downlink DMRS, CSI-RS, uplink reference signals, SRS, and/or uplink DMRS.
  • downlink reference signals, synchronization signals and/or SS/PBCH blocks may be referred to as reference signals.
  • Reference signals used in the downlink include downlink reference signals, synchronization signals, SS/PBCH blocks, downlink DMRS, CSI-RS, and the like.
  • Reference signals used in uplink include uplink reference signals, SRSs, and/or uplink DMRSs.
  • the reference signal may be used for radio resource measurement (RRM). Also, the reference signal may be used for beam management.
  • RRM radio resource measurement
  • the reference signal may be used for beam management.
  • Beam management consists of analog and/or digital beams at the transmitting device (base station device 3 for the downlink and terminal device 1 for the uplink) and the receiving device (terminal device 1 for the downlink). , the base station device 3 in the case of uplink) to align analog and/or digital beams and obtain beam gain.
  • the procedure for configuring, setting or establishing a beam pair link may include the following procedure. ⁇ Beam selection ⁇ Beam refinement ⁇ Beam recovery
  • beam selection may be a procedure for selecting a beam in communication between the base station device 3 and the terminal device 1.
  • the beam improvement may be a procedure of selecting a beam with a higher gain or changing the optimum beam between the base station device 3 and the terminal device 1 by moving the terminal device 1 .
  • Beam recovery may be a procedure for reselecting a beam when the quality of a communication link deteriorates due to blockage caused by obstacles or people passing through in communication between the base station device 3 and the terminal device 1 .
  • Beam management may include beam selection, beam refinement.
  • Beam recovery also called beam failure recovery, may include the following procedures. ⁇ Detecting beam failure ⁇ Finding new beams ⁇ Sending beam recovery requests ⁇ Monitoring responses to beam recovery requests
  • RSRP Reference Signal Received Power
  • CSI-RS resource index CRI: CSI-RS Resource Index
  • DMRS sequence of reference signals
  • the base station apparatus 3 indicates a beam to the terminal apparatus 1, it indicates the CRI or SS/PBCH time index, and the terminal apparatus 1 receives based on the indicated CRI or SS/PBCH time index. do.
  • the terminal device 1 may set a spatial filter based on the indicated CRI or SS/PBCH time index for reception. Also, the terminal device 1 may receive using the assumption of Quasi Co-Location (QCL). To say that one signal (antenna port, synchronization signal, reference signal, etc.) is "QCL" with another signal (antenna port, synchronization signal, reference signal, etc.) or "QCL assumption is used" means that a signal is It may be interpreted as being associated with another signal.
  • QCL Quasi Co-Location
  • Two antenna ports are said to be QCL if the Long Term Property of the channel over which a symbol is carried at one antenna port can be inferred from the channel over which a symbol at the other antenna port is carried.
  • the long-term characteristics of the channel include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. For example, if antenna port 1 and antenna port 2 are QCL in terms of average delay, it means that the reception timing of antenna port 2 can be inferred from the reception timing of antenna port 1 .
  • This QCL can also be extended to beam management.
  • a new QCL extended to the space may be defined.
  • the long term property of the channel in the spatial domain QCL assumption is the angle of arrival (AoA, Zenith angle of arrival, etc.) and/or angular spread in the radio link or channel.
  • Angle Spread e.g. ASA (Angle Spread of Arrival) or ZSA (Zenith angle Spread of Arrival)
  • delivery angle AoD, ZoD, etc.
  • Angle Spread e.g. ASD (Angle Spread of Departure), ZSD (Zenith angle Spread of Departure), Spatial Correlation, and receive spatial parameters.
  • the reception beam that receives the signal from antenna port 1 receives the signal from antenna port 2. It means that the beam can be inferred.
  • a QCL type may be defined as a combination of long-term features that may be considered a QCL.
  • the following types may be defined.
  • ⁇ Type A Doppler shift, Doppler spread, mean delay, delay spread
  • ⁇ Type B Doppler shift, Doppler spread
  • ⁇ Type C Mean delay
  • ⁇ Type D Reception spatial parameters
  • the above QCL types are configured as a Transmission Configuration Indication (TCI) and/or the assumption of QCL with one or two reference signals and PDCCH or PDSCH DMRS at the RRC and/or MAC layer and/or DCI. You can direct.
  • TCI Transmission Configuration Indication
  • the terminal device 1 When receiving PDCCH DMRS, it is assumed that Doppler shift, Doppler spread, average delay, delay spread, reception spatial parameters and long-term characteristics of the channel in receiving SS/PBCH block index #2 are received and synchronized with DMRS of PDCCH. Channel estimation may be performed.
  • the reference signal indicated by the TCI is the source reference signal, and the reference is affected by the long-term characteristics inferred from the long-term characteristics of the channel when receiving the source reference signal.
  • the signal (PDCCH DMRS in the example above) may be referred to as a target reference signal.
  • TCI one or more TCI states and a combination of a source reference signal and a QCL type for each state are set in RRC, and may be indicated to the terminal device 1 by the MAC layer or DCI.
  • beam management and beam indication/reporting are defined by the assumption of QCL in the spatial domain and the operation of the base station device 3 and the terminal device 1 equivalent to beam management by radio resources (time and/or frequency). good.
  • FIG. 21 is a diagram showing an example of beamforming.
  • a plurality of antenna elements are connected to one transmission unit (TXRU: Transceiver unit) 50, phase is controlled by a phase shifter 51 for each antenna element, and transmitted from the antenna element 52, so that the transmitted signal can be sent in any direction. You can direct the beam.
  • TXRU Transmission Unit
  • a TXRU may be defined as an antenna port, and only antenna ports may be defined in the terminal device 1 .
  • Directivity can be oriented in any direction by controlling the phase shifter 51, so that the base station apparatus 3 can communicate with the terminal apparatus 1 using a high-gain beam.
  • FIG. 22 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 whether a cell is a restricted cell based on information in system information blocks (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB).
  • 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 of receiving a 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 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 SSB, PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and/or DMRS for REDCAP PBCH.
  • the radio transmitting/receiving unit 10 may have a function of receiving SS/PBCH blocks and/or REDCAP PBCH blocks.
  • the radio transmitting/receiving unit 10 may have a function of receiving system information blocks (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB) corresponding to a predetermined cell.
  • 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. 23 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 bit information of the MIB transport block.
  • the upper layer processing unit 34 may have a function of generating bit information of transport blocks of the REDCAP MIB.
  • the upper layer processing unit 34 may have a function to generate a system information block (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB) containing information for the terminal device to determine whether a given cell is a
  • 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 transmitting/receiving unit 30 may have a function of transmitting SSB, PSS, SSS, PBCH, DMRS for PBCH, REDCAP PBCH, and/or DMRS for REDCAP PBCH.
  • the radio transmitting/receiving unit 30 may have a function of transmitting SS/PBCH blocks and/or REDCAP PBCH blocks.
  • 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 system information blocks (SIB1, REDCAP SIB1, SIB and/or REDCAP SIB).
  • 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. Note that when the base station device 3 is connected to one or a plurality of transmission/reception points 4, part or all of the functions of the radio transmission/reception section 30 may be included in each transmission/reception point 4.
  • FIG. 1 is a diagrammatic representation of the radio transmitting/receiving unit 30 .
  • 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. 23 other components of the base station device 3 and data (control information) transmission paths between the components are omitted, but other functions necessary for operating 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 terminal device 1 in the first aspect of the present invention comprises a receiving unit 10 for receiving a system information block containing first information for setting parameters of the first cell, and a processing unit 14,
  • the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell, a parameter (initialUplinkBWP/locationAndBandwidth) indicating the bandwidth of the initial uplink BWP of the first cell, and the first and a parameter (allocationBandwidth) indicating the maximum allocated bandwidth of the cell
  • the processing unit 14 determines the maximum transmission bandwidth of the bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial uplink BWP for the terminal device Based on whether the uplink channel bandwidth that is the bandwidth setting is supported and whether the terminal device 1 supports the allocated bandwidth equal to or greater than the maximum allocated bandwidth, the first cell is a regulation cell ( barred cell), the allocated bandwidth is the maximum number of resource blocks of the band of the uplink channel scheduled by the base station device 3, and the maximum transmission bandwidth setting is the
  • the base station device 3 includes the processing unit 34 that generates a system information block including first information for setting the parameters of the first cell, and the terminal device 1 that transmits the system information and a transmission unit 30 that transmits blocks, wherein the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell and the bandwidth of the initial uplink BWP of the first cell.
  • the processing unit 34 that generates a system information block including first information for setting the parameters of the first cell
  • the terminal device 1 that transmits the system information
  • a transmission unit 30 that transmits blocks, wherein the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell and the bandwidth of the initial uplink BWP of the first cell.
  • the terminal device 1 is equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial uplink BWP and whether or not to support an uplink channel bandwidth that is the maximum transmission bandwidth setting of the bandwidth, and whether or not the terminal device 1 supports an allocated bandwidth equal to or greater than the maximum allocated bandwidth.
  • the terminal device 1 determines whether one cell is a regulated cell, the allocated bandwidth is the maximum number of resource blocks of the band of the uplink channel scheduled by the base station device 3, and the The maximum transmission bandwidth setting indicates the number of resource blocks in a band that the terminal device 1 can receive by adjusting the frequency position of the transmitter of the terminal device 1 .
  • the terminal device 1 comprises a receiving unit 10 for receiving a system information block containing first information for setting the parameters of the first cell, and a processing unit 14,
  • the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell, a parameter (initialDownlinkBWP, locationAndBandwidth) indicating the bandwidth of the initial downlink BWP of the first cell, and the first and a parameter (allocationBandwidth) indicating the maximum allocated bandwidth of the cell
  • the processing unit 14 determines the maximum transmission bandwidth of the bandwidth equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP.
  • the first cell is a regulated cell based on whether the downlink channel bandwidth that is the bandwidth setting is supported and whether the terminal device 1 supports an allocated bandwidth equal to or greater than the maximum allocated bandwidth.
  • the allocated bandwidth is the maximum number of resource blocks of a downlink channel band scheduled by the base station apparatus 3, and the maximum transmission bandwidth setting is the terminal in the first cell; It indicates the number of resource blocks in a band that can be received by the device 1 by adjusting the frequency position of the receiver of the terminal device 1 .
  • the base station device 3 includes the processing unit 34 that generates a system information block including first information for setting the parameters of the first cell, and the terminal device 1 that transmits the system information and a transmission unit 30 that transmits blocks, wherein the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell and the bandwidth of the initial downlink BWP of the first cell.
  • the processing unit 34 that generates a system information block including first information for setting the parameters of the first cell
  • the terminal device 1 that transmits the system information
  • a transmission unit 30 that transmits blocks, wherein the first information includes a parameter (carrierbandwidth) indicating the carrier bandwidth of the first cell and the bandwidth of the initial downlink BWP of the first cell.
  • the terminal device 1 is equal to or less than the carrier bandwidth and equal to or greater than the bandwidth of the initial downlink BWP and whether or not to support a downlink channel bandwidth that is the maximum transmission bandwidth setting of the bandwidth of and whether or not the terminal device 1 supports an allocated bandwidth equal to or greater than the maximum allocated bandwidth.
  • the terminal device 1 determines whether one cell is a regulated cell, the allocated bandwidth is the maximum number of resource blocks of the downlink channel band scheduled by the base station device 3, and the The maximum transmission bandwidth setting indicates the number of resource blocks in a band that the terminal device 1 can receive by adjusting the frequency position of the receiver of the terminal device 1 .
  • the terminal device 1 and the base station device 3 can communicate efficiently.
  • the terminal device 1 can perform a random access procedure based on its terminal type or SSB RSRP with the base station device 3 .
  • a program that runs on a device according to one aspect of the present invention is a program that controls a Central Processing Unit (CPU) or the like to function a computer so as to realize the functions of the embodiments according to one aspect of the present invention. Also good. 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 embodiment related to one aspect of the present invention may be recorded on 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” referred to here is a computer system built into 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.
  • semiconductor technology progresses and an integrated circuit technology that replaces the current integrated circuit appears, 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.
  • One aspect of the present invention is, for example, a communication system, a communication device (e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device), an integrated circuit (e.g., a communication chip), or a program, etc. be able to.
  • a communication device e.g., a mobile phone device, a base station device, a wireless LAN device, or a sensor device
  • an integrated circuit e.g., a communication chip
  • a program etc. be able to.
  • 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 Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Ce dispositif terminal reçoit un SIB comprenant des premières informations d'une première cellule, les premières informations comprenant un paramètre indiquant une bande passante de porteuse, un paramètre indiquant une bande passante d'une BWP DL initiale, ainsi qu'un paramètre indiquant une bande passante attribuée maximale, puis détermine si la première cellule est une cellule régulée selon qu'une bande passante de canal DL d'une bande passante inférieure ou égale à la bande passante de porteuse et supérieure ou égale à la bande passante de la BWP DL initiale est prise en charge ou non, et qu'une bande passante attribuée supérieure ou égale à la bande passante allouée maximale est prise en charge ou non.
PCT/JP2022/012022 2021-03-19 2022-03-16 Dispositif terminal, dispositif de station de base et procédé de communication WO2022196735A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2023507160A JPWO2022196735A1 (fr) 2021-03-19 2022-03-16

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2021045414 2021-03-19
JP2021-045414 2021-03-19

Publications (1)

Publication Number Publication Date
WO2022196735A1 true WO2022196735A1 (fr) 2022-09-22

Family

ID=83321077

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/012022 WO2022196735A1 (fr) 2021-03-19 2022-03-16 Dispositif terminal, dispositif de station de base et procédé de communication

Country Status (2)

Country Link
JP (1) JPWO2022196735A1 (fr)
WO (1) WO2022196735A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024078192A1 (fr) * 2022-10-09 2024-04-18 中国电信股份有限公司 Procédé de configuration de bande passante spécifique à un terminal, et dispositif associé

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200413450A1 (en) * 2019-06-26 2020-12-31 Samsung Electronics Co., Ltd. Method and apparatus for random access in wireless communication system

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200413450A1 (en) * 2019-06-26 2020-12-31 Samsung Electronics Co., Ltd. Method and apparatus for random access in wireless communication system

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "On the bandwidth of initial BWP", 3GPP DRAFT; R4-1909102 ON THE BANDWIDTH OF INITIAL BWP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG4, no. Ljubljana, Slovenia; 20190826 - 20190830, 16 August 2019 (2019-08-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051772007 *
NOKIA, NOKIA SHANGHAI BELL: "UE Complexity Reduction", 3GPP DRAFT; R1-2100499, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20210125 - 20210205, 18 January 2021 (2021-01-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051970412 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024078192A1 (fr) * 2022-10-09 2024-04-18 中国电信股份有限公司 Procédé de configuration de bande passante spécifique à un terminal, et dispositif associé

Also Published As

Publication number Publication date
JPWO2022196735A1 (fr) 2022-09-22

Similar Documents

Publication Publication Date Title
JP7246874B2 (ja) 基地局装置、端末装置、および、通信方法
CN113475138B (zh) 用户设备、基站装置及通信方法
JP7249785B2 (ja) 端末装置、基地局装置、および通信方法
JP7287787B2 (ja) 基地局装置、端末装置、通信方法、および、集積回路
WO2020166672A1 (fr) Dispositif station de base, dispositif terminal et procédé de communication
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) 基站装置、终端装置以及通信方法
JP2022174350A (ja) 端末装置、基地局装置、および、通信方法
WO2022196735A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
WO2022239492A1 (fr) Dispositif terminal, dispositif de station de base et procédé de communication
JP2022025801A (ja) 端末装置、基地局装置、および、通信方法
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) 端末装置、基地局装置、および、通信方法
WO2022196770A1 (fr) Équipement 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
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

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: 22771480

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023507160

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22771480

Country of ref document: EP

Kind code of ref document: A1