Method and apparatus for on-demand synchronization signal and physical broadcast channel block operation in mobile communications

Abstract

Various solutions are described for on-demand synchronization signal and physical broadcast channel block (SSB) operation for user equipment (UE) and network apparatus in mobile communications. A UE can detect an SSB from a cell. The UE can determine whether the SSB is a non-cell-defining (NCD) SSB. The UE can search for another SSB for synchronization if the SSB is an NCD SSB. The NCD SSB is an on-demand SSB on the cell. By identifying on-demand SSBs, UEs that do not support on-demand SSBs can be prevented from performing a random-access channel (RACH) procedure based on an on-demand SSB.

Description

[0001] Cross-references

[0002] This disclosure is part of a non-provisional application claiming priority to U.S. Patent Application No. 63 / 572,979 (filed April 2, 2024), the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically to the operation of on-demand synchronization signal and physical broadcast channel block (SSB) for user equipment and network devices in mobile communications. Background Technology

[0004] Unless otherwise stated, the methods described in this section are not prior art to the following claims and are not recognized as prior art because they are included in this section.

[0005] In the current fifth-generation (5G) New Radio (NR) specification, the synchronization signal and physical broadcast channel block (SSB) are always configured as periodic signals via radio resource control (RRC) signaling. Specific SSB configuration details can be extracted from system information block 1 (SIB1) through their information elements (IEs). The configurable period of a periodic SSB ranges from 5 to 160 milliseconds (ms), with selectable values ​​of 5, 10, 20, 40, 80, or 160 ms. Furthermore, one or more periodic SSBs can be combined in the time domain to form an SSB burst. Each periodic SSB in this burst is aligned with a specific transmit beam direction in the time domain. This type of SSB is also known as a resident SSB.

[0006] In addition to resident SSBs, 3GPP Release 19 introduced on-demand SSBs in secondary cells (SCells). On-demand SSBs for SCells can be used at least for time / frequency synchronization of SCells in cross-band carrier aggregation (CA) without SSBs, and to promote SCell activation. To promote SCell activation, on-demand SSBs can be triggered to temporarily fill more SSB bursts within an SSB burst cycle, thereby reducing significant SCell activation delays.

[0007] For user equipment (UE) performing the initial cell search, it searches for SSBs on the synchronization grid. Since on-demand SSBs are only transmitted temporarily, it is necessary to ensure that on-demand SSBs are not used for the initial cell search. However, for UEs that do not support 3GPP Release 19 (i.e., legacy UEs prior to Release 19), on-demand SSBs are not supported. Such legacy UEs cannot recognize on-demand SSBs and do not know how to handle them.

[0008] Therefore, how to handle on-demand SSB for traditional UEs has become an important issue in the development of new wireless communication networks. Thus, it is necessary to provide UEs with appropriate on-demand SSB operation schemes. Summary of the Invention

[0009] The following abstract is for illustrative purposes only and is not intended to be limiting in any way. That is, the following abstract aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Some embodiments will be further described in the detailed description below. Therefore, the following abstract is not intended to identify the essential features of the claimed subject matter, nor is it intended to determine the scope of the claimed subject matter.

[0010] One objective of this disclosure is to provide a solution or scheme for the aforementioned problems of UE and network devices regarding on-demand SSB operation in mobile communications.

[0011] In one aspect, a method may include a device detecting an SSB from a cell. The method may further include the device determining whether the SSB is an NCD SSB. If the SSB is an NCD SSB, the device may further include searching for another SSB for synchronization. The NCD SSB is an on-demand SSB on the cell.

[0012] In one aspect, a method may include a device detecting an SSB from a cell. The method may further include the device determining whether a cell prohibition parameter in the MIB of the SSB is set to prohibition. If the cell prohibition parameter is set to prohibition, the device may further include searching for another SSB for synchronization. This SSB is an on-demand SSB on the cell.

[0013] In one aspect, an apparatus may include a transceiver that wirelessly communicates with a network node during operation. The apparatus may also include a processor communicatively connected to the transceiver. Operations that the processor may perform during operation include detecting an SSB from a cell via the transceiver. Further operations that the processor may perform include determining whether the SSB is an NCD SSB. If the SSB is an NCD SSB, further operations that the processor may perform include searching for another SSB via the transceiver for synchronization. The SSB is an on-demand SSB on the cell.

[0014] It is worth noting that although the content described herein may be presented in the context of certain wireless access technologies, networks, and network topologies, such as LTE, LTE-Advanced, LTE-Advanced Pro, 5G, NR, 5G-Advanced, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Beyond 5G (B5G), and 6th Generation (6G), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, used, and implemented by other types of wireless access technologies, networks, and network topologies. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0015] The accompanying drawings are intended to further understand this disclosure and are incorporated into and constitute a part of this disclosure. The drawings illustrate embodiments of the disclosure and, in conjunction with the description, are used to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0016] Figure 1 This is a schematic diagram illustrating the various solutions and implementation examples in communication environments described in this disclosure.

[0017] Figure 2This is a schematic diagram illustrating an example scenario of the frequency domain structure of the SSB in an embodiment of this disclosure.

[0018] Figure 3 This is a schematic diagram illustrating an example scenario of the frequency domain location of SIB1 in an embodiment of this disclosure.

[0019] Figure 4 This is a schematic diagram illustrating an example scenario of the MIB message format in an embodiment of this disclosure.

[0020] Figure 5 This is a block diagram describing an example communication system in an embodiment of this disclosure.

[0021] Figure 6 This is a flowchart describing an example process in an embodiment of this disclosure.

[0022] Figure 7 This is a flowchart describing another example process in an embodiment of this disclosure. Detailed Implementation

[0023] Detailed embodiments and implementations of the subject matter of the claims are disclosed herein. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the subject matter of the claims and may be implemented in various forms. This disclosure may take many different forms and should not be construed as limited to the exemplary embodiments and implementations listed herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully communicate the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0024] Overview

[0025] According to embodiments of this disclosure, various techniques, methods, schemes, and / or solutions relate to on-demand synchronization signal and physical broadcast channel block (SSB) operation in mobile communications, which can ensure the correct operation of the UE. According to this disclosure, several possible solutions can be implemented individually or in combination. That is, although these possible solutions are described separately below, two or more of them can be implemented in some combination.

[0026] Figure 1Scenario 100 is illustrated exemplarily in a communication environment in which various solutions and schemes of this disclosure can be implemented. Scenario 100 involves a UE 110 communicating wirelessly with a wireless network (e.g., a 5G NR or 6G network) consisting of an access network 120 and a core network 130. The UE 110 may be a smartphone, wearable device, IoT device, tablet, etc. Alternatively, the UE 110 may be a notebook (NB) or personal computer (PC) with a data card inserted or installed (the data card includes a modem and a radio frequency (RF) transceiver to provide wireless communication capabilities). In 5G NR, the access network 120 is connected to the core network 130 via an NG interface, and more specifically, to the user plane function (UPF) via the NG user-plane part (NG-u) and to the mobility management function (AMF) via the NG control-plane part (NG-c). A base station (BS) (such as a next-generation Node-B (gNB)) can connect to multiple UPFs / AMFs to achieve load balancing and redundancy. In addition, the core network may include other entities such as session management functions (SMFs) and unified data management (UDMs). Access network 120 may include multiple base stations (e.g., BS 121), each providing communication coverage for a geographically defined area (e.g., a cell) supporting communication with UE 110 within that area.

[0027] For base stations supporting on-demand SSBs (e.g., BS 121), they can be configured / triggered to broadcast on-demand SSB 140. Since the purpose of on-demand SSBs is for measurement assistance in synchronization and SCells, triggered on-demand SSBs should be correctly identified and used by the UE. In one embodiment, an on-demand SSB can be identified as a non-cell-defining (NCD) SSB, while a resident SSB can be identified as a cell-defining (CD) SSB. Specifically, a CD SSB is an SSB associated with remaining minimum system information (RMSI). The RMSI includes system information block 1 (SIB1). An NCD SSB is an SSB without an RMSI. That is, a CD SSB may include the associated Type 0 (Type 0) - physical downlink control channel (PDCCH) common search space (CSS) set, while an NCD SSB does not include the associated Type 0 - PDCCH CSS set. The Type 0-PDCCH CSS set is the control channel associated with SIB1. The UE can locate SIB1 based on the Type 0-PDCCH CSS set. By identifying the type of SSB, the UE can correctly execute the corresponding procedures.

[0028] Specifically, the UE can detect the SSB from the cell. The UE can determine whether the SSB is an NCD SSB or a CD SSB. That is, an NCD SSB is an on-demand SSB on the cell, and a CD SSB is a resident SSB on the cell. For UEs that do not support on-demand SSBs, if the SSB is an NCD SSB, the UE can be configured to search for / find another SSB for synchronization. If the SSB is a CD SSB, the UE can be configured to detect the SIB1 associated with that CD SSB. The UE can then perform a random-access channel (RACH) procedure based on that SIB1. Therefore, it is possible to prevent UEs that do not support on-demand SSBs from performing RACH procedures using on-demand SSBs.

[0029] When determining whether an SSB is an NCD SSB, the UE can determine the subcarrier offset (e.g., The UE determines whether the subcarrier offset is greater than or equal to a first value (e.g., 24) for frequency range 1 (FR1) or a second value (e.g., 12) for frequency range 2 (FR2). If the subcarrier offset is greater than or equal to the first value of FR1 or greater than or equal to the second value of FR2, the UE can determine that the SSB is an NCD SSB. In determining whether the SSB is a CD SSB, the UE can determine the subcarrier offset (e.g., ...). Whether the subcarrier offset is less than the first value of FR1 or less than the second value of FR2. If the subcarrier offset is less than the first value of FR1 or less than the second value of FR2, the UE can determine that the SSB is a CD SSB. Subcarrier offset (e.g., The parameters can be carried in the master information block (MIB) of the SSB.

[0030] Figure 2 A scenario 200 of the frequency domain structure of an SSB according to an embodiment of the present disclosure is illustrated exemplarily. The SSB may include a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The absolute frequency position may indicate the middle of the SSB 210 (i.e., absoluteFrequencySSB). The relative frequency position is relative to a reference frequency point A and may include one or a combination of OffsetToPointA, Kssb, and absoluteFrequencyPointA. It comes from the common resource block (CRB). The subcarrier offset from subcarrier 0 to the subcarrier with the smallest SSB number. It can be used to determine the location of control resource set (CORESET) 0, and this parameter is required for CD-SSB.

[0031] Figure 3An example scenario 300 of the frequency domain location of SIB1 according to an embodiment of this disclosure is illustrated. CORESET 0 is a special type of control resource set (CORESET) that carries PDCCH / downlink control information (DCI) for SIB1. The resource allocation of CORESET 0 (i.e., time-domain and frequency-domain resource allocation) is configured by the MIB (i.e., PBCH in the SSB). The starting position of CORESET 0 in the frequency domain is set with reference to the SSB position. For example, The resource block (RB) offset can be used to determine the location of CORESET 0. Therefore, when the UE detects an SSB, it can decode the MIB in the SSB's PBCH. The UE can then determine if a CORESET exists for SIB1 (e.g., CORESET 0). This is necessary for cell-defined SSBs (CD-SSBs) because CD-SSBs are associated with SIB1. For non-cell-defined SSBs (NCD-SSBs), CORESET 0 does not exist because NCD-SSBs are not associated with SIB1.

[0032] Figure 4 An example scenario 400 of a MIB message format according to an embodiment of this disclosure is illustrated. Generally, a MIB message may include multiple parameters. For example, “ssb-subcarrierOffset” (i.e., The field "pdcch-ConfigSIB1" indicates the frequency domain offset between the SSB and the overall resource block grid, in units of subcarriers. This field can indicate that the cell does not provide SIB1, and therefore has no common core set. In this case, the "pdcch-ConfigSIB1" field indicates where the UE might (or might not) find a synchronization signal / physical broadcast channel (SS / PBCH) with a control resource set and a search space for SIB1. Alternatively, "pdcch-ConfigSIB1" can correspond to "RMSI-PDCCH-Config" and can determine the bandwidth of the PDCCH / SIB, the common core set / common search space, and the necessary PDCCH parameters. If the "ssb-subcarrierOffset" field indicates that SIB1 does not exist, then the "pdcch-ConfigSIB1" field indicates the frequency location where the UE can find an SS / PBCH block with SIB1, or that the network does not provide a frequency range for SS / PBCH blocks with SIB1. Furthermore, "cellBarred" indicates whether the cell allows the UE to camp on that cell.

[0033] In some implementations, after the UE detects the SS / PBCH block, the UE can determine, based on the MIB, that FR1 satisfies... Or satisfy FR2 At that time, there exists a CORESET for the type 0-PDCCH CSS set. The UE can determine from the MIB whether FR1 satisfies... Or satisfy FR2 At that time, there is no CORESET for the type 0-PDCCH CSS collection; the CORESET for the type 0-PDCCH CSS collection can be provided by PDCCH-ConfigCommon.

[0034] In some implementations, if the UE detects the first SS / PBCH block and determines that there is no CORESET for the type 0-PDCCH CSS set, and FR1 satisfies Or satisfy FR2 At that time, the UE can determine that the most recent (in the corresponding frequency direction) global synchronization channel number (GSCN) of the second SS / PBCH block with the CORESET for the associated type 0-PDCCH CSS set is . It is the GSCN of the first SS / PBCH block. For use with FR1, FR2-1 and FR2-NTN, For FR2-2, This is the provided GSCN offset. If the UE detects a second SS / PBCH block and that second SS / PBCH block does not provide a CORESET for the type 0-PDCCH CSS set, the UE can ignore the information related to the SS / PBCH block location GSCN to perform cell search.

[0035] In some implementations, if the UE detects an SS / PBCH block and determines that there is no CORESET for the type 0-PDCCH CSS set, and FR1 satisfies Or satisfy FR2 At that time, the UE determines that it is within the GSCN range. There is no SS / PBCH block with an associated type 0-PDCCH CSS set. and These are determined by `controlResourceSetZero` and `searchSpaceZero` in `pdcch-ConfigSIB1`, respectively. If the GSCN range is... The UE determines that there is no information on the second SS / PBCH block for associating the type 0-PDCCH CSS set on the detected SS / PBCH block.

[0036] Another approach to prevent traditional UEs (i.e., UEs that do not support on-demand SSB) from using on-demand SSB for initial access or cell camping is to use a cell-barrier parameter (e.g., cellBarred) for on-demand SSB in the MIB. See also Figure 4 The "cellBarred" parameter can be set to "Disabled" or "Not Disabled". The network can use this parameter to prevent legacy UEs from accessing on-demand SSB cells based on existing blocking mechanisms. That is, for cells with NCD SSBs, "cellBarred" in the MIB can be set to "Disabled" to prevent legacy UEs from performing RACH procedures on that cell. For cells with CD SSBs, "cellBarred" in the MIB can be set to "Not Disabled" to allow legacy UEs to perform RACH procedures on that cell.

[0037] From the UE's perspective, the UE can be configured to detect SSBs from a cell. The UE can determine whether the cell prohibition parameter in the SSB's MIB is set to prohibited, or whether the cell prohibition parameter in the SSB's MIB is set to not prohibited. If the cell prohibition parameter is set to prohibited (e.g., the SSB is an on-demand SSB on the cell), the UE can search for another SSB for synchronization. If the cell prohibition parameter is set to not prohibited (e.g., the SSB is a resident SSB on the cell), the UE can detect SIB1 associated with the SSB. The UE can then perform a RACH procedure based on SIB1. Therefore, the cell prohibition parameter can be used to prevent the UE from performing a RACH procedure using an on-demand SSB on the cell. If there is no resident SSB on the cell, the cell prohibition parameter can be set to prohibited.

[0038] Example Implementation

[0039] Figure 5 An exemplary communication system 500 is shown, which includes at least an example communication device 510 and an example network device 520, consistent with embodiments of this disclosure. The communication device 510 and the network device 520 can perform various functions to implement the schemes, techniques, processes, and methods related to on-demand SSB operation in mobile communications described herein, including the scenarios / schemes described above and processes 600 and 700 described below.

[0040] The communication device 510 may be part of an electronic device, which may be a UE (User Equipment), such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 510 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device (such as a tablet, laptop, or mobile phone). The communication device 510 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIoT device, such as a non-movable or fixed device, a home device, a wired communication device, or a computing device. For example, the communication device 510 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 510 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set-computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. The communication device 510 may include... Figure 5 The communication device 510 may include at least some of the components shown, such as processor 512. It may also include one or more other components unrelated to this disclosure (e.g., internal power supply, display device, and / or user interface device), and therefore, these components of the communication device 510 are not included in... Figure 5 This is shown in the text and not described below, in order to simplify and refine the content.

[0041] Network device 520 may be part of a network device, which may be a network node such as a satellite, base station, small cell, router, or gateway. For example, network device 520 may be implemented in an eNB in ​​an LTE network, a gNB in ​​a 5G / NR, IoT, NB-IoT, or IIoT network, or a satellite or base station in a 6G network. Network device 520 may include... Figure 5 The diagram shows at least some components, such as processor 522. Processor 522 may also include a protocol stack and a set of control function modules and circuitry. Network device 520 may also include one or more other components unrelated to the present disclosure (e.g., internal power supply, display device, and / or user interface device); therefore, these components of network device 520 are not included in... Figure 5 This is shown in the text and not described below, in order to simplify and refine the content.

[0042] In one aspect, processors 512 and 522 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, although the singular term "processor" is used herein to refer to processors 512 and 522, according to embodiments of this disclosure, processors 512 and 522 may include multiple processors in some embodiments and a single processor in other embodiments. In another aspect, processors 512 and 522 may be implemented in hardware (and optionally firmware) comprising, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, these electronic components being configured and arranged to achieve the specific purposes of this disclosure. In other words, in at least some embodiments, processors 512 and 522 are special-purpose machines specifically designed, arranged, and configured to perform specific tasks in devices (e.g., represented by communication device 510) and networks (e.g., represented by network device 520), consistent with various embodiments of this disclosure.

[0043] In some embodiments, the communication device 510 may further include a transceiver 516 connected to the processor 512, capable of wirelessly transmitting and receiving data. In some embodiments, the communication device 510 may further include a memory 514 connected to the processor 512, capable of being accessed by the processor 512 and storing data.

[0044] In some embodiments, network device 520 may further include memory 524 connected to processor 522, which can be accessed by processor 522 and stores data. Therefore, communication device 510 and network device 520 can communicate wirelessly via transceiver 516 and transceiver 526, respectively.

[0045] For illustrative purposes and without limitation, the capabilities of communication device 510 are described below, in conjunction with procedures 600 and 700. In these procedures, communication device 510 is implemented as a communication device or UE, and network device 520 is implemented as a network node (e.g., a base station) of a communication network.

[0046] Example Process

[0047] Figure 6An example flow 600 according to an embodiment of this disclosure is illustrated. Flow 600 may be (whether partially or entirely) an example implementation of the above-described scenario / solution for on-demand SSB operation in mobile communications. Flow 600 may represent one aspect of a characteristic embodiment of communication device 510. Flow 600 may include one or more operations, actions, or functions as shown in one or more blocks 610, 620, and 630. Although shown as discrete blocks, the individual blocks of flow 600 may be divided into more blocks, merged into fewer blocks, or omitted depending on the desired implementation. Furthermore, the individual blocks of flow 600 may be arranged according to... Figure 6 The process can be executed in the order shown, or in a different order. Process 600 can be implemented by communication device 510 or any suitable UE (e.g., UE 110) or machine-type device. For illustrative purposes only and without limitation, process 600 is described below in the context of communication device 510 as a UE. Process 600 may begin at block 610.

[0048] In block 610, process 600 may involve the processor 512 of communication device 510 detecting SSBs from a cell (e.g., network device 520) via transceiver 516. Process 600 can continue from block 610 to block 620.

[0049] In block 620, process 600 may involve processor 512 determining whether the SSB is an NCD SSB. Process 600 can continue from block 620 to block 630.

[0050] In block 630, process 600 may involve processor 512 searching for another SSB for synchronization via transceiver 516, provided that the SSB is an NCD SSB. The NCD SSB is an on-demand SSB on the cell.

[0051] In some implementations, process 600 may further involve processor 512 determining whether the SSB is a CD SSB. If the SSB is a CD SSB, process 600 may further involve processor 512 detecting the SIB1 associated with the CD SSB via transceiver 516. Process 600 may further involve processor 512 performing a RACH procedure based on the SIB1.

[0052] In some implementations, the CD SSB may include an associated type 0-PDCCH CSS set. The NCD SSB does not include an associated type 0-PDCCH CSS set.

[0053] In some implementations, process 600 may further involve processor 512 determining whether the subcarrier offset is greater than or equal to a first value of FR1, or whether it is greater than or equal to a second value of FR2.

[0054] In some implementations, process 600 may further involve processor 512 determining whether the subcarrier offset is less than a first value of FR1 or a second value of FR2.

[0055] In some implementations, the communication device 510 does not support the on-demand SSB.

[0056] Figure 7 An example flow 700 according to an embodiment of this disclosure is illustrated. Flow 700 may be (whether partially or entirely) an example implementation of the above-described scenario / solution for on-demand SSB operation in mobile communications. Flow 700 may represent one aspect of a characteristic embodiment of communication device 510. Flow 700 may include one or more operations, actions, or functions as shown in one or more blocks 710, 720, and 730. Although shown as discrete blocks, the individual blocks of flow 700 may be divided into more blocks, merged into fewer blocks, or omitted depending on the desired implementation. Furthermore, the individual blocks of flow 700 may be arranged according to... Figure 7 The process can be executed in the order shown, or in a different order. Process 700 can be implemented by communication device 510 or any suitable UE (e.g., UE 110) or machine-type device. For illustrative purposes only and without limitation, process 700 is described below in the context of communication device 510 as a UE. Process 700 may begin at block 710.

[0057] In block 710, process 700 may involve the processor 512 of communication device 510 detecting SSBs from a cell (e.g., network device 520) via transceiver 516. Process 700 can continue from block 710 to block 720.

[0058] In block 720, process 700 may involve processor 512 determining whether the cell prohibition parameter in the MIB of the SSB is set to prohibit. Process 700 can continue from block 720 to block 730.

[0059] In block 730, process 700 may involve processor 512 searching for another SSB for synchronization via transceiver 516 when the cell's prohibition parameter is set to prohibit. This SSB is an on-demand SSB on the cell.

[0060] In some implementations, process 700 may further involve processor 512 determining whether the cell prohibition parameter in the MIB of the SSB is set to not prohibit. Process 700 may further involve processor 512 detecting the SIB1 associated with the SSB via transceiver 516 if the cell prohibition parameter is set to not prohibit. Process 700 may further involve processor 512 performing a RACH procedure based on the SIB1.

[0061] In some implementations, the cell prohibition parameter can be used to prevent the communication device 510 from using the on-demand SSB to perform the RACH procedure on the cell.

[0062] In some implementations, if there is no resident SSB on the cell, the cell prohibition parameter can be set to prohibit.

[0063] Additional notes

[0064] The topics described herein sometimes demonstrate that different components are contained within or connected to different other components. It should be understood that these architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated” to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive components.

[0065] Furthermore, regarding the use of almost all plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. Various singular / plural arrangements are explicitly listed herein for clarity.

[0066] Furthermore, those skilled in the art will understand that terms commonly used herein, particularly in appended claims, such as the body portion of appended claims, are generally considered "open" terms. For example, the word "comprising" should be interpreted as "comprising but not limited to," the word "having" should be interpreted as "having at least," and the word "including" should be interpreted as "including but not limited to," etc. Those skilled in the art will also further understand that if a particular quantity is intended to be introduced in a claim, that intention will be explicitly stated in the claim; if no such statement is made, then that intention does not exist. For example, for ease of understanding, the appended claims described below may contain the use of the introductory phrases "at least one" and "one or more" to introduce the content of the claim. However, the use of such phrases should not be construed as meaning that when the content of the claim is introduced by the indefinite article "a" or "an," any specific claim containing that content is limited to only one embodiment containing that content, even if the same claim contains the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a" and / or "an" should be interpreted as "at least one" or "one or more"; the same applies to definite articles used to introduce the content of the claim. Furthermore, even if a specific quantity is explicitly stated in the claims, those skilled in the art will recognize that such a statement should be interpreted as at least the stated quantity. For example, stating "two items" alone, without further modification, means at least two items, or two or more items. Additionally, when using conventions such as "at least one of A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. When using conventions such as "at least one of A, B, and C," such structures are generally intended for those skilled in the art to understand the meaning of the convention. For example, "a system having at least one of A, B, and C" includes, but is not limited to, systems having only A, only B, only C, both A and B, both A and C, both B and C, and systems having both A, B, and C. Those skilled in the art will further understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of including only one term, either term, or both terms simultaneously. For example, the phrase "A or B" would be understood to include the possibility of including "A" or "B" or "A and B".

[0067] As can be seen from the foregoing, various embodiments of this disclosure have been described for illustrative purposes, and various modifications can be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are defined by the following claims.

Claims

1. A method comprising: The device's processor detects synchronization signals and physical broadcast channel blocks from the cell; The processor determines whether the synchronization signal and physical broadcast channel block is a non-cell-defined synchronization signal and physical broadcast channel block; as well as If the synchronization signal and physical broadcast channel block is a non-cell-defined synchronization signal and physical broadcast channel block, the processor searches for another synchronization signal and physical broadcast channel block to perform synchronization. The non-cell-defined synchronization signal and physical broadcast channel block is the on-demand synchronization signal and physical broadcast channel block on the cell.

2. The method of claim 1, further comprising: The processor determines whether the synchronization signal and physical broadcast channel block is a cell-defined synchronization signal and physical broadcast channel block; When the synchronization signal and physical broadcast channel block is the cell-defined synchronization signal and physical broadcast channel block, the processor detects system information block 1 associated with the cell-defined synchronization signal and physical broadcast channel block; as well as The processor executes the random access channel procedure according to system information block 1.

3. The method as described in claim 2, wherein, The cell-defined synchronization signal and physical broadcast channel block includes the associated Type 0 physical downlink control channel common search space set, while the non-cell-defined synchronization signal and physical broadcast channel block does not include the associated Type 0 physical downlink control channel common search space set.

4. The method of claim 1, wherein, Determining whether the synchronization signal and physical broadcast channel block is a non-cell-defined synchronization signal and physical broadcast channel block further includes: Determine whether the subcarrier offset is greater than or equal to a first value of frequency band 1, or whether the subcarrier offset is greater than or equal to a second value of frequency band 2.

5. The method of claim 2, wherein, Determining whether the synchronization signal and physical broadcast channel block is defined for this cell further includes: Determine whether the subcarrier offset is less than a first value for frequency band 1, or whether the subcarrier offset is less than a second value for frequency band 2.

6. The method of claim 1, wherein, The device does not support the on-demand synchronization signal and physical broadcast channel block.

7. A method comprising: The device's processor detects synchronization signals and physical broadcast channel blocks from the cell; The processor determines whether the cell prohibition parameter in the master information block of the synchronization signal and physical broadcast channel block is set to prohibition; as well as With the cell's prohibition parameter set to "disabled," the processor searches for another synchronization signal and physical broadcast channel block to perform synchronization. The synchronization signal and physical broadcast channel block are the on-demand synchronization signal and physical broadcast channel blocks on this cell.

8. The method of claim 7, further comprising: The processor determines whether the cell prohibition parameter in the main information block of the synchronization signal and physical broadcast channel block is set to not prohibition; When the cell prohibition parameter is set to not prohibition, the processor detects system information block 1 associated with the synchronization signal and physical broadcast channel block; as well as The processor executes the random access channel procedure according to system information block 1.

9. The method of claim 8, wherein, The cell prohibition parameter is used to prevent the device from using the on-demand synchronization signal and physical broadcast channel block to perform the random access channel procedure on the cell.

10. The method of claim 7, wherein, If there are no resident synchronization signals and physical broadcast channel blocks on this cell, the cell prohibition parameter is set to prohibit.

11. An apparatus comprising: A transceiver that enables wireless communication during operation; as well as The processor, which is communicatively connected to the transceiver, performs the following operations during operation: The transceiver detects synchronization signals and physical broadcast channel blocks from the cell. Determine whether the synchronization signal and physical broadcast channel block is a non-cell-defined synchronization signal and physical broadcast channel block; and If the synchronization signal and physical broadcast channel block is not a cell-defined synchronization signal and physical broadcast channel block, the transceiver searches for another synchronization signal and physical broadcast channel block to perform synchronization. The non-cell-defined synchronization signal and physical broadcast channel block is the on-demand synchronization signal and physical broadcast channel block on the cell.

12. The apparatus of claim 11, wherein, The operations performed by the processor during operation further include: Determine whether the synchronization signal and physical broadcast channel block is a cell-defined synchronization signal and physical broadcast channel block; When the synchronization signal and physical broadcast channel block is a cell-defined synchronization signal and physical broadcast channel block, the transceiver detects system information block 1 associated with the cell-defined synchronization signal and physical broadcast channel block; and The random access channel procedure is executed according to system information block 1.

13. The apparatus of claim 12, wherein, The cell-defined synchronization signal and physical broadcast channel block includes the associated Type 0 physical downlink control channel common search space set, while the non-cell-defined synchronization signal and physical broadcast channel block does not include the associated Type 0 physical downlink control channel common search space set.

14. The apparatus of claim 11, wherein, In determining whether the synchronization signal and physical broadcast channel block is a non-cell-defined synchronization signal and physical broadcast channel block, the processor further performs the following operations: Determine whether the subcarrier offset is greater than or equal to a first value of frequency band 1, or whether the subcarrier offset is greater than or equal to a second value of frequency band 2.

15. The apparatus of claim 12, wherein, In determining whether the synchronization signal and physical broadcast channel block defines a synchronization signal and physical broadcast channel block for the cell, the processor further performs the following operations: Determine whether the subcarrier offset is less than a first value for frequency band 1, or whether the subcarrier offset is less than a second value for frequency band 2.

16. The apparatus of claim 11, wherein, The device does not support the on-demand synchronization signal and physical broadcast channel block.

17. The apparatus of claim 11, wherein, The operations performed by the processor during operation further include: Determine whether the cell prohibition parameter in the main information block of the synchronization signal and physical broadcast channel block is set to prohibit; and When the cell's prohibition parameter is set to "disabled," the transceiver searches for another synchronization signal and physical broadcast channel block to perform synchronization. The synchronization signal and physical broadcast channel block refers to the on-demand synchronization signal and physical broadcast channel block on the cell.

18. The apparatus of claim 11, wherein, The operations performed by the processor during operation further include: Determine whether the cell prohibition parameter in the main information block of the synchronization signal and physical broadcast channel block is set to not prohibition; and With the cell prohibition parameter set to not prohibition, the transceiver detects system information block 1 associated with the synchronization signal and physical broadcast channel block; and The random access channel procedure is executed according to system information block 1.

19. The apparatus of claim 18, wherein, The cell prohibition parameter is used to prevent the device from using the on-demand synchronization signal and physical broadcast channel block to perform the random access channel procedure on the cell.

20. The apparatus of claim 17, wherein, If there are no resident synchronization signals and physical broadcast channel blocks on this cell, the cell prohibition parameter is set to prohibit.

Images