WO2023054684A1 - Terminal, base station, and wireless communication method - Google Patents

Abstract

The present invention comprises: a reception unit for receiving system information that includes information used to set a first initial downlink bandwidth portion, cell-specific information relating to a physical downlink control channel configuration in the first initial downlink bandwidth portion, information used to set a second initial downlink bandwidth portion, and cell-specific information relating to a physical downlink control channel configuration in the second initial downlink bandwidth portion; and a control unit for determining an opportunity for monitoring a physical downlink control channel for paging, the determination being made on the basis of information relating to a synchronization signal and a physical notification channel block that are transmitted in the second initial downlink bandwidth portion, and a search space identifier.

Description

TERMINAL, BASE STATION, AND WIRELESS COMMUNICATION METHOD Cross-reference to related applications

This application is based on Japanese Patent Application No. 2021-162296 filed on September 30, 2021, and claims the benefit of its priority. incorporated herein by reference.

The present disclosure relates to terminals, base stations, and wireless communication methods.

In the Third Generation Partnership Project (3GPP), an international standardization organization, Long Term Evolution (LTE), which is the 3.9th generation Radio Access Technology (RAT), and LTE-Advanced, which is the 4th generation RAT As a successor, Release 15, which is New Radio (NR), which is a fifth generation (5G) RAT, has been specified (Non-Patent Document 1). LTE and/or LTE-Advanced is also called Evolved Universal Terrestrial Radio Access (E-UTRA).

In 3GPP (for example, Release 17 that defines NR), terminals that assume lower performance and price range than terminals introduced in Release 15 or 16 (hereinafter referred to as "existing terminals") capability: RedCap (also referred to as "terminal") is under consideration. Specifically, it is being considered to make it possible to newly set an initial DL BWP for RedCap terminals in a cell in which an initial downlink bandwidth part (Initial Downlink BWP) is set. Also, transmission of a synchronization signal block (SSB) in the initial DL BWP for RedCap terminals is being considered.

However, an initial DL BWP (hereinafter referred to as “second initial DL BWP”) is set separately from the existing initial DL BWP (hereinafter referred to as “first initial DL BWP”) in the cell, and the second initial If SSB can also be transmitted in DL BWP, the terminal may not be able to properly control the operation based on SSB. As an operation based on such an SSB, for example, an operation of determining a predetermined period used for monitoring a downlink control channel for paging (hereinafter referred to as "PDCCH monitoring occasion") is assumed.
An object of the present disclosure is to provide a terminal and a wireless communication method capable of appropriately controlling operations related to paging.

A terminal according to an aspect of the present disclosure includes information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in the first initial downlink bandwidth portion, information, information used to configure a second initial downlink bandwidth portion, and system information including cell-specific information regarding configuration of a physical downlink control channel in said second initial downlink bandwidth portion. When the cell-specific information related to the setting of the physical downlink control channel in the receiving unit to receive and the second initial downlink bandwidth part includes the identifier of the search space for paging, the second initial downlink A control unit that determines monitoring opportunities of a physical downlink control channel for paging based on information about synchronization signals and physical broadcast channel (SS/PBCH) blocks transmitted in the link bandwidth portion and the identifier of the search space. And prepare.

A base station according to an aspect of the present disclosure includes information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in the first initial downlink bandwidth portion, information used to configure a second initial downlink bandwidth portion; and system information including cell-specific information regarding configuration of a physical downlink control channel in said second initial downlink bandwidth portion. and the identifier of the search space for paging is included in the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion, the second initial Information about synchronization signals and physical broadcast channel (SS/PBCH) blocks transmitted in the downlink bandwidth portion, and control for setting monitoring opportunities of the physical downlink control channel for paging based on the identifier of the search space. and

A wireless communication method for a terminal according to an aspect of the present disclosure includes information used to set a first initial downlink bandwidth portion, setting of a physical downlink control channel in the first initial downlink bandwidth portion cell-specific information about, information used to configure a second initial downlink bandwidth portion, and cell-specific information regarding configuration of a physical downlink control channel in the second initial downlink bandwidth portion and receiving system information including the second initial downlink bandwidth portion, if the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion includes an identifier of a search space for paging, the second Determine physical downlink control channel monitoring opportunities for paging based on information about synchronization signals and physical broadcast channel (SS/PBCH) blocks transmitted in the initial downlink bandwidth portion of and the identifier of the search space. and a step of.

A radio communication method for a base station according to an aspect of the present disclosure includes information used for setting a first initial downlink bandwidth portion, a physical downlink control channel in the first initial downlink bandwidth portion cell-specific information on configuration, information used to configure a second initial downlink bandwidth portion, and cell-specific information on configuration of a physical downlink control channel in said second initial downlink bandwidth portion. and a step of transmitting system information containing the above; Information about synchronization signals and physical broadcast channel (SS/PBCH) blocks transmitted in the initial downlink bandwidth portion of 2, and based on the identifier of the search space, a physical downlink control channel monitoring opportunity for paging. and setting.

According to one aspect of the present disclosure, operations related to paging can be appropriately controlled.

FIG. 1 is a diagram showing an example of an outline of a wireless communication system according to this embodiment. FIG. 2 is a diagram showing an example of the SSB according to this embodiment. FIG. 3 is a diagram showing an example of an SS burst set according to this embodiment. FIG. 4 is a diagram showing an example of BWP in this embodiment. FIG. 5 is a diagram showing an example of first and second initial DL/UP BWPs according to this embodiment. FIGS. 6A and 6B are diagrams showing examples of first and second initial DL BWPs according to this embodiment. FIG. 7 is a diagram showing an example of SSB, PF and PO according to this embodiment. FIG. 8 is a diagram showing an example of SSB, PF and PO according to this embodiment. FIG. 9 is a flow chart showing an example of operation for setting PDCCH monitoring opportunities for paging according to the present embodiment. FIG. 10 is a diagram showing an example of the relationship between SSB and RO and RA preambles according to this embodiment. FIG. 11 is a diagram showing another example of the relationship between SSB and RO and RA preambles according to this embodiment. FIG. 12 is a flowchart showing an example of the RO and/or RA preamble selection operation according to this embodiment. FIG. 13 is a diagram showing an example of the MIB according to this embodiment. FIG. 14 is a flow chart showing an example of the operation at the time of MIB reception according to this embodiment. FIG. 15 is a diagram showing an example of BWP-DownlinkCommon according to this embodiment. FIG. 16 is a diagram showing an example of BWP-UplinkCommon according to this embodiment. FIG. 17 is a diagram showing an example of RACH-ConfigCommon according to this embodiment. FIG. 18 is a diagram showing an example of RACH-ConfigCommonTwoStepRA according to this embodiment. FIG. 19 is a diagram showing an example of the hardware configuration of each device in the wireless communication system according to this embodiment. FIG. 20 is a diagram showing an example of a functional block configuration of a terminal according to this embodiment. FIG. 21 is a diagram showing an example of the functional block configuration of the base station according to this embodiment.

The present embodiment will be described below with reference to the accompanying drawings. In order to facilitate understanding of the description, the same constituent elements in each drawing are denoted by the same reference numerals as much as possible, and overlapping descriptions are omitted.

FIG. 1 is a diagram showing an example of an overview of a wireless communication system according to this embodiment. As shown in FIG. 1, the wireless communication system 1 may include a terminal 10, a base station 20, and a core network 30. Note that the numbers of terminals 10 and base stations 20 shown in FIG. 1 are merely examples, and are not limited to the numbers shown.

The radio communication system 1 is a system that communicates in compliance with the radio access technology (RAT) defined by 3GPP. As a radio access technology to which the radio communication system 1 conforms, for example, a fifth generation RAT such as NR is assumed, but not limited to this, for example, a fourth generation RAT such as LTE, LTE-Advanced, etc. One or more RATs can be used, such as a 6th generation RAT or later, or a non-3GPP RAT such as Wi-Fi®. Note that the wireless communication system 1 is a form of communication that conforms to a wireless access technology defined by a standard development organization different from 3GPP (for example, Institute of Electrical and Electronics Engineers (IEEE), Internet Engineering Task Force (IETF)). may be

The terminal 10 is a device corresponding to a terminal (for example, UE (User Equipment)) defined in the 3GPP specifications. The terminal 10 is, for example, a predetermined terminal or device such as a smartphone, a personal computer, a car, an in-vehicle terminal, an in-vehicle device, a stationary device, a telematics control unit (TCU), and an IoT device such as a sensor. Terminal 10 may also be called a User Equipment (UE), a Mobile Station (MS), a User Terminal, a Radio apparatus, a subscriber terminal, an access terminal, and so on. In addition, the terminal 10 may be a so-called Reduced capability (RedCap) terminal, such as an industrial wireless sensor, a surveillance camera (video service), a wearable device, etc. There may be. The terminal 10 may be mobile or stationary. The terminal 10 is configured to be able to communicate using one or more RATs such as NR, LTE, LTE-Advanced, Wi-Fi (registered trademark), for example. Note that the terminal 10 is not limited to a terminal defined in the 3GPP specifications, and may be a terminal complying with standards defined by other standard development organizations. Also, the terminal 10 does not have to be a standard-compliant terminal.

The base station 20 is a device corresponding to a base station (eg, gNodeB (gNB) or eNB) defined in the 3GPP specifications. The base station 20 forms one or more cells C and communicates with the terminal 10 using the cells. Cell C may be interchangeably referred to as serving cell, carrier, component carrier (CC), and the like. Cell C may also have a predetermined bandwidth. For example, base station 20 may communicate with terminal 10 using one or more cell groups. Each cell group may include one or more cells C. Aggregating multiple cells C within a cell group is called carrier aggregation. The plurality of cells C includes a primary cell (Primary Cell: PCell) or a primary SCG cell (Primary Secondary Cell Group (SCG) Cell: PSCell) and one or more secondary cells (Secondary Cell: SCG). Communicating with the terminal 10 using two cell groups is also called dual connectivity. Note that the terminal 10 is not limited to a base station defined in the 3GPP specifications, and may be a terminal complying with standards defined by other standard development organizations. Also, the terminal 10 does not have to be a base station conforming to the standards.

Base station 20 includes gNodeB (gNB), en-gNB, Next Generation-Radio Access Network (NG-RAN) node, low-power node, Central Unit (CU), Distributed Unit (DU), gNB It may also be called -DU, Remote Radio Head (RRH), Integrated Access and Backhaul/Backhauling (IAB) node, access point, and so on. The base station 20 is not limited to one node, and may be composed of a plurality of nodes (for example, a combination of a lower node such as DU and an upper node such as CU).

The core network 30 is, for example, a fifth generation core network (5G Core Network: 5GC) or a fourth generation core network (Evolved Packet Core: EPC), but is not limited to this. A device on the core network 30 (hereinafter also referred to as a “core network device”) may perform mobility management such as paging and location registration of the terminal 10 . A core network device may be connected to the base station 20 or terminal 10 via a predetermined interface (eg, S1 or NG interface).

The core network device includes, for example, an Access and Mobility Management Function (AMF) that manages C-plane information (e.g., information related to access and mobility management), and a User that controls transmission of U-plane information (e.g., user data). At least one Plane Function (UPF) may be included.

In the wireless communication system 1 , the terminal 10 receives a downlink (DL) signal from the base station 20 and/or transmits an uplink (UL) signal to the base station 20 . One or more cells C are configured in the terminal 10, and at least one of the configured cells is activated. The maximum bandwidth of each cell is, for example, 20 MHz or 400 MHz.

Also, the terminal 10 performs a cell search based on a synchronization signal (eg, Primary Synchronization Signal (PSS) and/or Secondary Synchronization Signal (SSS)) from the base station 20. Cell search is a procedure by which the terminal 10 acquires time and frequency synchronization in a cell and detects the identifier of the cell (eg, physical layer cell ID).

The terminal 10 determines a search space set and/or a control resource set (Control Resource Set: CORESET) based on parameters included in a Radio Resource Control (RRC) message (hereinafter referred to as "RRC parameters"). do. A CORESET may consist of frequency domain resources (eg, a predetermined number of resource blocks) and time domain resources (eg, a predetermined number of symbols). Note that the RRC parameter may also be called an RRC information element (Information Element: IE) or the like.

Terminal 10, within the search space set associated with the CORESET, downlink control channel (for example, physical downlink control channel (Physical Downlink Control Channel: PDCCH)) transmitted via downlink control information (Downlink Control Information: DCI) of perform monitoring; Note that the RRC message may include, for example, an RRC setup message, an RRC reconfiguration message, an RRC resume message, an RRC reestablishment message, system information, and the like.

DCI monitoring means that the terminal 10 blind-decodes the PDCCH candidate (PDCCH candidate) in the search space set in the assumed DCI format. The number of bits (also referred to as size, bit width, etc.) of the DCI format is predetermined or derived according to the number of bits of fields included in the DCI format. The terminal 10 specifies the number of bits in the DCI format and the scramble (hereinafter referred to as “CRC scramble”) of the cyclic redundancy check (CRC) bits (also referred to as CRC parity bits) of the DCI format. DCI for the terminal 10 is detected based on the Radio Network Temporary Identifier (RNTI). DCI monitoring is also called PDCCH monitoring, monitor, and the like. A given period for monitoring DCI or PDCCH is also called a PDCCH monitoring occasion.

A search space set is a set of one or more search spaces. A search space set commonly used by one or more terminals 10 (hereinafter referred to as a "common search space (CSS) set") and a terminal-specific search space set (UE-specific search space (USS) set), and The search space set includes a search space set for paging (hereinafter referred to as "paging search space"), a search space set for random access (RA) (hereinafter referred to as "RA search space"), and system information (hereinafter referred to as "system information search space"), etc. may also be included. Terminal 10 may receive information regarding the configuration of each search space set.

The terminal 10 monitors PDCCH using a search space set (or search space) at PDCCH monitoring opportunities and receives (or detects) DCI that is CRC-scrambled by a specific RNTI. The terminal 10 receives a downlink shared channel scheduled using the DCI (for example, a physical downlink shared channel (Physical Downlink Shared Channel: PDSCH)) and/or receives an uplink shared channel (for example, a physical uplink shared channel (Physical Controls transmission of Uplink Shared Channel: PUSCH)).

The system information broadcast in cell C may include a master information block (MIB) and/or one or more system information blocks (SIB). The MIB is broadcast via a broadcast channel (for example, a physical broadcast channel (PBCH)). MIB and SIB1 are also called Minimum System Information, and SIB1 is also called Remaining Minimum System Information (RMSI). SIBx (an arbitrary character string such as x=2, 3, . . . ) other than SIB1 is also called Other System Information (OSI). SIB1 and SIBx other than SIB1 are broadcast via PDSCH. SIB1 is cell-specific, and SIBx other than SIB1 may be cell-specific or area-specific containing one or more cells.

(SSB)
The SSB is a block containing at least one of a synchronization signal, a PBCH, and a demodulation reference signal (DM-RS) for the PBCH. An SSB may also be called an SS/PBCH block, an SS block, and so on.

FIG. 2 is a diagram showing an example of the SSB according to this embodiment. Note that FIG. 2 is merely an example, and the SSB is not limited to the illustrated one. As shown in FIG. 2, the SSB consists of a predetermined number of symbols (e.g., four consecutive symbols) as time domain resources and a predetermined number of subcarriers (e.g., consecutive four symbols) as frequency resource resources. 240 subcarriers).

For example, in FIG. 2, the PSS is transmitted in the first symbol within the SSB and mapped to 127 subcarriers. The remaining subcarriers of the first symbol may be empty. SSS is transmitted in the third symbol within SSB and is mapped to the same 127 subcarriers as PSS. A predetermined number (8 or 9) of empty subcarriers may be provided at both ends of the SSS. The PBCH is transmitted on the 2nd and 4th symbols in the SSB and mapped to 240 subcarriers. Also, the PBCH is mapped to 48 subcarriers at both ends of the SSS. Different numerologies (eg subcarrier spacing = 15, 30, 120 or 240 kHz) can be applied for SSB. A DMRS (not shown) may be mapped to some subcarriers indicated as PBCH in FIG.

An SS burst set, which is a set of one or more SSBs, is transmitted at predetermined intervals. Note that the SS burst set may also be called an SS burst or the like. The terminal 10 receives information (hereinafter referred to as "ssb-periodicityServingCell") regarding the period of the SSB or SS burst set (hereinafter referred to as "SSB period"). The ssb-periodicityServingCell may indicate the SSB period (eg, 5, 10, 20, 40, 80 or 160 ms).

Each SSB in the SS burst set is identified by an index (hereinafter referred to as "SSB index"). In the case of multi-beam operation, SSBs with different indexes in the SS burst set correspond to different beams, and may be transmitted by sequentially switching beam directions by beam sweeping. For single-beam operation, the SSB (single or multiple SSBs) of a particular index within the SS burst set may be transmitted in all directions.

The terminal 10 receives information about SSB transmission within the SS burst set (hereinafter referred to as "ssb-PositionsInBurst"). For example, ssb-PositionsInBurst may be a bitmap containing bits corresponding to each SSB in the SS burst set, with the value of each bit indicating whether the corresponding SSB is actually transmitted. For example, a bit value of '1' may indicate that the corresponding SSB is actually transmitted, and a bit value of '0' may indicate that the corresponding SSB is not actually transmitted. Note that ssb-PositionsInBurst is not limited to the above, and may be any information regarding SSB transmission within the SS burst set. ssb-PositionsInBurst may be cell specific. Also, ssb-PositionsInBurst is included in SIB1, for example, but may be included in other RRC messages.

FIG. 3 is a diagram showing an example of an SS burst set according to this embodiment. FIG. 3 is only an example, and the number of SSBs in the SS burst set, the SSB period, the subcarrier interval, the beam direction, the arrangement position of the SS burst set, etc. are not limited to those shown in the drawing. For example, in FIG. 3, SSBs #0 to #7 in the SS burst set are transmitted from the base station 20 at different times with beams #0 to #7 having different directivities.

An SS burst set containing one or more SSBs is placed in the first or second half frame (eg, 5 ms) of a radio frame, and is repeated at the SSB cycle. For example, in FIG. 3, the SS burst set including SSB #0 to #7 is arranged in the first half frame of the radio frame and repeated with an SSB period of 20 ms. As shown in FIG. 3, the positions within the half-frame where SSB#0-#7 are transmitted may vary depending on the subcarrier spacing.

Also, for example, in FIG. 3, ssb-PositionsInBurst is an 8-bit bitmap corresponding to each of SSB #0 to #7 and is set to "11111111". Therefore, the terminal 10 recognizes that all SSBs #0 to #7 in the SS burst set are transmitted. Thus, the terminal 10 determines the SSBs actually transmitted within the SS burst set based on ssb-PositionsInBurst.

Although FIG. 3 shows an example of multi-beam operation, it is also applicable to single-beam operation. For single-beam operation, a specific SSB (eg, only SSB#0) may be transmitted omnidirectionally, the bit corresponding to that specific SSB in ssb-PositionsInBurst is set to '1', and the other bits may be set to '0'.

(BWP)
For one cell C, one or a plurality of bandwidth parts (BWP) may be set. The BWP may include a BWP for DL (hereinafter referred to as "DL BWP") and/or a BWP for UL (hereinafter referred to as "UL BWP"). In addition, the BWP includes a BWP that is set unique to the cell (hereinafter referred to as "initial BWP"), a BWP that is uniquely set to the terminal 10 (hereinafter referred to as "dedicated BWP"), may include The initial BWP may be used for initial access and/or common to one or more terminals 10 . The initial BWP may include an initial BWP for DL (hereinafter referred to as "initial DL BWP") and an initial BWP for UL (hereinafter referred to as "initial UL BWP"). Dedicated BWP is also called "UE-specific BWP".

Initial DL BWP and/or initial UL BWP (hereinafter referred to as "initial DL/UL BWP") is equal to CORESET#0 determined based on a specific parameter in the MIB (hereinafter referred to as "pdcch-ConfigSIB1") may Alternatively, the initial DL/UL BWP may be set in the terminal 10 based on information on the initial DL/UL BWP received by the terminal 10 from the base station 20 (hereinafter referred to as "initial DL/UL BWP information"). . The initial DL/UL BWP information includes information indicating the location and/or bandwidth of the frequency domain of the initial DL/UL BWP (hereinafter referred to as "locationAndBandwidth") and information indicating subcarrier spacing (hereinafter referred to as "subcarrierSpacing"). , and information about a cyclic prefix (hereinafter referred to as “cyclicPrefix”). Initial DL/UL BWP information is a cell-specific RRC parameter and may be included in SIB1 or other RRC messages

The initial DL BWP is a DL BWP with a BWP identifier (hereinafter referred to as "bwp-id") = 0 (that is, DL BWP#0), and the initial UL BWP is a UL BWP with bwp-id = 0 (that is, UL BWP#0). On the other hand, an individual BWP for DL (hereinafter referred to as "individual DL BWP") is a DL BWP with bwp-id ≠ 0 (that is, DL BWP#bwp-id), and an individual BWP for UL (hereinafter referred to as "individual UL BWP") may be a UL BWP with bwp-id≠0 (that is, UL BWP#bwp-id). When one or more individual DL BWPs and/or one or more individual UL BWPs are configured in the terminal 10, one individual DL BWP and/or one individual UL BWP may be activated.

SSB is transmitted in one or more DL BWPs. For example, in the initial DL BWP, Cell Defining (CD)-SSB is transmitted, and in individual DL BWP, CD-SSB and/or Non Cell Defining (NCD)-SSB are transmitted. may be transmitted. A CD-SSB is an SSB associated with a particular cell and may be associated with SIB1. NCD-SSBs are SSBs that are not associated with a particular cell and may not be associated with SIB1.

FIG. 4 is a diagram showing an example of the DL BWP in this embodiment. Although DL BWP is shown in FIG. 4, it goes without saying that UL BWP may also be set. For example, in FIG. 4, multiple SSBXs (where X=1 to 4) are transmitted at predetermined frequency locations within cell C (or the bandwidth of cell C). Note that X is a number given for convenience to distinguish SSBs in different frequency domains, and does not indicate an SSB index that identifies each SSB within an SS burst set.

For example, in FIG. 4, terminals 10A and 10B are connected to cell #5 with NR Cell Global Identifier (NCGI)=5, and terminal 10C is connected to cell #6 with NGCI=6. shall be NGCI is the cell C identifier. Also, SSB1 is CD-SSB and is associated with cell #5 (and/or SIB1 broadcasted in cell #5). Similarly, SSB3 is CD-SSB and is associated with cell #6 (and/or SIB1 broadcast on cell #6). SSB2 and SSB4, on the other hand, are NCD-SSBs and are not associated with SIB1 of a particular cell.

In FIG. 4, terminals 10A and 10B are connected to cell #5, so they may detect SSB1 associated with cell #5 and set initial DL BWP#0 based on SSB1. In addition, the terminal 10A sets individual DL BWP #1 and #2 based on parameters unique to the terminal 10A. Terminal 10A may use individual DL BWP #1 and #2 by switching over time. On the other hand, terminal 10B sets individual DL BWP#1 based on parameters specific to terminal 10B. Also, since terminal 10C is connected to cell #6, it may detect SSB3 associated with cell #6 and set initial DL BWP#0 based on SSB3. Terminal 10C sets individual DL BWP #1 and #2 based on parameters specific to terminal 10C.

Each of the terminals 10A-10C may perform measurement based on at least one SSB in the initial DL BWP or the individual DL BWP. In the measurement, for example, received power (for example, reference signal received power (RSRP)) may be measured based on SSB. RSRP measured based on SSB may be referred to as Synchronization Signal (SS)-RSRP. The measurement may be performed for at least one of radio resource management (RRM), radio link monitoring (RLM), and mobility.

(Red Cap)
The terminal 10 may be a RedCap terminal intended for lower performance or price range than existing terminals supported by Release 15 or 16 of 3GPP. RedCap terminals are expected to be used, for example, in industrial wireless sensors, surveillance cameras (video serveilance), wearable devices, and the like. For example, the maximum bandwidth supported by a RedCap terminal may be narrower than the maximum bandwidth of existing terminals.

Multiple initial BWPs (multiple initial DL BWPs and/or multiple initial UL BWPs) may be set in such a terminal 10 . For example, in the terminal 10, the initial DL/UL BWP may be set independently of the conventional initial DL/UL BWP. Hereinafter, the conventional initial DL/UL BWP will be referred to as the first initial DL/UL BWP, and the initial DL/UL BWP that is set independently of the first initial DL/UL BWP will be referred to as the second initial DL/UL BWP. call.

In addition, the initial DL/UL BWP information used for setting the first initial DL/UL BWP is referred to as the first initial DL/UL BWP information, and the above information used for setting the second initial DL/UL BWP. The initial DL/UL BWP information shall be referred to as the second initial DL/UL BWP information. The first and second initial DL/UL BWP information may each include at least one of locationAndBandwidth, subcarrierSpacing and cyclicPrefix.

The first initial DL/UL BWP may be set based on CORESET#0 or the frequency position and/or bandwidth indicated by locationAndBandwidth in the first initial DL/UL BWP information. The first initial DL/UL BWP may be set for existing terminals and/or RedCap terminals.

On the other hand, the second initial DL/UL BWP may be the DL/UL BWP of the frequency location and/or bandwidth specified in advance, or the second initial DL/UL BWP information It may be set based on the frequency location and/or bandwidth indicated by locationAndBandwidth. A second initial DL/UL BWP may be set in the RedCap terminal. For the second initial DL/UL BWP, the above subcarrierSpacing and/or cyclicPrefix may or may not be set. The second initial DL/UL DWP may be called a separate initial DL/UL BWP, an additional initial DL/UL BWP, or the like. A RedCap terminal may use a second initial UL BWP during initial access (eg after message 3) and/or after initial access (eg after message 4). The RedCap terminal may use the second initial DL BWP after the initial access (for example, after message 4) or before the initial access (for example, after receiving configuration information for the second initial DL BWP). may be used for

In the second initial DL BWP, CORESET#0 may not be set. Also, SIB1 may not be transmitted in the second initial DL BWP. Also, at least part of the second initial DL BWP may or may not overlap with the first initial UL BWP. Also, at least part of the second initial UL BWP may or may not overlap with the first initial UL BWP. The bandwidth of each of the second initial DL BWP and the second initial UL BWP may be narrower than the maximum bandwidth of the RedCap terminal.

FIG. 5 is a diagram showing an example of first and second initial DL/UL BWPs according to this embodiment. As shown in FIG. 5, one end of the first and second initial UL BWPs are aligned to share a resource region for an uplink control channel (eg, Physical Uplink Control Channel (PUCCH)). may In Time Division Duplex (TDD), the second initial UL BWP and the second initial DL BWP may be identical. Note that FIG. 5 is merely an example, and the bandwidth and arrangement of the first and second initial DL/UL BWPs are not limited to those shown.

FIGS. 6(A) and (B) are diagrams showing examples of the first and second initial DL BWPs according to this embodiment. In FIG. 6A, SSB (eg, CD-SSB) is transmitted in the first initial DL BWP, but no SSB is transmitted in the second initial DL BWP. In this case, the terminal 10, which transmits and receives data in the second initial DL BWP, performs RF retuning for SSB-based measurement, and may need RF retuning again for data transmission and reception after measurement. is assumed. Also, in FIG. 6(A), CORESET#0 may be set to the first initial DL BWP and may not be set to the second initial DL BWP. As shown in FIG. 6A, information on BWP support in which SSB is not transmitted and/or CORESET#0 is not set (hereinafter referred to as "support information") is information on the capability of the terminal 10 (hereinafter referred to as "UE capability”). UE capability may be transmitted from the terminal 10 to the base station 20 .

In FIG. 6(B), SSB (eg, CD-SSB) is transmitted in the first initial DL BWP, and SSB (eg, NC-SSB) is transmitted in the second initial DL BWP. In FIG. 6B, unlike FIG. 6A, there is no need to perform RF retuning for measurement. Therefore, SSB transmission in the second initial DL BWP can contribute to reducing the processing load on terminal 10 .

However, if a second initial DL BWP is set in cell C where the first initial DL BWP is set and SSB can be transmitted in the second initial DL BWP, the terminal 10 Alternatively, there is a risk that it may not be possible to properly recognize which SSB of the second initial DL BWP should be operated based on. As a result, the SSB-based operation may not be properly controlled.

Therefore, the terminal 10 controls SSB-based operations based on whether or not the second initial DL BWP is set in the cell C in which the first initial DL BWP is set. For example, based on whether or not the second initial DL BWP is set in the cell C, the terminal 10 transmits SSB (hereinafter referred to as "first SSB") in the first initial DL BWP. Alternatively, it may be determined based on which of the SSBs transmitted in the second initial DL BWP (hereinafter referred to as "second SSB"). As a result, even if a second initial DL BWP is set in cell C where the first initial DL BWP is set, and SSB can be transmitted in the second initial DL BWP, the operation based on SSB is appropriately controlled. can.

In the following, as examples of operations based on SSB, (1) PDCCH monitoring opportunity determination operation for paging, (2) RA preambles and/or resources used for transmitting RA preambles (hereinafter referred to as “random access opportunities Occasion: RO)" selection operation, (3) operation when MIB is received. This embodiment is applicable not only to the following (1) to (3), but also to other operations based on SSB. Appropriately applicable.

(setting)
The configuration of terminal 10 for operations (1) to (3) based on SSB in this embodiment will be described. Terminal 10 receives parameters or information from base station 20 . In the present embodiment, "configured" may mean receiving the parameters and/or information, or controlling the operation of the terminal 10 based on the received parameters and/or information. may be Although RRC parameters are exemplified below as the parameters and/or information, the parameters and/or information are not limited thereto. The parameters and/or information are parameters of higher layers (for example, layers higher than physical layers such as Medium Access Control (MAC) layers and Non Access Stratum (NAS) layers). may be a parameter of the physical layer.

<Settings related to initial DL BWP>
In the present embodiment, the first initial DL BWP may be set in terminal 10 based on the first initial DL BWP information from base station 20 . Here, the first initial DL BWP information may include at least one of locationAndBandwidth, subcarrierSpacing and cyclicPrefix. Also, the first initial DL BWP information is the RRC parameters in SIB1 (e.g., "BWP" as "genericParameters" in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommonSIB" in "ServingCellConfigCommonSIB") may be Alternatively, the first initial DL BWP information may be specified as RRC parameters in other RRC messages (e.g., "genericParameters" in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommon" in "ServingCellConfigCommon"). BWP”). The first initial DL BWP information may be cell specific.

Also, the second initial DL BWP may be set in the terminal 10 based on the second initial DL BWP information from the base station 20. Here, the second initial DL BWP information may include at least one of locationAndBandwidth, subcarrierSpacing and cyclicPrefix. The second initial DL BWP information is the RRC parameters in SIB1 (for example, "BWP" as "genericParametersRedCap" in "BWP-DownlinkCommon" as "initialDownlinkBWP-RedCap" in "DownlinkConfigCommonSIB" in "ServingCellConfigCommonSIB") may be Alternatively, the second initial DL BWP information is RRC parameters in other RRC messages (for example, as "genericParametersRedCap" in "BWP-DownlinkCommon" as "initialDownlinkBWP-RedCap" in "DownlinkConfigCommon" in "ServingCellConfigCommon" "BWP"). The second initial DL BWP information may be cell specific.

<Settings for initial UL BWP>
The first initial UL BWP may be configured in terminal 10 based on the first initial UL BWP information from base station 20 . Here, the first initial DL BWP information may include at least one of locationAndBandwidth, subcarrierSpacing and cyclicPrefix. Also, the first initial UL BWP information is the RRC parameters in SIB1 (e.g., "BWP" as "genericParameters" in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommonSIB" in "ServingCellConfigCommonSIB") may be Alternatively, the first initial UL BWP information may include RRC parameters in other RRC messages (e.g., "genericParameters" in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommon" in "ServingCellConfigCommon"). BWP”). The second initial UL BWP information may be cell specific.

Also, the second initial UL BWP may be set in the terminal 10 based on the second initial UL BWP information from the base station 20. Here, the second initial UL BWP information may include at least one of locationAndBandwidth, subcarrierSpacing and cyclicPrefix. The second initial UL BWP information is the RRC parameters in SIB1 (for example, "BWP" as "genericParametersRedCap" in "BWP-UplinkCommon" as "initialUplinkBWP-RedCap" in "UplinkConfigCommonSIB" in "ServingCellConfigCommonSIB") may be Alternatively, the second initial UL BWP information can be specified as RRC parameters in other RRC messages (for example, as "genericParametersRedCap" in "BWP-UplinkCommon" as "initialUplinkBWP-RedCap" in "UplinkConfigCommon" in "ServingCellConfigCommon" "BWP"). The second initial UL BWP information may be cell specific.

<Settings for SSB>
The first SSB may be set in the terminal 10 based on information regarding transmission of the first SSB (hereinafter referred to as "first SSB transmission information"). The first SSB transmission information includes information on the first SSB transmission within the SS burst set (hereinafter referred to as "ssb-PositionsInBurst"), information on the SSB period of the first SSB (hereinafter referred to as "ssb-periodicityServingCell"). ), information on the transmission power of the first SSB (hereinafter referred to as “ss-PBCH-BlockPower”), information on the transmission frequency of the first SSB (hereinafter referred to as “ssb-Frequency”), and the first SSB measurement timing (hereinafter referred to as “SSB-MTC”). The first SSB transmission information may be RRC parameters in SIB1 (e.g. parameters in 'ServingCellConfigCommonSIB') or RRC parameters in other RRC messages (e.g. parameters in 'ServingCellConfigCommon'). may The first SSB transmission information may be cell specific.

The second SSB may be set in the terminal 10 based on information regarding transmission of the second SSB (hereinafter referred to as "second SSB transmission information"). The second SSB transmission information includes information on the second SSB transmission within the SS burst set (hereinafter referred to as "additional SSB-PositionsInBurst"), information on the SSB period of the second SSB (hereinafter referred to as "additional SSB-periodicityServingCell"). ), information on the transmission power of the second SSB (hereinafter referred to as “additional-SS-PBCH-BlockPower”), information on the transmission frequency of the second SSB (hereinafter referred to as “additional SSB-Frequency”), and the second SSB measurement timing (hereinafter referred to as “additional SSB-SMTC”). The second SSB transmission information may be RRC parameters in SIB1 (e.g. parameters in 'ServingCellConfigCommonSIB') or RRC parameters in other RRC messages (e.g. parameters in 'ServingCellConfigCommon'). may The second SSB transmission information may be cell specific. Also, if additionalSSB-PositionsInBurst and/or additionalSSB-periodicityServingCell and/or additional-SS-PBCH-BlockPower and/or additionalSSB-SMTC are not set, the first SSB transmission information (ssb-PositionsInBurst , and/or ssb-periodicityServingCell, and/or ss-PBCH-BlockPower, and/or ssb-SMTC) may be applied to the second SSB transmission information.

Note that when the transmission resources for the first SSB and the transmission resources for the second SSB overlap, the terminal 10 may use the first SSB (that is, give priority to the first SSB). good). The transmission resources may be, for example, time domain and/or frequency domain resources.

<PDCCH settings>
Information related to PDCCH configuration in the first initial DL BWP (hereinafter referred to as “pdcch-ConfigCommon”) may be configured in terminal 10 . pdcch-ConfigCommon contains information about paging search space (hereinafter referred to as "pagingSearchSpace"), information about RA search space (hereinafter referred to as "ra-SearchSpace"), information about CORESET (hereinafter referred to as "commonControlResourceSet"), and paging It may include at least one of information about the first PDCCH monitoring opportunity within the paging occasion (PO) (hereinafter referred to as "firstPDCCH-MonitoringOccasionOfPO"). pdcch-ConfigCommon may be the RRC parameter in SIB1 (eg, the parameter in 'BWP-DownlinkCommon' as 'initialDownlinkBWP' in 'DownlinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). Alternatively, pdcch-ConfigCommon may be RRC parameters in other RRC messages (eg, parameters in 'BWP-DownlinkCommon' as 'initialDownlinkBWP' in 'DownlinkConfigCommon' in 'ServingCellConfigCommon'). pdcch-ConfigCommon may be cell specific. pdcch-ConfigCommon may be called first downlink control channel setting information or the like.

Information related to PDCCH configuration in the second initial DL BWP (hereinafter referred to as "pdcch-ConfigCommonRedCap") may be configured in the terminal 10. pdcch-ConfigCommonRedCap may include at least one of pagingSearchSpace, ra-SearchSpace, commonControlResourceSet, and firstPDCCH-MonitoringOccasionOfPO. pdcch-ConfigCommonRedCap may be an RRC parameter in SIB1 (eg, a parameter in 'BWP-DownlinkCommon' as 'initialDownlinkBWP' in 'DownlinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). Alternatively, pdcch-ConfigCommonRedCap may be an RRC parameter in another RRC message (eg, a parameter in 'BWP-DownlinkCommon' as 'initialDownlinkBWP' in 'DownlinkConfigCommon' in 'ServingCellConfigCommon'). pdcch-ConfigCommonRedCap may be cell specific. pdcch-ConfigCommonRedCap may be called second downlink control channel setting information or the like.

<Settings related to random access>
Information related to random access configuration in the first initial DL BWP (hereinafter referred to as “rach-ConfigCommon”) may be configured in the terminal 10 . rach-ConfigCommon is information indicating the number of first SSBs per RO and/or the number of RA preambles per first SSB transmission (hereinafter referred to as "ssb-perRACH-OccasionAndCB-PreamblesPerSSB"); It may include at least one piece of information (hereinafter referred to as “rsrp-ThresholdSSB”) regarding the received power (for example, RSRP) threshold of the first SSB. rach-ConfigCommon may be the RRC parameter in SIB1 (eg, the parameter in 'BWP-UplinkCommon' as 'initialUplinkBWP' in 'UplinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). Alternatively, rach-ConfigCommon may be RRC parameters in other RRC messages (eg, parameters in 'BWP-UplinkCommon' as 'initialUplinkBWP' in 'UplinkConfigCommon' in 'ServingCellConfigCommon'). rach-ConfigCommon may be cell-specific. rach-ConfigCommon may be called the first random access parameter, and so on.

Information related to the random access setting in the second initial DL BWP (hereinafter referred to as "rach-ConfigCommonRedCap") may be set in the terminal 10. rach-ConfigCommonRedCap is information indicating the number of second SSBs per RO and/or the number of RA preambles per second SSB transmission (hereinafter referred to as "ssb-perRACH-OccasionAndCB-PreamblesPerSSB"); It may include at least one piece of information (hereinafter referred to as “rsrp-ThresholdSSB”) regarding the threshold of the received power (for example, RSRP) of the second SSB. rach-ConfigCommonRedCap may be an RRC parameter in SIB1 (eg, a parameter in 'BWP-UplinkCommon' as 'initialUplinkBWP' in 'UplinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). Alternatively, rach-ConfigCommonRedCap may be an RRC parameter in another RRC message (eg, parameter in 'BWP-UplinkCommon' as 'initialUplinkBWP' in 'UplinkConfigCommon' in 'ServingCellConfigCommon'). rach-ConfigCommonRedCap may be cell specific. The rach-ConfigCommonRedCap may be called a second random access parameter or the like.

<Settings related to paging>
Information related to paging configuration in the first initial DL BWP (hereinafter referred to as “PCCH-Config”) may be configured in the terminal 10 . PCCH-Config includes information about the paging cycle (hereinafter referred to as "PagingCycle"), firstPDCCH-MonitoringOccasionOfPO, information indicating the number of paging frames (paging frmae: PF) in the paging cycle and/or time offset (hereinafter referred to as "nAndPagingFrameOffset" ), information on the number of POs per PF (hereinafter referred to as “ns”), and information on the number of PDCCH monitoring opportunities per SSB in a PO (hereinafter referred to as “nrofPDCCH-MonitoringOccasionPerSSB-InPO”). may contain one. PCCH-Config may be RRC parameters in SIB1 (eg, parameters in 'DownlinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). PCCH-Config may be cell specific. PCCH-Config may be called first paging configuration information or the like.

Information related to paging settings in the second initial DL BWP (hereinafter referred to as "PCCH-ConfigRedCap") may be set in the terminal 10. PCCH-ConfigRedCap may include at least one of defaultPagingCycle, firstPDCCH-MonitoringOccasionOfPO, nAndPagingFrameOffset, ns and nrofPDCCH-MonitoringOccasionPerSSB-InPO. PCCH-ConfigRedCap may be an RRC parameter in SIB1 (eg, a parameter in 'DownlinkConfigCommonSIB' in 'ServingCellConfigCommonSIB'). PCCH-Config may be cell specific. PCCH-ConfigRedCap may be referred to as second paging configuration information or the like.

(Operation based on SSB)
(1) Determining PDCCH Monitoring Opportunity for Paging The terminal 10 monitors the PDCCH at the PDCCH monitoring opportunity and receives DCI used for scheduling the PDSCH that transmits the paging message. The DCI may be CRC scrambled with a specific RNTI (eg Paging(P)-RNTI). Terminal 10 may determine the PDCCH monitoring opportunity based on whether the second initial DL BWP is configured in cell C where the first initial DL BWP is configured.

The terminal 10 determines paging frames based on at least one of the DRX cycle, the number of PFs in the DRX cycle, the time offset and the identifier of the terminal 10 . Here, PF is, for example, a radio frame (RF) including PO. For example, the terminal 10 may determine the identification number of the PF (hereinafter referred to as "system frame number (SFN)") based on Equation (1) below.
(Formula 1)
(SFN+PF_offset) mod T
= (T div N) * (UE_ID mod N)
where T is the DRX period, N is the number of PFs in T, PF_offset is a predetermined offset, and UE_ID is determined based on the terminal 10 identifier (eg, 5G-S-TMSI). value. T may be determined based on the PagingCycle. PagingCycle may indicate, for example, 32, 64, 128 or 256 RF. Also, N and/or PF_offset may be determined based on the nAndPagingFrameOffset. nAndPagingFrameOffset may indicate that the PF is placed every xRF in T (eg, x=1, 2, 4, 8 or 16) and/or the time offset.

The terminal 10 may determine POs in the PF based on at least one of the ID of the search space used as the paging search space, firstPDCCH-MonitoringOccasionOfPO, and nrofPDCCH-MonitoringOccasionPerSSB-InPO. PO is, for example, a set of one or more PDCCH monitoring occasions for paging, and S*X consecutive PDCCH monitoring occasions from the time position indicated by firstPDCCH-MonitoringOccasionOfPO (e.g., S*X consecutive excluding UL symbols symbol). Each PDCCH monitoring occasion within the PO may consist of a predetermined number of symbols. firstPDCCH-MonitoringOccasionOfPO may, for example, indicate the time position (eg, symbol position) of the first PDCCH monitoring occasion within the PF.

Here, S is the number of SSBs actually transmitted within the SS burst set, and may be indicated by ssb-PositionsInBurst or additional SSB-PositionsInBurst. X is the number of PDCCH monitoring occasions per SSB in PO, which may be determined based on nrofPDCCH-MonitoringOccasionPerSSB-InPO. nrofPDCCH-MonitoringOccasionPerSSB-InPO indicates, for example, that the number of PDCCH monitoring occasions per SSB in PO is either 2 to 4, and if nrofPDCCH-MonitoringOccasionPerSSB-InPO is not set, the number of PDCCH monitoring occasions is 1 It may be shown that

7 and 8 are diagrams showing examples of SSB, PF and PO according to this embodiment. 7 and 8 show an example of the first and second SSBs, PFs and POs in the first and second initial DL BWPs, respectively, while the first and second SSBs in the first and second initial DL BWPs The settings of SSB, PF and PO of 2 are not limited to those shown in the figure, and can be appropriately changed by setting various parameters.

For example, in the first initial DL BWP, as shown in FIG. 7, T=32 RFs, and nAndPagingFrameOffset may indicate that PFs are placed every 1 RF within T (oneT). The terminal 10 may determine the PF for the terminal 10 (here, RF#0) among the 32 PFs in T based on the UE_ID. In addition, firstPDCCH-MonitoringOccasionOfPO for the first initial DL BWP indicates the fifth symbol from the first in symbols #0 to #139 in the PF (that is, symbol #4 of slot #0). Also, ssb-PositionsInBurst=11111111, and SSB#0-#7 (first SSB) in the SS burst set are actually transmitted, so S=8. Also, since the number of PDCCH opportunities per first SSB is one, X=1. Therefore, the terminal 10 determines 8 consecutive symbols from symbol #4 of slot #0 of RF#0 as PO. The PO is composed of S*X (here, 8) PDCCH monitoring opportunities, and SSB #0 to #7 are the first to eighth PDCCH monitoring opportunities in the PO (that is, symbols of slot #0 #4 to #11 PDCCH monitoring occasions) may be supported. For multi-beam operation, the terminal 10 may assume that the corresponding SSB and PDCCH DM-RSs are quasi-collocated at each PDCCH monitoring occasion in the PO.

On the other hand, in the second initial DL BWP, as shown in FIG. 8, T=32RFs, and nAndPagingFrameOffset indicates that PFs are placed every eight RFs within T (oneEightT) and a time offset of "2". good. The terminal 10 may determine the PF for the terminal 10 (here, RF#2) among the 4 PFs in T based on the UE_ID. In FIG. 8, nAndPagingFrameOffset indicates oneEightT, so the candidate position of the first symbol of the paging monitoring opportunity is 1120 symbols (that is, 1120 symbols of indices #0 to #1119 of RF #0 to #7 (=8*10*14 )). In FIG. 8, firstPDCCH-MonitoringOccasionOfPO for the second initial DL BWP is symbol #284 in symbols #0-#1119 in RF#0-#7 (that is, symbol #4 in slot #0 of PF#2). ). In FIG. 8, a symbol index is attached to each slot in each RF, but symbol indexes #0 to #1119 may be attached to all symbols in RF #0 to #7. Further, since additionalSSB-PositionsInBurst=11110000, SSB #0 to #3 (second SSB) in the SS burst set are actually transmitted, and SSB #4 to #7 are not actually transmitted, so S=4. be. Also, since the number of PDCCH opportunities per SSB is one, X=1. Therefore, the terminal 10 determines four consecutive symbols from symbol #4 in slot #0 of RF#2 as PO. The PO is composed of S*X (here, 4) PDCCH monitoring opportunities, and SSB #0 to #4 are the first to fourth PDCCH monitoring opportunities in the PO (that is, symbols of slot #0). #4 to #7 PDCCH monitoring occasions) may be supported. Terminal 10 may assume that the corresponding SSB and PDCCH DM-RSs are quasi-colocated at each PDCCH monitoring occasion in the PO.

As shown in FIGS. 7 and 8, the terminal 10 has parameters for the first initial DL BWP (eg, first SSB transmission information and pdcch-ConfigCommon) and parameters for the second initial DL BWP (eg, , second SSB transmission information and pdcch-ConfigCommonRedCap) can be set independently. Therefore, the terminal 10 sets the first initial DL BWP or the second initial DL based on whether the second initial DL BWP is set and/or whether a predetermined condition is satisfied. Determine which parameters for BWP to set PDCCH monitoring occasions for paging based on.

FIG. 9 is a flowchart showing an example of operation for determining PDCCH monitoring opportunities for paging according to the present embodiment. In FIG. 9, it is assumed that the terminal 10 has the first initial DL BWP set. In step S101, the terminal 10 determines whether or not the second initial DL BWP is set.

In step S102, when the terminal 10 is configured with the second initial DL BWP, the terminal 10 transmits the second SSB in the second initial DL BWP, configures the paging search space in the second initial DL BWP, Then, it is determined whether or not conditions related to at least one of the capabilities of the terminal 10 are satisfied. Specifically, the terminal 10 may determine whether at least one of the following conditions is satisfied.
(a) transmission of the second SSB in the second initial DL BWP is set;
(b) A paging search space is set up in the second initial DL BWP.
(c) that the terminal 10 has certain capabilities;

For example, the above condition (a) may be that the second SSB transmission information (eg, at least one of additional SSB-Frequency, additional SSB-PositionsInBurst, and additional SSB-PeriodicityServingCell) is set. Moreover, the above condition (b) is that pagingsearchspace (for example, a search space ID of a paging search space) is set in pdcch-ConfigCommonRedCap, or that pagingsearchspace and commonControlResourceSet are set in pdcch-ConfigCommonRedCap. good too. Also, the specific capability in the above condition (c) is the capability of the terminal 10 regarding CORESET#0 and/or SSB in BWP. For example, the condition (c) is that each BWP set in the terminal 10 includes the bandwidth of CORESET #0 and SSB (feature group 6-1), and/or the CORESET #0 and SSB It may be to allow BWPs that do not include bandwidth (feature group 6-1a).

If the second initial DL BWP is set and the condition of step S102 is satisfied (step S102; YES), then in step S103 the terminal 10 sets the additional SSB-PositionsInBurst and/or the second initial Based on pdcch-ConfigCommonRedCap related to PDCCH configuration in DL BWP, PDCCH monitoring opportunities for paging are determined.

Specifically, in step S103, if the search space ID indicated by pagingsearchspace in pdcch-ConfigCommonRedCap is other than 0, terminal 10 performs PDCCH monitoring for paging based on additionalSSB-PositionsInBurst and/or pdcch-ConfigCommonRedCap. Opportunity may be determined. For example, as shown in FIG. 8, the terminal 10 sets PDCCH monitoring opportunities for paging based on additionalSSB-PositionsInBurst and firstPDCCH-MonitoringOccasionOfPO in pdcch-ConfigCommonRedCap from symbol #4 in slot #0 in RF #2 to symbol #4 in slot #0 in RF #2. #7 may be determined. On the other hand, when the search space ID is 0, the terminal 10 may determine the PDCCH monitoring opportunity for SIB1 as the PDCCH monitoring opportunity for paging.

Note that in step S103, the terminal 10 may determine PDCCH monitoring opportunities for paging based on pcch-ConfigRedCap instead of or in addition to pdcch-ConfigCommonRedCap. For example, the terminal 10 is based on at least one of pdcch-ConfigCommonRedCap or firstPDCCH-MonitoringOccasionOfPO in pcch-ConfigRedCap, nrofPDCCH-MonitoringOccasionPerSSB-InPO in pcch-ConfigRedCap, defaultPagingCycle in pcch-ConfigRedCap, and nAndPagingFrameOffset in pcch-ConfigRedCap. , may determine PDCCH monitoring occasions for paging.

If the second initial DL BWP is not set (step S101; NO), or if the second initial DL BWP is set and the condition of step S102 is not satisfied (step S102; NO), in step S104, The terminal 10 determines PDCCH monitoring opportunities for paging based on ssb-PositionsInBurst for the first SSB and/or pdcch-ConfigCommon for PDCCH configuration in the first initial DL BWP.

Specifically, in step S104, when the search space ID indicated by pagingsearchspace in pdcch-ConfigCommon is other than 0, terminal 10 performs PDCCH monitoring for paging based on ssb-PositionsInBurst and/or pdcch-ConfigCommon. Opportunity may be determined. For example, as shown in FIG. 7, the terminal 10 sets PDCCH monitoring opportunities for paging based on ssb-PositionsInBurst and firstPDCCH-MonitoringOccasionOfPO in pdcch-ConfigCommon to symbols #4 to symbols #4 in slot #0 in RF #0. #11 may be determined. On the other hand, if the search space ID is 0, the terminal 10 may determine the PDCCH monitoring opportunity for SIB1 as the PDCCH monitoring opportunity for paging.

Note that in step S104, the terminal 10 may determine PDCCH monitoring opportunities for paging based on pcch-Config instead of or in addition to pdcch-ConfigCommon. For example, the terminal 10, based on at least one of pdcch-ConfigCommonRedCap or firstPDCCH-MonitoringOccasionOfPO in pcch-Config, nrofPDCCH-MonitoringOccasionPerSSB-InPO in pcch-Config, defaultPagingCycle in pcch-Config and nAndPagingFrameOffset in pcch-Config , may determine PDCCH monitoring occasions for paging.

According to the above operation, even if the second SSB can be transmitted in the second initial DL BWP, PDCCH monitoring opportunities for paging can be determined appropriately. Therefore, the terminal 10 can receive paging messages based on the DCI detected at PDCCH monitoring occasions.

(2) RA Preamble and /RO Decision Operation In the random access procedure, the terminal 10 transmits the RA preamble. The terminal 10 determines the RA preamble and/or the RO used to transmit the RA preamble based on whether the second initial DL BWP is configured in the cell C in which the first initial DL BWP is configured. You may

The RA preamble is a predetermined sequence and is also called PRACH preamble or preamble, preamble sequence, message 1, PRACH, and the like. An RO is, for example, time domain and/or frequency domain resources for transmission of an RA preamble, and may consist of one or more symbols and M (M≧1) resource blocks. RO is also called PRACH opportunity, random access opportunity, transmission opportunity, opportunity, and so on. The RA preamble may be transmitted using a random access channel (PRACH). The RACH is a UL channel used for transmitting the RA preamble, and is also called a Physical Random Access Channel (PRACH) or the like.

Random access procedures include contention-based random access (CBRA) and contention-free random access (CFRA). Two types are supported for CBRA and CFRA, respectively. The first type is called Type 1, Type-1 random access procedure, 4-step RACH, or 4-step random access, or the like. The second type is called Type-2, Type-2 random access procedure, 2-step RACH, or 2-step random access, or the like.

In type 1 CBRA, terminal 10 randomly selects an RA preamble and transmits the selected RA preamble to base station 20 . The terminal 10 receives a Random Access Response (RAR) (also called message 2) via PDSCH in response to the RA preamble and transmits message 3 via PUSCH in response to the RAR. Terminal 10 receives message 4 (collision resolution message) via PDSCH in response to message 3 .

In type 1 CFRA, the terminal 10 transmits the RA preamble assigned by the base station 20 to the base station 20 . The terminal 10 receives RAR from the base station 20 via PDSCH according to the RA preamble. Since the RA preamble is indicated by DCI, CFRA is also called PDCCH-ordered RA.

In type 2 CBRA, the terminal 10 transmits the RA preamble and message 3 in type 1 CBRA as message A, and receives message B (that is, RAR). In type 2 CBRA, the RA preamble in message A is also randomly selected. In type 2 CFRA, the RA preamble and message 3 indicated by the DCI from base station 20 are sent as message A and message B is received.

In the types 1 and 2 CBRA and CFRA described above, the terminal 10 may select an RO and/or an RA preamble based on the RSRP of the SSB and transmit the RA preamble using the selected RO. Based on the RA preamble received from the terminal 10 and/or the RO used for transmitting the RA preamble, the base station 20 recognizes which SSB the terminal 10 has received, that is, in which beamforming direction the terminal 10 is located. can. That is, the base station 20 may estimate the pseudo collocation (QCL) relationship for the terminal 10 based on the RA preamble from the terminal 10 and/or the SSB associated with the RO used to receive the RA preamble. The control unit 203 may control transmission of DL signals and/or reception of UL signals using the same spatial parameters (beams) as those of the SSB.

In addition, the terminal 10 monitors the PDCCH in the RA search space, detects DCI that is CRC scrambled with a specific RNTI (eg, RA-RNTI), and uses the PDSCH scheduled by the DCI to perform type 1 and 2 CBRA and CFRA, message 4 and/or message B may be received.

FIG. 10 is a diagram showing an example of the relationship between SSB and RO and RA preambles according to this embodiment. For example, FIG. 10 shows the relationship between SSB #0 to #7 (first SSB) actually transmitted in the first initial DL BWP and the RO and RA preambles in the first initial UL BWP. Note that FIG. 10 is merely an example, and the relationship between SSB, RO, and RA preambles is not limited to that illustrated.

As shown in FIG. 10, one or more slots (hereinafter referred to as "RACH slots") used for transmitting RA preambles are provided in a predetermined period (hereinafter referred to as "RACH resource periodicity"). . For example, in FIG. 10, the RACH resource period is 10 slots, and the 2nd, 5th, and 8th slots in RF are RACH slots, but this is not limitative.

For example, as shown in FIG. 10, each RACH slot may be provided with one or more ROs. One RO is composed of M (M≧1) resource blocks. Also, K (K=2 in FIG. 10) ROs can be arranged in the frequency domain. Also, in the time domain, one or more ROs can be allocated per RACH slot. For example, in FIG. 10, a total of 2 ROs, 2 ROs in the frequency domain and 1 RO in the time domain, are allocated per RACH slot. Thus, each RACH slot may contain one or more ROs in the time domain and/or frequency domain.

An SSB is associated with one or more ROs. Also, one SSB is associated with one or more RA preambles. The association between SSB and RO and/or RA preambles may be indicated by ssb-perRACHOccasionAndCB-PreamblesPerSSB above. Specifically, the ssb-perRACHOccasionAndCB-PreamblesPerSSB may indicate the number of SSBs associated with one RO and/or the number of RA preambles associated with one SSB.

For example, in FIG. 10, ssb-PositionsInBurst=11111111 and SSB #0 to #7 in the SS burst set are actually transmitted in the first initial DL BWP. ssb-perRACHOccasionAndCB-PreamblesPerSSB indicates that one RO corresponds to one SSB ("one") and that one SSB corresponds to 8RA preambles ("n8"). Note that the SSB number X associated with one RO is not limited to 1, and may be a number larger than 1 (eg, 2, 4, 8, or 16) or a number smaller than 1 (eg, 1/8 , 1/4 or 1/2). If X≧1, one RO is associated with X SSBs. For X<1, one SSB is associated with the reciprocal of X ROs. Also, the number Y of RA preambles associated with one SSB is, for example, 4, 8, 12, etc., but is not limited thereto, and may be 1 or more. Also, the RO and RA preamble indexes and the like associated with each SSB shown in FIG. 10 are merely examples, and are not limited to those shown.

In FIG. 10, terminal 10 measures RSRP using SSB #0 to #7 in the SS burst set in the first initial DL BWP. At least one of SSB #0 to #7 is selected for terminal 10 based on the RSRP measurement result of SSB #0 to #7 and the threshold indicated by rsrp-ThresholdSSB. Specifically, the terminal 10 may select at least one of the SSBs #0 to #7 whose RSRP exceeds the threshold.

For example, in FIG. 10, when terminal 10 selects two SSB #0 and #1 based on RSRP and the threshold, random Select one RA preamble for . Also, the terminal 10 selects one RO from RO #0 and #1 associated with SSB #0 and #1 respectively. Terminal 10 uses the selected RO to transmit the selected RA preamble. Note that, in the case of CFRA, the terminal 10 may transmit the RA preamble indicated by DCI using the selected RO.

In addition, although type 1 CBRA or CFRA is assumed in FIG. 10, it is applicable to type 2 CBRA or CFRA. Information related to association of RO and/or RA preambles for message A (hereinafter referred to as “msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB”) may be configured in terminal 10 . Also, information on the threshold of RSRP of SSB (hereinafter referred to as “msgA-RSRP-ThresholdSSB”) may be configured in the terminal 10 for type 2 CBRA or CFRA. Terminal 10, similar to ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB described in FIG. An RO may be selected for RA preamble transmission.

FIG. 11 is a diagram showing another example of the relationship between SSB and RO and RA preambles according to this embodiment. For example, FIG. 11 shows the relationship between SSB #0 to #3 (second SSB) actually transmitted in the second initial DL BWP and the RO and RA preambles in the second initial UL BWP. Note that FIG. 11 is merely an example, and the relationship between SSB, RO, and RA preambles is not limited to that illustrated. Also, FIG. 11 will be described with a focus on differences from FIG. 10 .

For example, in FIG. 11, additional SSB-PositionsInBurst=11110000, and SSB #0 to #3 in the SS burst set are actually transmitted in the second initial DL BWP. ssb-perRACHOccasionAndCB-PreamblesPerSSB indicates that 1/2 SSBs correspond to one RO (that is, one SSB corresponds to two ROs) ("oneHalf"), and one SSB has 16 RAs. Indicates that the preamble supports ("n16").

In FIG. 11, terminal 10 measures RSRP using SSB #0 to #3 in the SS burst set in the second initial DL BWP. At least one of SSB #0 to #7 is selected for terminal 10 based on the RSRP measurement result of SSB #0 to #3 and the threshold indicated by rsrp-ThresholdSSB. Specifically, the terminal 10 may select at least one of the SSBs #0 to #3 whose RSRP exceeds the threshold.

For example, in FIG. 11, when terminal 10 selects SSB#1 based on RSRP and the threshold, terminal 10 randomly selects one RA preamble from RA preambles #15 to #31 associated with SSB#1. . Also, the terminal 10 selects one RO from RO #2 and #3 associated with SSB #1. Terminal 10 uses the selected RO to transmit the selected RA preamble. Note that, in the case of CFRA, the terminal 10 may transmit the RA preamble indicated by DCI using the selected RO.

In addition, although type 1 CBRA or CFRA is assumed in FIG. 11, it is applicable to type 2 CBRA or CFRA. Information related to association of RO and/or RA preambles for message A (hereinafter referred to as “msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB”) may be configured in terminal 10 . Also, information on the threshold of RSRP of SSB (hereinafter referred to as “msgA-RSRP-ThresholdSSB”) may be configured in the terminal 10 for type 2 CBRA or CFRA. Terminal 10, similar to ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB described in FIG. An RO may be selected for RA preamble transmission.

As shown in FIGS. 10 and 11, the terminal 10 has parameters for the first initial DL BWP (for example, first SSB transmission information and rach-ConfigCommon) and parameters for the second initial DL BWP ( For example, the second SSB transmission information (rach-ConfigCommonRedCap) can be set independently. Therefore, the terminal 10 sets the first initial DL BWP or the second initial DL based on whether the second initial DL BWP is set and/or whether a predetermined condition is satisfied. Decide on which parameters for BWP to select RO and/or RA preambles.

FIG. 12 is a flowchart showing an example of the RO and/or RA preamble selection operation according to this embodiment. In FIG. 12, it is assumed that the terminal 10 has the first initial DL BWP set. In step S201, the terminal 10 determines whether or not the second initial DL BWP is set.

In step S202, when the terminal 10 is configured with the second initial DL BWP, the terminal 10 transmits the second SSB in the second initial DL BWP, configures the RA search space in the second initial DL BWP, It is determined whether or not conditions related to at least one of the setting of the second random access parameter and the capability of the terminal 10 are satisfied. Specifically, the terminal 10 may determine whether at least one of the following conditions is satisfied.
(A) Transmission of the second SSB in the second initial DL BWP is set.
(B) RA search space is set in the second initial DL BWP.
(C) A second random access parameter is set.
(D) Terminal 10 has a specific capability.

For example, condition (B) is that ra-searchspace (for example, search space ID of RA search space) is set in pdcch-ConfigCommonRedCap, or that ra-searchspace and the commonControlResourceSet are set in pdcch-ConfigCommonRedCap. It may be Also, the above condition (C) may be that ssb-perRACH-OccasionAndCB-preamblesPerSSB and/or RSRP-ThresholdSSB are set in rach-ConfigCommonRedCap. Conditions (A) and (D) above are the same as conditions (a) and (c) above.

If the second initial DL BWP is set and the condition of step S202 is satisfied (step S202; YES), then in step S203 the terminal 10 sets additionalSSB-PositionsInBurst and/or RACH-ConfigCommonRedCap for the second SSB. based on which RA preamble and/or RO is selected.

Specifically, in step S203, the terminal 10 generates an RA preamble based on at least one of additionalSSB-PositionsInBurst, ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB in RACH-ConfigCommonRedCap, and RSRP of the second SSB. and/or RO may be selected. For example, as shown in FIG. 11, terminal 10 determines RO and/or RA preambles corresponding to SSB #0 to #3 based on additional SSB-PositionsInBurst and ssb-perRACHOccasionAndCB-PreamblesPerSSB in RACH-ConfigCommonRedCap. may In addition, the terminal 10, based on the RSRP of SSB #0 ~ #3 and RSRP-ThresholdSSB in RACH-ConfigCommonRedCap, at least one of SSB #0 ~ #3 (for example, in FIG. 11, the threshold indicated by RSRP-ThresholdSSB SSB#1) with an RSRP greater than . Also, in FIG. 11, the terminal 10 has one of RO #2 and #3 corresponding to the selected SSB and/or one of RA preambles #15 to #31 corresponding to the selected SSB #1. may be selected.

If the second initial DL BWP is not set (step S201; NO), or if the second initial DL BWP is set and the condition of step S202 is not satisfied (step S202; NO), in step S204, Terminal 10 selects the RA preamble and/or RO based on ssb-PositionsInBurst and/or RACH-ConfigCommon for the first SSB.

Specifically, in step S204, the terminal 10 generates an RA preamble based on at least one of ssb-PositionsInBurst, ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB in RACH-ConfigCommon, and RSRP of the first SSB. and/or RO may be determined. For example, as shown in FIG. 10, terminal 10 determines RO and/or RA preambles corresponding to SSB #0 to #7 based on ssb-PositionsInBurst and ssb-perRACHOccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. may In addition, the terminal 10, based on the RSRP of SSB #0 ~ #7 and RSRP-ThresholdSSB in RACH-ConfigCommon, at least one of SSB #0 ~ #7 (for example, in FIG. 10, the threshold indicated by RSRP-ThresholdSSB SSBs #0 and #1) with RSRP greater than . In addition, in FIG. 10, the terminal 10 uses one of RO #0 and #1 corresponding to the selected SSB #0 and #1 and/or the RA preamble corresponding to the selected SSB #0 and #1. One of #0 to #15 may be selected.

Note that the operation shown in FIG. 12 is also applicable to type 2 CBRA and CFRA. For type 2, the above RACH-ConfigCommon and RACH-ConfigCommonRedCap may be replaced with msgA-ConfigCommon and msgA-ConfigCommonRedCap, respectively. Also, ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB may be replaced with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB and msgA-RSRP-ThresholdSSB, respectively.

According to the above operation, RO and/or RA preambles can be appropriately selected even if the second SSB can be transmitted in the second initial DL BWP. Therefore, operations related to random access can be appropriately controlled. Note that the selection of RA preambles in the above means selecting (or determining) one RA preamble transmitted by terminal 10 using RACH from among one or more groups (or sets) of RA preambles. It may be to Also, the selection of the RA preamble may be translated into selection or determination of the index of the RA preamble, and the terminal 10 may transmit the RA preamble of the selected index via the RACH.

(3) Operation when MIB is received Terminal 10 receives MIB via PBCH. The terminal 10 may control the operation when receiving the MIB based on whether or not the second initial DL BWP is set in the cell C in which the first initial DL BWP is set. Specifically, when the second initial DL BWP is configured, the terminal 10 receives a specific It may ignore the parameter or assume that the particular parameter is not sent.

FIG. 13 is a diagram showing an example of the MIB according to this embodiment. As shown in Figure 13, the MIB may include at least one of the following parameters.
・ Information about SFN (hereinafter referred to as “systemFrameNumber”)
- Information on subcarrier spacing (hereinafter referred to as "subCarrierSpacingCommon")
- Information on the frequency offset (k _SSB ) between the SSB and the resource block grid (hereinafter referred to as "ssb-SubcarrierOffset")
・ Information about the position of DM-RS (hereinafter referred to as "dmrs-TypeA-Position")
- Information on common CORESET (CORESET#0) and/or common search space (search space #0) (hereinafter referred to as "pdcch-ConfigSIB1")
・Information on whether or not (camp-on to) the cell is prohibited (hereinafter referred to as "cellBarred")
- Information on the selection and / or reselection of the same frequency cell (hereinafter referred to as "intraFreqReselection")

FIG. 14 is a flow chart showing an example of the operation when MIB is received according to this embodiment. In FIG. 14, it is assumed that the terminal 10 has the first initial DL BWP set. In step S301, the terminal 10 determines whether or not the second initial DL BWP is set.

In step S302, when the second initial DL BWP is configured in the terminal 10, the terminal 10 transmits the second SSB in the second initial DL BWP, configures the paging search space in the second initial DL BWP, It is determined whether or not conditions related to at least one of setting of RA search spaces in the second initial DL BWP and capabilities of the terminal 10 are satisfied. Specifically, the terminal 10 may determine whether at least one of the following conditions is satisfied.
(i) transmission of the second SSB in the second initial DL BWP is set;
(ii) A paging search space is set up in the second initial DL BWP.
(iii) RA search space is set in the second initial DL BW.
(iv) the terminal 10 has certain capabilities;
For example, conditions (i), (ii) and (iv) above are the same as conditions (a), (b) and (c) above. Condition (iii) above is the same as condition (B) above.

If the second initial DL BWP is set and the condition of step S302 is satisfied (step S302; YES), then in step S303 the terminal 10 receives the may ignore certain parameters of or assume that certain parameters are not transmitted.

Here, the specific parameter in the MIB is, for example, at least one of cellBarred, intraFreqReselection, and ssb-SubcarrierOffset, but is not limited to this. The specific parameter may be at least one parameter within the MIB. The terminal 10 may control reception of DL signals in the second initial DL BWP and/or transmission of UL signals in the second initial UL BWP based on parameters other than the specific parameters in the MIB. good.

If the second initial DL BWP is not set (step S301; NO), or if the second initial DL BWP is set and the condition of step S302 is not satisfied (step S302; NO), in step S304, Terminal 10 receives DL signals in the first initial DL BWP and/or receives UL signals in the first initial UL BWP based on each parameter in the MIB received via the PBCH in the first SSB Signal transmission may be controlled.

Note that the operation of the terminal 10 when the second initial DL BWP is set is not limited to the above. For example, when the second initial DL BWP is set, the terminal 10 can set a specific meaning regardless of the value of a specific parameter in the MIB received via the PBCH in the second SSB. can be interpreted as The specific parameter is, for example, cellBarred, and the terminal 10 may interpret cellBarred to indicate that the cell is not barred even if it indicates that the cell is barred.

According to the above operation, when the second SSB can be transmitted not only in the first initial DL BWP but also in the second initial DL BWP, appropriate operation can be performed based on the MIB.

(parameter)
An example of the above parameters or information used to configure the terminal 10 for the above SSB-based operations (1) to (3) in this embodiment will be described with reference to FIGS. Note that each parameter or information shown in FIGS. 15 to 18 is merely an example, and the names, sizes, hierarchical structures, etc. are not limited to those shown in the drawings. Further, parameters or information not shown in FIGS. 15 to 18 may of course be used for the operations (1) to (3) in this embodiment.

FIG. 15 is a diagram showing an example of BWP-DownlinkCommon according to this embodiment. BWP-DownlinkCommon is information used for setting DL BWP common parameters, and may be included in ServingCellConfigCommon or ServingCellConfigCommonSIB. ServingCellConfigCommonSIB is a cell-specific parameter and may be included in SIB1. ServingCellConfigCommon is a cell-specific configuration parameter and may be included in other RRC messages.

As shown in FIG. 15, BWP-DownlinkCommon may include at least one of the following.
- genericParameters, which is the first initial DL BWP information
- pdcch-ConfigCommon, which is information about PDCCH configuration in the first initial DL BWP
- pdsch-ConfigCommon, which is information about the configuration of the PDSCH in the first initial DLBWP
- genericParametersRedCap, which is the second initial DL BWP information
- pdcch-ConfigCommonRedCap, which is information about PDCCH configuration in the second initial DL BWP
- pdsch-ConfigCommonRedCap, which is information about the setting of PDSCH in the second initial DL BWP, and additionalSSB-PositionsInBurst, additionalSSB-periodicityServingCell, additional-SS-PBCH-BlockPower, additionalSSB-Frequency, and additionalSSB as second SSB transmission information - At least one of SMTC Note that groupPresence in additionalSSB-PositionsInBurst indicates whether or not each SSB group is actually transmitted when a maximum of 64 SSBs that can be transmitted within the SS burst set are divided into 8 SSB groups. is indicated by the value of each corresponding bit. Also, inOneGroup is information indicating whether or not each SSB in the SSB group is actually transmitted by the value of each corresponding bit. In operation bands below 6 GHz, only information indicated by inOneGroup may be used. Also, in the operation band above 6 GHz, information indicated by inOneGroup and groupPresence may be used.

FIG. 16 is a diagram showing an example of BWP-UplinkCommon according to this embodiment. BWP-UplinkCommon is information used to configure UL BWP common parameters, and may be included in ServingCellConfigCommon or ServingCellConfigCommonSIB. ServingCellConfigCommonSIB is a cell-specific parameter and may be included in SIB1. ServingCellConfigCommon is a cell-specific configuration parameter and may be included in other RRC messages.

As shown in FIG. 16, BWP-UplinkCommon may include at least one of the following.
- genericParameters, which is the first initial UL BWP information
- rach-ConfigCommon, which is information about the configuration of random access in the first initial UL BWP
- pusch-ConfigCommon, which is information about the configuration of PUSCH in the first initial ULBWP
- pucch-ConfigCommon, which is information about the configuration of PUCCH in the first initial ULBWP
msgA-ConfigCommon, which is information about the transmission of message A in the first initial UL BWP
- genericParametersRedCap, which is the second initial UL BWP information
- rach-ConfigCommonRedCap, which is information about the configuration of random access in the second initial UL BWP
- pusch-ConfigCommonRedCap, which is information about the configuration of PUSCH in the second initial ULBWP
- pucch-ConfigCommonRedCap, which is information about the configuration of PUCCH in the second initial ULBWP
msgA-ConfigCommonRedCap, which is information about the transmission of message A in the second initial UL BWP

FIG. 17 is a diagram showing an example of RACH-ConfigCommon according to this embodiment. RACH-ConfigCommon may function as information on the configuration of random access in the first initial UL BWP (that is, rach-ConfigCommon), or information on the configuration of random access in the second initial UL BWP ( That is, it may function as rach-ConfigCommonRedCap).

As shown in FIG. 17, push-ConfigCommon may include at least one of the following parameters.
ssb-perRACH-OccasionAndCB-PreamblesPerSSB, which is information indicating the number of first or second SSBs per RO and/or the number of RA preambles per first or second SSB
- rsrp-ThresholdSSB, which is information about the RSRP threshold of the first or second SSB

FIG. 18 is a diagram showing an example of RACH-ConfigCommonTwoStepRA according to this embodiment. RACH-ConfigCommonTwoStepRA may serve as information regarding the transmission of message A in the first initial UL BWP (ie msgA-ConfigCommon) or information regarding the transmission of message A in the second initial UL BWP (ie msgA -ConfigCommonRedCap).

As shown in FIG. 18, RACH-ConfigCommonTwoStepRA may include at least one of the following parameters.
msgA-SSB-perRACH-OccasionAndCB-PreamblesPerSSB, which is information indicating the number of first or second SSBs per RO and/or the number of RA preambles per first or second SSB
- msgA-rsrp-ThresholdSSB, which is information about the RSRP threshold of the first or second SSB

(Configuration of wireless communication system)
Next, the configuration of each device of the radio communication system 1 as described above will be described. Note that the following configuration is for showing the configuration required in the description of the present embodiment, and does not exclude that each device has functional blocks other than those illustrated.

<Hardware configuration>
FIG. 19 is a diagram showing an example of the hardware configuration of each device in the wireless communication system according to this embodiment. Each device in the wireless communication system 1 (for example, the terminal 10, the base station 20, the CN 30, etc.) includes a processor 11, a storage device 12, a communication device 13 that performs wired or wireless communication, an input device that receives various input operations, and various It includes an input/output device 14 for outputting information.

The processor 11 is, for example, a CPU (Central Processing Unit) and controls each device within the wireless communication system 1 . The processor 11 may read and execute the program from the storage device 12 to execute various processes described in this embodiment. Each device within the wireless communication system 1 may be configured with one or more processors 11 . Each device may also be called a computer.

The storage device 12 is composed of storage such as memory, HDD (Hard Disk Drive) and/or SSD (Solid State Drive). The storage device 12 may store various types of information necessary for execution of processing by the processor 11 (for example, programs executed by the processor 11, etc.).

The communication device 13 is a device that communicates via a wired and/or wireless network, and may include, for example, network cards, communication modules, chips, antennas, and the like. Further, the communication device 13 may include an amplifier, an RF (Radio Frequency) device that performs processing related to radio signals, and a BB (BaseBand) device that performs baseband signal processing.

The RF device, for example, performs D/A conversion, modulation, frequency conversion, power amplification, etc. on the digital baseband signal received from the BB device to generate a radio signal to be transmitted from the antenna. Further, the RF device generates a digital baseband signal by performing frequency conversion, demodulation, A/D conversion, etc. on the radio signal received from the antenna, and transmits the digital baseband signal to the BB device.

The BB device performs processing to convert data into digital baseband signals. Specifically, the BB device may map data to subcarriers, perform IFFT to generate OFDM symbols, insert CPs into the generated OFDM symbols, and generate digital baseband signals. Note that the BB device may apply a transform precoder (DFT spreading) before mapping data to subcarriers.

Also, the BB device performs processing to convert the digital baseband signal into data. Specifically, the BB device may remove the CP from the digital baseband signal input from the RF device, perform FFT on the CP-removed signal, and extract the signal in the frequency domain. Note that the BB device may apply IDFT to the signal in the frequency domain.

The input/output device 14 includes input devices such as keyboards, touch panels, mice and/or microphones, and output devices such as displays and/or speakers.

The hardware configuration described above is just an example. Each device in the wireless communication system 1 may omit part of the hardware shown in FIG. 19, or may include hardware not shown in FIG. Also, the hardware shown in FIG. 19 may be configured by one or a plurality of chips.

<Functional block configuration>
≪Device≫
FIG. 20 is a diagram showing an example of the functional configuration of a terminal according to this embodiment. As shown in FIG. 20 , terminal 10 includes receiver 101 , transmitter 102 , and controller 103 . The functional configuration shown in FIG. 20 is merely an example, and any names of functional divisions and functional units may be used as long as the operations according to the present embodiment can be executed. Also, the receiving unit 101 and the transmitting unit 102 may be collectively referred to as a communication unit.

All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 can be realized using the communication device 13. All or part of the functions realized by the receiving unit 101 and the transmitting unit 102 and the control unit 103 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium. The storage medium storing the program may be a non-transitory computer readable medium. The non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.

The receiving unit 101 receives a signal (eg, DL signal and/or sidelink signal). Also, the receiving unit 101 may receive information and/or data transmitted via the signal. Here, "receiving" may include, for example, performing processing related to reception such as at least one of receiving, demapping, demodulating, decoding, monitoring, and measuring radio signals. The DL signal may include, for example, at least one of PDSCH, PDCCH, downlink reference signal, synchronization signal, PBCH, and the like.

Receiving section 101 monitors PDCCH candidates in the search space to detect DCI. The receiver 101 may receive DL data via PDSCH scheduled using DCI. The DL data may include downlink user data and/or higher layer control information (eg, at least one parameter of the MAC layer, RRC layer and Non Access Stratum (NAS) layer). The receiver 101 may receive system information via PBCH and/or PDSCH.

The transmission unit 102 transmits signals (eg, UL signals and/or sidelink signals). Also, the transmitting unit 102 may transmit information and/or data transmitted via the signal. Here, "transmitting" may include performing processing related to transmission, such as at least one of encoding, modulation, mapping, and transmission of radio signals. The UL signal may include, for example, at least one of PUSCH, PRACH, PUCCH, uplink reference signals, and the like.

The transmitting section 102 may transmit UL data via PUSCH scheduled using the DCI received by the receiving section 101 . The UL data may transmit uplink user data and/or higher layer control information (eg, at least one parameter of the MAC layer, RRC layer and NAS layer).

The control unit 103 performs various controls in the terminal 10. Specifically, the control unit 103 controls the operation of the terminal 10 based on information (for example, RRC layer parameters) related to various configurations received by the receiving unit 101 from the base station 20 or another terminal 10. may be controlled. The operation of the terminal 10 based on the information may be synonymous with "the setting information is configured in the terminal 10".

The control unit 103 may control signal reception in the receiving unit 101 . Further, the control section 103 may control transmission of signals in the transmission section 102 . The control unit 103 may determine whether to apply the transform precoder to the signal transmitted by the transmission unit 102 .

In this embodiment, the terminal 10 monitors the downlink control channel using a search space (eg, paging search space) in a predetermined period (eg, PDCCH monitoring opportunity), and schedules the downlink shared channel that transmits the paging message. Whether the second initial downlink bandwidth part (DL BWP) is set in the receiving unit 101 that receives the downlink control information to be used and the cell C in which the first initial downlink bandwidth part (DL BWP) is set and a control unit 103 that determines the predetermined period based on whether or not.

When the second initial DL BWP is set, the control unit 103 controls transmission of the second synchronization signal block (SSB) in the second initial DL BWP, transmission of the search space in the second initial DL BWP, The predetermined period of time may be determined based on configuration and whether conditions relating to at least one of the capabilities of the terminal are met.

When the second initial DL BWP is set and the conditions are satisfied, the control unit 103 stores information on the transmission of the second SSB (for example, additional SSB-PositionInBurst) and The predetermined period may be determined based on at least one piece of information (for example, pdcch-ConfigCommonRedCap) regarding configuration of the downlink control channel.

When a search space other than a specific ID (eg, “0”) is set as the search space, control section 103 receives information (eg, additional SSB-PositionInBurst) regarding transmission of the second SSB and the second The predetermined period may be determined based on at least one piece of information (for example, pdcch-ConfigCommonRedCap) regarding the configuration of the downlink control channel in the initial DL BWP.

When the second initial DL BWP is set and the condition is not satisfied, the control unit 103 stores information on the transmission of the first SSB (for example, SSB-PositionInBurst) and The predetermined period may be determined based on at least one piece of information (for example, pdcch-ConfigCommon) regarding configuration of the downlink control channel.

When a search space other than a specific ID (for example, “0”) is set as the search space, control section 103 receives information on transmission of the first SSB (for example, SSB-PositionInBurst) and the first The predetermined period may be determined based on at least one piece of information (for example, pdcch-ConfigCommon) regarding the configuration of the downlink control channel in the initial DL BWP.

When the second initial DL BWP is not set, the control unit 103 provides information regarding the transmission of the first SSB (for example, SSB-PositionInBurst) and information regarding the setting of the downlink control channel in the first initial DL BWP. (eg, pdcch-ConfigCommon).

In addition, in this embodiment, the terminal 10 has a transmission section 102 that transmits a random access preamble, and a second initial downlink bandwidth part (DL BWP) in the cell in which the first initial downlink bandwidth part (DL BWP) is set. DL BWP) is configured, the control unit 103 that selects the random access preamble and/or the resource used for transmitting the random access preamble.

When the second initial DL BWP is set, the control unit 103 controls the transmission of the second synchronization signal block (SSB) in the second initial DL BWP, the random access in the second initial DL BWP. Search space setting, second random access parameter setting for random access in the second initial DL BWP, and whether or not conditions regarding at least one of the capabilities of the terminal are satisfied, the random access A preamble and/or the resource may be selected.

When the second initial DL BWP is set and the conditions are satisfied, the control unit 103 sets the information on the transmission of the second SSB (for example, additional SSB-PositionInBurst), the second random access parameter ( For example, the random access preamble and/or the resource may be selected based on at least one of RACH-ConfigCommonRedCap) and received power of the second SSB.

The second random access parameters include information about association of the second SSB with the resource and/or the random access preamble (eg, ssb-perRACH-OccasionAndCB-preamblesPerSSB), and reception of the second SSB. It may include at least one of information on power thresholds (eg, RSRP-ThresholdSSB).

When the second initial DL BWP is set and the condition is not satisfied, the control unit 103 transmits information (for example, ssb -PositionsInBurst), a first random access parameter for random access in the first initial DL BWP (for example, Rach-ConfigCommon), and the received power of the first SSB, the random access A preamble and/or the resource may be selected.

When the second initial DL BWP is not set, the control unit 103 sets information on transmission of the first synchronization signal block (SSB) in the first initial DL BWP (for example, ssb-PositionsInBurst), the first Select the random access preamble and/or the resource based on at least one of the first random access parameter (eg, Rach-ConfigCommon) for random access in the initial DL BWP and the received power of the first SSB You may

The first random access parameters include information on association between the first SSB and the resource and/or the random access preamble (eg, ssb-perRACH-OccasionAndCB-preamblesPerSSB), and reception of the first SSB. It may include at least one of information on power thresholds (eg, RSRP-ThresholdSSB).

In this embodiment, the terminal 10 includes a receiving section 101 that receives a master information block (MIB), and a second initial downlink bandwidth part (DL BWP) in a cell in which the first initial downlink bandwidth part (DL BWP) is set. and a control unit 103 that controls an operation based on a specific parameter in the MIB based on whether (DL BWP) is set.

When the second initial DL BWP is set, the control unit 103 transmits the second synchronization signal block (SSB) at the second initial DL BWP and searches for paging at the second initial DL BWP. Space setting, search space setting for random access in the second initial DL BWP, and ignoring the specific parameter based on whether at least one of the terminal capabilities conditions are met Alternatively, it may be assumed that said specific parameter is not transmitted.

When the second initial DL BWP is set and the condition is satisfied, the control unit 103 converts the specific parameter in the MIB received via the broadcast channel included in the second SSB to It may be ignored or assumed that said particular parameter is not transmitted.

The specific parameters include information on whether a cell is barred (eg, cellBarred), information on intra-frequency cell selection and/or reselection (eg, intraFreqReselection), and the second SSB and resource block. At least one of information about the frequency domain offset to/from the grid (eg, ssb-SubcarrierOffset) may be included.

When the second initial DL BWP is set, the control unit 103 may interpret it to have a specific meaning regardless of the value of the specific parameter. The specific parameter may include information on whether or not a cell is barred (eg, cellBarred), and the control unit 103 may interpret that the cell is not barred regardless of the value indicated by the information.

≪Base station≫
FIG. 21 is a diagram showing an example of the functional block configuration of the base station according to this embodiment. As shown in FIG. 21, the base station 20 includes a receiver 201, a transmitter 202, and a controller 203. FIG. The functional configuration shown in FIG. 21 is merely an example, and any names of functional divisions and functional units may be used as long as the operations according to the present embodiment can be executed. Also, the receiving unit 201 and the transmitting unit 202 may be collectively referred to as a communication unit.

All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 can be realized using the communication device 13. All or part of the functions realized by the receiving unit 201 and the transmitting unit 202 and the control unit 203 can be realized by the processor 11 executing a program stored in the storage device 12 . Also, the program can be stored in a storage medium. The storage medium storing the program may be a computer-readable non-temporary storage medium. The non-temporary storage medium is not particularly limited, but may be a storage medium such as a USB memory or CD-ROM, for example.

The receiving unit 201 receives signals (eg, UL signals and/or sidelink signals). Also, the receiving unit 201 may receive information and/or data (for example, the UL data described above) transmitted via the signal.

The transmission unit 202 transmits signals (eg, DL signals and/or sidelink signals). Also, the transmitting unit 202 may transmit information and/or data (for example, the DL data described above) transmitted via the signal. Part of the information transmitted from the transmission unit 202 may be transmitted by a transmission unit within the core network device.

The control unit 203 performs various controls for communication with the terminal 10. Specifically, the control unit 203 may determine information regarding various settings to be notified to the terminal 10 . Transmitting the information to the terminal 10 may be synonymous with "setting the information in the terminal".

The control unit 203 may control signal reception in the receiving unit 201 . The control unit 203 may also control signal transmission in the transmission unit 202 .

In this embodiment, the base station 20 monitors the downlink control channel using a search space (eg, paging search space) in a predetermined period (eg, PDCCH monitoring opportunity), and schedules a downlink shared channel for transmitting paging messages. and the second initial downlink bandwidth part (DL BWP) is set in the cell C in which the first initial downlink bandwidth part (DL BWP) is set. and a control unit 203 that determines the predetermined period based on whether or not.

Further, in the present embodiment, the base station 20, based on the receiving unit 201 that receives a random access preamble, the random access preamble and/or the resources used for receiving the random access preamble, the transmission of the DL signal and / Alternatively, it may include a control unit 203 that controls reception of the UL signal.

The control unit 203 may estimate the pseudo collocation (QCL) relationship for the terminal 10 based on the random access preamble and/or the synchronization signal block (SSB) associated with the random access preamble. The control unit 203 may control transmission of DL signals and/or reception of UL signals using the same beam as the SSB.

In this embodiment, the base station 20 includes a transmission section 202 that transmits a master information block (MIB), and a second initial downlink bandwidth part (DL BWP) within a cell in which the first initial downlink bandwidth part (DL BWP) is set. and a control unit 203 that controls transmission of specific parameters in the MIB based on whether or not the part (DL BWP) is set.

When the second initial DL BWP is set, the control unit 203 transmits the second synchronization signal block (SSB) at the second initial DL BWP and searches for paging at the second initial DL BWP. Space setting, search space setting for random access in the second initial DL BWP, and inclusion in the second SSB based on whether at least one condition on the capability of the terminal is met. transmission of the specific parameter in the MIB over the broadcast channel provided by the MIB may be discontinued.

When the second initial DL BWP is set and the condition is satisfied, the control unit 203 stops transmission of the specific parameter in the MIB via the broadcast channel included in the second SSB. You may

(supplement)
Various signals, information and parameters in the above embodiments may be signaled in any layer. That is, the various signals, information, and parameters are replaced with signals, information, and parameters of any layer such as higher layers (eg, NAS layer, RRC layer, MAC layer, etc.), lower layers (eg, physical layer), etc. good too. Further, the notification of the predetermined information is not limited to being performed explicitly, but may be performed implicitly (for example, by not notifying the information or using other information).

Also, the names of various signals, information, parameters, IEs, channels, time units, and frequency units in the above embodiments are merely examples, and may be replaced with other names. For example, a slot may be named any unit of time having a predetermined number of symbols. Also, RB may be any name as long as it is a frequency unit having a predetermined number of subcarriers. Also, the "first .

For example, in the present embodiment, as an example of a physical channel that transmits DL data, a physical channel that transmits UL data, a physical channel that transmits DCI, a physical channel that transmits broadcast information, and a physical channel that transmits RA preambles, PDSCH, PUSCH, PDCCH, PBCH, and PRACH are exemplified, respectively, but the names are not limited to these as long as the physical channels have similar functions. These physical channels may also be translated into transport channels to which physical channels are mapped. In addition, PDSCH, PUSCH, PDCCH, PBCH and PRACH, etc. are respectively transport channels mapped to physical channels (for example, downlink shared channel (DL-SCH), uplink shared channel (Uplink Shared Channel: UL -SCH), broadcast channel (at least one of Broadcast Channel: BCH and Random Access Channel (Random Access Channel: RCH)), etc. In addition, these transport channels are mapped to transport channels. DL data and UL data are downlink and uplink data, respectively, and the data includes user data and higher layer control information (e.g., RRC parameters, medium access control (Medium Access Control: MAC) parameters, etc.).

In addition, the use of the terminal 10 in the above embodiment (for example, for RedCap, IoT, etc.) is not limited to those illustrated, as long as it has similar functions, any use (for example, eMBB, URLLC, Device-to- Device (D2D), Vehicle-to-Everything (V2X), etc.). Also, the format of various information is not limited to the above embodiment, and may be appropriately changed to bit representation (0 or 1), true/false value (Boolean: true or false), integer value, character, or the like. Also, singularity and plurality in the above embodiments may be interchanged.

The embodiments described above are for facilitating understanding of the present disclosure, and are not for limiting interpretation of the present disclosure. Flowcharts, sequences, elements included in the embodiments, their arrangement, indexes, conditions, and the like described in the embodiments are not limited to those illustrated and can be changed as appropriate. Moreover, it is possible to partially replace or combine at least part of the configurations described in the above embodiments.

Claims (12)

1. information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in said first initial downlink bandwidth portion, second initial downlink bandwidth a receiving unit for receiving system information including information used to configure a portion and cell-specific information regarding configuration of a physical downlink control channel in said second initial downlink bandwidth portion;
   If the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion includes an identifier of a search space for paging, it is transmitted in the second initial downlink bandwidth portion a control unit that determines a monitoring opportunity of a physical downlink control channel for paging based on information about a synchronization signal and a physical broadcast channel (SS/PBCH) block to be transmitted and an identifier of the search space.
2. The terminal according to claim 1, wherein information about the SS/PBCH blocks transmitted in the second initial downlink bandwidth portion is included in the system information.
3. The information used to configure the second initial downlink bandwidth portion and the cell-specific information regarding the configuration of the physical downlink control channel in said second initial downlink bandwidth portion are intended for RedCap terminals. The terminal according to claim 1 or 2.
4. information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in said first initial downlink bandwidth portion, second initial downlink bandwidth a transmitting unit for transmitting system information including information used to configure a portion and cell-specific information regarding configuration of a physical downlink control channel in said second initial downlink bandwidth portion;
   When the identifier of the search space for paging is included in the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion, transmission in the second initial downlink bandwidth portion a control unit that sets monitoring opportunities of the physical downlink control channel for paging based on information on the synchronization signal and physical broadcast channel (SS/PBCH) block to be received and the identifier of the search space. .
5. 5. The base station according to claim 4, wherein information about the SS/PBCH blocks transmitted in the second initial downlink bandwidth portion is included in the system information.
6. The information used to configure the second initial downlink bandwidth portion and the cell-specific information regarding the configuration of the physical downlink control channel in said second initial downlink bandwidth portion are intended for RedCap terminals. 6. A base station according to claim 4 or claim 5.
7. information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in said first initial downlink bandwidth portion, second initial downlink bandwidth receiving system information including information used to configure a portion and cell-specific information regarding configuration of physical downlink control channels in said second initial downlink bandwidth portion;
   If the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion includes an identifier of a search space for paging, it is transmitted in the second initial downlink bandwidth portion determining a monitoring opportunity of a physical downlink control channel for paging based on information about a synchronization signal and a physical broadcast channel (SS/PBCH) block to be transmitted and an identifier of the search space; Communication method.
8. The wireless communication method for a terminal according to claim 7, wherein information about the SS/PBCH blocks transmitted in the second initial downlink bandwidth portion is included in the system information.
9. The information used to configure the second initial downlink bandwidth portion and the cell-specific information regarding the configuration of the physical downlink control channel in said second initial downlink bandwidth portion are intended for RedCap terminals. The terminal wireless communication method according to claim 7 or 8.
10. information used to configure a first initial downlink bandwidth portion, cell-specific information regarding configuration of a physical downlink control channel in said first initial downlink bandwidth portion, second initial downlink bandwidth transmitting system information including information used to configure a portion and cell-specific information regarding configuration of a physical downlink control channel in the second initial downlink bandwidth portion;
    When the identifier of the search space for paging is included in the cell-specific information regarding the configuration of the physical downlink control channel in the second initial downlink bandwidth portion, transmission in the second initial downlink bandwidth portion and setting a physical downlink control channel monitoring opportunity for paging based on information about the synchronization signal and physical broadcast channel (SS/PBCH) block to be received and the identifier of the search space. wireless communication method.
11. 11. The wireless communication method of claim 10, wherein information regarding the SS/PBCH blocks transmitted in the second initial downlink bandwidth portion is included in the system information.
12. The information used to configure the second initial downlink bandwidth portion and the cell-specific information regarding the configuration of the physical downlink control channel in said second initial downlink bandwidth portion are intended for RedCap terminals. The wireless communication method according to claim 10 or 11.

Images