terminal

By equipping terminals with receiving units for both types of SSBs and controlling MIB information, the SSB procedures in network energy saving are clarified, improving flexibility and efficiency in SSB utilization.

WO2026234988A1PCT designated stage Publication Date: 2026-11-12NTT DOCOMO INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2026/015851
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-04-20
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

The procedures for applying Synchronization Signaling Blocks (SSBs) in network energy saving (NES) in wireless communication systems are unclear, particularly regarding the relationship between always-on (AO) SSBs and on-demand (OD) SSBs, and the transmission start positions based on Downlink Control Information (DCI).

Method used

A terminal is equipped with a receiving unit for both continuously transmitted and on-demand synchronization signal blocks, assuming same or different center frequencies, and a control unit to clarify the MIB information and SSB types, allowing flexible and efficient SSB configurations through methods like assuming same or different MIB parameters and control channel settings for AO-SSB and OD-SSB.

Benefits of technology

This clarifies SSB procedures in network energy saving, enhancing flexibility and simplifying configurations, thereby optimizing SSB utilization for various use cases and reducing operational load on terminals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2026015851_12112026_PF_FP_ABST
    Figure JP2026015851_12112026_PF_FP_ABST
Patent Text Reader

Abstract

This terminal comprises: a reception unit for receiving a constantly transmitted synchronization signal block and a synchronization signal block transmitted on demand, the synchronization signal blocks having the same or different center frequencies; and a control unit for assuming that information in master information blocks (MIBs) respectively included in the constantly transmitted synchronization signal block and the synchronization signal block transmitted on demand partially or completely overlap, or that the types of the constantly transmitted synchronization signal block and the synchronization signal block transmitted on demand are the same.
Need to check novelty before this filing date? Find Prior Art

Description

Terminal

[0001] The present invention relates to a terminal in a communication system.

[0002] In NR (New Radio, also referred to as "5G"), which is a radio communication system based on the 3GPP (registered trademark) standard, and systems succeeding NR (for example, "6G"), technologies that satisfy requirements such as large system capacity, high data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are under study.

[0003] In NR, a network architecture including 5GC (5G Core Network) corresponding to EPC (Evolved Packet Core), which is the core network in the LTE (Long Term Evolution) network architecture, and NG-RAN (Next Generation - Radio Access Network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the LTE network architecture, is under study (for example, Non-Patent Document 1).

[0004] In 3GPP Rel-19, in the working item related to NES (Network Energy Saving), adaptation of a Synchronization Signaling Block (SSB) in the time domain and the like are discussed as items related to common signal / channel transmission (for example, Non-Patent Document 2).

[0005] 3GPP TS 38.300 V18.5.0 (2025-03) "New WID: Enhancements of network energy savings for NR ", RP-234065, 3GPP TSG RAN Meeting #102, December 2023 3GPP TS 38.211 V18.6.0 (2025-03) 3GPP TS 38.331 V18.5.0 (2025-03) 3GPP TS 38.213 V18.6.0 (2025-03)

[0006] In 3GPP Rel-19, working items related to Network Energy Saving (NES) include discussions on the adaptation of Synchronization Signaling Blocks (SSBs) in the time domain, as part of items related to common signal / channel transmission (see, for example, Non-Patent Document 2).

[0007] At the 120th meeting of 3GPP RAN1, discussions were held regarding the application of SSB in NES, including the relationship between always-on (AO) SSB and on-demand (OD) SSB, as well as the period of SSB transmitted based on instructions from Downlink Control Information (DCI).

[0008] However, at present, there are unclear points regarding the procedures for applying SSB to NES.

[0009] This invention has been made in view of the above points, and aims to clarify the procedure for synchronous signal blocking in saving network energy in wireless communication systems.

[0010] According to the disclosed technology, a terminal is provided having a receiving unit that receives a continuously transmitted synchronization signal block and an on-demand transmission synchronization signal block, which have the same or different center frequencies, and a control unit that assumes that some or all of the MIB (Master Information Block) information contained in the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block is the same, or that the types of the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block are the same.

[0011] According to the disclosed technology, procedures for synchronous signal blocking in network energy saving can be clarified in wireless communication systems.

[0012] This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (1). This figure shows an example configuration of a wireless communication system in an embodiment of the present invention (2). This is a sequence diagram illustrating an example of a random access procedure in an embodiment of the present invention. This is a diagram illustrating SSB in an embodiment of the present invention. This is a diagram illustrating PRACH settings in an embodiment of the present invention. This is a diagram illustrating agreements at 3GPP (RAN1 120th meeting). This is a diagram illustrating bit allocation information for SSB settings in an embodiment of the present invention. This is a diagram illustrating PDCCH-ConfigSIB1 in an embodiment of the present invention. This is a diagram illustrating MIB in an embodiment of the present invention. This is a diagram illustrating a set of resource blocks and slot symbols for the CORESET for the Type0-PDCCH search space set in an embodiment of the present invention. This is a diagram illustrating the positional relationship of the frequency domain between CORESET#0 and SSB (1) in an embodiment of the present invention. This is a diagram illustrating the positional relationship of the frequency domain between CORESET#0 and SSB (2) in an embodiment of the present invention. This is a diagram illustrating the positional relationship of the frequency domain between CORESET#0 and SSB (index=12-14) in an embodiment of the present invention. This is a figure showing Case 1 (Alt.1) in an embodiment of the present invention. This is a diagram illustrating Case 1 (Alt. 2) in an embodiment of the present invention. This is a diagram illustrating Case 2 (Alt. 1-1) in an embodiment of the present invention. This is a diagram illustrating Case 2 (Alt. 1-2) in an embodiment of the present invention. This is a diagram illustrating Case 2 (Alt. 2-1) in an embodiment of the present invention. This is a diagram illustrating Case 2 (Alt. 2-2) in an embodiment of the present invention. This is a diagram illustrating the agreements reached at the 3GPP (RAN1 120th bis meeting). This is a diagram illustrating the candidate position for SSB transmission start in an embodiment of the present invention. This is a diagram illustrating the minimum time gap value (d) in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of the base station 10 and network node 30 in an embodiment of the present invention. This is a diagram illustrating an example of the functional configuration of the terminal 20 in an embodiment of the present invention.This figure shows an example of the hardware configuration of a base station 10 and a terminal 20 in an embodiment of the present invention.

[0013] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0014] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies may be used as appropriate. However, such existing technologies may be, for example, existing LTE or existing NR, but are not limited to existing LTE or NR.

[0015] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

[0016] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).

[0017] Furthermore, in embodiments of the present invention, "configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured. Also, in the following description, " / " means "and / or" unless otherwise specified, or unless it is clear from the context that it has a different meaning.

[0018] Figure 1 shows an example configuration (1) of a wireless communication system according to an embodiment of the present invention. The wireless communication system according to an embodiment of the present invention includes a base station 10 and a terminal 20, as shown in Figure 1. Figure 1 shows one base station 10 and one terminal 20, but this is an example, and there may be multiple base stations 10 and terminals 20.

[0019] Base station 10 is a communication device that provides one or more cells and communicates wirelessly with terminal 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of OFDM (Orthogonal Frequency Division Multiplexing) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. Base station 10 transmits synchronization signals and system information to terminal 20. Synchronization signals are, for example, NR-PSS and NR-SSS. System information is transmitted, for example, in NR-PBCH and is also called broadcast information. Synchronization signals and system information may also be called SSB (SS / PBCH block). As shown in Figure 1, base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both the base station 10 and the terminal 20 can apply MIMO (Multiple Input Multiple Output) communication to DL or UL. Also, both the base station 10 and the terminal 20 may communicate via Carrier Aggregation (CA) through secondary cells (SCell) and primary cells (PCell). Additionally, the terminal 20 may communicate via Dual Connectivity (DC) through the primary cell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10.

[0020] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. As shown in Figure 1, Terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from the base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0021] Furthermore, various requirements are being considered for the next generation of 6G. For example, these requirements may include ultra-broadband communication, mission-critical communication, ultra-massive connection, universal coverage, intelligent connection, and ubiquitous sensing.

[0022] Furthermore, these requirements may include ultra-high-speed communication, large-capacity communication, ultra-wide coverage, ultra-low power consumption, cost reduction, ultra-low latency, ultra-high reliability communication, ultra-high connectivity, and sensing.

[0023] To meet these requirements, the new concept aims for extensibility (e.g., making it more effective for future use), ease of operation, customizability (e.g., making it easier to operate), and sustainability (e.g., cost reduction, a more robust configuration, and resilience). Furthermore, guaranteed communication, ensuring a minimum level of performance at all times, is being considered.

[0024] Figure 2 shows an example configuration (2) of a wireless communication system according to an embodiment of the present invention. Figure 2 shows an example configuration of a wireless communication system when DC (Dual connectivity) is performed. As shown in Figure 2, a base station 10A that will be an MN (Master Node) and a base station 10B that will be an SN (Secondary Node) are provided. Base stations 10A and 10B are each connected to the core network. Terminal 20 can communicate with both base station 10A and base station 10B.

[0025] A cell group provided by base station 10A, which is an MN (Mobile Network), is called an MCG (Master Cell Group), and a cell group provided by base station 10B, which is an SN (Mobile Network), is called an SCG (Secondary Cell Group). In a data center, an MCG consists of one PCell and one or more SCells, and an SCG consists of one PSCell (Primary SCG Cell) and one or more SCells.

[0026] (SSB in Existing Specifications) Note that SSB in existing specifications (existing SSB) may mean any of the following 1)-4), or any combination of 1)-4). 1) SSB configured in RRC signaling up to release 18. 2) SSB configured in servingCellConfigCommon configured in SIB1 or RRCReconfiguration. 3) Cell-defined SSB (CD SSB) or non-cell-defined SSB (NCD SSB). SSB configured as NCD-SSB in RRC signaling. 4) SSB placed on a sync raster or SSB placed elsewhere. 5) SSB configured in servingCellConfig under SCell configuration Note that on-demand SSB may mean any of the following 1)-13), or any combination of the following 1)-13). For example, it may mean an SSB triggered by any of the following 1)-13), or an SSB triggered by any combination of the following 1)-13), or it may mean an adaptation of an existing and / or new SSB, or it may be interpreted as an adaptation of an on-demand SSB. Note that " / " may be replaced with "and / or", "and", or "or". 1) An SSB that is notified with a different setting than the existing SSB mentioned above. 2) Triggering SSB transmission itself. Turning SSB transmission on or off. 3) Triggering SSB transmission at a certain period X, SSB transmission at or above a certain period X, or below a certain period X, or longer than a certain period X, or shorter than a certain period X, SSB transmission with a shorter period than the currently transmitted, currently set, or most recently received SSB by the UE, SSB transmission with a longer period than the currently transmitted, currently set, or most recently received SSB by the UE, or maintaining SSB transmission at the current period. Changing the SSB period. 4) Triggering / not transmitting a certain SS burst (or referred to as an SSB burst) (triggering SSB transmission at a certain occasion). It is also possible to trigger / not transmit multiple SSB bursts.Here, an SS burst (or SSB burst) is a set of SSBs transmitted within a half frame. 5) Triggering the transmission / not transmitting of an SS burst within a period (triggering an SSB transmission at a certain opportunity). Multiple SS bursts may be triggered to be transmitted / not transmitted. 6) A certain number of SSB transmissions / fewer SSB transmissions / more SSB transmissions / maintaining the current SSB transmission. Changing the SSB position or SSB index. 7) A certain number of SSB transmissions / fewer SSB transmissions / more SSB transmissions / maintaining the current SSB transmission. Changing the SSB position or SSB index. 8) Triggering a certain SSB. 9) Triggering an SSB with a different SSB index / position. 10) Triggering a certain SSB within a certain SS burst. 11) Triggering an SSB with a different SSB index / position within a given SS burst. 12) Triggering an SSB transmission that has a predetermined QCL (Quasi Co Location) relationship with a transmit beam / other RS. 13) Triggering an SSB transmission that has a predetermined QCL relationship with a transmit beam / other RS ​​used for each SSB with a different SSB index / position.

[0027] Note that the on-demand SSB may be replaced with on-demand SIB1, or it may be a CORESET (Control Resource Set) associated with the Type0-PDCCH CSS set to which the UE belongs, which is transmitted on demand or triggered by the UE.

[0028] (WI on NES in Rel-19) In 3GPP Rel-19, the working item on Network Energy Saving (NES) discusses the adaptation of a Synchronization Signaling Block (SSB) in the time domain as an item related to common signal / channel transmission (see, for example, Non-Patent Document 2).

[0029] (Initial Access Procedure) Figure 3 is a sequence diagram illustrating an example of a random access procedure in an embodiment of the present invention. In step S401, the UE performs PSS detection. The UE performs time and frequency synchronization and obtains a portion of the physical cell ID. In step S402, the UE performs SSS detection. The UE obtains a portion of the physical cell ID. In step S403, the UE performs PBCH-DMRS detection. The UE detects the SSB index or a portion of the SSB index within a 5ms half-frame. In step S404, the UE receives the PBCH. The UE obtains the SFN, the radio frame timing of the SSB index, settings necessary for obtaining the RMSI, and information indicating whether or not camp-on to the cell is possible. Steps S401 to S404 correspond to the operation of receiving the SS / PBCH block.

[0030] In step S405, the UE receives PDCCH, and in step S406, the UE receives SIB1-PDSCH. The UE obtains information related to cell settings, including PRACH settings, and initial access.

[0031] In step S407, the UE transmits Msg1 via PRACH. Msg1 is the first transmitted signal in the initial access procedure. In step S408, the UE receives PDCCH, and in step S409, it receives Msg2-PDSCH (RAR, Random Access Response). The UE obtains scheduling information (RAR UL grant) for TA, TC-RNTI, and Msg3.

[0032] In step S410, Msg3 is sent via PUSCH. The UE sends an RRC setup request including the UE-ID. In step S411, the UE receives Msg4-PDCCH, and in step S412, it receives Msg4-PDSCH. The UE performs collision resolution. If collision resolution is successful, TC-RNTI is used as C-RNTI. In step S413, the UE sends HARQ-ACK corresponding to Msg4 via PUCCH.

[0033] Figure 4 is a diagram illustrating SSB in an embodiment of the present invention. Compared to LTE, SSB in NR has a wider bandwidth and fewer symbols, from 6RB6 symbols to 20RB4 symbols. In addition, flexibility is improved, and longer period settings are possible than before, such as {5, 10, 20, 40, 80, 160} ms. Multiple candidate symbol positions can be set within a 5 ms half-wireless frame. For example, 4 can be set in the 0-3 GHz band, 8 in the 3-6 GHz band, and 64 in the 6-52.6 GHz band.

[0034] As shown in Figure 4, transmit beam sweeping is possible for SSB transmission. The same cell ID is used between SSBs, and the SSB index is unique. The SSB index determines the time domain position within a 5ms half-radio frame.

[0035] Figure 5 is a diagram illustrating the settings related to PRACH in an embodiment of the present invention. As shown in Figure 5, the existing specifications (Non-Patent Document 3) specify the settings related to PRACH.

[0036] (Examples) Procedures for synchronous signal blocking in network energy saving in wireless communication systems are described. Example 1 clarifies the relationship between always-on (AO) SSB and on-demand (OD) SSB in relation to SSB adaptation in NES. Example 2 clarifies the transmission start position of SSB transmitted based on instructions from Downlink Control Information (DCI).

[0037] (Example 1) At the 3GPP (RAN1 120th meeting), the relationship between AO-SSB and OD-SSB in the time domain was agreed upon as shown in Figure 6. The current agreement suggests that the values ​​of each parameter included in the PBCH payload may be the same between OD-SSB and AO-SSB, except for the SFN index and half-frame index. However, if the aforementioned parameters are constrained to have the same values ​​between OD-SSB and AO-SSB, it will create constraints on the types of SSBs used in OD-SSB and AO-SSB, leading to problems such as limiting the use cases for OD-SSB.

[0038] Figure 7 is a diagram illustrating the bit assignment information for SSB settings in an embodiment of the present invention. As shown in Figure 7, existing specifications define the bit assignments for each parameter in the SSB (SFN, PDCCH Config for SIB1, Cell Barring Information flag, SSB index, Half-frame bit, CRC bits, etc.).

[0039] Figure 8 is a diagram illustrating PDCCH-ConfigSIB1 in an embodiment of the present invention. As shown in Figure 8, the existing specification (Non-Patent Literature 4) defines PDCCH-ConfigSIB1, which is an Information Element (IE) that sets the control resource set (CORESET#0 (Control REsource SET#0)) and the search space (search space#0) during initial access.

[0040] Figure 9 is a diagram illustrating the MIB in an embodiment of the present invention. As shown in Figure 9, an MIB (Master Information Block) including PDCCH-ConfigSIB1 is defined in an existing specification (Non-Patent Literature 4).

[0041] Figure 10 is a diagram illustrating the set of resource blocks and slot symbols for a CORESET for a Type0-PDCCH search space set in an embodiment of the present invention. As shown in Figure 10, an existing specification (Non-Patent Literature 5) defines a set of index, the number of resource blocks (RBs) for the CORESET, the number of symbols, and the offset from the SSB containing the Type0-PDCCH.

[0042] Figure 11 is a diagram illustrating the positional relationship (1) between CORESET#0 and SSB in the frequency domain in an embodiment of the present invention. As shown in Figure 11, when the index in Figure 10 is from 0 to 5, the number of RBs in CORESET is 2 or 3, and the positional relationship between CORESET and SSB is in the frequency domain, separated by an offset of 0, 2, or 4. Here, for two SSBs, regardless of the offset value set, if the two SSBs overlap in the time domain, an overlap will also occur in the frequency domain, so it is necessary to define a CORESET#0 corresponding to each SSB.

[0043] Figure 12 is a diagram illustrating the positional relationship (2) in the frequency domain between CORESET#0 and SSB in an embodiment of the present invention. As shown in Figure 12, when the index in Figure 10 is 6 to 11, the number of RBs in CORESET is 1, 2, or 3, and the positional relationship between CORESET and SSB is in the frequency domain, separated by an offset of either 12 or 16. Here, for two SSBs (SSB1 and SSB2), regardless of the offset value, if the two SSBs overlap in the time domain, overlap will also occur in the frequency domain, so it is necessary to define a CORESET#0 corresponding to each SSB. Note that the positional relationship between CORESET and SSB in the time domain is set based on existing specifications (Tables 13-11 to 13-14 of Non-Patent Literature 5), so there is always no overlap.

[0044] FIG. 13 is a diagram for explaining (3) the frequency domain positional relationship between CORESET#0 and SSB in the embodiment of the present invention. As shown in FIG. 13, when the Index in FIG. 10 is 12 to 14, the number of RBs of the CORESET is 1, 2, or 3, and the CORESET and the SSB are in a frequency domain positional relationship separated by an Offset of 38. Here, by setting the offset of SSB2 such that the two SSBs (SSB1 and SSB2) do not overlap in the frequency domain (a new value may be assigned to the reserved index), even when the two SSBs overlap in the time domain, there is no influence due to resource overlap. Note that the positional relationship of CORESET and SSB in the time domain is always non-overlapping by performing setting based on existing specifications (Table 13-11 to Table 13-14 of Non-Patent Document 5).

[0045] (Method 1) Method 1 related to configuration of OD-SSB and AO-SSB will be described.

[0046] (Alt.1) When the center frequencies of OD-SSB and AO-SSB are the same (Alt.1-1) The base station 10 / terminal 20 may assume that part or all of the MIB information (such as parameter values) included in the received SSB is the same between OD-SSB and AO-SSB for the terminal 20 on which configuration related to OD-SSB is performed according to the configuration information related to OD-SSB (od-ssb-config). Here, the SSB received by the terminal 20 may be a CD (Cell Defining)-SSB that defines a cell, or may be an NCD (Non / Not Cell Defining)-SSB that does not define a cell.

[0047] In addition, the base station 10 / terminal 20 may assume that when the values of some parameters in the MIB are the same, any one of the following parameters or a combination of a plurality of parameters is the same: - Parameters in the downlink control channel configuration information (PDCCH-ConfigSIB1) related to SIB1 configuration - Parameters related to the (frequency) offset of SSB (k_ssb, ssb-subcarrierOffset) - Parameters in cell access restriction information (cellbarring information) - Other MIB parameters (for example, those shown in Information / field in FIG. 7) (Alt.1-2) The base station 10 / terminal 20 may assume that for the terminal 20 for which the configuration related to OD-SSB is performed by the configuration information related to OD-SSB (od-ssb-config), the SSB types for AO-SSB and OD-SSB are the same.

[0048] For example, neither AO-SSB nor OD-SSB is on the sync raster.

[0049] For example, both AO-SSB and OD-SSB are on the sync raster.

[0050] (Effects) In Alt.1-1, the degree of freedom in the type of SSB to be utilized is improved for AO-SSB and OD-SSB, making it possible to appropriately select an SSB corresponding to various use cases.

[0051] In Alt.1-2, by limiting the types of SSB to be utilized for AO-SSB and OD-SSB, it is possible to simplify procedures / processing related to configuration.

[0052] (Alt.2) When the center frequencies of OD-SSB and AO-SSB are different (Alt.2-1) The base station 10 / terminal 20 may assume that some or all of the MIB information (parameter values, etc.) included in the received SSB is the same for OD-SSB and AO-SSB, based on the configuration information for OD-SSB (od-ssb-config) used by the terminal 20 which has performed the OD-SSB configuration. Here, the SSB received by the terminal 20 may be a CD (Cell Defining)-SSB which defines a cell, or an NCD (Non Cell Defining)-SSB which does not define a cell.

[0053] Furthermore, if the values ​​of some MIB parameters are the same, the base station 10 / terminal 20 may assume that any one or more combinations of the following parameters are the same: ・Parameters in the downlink control channel (PDCCH-ConfigSIB1) related to the setting of SIB1 ・Parameters related to the (time / frequency) offset of the SSB (k_ssb, ssb-subcarrierOffset, etc.) ・Parameters in the cell access restriction information (cellbarring information) ・Other MIB parameters (for example, shown in Information / field in Figure 7) (Alt.2-2) The base station 10 / terminal 20 may assume that terminal 20 on which the OD-SSB setting has been executed has the same SSB type for AO-SSB and OD-SSB, based on the OD-SSB setting information (od-ssb-config). Here, the base station 10 / terminal 20 may assume that some or all of the aforementioned MIB parameters have the same value.

[0054] For example, neither AO-SSB nor OD-SSB are on a sync raster.

[0055] For example, both AO-SSB and OD-SSB reside on a sync raster.

[0056] Here, a sync raster is a defined frequency (grid) used when searching for SSB.

[0057] (Effects) Alt.2-1 improves the flexibility in the type of SSB used for AO-SSB and OD-SSB, making it possible to appropriately select an SSB that suits various use cases.

[0058] Alt.2-2 simplifies the setup procedures and processes for AO-SSB and OD-SSB by limiting the types of SSBs that can be used.

[0059] (Method 2) Method 2 regarding the configuration of OD-SSB and AO-SSB will be explained.

[0060] (Case 1) If the base station 10 / terminal 20 has different time and frequency positions for the control resource set (CORESET #0 for type0-PDCCH) for the downlink control channel during initial access, which is associated with AO-SSB and OD-SSB respectively, then the following Alt.1 or Alt.2 may be assumed.

[0061] (Alt.1) The setting information for the downlink control channel (PDCCH-ConfigSIB1) related to the setting of SIB1 is the same setting value. Figure 14 shows Case 1 (Alt.1) in an embodiment of the present invention. In Figure 14, the offset for AO-SSB (Offset RB for AO-SSB) and the offset for OD-SSB (Offset RB for OD-SSB) are set to the same offset value.

[0062] (Alt.2) The setting information for the downlink control channel (PDCCH-ConfigSIB1) related to the setting of SIB1 is a different setting value. Figure 15 shows Case 1 (Alt.2) in an embodiment of the present invention. In Figure 15, the offset for AO-SSB (Offset RB for AO-SSB) and the offset for OD-SSB (Offset RB for OD-SSB) may be set to different offset values. Also, the offset value for OD-SSB may be set to a different offset value than the value that can be referenced from the existing specification table.

[0063] (Case 2) The base station 10 / terminal 20 has the same time and frequency position for the control resource set (CORESET #0 for type0-PDCCH) for the downlink control channel during initial access, which is associated with AO-SSB and OD-SSB respectively, and the following Alt.1 or Alt.2 may be assumed.

[0064] Furthermore, in Case 2, terminal 20 with OD-SSB settings may be assumed to have the following characteristics: • If the center frequencies of AO-SSB and OD-SSB are different, the PDCCH-ConfigSIB1 values ​​associated with the two SSBs are different or the same. • The time and frequency positions in the control resource set (CORESET #0 for type0-PDCCH) for the downlink control channel during initial access, associated with AO-SSB and OD-SSB respectively, are the same or different. - When the time and frequency positions in the control resource sets (CORESET #0 for type0-PDCCH) for the downlink control channel during initial access, associated with AO-SSB and OD-SSB respectively, are the same or different, the method for determining the offset value between AO-SSB and (corresponding to AO-SSB) CORESET #0 for Type0-PDCCH, and between OD-SSB and (corresponding to O-SSB) CORESET #0 for Type0-PDCCH is one of the following Alt.1-1, Alt.1-2, Alt.2-1, and Alt.2-2.

[0065] (Alt.1) The downlink control channel (Type0-PDCCH) used for initial access is common to both AO-SSB and OD-SSB. Here, the base station 10 / terminal 20 may be assumed to be either Alt.1-1 or Alt.1-2 below.

[0066] (Alt.1-1) The offset value (in RB units) of AD-SSB and the offset value (in RB units) of OD-SSB are the same. Figure 16 shows Case 2 (Alt.1-1) in an embodiment of the present invention. In Figure 16, the OD-SSB offset (Offset RB for OD-SSB) may be the offset value from the upper end of the OD-SSB frequency domain to the lower end of CORESET#0. Alternatively, it may be the offset value from the upper end of CORESET#0 to the upper end of the OD-SSB frequency domain. Alternatively, it may be the offset value from the lower end of the OD-SSB frequency domain to the lower end of CORESET#0. Furthermore, the OD-SSB offset (Offset RB for OD-SSB) may be a positive or negative value.

[0067] (Alt.1-2) The offset value (in RB units) for AD-SSB and the offset value (in RB units) for OD-SSB are different values. Figure 17 shows Case 2 (Alt.1-2) in an embodiment of the present invention. In Figure 17, the OD-SSB offset (Offset RB for OD-SSB) may be the offset value from the upper end of the OD-SSB frequency domain to the lower end of CORESET#0. Alternatively, it may be the offset value from the upper end of CORESET#0 to the upper end of the OD-SSB frequency domain. Furthermore, the OD-SSB offset (Offset RB for OD-SSB) may be a positive or negative value.

[0068] (Alt.2) The downlink control channel (Type0-PDCCH) accessible from AO-SSB and OD-SSB is independent during initial access. Here, the base station 10 / terminal 20 may be assumed to be either Alt.2-1 or Alt.2-2 below.

[0069] (Alt.2-1) The offset value between the control resource set (CORESET#0) corresponding to AO-SSB and AO-SSB is the same as the offset value between the control resource set (CORESET#0) corresponding to OD-SSB and OD-SSB. Figure 18 shows Case 2 (Alt.2-1) in an embodiment of the present invention. In Figure 18, the OD-SSB offset (Offset RB for OD-SSB) may be the offset value from the upper end of the OD-SSB frequency domain to the lower end of CORESET#0. Alternatively, it may be the offset value from the upper end of CORESET#0 to the upper end of the OD-SSB frequency domain. Furthermore, the OD-SSB offset (Offset RB for OD-SSB) may be a positive or negative value.

[0070] (Alt.2-2) The offset value between the control resource set (CORESET#0) corresponding to AO-SSB and AO-SSB is different from the offset value between the control resource set (CORESET#0) corresponding to OD-SSB and OD-SSB. Figure 19 shows Case 2 (Alt.2-2) in an embodiment of the present invention. In Figure 19, the OD-SSB offset (Offset RB for OD-SSB) may be the offset value from the upper end of the OD-SSB frequency domain to the lower end of CORESET#0. Alternatively, it may be the offset value from the upper end of CORESET#0 to the upper end of the OD-SSB frequency domain. Furthermore, the OD-SSB offset (Offset RB for OD-SSB) may be a positive or negative value.

[0071] (Number of RBs for CORESET #0 for type0-PDCCH) The base station 10 / terminal 20 may assume that a value other than the existing values ​​(12, 24, 48, 96) (e.g., 6, 18, 36, 72, 108, 120) is set as the number of resource blocks (RBs) for the downlink control channel during initial access, corresponding to OD-SSB (CORESET #0 for type0-PDCCH).

[0072] Furthermore, the base station 10 / terminal 20 may assume that the frequency offset value between OD-SSB and the control resource set for the downlink control channel during initial access (CORESET #0 for type0-PDCCH) will be set to the following values ​​in addition to the values ​​in the existing table.

[0073] If the number of RBs in the control resource set is 12, then one or more integer values ​​from 0 to 11 or -1 to -11.

[0074] If the number of RBs in the control resource set is 24, then one or more integer values ​​between 0 and 23, or between -1 and -23.

[0075] If the number of RBs in the control resource set is 48, then one or more integer values ​​from 0 to 47 or -1 to -47.

[0076] If the number of RBs in the control resource set is 96, then one or more integer values ​​between 0 and 95, or between -1 and -95.

[0077] If the number of RBs in the control resource set is X (where X is an integer), then one or more integer values ​​from 0 to X, and from -1 to -(X-1).

[0078] (Example 2) At the 3GPP (RAN1 120th bis meeting), the following was agreed upon regarding the transmission start position of SSB transmitted based on instructions in the downlink control information (DCI), as shown in Figure 20. Based on this agreement, terminal 20, which receives an instruction (indication) regarding SSB adaptation in DCI format 2_9 in slot m, is expected to receive the first (potentially first transmitted) SSB in slot m+d or later. Here, d is the grace period (gap) between the instruction to adapt and the start of transmission.

[0079] On the other hand, the current agreement does not clarify which slot the first SSB that may be received will be transmitted in. For example, it is unclear whether the next indicated SSB is a candidate position based on the period before SSB adaptation or a candidate position based on the period after SSB adaptation. When the transmission slot is unclear, terminal 20 has to perform a blind search for the next SSB to be transmitted, which leads to an increased operational load.

[0080] Figure 21 is a diagram illustrating candidate positions for SSB transmission in an embodiment of the present invention. As shown in Figure 21, based on the current consensus interpretation, multiple candidate positions for SSB transmission can be considered. For example, if a period of 80ms is applied by the adaptation from a period of 20ms before the SSB adaptation is performed, after indication in slot m, there are eight possible candidates for the first SSB transmission in slot m+d and beyond, as shown in Alt.1 to Alt.8. If the offset for setting the SSB transmission position within the SSB transmission period is the SFN (System Frame Number) offset (SNF-offset), then Alt.1 to 8 correspond to SNF-offset = 0 to 7, respectively. Here, if the slot in which the SSB is transmitted is not clearly determined, terminal 20 needs to perform a blind search considering the possibilities for all candidates.

[0081] (Method 1) Regarding the assumption of the SSB transmission start position based on SFN-offset, the operation of terminal 20 in determining the transmission start position of the first SSB transmitted after SSB adaptation will be described.

[0082] (Alt.1) The base station 10 / terminal 20 may assume that terminal 20, which has been configured for SSB adaptation, will pre-configure the SFN-offset after the adaptation has been performed for SSB adaptation. Here, terminal 20 may receive information about the SFN-offset to be pre-configured from base station 10 and configure it in advance.

[0083] For example, terminal 20 may receive an indication regarding SSB adaptation in slot m at a predetermined location (e.g., cell A), and assume that in cell A or cell B to which SSB adaptation is applied, SSB is transmitted from slot m+d onward, starting from an adapted SSB transmission start position based on a pre-configured SFN-offset.

[0084] Alternatively, the base station 10 / terminal 20 may assume that the SFN-offset to be set during adaptation is defined (for example, specified in the specifications).

[0085] This eliminates the need for terminal 20 to change the SFN-offset value for each SSB adaptation.

[0086] (Alt.2) The base station 10 / terminal 20 may assume that the terminal 20, which has been configured for SSB adaptation, will set the SFN-offset when the adaptation is performed for SSB adaptation. Here, the terminal 20 may assume that the indication for SSB adaptation transmitted from the base station 10 includes configuration information for the SFN-offset to be set. Alternatively, configuration information for the SFN-offset used in existing specifications may be used. This makes it possible to reduce the amount of additional configuration information that needs to be defined.

[0087] For example, terminal 20 may set an SFN-offset when it receives an indication regarding SSB adaptation in slot m at a predetermined location (e.g., cell A), and assume that in cell A or cell B to which SSB adaptation is applied, SSB will be transmitted from the transmission start position of the adapted SSB based on the set SFN-offset, starting from slot m+d.

[0088] Furthermore, when the base station 10 / terminal 20 receives an indication regarding SSB adaptation, it may assume that the previously set SFN-Offset will be changed or not changed.

[0089] (Alt.3) The base station 10 / terminal 20 may assume that if a terminal 20 configured for SSB adaptation receives an indication for SSB adaptation in slot m at a predetermined location (for example, cell A), then in cell A or cell B to which SSB adaptation is applied, the first SSB after the application will be transmitted in slot m+d or later, in the [next / next-next / xth / pre-set number of SSB transmission opportunities] of the SSB transmission opportunity before the SSB adaptation was executed.

[0090] This makes it possible to apply SSB adaptation in a short amount of time.

[0091] (Alt.4) The base station 10 / terminal 20 may assume that, with respect to SSB adaptation, if terminal 20 configured for SSB adaptation receives an indication for SSB adaptation in slot m at a predetermined location (for example, cell A), the first SSB will be transmitted in cell A or cell B to which SSB adaptation is applied, at the first / Xth slot of the slots corresponding to the [SMTC (SSB based RRM (Radio Resource Management) Measurement Timing Configuration) period for SSB adaptation / configured SMTC period] from slot m+d onwards.

[0092] The base station 10 may transmit an indication regarding SSB adaptation along with an indication regarding the change in the SMTC period to the terminal 20, or it may transmit the two indications separately to the terminal 20. The base station 10 / terminal 20 may also assume that the change in the SMTC period is pre-configured or defined in the specifications. Furthermore, the base station 10 / terminal 20 may also assume that an information element (IE) for SSB adaptation is defined.

[0093] This eliminates the need to explicitly notify terminal 20 of the starting position of the SSB adaptation.

[0094] (Alt.5) The base station 10 / terminal 20 may assume that when a terminal 20 configured for SSB adaptation receives an indication for SSB adaptation in slot m at a predetermined location (for example, cell A), the first SSB will be transmitted in slot m+d in cell A or cell B to which SSB adaptation is applied.

[0095] This allows the starting position of the SSB to be identified in the implementation of terminal 20, thereby reducing the impact on existing specifications.

[0096] (Alt.6) A terminal 20 configured for SSB adaptation may assume that, when it receives an indication for SSB adaptation at a predetermined location (for example, cell A), in cell A or a predetermined cell B to which SSB adaptation is applied, an SSB will be transmitted from the transmission start position of the adapted SSB, based on the SFN-offset value known in advance by the terminal 20, after m+d slots following the receipt of the indication. Here, the terminal 20 can obtain the SFN number to which the SSB is being transmitted from the MIB value in advance and determine the SFN-offset based on that number.

[0097] (Alt.7) The base station 10 / terminal 20 may assume that, when an SSB adaptation is performed on a terminal 20 that has been configured for SSB adaptation, if an SFN-offset is set, the SSB will be transmitted from the transmission start position of the adapted SSB based on the set SFN-offset value, and if an SFN-offset is not set, the SSB will be transmitted from the transmission start position of the adapted SSB based on the SFN-offset value known in advance by the UE.

[0098] Alt.1 to Alt.7 may be applied individually or in combination. Also, cells A and B in Alt.1 to Alt.7 may be PCell / SCell / PSCell / sPCell / Serving Cell.

[0099] (Method 2) The method for determining the processing time of terminal 20 will be described below.

[0100] The base station 10 / terminal 20, upon receiving an indication regarding SSB adaptation based on downlink control information (e.g., DCI format 2_9) in slot m, may assume that the first possible SSB will be transmitted in slot m+d and beyond. Here, d is the slot level value, which may be the value shown in Figure 22.

[0101] Figure 22 is a diagram illustrating the minimum time gap value (d) in an embodiment of the present invention. In Figure 22, " / " means either or, and it may be assumed that one of the values ​​is specified. Alternatively, a value specified in an existing specification (Table 11.5-1 of Non-Patent Document 5) may be used.

[0102] (Example 3) At the RAN1#120bis meeting, it was agreed that a single CSI report configuration could be linked to either both AO-SSB and OD-SSB, or only OD-SSB. In particular, in the former case (linking both AO-SSB and OD-SSB), the choice of which SSB to use when performing measurements was left to the UE implementation. However, if timeRestrictionForChannelMeasurement is set in CSI-ReportConfig, the network and UE need to have a common understanding of which SSB to use. Therefore, if the UE implementation decides which SSB to use for measurement, it becomes impossible for the network and UE to have a common understanding. Thus, in this example, the above problem is solved by clarifying which SSB to use on the network and UE sides.

[0103] (Method 1) Proposal for UE behavior related to L1-SINR reporting when timeRestrictionForChannelMeasurement is set.

[0104] Terminal 20, in which one or two resource settings are configured for L1-SINR measurement, may be expected to behave as follows:

[0105] If timeRestrictionForChannelMeasurements is set to "configured", terminal 20, which has OD-SSB-related settings provided by od-ssb-config, etc., derives channel measurements for calculating the L1-SINR reported in uplink slot n, based only on opportunities when (A) and (B) are not slower than the CSI reference resource, as shown below.

[0106] (A) may be any or a combination of the following: • Case #1 • Case #2 • When the center frequencies of AO-SSB and OD-SSB are equal • When the center frequencies of AO-SSB and OD-SSB are different • When there is an assumption of QCL between AO-SSB and OD-SSB • The union of AO-SSB and OD-SSB is periodic • The union of AO-SSB and OD-SSB is non-periodic

[0107] (B) may be: - Only at the latest opportunity of the AO-SSB or OD-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the latest CSI reference resource; - Only at the latest opportunity of either the AO-SSB or OD-SSB associated with the CSI resource setting, or the latest NZP CSI-RS, no later than the latest CSI reference resource; - Only at the latest opportunity of either the AO-SSB or OD-SSB associated with the CSI resource setting, or the latest NZP CSI-RS, no later than the latest CSI reference resource; - Only at the latest opportunity of the AO-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the latest CSI reference resource; - Only at the latest opportunity of the OD-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the latest CSI reference resource; - The OD-SSB transmission indication is [MAC If instructed by [CE / RRC / DCI], only the latest opportunity of the OD-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the CSI reference resource; otherwise, only the latest opportunity of the AO-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the CSI reference resource; if the parameter for the indicator, such as the SSB indicator set in CSI-ReportConfig, is OD-SSB, only the latest opportunity of the OD-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the CSI reference resource; if AO-SSB, only the latest opportunity of the AO-SSB or NZP CSI-RS associated with the CSI resource setting, no later than the CSI reference resource; if absent (i.e., not set), only the latest opportunity of either the AO-SSB or OD-SSB associated with the CSI resource setting, or the latest opportunity of the NZP CSI-RS, no later than the CSI reference resource.

[0108] (Method 2) Proposed UE behavior related to L1-SINR reporting when timeRestrictionForChannelMeasurement is not set

[0109] A terminal 20 with one or two resource settings configured for L1-SINR measurement may be expected to behave as follows:

[0110] If timeRestrictionForChannelMeasurements is set to "notconfigured", terminal 20, which has OD-SSB-related settings provided by od-ssb-config, etc., derives channel measurements for calculating the L1-SINR reported in uplink slot n, based only on the occasions when (A) (B) it is not slower than the CSI reference resource.

[0111] (A) may be any or a combination of the following: • Case #1 • Case #2 • When the center frequencies of AO-SSB and OD-SSB are equal • When the center frequencies of AO-SSB and OD-SSB are different • When there is an assumption of QCL between AO-SSB and OD-SSB • The union of AO-SSB and OD-SSB is periodic • The union of AO-SSB and OD-SSB is non-periodic

[0112] (B) may be: - Only at times when the AO-SSB or OD-SSB or NZP CSI-RS associated with the CSI resource setting is no slower than the CSI reference resource; - Only at times when either the AO-SSB or OD-SSB or NZP CSI-RS associated with the CSI resource setting is no slower than the CSI reference resource; - Only at times when either the AO-SSB or OD-SSB or NZP CSI-RS associated with the CSI resource setting is no slower than the CSI reference resource; - Only at times when the AO-SSB or NZP CSI-RS associated with the CSI resource setting is no slower than the CSI reference resource; - Only at times when the OD-SSB or NZP CSI-RS associated with the CSI resource setting is no slower than the CSI reference resource; - If the OD-SSB transmission indication is indicated by [MAC CE / RRC / DCI], the OD-SSB or NZP CSI-RS associated with the CSI resource setting, Only opportunities that are not slower than the CSI reference resource; otherwise, only opportunities that are not slower than the CSI reference resource for AO-SSB or NZP CSI-RS associated with the CSI resource setting; if the parameter for the indicator shown by the SSB indicator etc. set in CSI-ReportConfig is OD-SSB, only opportunities that are not slower than the CSI reference resource for OD-SSB or NZP CSI-RS associated with the CSI resource setting; if it is AO-SSB, only opportunities that are not slower than the CSI reference resource for AO-SSB or NZP CSI-RS associated with the CSI resource setting; if it is absent (i.e., not set), only opportunities that are not slower than the CSI reference resource for either AO-SSB or OD-SSB or NZP CSI-RS associated with the CSI resource setting.

[0113] (Explanation of terms)

[0114] The following explains the terminology related to the above-mentioned examples.

[0115] The specified period may be any of the following, or it may be determined based on specified parameters set by BS.

[0116] The prescribed period may be a period of a predetermined time width from a predetermined reference point. The prescribed reference point may be a reference time (SFN (System Frame Number), slot number, symbol number) set from the time of transmission / reception of a predetermined DL / UL signal and / or from the BS.

[0117] The units in the time direction may also be symbols, slots, wireless frames, system frames, sub-milliseconds, milliseconds, or seconds.

[0118] The predetermined time window is defined by parameters and / or specifications set by the BS and / or determined according to the UE capability, or it may be after a certain delay (application delay, processing delay).

[0119] The predetermined time window is defined by parameters and / or specifications set by BS, and / or determined according to UE capability, and / or varies depending on SCS, and / or varies depending on the UE's Timing Advanced value, and / or may be a time window from a reference point, or from a reference point and / or after a certain delay (application delay, processing delay).

[0120] UE may take a minimum value (using a smaller value) or a maximum value (using a larger value) from a predetermined value to determine a predetermined period. The predetermined value may be 1 symbol / 1 slot / 1 millisecond, or it may be a value determined below.

[0121] A value determined by parameters and / or specifications set by the BS and / or determined by the UE's capability and / or differing by the SCS.

[0122] The specified cell in BS may be any of the following: SpCell, PCell, PSCell during DC, active SCell, or Cell that satisfies the specified conditions.

[0123] UE can be in any of the following states: idle, inactive, or RRCconnected, and different actions may be performed depending on the UE state.

[0124] A UE may correspond to and / or report predetermined functions / operations within a predetermined UE capability. The predetermined UE capability may be set at any of the following granularities: UE, FR1, FR2, FR2-1, FR2-2, SCS, band, band combination, feature combination, and / or FSPC unit; or UE, Cell, TDD, FDD unit.

[0125] The specified settings / notifications may be any of the following:

[0126] Configuration / notification may be performed via RRC, MAC-CE, or DCI, and a parameter list configured / notified via RRC, MAC-CE, or DCI may be associated with an identifier (index), and the identifier may be notified to the UE by another notification (MAC-CE, DCI), allowing the UE to determine which parameter lists are activated / applied / used (deactivated, not applied, used).

[0127] Identifiers may be implicitly associated by the order of the list set in the RRC, or they may be associated by explicitly assigning a number.

[0128] The UE may respond to any of the signals with a response signal (NACK, ACK, feedback, retransmission request).

[0129] UE may have multiple parameter lists set, modified, and released by RRC as "AddModlist" and / or "releaselist".

[0130] Settings / notifications may be made via SI / SIB RRC messages, or via individual UE RRC messages (e.g., RRCReconfiguration) for UEs that are connected via RRC.

[0131] Dedicated RRC configuration / RRC release / RRC setup may also be configured / notified.

[0132] The dedicated RRC configuration / RRC release / RRC setup for SS / PBCH / SIB1 / SIBX / one / multiple cells / bands / carriers may be configured / notified.

[0133] The SS / PBCH / SIB1 / SIBX / dedicated RRC configuration / RRC release / RRC setup of one or more cells / bands / carriers may be configured / notified.

[0134] The SS / PBCH / SIB1 / SIBX of one or more cells / bands / carriers may be configured / notified as a dedicated RRC configuration / RRC release / RRC setup.

[0135] The setting / notification may be a predetermined DCI format scrambled with X-RNTI, and X-RNTI may be NES-RNTI, SI-RNTI, or not limited to these, and may also be a new DCI format and / or RNTI.

[0136] For all parameters, the UE may perform default values / actions when not set / notified by the BS, and the default actions may include: • Perform no action • Repeat the previous action • Perform RRC Release / RRC Re-establishment • Send a predetermined notification to the BS • Send a predetermined notification to the UE's upper layer. The default values ​​may include: • Always 0 / 1 • The value used most recently • The value that was set / notified most recently • A value (pre-)defined in the specification • A parameter value from another setting / notification • A predetermined timer value

[0137] Furthermore, for all UE actions #A, the UE may perform a default action #B if a particular action #A could not be performed.

[0138] The above-described embodiment clarifies the procedure for synchronous signal blocking in network energy saving in a wireless communication system.

[0139] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include functions to implement the above-described embodiment. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0140] <Base Station 10 and Network Node 30> Figure 23 is a diagram showing an example of the functional configuration of a base station 10 and a network node 30 in an embodiment of the present invention. As shown in Figure 23, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 23 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0141] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0142] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The content of the setting information includes, for example, information related to the operation described in the embodiment.

[0143] The control unit 140 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.

[0144] <Terminal 20> Figure 24 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 24, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 24 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.

[0145] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to the operation described in the embodiment.

[0146] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.

[0147] (Hardware Configuration) The block diagrams (Figures 23 and 24) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0148] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 25 is a diagram showing an example of the hardware configuration of a base station and a terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

[0149] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.

[0150] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.

[0151] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit 104 and call processing unit 105 described above may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.

[0152] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.

[0153] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).

[0154] The memory 1002 is a computer-readable recording medium and may be composed of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or at least a combination of these. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of the present disclosure.

[0155] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., card, stick, key drive), a floppy® disk, a magnetic strip, or a combination of at least two of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.

[0156] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, the above-mentioned transmit / receive antenna 101, amplifier unit 102, transmit / receive unit 103, or transmission path interface 106 may be implemented by the communication device 1004. The transmit / receive unit 103 may be implemented with physically or logically separated transmitting unit 103a and receiving unit 103b.

[0157] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0158] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0159] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0160] O-CU may be interpreted as CU, control device, communication device, aggregation device, central device, management device, etc. Each of these devices may be rephrased as a unit, node, etc. For example, O-CU may be interpreted as a central unit, aggregation node, etc.

[0161] O-DU may be interpreted as DU, control device, communication device, distributed device, high-PHY device, etc. Each of these devices may be rephrased as unit, node, etc. For example, O-DU may be interpreted as distributed unit, distributed node, etc.

[0162] O-RU may be interpreted as RU, radio equipment, RF (Radio Frequency) equipment, low PHY equipment, etc. Each piece of equipment may be rephrased as a unit, node, etc. For example, O-RU may be interpreted as a radio unit, radio node, etc.

[0163] SMO may be interpreted as a control device, communication device, or management device. Each of these devices may be rephrased as a unit, node, etc. For example, SMO may be interpreted as a management unit, management node, etc.

[0164] Non-Real Time RIC may be interpreted as RIC, non-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0165] Near-Real Time RIC may be interpreted as RIC, quasi-real-time control device, control device, or communication device. Each of these devices may be rephrased as a unit, node, etc. For example, Non-Real Time RIC may be interpreted as a control unit, control node, etc.

[0166] <Configuration relating to this embodiment> (Note 1) A terminal having: a receiving unit that receives a continuously transmitted synchronization signal block and an on-demand transmission synchronization signal block having the same or different center frequencies; and a control unit that assumes that some or all of the MIB (Master Information Block) information contained in the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block is the same, or that the types of the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block are the same. (Note 2) A terminal having: a receiving unit that receives a continuously transmitted synchronization signal block and an on-demand transmission synchronization signal block; and a control unit that assumes that when the time and frequency positions of the control resource sets for the downlink control channel at initial access are different, the setting information for the downlink control channel relating to the setting of SIB1 (System Information Block1) is the same or different setting values, associated with the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block, respectively.(Note 3) A terminal having: a receiving unit that receives a continuously transmitted synchronization signal block and a synchronization signal block transmitted on demand; and a control unit that assumes that the offset values ​​set in the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block are the same or different when the time and frequency positions of the control resource sets for the downlink control channel at initial access, associated with the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block, respectively, are the same, and the downlink control channel at initial access, accessible from the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block, is the same or different, or the offset value between the control resource set corresponding to the continuously transmitted synchronization signal block and the continuously transmitted synchronization signal block, and the offset value between the control resource set corresponding to the on-demand transmission synchronization signal block and the on-demand transmission synchronization signal block are the same or different. (Note 4) A terminal having: a receiving unit that receives instructions for adaptation regarding a synchronization signal block; a control unit that sets an offset value that specifies the position of the first synchronization signal block to be transmitted after the adaptation is performed, either in advance or when the instruction is received; and a receiving unit that receives the first synchronization signal block to be transmitted after the adaptation is performed based on the offset value. (Note 5) A terminal having: a control unit that assumes the position of the first synchronization signal block to be transmitted after the adaptation is performed is an SSB transmission opportunity that is a number of times later than the transmission opportunity of the synchronization signal block before the adaptation is performed; and a receiving unit that receives the first synchronization signal block to be transmitted after the adaptation is performed based on the assumption.(Note 6) A terminal having: a control unit that assumes the position of the first synchronization signal block transmitted after an adaptation to the synchronization signal block has been performed is the first slot position indicated in the SMTC (SSB based RRM (Radio Resource Management) Measurement Timing Configuration) period relating to the adaptation; and a receiving unit that receives the first synchronization signal block transmitted after the adaptation has been performed based on the assumption.

[0167] Any of the above configurations can clarify the procedure for synchronous signal blocking in network energy saving in a wireless communication system.

[0168] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0169] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.

[0170] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base Station", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point (AP)", "Transmission Point (TP)", "Reception Point (RP)", "Transmission / Reception Point (TRP)", "Radio Unit (RU)", "Remote Unit (RU)", "Control Unit (CU)", "Distributed Unit (DU)", "Remote Radio Head (RRH)", "Node", "Gateway", "Ground Base Station", "Stratospheric Base Station", "Unmanned Aerial Vehicle", "High Altitude Platform Station (HAPS)", "Airborne Platform", "Panel", "Cell", "Radio Access Network (RAN)", and "Network" may be used interchangeably.

[0171] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.

[0172] In this disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "module", and "Terminal" may be used interchangeably.

[0173] The terminal may be called a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other appropriate term.

[0174] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0175] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be interpreted as a sidelink channel.

[0176] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).

[0177] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.

[0178] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.

[0179] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.

[0180] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).

[0181] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."

[0182] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution.

[0183] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.

[0184] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0185] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.

[0186] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.

[0187] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.

[0188] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.

[0189] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0190] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.

[0191] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.

[0192] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0193] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0194] This patent application claims priority based on Japanese Patent Application No. 2025-078983, filed on 9 May 2025, and the entire contents of Japanese Patent Application No. 2025-078983 are incorporated herein by reference.

[0195] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims

A receiving unit that receives a continuously transmitted synchronization signal block with the same or different center frequencies, and a synchronization signal block transmitted on demand. It is assumed that some or all of the MIB (Master Information Block) information contained in the continuously transmitted synchronization signal block and the on-demand transmitted synchronization signal block are the same. Alternatively, a control unit that assumes that the continuously transmitted synchronization signal block and the on-demand transmitted synchronization signal block are of the same type, A terminal.   A receiving unit that receives a synchronization signal block that is transmitted continuously and a synchronization signal block that is transmitted on demand, A control unit that assumes that the setting information for the downlink control channel related to the settings of SIB1 (System Information Block1) is the same or different if the time and frequency positions of the control resource sets for the downlink control channel at initial access are different, associated with the continuously transmitted synchronization signal block and the on-demand transmitted synchronization signal block, respectively, A terminal.   A receiving unit that receives a synchronization signal block that is transmitted continuously and a synchronization signal block that is transmitted on demand, The time and frequency positions of the control resource sets for the downlink control channel at initial access, associated with the continuously transmitted synchronization signal block and the on-demand transmission synchronization signal block, respectively, are the same. If the downlink control channel accessible from the continuously transmitted synchronization signal block and the on-demand synchronization signal block is the same, It is assumed that the offset values ​​set in the continuously transmitted synchronization signal block and the on-demand transmitted synchronization signal block are the same or different, or The offset value between the control resource set corresponding to the continuously transmitted synchronization signal block and the continuously transmitted synchronization signal block, A control unit assumes that the offset value between the control resource set corresponding to the on-demand transmitted synchronization signal block and the on-demand transmitted synchronization signal block is the same or different. A terminal.   A receiving unit that receives instructions for adaptation regarding the synchronization signal block, A control unit that sets an offset value that specifies the position of the first synchronization signal block transmitted after the above adaptation has been performed, or sets the offset value when the above instruction is received. A receiving unit that receives the first synchronization signal block transmitted after the adaptation is performed based on the offset value, A terminal.   A control unit that assumes the position of the first synchronization signal block to be transmitted after an adaptation to the synchronization signal block has been performed is an SSB transmission opportunity that is a predetermined number of times later than the transmission opportunities of the synchronization signal block before the adaptation was performed, Based on the above assumption, a receiving unit receives the first synchronization signal block transmitted after the above adaptation has been performed, A terminal.   A control unit that assumes the position of the first synchronization signal block transmitted after an adaptation to the synchronization signal block has been performed is the first slot position indicated in the SMTC (SSB based RRM (Radio Resource Management) Measurement Timing Configuration) period for the adaptation, Based on the above assumption, a receiving unit receives the first synchronization signal block transmitted after the above adaptation has been performed, A terminal.