Terminal, base station, and wireless communication method

Abstract

The present invention provides a terminal, base station, and wireless communication method that enable a terminal to appropriately control SSB-based operations even when a synchronous signal block (SSB) is transmitted in a second initial DL BWP in addition to the existing initial DL BWP within a cell. [Solution] The wireless communication method in the wireless communication system receives a wireless resource control message, receives a first SS / PBCH block based on a first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the wireless resource control message, and if the wireless resource control message includes information regarding the period of a second SS / PBCH block, receives a second SS / PBCH block based on information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block.

Description

Cross-reference to related applications

[0001] This application is based on Japanese Patent Application No. 2021-162298 filed on September 30, 2021, claims the benefit of its priority, and all the contents of that patent application are incorporated herein by reference.

Technical Field

[0002] This disclosure relates to a terminal, a base station, and a wireless communication method.

Background Art

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

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] 3GPP (for example, Release 17 which defines NR) is considering supporting terminals designed for lower performance and price ranges than terminals introduced in Release 15 or 16 (hereinafter referred to as "existing terminals") (hereinafter also referred to as "Reduced Capability (RedCap) terminals"). Specifically, it is being considered to allow the setting of a new Initial Downlink Bandwidth Part (Initial DL BWP) for RedCap terminals within the cell where the Initial Downlink Bandwidth Part (Initial DL BWP) is set. It is also being considered to transmit a Synchronization Signal Block (SSB) in the Initial DL BWP for RedCap terminals.

[0006] However, if an initial DL BWP (hereinafter referred to as "second initial DL BWP") is set within a cell in addition to the existing initial DL BWP (hereinafter referred to as "first initial DL BWP"), and SSB can also be transmitted in the second initial DL BWP, there is a risk that the terminal may not be able to properly control operations based on SSB.

[0007] A terminal relating to one aspect of this disclosure is Received a wireless resource control message, Based on the first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the aforementioned wireless resource control message, the first SS / PBCH block is received. Determine whether the aforementioned wireless resource control message contains information regarding the period of the second SS / PBCH block. If the radio resource control message includes information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the second SS / PBCH block. If the radio resource control message does not include information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the period of the first SS / PBCH block.

[0008] A base station relating to one aspect of this disclosure is Send a wireless resource control message, Based on the first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the aforementioned wireless resource control message, the first SS / PBCH block is transmitted. If the radio resource control message includes information regarding the period of the second SS / PBCH block, the second SS / PBCH block is transmitted based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the second SS / PBCH block. If the radio resource control message does not include information regarding the period of the second SS / PBCH block, the second SS / PBCH block is transmitted based on the information regarding the period of the first SS / PBCH block.

[0009] A wireless communication method performed by a terminal according to one aspect of the present disclosure includes receiving a wireless resource control message, receiving a first SS / PBCH block based on a first synchronization signal and information regarding the period of a physical broadcast channel (SS / PBCH) block included in the wireless resource control message, determining whether the wireless resource control message includes information regarding the period of a second SS / PBCH block, receiving the second SS / PBCH block based on information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block if the wireless resource control message includes information regarding the period of the second SS / PBCH block, and receiving the second SS / PBCH block based on information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block if the wireless resource control message does not include information regarding the period of the second SS / PBCH block.

[0010] A wireless communication method performed by a base station according to one aspect of the present disclosure transmits a resource control message, transmits a first SS / PBCH block based on a first synchronization signal and information regarding the period of a physical broadcast channel (SS / PBCH) block included in the wireless resource control message, transmits the second SS / PBCH block based on information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block if the wireless resource control message includes information regarding the period of a second SS / PBCH block, and transmits the second SS / PBCH block based on information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block if the wireless resource control message does not include information regarding the period of the second SS / PBCH block.

[0011] According to one aspect of this disclosure, SSB-based operation can be appropriately controlled. [Brief explanation of the drawing]

[0012] [Figure 1] Figure 1 shows an example of the overview of the wireless communication system according to this embodiment. [Figure 2] Figure 2 shows an example of an SSB according to this embodiment. [Figure 3] Figure 3 shows an example of an SS burst set according to this embodiment. [Figure 4] Figure 4 shows an example of BWP in this embodiment. [Figure 5] Figure 5 shows examples of the first and second initial DL / UP BWP according to this embodiment. [Figure 6] Figures 6(A) and (B) show examples of the first and second initial DL BWP according to this embodiment. [Figure 7] Figure 7 shows an example of the SSB, PF, and PO according to this embodiment. [Figure 8]FIG. 8 is a diagram showing an example of SSB, PF, and PO according to this embodiment. [Figure 9] FIG. 9 is a flowchart showing an example of the operation of setting a PDCCH monitoring opportunity for paging according to this embodiment. [Figure 10] FIG. 10 is a diagram showing an example of the relationship between SSB, RO, and RA preamble according to this embodiment. [Figure 11] FIG. 11 is a diagram showing another example of the relationship between SSB, RO, and RA preamble according to this embodiment. [Figure 12] FIG. 12 is a flowchart showing an example of the operation of selecting RO and / or RA preamble according to this embodiment. [Figure 13] FIG. 13 is a diagram showing an example of MIB according to this embodiment. [Figure 14] FIG. 14 is a flowchart showing an example of the operation when receiving MIB according to this embodiment. [Figure 15] FIG. 15 is a diagram showing an example of BWP-DownlinkCommon according to this embodiment. [Figure 16] FIG. 16 is a diagram showing an example of BWP-UplinkCommon according to this embodiment. [Figure 17] FIG. 17 is a diagram showing an example of RACH-ConfigCommon according to this embodiment. [Figure 18] FIG. 18 is a diagram showing an example of RACH-ConfigCommonTwoStepRA according to this embodiment. [Figure 19] FIG. 19 is a diagram showing an example of the hardware configuration of each device in a wireless communication system according to this embodiment. [Figure 20] FIG. 20 is a diagram showing an example of the functional block configuration of a terminal according to this embodiment. [Figure 21] FIG. 21 is a diagram showing an example of the functional block configuration of a base station according to this embodiment.

Embodiments for Carrying Out the Invention

[0013] This embodiment will now be described with reference to the attached drawings. To facilitate understanding of the explanation, the same reference numerals are used for identical components in each drawing whenever possible, and redundant explanations are omitted.

[0014] Figure 1 shows an example of the overview of a wireless communication system according to this embodiment. As shown in Figure 1, the wireless communication system 1 may include a terminal 10, a base station 20, and a core network 30. Note that the number of terminals 10 and base stations 20 shown in Figure 1 is merely illustrative and is not limited to the number shown.

[0015] Wireless communication system 1 is a system that communicates in accordance with Radio Access Technology (RAT) defined by 3GPP. While fifth-generation RATs such as NR are envisioned as the radio access technology to which wireless communication system 1 conforms, it is not limited to this. One or more RATs may be used, such as fourth-generation RATs like LTE and LTE-Advanced, sixth-generation and later RATs, or non-3GPP RATs like Wi-Fi®. Furthermore, wireless communication system 1 may also communicate in accordance with radio access technology defined by standards-setting organizations other than 3GPP (e.g., the Institute of Electrical and Electronics Engineers (IEEE), the Internet Engineering Task Force (IETF)).

[0016] Terminal 10 is a device equivalent to a terminal (e.g., UE (User Equipment)) as defined in the 3GPP specification. Terminal 10 is a specified terminal or device such as a smartphone, personal computer, car, in-vehicle terminal, in-vehicle device, stationary device, telematics control unit (TCU), sensor, or other IoT device. Terminal 10 may also be called User Equipment (UE), Mobile Station (MS), User Terminal, Radio apparatus, subscriber terminal, access terminal, etc. Furthermore, Terminal 10 may be a so-called Reduced Capability (RedCap) terminal, such as an industrial wireless sensor, video service, or wearable device. Terminal 10 may be mobile or fixed. Terminal 10 is configured to communicate using one or more RATs such as NR, LTE, LTE-Advanced, or Wi-Fi (registered trademark). Furthermore, terminal 10 is not limited to terminals specified in the 3GPP specification, but may also be a terminal conforming to a standard specified by another standards-setting organization. In addition, terminal 10 does not have to be a terminal conforming to a standard.

[0017] Base station 20 is a device equivalent to a base station (e.g., gNodeB (gNB) or eNB) as defined in the 3GPP specification. Base station 20 forms one or more cells C and communicates with terminal 10 using these cells. Cell C may be interchangeably referred to as a serving cell, carrier, component carrier (CC), etc. 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 contain one or more cells C. Integrating multiple cells C within a cell group is called carrier aggregation. These multiple cells C may include a primary cell (PCell) or primary / secondary cell group (SCG) cell (PSCell) and one or more secondary cells (Secondary Cells (SCG)). Communicating with terminal 10 using two cell groups is also called dual connectivity. Furthermore, terminal 10 is not limited to base stations specified in the 3GPP specification, but may also be a terminal compliant with standards specified by other standards-setting organizations. Also, terminal 10 does not have to be a base station compliant with standards.

[0018] The base station 20 may also be called a gNodeB (gNB), en-gNB, Next Generation-Radio Access Network (NG-RAN) node, low-power node, Central Unit (CU), Distributed Unit (DU), gNB-DU, Remote Radio Head (RRH), Integrated Access and Backhaul / Backhauling (IAB) node, access point, etc. The base station 20 is not limited to a single node, but may consist of multiple nodes (for example, a combination of lower-level nodes such as DUs and higher-level nodes such as CUs).

[0019] 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 these. Devices on the core network 30 (hereinafter also referred to as "core network devices") may perform mobility management such as paging and location registration of terminals 10. The core network devices may be connected to base stations 20 or terminals 10 via a predetermined interface (for example, S1 or NG interface).

[0020] The core network device may include, for example, at least one of the following: an Access and Mobility Management Function (AMF) that manages C-plane information (e.g., information related to access and mobility management, etc.) and a User Plane Function (UPF) that controls the transmission of U-plane information (e.g., user data).

[0021] In the wireless communication system 1, terminal 10 receives downlink (DL) signals from base station 20 and / or transmits uplink (UL) signals to base station 20. Terminal 10 is configured with one or more cells C, and at least one of the configured cells is activated. The maximum bandwidth of each cell is, for example, 20 MHz or 400 MHz.

[0022] Furthermore, terminal 10 performs a cell search based on synchronization signals from base station 20 (e.g., Primary Synchronization Signal (PSS) and / or Secondary Synchronization Signal (SSS)). Cell search is a procedure in which terminal 10 obtains the synchronization of time and frequency in a cell and detects the identifier of that cell (e.g., physical layer cell ID).

[0023] Terminal 10 determines the search space set and / or control resource set (CORESET) based on the parameters included in the Radio Resource Control (RRC) message (hereinafter referred to as "RRC parameters"). The CORESET may consist of frequency domain resources (e.g., a predetermined number of resource blocks) and time domain resources (e.g., a predetermined number of symbols). The RRC parameters may also be called RRC information elements (IE), etc.

[0024] Terminal 10 monitors Downlink Control Information (DCI) transmitted via a downlink control channel (e.g., Physical Downlink Control Channel: PDCCH) within the search space set associated with CORESET. RRC messages may include, for example, RRC setup messages, RRC reconfiguration messages, RRC resume messages, RRC reestablishment messages, system information, etc.

[0025] DCI monitoring is the process by which terminal 10 blindly decodes PDCCH candidates in the search space set using the expected DCI format. The number of bits in the DCI format (also called size, bit width, etc.) is predetermined or derived according to the number of bits in the fields included in the DCI format. Terminal 10 detects the DCI for itself based on the number of bits in the DCI format and a specific Radio Network Temporary Identifier (RNTI) used for scrambling the Cyclic Redundancy Check (CRC) bits (also called CRC parity bits) of the DCI format (hereinafter referred to as "CRC scrambling"). DCI monitoring is also called PDCCH monitoring or monitoring. The given period for performing DCI or PDCCH monitoring is also called a PDCCH monitoring occasion.

[0026] A search space set is a collection of one or more search spaces, and may include a search space set used in common by one or more terminals 10 (hereinafter referred to as the "Common search space (CSS) set") and a terminal-specific search space set (UE-specific search space (USS) set). A search space set may also include a search space set for paging (hereinafter referred to as the "paging search space"), a search space set for random access (RA) (hereinafter referred to as the "RA search space"), and a search space set for system information (hereinafter referred to as the "system information search space"). Terminal 10 may receive information regarding the settings of each search space set.

[0027] Terminal 10 monitors the PDCCH using a search space set (or search space) during a PDCCH monitoring opportunity and receives (or detects) DCIs that are CRC scrambled by a specific RNTI. Terminal 10 controls the reception of downlink shared channels (e.g., Physical Downlink Shared Channel: PDSCH) and / or the transmission of uplink shared channels (e.g., Physical Uplink Shared Channel: PUSCH) that are scheduled using the DCI.

[0028] The system information broadcast in cell C may include a Master Information Block (MIB) and / or one or more System Information Blocks (SIBs). The MIB is broadcast via a broadcast channel (e.g., 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 other than SIB1 (x = any string such as 2, 3, ...) are also called Other System Information (OSI). SIB1 and SIBx other than SIB1 are broadcast via the PDSCH. SIB1 is cell-specific, and SIBx other than SIB1 may be cell-specific or area-specific, including one or more cells.

[0029] (SSB) An SSB is a block that includes at least one of the following: 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, etc.

[0030] Figure 2 shows an example of an SSB according to this embodiment. Note that Figure 2 is merely an example, and the SSB is not limited to what is shown. As shown in Figure 2, the SSB may consist of a predetermined number of symbols as time domain resources (for example, 4 consecutive symbols) and a predetermined number of subcarriers as frequency domain resources (for example, 240 consecutive subcarriers).

[0031] For example, in Figure 2, PSS is transmitted with the first symbol in SSB and mapped to subcarrier 127. The remaining subcarriers of this first symbol may be empty. SSS is transmitted with the third symbol in SSB and mapped to the same 127 subcarriers as PSS. A predetermined number (8 or 9) of empty subcarriers may be provided at both ends of SSS. PBCH is transmitted with the second and fourth symbols in SSB and mapped to subcarrier 240. PBCH is also mapped to the 48 subcarriers at both ends of SSS. Different neurology (e.g., subcarrier spacing = 15, 30, 120, or 240 kHz) can be applied to SSB. Note that some subcarriers shown as PBCH in Figure 3 may be mapped to DMRS, which is not shown.

[0032] An SS burst set, which is a set of one or more SSBs, is transmitted at a predetermined period. An SS burst set may also be called an SS burst, etc. 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 (for example, 5, 10, 20, 40, 80, or 160 ms).

[0033] Each SSB within an SS burst set is identified by an index (hereinafter referred to as the "SSB index"). In multi-beam operation, SSBs with different indices within an SS burst set may correspond to different beams and be transmitted by sequentially switching beam directions through beam sweeping. In single-beam operation, one or more SSBs with a specific index within an SS burst set may be transmitted in all directions.

[0034] Terminal 10 receives information regarding SSB transmission within the SS burst set (hereinafter referred to as "ssb-PositionsInBurst"). For example, ssb-PositionsInBurst is a bitmap containing bits corresponding to each SSB in the SS burst set, where the value of each bit may indicate whether the corresponding SSB is actually transmitted or not. 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 contain any information regarding SSB transmission within the SS burst set. ssb-PositionsInBurst may also be cell-specific. Furthermore, ssb-PositionsInBurst may be included in other RRC messages, for example, SIB1.

[0035] Figure 3 shows an example of an SS burst set according to this embodiment. Note that Figure 3 is merely an example, and the number of SSBs in the SS burst set, SSB period, subcarrier spacing, beam direction, and placement of the SS burst set are not limited to those shown. For example, in Figure 3, SSBs #0 to #7 in the SS burst set are transmitted from the base station 20 at different times using beams #0 to #7, each with different directivity.

[0036] An SS burst set containing one or more SSBs is placed in the first or second half of a radio frame (e.g., 5 ms) and repeated with an SSB period. For example, in Figure 3, an SS burst set containing SSBs #0 to #7 is placed in the first half of a radio frame and repeated with an SSB period of 20 ms. As shown in Figure 3, the position of SSBs #0 to #7 within the half frame may vary depending on the subcarrier interval.

[0037] Furthermore, for example, in Figure 3, ssb-PositionsInBurst is an 8-bit bitmap corresponding to SSB#0 to #7, and is set to "11111111". Therefore, terminal 10 recognizes that all SSB#0 to #7 in the SS burst set will be transmitted. In this way, terminal 10 determines which SSBs will actually be transmitted in the SS burst set based on ssb-PositionsInBurst.

[0038] Note that Figure 3 shows an example of multi-beam operation, but it is also applicable to single-beam operation. In single-beam operation, a specific SSB (for example, only SSB#0) may be transmitted in all directions, and in ssb-PositionsInBurst, the bit corresponding to that specific SSB may be set to "1" and the other bits may be set to "0".

[0039] (BWP) One or more Bandwidth Parts (BWPs) may be configured for a single cell C. A BWP may include a DL BWP (hereinafter referred to as "DL BWP") and / or a UL BWP (hereinafter referred to as "UL BWP"). A BWP may also include a cell-specific BWP (hereinafter referred to as "initial BWP") and a terminal 10-specific BWP (hereinafter referred to as "dedicated BWP"). An initial BWP is used for initial access and / or may be common to one or more terminals 10. An initial BWP may include an initial DL BWP (hereinafter referred to as "initial DL BWP") and an initial UL BWP (hereinafter referred to as "initial UL BWP"). A dedicated BWP is also called a "UE-specific BWP".

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

[0041] The initial DL BWP is a DL BWP with a BWP identifier (hereinafter referred to as "bwp-id") = 0 (i.e., DL BWP#0), and the initial UL BWP may be a UL BWP with bwp-id = 0 (i.e., 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 (i.e., 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 (i.e., UL BWP#bwp-id). If one or more individual DL BWPs and / or one or more individual UL BWPs are configured on terminal 10, one individual DL BWP and / or one individual UL BWP may be activated.

[0042] One or more DL BWPs transmit SSBs. For example, the initial DL BWP transmits a Cell Defining (CD)-SSB, while individual DL BWPs may transmit CD-SSBs and / or Non-Cell Defining (NCD)-SSBs. A CD-SSB is an SSB associated with a specific cell and may be associated with SIB1. An NCD-SSB is an SSB not associated with a specific cell and may not be associated with SIB1.

[0043] Figure 4 shows an example of DL BWP in this embodiment. Although Figure 4 shows DL BWP, UL BWP may also be set. For example, in Figure 4, multiple SSBX (here, X=1~4) are transmitted at predetermined frequency positions within cell C (or the bandwidth of cell C). Note that X is a number assigned for convenience to distinguish SSBs in different frequency domains and does not represent an SSB index that identifies each SSB within the SS burst set.

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

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

[0046] Each of terminals 10A to 10C may perform measurement based on the initial DL BWP or at least one SSB within the individual DL BWP. In the measurement, for example, the received power (e.g., Reference Signal Received Power: RSRP) may be measured based on the SSB. RSRP measured based on the SSB may be called Synchronization Signal (SS)-RSRP. The measurement may be performed for at least one of radio resource management (RRM), radio link monitoring (RLM), and mobility.

[0047] (RedCap) Terminal 10 may be a RedCap terminal designed for lower performance and price range than existing terminals supported by 3GPP release 15 or 16. RedCap terminals are intended for use in applications such as industrial wireless sensors, video service cameras, and wearable devices. For example, the maximum bandwidth supported by a RedCap terminal may be narrower than the maximum bandwidth of existing terminals.

[0048] Multiple initial BWPs (multiple initial DL BWPs and / or multiple initial UL BWPs) may be configured in such a terminal 10. For example, an initial DL / UL BWP may be configured in terminal 10 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 configured independently of the first initial DL / UL BWP will be referred to as the second initial DL / UL BWP.

[0049] Furthermore, the initial DL / UL BWP information used to set the first initial DL / UL BWP will be referred to as the first initial DL / UL BWP information, and the initial DL / UL BWP information used to set the second initial DL / UL BWP will 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 the above-mentioned locationAndBandwidth, subcarrierSpacing, and cyclicPrefix.

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

[0051] On the other hand, the second initial DL / UL BWP may be a DL / UL BWP with a frequency position and / or bandwidth predetermined in the specifications, or it may be set based on the frequency position and / or bandwidth indicated by locationAndBandwidth in the second initial DL / UL BWP information. The second initial DL / UL BWP may be set on 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, or an additional initial DL / UL BWP, etc. The RedCap terminal may use the second initial UL BWP during the initial access (e.g., from message 3 onwards) and / or after the initial access (e.g., 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 the configuration information for the second initial DL BWP).

[0052] In the second initial DL BWP, CORESET#0 does not need to be set. Also, SIB1 does not need to be transmitted in the second initial DL BWP. Furthermore, at least a portion of the second initial DL BWP may or may not overlap with the first initial UL BWP. Also, at least a portion 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.

[0053] Figure 5 shows an example of the first and second initial DL / UL BWPs according to this embodiment. As shown in Figure 5, one end of the first and second initial UL BWPs may be aligned in order to share the resource area for the uplink control channel (e.g., Physical Uplink Control Channel: PUCCH). In Time Division Duplex (TDD), the second initial UL BWP and the second initial DL BWP may be the same. Note that Figure 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.

[0054] Figures 6(A) and (B) show examples of the first and second initial DL BWPs according to this embodiment. In Figure 6(A), SSB (e.g., CD-SSB) is transmitted in the first initial DL BWP, but not in the second initial DL BWP. In this case, it is assumed that the terminal 10 that transmits and receives data in the second initial DL BWP will perform RF retuning for SSB-based measurement, and will need to perform RF retuning again for data transmission and reception after measurement. Also, in Figure 6(A), CORESET#0 is set in the first initial DL BWP, but not necessarily in the second initial DL BWP. As shown in Figure 6(A), information regarding support for BWPs in which SSB is not transmitted and / or CORESET#0 is not set (hereinafter referred to as "support information") may be defined as information regarding the capabilities of the terminal 10 (hereinafter referred to as "UE capability"). UE capability may be transmitted from the terminal 10 to the base station 20.

[0055] In Figure 6(B), SSB (e.g., CD-SSB) is transmitted in the first initial DL BWP, and SSB (e.g., NC-SSB) is also transmitted in the second initial DL BWP. In Figure 6(B), RF retuning for measurement is not required, as in Figure 6(A). Therefore, SSB transmission in the second initial DL BWP can contribute to reducing the processing load on terminal 10.

[0056] However, if a second initial DL BWP is set within cell C where the first initial DL BWP is set, and SSB can be transmitted using the second initial DL BWP, terminal 10 may not be able to properly recognize which SSB, the first or the second initial DL BWP, it should operate on. As a result, it may not be able to properly control SSB-based operation.

[0057] Therefore, terminal 10 controls SSB-based operation based on whether or not a second initial DL BWP is set in cell C where the first initial DL BWP is set. For example, terminal 10 may decide whether or not to operate based on the SSB transmitted with the first initial DL BWP (hereinafter referred to as "first SSB") or the SSB transmitted with the second initial DL BWP (hereinafter referred to as "second SSB"), based on whether or not a second initial DL BWP is set in cell C. This ensures that SSB-based operation can be appropriately controlled even when a second initial DL BWP is set in cell C where the first initial DL BWP is set, and an SSB can be transmitted with the second initial DL BWP.

[0058] The following describes, as examples of SSB-based operations: (1) the operation of determining PDCCH monitoring opportunities for paging, (2) the operation of selecting resources used for transmitting RA preambles and / or RA preambles (hereinafter referred to as "Random Access Occasions (RO)"), and (3) the operation when MIB is received. Note that this embodiment can be appropriately applied not only to (1) to (3) below, but also to other SSB-based operations.

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

[0060] <Initial DL BWP settings> In this embodiment, the first initial DL BWP may be set in the terminal 10 based on the first initial DL BWP information from the base station 20. Here, the first initial DL BWP information may include at least one of the locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. Alternatively, the first initial DL BWP information may be an RRC parameter in SIB1 (for example, "BWP" as "genericParameters" in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Or, the first initial DL BWP information may be an RRC parameter in another RRC message (for example, "BWP" as "genericParameters" in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommon" within "ServingCellConfigCommon"). The first initial DL BWP information may be cell-specific.

[0061] Furthermore, a 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 the locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. The second initial DL BWP information may also be an RRC parameter in SIB1 (for example, "BWP" as "genericParametersRedCap" in "BWP-DownlinkCommon" as "initialDownlinkBWP-RedCap" in "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Alternatively, the second initial DL BWP information may also be an RRC parameter in another RRC message (for example, "BWP" as "genericParametersRedCap" in "DownlinkCommon" as "initialDownlinkBWP-RedCap" in "DownlinkConfigCommon" within "ServingCellConfigCommon"). The second initial DL BWP information may also be cell-specific.

[0062] <Initial UL BWP settings> The first initial UL BWP may be set on the terminal 10 based on the first initial UL BWP information from the base station 20. Here, the first initial DL BWP information may include at least one of the locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. Alternatively, the first initial UL BWP information may be an RRC parameter in SIB1 (for example, "BWP" as "genericParameters" in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Or, the first initial UL BWP information may be an RRC parameter in another RRC message (for example, "BWP" as "genericParameters" in "UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommon" within "ServingCellConfigCommon"). The second initial UL BWP information may be cell-specific.

[0063] Alternatively, the second initial UL BWP may be set in the terminal 10 based on the above second initial UL BWP information from the base station 20. Here, the second initial UL BWP information may include at least one of the above locationAndBandwidth, subcarrierSpacing, and cyclicPrefix. The second initial UL BWP information may be an RRC parameter in SIB1 (e.g., "BWP" as "genericParametersRedCap" in "BWP-UplinkCommon" as "initialUplinkBWP-RedCap" in "UplinkConfigCommonSIB" in "ServingCellConfigCommonSIB"). Or, the second initial UL BWP information may be an RRC parameter in other RRC messages (e.g., "BWP" as "genericParametersRedCap" in "BWP-UplinkCommon" as "initialUplinkBWP-RedCap" in "UplinkConfigCommon" in "ServingCellConfigCommon"). The second initial UL BWP information may be cell-specific.

[0064] <Settings related to SSB> The first SSB may be set on the terminal 10 based on information regarding the transmission of the first SSB (hereinafter referred to as "first SSB transmission information"). The first SSB transmission information may include at least one of the following: information regarding the transmission of the first SSB within an SS burst set (hereinafter referred to as "ssb-PositionsInBurst"), information regarding the SSB period of the first SSB (hereinafter referred to as "ssb-periodicityServingCell"), information regarding the transmission power of the first SSB (hereinafter referred to as "ss-PBCH-BlockPower"), information regarding the transmission frequency of the first SSB (hereinafter referred to as "ssb-Frequency"), and information regarding the measurement timing of the first SSB (hereinafter referred to as "SSB-MTC"). The first SSB transmission information may be an RRC parameter in SIB1 (for example, a parameter in "ServingCellConfigCommonSIB") or an RRC parameter in another RRC message (for example, a parameter in "ServingCellConfigCommon"). The first SSB transmission information may be cell-specific.

[0065] A second SSB may be set in terminal 10 based on information regarding the transmission of the second SSB (hereinafter referred to as "second SSB transmission information"). The second SSB transmission information may include at least one of the following: information regarding the transmission of the second SSB within an SS burst set (hereinafter referred to as "additionalSSB-PositionsInBurst"), information regarding the SSB period of the second SSB (hereinafter referred to as "additionalSSB-periodicityServingCell"), information regarding the transmission power of the second SSB (hereinafter referred to as "additional-SS-PBCH-BlockPower"), information regarding the transmission frequency of the second SSB (hereinafter referred to as "additionalSSB-Frequency"), and information regarding the measurement timing of the second SSB (hereinafter referred to as "additionalSSB-SMTC"). The second SSB transmission information may be an RRC parameter in SIB1 (for example, a parameter in "ServingCellConfigCommonSIB") or an RRC parameter in another RRC message (for example, a parameter in "ServingCellConfigCommon"). 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.

[0066] If the transmission resources for the first SSB and the transmission resources for the second SSB overlap, terminal 10 may use the first SSB (i.e., prioritize the first SSB). The transmission resources may be, for example, resources in the time domain and / or frequency domain.

[0067] <Settings related to PDCCH> Information regarding the configuration of PDCCH in the first initial DL BWP (hereinafter referred to as "pdcch-ConfigCommon") may be set in the terminal 10. pdcch-ConfigCommon may include at least one of information regarding the paging search space (hereinafter referred to as "pagingSearchSpace"), information regarding the RA search space (hereinafter referred to as "ra-SearchSpace"), information regarding the CORESET (hereinafter referred to as "commonControlResourceSet"), and information regarding the first PDCCH monitoring occasion within the paging occasion (paging occasion: PO) (hereinafter referred to as "firstPDCCH-MonitoringOccasionOfPO"). pdcch-ConfigCommon may be an RRC parameter within SIB1 (for example, a parameter within "BWP-DownlinkCommon" as "initialDownlinkBWP" within "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Alternatively, pdcch-ConfigCommon may be an RRC parameter within other RRC messages (for example, a parameter within "BWP-DownlinkCommon" as "initialDownlinkBWP" within "DownlinkConfigCommon" within "ServingCellConfigCommon"). pdcch-ConfigCommon may be cell-specific. pdcch-ConfigCommon may be referred to as the first downlink control channel configuration information or the like.

[0068] Information regarding the PDCCH configuration in the second initial DL BWP (hereinafter referred to as "pdcch-ConfigCommonRedCap") may be set on 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 (for example, a parameter in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Alternatively, pdcch-ConfigCommonRedCap may be an RRC parameter in another RRC message (for example, a parameter in "BWP-DownlinkCommon" as "initialDownlinkBWP" in "DownlinkConfigCommon" within "ServingCellConfigCommon"). pdcch-ConfigCommonRedCap may be cell-specific. pdcch-ConfigCommonRedCap may also be referred to as the second downlink control channel configuration information, etc.

[0069] <Settings related to random access> Information regarding the configuration of random access in the first initial DL BWP (hereinafter referred to as "rach-ConfigCommon") may be set in terminal 10. rach-ConfigCommon may include at least one of the following: 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"), and information regarding the threshold of the received power (e.g., RSRP) of the first SSB (hereinafter referred to as "rsrp-ThresholdSSB"). rach-ConfigCommon may also be an RRC parameter in SIB1 (e.g., a parameter in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Alternatively, rach-ConfigCommon may be an RRC parameter in another RRC message (for example, a parameter in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommon" within "ServingCellConfigCommon"). rach-ConfigCommon may be cell-specific. rach-ConfigCommon may also be called the first random access parameter, etc.

[0070] Information regarding the configuration of random access in the second initial DL BWP (hereinafter referred to as "rach-ConfigCommonRedCap") may be set in terminal 10. rach-ConfigCommonRedCap may include at least one of the following: 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"), and information regarding the threshold of the received power (e.g., RSRP) of the second SSB (hereinafter referred to as "rsrp-ThresholdSSB"). rach-ConfigCommonRedCap may also be an RRC parameter in SIB1 (e.g., a parameter in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). Alternatively, rach-ConfigCommonRedCap may be an RRC parameter in another RRC message (for example, a parameter in "BWP-UplinkCommon" as "initialUplinkBWP" in "UplinkConfigCommon" within "ServingCellConfigCommon"). rach-ConfigCommonRedCap may be cell-specific. rach-ConfigCommonRedCap may also be called a second random access parameter, etc.

[0071] <Paging settings> Information regarding the paging settings in the first initial DL BWP (hereinafter referred to as "PCCH-Config") may be set in terminal 10. PCCH-Config may include at least one of the following: information regarding the paging cycle (hereinafter referred to as "PagingCycle"), firstPDCCH-MonitoringOccasionOfPO, information indicating the number and / or time offset of paging frames (paging frames: PF) in the paging cycle (hereinafter referred to as "nAndPagingFrameOffset"), information regarding the number of POs per PF (hereinafter referred to as "ns"), and information regarding the number of PDCCH monitoring opportunities per SSB in PO (hereinafter referred to as "nrofPDCCH-MonitoringOccasionPerSSB-InPO"). PCCH-Config may also be an RRC parameter in SIB1 (for example, a parameter in "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). PCCH-Config may also be cell-specific. PCCH-Config may also be referred to as the first paging setting information, etc.

[0072] Information regarding the paging settings in the second initial DL BWP (hereinafter referred to as "PCCH-ConfigRedCap") may be set in terminal 10. PCCH-ConfigRedCap may include at least one of defaultPagingCycle, firstPDCCH-MonitoringOccasionOfPO, nAndPagingFrameOffset, ns, and nrofPDCCH-MonitoringOccasionPerSSB-InPO. PCCH-ConfigRedCap may also be an RRC parameter in SIB1 (for example, a parameter in "DownlinkConfigCommonSIB" within "ServingCellConfigCommonSIB"). PCCH-Config may be cell-specific. PCCH-ConfigRedCap may also be referred to as the second paging setting information, etc.

[0073] (Operation based on SSB) (1) Determination of PDCCH monitoring opportunities for paging Terminal 10 monitors the PDCCH during a PDCCH monitoring opportunity and receives the DCI used for scheduling the PDSCH that transmits paging messages. The DCI may be CRC scrambled by a specific RNTI (e.g., Paging(P)-RNTI). Terminal 10 may determine a PDCCH monitoring opportunity based on whether a second initial DL BWP is set within cell C where a first initial DL BWP is set.

[0074] Terminal 10 determines the paging frame based on at least one of the DRX period, the number of PFs within the DRX period, the time offset, and the identifier of terminal 10. Here, PF is, for example, a radio frame (RF) containing a PO. For example, terminal 10 may determine the identification number of the PF (hereinafter referred to as the "System Frame Number (SFN)") based on the following equation (1). (Formula 1) (SFN+PF_offset) mod T = (T div N)*(UE_ID mod N) Here, T is the DRX period, N is the number of PFs in T, PF_offset is a predetermined offset, and UE_ID is a value determined based on the identifier of terminal 10 (e.g., 5G-S-TMSI). T may be determined based on the above PagingCycle. PagingCycle may represent, for example, 32, 64, 128, or 256 RFs. Also, N and / or PF_offset may be determined based on the above nAndPagingFrameOffset. nAndPagingFrameOffset may represent that a PF is placed for every x RF in T (e.g., x=1, 2, 4, 8, or 16) and / or a time offset.

[0075] Terminal 10 may determine the PO within the PF based on at least one of the ID of the search space used as the paging search space, the firstPDCCH-MonitoringOccasionOfPO, and the nrofPDCCH-MonitoringOccasionPerSSB-InPO. A PO may be, for example, a set of one or more PDCCH monitoring opportunities for paging, and may consist of S*X consecutive PDCCH monitoring opportunities (e.g., S*X consecutive symbols excluding UL symbols) from the time position indicated by firstPDCCH-MonitoringOccasionOfPO. Each PDCCH monitoring opportunity within a PO may consist of a predetermined number of symbols. firstPDCCH-MonitoringOccasionOfPO may indicate, for example, the time position (e.g., the position of a symbol) of the first PDCCH monitoring opportunity within the PF.

[0076] Here, S is the number of SSBs actually transmitted within the SS burst set, and may be indicated by ssb-PositionsInBurst or additionalSSB-PositionsInBurst. X is the number of PDCCH monitoring opportunities per SSB in the PO, and may be determined based on nrofPDCCH-MonitoringOccasionPerSSB-InPO. nrofPDCCH-MonitoringOccasionPerSSB-InPO may indicate, for example, that the number of PDCCH monitoring opportunities per SSB in the PO is between 2 and 4, and if nrofPDCCH-MonitoringOccasionPerSSB-InPO is not set, it may indicate that the number of such PDCCH monitoring opportunities is 1.

[0077] Figures 7 and 8 show examples of SSB, PF, and PO according to this embodiment. Figures 7 and 8 show examples of the first and second SSB, PF, and PO in the first and second initial DL BWP, respectively. However, the settings for the first and second SSB, PF, and PO in the first and second initial DL BWP are not limited to those shown and can be changed as appropriate by setting various parameters.

[0078] For example, in the first initial DL BWP, as shown in Figure 7, T=32RF, and nAndPagingFrameOffset may indicate that a PF is placed for every RF in T (oneT). Terminal 10 may determine the PF for terminal 10 (here, RF#0) from among the 32 PFs in T based on its UE_ID. Also, firstPDCCH-MonitoringOccasionOfPO for the first initial DL BWP indicates the 5th symbol from the beginning among symbols #0 to #139 in the PF (i.e., symbol #4 in slot #0). Furthermore, ssb-PositionsInBurst=11111111, and S=8 because SSB#0 to #7 (the first SSB) in the SS burst set are actually transmitted. Also, since the number of PDCCH opportunities per first SSB is 1, X=1. Therefore, terminal 10 determines the 8 consecutive symbols starting from symbol #4 in slot #0 of RF#0 as the PO. The PO consists of S*X (in this case, 8) PDCCH monitoring opportunities, and SSB#0 to #7 may correspond to the 1st to 8th PDCCH monitoring opportunities within the PO (i.e., PDCCH monitoring opportunities with symbols #4 to #11 in slot #0). In multibeam operation, terminal 10 may assume that the DM-RS of the corresponding SSB and PDCCH are quasi-collocated at each PDCCH monitoring opportunity within the PO.

[0079] On the other hand, in the second initial DL BWP, as shown in Figure 8, T=32RF, and nAndPagingFrameOffset may indicate that a PF is placed every 8RFs in T (oneEightT) and a time offset of "2". Terminal 10 may determine the PF for terminal 10 (here, RF#2) from among the 4 PFs in T based on its UE_ID. In Figure 8, since nAndPagingFrameOffset indicates oneEightT, the candidate position of the first symbol for the paging monitoring opportunity is 1120 symbols (i.e., 1120 symbols at indices #0 to #1119 in RF#0 to #7 (=8*10*14)). In Figure 8, firstPDCCH-MonitoringOccasionOfPO for the second initial DL BWP indicates symbol #284 within symbols #0 to #1119 in RF#0 to #7 (i.e., symbol #4 in slot #0 of PF#2). In Figure 8, each slot within each RF is assigned a symbol index, but symbol indices #0 to #1119 may also be assigned to all symbols within RF #0 to #7. Additionally, additionalSSB-PositionsInBurst = 11110000, and SSBs #0 to #3 (the second SSB) in the SS burst set are actually transmitted, while SSBs #4 to #7 are not, so S = 4. Also, since the number of PDCCH opportunities per SSB is 1, X = 1. Therefore, terminal 10 determines the 4 consecutive symbols starting from symbol #4 in slot #0 of RF #2 as the PO. This PO consists of S*X (4 in this case) PDCCH monitoring opportunities, and SSBs #0 to #4 may correspond to the 1st to 4th PDCCH monitoring opportunities within the PO (i.e., the PDCCH monitoring opportunities for symbols #4 to #7 in slot #0). Terminal 10 may assume that the corresponding SSB and PDCCH DM-RS are pseudo-collocated at each PDCCH monitoring opportunity within the PO.

[0080] As shown in Figures 7 and 8, the terminal 10 can independently configure parameters for a first initial DL BWP (e.g., first SSB transmission information and pdcch-ConfigCommon) and parameters for a second initial DL BWP (e.g., second SSB transmission information and pdcch-ConfigCommonRedCap). Therefore, the terminal 10 decides whether to configure the PDCCH monitoring opportunity for paging based on the parameters for the first or second initial DL BWP, depending on whether the second initial DL BWP is configured and / or whether predetermined conditions are met.

[0081] Figure 9 is a flowchart illustrating an example of the operation for determining a PDCCH monitoring opportunity for paging according to this embodiment. In Figure 9, it is assumed that the terminal 10 has a first initial DL BWP set. In step S101, the terminal 10 determines whether or not a second initial DL BWP is set.

[0082] In step S102, if a second initial DL BWP is set on terminal 10, terminal 10 determines whether it satisfies the conditions for sending a second SSB in the second initial DL BWP, setting a paging search space in the second initial DL BWP, and at least one of the capabilities of terminal 10. Specifically, terminal 10 may determine whether at least one of the following conditions is satisfied. (a) The second SSB transmission in the second initial DL BWP is configured. (b) In the second initial DL BWP, a paging search space is set up. (c) Terminal 10 has certain capabilities.

[0083] For example, condition (a) above may be that a second SSB transmission information (e.g., at least one of additionalSSB-Frequency, additionalSSB-PositionsInBurst, and additionalSSB-PeriodicityServingCell) is set. Also, condition (b) above may be that pagingsearchspace (e.g., the search space ID of the paging search space) is set in pdcch-ConfigCommonRedCap, or that pagingsearchspace and commonControlResourceSet are set in pdcch-ConfigCommonRedCap. Furthermore, the specific capability in condition (c) above is the capability of terminal 10 regarding CORESET#0 and / or SSB in BWP. For example, condition (c) may be that each BWP set in terminal 10 includes the bandwidth of CORESET#0 and SSB (feature group 6-1), and / or allows BWPs that do not include the bandwidth of CORESET#0 and SSB (feature group 6-1a).

[0084] If a second initial DL BWP is configured and the conditions of step S102 are met (step S102; YES), in step S103, terminal 10 determines a PDCCH monitoring opportunity for paging based on additionalSSB-PositionsInBurst for the second SSB and / or pdcch-ConfigCommonRedCap for the PDCCH configuration in the second initial DL BWP.

[0085] Specifically, in step S103, terminal 10 may determine a PDCCH monitoring opportunity for paging based on additionalSSB-PositionsInBurst and / or pdcch-ConfigCommonRedCap if the search space ID indicated by pagingsearchspace in pdcch-ConfigCommonRedCap is not 0. For example, as shown in Figure 8, terminal 10 may determine the PDCCH monitoring opportunity for paging to be symbols #4 to #7 in slot #0 in RF#2 based on additionalSSB-PositionsInBurst and firstPDCCH-MonitoringOccasionOfPO in pdcch-ConfigCommonRedCap. On the other hand, if the search space ID is 0, terminal 10 may determine the PDCCH monitoring opportunity for SIB1 as the PDCCH monitoring opportunity for paging.

[0086] In step S103, terminal 10 may determine a PDCCH monitoring opportunity for paging based on pcch-ConfigRedCap instead of or in addition to pdcch-ConfigCommonRedCap. For example, terminal 10 may determine a PDCCH monitoring opportunity for paging based on at least one of the following: firstPDCCH-MonitoringOccasionOfPO, nrofPDCCH-MonitoringOccasionPerSSB-InPO, defaultPagingCycle, and nAndPagingFrameOffset within pdcch-ConfigCommonRedCap or pcch-ConfigRedCap.

[0087] If the second initial DL BWP is not set (step S101; NO), or if the second initial DL BWP is set and the conditions of step S102 are not met (step S102; NO), in step S104, terminal 10 determines a PDCCH monitoring opportunity for paging based on ssb-PositionsInBurst for the first SSB and / or pdcch-ConfigCommon for the PDCCH setting in the first initial DL BWP.

[0088] Specifically, in step S104, terminal 10 may determine a PDCCH monitoring opportunity for paging based on ssb-PositionsInBurst and / or pdcch-ConfigCommon if the search space ID indicated by pagingsearchspace in pdcch-ConfigCommon is not 0. For example, as shown in Figure 7, terminal 10 may determine the PDCCH monitoring opportunity for paging to be symbols #4 to #11 in slot #0 in RF#0 based on ssb-PositionsInBurst and firstPDCCH-MonitoringOccasionOfPO in pdcch-ConfigCommon. On the other hand, if the search space ID is 0, terminal 10 may determine the PDCCH monitoring opportunity for SIB1 as the PDCCH monitoring opportunity for paging.

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

[0090] According to the above operation, even if a second SSB may be transmitted in the second initial DL BWP, the PDCCH monitoring opportunity for paging can be appropriately determined. Therefore, terminal 10 can receive paging messages based on the DCI detected in the PDCCH monitoring opportunity.

[0091] (2) Determination of RA preamble and / RO In the random access procedure, terminal 10 transmits an RA preamble. Terminal 10 may determine the RO used to transmit the RA preamble and / or the RA preamble based on whether a second initial DL BWP is set in cell C where a first initial DL BWP is set.

[0092] The RA preamble is a predetermined sequence, also known as the PRACH preamble, preamble, preamble sequence, message 1, PRACH, etc. RO is, for example, a time-domain and / or frequency-domain resource for transmitting the RA preamble, and may consist of one or more symbols and M (M≧1) resource blocks. RO is also known as the PRACH opportunity, random access opportunity, transmission opportunity, opportunity, etc. The RA preamble may be transmitted using a Random Access Channel (PRACH). RACH is a UL channel used for transmitting the RA preamble, also known as the Physical Random Access Channel (PRACH), etc.

[0093] Random access procedures include contention-based random access (CBRA) and contention-free random access (CFRA). Both CBRA and CFRA support two types each. The first type is called Type 1, Type-1 random access procedure, 4-step RACH, or 4-step random access, etc. The second type is called Type 2, Type-2 random access procedure, 2-step RACH, or 2-step random access, etc.

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

[0095] In a Type 1 CFRA, terminal 10 transmits an RA preamble assigned by base station 20 to base station 20. Terminal 10 receives an RAR from base station 20 via PDSCH, depending on the RA preamble. Since the RA preamble is indicated by DCI, the CFRA is also called an RA in the order of PDCCH.

[0096] In a Type 2 CBRA, terminal 10 sends the RA preamble and message 3 from a Type 1 CBRA as message A and receives message B (i.e., RAR). In a Type 2 CBRA, the RA preamble in message A is also randomly selected. In a 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.

[0097] In the above-described types 1 and 2 CBRA and CFRA, terminal 10 may select an RO and / or RA preamble based on the RSRP of the SSB and transmit the RA preamble using the selected RO. Base station 20 can recognize which SSB terminal 10 received, i.e., which beamforming direction it is in, from the RA preamble received from terminal 10 and / or the RO used to transmit the RA preamble. In other words, base station 20 may estimate a pseudo-collocation (QCL) relationship for terminal 10 based on the RA preamble from terminal 10 and / or the SSB associated with the RO used to receive the RA preamble. Control unit 203 may control the transmission of DL signals and / or the reception of UL signals using the same spatial parameters (beams) as the SSB.

[0098] Furthermore, terminal 10 may monitor PDCCH in the RA search space to detect DCIs that have been CRC scrambled in a specific RNTI (e.g., RA-RNTI), and receive at least one of RARs, message 4, and message B in type 1 and 2 CBRAs and CFRAs via PDSCH scheduled by the DCI.

[0099] Figure 10 shows an example of the relationship between the SSB, RO, and RA preamble according to this embodiment. For example, Figure 10 shows the relationship between SSB#0~#7 (first SSB) actually transmitted in the first initial DL BWP and the RO and RA preamble in the first initial UL BWP. Note that Figure 10 is merely an example, and the relationship between the SSB, RO, and RA preamble is not limited to that shown.

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

[0101] For example, as shown in Figure 10, each RACH slot may be provided with one or more ROs. One RO consists of M (M≧1) resource blocks. In addition, K (K=2 in Figure 10) ROs can be placed in the frequency domain. In addition, one or more ROs can be placed in the time domain per RACH slot. For example, in Figure 10, a total of 2 ROs are placed in each RACH slot: 2 in the frequency domain and 1 in the time domain. Thus, each RACH slot may contain one or more ROs in the time domain and / or the frequency domain.

[0102] An SSB is associated with one or more ROs. Also, one SSB is associated with one or more RA preambles. The association between an SSB and ROs and / or RA preambles may be shown by ssb-perRACHOccasionAndCB-PreamblesPerSSB. Specifically, ssb-perRACHOccasionAndCB-PreamblesPerSSB may show the number of SSBs associated with one RO and / or the number of RA preambles associated with one SSB.

[0103] For example, in Figure 10, ssb-PositionsInBurst=11111111, and it is assumed that SSB#0~#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 number of SSBs X associated with one RO is not limited to 1; it may be a number greater than 1 (e.g., 2, 4, 8, or 16) or a number less than 1 (e.g., 1 / 8, 1 / 4, or 1 / 2). If X≧1, one RO is associated with X SSBs. If X<1, one SSB is associated with the reciprocal of X ROs. Also, the number of RA preambles Y associated with one SSB is not limited to, for example, 4, 8, 12, etc.; it can be 1 or greater. Furthermore, the indices of the RO and RA preambles associated with each SSB shown in Figure 10 are merely examples and are not limited to those illustrated.

[0104] In Figure 10, terminal 10 measures the RSRP using SSB#0 to #7 in the SS burst set during the first initial DL BWP. Terminal 10 selects at least one of SSB#0 to #7 based on the measured RSRP of SSB#0 to #7 and the threshold indicated by rsrp-ThresholdSSB. Specifically, terminal 10 may select at least one of SSB#0 to #7 whose RSRP exceeds the threshold.

[0105] For example, in Figure 10, when terminal 10 selects two SSBs, #0 and #1, based on the RSRP and the threshold, it randomly selects one RA preamble from RA preambles #0 to #15 associated with SSBs #0 and #1. Terminal 10 also selects one RO from RO#0 and #1 associated with SSBs #0 and #1, respectively. Terminal 10 transmits the selected RA preamble using the selected RO. In the case of CFRA, terminal 10 may also transmit the RA preamble indicated by DCI using the selected RO.

[0106] Furthermore, although Figure 10 assumes a Type 1 CBRA or CFRA, it is applicable to Type 2 CBRA or CFRA. Information regarding the association of RO and / or RA preamble for message A (hereinafter referred to as "msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB") may be set in terminal 10. Also, information regarding the RSRP threshold of the SSB for Type 2 CBRA or CFRA (hereinafter referred to as "msgA-RSRP-ThresholdSSB") may be set in terminal 10. Terminal 10 may select the RA preamble as message A and / or RO for sending the RA preamble based on msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB and msgA-RSRP-ThresholdSSB, similar to ssb-perRACH-OccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB described in Figure 10.

[0107] Figure 11 shows another example of the relationship between the SSB and the RO and RA preamble according to this embodiment. For example, Figure 11 shows the relationship between SSB#0~#3 (second SSB) actually transmitted in the second initial DL BWP and the RO and RA preamble in the second initial UL BWP. Note that Figure 11 is merely illustrative, and the relationship between the SSB, RO, and RA preamble is not limited to what is shown. Furthermore, Figure 11 will be explained focusing on the differences from Figure 10.

[0108] For example, in Figure 11, additionalSSB-PositionsInBurst=11110000, and it is assumed that SSB#0~#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 (i.e., one SSB corresponds to two ROs) ("oneHalf"), and that 16RA preambles correspond to one SSB ("n16").

[0109] In Figure 11, terminal 10 measures the RSRP using SSB#0 to #3 in the SS burst set during the second initial DL BWP. Terminal 10 selects at least one of SSB#0 to #7 based on the RSRP measurement results of SSB#0 to #3 and the threshold indicated by rsrp-ThresholdSSB. Specifically, terminal 10 may select at least one of SSB#0 to #3 whose RSRP exceeds the threshold.

[0110] For example, in Figure 11, when terminal 10 selects SSB#1 based on the RSRP and the threshold, it randomly selects one RA preamble from RA preambles #15 to #31 associated with SSB#1. Terminal 10 also selects one RO from RO#2 and #3 associated with SSB#1. Terminal 10 transmits the selected RA preamble using the selected RO. In the case of CFRA, terminal 10 may also transmit the RA preamble indicated by DCI using the selected RO.

[0111] Furthermore, although Figure 11 assumes a Type 1 CBRA or CFRA, it is applicable to Type 2 CBRA or CFRA as well. Information regarding the association of RO and / or RA preamble for message A (hereinafter referred to as "msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB") may be set in terminal 10. Also, information regarding the RSRP threshold of the SSB for Type 2 CBRA or CFRA (hereinafter referred to as "msgA-RSRP-ThresholdSSB") may be set in terminal 10. Terminal 10 may select the RA preamble as message A and / or RO for sending the RA preamble based on msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB and msgA-RSRP-ThresholdSSB, similar to ssb-perRACH-OccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB described in Figure 11.

[0112] As shown in Figures 10 and 11, the terminal 10 may independently configure parameters for a first initial DL BWP (e.g., first SSB transmission information and rach-ConfigCommon) and parameters for a second initial DL BWP (e.g., second SSB transmission information and rach-ConfigCommonRedCap). Therefore, the terminal 10 decides whether to select the RO and / or RA preamble based on the parameters for the first or second initial DL BWP, based on whether the second initial DL BWP is configured and / or whether predetermined conditions are met.

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

[0114] In step S202, if a second initial DL BWP is configured on terminal 10, terminal 10 determines whether it satisfies the conditions for transmitting a second SSB in the second initial DL BWP, configuring the RA search space in the second initial DL BWP, configuring the second random access parameter, and at least one of the capabilities of terminal 10. Specifically, terminal 10 may determine whether at least one of the following conditions is satisfied. (A) The second SSB transmission in the second initial DL BWP is configured. (B) The RA search space is set up in the second initial DL BWP. (C) The second random access parameter is set. (D) Terminal 10 has certain capabilities.

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

[0116] If a second initial DL BWP is configured and the conditions in step S202 are met (step S202; YES), in step S203, terminal 10 selects an RA preamble and / or RO based on additionalSSB-PositionsInBurst and / or RACH-ConfigCommonRedCap for the second SSB.

[0117] Specifically, in step S203, terminal 10 may select an RA preamble and / or RO based on additionalSSB-PositionsInBurst, ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB within RACH-ConfigCommonRedCap, and RSRP of the second SSB. For example, as shown in Figure 11, terminal 10 may determine the RO and / or RA preamble corresponding to SSB#0 to #3, respectively, based on additionalSSB-PositionsInBurst and ssb-perRACHOccasionAndCB-PreamblesPerSSB within RACH-ConfigCommonRedCap. Furthermore, terminal 10 may select at least one of SSB#0 to #3 (for example, in Figure 11, SSB#1 which has an RSRP that exceeds the threshold indicated by RSRP-ThresholdSSB) based on the RSRP of SSB#0 to #3 and the RSRP-ThresholdSSB in RACH-ConfigCommonRedCap. Also in Figure 11, terminal 10 may select 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.

[0118] If the second initial DL BWP is not set (step S201; NO), or if the second initial DL BWP is set and the conditions of step S202 are not met (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.

[0119] Specifically, in step S204, terminal 10 may determine the RA preamble and / or RO based on at least one of ssb-PositionsInBurst, ssb-perRACHOccasionAndCB-PreamblesPerSSB and RSRP-ThresholdSSB in RACH-ConfigCommon, and the RSRP of the first SSB. For example, as shown in Figure 10, terminal 10 may determine the RO and / or RA preamble corresponding to each of SSB#0 to #7 based on ssb-PositionsInBurst and ssb-perRACHOccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. Furthermore, terminal 10 may select at least one of SSB#0 to #7 (for example, in Figure 10, SSB#0 and #1 which have RSRPs that exceed the threshold indicated by RSRP-ThresholdSSB) based on the RSRPs of SSB#0 to #7 and the RSRP-ThresholdSSB in RACH-ConfigCommon. Also in Figure 10, terminal 10 may select one of RO#0 and #1 corresponding to the selected SSB#0 and #1, and / or one of RA preambles #0 to #15 corresponding to the selected SSB#0 and #1.

[0120] The operation shown in Figure 12 is also applicable to Type 2 CBRA and CFRA. In the case of Type 2, 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.

[0121] According to the above operation, even if a second SSB may be transmitted in the second initial DL BWP, the RO and / or RA preamble can be appropriately selected. Therefore, the operation related to random access can be appropriately controlled. Note that the selection of the RA preamble described above may also mean selecting (or determining) one RA preamble to be transmitted by terminal 10 using RACH from one or more groups (or sets) of RA preambles. Furthermore, the selection of the RA preamble may be rephrased as the selection or determination of the index of the RA preamble, and terminal 10 may transmit the RA preamble of the selected index via RACH.

[0122] (3) Operation when MIB is received Terminal 10 receives the MIB via the PBCH. Terminal 10 may control its operation upon MIB reception based on whether a second initial DL BWP is set within cell C where the first initial DL BWP is set. Specifically, if a second initial DL BWP is set, terminal 10 may ignore certain parameters in the MIB received via the PBCH in the SSB transmitted by the second initial DL BWP, or assume that such specific parameters are not transmitted.

[0123] Figure 13 shows an example of an MIB according to this embodiment. As shown in Figure 13, the MIB may include at least one of the following parameters. • Information regarding SFN (hereinafter referred to as "systemFrameNumber") • Information regarding subcarrier spacing (hereinafter referred to as "subCarrierSpacingCommon") • Frequency offset between SSB and resource block grid (k SSB Information regarding ) (hereinafter referred to as "ssb-SubcarrierOffset") • Information regarding the location of the DM-RS (hereinafter referred to as "dmrs-TypeA-Position") • Information regarding the common CORESET (CORESET#0) and / or the common search space (search space#0) (hereinafter referred to as "pdcch-ConfigSIB1") • Information regarding whether or not a cell (or camp-on against it) is prohibited (hereinafter referred to as "cellBarred") • Information regarding the selection and / or reselection of the same frequency cell (hereinafter referred to as "intraFreqReselection")

[0124] Figure 14 is a flowchart illustrating an example of the operation when receiving an MIB according to this embodiment. In Figure 14, it is assumed that the terminal 10 has a first initial DL BWP set. In step S301, the terminal 10 determines whether or not a second initial DL BWP is set.

[0125] In step S302, if a second initial DL BWP is configured on terminal 10, terminal 10 determines whether it satisfies at least one of the following conditions: transmission of a second SSB in the second initial DL BWP, configuration of a paging search space in the second initial DL BWP, configuration of an RA search space in the second initial DL BWP, or a condition relating to the capabilities of terminal 10. Specifically, terminal 10 may determine whether at least one of the following conditions is satisfied. (i) The second SSB transmission in the second initial DL BWP is configured. (ii) In the second initial DL BWP, a paging search space is set up. (iii) The RA search space is set up in the second initial DL BW. (iv) Terminal 10 has a specific capability. 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.

[0126] If a second initial DL BWP is set and the conditions of step S302 are met (step S302; YES), in step S303, terminal 10 may ignore a specific parameter in the MIB received via the PBCH in the second SSB, or assume that such a specific parameter is not transmitted.

[0127] Here, the specific parameter in the MIB is, for example, at least one of cellBarred, intraFreqReselection, and ssb-SubcarrierOffset. The specific parameter only needs to be at least one parameter in the MIB. Terminal 10 may control the reception of DL signals in the second initial DL BWP and / or the transmission of UL signals in the second initial UL BWP based on parameters in the MIB other than the specific parameter.

[0128] If the second initial DL BWP is not set (step S301; NO), or if the second initial DL BWP is set and the conditions of step S302 are not met (step S302; NO), in step S304, terminal 10 may control the reception of DL signals in the first initial DL BWP and / or the transmission of UL signals in the first initial UL BWP based on each parameter in the MIB received via the PBCH in the first SSB.

[0129] The operation of terminal 10 when a second initial DL BWP is set is not limited to the above. For example, when a second initial DL BWP is set, terminal 10 may interpret a specific parameter in the MIB received via the PBCH in the second SSB to have a specific meaning, regardless of its value. The specific parameter in question may be, for example, cellBarred, and terminal 10 may interpret cellBarred to mean that the cell is not prohibited, even if it means the cell is prohibited.

[0130] Based on the above operation, if a second SSB can be transmitted not only in the first initial DL BWP but also in the second initial DL BWP, the system can operate appropriately based on the MIB.

[0131] (Parameters) Referring to Figures 15-18, an example of the parameters or information used to configure terminal 10 for the SSB-based operations (1)-(3) in this embodiment will be described. Note that the parameters or information shown in Figures 15-18 are merely examples, and their names, sizes, hierarchical structures, etc., are not limited to those shown. Furthermore, it goes without saying that parameters or information not shown in Figures 15-18 may also be used for the operations (1)-(3) in this embodiment.

[0132] Figure 15 shows an example of BWP-DownlinkCommon according to this embodiment. BWP-DownlinkCommon is information used to set common parameters of DL BWP and may be included in ServingCellConfigCommon or ServingCellConfigCommonSIB. ServingCellConfigCommonSIB is cell-specific parameters and may be included in SIB1. ServingCellConfigCommon is cell-specific configuration parameters and may be included in other RRC messages.

[0133] As shown in Figure 15, BWP-DownlinkCommon may include at least one of the following: • The first initial DL BWP information mentioned above is genericParameters • Information regarding the PDCCH configuration in the first initial DL BWP: pdcch-ConfigCommon • Information regarding PDSCH configuration in the first initial DLBWP: pdsch-ConfigCommon • The second initial DL BWP information mentioned above is genericParametersRedCap • Information regarding PDCCH configuration in the second initial DL BWP: pdcch-ConfigCommonRedCap • pdsch-ConfigCommonRedCap, which is information regarding the PDSCH configuration in the second initial DL BWP, and at least one of the following as second SSB transmission information: additionalSSB-PositionsInBurst, additionalSSB-periodicityServingCell, additional-SS-PBCH-BlockPower, additionalSSB-Frequency, and additionalSSB-SMTC Furthermore, within additionalSSB-PositionsInBurst, groupPresence indicates whether each SSB group is actually transmitted when the maximum of 64 transmittable SSBs in an SS burst set is divided into eight SSB groups, based on the values ​​of the corresponding bits. Similarly, inOneGroup indicates whether each SSB within an SSB group is actually transmitted, based on the values ​​of the corresponding bits. In operating bands below 6 GHz, only the information indicated by inOneGroup may be used. In operating bands above 6 GHz, the information indicated by both inOneGroup and groupPresence may be used.

[0134] Figure 16 shows an example of BWP-UplinkCommon according to this embodiment. BWP-UplinkCommon is information used to set common parameters of UL BWP and may be included in ServingCellConfigCommon or ServingCellConfigCommonSIB. ServingCellConfigCommonSIB is cell-specific parameters and may be included in SIB1. ServingCellConfigCommon is cell-specific configuration parameters and may be included in other RRC messages.

[0135] As shown in Figure 16, BWP-UplinkCommon may include at least one of the following: • The first initial UL BWP information mentioned above is genericParameters • Information regarding the configuration of random access in the first initial UL BWP, rach-ConfigCommon • Information regarding the configuration of PUSCH in the first initial ULBWP: push-ConfigCommon • Information regarding PUCCH configuration in the first initial ULBWP: pucch-ConfigCommon • msgA-ConfigCommon, which contains information about sending message A in the first initial UL BWP. • The second initial UL BWP information mentioned above is genericParametersRedCap • Information regarding the configuration of random access in the second initial UL BWP: rach-ConfigCommonRedCap • Information regarding the configuration of PUSCH in the second initial ULBWP: push-ConfigCommonRedCap • Information regarding PUCCH configuration in the second initial ULBWP: pucch-ConfigCommonRedCap • msgA-ConfigCommonRedCap, which contains information about sending message A in the second initial UL BWP.

[0136] Figure 17 shows an example of RACH-ConfigCommon according to this embodiment. RACH-ConfigCommon may function as information regarding the configuration of random access in the first initial UL BWP (i.e., rach-ConfigCommon), or as information regarding the configuration of random access in the second initial UL BWP (i.e., rach-ConfigCommonRedCap).

[0137] As shown in Figure 17, push-ConfigCommon may include at least one of the following parameters: ssb-perRACH-OccasionAndCB-PreamblesPerSSB 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 is information regarding the RSRP threshold of the first or second SSB.

[0138] Figure 18 shows an example of RACH-ConfigCommonTwoStepRA according to this embodiment. RACH-ConfigCommonTwoStepRA may function as information regarding the transmission of message A in the first initial UL BWP (i.e., msgA-ConfigCommon) or as information regarding the transmission of message A in the second initial UL BWP (i.e., msgA-ConfigCommonRedCap).

[0139] As shown in Figure 18, RACH-ConfigCommonTwoStepRA may include at least one of the following parameters: msgA-SSB-perRACH-OccasionAndCB-PreamblesPerSSB 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 is information regarding the RSRP threshold for the first or second SSB.

[0140] (Configuration of the wireless communication system) Next, the configuration of each device in the wireless communication system 1 described above will be explained. Note that the following configuration is for illustrating the necessary configurations in this embodiment and does not preclude each device from having functional blocks other than those shown.

[0141] <Hardware Configuration> Figure 19 shows 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, terminal 10, base station 20, CN30, etc.) includes a processor 11, a storage device 12, a communication device 13 that performs wired or wireless communication, an input device that accepts various input operations, and an input / output device 14 that outputs various information.

[0142] The processor 11 is, for example, a CPU (Central Processing Unit) and controls each device in the wireless communication system 1. The processor 11 may perform various processes described in this embodiment by reading and executing a program from the storage device 12. Each device in the wireless communication system 1 may be composed of one or more processors 11. Each of these devices may also be called a computer.

[0143] The storage device 12 consists of, for example, memory, an HDD (Hard Disk Drive), and / or an SSD (Solid State Drive). The storage device 12 may store various information necessary for the execution of processing by the processor 11 (for example, programs executed by the processor 11).

[0144] The communication device 13 is a device that communicates via a wired and / or wireless network, and may include, for example, a network card, a communication module, a chip, an antenna, etc. The communication device 13 may also include an amplifier, an RF (Radio Frequency) device that processes wireless signals, and a BB (BaseBand) device that processes baseband signals.

[0145] For example, an RF device generates a radio signal to be transmitted from an antenna by performing D / A conversion, modulation, frequency conversion, power amplification, etc., on a digital baseband signal received from a BB device. The RF device also generates a digital baseband signal by performing frequency conversion, demodulation, A / D conversion, etc., on a radio signal received from an antenna and transmits it to the BB device.

[0146] The BB device performs the process of converting data into a digital baseband signal. Specifically, the BB device may map the data to subcarriers, perform an IFFT to generate OFDM symbols, insert CPs into the generated OFDM symbols, and generate a digital baseband signal. The BB device may also apply a transform precoder (DFT spread) before mapping the data to subcarriers.

[0147] Furthermore, the BB device performs a process 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 an FFT on the signal from which the CP has been removed, and extract the signal in the frequency domain. Alternatively, the BB device may apply an IDFT to the signal in the frequency domain.

[0148] The input / output device 14 includes, for example, an input device such as a keyboard, touch panel, mouse, and / or microphone, and an output device such as a display and / or speaker.

[0149] The hardware configuration described above is merely an example. Each device within the wireless communication system 1 may omit some of the hardware shown in Figure 19, or may include hardware not shown in Figure 19. Furthermore, the hardware shown in Figure 19 may be comprised of one or more chips.

[0150] <Functional Block Configuration> ≪Device≫ Figure 20 shows an example of the functional configuration of a terminal according to this embodiment. As shown in Figure 20, the terminal 10 comprises a receiving unit 101, a transmitting unit 102, and a control unit 103. The functional configuration shown in Figure 20 is merely an example, and the names of the functional categories and functional units can be anything as long as they can perform the operations according to this embodiment. Also, the receiving unit 101 and the transmitting unit 102 may be collectively referred to as the communication unit.

[0151] Furthermore, 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. In addition, 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. The program can be stored in a storage medium. The storage medium on which the program is stored may be a non-transitory computer-readable medium. The non-transitory storage medium is not particularly limited, but may be a USB memory or a CD-ROM, for example.

[0152] The receiving unit 101 receives signals (e.g., DL signals and / or sidelink signals). The receiving unit 101 may also receive information and / or data transmitted via such signals. Here, "receiving" may include performing reception-related processing such as receiving, demapping, demodulating, decoding, monitoring, and measuring at least one of the following: receiving, demapping, demodulating, decoding, monitoring, and measuring radio signals. The DL signals may include at least one of the following: PDSCH, PDCCH, downlink reference signal, synchronization signal, PBCH, etc.

[0153] The receiver 101 monitors PDCCH candidates in the search space and detects DCI. The receiver 101 may receive DL data via PDSCH scheduled using DCI. The DL data may include downlink user data and / or control information from higher layers (e.g., at least one parameter from the MAC layer, RRC layer, and Non Access Stratum (NAS) layer). The receiver 101 may also receive system information via PBCH and / or PDSCH.

[0154] The transmitter 102 transmits signals (e.g., UL signals and / or sidelink signals). The transmitter 102 may also transmit information and / or data transmitted via such signals. Here, "transmit" may include performing transmission-related processing such as encoding, modulation, mapping, and transmitting radio signals. The UL signals may include at least one of the following: PUSCH, PRACH, PUCCH, uplink reference signals, etc.

[0155] The transmitting unit 102 may transmit UL data via PUSCH, which is scheduled using the DCI received by the receiving unit 101. The UL data may include uplink user data and / or control information from higher layers (e.g., at least one parameter from the MAC layer, RRC layer, and NAS layer).

[0156] The control unit 103 performs various controls on the terminal 10. Specifically, the control unit 103 may control the operation of the terminal 10 based on various configuration information (for example, RRC layer parameters) received by the receiving unit 101 from the base station 20 or other terminal 10. The operation of the terminal 10 based on such information may be synonymous with "configuration information being set in the terminal 10 (configured)".

[0157] The control unit 103 may control the reception of signals in the receiving unit 101. The control unit 103 may also control the transmission of signals in the transmitting unit 102. The control unit 103 may decide whether or not to apply a transform precoder to the signal transmitted by the transmitting unit 102.

[0158] In this embodiment, the terminal 10 may include a receiving unit 101 that monitors the downlink control channel using a search space (e.g., a paging search space) for a predetermined period (e.g., a PDCCH monitoring opportunity) and receives downlink control information used for scheduling downlink shared channels that transmit paging messages, and a control unit 103 that determines the predetermined period based on whether or not a second initial downlink bandwidth portion (DL BWP) is set within a cell C where a first initial downlink bandwidth portion (DL BWP) is set.

[0159] The control unit 103 may determine the predetermined period based on whether the conditions relating to the transmission of the second synchronization signal block (SSB) in the second initial DL BWP, the setting of the search space in the second initial DL BWP, and at least one of the capabilities of the terminal are met when the second initial DL BWP is set.

[0160] The control unit 103 may determine the predetermined period based on at least one of the following: information regarding the transmission of the second SSB (e.g., additionalSSB-PositionInBurst) and information regarding the setting of the downlink control channel in the second initial DL BWP (e.g., pdcch-ConfigCommonRedCap), if the second initial DL BWP is set and the above conditions are met.

[0161] If a search space other than a specific ID (e.g., "0") is set as the search space, the control unit 103 may determine the predetermined period based on at least one of the information relating to the transmission of the second SSB (e.g., additionalSSB-PositionInBurst) and the information relating to the setting of the downlink control channel in the second initial DL BWP (e.g., pdcch-ConfigCommonRedCap).

[0162] If the second initial DL BWP is set and the above conditions are not met, the control unit 103 may determine the predetermined period based on at least one of the information relating to the transmission of the first SSB (e.g., SSB-PositionInBurst) and the information relating to the setting of the downlink control channel in the first initial DL BWP (e.g., pdcch-ConfigCommon).

[0163] If a search space other than a specific ID (e.g., "0") is set as the search space, the control unit 103 may determine the predetermined period based on at least one of the information relating to the transmission of the first SSB (e.g., SSB-PositionInBurst) and the information relating to the setting of the downlink control channel in the first initial DL BWP (e.g., pdcch-ConfigCommon).

[0164] If the second initial DL BWP is not set, the control unit 103 may determine the predetermined period based on at least one of the information relating to the transmission of the first SSB (e.g., SSB-PositionInBurst) and the information relating to the setting of the downlink control channel in the first initial DL BWP (e.g., pdcch-ConfigCommon).

[0165] Furthermore, in this embodiment, the terminal 10 may include a transmission unit 102 that transmits a random access preamble, and a control unit 103 that selects the resources used to transmit the random access preamble and / or the random access preamble based on whether or not a second initial downlink bandwidth portion (DL BWP) is set in a cell where a first initial downlink bandwidth portion (DL BWP) is set.

[0166] When the second initial DL BWP is set, the control unit 103 may select the random access preamble and / or the resource based on whether the following conditions are met: transmission of a second synchronization signal block (SSB) in the second initial DL BWP, setting of a search space for random access in the second initial DL BWP, setting of a second random access parameter for random access in the second initial DL BWP, and at least one of the capabilities of the terminal.

[0167] The control unit 103 may, if the second initial DL BWP is set and the above conditions are met, select the random access preamble and / or the resource based on at least one of the information relating to the transmission of the second SSB (e.g., additionalSSB-PositionInBurst), the second random access parameter (e.g., RACH-ConfigCommonRedCap), and the received power of the second SSB.

[0168] The second random access parameter may include at least one of the following: information relating the second SSB to the resource and / or the random access preamble (e.g., ssb-perRACH-OccasionAndCB-preamblesPerSSB); and information relating to the threshold of the received power of the second SSB (e.g., RSRP-ThresholdSSB).

[0169] If the second initial DL BWP is set and the above conditions are not met, the control unit 103 may select the random access preamble and / or the resource based on at least one of the following: information regarding the transmission of the first synchronization signal block (SSB) in the first initial DL BWP (e.g., ssb-PositionsInBurst), a first random access parameter for random access in the first initial DL BWP (e.g., Rach-ConfigCommon), and the received power of the first SSB.

[0170] If the second initial DL BWP is not set, the control unit 103 may select the random access preamble and / or the resource based on at least one of the following: information regarding the transmission of the first synchronization signal block (SSB) in the first initial DL BWP (e.g., ssb-PositionsInBurst), a first random access parameter for random access in the first initial DL BWP (e.g., Rach-ConfigCommon), and the received power of the first SSB.

[0171] The first random access parameter may include at least one of the following: information relating the first SSB to the resource and / or the random access preamble (e.g., ssb-perRACH-OccasionAndCB-preamblesPerSSB); and information relating to the threshold of the received power of the first SSB (e.g., RSRP-ThresholdSSB).

[0172] In this embodiment, the terminal 10 may include a receiving unit 101 that receives a master information block (MIB), and a control unit 103 that controls operation based on specific parameters in the MIB, based on whether or not a second initial downlink bandwidth portion (DL BWP) is set in a cell where a first initial downlink bandwidth portion (DL BWP) is set.

[0173] When the second initial DL BWP is set, the control unit 103 may ignore the specific parameter or assume that the specific parameter will not be transmitted, based on whether the conditions relating to the transmission of the second synchronization signal block (SSB) in the second initial DL BWP, the setting of the search space for paging in the second initial DL BWP, the setting of the search space for random access in the second initial DL BWP, and at least one of the capabilities of the terminal are met.

[0174] If the second initial DL BWP is set and the above conditions are met, the control unit 103 may ignore the specific parameter in the MIB received via the broadcast channel included in the second SSB, or assume that the specific parameter is not transmitted.

[0175] The specific parameter may include at least one of the following: information on whether a cell is prohibited (e.g., cellBarred), information on the selection and / or reselection of the frequency cell (e.g., intraFreqReselection), and information on the frequency domain offset between the second SSB and the resource block grid (e.g., ssb-SubcarrierOffset).

[0176] The control unit 103 may interpret the second initial DL BWP to have a specific meaning, regardless of the value of the specific parameter, when the second initial DL BWP is set. The specific parameter includes information about whether a cell is prohibited or not (e.g., cellBarred), and the control unit 103 may interpret that the cell is not prohibited, regardless of the value indicated by the information.

[0177] ≪Base station≫ Figure 21 is a diagram showing an example of the functional block configuration of a base station according to this embodiment. As shown in Figure 21, the base station 20 comprises a receiving unit 201, a transmitting unit 202, and a control unit 203. The functional configuration shown in Figure 21 is merely an example, and the names of the functional categories and functional units can be anything as long as they can perform the operation according to this embodiment. Also, the receiving unit 201 and the transmitting unit 202 may be collectively referred to as the communication unit.

[0178] Furthermore, 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. In addition, 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. The program can be stored in a storage medium. The storage medium on which the program is stored 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.

[0179] The receiving unit 201 receives signals (e.g., UL signals and / or sidelink signals). The receiving unit 201 may also receive information and / or data (e.g., the UL data) transmitted via the said signals.

[0180] The transmitting unit 202 transmits signals (e.g., DL signals and / or sidelink signals). The transmitting unit 202 may also transmit information and / or data (e.g., the DL data) transmitted via these signals. Some of the information transmitted from the transmitting unit 202 may be transmitted by a transmitting unit within the core network device.

[0181] The control unit 203 performs various controls for communication with the terminal 10. Specifically, the control unit 203 may determine information regarding various settings that will be notified to the terminal 10. Sending such information to the terminal 10 may be synonymous with "setting such information on the terminal."

[0182] The control unit 203 may control the reception of signals in the receiving unit 201. The control unit 203 may also control the transmission of signals in the transmitting unit 202.

[0183] In this embodiment, the base station 20 may include a transmission unit 202 that monitors the downlink control channel using a search space (e.g., a paging search space) for a predetermined period (e.g., a PDCCH monitoring opportunity) and transmits downlink control information used for scheduling downlink shared channels that transmit paging messages, and a control unit 203 that determines the predetermined period based on whether or not a second initial downlink bandwidth portion (DL BWP) is set in a cell C where a first initial downlink bandwidth portion (DL BWP) is set.

[0184] Furthermore, in this embodiment, the base station 20 may include a receiving unit 201 that receives a random access preamble, and a control unit 203 that controls the transmission of DL signals and / or the reception of UL signals based on the random access preamble and / or the resources used to receive the random access preamble.

[0185] The control unit 203 may estimate a pseudo-collocation (QCL) relationship to 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 the transmission of DL signals and / or the reception of UL signals using the same beam as the SSB.

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

[0187] When the second initial DL BWP is set, the control unit 203 may stop transmitting the specific parameter in the MIB via the broadcast channel included in the second SSB, based on whether the following conditions are met: transmission of the second synchronization signal block (SSB) in the second initial DL BWP, setting of the search space for paging in the second initial DL BWP, setting of the search space for random access in the second initial DL BWP, and at least one of the capabilities of the terminal.

[0188] The control unit 203 may stop transmitting the specific parameter in the MIB via the broadcast channel included in the second SSB if the second initial DL BWP is set and the above conditions are met.

[0189] (supplement) The various signals, information, and parameters in the above embodiment may be signaled at any layer. That is, the various signals, information, and parameters may be replaced by signals, information, and parameters of any layer, such as a higher layer (e.g., NAS layer, RRC layer, MAC layer, etc.) or a lower layer (e.g., physical layer). Furthermore, notification of predetermined information is not limited to explicit notification, but may also be done implicitly (e.g., by not notifying the information or by using other information).

[0190] Furthermore, the names of the various signals, information, parameters, IE, channels, time units, and frequency units in the above embodiments are merely illustrative and may be replaced with other names. For example, a slot may have any name as long as it is a time unit having a predetermined number of symbols. Similarly, an RB may have any name as long as it is a frequency unit having a predetermined number of subcarriers. Also, "first ~" and "second ~" are merely identifiers of multiple pieces of information or signals and may be rearranged as appropriate.

[0191] For example, in the present embodiment described above, examples of physical channels for transmitting DL data, UL data, DCI, broadcast information, and RA preamble are given as PDSCH, PUSCH, PDCCH, PBCH, and PRACH, respectively, but the names are not limited to these, as long as the physical channels have similar functions. Furthermore, these physical channels may be rephrased as the transport channels to which the physical channels are mapped. Furthermore, PDSCH, PUSCH, PDCCH, PBCH, and PRACH may be rephrased as transport channels mapped to physical channels (for example, Downlink Shared Channel (DL-SCH), Uplink Shared Channel (UL-SCH), Broadcast Channel (BCH), and at least one Random Access Channel (RCH)). These transport channels may also be rephrased as logical channels to which the transport channels are mapped. DL data and UL data are data for the downlink and uplink links, respectively, and this data may include user data and control information from higher layers (for example, RRC parameters, Medium Access Control (MAC) parameters, etc.).

[0192] Furthermore, the applications of terminal 10 in the above embodiment (e.g., RedCap, IoT, etc.) are not limited to those exemplified, and it may be used for any application (e.g., eMBB, URLLC, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.) as long as it has similar functionality. Also, the format of various information is not limited to the above embodiment, and may be changed as appropriate, such as bit representation (0 or 1), boolean value (true or false), integer value, character, etc. Also, singular and plural in the above embodiment may be interchangeable.

[0193] The embodiments described above are provided to facilitate understanding of this disclosure and are not intended to limit it. The flowcharts, sequences, elements, arrangements, indices, conditions, etc., described in the embodiments are not limited to those exemplified and can be modified as appropriate. Furthermore, it is possible to partially replace or combine at least some of the configurations described in the embodiments above.

Claims

1. Received a wireless resource control message, Based on the first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the wireless resource control message, the first SS / PBCH block is received. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the second SS / PBCH block. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block but does not include information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the first SS / PBCH block. Terminal.

2. The first SS / PBCH block is a cell-defining SS / PBCH block, and the second SS / PBCH block is a non-cell-defining SS / PBCH block. The terminal according to claim 1.

3. The terminal receives the second SS / PBCH block in the initial downlink bandwidth portion for the RedCap terminal. The terminal according to claim 1 or 2.

4. Send a wireless resource control message, Based on the first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the wireless resource control message, the first SS / PBCH block is transmitted. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block, the second SS / PBCH block is transmitted based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the second SS / PBCH block. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block but does not include information regarding the period of the second SS / PBCH block, the second SS / PBCH block is transmitted based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the first SS / PBCH block. Base station.

5. The first SS / PBCH block is a cell-defining SS / PBCH block, and the second SS / PBCH block is a non-cell-defining SS / PBCH block. The base station according to claim 4.

6. The base station transmits the second SS / PBCH block in the initial downlink bandwidth portion for the RedCap terminal. The base station according to claim 4 or 5.

7. Received a wireless resource control message, Based on the first synchronization signal and information regarding the period of the physical broadcast channel (SS / PBCH) block included in the wireless resource control message, the first SS / PBCH block is received. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block and information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the second SS / PBCH block. If the wireless resource control message includes information regarding the frequency of the second SS / PBCH block but does not include information regarding the period of the second SS / PBCH block, the second SS / PBCH block is received based on the information regarding the frequency of the second SS / PBCH block and the information regarding the period of the first SS / PBCH block. A wireless communication method performed by a terminal.

8. The first SS / PBCH block is a cell-defining SS / PBCH block, and the second SS / PBCH block is a non-cell-defining SS / PBCH block. The wireless communication method according to claim 7.

9. In the process of receiving the second SS / PBCH block, the terminal receives the second SS / PBCH block in the initial downlink bandwidth portion for the RedCap terminal. The wireless communication method according to claim 7 or 8.

Images