Synchronization and cell search for environmental internet of things devices

Abstract

Methods, systems, and devices are described for wireless communication. A user equipment (UE) can receive a first primary synchronization signal (PSS) during a first PSS occasion. The UE can receive a secondary synchronization signal (SSS) or a wake-up signal (WUS) during one of a set of monitoring occasions between the first PSS and a second PSS. Successive monitoring occasions of the set of monitoring occasions can be separated in time by a first time gap, and each monitoring occasion of the set of monitoring occasions can be associated with a different cell. The UE can transmit, in response to the wake-up signal, a request for system information via resources indicated by the wake-up signal. The UE can receive, in response to the request, a system information block (SIB).

Description

Technical Field

[0001] The following section deals with wireless communications, including synchronization and cell search for environmental Internet of Things (IoT) devices. Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0003] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting synchronization and cell search for environmental Internet of Things (IoT) devices. For example, instead of Orthogonal Frequency Division Multiplexing (OFDM) waveforms, on-off keying (OOK) or Manchester decoding can be used to encode the primary synchronization signal (PSS) and secondary synchronization signal (SSS) for environmental IoT devices. The periodicity of the PSS for environmental IoT devices can be longer than the periodicity of synchronization signal blocks in other systems. Cell-specific mappings can exist for the monitoring timings used for synchronization. For example, there can be a set of SSS timings or a set of Wake-up Signal (WUS) timings, or both, between PSS timings, and different cells can send SSS during different SSS timings or WUS during different WUS timings based on cell identifiers. A cell can send one SSS sequence per timing, so the UE can associate the received SSS waveform with a single SSS sequence per time slot. For example, the UE can associate the received SSS waveform with one sequence per time slot instead of all possible sequences. In some examples, the UE can monitor broadcast WUS, which can indicate resources available for the UE to send system information requests. The UE can send a request for system information based on broadcast WUS, and the UE can request complete system information or system information updates. In response to this request, the UE can receive a System Information Block (SIB). The SIB can indicate parameters used for random access procedures or WUS monitoring, or both.

[0004] A method for wireless communication by a UE is described. The method may include: receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and receiving an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and a second PSS, wherein the consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0005] A UE for wireless communication is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories (e.g., operative ground, communicative ground, functional ground, electronic ground, or electrical ground). The one or more processors may be able to operate individually or jointly to execute code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the UE to: receive a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and receive an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and a second PSS, wherein consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0006] Another UE for wireless communication is described. The UE may include: components for receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and components for receiving an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and a second PSS, wherein the consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0007] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) for: receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first period; and receiving an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and a second PSS, wherein consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0008] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for sending requests for system information in response to a resource indicated by the WUS.

[0009] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, sending a request for system information may include operations, features, components, or instructions for sending a preamble indicating a request for complete system information or a request for an update of system information.

[0010] In some examples of the methods, UEs, and non-transitory computer-readable media described herein, requests for system information may be sent based on the expiration of system information stored at the UE.

[0011] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving system information blocks in response to a request for system information.

[0012] In the methods described herein, and in some examples of UEs and nontransitory computer-readable media, the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a WUS monitoring configuration for paging signaling, or any combination thereof.

[0013] In the methods described herein, and in some examples of UEs and non-transitory computer-readable media, system information blocks indicate carrier information for random access channel configuration or WUS monitoring configuration for paging signaling, or both.

[0014] The methods described herein, examples of UEs, and non-transitory computer-readable media may also include operations, features, components, or instructions for: monitoring one or more WUS monitoring opportunities via a carrier indicated by a system information block based on the UE's identifier or the identifier of a subgroup of the UE to obtain paging signaling.

[0015] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for monitoring one or more WUS moments in a set of multiple WUS moments, wherein the set of multiple monitoring moments between a first PSS and a second PSS may be an SSS moment, and wherein the first WUS moment in the set of multiple WUS moments may be offset from the SSS by a fixed duration in time.

[0016] In some examples of the methods described herein, UEs, and nontransitory computer-readable media, WUS indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with the SSS, the presence of auxiliary nodes for environmental IoT devices, information for in-frequency cell reselection, or any combination thereof.

[0017] The methods described herein, some examples of UEs and nontransitory computer-readable media may also include operations, features, components or instructions for decoding a first PSS or SSS or both based on on-keying encoding or Manchester encoding or both.

[0018] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first PSS may be received during a time slot in a set of multiple time slots in the first PSS timing, and each time slot in the set of multiple time slots may be associated with a different beam direction.

[0019] The methods described herein, examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for associating SSS waveforms with SSS sequences during a monitoring period.

[0020] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, receiving an SSS may include operations, features, components, or instructions for receiving an SSS during a time slot in a set of multiple time slots at a monitoring time, wherein each of the multiple time slots may be associated with a different beam direction.

[0021] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first monitoring opportunity in a set of multiple monitoring opportunities may have a fixed duration in time with a first PSS offset.

[0022] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the first time interval may be based on a first periodicity and the number of that set of multiple monitoring opportunities.

[0023] A method for wireless communication by a network entity is described. The method may include: outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and a second PSS, wherein the successive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0024] A network entity for wireless communication is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories (e.g., operative ground, communicative ground, functional ground, electronic ground, or electrical ground). The one or more processors may be able to operate individually or jointly to execute code (e.g., directly, indirectly, after preprocessing, or without preprocessing) to cause the network entity to: output a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and output an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and a second PSS, wherein consecutive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0025] Another network entity for wireless communication is described. This network entity may include: components for outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity; and components for outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and a second PSS, wherein the successive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0026] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by at least one processor (e.g., directly, indirectly, after preprocessing, or without preprocessing) for: outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first period; and outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and a second PSS, wherein consecutive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0027] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for obtaining system information in response to a request from WUS via a resource indicated by WUS.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a request for system information may include operations, features, components, or instructions for obtaining a preamble indicating a request for complete system information or a request for an update of system information.

[0029] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a block of system information in response to a request for system information.

[0030] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a WUS monitoring configuration for paging signaling, or any combination thereof.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the system information block indicates carrier information for random access channel configuration or WUS monitoring configuration for paging signaling, or both.

[0032] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting WUS for paging signaling via a carrier indicated by a system information block, based on a UE identifier or an identifier of a subgroup including the UE, during one or more WUS transmission opportunities.

[0033] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, WUS may be output during a WUS timing in a set of multiple WUS timings, the set of multiple transmission timings between a first PSS and a second PSS may be an SSS timing, and the first WUS timing in the set of multiple WUS timings may be offset from the SSS by a fixed duration in time.

[0034] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, WUS indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with the SSS, the presence of auxiliary nodes for environmental IoT devices, information for in-frequency cell reselection, or any combination thereof.

[0035] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for encoding a first PSS or SSS or both using on / off keying encoding or Manchester encoding or both.

[0036] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, a first PSS may be output using a first beam direction during a time slot in a set of multiple time slots in the first PSS timing, and each time slot in the set of multiple time slots may be associated with a different beam direction.

[0037] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the output SSS may include operations, features, components, or instructions for outputting an SSS during a time slot in a set of multiple time slots in a transmission timing, using a first beam direction, wherein each time slot in the set of multiple time slots may be associated with a different beam direction and a different SSS sequence. Attached Figure Description

[0038] Figure 1 An example of a wireless communication system supporting synchronization and cell search for environmental Internet of Things (IoT) devices, according to one or more aspects of this disclosure, is shown.

[0039] Figure 2 Examples of wireless communication systems supporting synchronization and cell search for environmental IoT devices are shown, according to one or more aspects of this disclosure.

[0040] Figure 3 An example of a synchronization signaling configuration supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0041] Figure 4 An example of a system information request configuration supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0042] Figure 5 An example of a process flow supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0043] Figure 6 and Figure 7 A block diagram of a device supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0044] Figure 8 A block diagram is shown of a communication manager supporting synchronization and cell search for environmental IoT devices, according to one or more aspects of this disclosure.

[0045] Figure 9 A diagram is shown illustrating a system including devices supporting synchronization and cell search for environmental IoT devices, according to one or more aspects of this disclosure.

[0046] Figure 10 and Figure 11 A block diagram of a device supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0047] Figure 12A block diagram is shown of a communication manager supporting synchronization and cell search for environmental IoT devices, according to one or more aspects of this disclosure.

[0048] Figure 13 A diagram is shown illustrating a system including devices supporting synchronization and cell search for environmental IoT devices, according to one or more aspects of this disclosure.

[0049] Figures 14 to 16 A flowchart illustrating a method for synchronization and cell search of environmental IoT devices according to one or more aspects of this disclosure is shown. Detailed Implementation

[0050] Wireless communication systems for environmental Internet of Things (IoT) communication systems can include low-complexity devices with small energy budgets. For example, low-complexity devices such as radio frequency identifier (RFID) tags, sensors, and trackers can harvest ambient energy to perform backscatter communication. In some examples, devices in environmental IoT systems may be able to perform active transmission (e.g., non-backscatter communication), but the device is likely still very low-complexity and has a much smaller maximum instantaneous power consumption compared to devices configured for narrowband IoT communication, enhanced mobile broadband, etc. The device may be able to perform a cell search process as a conventional user equipment (UE) to obtain time and frequency synchronization with the cell and establish a dedicated connection. However, current techniques for cell search processes can be complex and consume more power than the device can sustain or support.

[0051] The wireless communication system described herein supports techniques for low-complexity synchronization and cell search processes for environmental IoT devices. For example, on-off keying (OOK) or Manchester decoding can be used instead of OFDM waveforms to encode the primary synchronization signal (PSS) and secondary synchronization signal (SSS) for environmental IoT devices. The periodicity of the PSS for environmental IoT devices can be longer than the periodicity of synchronization signal blocks in other systems (e.g., New Radio (NR)). Monitoring timings associated with synchronization can use cell-specific mappings. For example, there can be N SSS timings between PSS timings, and different cells can transmit SSSs during different SSS timings based on cell identifiers. In some examples, a cell can transmit one SSS sequence per SSS timing. The UE can associate the received SSS waveform with a single SSS sequence per time slot. For example, the UE can associate the received SSS waveform with one sequence per time slot instead of all possible sequences. Additionally or alternatively, there can be a set of wake-up signal (WUS) timings between PSS timings, and different cells can transmit WUS during different WUS timings in some examples based on cell identifiers.

[0052] In some examples, the UE can monitor a broadcast WUS, which can indicate resources available for the UE to send system information requests. The broadcast WUS can indicate information similar to the Master Information Block (MIB) in other systems, while requiring less power consumption at the UE. The UE can send a request for system information based on the broadcast WUS, and can request complete system information or system information updates. The UE can respond to this request by receiving a System Information Block (SIB). The SIB can indicate parameters used for random access procedures or WUS monitoring, or both.

[0053] The various aspects of this disclosure are first described in the context of a wireless communication system. These aspects are further illustrated by apparatus diagrams, system diagrams, and flowcharts relating to synchronization and cell search for IoT devices in an environment, and are described with reference to these diagrams.

[0054] Figure 1 An example of a wireless communication system 100 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more devices, such as one or more network devices (e.g., network entity 105), one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, an NR network, or a network operating according to other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0055] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via communication link 125 (e.g., a radio frequency (RF) access link). For example, network entity 105 may support a coverage area 110 (e.g., a geographical coverage area) over which UE 115 and network entity 105 can establish communication link 125. Coverage area 110 may be an example of a geographical area in which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0056] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1Some example UE 115s are illustrated herein. The UE 115 described herein may be able to support, for example, Figure 1 Communication of various types of devices (e.g., including UE 115 or other wireless communication devices of network entity 105) in the wireless communication system 100 shown.

[0057] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0058] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via backhaul communication link 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication link 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. The backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof, or may include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 may communicate with the core network 130 via communication link 155.

[0059] One or more network entities or network equipment described herein as network entity 105 or network equipment may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, NodeB, eNodeB (eNB), next-generation NodeB or gigabit NodeB (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home NodeB, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity (e.g., network entity 105 or a single RAN node, such as base station 140).

[0060] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across multiple network entities (e.g., network entity 105) such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) such as CU 160, a Distributed Unit (DU) such as DU 165, a Radio Unit (RU) such as RU 170, a RAN Intelligent Controller (RIC) such as RIC 175 (e.g., a near real-time RIC (near RT RIC), a non-real-time RIC (non-RT RIC)), a Service Management and Orchestration (SMO) system such as SMO system 180, or any combination thereof. RU 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities in network entity 105 of a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0061] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 (e.g., one or more CUs) may connect to DU 165 (e.g., one or more DUs) or RU 170 (e.g., one or more RUs) or some combination thereof, and DU 165, RU 170, or both may host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and may each be at least partially controlled by CU 160. Additionally or alternatively, a functional split of the protocol stack may be employed between DU 165 and RU 170, such that DU 165 may support one or more layers of the protocol stack, and RU 170 may support one or more different layers of the protocol stack. DU 165 may (e.g., via one or more different RUs, such as RU 170) support one or more different cells. In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by corresponding network entities (e.g., one or more network entities in network entity 105) that communicate via such communication links.

[0062] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities in network entity 105 (e.g., network entity 105 or IAB node 104) may be partially controlled by each other. IAB node 104 may be referred to as a donor entity or IAB donor. DU 165 or RU 170 may be partially controlled by CU 160 associated with network entity 105 or base station 140 (such as a donor network entity or donor base station). One or more donor entities (e.g., IAB donors) may communicate with one or more additional devices (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DU 165) of a coupled IAB donor. The IAB-MT may be equipped with a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include one or more DUs (e.g., DU 165) that support communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., IAB node 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0063] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include one or more of CU 160, DU 165, and RU 170, in which case CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, CU 160 may communicate with core network 130 via an interface (which may be part of a backhaul link) and may communicate with other CUs (e.g., including CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be another part of a backhaul link).

[0064] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may be relayed by other IAB nodes 104 for UE transmission). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. The IAB-MT entity of IAB node 104 can provide a Uu interface to the child IAB node (e.g., IAB node 104) to receive signaling from the parent IAB node (e.g., IAB node 104), and the DU interface (e.g., DU 165) can provide a Uu interface to the parent IAB node to send signaling notifications to the child IAB node or UE 115.

[0065] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node to IAB node 104. For example, an IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. An IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions (e.g., transmissions relayed from the IAB donor to UE 115) via one or more DUs (e.g., DU 165). In other words, data can be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104 (e.g., other IAB nodes). Communication with IAB node 104 can be scheduled by the IAB donor or by DU 165 of IAB node 104.

[0066] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support the tests described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., components such as IAB node, DU 165, CU 160, RU 170, RIC 175, SMO system 180, etc.).

[0067] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein “device” may also be referred to as a unit, station, terminal, or client, etc. UE 115 may also include or be referred to as personal electronic devices, such as cellular phones, personal digital assistants (PDAs), multimedia / entertainment devices (e.g., radios, MP3 players, or video devices), cameras, gaming devices, navigation / positioning devices (e.g., GNSS (Global Navigation Satellite System) devices based on, for example, GPS (Global Positioning System), BeiDou system, GLONASS or Galileo system, ground-based devices, etc.), tablet computers, laptop computers, netbooks, smartbooks, personal computers, smart devices, wearable devices (e.g., smartwatches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), drones, robots / robotic devices, vehicles, vehicle equipment, meters (e.g., parking timers, electricity meters, gas meters, water meters), monitors, air pumps, electrical appliances (e.g., kitchen appliances, washing machines, dryers), location tags, medical / healthcare devices, implants, sensors / actuators, displays, or any other suitable device configured to communicate via wireless or wired media. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which can be implemented in a variety of objects such as appliances or vehicles, meters, etc.

[0068] The UE 115 described herein can communicate with various types of devices, such as the UE 115 which sometimes operates as a relay, and network entity 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0069] UE 115 and network entity 105 can wirelessly communicate with each other via communication link 125 (e.g., one or more access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined PHY layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating operation for the carrier, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured to utilize multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can mean that any part of network entity 105 of the RAN (e.g., base station 140, CU160, DU 165, RU 170) communicates with another device (e.g., directly or via one or more other network entities, such as one or more network entities in network entity 105).

[0070] In some examples, such as in carrier aggregation configurations, a carrier may have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., of the same or different RATs) are used to anchor the connection.

[0071] The communication link 125 of the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. The carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0072] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a set of bandwidths for a carrier for a specific RAT (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0073] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0074] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and communication for UE 115 can be constrained to one or more active BWPs.

[0075] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, in response This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval for organizing communication resources can be based on radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0076] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems, such as wireless communication system 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0077] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0078] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a public search space set configured to transmit control information to UE115 (e.g., one or more UEs), or it may include a UE-specific search space set configured to transmit control information to UE115 (e.g., a particular UE).

[0079] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0080] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. Small cells may be associated with network entities 105 (e.g., base station 140 operating at lower power relative to macro cells) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed user group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0081] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0082] In some examples, network entity 105 (e.g., base station 140, RU 170) can be mobile, and thus provide communication coverage to mobile coverage areas (such as coverage area 110). In some examples, coverage areas 110 associated with different technologies (e.g., different coverage areas) can overlap, but coverage areas 110 (e.g., different coverage areas) can be supported by the same network entity (e.g., network entity 105). In some other examples, overlapping coverage areas (such as coverage area 110) associated with different technologies can be supported by different network entities (e.g., network entity 105). The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different RATs to support communication for coverage area 110 (e.g., different coverage areas).

[0083] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timing, and transmissions from different network entities (e.g., different network entities within network entity 105) can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timing, and in some examples, transmissions from different network entities (e.g., different network entities within network entity 105) can be time-disaligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0084] Some UEs 115 (such as MTC or IoT devices) can be relatively low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entities 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or instruments to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging. In one respect, the techniques disclosed herein are applicable to MTC or IoT UEs. MTC or IoT UE can include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UE, NB-IoT (also known as CAT NB1) UE, and other types of UE. eMTC and NB-IoT can refer to future technologies that can evolve from or are based on these technologies. For example, eMTC can include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), and mMTC (massive MTC), while NB-IoT can include eNB-IoT (enhanced NB-IoT) and FeNB-IoT (further enhanced NB-IoT).

[0085] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115 may include: entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0086] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0087] In some examples, UE 115 may be configured to support direct communication with other UEs (e.g., one or more UEs in UE 115) via a device-to-device (D2D) communication link (such as D2D communication link 135) (e.g., according to a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 in a group performing D2D communication may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UEs 115 in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, a group of UEs 115 communicating via D2D communication can support a one-to-many (1:M) system, in which each UE 115 transmits to one or more UEs in the group. In some examples, network entity 105 can facilitate the scheduling of resources used for D2D communication. In some other examples, D2D communication can be performed between UEs 115 without involving network entity 105.

[0088] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0089] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers).

[0090] The wireless communication system 100 can also operate in the Ultra High Frequency (SHF) band (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the Extremely High Frequency (EHF) band (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and closer together than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may have even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency bands, and the frequency band usage specified across these frequency bands may vary by country or regulatory authority.

[0091] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may employ licensed assisted access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be based on carrier aggregation configurations combined with component carriers operating with licensed frequency bands (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0092] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0093] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0094] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0095] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0096] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., network entity 105 or UE 115) along a single beam direction (e.g., a direction associated with a receiving device such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0097] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0098] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0099] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0100] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under relatively poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0101] Some systems support devices that operate using low-power radio. For example, a low-power wake-up receiver can be implemented to reduce power consumption at UE 115. The low-power wake-up radio can be a companion receiver that monitors wake-up signals with very low power consumption. When there is no data to receive at UE 115, the main radio can be turned off unless UE 115 has something to transmit. The low-power wake-up radio can remain active to monitor low-power WUS. When data for UE 115 is available, the low-power wake-up radio can receive low-power WUS on demand. UE 115 can then provide power to the main radio to receive data (e.g., paging messages) based on the received low-power WUS.

[0102] Network entity 105 may send a low-power synchronization signal for low-power wake-up radio to adjust timing at UE 115 and maintain synchronization with the network. After receiving the low-power synchronization signal, UE 115 can use it to resynchronize and calibrate timing to receive low-power WUS. The periodicity of the low-power synchronization signal may be based on the timing synchronization requirements of the low-power wake-up radio under certain clock uncertainties. Clock uncertainties may be based on, for example, clock frequency drift and maximum clock frequency error. Compared to the synchronization signal used for the master radio, the low-power synchronization signal may have a longer periodicity (e.g., once every 1.28 seconds).

[0103] Network entity 105 can use the OOK waveform for low-power WUS and low-power synchronization signals. The OOK waveform can be detected using an incoherent envelope detector without requiring a time-domain / frequency-domain equalizer. Compared to receiving OFDM waveforms, the receiver does not need to maintain or track a highly accurate oscillation rate, and therefore avoids a phase-locked loop (PLL) to further reduce power consumption on the receiver side.

[0104] Environmental IoT can be a communication system comprising devices that operate based on energy harvesting. These devices can be low-complexity devices with small operating energy budgets. Environmental IoT can be implemented for inventory, location, tracking, sensors, etc. Different types of devices can exist operating in an environmental IoT system. The first type of device can be a battery-free device without energy storage or with energy storage capacity. The first type of device can rely on the availability of an environmental energy source to perform energy harvesting and communication. The second type of device can be a semi-passive device (e.g., a capacitor) with limited energy storage capacity. The second type of device can support backscatter communication by modulating the incoming RF. The second type of device may not be equipped with active RF components.

[0105] The third type of device in an environmental IoT system can be capable of active transmission and can be equipped with active RF components. For example, the third type of device can support non-backscatter communication. The third type of device can still be a low-complexity device with a small power budget.

[0106] The third type of device can perform a cell search process as a non-environmental IoT device to obtain time and frequency synchronization with the cell and establish a dedicated connection. For example, UE 115, as a third type of device, can switch to a specific frequency, monitor the PSS and SSS to perform a cell search, detect candidate signals, and select a candidate signal to perform synchronization. After time and frequency synchronization, UE 115 can attempt to decode the Physical Broadcast Channel (PBCH) and the corresponding Master Information Block (MIB). Based on the MIB, UE 115 can obtain parameters for the control resource set and search space used to receive downlink control information for the first SIB (e.g., SIB1). UE 115 can blindly decode the downlink control information scrambled by the System Information Radio Network Temporary Identifier (SI-RNTI). Based on the content of the downlink control information encoded by the SI-RNTI, UE 115 can decode the downlink shared channel carrying SIB1 and obtain initial system information. After the cell search, UE 115 can perform a random access procedure to obtain uplink synchronization and establish an RRC connection with network entity 105.

[0107] Cell search processes in some systems can increase UE complexity and consume significant power. For example, for UE 115, a third-type environment IoT device, cell search processes in NR systems can be extremely complex. PSS and SSS can be based on OFDM waveforms, and UE 115 can first estimate the frequency offset. For instance, UE 115 can frequency-shift the received waveform using candidate frequency offsets before associating it with a local PSS sequence. This can increase UE search complexity. For SSS search, UE 115 can associate a frequency-corrected waveform with each possible SSS sequence, thus searching all candidate signals. In some examples, up to 1008 different sequences may exist to search. UE 115 can perform this for each synchronization signal block in a synchronization signal burst within a 5-millisecond time period. Long sequences can be used for cell differentiation when on / off keying is used for synchronization signals. This can keep UE 115 awake in an active or high-power state, increasing power consumption. Additionally, UE 115 can read MIB and SIB frequencies for system information change updates. Some updates may not be necessary but can consume power at the UE, such as when the UE 115 does not need to connect to the cell. SSBs can be sent at short intervals (e.g., 20ms) to support RRM measurements for devices performing cell reselection while operating in idle mode. However, in battery-less environments, IoT UEs may not need to measure as frequently as other UE 115s, as the amount of energy harvested may be time-varying.

[0108] The wireless communication system 100 can support techniques for low-complexity synchronization and cell search processes for environmental IoT devices. For example, on / off keying or Manchester decoding can be used instead of OFDM waveforms to encode the PSS and SSS for environmental IoT devices. The periodicity of the PSS for environmental IoT devices can be longer than the periodicity of synchronization signal blocks in other systems (e.g., NR). The monitoring timing for synchronization can employ cell-specific mapping. For example, there can be N SSS timings between PSS timings, and different cells can transmit SSS during different SSS timings based on cell identifiers. A cell can transmit one SSS sequence per timing, so the UE can associate the received SSS waveform with a single SSS sequence per time slot. For example, the UE can associate the received SSS waveform with one sequence per time slot instead of all possible sequences. In some examples, the UE can monitor a broadcast WUS, which can indicate resources available for the UE to send system information requests. The broadcast WUS can indicate information similar to the MIB in other systems, while requiring less power consumption at the UE. The UE may send a request for system information based on broadcast WUS, and the UE may request complete system information or system information updates. The UE may respond to this request by receiving an SIB. The SIB may indicate parameters used for random access procedures or WUS monitoring, or both.

[0109] Figure 2 An example of a wireless communication system 200 supporting synchronization and cell search for environmental IoT devices according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entity 105-a and UE 115-a, which may be corresponding examples of network entity 105 and UE 115 as described herein. UE 115-a may be an example of a low-power, low-complexity device. For example, UE 115-a may be an example of an environmental IoT device or an environmental IoT UE (e.g., a tag).

[0110] In some cases, UE 115-a may use backscatter signaling for communication. Backscatter or backscatter-based communication includes techniques for transmitting data using incident radio frequency signals without batteries or power sources by employing passive reflection and modulation of the incoming radio frequency signal and converting that signal into power that can then be used for data communication. For example, UE 115-a may include a backscatter system 205. Backscatter system 205 may modulate a portion of an incoming signal, such as an excitation signal or a continuous wave signal, and reflect it back as a backscatter signal. In some examples, the backscatter device may harvest some energy from the incoming signal to power the backscatter device or to power the energy storage device of the backscatter device.

[0111] Some environmental IoT devices may be battery-free or lack energy storage capabilities. For example, a first type of environmental IoT device may rely on an ambient energy source for energy harvesting and backscatter communication. Some environmental IoT devices may be semi-passive, such as capacitors, with limited energy storage capacity. For example, a second type of environmental IoT device may not be equipped with active RF components but can perform backscatter communication by modulating incoming RF signals.

[0112] UE 115-a can be an example of a third type of environmental IoT device capable of active transmission or non-backscatter communication, but it is a low-complexity device. For example, UE 115-a can be a device with lower complexity than UE 115, which supports narrowband IoT communication. In some cases, UE 115-a may have low maximum instantaneous power consumption, such as 100 microwatts. The wireless communication system 200 can provide techniques for low-complexity devices, such as environmental IoT devices including UE 115-a, to obtain synchronization information and perform cell search procedures.

[0113] In some examples, network entity 105-a may use On-Off Keying (OOK) encoding or Manchester decoding, or both, to encode synchronization signals or signals used for synchronization at ambient IoT devices. For example, UE 115-a may wake up or power on and search for an OOK-based PSS for coarse time synchronization. Network entity 105-a may periodically send a PSS during PSS timing periods. For example, UE 115-a may receive a PSS during PSS timing period 210. UE 115-a may receive the PSS and synchronize coarse timing information with network entity 105-a based on the PSS. In some examples, the periodicity of the PSS for ambient IoT devices may be longer than the periodicity of the PSS for non-ambient IoT devices (such as the PSS for NR).

[0114] In some examples, UE 115-a may determine the slot length based on the PSS or by searching for the PSS. UE 115-a may also search for other signals for synchronization based on the slot length. In some examples, the slot length may be based on the PSS periodicity. For example, different PSS periodicities may be associated with different slot lengths. In another example, the slot length may be based on a PSS sequence. In some examples, the PSS may include or be based on a binary m-sequence. In some examples, Manchester decoding may be applied prior to OOK modulation.

[0115] Compared to other modulations used for OFDM signaling, OOK coding reduces UE search complexity. For waveform generation at network entity 105-a, bits '1' of the decoded binary sequence can be mapped to OOK 'ON' symbols, and bits '0' can be mapped to OOK 'OFF' symbols. In some examples, network entity 105-a can apply an overlay OFDM signal to the OOK 'ON' symbols, which can flatten the spectrum of the PSS waveform.

[0116] In some examples, network entity 105-a may perform beam scanning for a PSS. For example, different beams may be associated with different sequences or mapped to different time slots, or both. In some examples, different beams may be segmented from a long sequence based on a maximum or threshold number of beams. In some examples, if network entity 105-a does not use a beam to transmit a PSS, the sequence associated with that beam may not be reused for another beam.

[0117] For example, network entity 105-a can use an m-sequence generator to generate a sequence. In some examples, network entity 105-a can encode the sequence using Manchester decoding. Network entity 105-a can segment the sequence based on the maximum number of beams. Network entity 105-a can perform OOK encoding on the segmented sequence, or generate OOK for the sequence and map the OOK-encoded sequence to time slots. Network entity 105-a can use beam scanning across multiple time slots to transmit the OOK-encoded sequence.

[0118] Network entity 105-a may send another signal for additional or more granular synchronization of environmental IoT devices. For example, a set of monitoring times 215 may be configured between each PSS time 210. In some examples, network entity 105-a may send an SSS during monitoring time 215. For example, monitoring time 215 may be an SSS time. In some examples, network entity 105-a may send a WUS during monitoring time 215. For example, monitoring time 215 may be a WUS time. In some examples, the number of monitoring times 215 between PSS times 210 may be fixed, pre-configured for the wireless communication system 200, or configurable by network entity 105-a.

[0119] UE 115-a can perform more granular synchronization based on WUS or SSS. In some examples, WUS or SSS can indicate additional synchronization information, such as time synchronization, frequency synchronization, or both. In some examples, WUS for ambient IoT devices can indicate information associated with system information or the cell search process. For example, WUS received after an SSS or during monitoring opportunity 215 can indicate cell prohibition information or which types of devices are supported. For example, WUS can indicate which types of ambient IoT devices are supported. In some examples, WUS can indicate the presence of auxiliary nodes, such as auxiliary nodes for the first type or second type of ambient IoT devices described herein. In some examples, WUS can indicate information for in-frequency cell reselection.

[0120] In some examples, UE 115-a may receive SSS during monitoring time 215. After performing synchronization based on SSS, UE 115-a may monitor WUS broadcast. WUS broadcast may trigger UE 115-a to send a request for system information 220.

[0121] In some examples, UE 115-a may receive WUS during monitoring timing 215, and the WUS received during monitoring timing 215 may trigger UE 115-a to send a request for system information 220. In some examples, if UE 115-a has not yet obtained system information or the system information stored at UE 115-a is outdated, UE 115-a may send a preamble on the resource indicated by the WUS, and the preamble may indicate a request for system information.

[0122] In some examples, the UE may monitor WUS during the WUS timing between PSS timings, instead of monitoring SSS during the SSS timing between PSS timings. If WUS is used instead of SSS for more granular synchronization and cell identifier acquisition, the cell identifier information may be indicated by the broadcast group WUS. In some examples, WUS during different WUS timings may be examples of broadcast group WUS, or the broadcast WUS group may be separate.

[0123] Network entity 105-a may receive request 220 for system information and send system information in response. For example, network entity 105-a may respond to request 220 from UE 115-a, such as sending system information via SIB. In some examples, the SIB may be an example of on-demand system information or on-demand SIB. The SIB may indicate information such as the SFN of network entity 105-a or wireless communication system 200. In some examples, the SIB may indicate resource pool configuration for environmental IoT devices. In some examples, the SIB may indicate random access channel (RACH) configuration for initial access. In some examples, the SIB may indicate WUS monitoring configuration for paging signaling, such as duty cycle WUS monitoring configuration for paging signaling.

[0124] UE 115-a may receive system information in response to request 220. UE 115-a may attempt to establish a connection with network entity 105-a based on the system information. For example, UE 115-a may perform a random access procedure based on the system information. In some examples, UE 115-a may perform a random access procedure based on a RACH configuration for initial access indicated by the SIB. Additionally or alternatively, UE 115-a may monitor WUS from network entity 105-a based on a WUS monitoring configuration for paging signaling indicated by the SIB.

[0125] Figure 3 An example of a synchronization signaling configuration 300 supporting synchronization and cell search for environmental IoT devices, according to one or more aspects of this disclosure, is shown.

[0126] Network entity 105 may periodically send PSSs for environmental IoT devices. PSSs for environmental IoT devices may have a longer periodicity than PSSs for other types of devices. In some examples, network entity 105 may use Manchester decoding, OOK decoding, or both to encode the PSS.

[0127] For example, network entity 105 may transmit a PSS during PSS timing 305-a. After one period of PSS, network entity 105 may transmit a PSS during PSS timing 305-b. In some examples, the periodicity of the PSS may be configured for the wireless communication system or may be configured by network entity 105.

[0128] Environmental IoT devices (such as UE 115) can monitor the PSS during PSS timing 305. For example, UE 115 can monitor the PSS during PSS timing 305-a. UE 115 can determine the slot length or slot duration based on searching for or receiving the PSS. UE 115 can search for the PSS and perform coarse time synchronization based on the PSS.

[0129] In some examples, network entity 105 may perform beam scanning for a PSS transmitted for environmental IoT devices. For example, different beams may be associated with different sequences. Different sequences may be segmented from a long sequence based on the maximum number of beams. Different sequences may be mapped to different time slots. For example, network entity 105 may transmit a first sequence using a first beam during a first time slot of PSS timing 305-a, and network entity 105 may transmit a second sequence using a second beam during a second time slot of PSS timing 305-a. In some examples, if a beam is not transmitted, network entity 105 may not reuse the sequence associated with that beam for other beams.

[0130] Network entity 105 may transmit additional signals for synchronization between PSS transmissions. For example, network entity 105 may transmit additional signals that can be received and used for synchronization by environmental IoT devices such as UE 115. Some examples of signals that network entity 105 may transmit during monitoring time 310 may include SSS or WUS, or both. A set of monitoring times 310 may exist between PSS time 305-a and PSS time 305-b. In some examples, a fixed number of monitoring times 310 may exist between two consecutive PSS times 305. In some examples, this fixed number may be configured or pre-configured for the wireless communication system. In some examples, the network may configure the number of monitoring times 310 between two consecutive PSS times 305.

[0131] In some examples, the same time interval may exist between consecutive monitoring times 310. For example, a time interval 320 may exist between monitoring times 310-a and 310-b. The same time interval (e.g., time interval 320) may be between each consecutive monitoring time between PSS time 305-a and PSS time 305-b. For example, a time interval 320 may exist between monitoring time 310-m (e.g., the penultimate monitoring time in this set of monitoring times) and monitoring time 310-n (e.g., the last monitoring time in this set of monitoring times).

[0132] In some examples, the time interval between continuous monitoring events 310 can be a certain number of time slots (e.g., an integer number of time slots). For example, there may be a time interval between PSS events 305-a and PSS events 305-b. There are 310 monitoring opportunities, and PSS can have The periodicity of each time slot. The time interval 320 between continuous monitoring opportunities 310 can be equal to... .

[0133] A time gap 315 may exist between the end of PSS timing 305 and the first monitoring timing 310 in the set of monitoring timings 310. For example, time gap 315 may be between PSS timing 305-a and monitoring timing 310-a. In some examples, time gap 315 may be fixed or pre-configured for the wireless communication system. In some examples, the network may configure time gap 315. For example, the network entity 105 transmitting the PSS may configure time gap 315 between the end of PSS timing 305 and the first monitoring timing 310 in the set of monitoring timings 310. In some examples, a symbol offset may be defined if the start of the signal within a monitoring timing is not aligned with the PSS during PSS timing 305. For example, the network may configure the symbol offset based on the misalignment between the signal transmitted during monitoring timing 310-a and the PSS transmitted during PSS timing 305-a.

[0134] In some examples, monitoring timing 310 may be associated with different cells. For example, the index for monitoring timing 310 for a cell may be determined based on the cell identifier of that cell. For example, a first cell may transmit a signal (e.g., SSS or WUS or both) during monitoring timing 310-a, and a second cell may transmit a signal (e.g., SSS or WUS or both) during monitoring timing 310-b. The timing index for monitoring timing 310 for a cell may be based on, for example... To determine, among which .

[0135] In some examples, network entity 105 may send an SSS between PSS times 305. For example, UE 115 may receive a PSS during PSS time 305-a, and UE 115 may monitor an SSS during one or more of a set of monitoring times 310 between PSS time 305-a and PSS time 305-b. The generation of the SSS sequence received by the environmental IoT device may be similar to the generation of the SSS sequence received by other devices, such as SSS for NR signaling. For example, network entity 105 or the cell may use an m-sequence to generate an SSS sequence for the environmental IoT device.

[0136] In some examples, one SSS sequence may exist for each monitoring time slot 310. For example, the first cell may transmit the first SSS sequence during monitoring time slot 310-a. UE 115 may associate the received waveform with a single SSS sequence per time slot. For example, UE 115 may receive a waveform carrying the first SSS sequence during monitoring time slot 310-a, and UE 115 may associate the received waveform with the first SSS sequence without buffering. For example, in other systems, UE 115 may attempt to associate the frequency-corrected waveform with each possible SSS sequence by searching for each candidate signal (which may include 1008 different sequences). In some specific implementations where a single cell transmits a single SSS sequence per monitoring time slot, UE 115 can search for the SSS with low computational complexity.

[0137] In some examples, network entity 105 may transmit WUS during monitoring time 310. For example, monitoring time 310 may be a WUS monitoring time, and UE 115 may monitor WUS during a WUS monitoring time. The WUS transmitted during monitoring time 310 may be a broadcast WUS or transmitted using broadcast signaling. In some examples, each WUS monitoring time may be associated with a different cell. For example, different cells may transmit WUS in each monitoring time 310 between PSS time 305-a and PSS time 305-b. For example, a first cell may transmit WUS during monitoring time 310-a, and a second cell may transmit WUS during monitoring time 310-b. In some cases, a cell may transmit WUS during monitoring time 310 in addition to or instead of transmitting SSS during a monitoring time.

[0138] The WUS transmitted during monitoring time 310 can be used for synchronization. For example, UE 115 can perform fine-tuned timing synchronization based on the WUS transmitted during monitoring time 310. In some examples, the WUS may include a preamble and a payload. The preamble may be a cell-specific sequence and may be based on the cell identifier of the cell transmitting the WUS. In some examples, the preamble may be a random access channel preamble. In some examples, the payload of the WUS may indicate the configuration for system information requests. For example, the WUS may indicate the time and frequency resources available for UE 115 to transmit system information requests. In some examples, the WUS may indicate information such as: cell prohibition information, which types of ambient IoT devices are supported, the presence of auxiliary nodes for ambient IoT devices, in-frequency cell reselection information, or any combination thereof.

[0139] UE 115 may send a request for system information based on WUS. If UE 115 has not yet obtained system information (e.g., a system information message) or the system information at UE 115 is outdated, UE 115 may send a preamble on the time and frequency resources indicated by the WUS to request system information. In some examples, UE 115 may determine that the system information stored at UE 115 is outdated based on indicators in the WUS (such as value labels in the WUS payload). The preamble used for the request may be selected based on the type of system information requested. For example, if UE 115 is requesting complete or all system information, UE 115 may send a first preamble, or if UE 115 is requesting a system information update, UE 115 may send a second preamble. Based on the requested preamble, the cell or network entity 105 receiving the request may determine the information used or how to send the system information block.

[0140] In some examples, the resources used for system information requests can be beam-specific. For example, UE 115 may select the resource for sending the request for system information based on the beam index of PSS or WUS, or both. In some examples, WUS may indicate a set of resources, and each resource in this set may correspond to a different beam. In some cases, the transmission of a preamble may correspond to or serve as an acknowledgment for WUS (e.g., for broadcast WUS). Different UEs 115 may send the same preamble, and the network entity 105 receiving the preamble may detect that the preamble has been received, but may not be able to distinguish between different UEs 115. After UE 115 sends the preamble to network entity 105, UE 115 may monitor the response from network entity 105 to obtain system information.

[0141] Network entity 105 may receive a preamble and send system information in response. For example, network entity 105 may send an SIB in response to the preamble. The SIB may indicate information such as: SFN, resource pool configuration for environmental IoT devices, RACH configuration for initial access, WUS monitoring configuration for paging signaling, or any combination thereof.

[0142] Figure 4 An example of a system information request configuration 400 supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0143] Network entity 105 may periodically send PSSs for environmental IoT devices (such as UE 115). PSSs for environmental IoT devices may have a longer periodicity than PSSs for other types of devices. In some examples, network entity 105 may use Manchester decoding, OOK decoding, or both to encode the PSS.

[0144] For example, network entity 105 may transmit a PSS during PSS timing 405-a. After one period of PSS, network entity 105 may transmit a PSS during PSS timing 405-b. In some examples, the periodicity of the PSS may be configured for the wireless communication system or may be configured by network entity 105.

[0145] Environmental IoT devices (such as UE 115) can monitor the PSS during PSS timing 405. For example, UE 115 can monitor the PSS during PSS timing 405-a. UE 115 can determine the slot length or slot duration based on searching for or receiving the PSS. UE 115 can search for the PSS and perform coarse time synchronization based on the PSS.

[0146] A set of SSS opportunities may exist between consecutive PSS opportunities (such as between PSS opportunity 405-a and PSS opportunity 405-b). For example, there may be a set of SSS opportunities between consecutive PSS opportunities. Each SSS timing may be associated with a different cell or a different network entity 105 in some examples. For example, a first cell may send a first SSS sequence during a first SSS timing, and a second cell may send a second SSS sequence during a second SSS timing.

[0147] In some examples, a time gap may exist between PSS timing 405 and the first SSS timing 410 in the set of SSS timings 410. For example, a first time gap may exist between PSS timing 405-a and SSS timing 410-a. In some examples, a second time gap may exist between consecutive SSS timings 410. In some examples, the first time gap may be pre-configured by the network or can be configured by the network. In some examples, the second time gap may be pre-configured by the network or can be configured by the network. The second time gap may be based on the number of SSS timings 410 between PSS timings 405. In some examples, the number of SSS timings 410 between PSS timings 405 may be pre-configured by the network or can be configured by the network.

[0148] UE 115 can monitor SSS during SSS timing 410. For example, UE 115 can monitor SSS during SSS timing 410-a. The cell can transmit an SSS sequence during SSS timing 410-a. UE 115 can associate a waveform carrying an SSS sequence with an SSS sequence associated with the same cell or SSS timing 410-a, or both. UE 115 can perform fine-grained time synchronization based on the received SSS.

[0149] After synchronization, UE 115 may monitor one or more WUS opportunities 415 to obtain a WUS, such as broadcasting a WUS. A WUS may trigger UE 115 to transmit a request for system information. In some examples, multiple WUS opportunities 415 may exist per PSS period or SSS period. For example, WUS opportunities 415-a, WUS opportunity 415-b, and WUS opportunity 415-c may occur after SSS opportunity 410-a. In some examples, UE 115 may monitor each WUS opportunity 415 until UE 115 receives a WUS. In some examples, each WUS opportunity 415 may be associated with a different cell, and UE 115 may monitor the WUS opportunities 415 associated with the cell to which UE 115 is synchronized.

[0150] UE 115 can monitor WUS timing 415-b and receive broadcast WUS. In some examples, broadcast WUS may indicate information associated with an environmental IoT device. For example, broadcast WUS may indicate cell prohibition information, the type of supported environmental IoT device, the presence of auxiliary nodes for the environmental IoT device, inter-frequency cell reselection indicators, or any combination thereof. In some examples, broadcast WUS may indicate at least some information indicated by the Master Information Block (MIB).

[0151] In some examples, broadcasting WUS may indicate a resource associated with a request for system information. UE 115 may use this resource to send preamble 420 to request system information. A random access preamble may be an example of preamble 420. In some examples, UE 115 may send preamble 420 based on the fact that UE 115 has not yet received a system information message or based on the fact that the system information stored at UE 115 is outdated. In some examples, the type of preamble 420 or the sequence of preamble 420 may correspond to a request for different amounts of system information. For example, UE 115 may use preamble 420 to request complete system information or system information updates.

[0152] Network entity 105 may receive preamble 420 and, in response, send system information to UE 115. For example, network entity 105 may send SIB 425 in response to preamble 420. SIB 425 may indicate SFN, resource pool configuration for environmental IoT devices, RACH configuration for initial access, and WUS monitoring configuration for paging signaling, or any combination thereof.

[0153] In some examples, SIB 425 may indicate carrier information for RACH configuration or WUS monitoring configuration, or both. For example, if RACH signaling or WUS transmission is supported on a different carrier than the carrier used for transmitting PSS, SSS, and broadcasting WUS, SIB 425 may indicate carrier information for RACH configuration or WUS monitoring configuration. If multiple carriers are configured or supported for RACH signaling or WUS transmission, or both, UE 115 may select a carrier based on UE 115's identifier or the identifier of a subgroup of UE 115. For example, multiple carriers may be configured for RACH signaling, and SIB 425 may indicate carrier information for each of the multiple subcarriers. UE 115 may select a carrier from the multiple carriers based on UE 115's identifier, and UE 115 may transmit or receive RACH signaling via the selected carrier. Based on the information indicated by SIB 425, UE 115 may periodically monitor WUS to obtain paging signaling according to the WUS monitoring configuration. Alternatively, UE115 may perform a random access procedure to establish a connection with network entity 105 according to the RACH configuration indicated by SIB 425.

[0154] In some examples, UE 115 can operate in an inactive state before receiving a broadcast WUS. For example, UE 115 can operate in an inactive state during inactive time 430-a. When UE 115 receives a broadcast WUS during WUS time 415-b, UE 115 can switch to an active state to receive or send signaling. For example, UE 115 can operate in an active state during active time 435. After receiving SIB 425, UE 115 can switch to an inactive state 430-b. For example, UE 115 can switch to an inactive state 430-b until UE 115 monitors WUS signaling according to the WUS configuration or performs a random access procedure according to the RACH configuration.

[0155] Figure 5 An example of a process flow 500 supporting synchronization and cell search for environmental IoT devices is shown, according to one or more aspects of this disclosure.

[0156] Process flow 500 can implement aspects of wireless communication system 100 or wireless communication system 200. For example, process flow 500 can exemplify operations between UE 115-b and network entity 105-b, which can be corresponding examples of UE 115 and network entity 105 described herein. In the following description of process flow 500, operations between UE 115-b and network entity 105-b may be transmitted in a different order than the example order shown, or operations performed by UE 115-b and network entity 105-b may be performed in a different order or at different times. Some operations may also be omitted from process flow 500, and other operations may be added to process flow 500.

[0157] Although process flow 500 shows a single network entity 105, different entities or devices in the network can communicate with UE 115-b, as shown in reference 115-b. Figure 5 As shown and described. For example, UE 115-b can send signaling to or receive signaling from different cells that can be provided by network entity 105-b. In some examples, different network entities 105 can provide different cells.

[0158] UE 115-b can be an example of an environmental IoT device. For example, UE 115-b can be capable of active transmission, including non-backscatter communication. In some examples, UE 115-b may also support backscatter communication. UE 115-b can be an example of a lower-complexity device and can have low maximum instantaneous power consumption.

[0159] At 505, UE 115-b can monitor the first PSS during the first PSS timing period. For example, network entity 105-b can output the first PSS during the first PSS timing period, and UE 115-b can receive the first PSS during the first PSS timing period. The first PSS may have a first periodicity. In some examples, the PSS associated with an ambient IoT device may have a longer periodicity than the PSS associated with a non-ambient IoT device (such as a PSS used for NR). UE 115-b can perform coarse time synchronization based on the PSS.

[0160] In some examples, UE 115-b may monitor another signal associated with synchronization. For example, UE 115-b may receive an SSS or WUS during a monitoring period within a set of monitoring periods between the first PSS and the second PSS. The consecutive monitoring periods within this set of monitoring periods may be separated in time by a first gap. In some examples, each monitoring period within this set of monitoring periods may be associated with a different cell. The different cells may be provided by network entity 105-b or by one or more individual network entities 105.

[0161] In some examples, UE 115-b may receive SSS at 510. For example, this set of monitoring times may be a set of SSS monitoring times. UE 115-b may perform fine-grained time synchronization based on SSS.

[0162] At 515, UE 115-b can receive WUS. For example, UE 115-b can receive WUS during a WUS monitoring period. In an example where UE 115-b receives SSS, UE 115-b can monitor one or more WUS periods in a set of WUS periods, and the first WUS period in the set of WUS periods can be offset from the SSS by a fixed duration in time.

[0163] In some examples, this set of monitoring times can be a set of WUS times, and UE 115-b can receive WUS during the WUS times in this set of WUS times. For example, network entity 105-b may not output SSS, and UE 115-b may perform fine-grained time synchronization based on WUS.

[0164] At 520, UE 115-b may send a system information request. For example, UE 115-b may send a request for system information in response to a WUS request via resources indicated by the WUS. For example, the WUS may indicate resources associated with the request for system information, or time and frequency resources. In some examples, the request for system information may be a preamble, such as a random access preamble. In some examples, the preamble may request complete system information or system information updates. UE 115-b may send a request for system information based on the fact that system information has not yet been received or based on the fact that the system information stored at UE 115-b is outdated.

[0165] In some examples, UE 115-b may send a request for system information to network entity 105-b. Additionally or alternatively, UE 115-b may send a request for system information to the cell transmitting WUS. The cell transmitting WUS may be provided by network entity 105-b or by another network entity 105.

[0166] At 525, UE 115-b can receive system information in response to a request for system information. For example, UE 115-b can receive an SIB in response to a request for system information. The SIB can indicate an SFN, a resource pool configuration for environmental IoT devices, a RACH configuration for initial access, a WUS monitoring configuration for paging signaling, or any combination thereof.

[0167] In some examples, UE 115-b and network entity 105-b may perform a random access procedure at 530. For example, UE 115-b may perform a random access procedure based on a RACH configuration for initial access indicated by the SIB. In some examples, UE 115-b may monitor WUS timings at 535. For example, UE 115-b may monitor wake-up signals during WUS timings to obtain paging signaling based on a WUS monitoring configuration for paging signaling indicated by the SIB.

[0168] Figure 6 A block diagram 600 illustrates a device 605 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, communication manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0169] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to synchronization and cell search for environmental IoT devices). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0170] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to synchronization and cell search for environmental IoT devices, including packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0171] The communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be examples of components used to perform various aspects of synchronization and cell search for IoT devices in an environment as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0172] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), graphics processing unit (GPU), neural processing unit (PNU), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0173] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communication management software) executed by at least one processor (e.g., referred to as processor executable code). If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, GPU, NPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0174] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated in combination with the receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0175] The communication manager 620 may support wireless communication according to examples disclosed herein. For example, the communication manager 620 may be capable of, configured to, or operable to support components for receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The communication manager 620 may be capable of, configured to, or operable to support components for receiving an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and the second PSS, wherein consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0176] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., at least one processor that controls or is otherwise coupled to receiver 610, transmitter 615, communication manager 620, or a combination thereof) can support techniques for reducing processing and improving synchronization with lower complexity.

[0177] Figure 7 A block diagram 700 illustrates a device 705 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, communication manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0178] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels related to synchronization and cell search for environmental IoT devices). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0179] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels, such as control channels, data channels, and information channels related to synchronization and cell search for environmental IoT devices, including packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0180] Device 705 or its various components may be examples of parts used to perform various aspects of synchronization and cell search for environmental IoT devices as described herein. For example, communication manager 720 may include PSS component 725, monitoring timing component 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0181] The communication manager 720 may support wireless communication according to examples disclosed herein. The PSS component 725 is capable of, configured to, or operable to support components for receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The monitoring timing component 730 is capable of, configured to, or operable to support components for receiving an SSS or WUS during a monitoring timing within a set of multiple monitoring timings between the first and second PSS, wherein consecutive monitoring timings within this set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing within this set of multiple monitoring timings is associated with a different cell.

[0182] Figure 8 A block diagram 800 is shown of a communication manager 820 supporting synchronization and cell search for environmental IoT devices according to one or more aspects of this disclosure. The communication manager 820 may be an example of a communication manager 620, a communication manager 720, or aspects thereof as described herein. The communication manager 820 or its various components may be examples of parts for performing the various aspects of synchronization and cell search for environmental IoT devices as described herein. For example, the communication manager 820 may include a PSS component 825, a monitoring timing component 830, a system information request component 835, an association component 840, an SIB component 845, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0183] The communication manager 820 may support wireless communication according to examples disclosed herein. The PSS component 825 is capable of, configured to, or operable to support components for receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The monitoring timing component 830 is capable of, configured to, or operable to support components for receiving an SSS or WUS during a monitoring timing within a set of multiple monitoring timings between the first and second PSS, wherein consecutive monitoring timings within this set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing within this set of multiple monitoring timings is associated with a different cell.

[0184] In some examples, the system information request component 835 is capable of, configured to, or able to operate to support components for sending requests for system information in response to a resource indicated by the WUS via the WUS.

[0185] In some examples, in order to support sending requests for system information, the system information request component 835 can be, configured, or operated to support components for sending a preamble indicating a request for complete system information or a request for system information updates.

[0186] In some examples, requests for system information are sent based on the expiration of system information stored at the UE.

[0187] In some examples, SIB component 845 is capable of, configured to, or able to operate to support a component for receiving system information blocks in response to a request for system information.

[0188] In some examples, the system information block indicates the system frame number, the resource pool configuration for the environmental IoT device, the random access channel configuration for initial access, the WUS monitoring configuration for paging signaling, or any combination thereof.

[0189] In some examples, the system information block indicates carrier information for random access channel configuration or WUS monitoring configuration for paging signaling, or both.

[0190] In some examples, SIB component 845 is capable of, configured to, or able to operate to support the use of a carrier indicated by a system information block to monitor one or more WUS monitoring opportunities to obtain paging signaling for a UE-based identifier or an identifier that includes a subgroup of UEs.

[0191] In some examples, the monitoring timing component 830 is capable of, configured to, or operable to support components for monitoring one or more WUS timings in a set of multiple WUS timings, wherein the set of multiple monitoring timings between a first PSS and a second PSS is an SSS timing, and wherein the first WUS timing in the set of multiple WUS timings has a fixed duration of time offset from the SSS.

[0192] In some examples, WUS indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with SSS, the presence of auxiliary nodes for environmental IoT devices, information for in-frequency cell reselection, or any combination thereof.

[0193] In some examples, the PSS component 825 is capable of, can be configured to, or is able to operate to support components for decoding the first PSS or SSS or both based on on-keying encoding or Manchester encoding or both.

[0194] In some examples, the first PSS is received during a time slot within a set of multiple time slots in the first PSS timing. In some examples, each time slot in this set of multiple time slots is associated with a different beam direction.

[0195] In some examples, the association component 840 is capable of, can be configured to, or can operate to support components for associating the waveform of the SSS with the SSS sequence during monitoring.

[0196] In some examples, in order to support the reception of SSS, the monitoring timing component 830 is capable of being configured to operate to support components for receiving SSS during a set of multiple time slots in a monitoring timing, wherein each of the multiple time slots is associated with a different beam direction.

[0197] In some examples, the first monitoring opportunity in this set of multiple monitoring opportunities has a fixed duration in time with the first PSS offset.

[0198] In some examples, the first time interval is based on the first periodicity and the number of monitoring opportunities in that set.

[0199] Figure 9A diagram of a system 900 including device 905 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or a component including such devices. Device 905 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entity 105, UE 115, or a combination thereof). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller (e.g., I / O controller 910), a transceiver 915, one or more antennas 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 945).

[0200] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0201] In some cases, device 905 may include a single antenna. However, in other cases, device 905 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925 using a wired or wireless link, as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0202] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable, or processor-executable code, such as code 935. Code 935 may include instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 930 may include a basic I / O system (BIOS), etc., which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0203] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, GPUs, NPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to use a memory controller to operate a memory array. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting synchronization and cell search for environmental IoT devices). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, wherein at least one processor 940 and at least one memory 930 are configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code 935 (e.g., processor-executable code) stored in at least one memory 930 or otherwise.

[0204] The communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The communication manager 920 may be capable of, configured to, or operable to support components for receiving an SSS or WUS during a monitoring timing in a set of multiple monitoring timings between the first PSS and the second PSS, wherein consecutive monitoring timings in the set of multiple monitoring timings are temporally separated by a first time interval, and each monitoring timing in the set of multiple monitoring timings is associated with a different cell.

[0205] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving user experience related to reducing processing, lowering power consumption, and improving processing capabilities.

[0206] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported by or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of synchronization and cell search for environmental IoT devices as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0207] Figure 10 A block diagram 1000 of a device 1005 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of various aspects of network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, communication manager 1020), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0208] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0209] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0210] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be examples of components used to perform various aspects of synchronization and cell search for IoT devices in an environment as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be able to perform one or more of the functions described herein.

[0211] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, GPU, NPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0212] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., as communication management software) executed by at least one processor (e.g., referred to as processor executable code). If implemented in code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be executed by a general-purpose processor, DSP, CPU, GPU, NPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0213] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with the receiver 1010, the transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0214] The communication manager 1020 may support wireless communication according to examples disclosed herein. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The communication manager 1020 may be capable of, configured to, or operable to support components for outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and the second PSS, wherein consecutive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0215] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., at least one processor that controls or is otherwise coupled to receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof) can support techniques for reduced processing and improved synchronization for lower-complexity devices.

[0216] Figure 11 A block diagram 1100 of a device 1105 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, communication manager 1120), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0217] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0218] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0219] Device 1105 or its various components may be examples of parts used to perform various aspects of synchronization and cell search for IoT devices in an environment as described herein. For example, communication manager 1120 may include PSS component 1125, transmission timing component 1130, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0220] The communication manager 1120 may support wireless communication according to examples disclosed herein. The PSS component 1125 is capable of, configured to, or operable to support components for outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The transmission timing component 1130 is capable of, configured to, or operable to support components for outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first and second PSS, wherein consecutive transmission timings in this set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in this set of multiple transmission timings is associated with a different cell.

[0221] Figure 12A block diagram 1200 is shown of a communication manager 1220 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure. The communication manager 1220 may be an example of a communication manager 1020, a communication manager 1120, or aspects thereof as described herein. The communication manager 1220 or its various components may be examples of parts for performing various aspects of synchronization and cell search for IoT devices in an environment as described herein. For example, the communication manager 1220 may include a PSS component 1225, a transmission timing component 1230, a system information request component 1235, an SIB component 1240, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses). Communication may include communication within a protocol layer of a protocol stack, communication associated with a logical channel of the protocol stack (e.g., between protocol layers of the protocol stack, within a device, component, or virtualization component associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0222] The communication manager 1220 may support wireless communication according to examples disclosed herein. The PSS component 1225 is capable of, configured to, or operable to support components for outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The transmission timing component 1230 is capable of, configured to, or operable to support components for outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first and second PSS, wherein consecutive transmission timings in this set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in this set of multiple transmission timings is associated with a different cell.

[0223] In some examples, the system information request component 1235 is capable of being configured or operated to support components for obtaining system information in response to a resource indicated by the WUS via the WUS.

[0224] In some examples, in order to support requests for system information, the system information request component 1235 can be configured or operated to support components for obtaining a preamble indicating a request for complete system information or a request for system information updates.

[0225] In some examples, SIB component 1240 is capable of, configured to, or able to operate to support a component for outputting system information blocks in response to a request for system information.

[0226] In some examples, the system information block indicates the system frame number, the resource pool configuration for the environmental IoT device, the random access channel configuration for initial access, the WUS monitoring configuration for paging signaling, or any combination thereof.

[0227] In some examples, the system information block indicates carrier information for random access channel configuration or WUS monitoring configuration for paging signaling, or both.

[0228] In some examples, SIB component 1240 is capable of, configured to, or able to operate to support the output of WUS for paging signaling via a carrier indicated by a system information block for a UE-based identifier or an identifier including a subgroup of UEs during one or more WUS transmission times.

[0229] In some examples, WUS is output during a WUS timing within a set of multiple WUS timings. In some examples, this set of multiple transmission timings between the first PSS and the second PSS is an SSS timing. In some examples, the first WUS timing within this set of multiple WUS timings has a fixed duration offset from the SSS timing.

[0230] In some examples, WUS indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with SSS, the presence of auxiliary nodes for environmental IoT devices, information for in-frequency cell reselection, or any combination thereof.

[0231] In some examples, PSS component 1225 is capable of, configured to, or able to operate to support components for encoding the first PSS or SSS or both using on / off keying encoding or Manchester encoding or both.

[0232] In some examples, the first PSS is output using a first beam direction during a time slot within a set of multiple time slots in the first PSS timing. In some examples, each time slot in this set of multiple time slots is associated with a different beam direction.

[0233] In some examples, in order to support output SSS, the transmission timing component 1230 is capable of, can be configured to, or can operate to support components for outputting SSS during a time slot in a set of multiple time slots in the transmission timing using a first beam direction, wherein each time slot in the set of multiple time slots is associated with a different beam direction and a different SSS sequence.

[0234] Figure 13A diagram of a system 1300 including device 1305 supporting synchronization and cell search for IoT devices in an environment, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 may communicate with other network devices or network equipment, such as one or more of network entity 105, UE 115, or any combination thereof. Communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components that support output and enable communication, such as a communication manager 1320, a transceiver 1310, one or more antennas 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1340).

[0235] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components or configured to be coupled to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0236] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable, or processor-executable code, such as code 1330. Code 1330 may include instructions that, when executed by one or more of the at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by one of the at least one processor 1335, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may include a BIOS, etc., that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0237] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, GPUs, NPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., functions or tasks supporting synchronization and cell search for environmental IoT devices). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, wherein at least one processor 1335 and at least one memory 1325 are configured to perform the various functions described herein. At least one processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories in at least one memory 1325). In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1335 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325)) or components that receive or acquire input and process the input to produce, generate, or acquire a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1335 or a processing system including at least one processor 1335 may be configured, configured to, or operable to cause the device 1305 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1325 or otherwise.

[0238] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more processors of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330, and at least one processor 1335 may be located in one of the different components or partitioned between the different components).

[0239] In some examples, the communication manager 1320 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 may manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communication with one or more other network devices 105 and may include a controller or scheduler for (e.g., cooperating with one or more other network devices) controlling communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0240] The communication manager 1320 may support wireless communication according to examples disclosed herein. For example, the communication manager 1320 may be capable of, configured to, or operable to support components for outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The communication manager 1320 may be capable of, configured to, or operable to support components for outputting an SSS or WUS during a transmission timing in a set of multiple transmission timings between the first PSS and the second PSS, wherein consecutive transmission timings in the set of multiple transmission timings are temporally separated by a first time interval, and each transmission timing in the set of multiple transmission timings is associated with a different cell.

[0241] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support technologies for improving user experience related to reducing processing, lowering power consumption, and improving processing capabilities.

[0242] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors in at least one processor 1335 to cause the device 1305 to perform various aspects of synchronization and cell search for environmental IoT devices as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0243] Figure 14 A flowchart illustrating a method 1400 for synchronization and cell search for an environmental IoT device, according to one or more aspects of this disclosure, is shown. Operation of method 1400 may be implemented by a UE or its components as described herein. For example, operation of method 1400 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0244] At 1405, the method may include receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The operation of 1405 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1405 may be derived from references... Figure 8 The described PSS component 825 is used to perform this.

[0245] At 1410, the method may include receiving an SSS or WUS during a monitoring time within a set of multiple monitoring times between a first PSS and a second PSS, wherein consecutive monitoring times within this set of multiple monitoring times are temporally separated by a first time interval, and each monitoring time within this set of multiple monitoring times is associated with a different cell. Operation of 1410 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1410 may be derived from references... Figure 8 The monitoring timing component 830 is used to perform the described monitoring.

[0246] Figure 15 A flowchart illustrating a method 1500 for synchronization and cell search for an environmental IoT device, according to one or more aspects of this disclosure, is shown. Operation of method 1500 may be implemented by a UE or its components as described herein. For example, operation of method 1500 may be performed by, as referenced... Figures 1 to 9 The UE 115 described herein performs the following: In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0247] At 1505, the method may include receiving a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The operation of 1505 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1505 may be derived from references... Figure 8 The described PSS component 825 is used to perform this.

[0248] At 1510, the method may include receiving an SSS or WUS during a monitoring time within a set of multiple monitoring times between a first PSS and a second PSS, wherein consecutive monitoring times within this set of multiple monitoring times are temporally separated by a first time interval, and each monitoring time within this set of multiple monitoring times is associated with a different cell. Operation of 1510 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1510 may be derived from references... Figure 8 The monitoring timing component 830 is used to perform the described monitoring.

[0249] At 1515, the method may include sending a request for system information in response to a resource indicated by WUS. The operation of 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1515 may be as described in the references... Figure 8 The system information request component 835 described herein is used to execute this request.

[0250] Figure 16A flowchart illustrating a method 1600 for synchronization and cell search of IoT devices in an environment, according to one or more aspects of this disclosure, is shown. Operation of method 1600 may be implemented by a network entity or its components as described herein. For example, operation of method 1600 may be implemented by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The described network entity performs the functions. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described functions.

[0251] At 1605, the method may include outputting a first PSS during a first PSS timing, wherein the first PSS timing has a first periodicity. The operation at 1605 may be performed according to examples as disclosed herein. In some examples, aspects of the operation at 1605 may be derived from references... Figure 12 The described PSS component 1225 is used to perform this.

[0252] At 1610, the method may include outputting an SSS or WUS during a transmission opportunity within a set of multiple transmission opportunities between a first PSS and a second PSS, wherein consecutive transmission opportunities within this set of multiple transmission opportunities are temporally separated by a first time interval, and each transmission opportunity within this set of multiple transmission opportunities is associated with a different cell. The operation of 1610 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1610 may be derived from references... Figure 12 The described sending timing component 1230 is used to execute this.

[0253] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication at a UE, the method comprising: receiving a first primary synchronization signal during a first primary synchronization signal timing, wherein the first primary synchronization signal timing has a first periodicity; and receiving a secondary synchronization signal or a wake-up signal during a monitoring timing of a plurality of monitoring timings between the first primary synchronization signal and a second primary synchronization signal, wherein the consecutive monitoring timings of the plurality of monitoring timings are temporally separated by a first time interval, and each monitoring timing of the plurality of monitoring timings is associated with a different cell.

[0254] Aspect 2: According to the method of aspect 1, the method further includes: sending a request for system information via a resource indicated by the wake-up signal in response to the wake-up signal.

[0255] Aspect 3: According to the method of aspect 2, sending the request for system information includes: sending a preamble indicating a request for complete system information or a request for system information updates.

[0256] Aspect 4: The method according to any one of Aspects 2 to 3, wherein the request for system information is sent at least in part based on the expiration of system information stored at the UE.

[0257] Aspect 5: The method according to any one of Aspects 2 to 4, the method further comprising: receiving a system information block in response to the request for system information.

[0258] Aspect 6: According to the method of aspect 5, wherein the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a wake-up signal monitoring configuration for paging signaling, or any combination thereof.

[0259] Aspect 7: According to the method of aspect 6, wherein the system information block indicates carrier information for the random access channel configuration or the wake-up signal monitoring configuration for paging signaling, or both.

[0260] Aspect 8: The method according to aspect 7 further includes: at least in part based on the identifier of the UE or the identifier of a subgroup including the UE, monitoring one or more wake-up signal monitoring opportunities via a carrier indicated by the system information block to obtain paging signaling.

[0261] Aspect 9: The method according to any one of aspects 1 to 8, the method further comprising: monitoring one or more wake-up signal timings among a plurality of wake-up signal timings, wherein the plurality of monitoring timings between the first primary synchronization signal and the second primary synchronization signal are secondary synchronization signal timings, and wherein the first wake-up signal timing among the plurality of wake-up signal timings is offset from the secondary synchronization signal by a fixed duration in time.

[0262] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the wake-up signal indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with the secondary synchronization signal, the presence of an auxiliary node for an environmental Internet of Things device, information for in-frequency cell reselection, or any combination thereof.

[0263] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: decoding the first primary synchronization signal or the secondary synchronization signal or both based at least in part on on / off keying or Manchester encoding or both.

[0264] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the first primary synchronization signal is received during a time slot of a plurality of time slots in the timing of the first primary synchronization signal, each of the plurality of time slots being associated with a different beam direction.

[0265] Aspect 13: The method according to any one of aspects 1 to 12, the method further comprising: associating the waveform of the auxiliary synchronization signal with the sequence of auxiliary synchronization signals during the monitoring timing.

[0266] Aspect 14: The method according to any one of Aspects 1 to 13, wherein receiving the secondary synchronization signal comprises: receiving the secondary synchronization signal during a time slot of a plurality of time slots in the monitoring timing, wherein each of the plurality of time slots is associated with a different beam direction.

[0267] Aspect 15: The method according to any one of aspects 1 to 14, wherein the first monitoring opportunity of the plurality of monitoring opportunities is offset from the first master synchronization signal by a fixed duration in time.

[0268] Aspect 16: The method according to any one of Aspects 1 to 15, wherein the first time interval is based at least in part on the first periodicity and the number of the plurality of monitoring opportunities.

[0269] Aspect 17: A method for wireless communication at a network entity, the method comprising: outputting a first primary synchronization signal during a first primary synchronization signal timing, wherein the first primary synchronization signal timing has a first periodicity; and outputting a secondary synchronization signal or a wake-up signal during a transmission timing of a plurality of transmission timings between the first primary synchronization signal and a second primary synchronization signal, wherein the successive transmission timings of the plurality of transmission timings are temporally separated by a first time interval, and each of the plurality of transmission timings is associated with a different cell.

[0270] Aspect 18: The method according to aspect 17, the method further comprising: responding to a wake-up signal to obtain a request for system information via a resource indicated by the wake-up signal.

[0271] Aspect 19: According to the method of aspect 18, the request for system information includes: obtaining a preamble indicating a request for complete system information or a request for an update of system information.

[0272] Aspect 20: The method according to any one of aspects 18 to 19, the method further comprising: outputting a system information block in response to the request for system information.

[0273] Aspect 21: According to the method of aspect 20, wherein the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a wake-up signal monitoring configuration for paging signaling, or any combination thereof.

[0274] Aspect 22: According to the method of aspect 21, wherein the system information block indicates carrier information for the random access channel configuration or the wake-up signal monitoring configuration for paging signaling, or both.

[0275] Aspect 23: The method according to aspect 22 further includes: outputting a wake-up signal for paging signaling via a carrier indicated by the system information block at least in part based on the identifier of the UE or the identifier of a subgroup including the UE during one or more wake-up signal transmission times.

[0276] Aspect 24: The method according to any one of Aspects 18 to 23, wherein the wake-up signal is output during a wake-up signal timing among a plurality of wake-up signal timings, the plurality of transmission timings between the first primary synchronization signal and the second primary synchronization signal are secondary synchronization signal timings, and the first wake-up signal timing among the plurality of wake-up signal timings is offset from the secondary synchronization signal by a fixed duration in time.

[0277] Aspect 25: The method according to any one of Aspects 18 to 24, wherein the wake-up signal indicates timing synchronization information, cell prohibition information, the type of device supported by the cell associated with the secondary synchronization signal, the presence of an auxiliary node for an environmental Internet of Things device, information for in-frequency cell reselection, or any combination thereof.

[0278] Aspect 26: The method according to any one of Aspects 17 to 25, the method further comprising: encoding the first primary synchronization signal or the secondary synchronization signal or both using on / off keying or Manchester encoding or both.

[0279] Aspect 27: The method according to any one of Aspects 17 to 26, wherein the first primary synchronization signal is output using a first beam direction during a time slot in a plurality of time slots in the timing of the first primary synchronization signal, and each of the plurality of time slots is associated with a different beam direction.

[0280] Aspect 28: The method according to any one of Aspects 17 to 27, wherein outputting the auxiliary synchronization signal comprises: outputting the auxiliary synchronization signal during a time slot of a plurality of time slots in the transmission timing using a first beam direction, wherein each of the plurality of time slots is associated with a different beam direction and a different sequence of auxiliary synchronization signals.

[0281] Aspect 29: A UE for wireless communication, the UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 1 to 16.

[0282] Aspect 30: A UE for wireless communication, the UE including at least one component for performing the method according to any one of aspects 1 to 16.

[0283] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by at least one processor to perform the method according to any one of aspects 1 to 16.

[0284] Aspect 32: A network entity for wireless communication, the network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of aspects 17 to 28.

[0285] Aspect 33: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 17 to 28.

[0286] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by at least one processor to perform a method according to any one of aspects 17 to 28.

[0287] It should be noted that the methods described herein describe possible specific implementations. These operations and steps can be rearranged or otherwise modified, and other specific implementations are possible. Furthermore, aspects from two or more of these methods can be combined.

[0288] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0289] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0290] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, GPU, NPU, FPGA, or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described function or operation individually or jointly.

[0291] The functionality described herein can be implemented using hardware, software executed by a processor, or any combination thereof. When implemented using software executed by a processor, the functionality can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and embodiments are within the scope of this disclosure and the appended claims. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functionality can also be physically located in various locations, including various parts distributed such that the functionality is implemented in different physical locations.

[0292] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, phase-change memory, compact disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0293] As used herein (including in the claims), the word "or" in an enumeration of items (e.g., including enumerations of items ending with phrases such as "at least one of..." or "one or more of...") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". As used herein, when the term "and / or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be used. For example, if a composition is described as containing components A, B and / or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B and C.

[0294] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0295] The terms "determine" or "identify" encompass a variety of actions, and therefore, "determine" or "identify" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), and ascertainment. Additionally, "determine" or "identify" can include receiving (such as receiving information or signaling, e.g., receiving information or signaling for determination, receiving information or signaling for identification), accessing (such as accessing data in memory or accessing information), etc. Furthermore, "determine" or "identify" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0296] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0297] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some of the drawings, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0298] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: A first primary synchronization signal is received during a first primary synchronization signal timing period, wherein the first primary synchronization signal timing period has a first periodicity. as well as A secondary synchronization signal or wake-up signal is received during a monitoring period among a plurality of monitoring periods between the first primary synchronization signal and the second primary synchronization signal, wherein the consecutive monitoring periods among the plurality of monitoring periods are separated in time by a first time interval, and each monitoring period among the plurality of monitoring periods is associated with a different cell.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: In response to the wake-up signal, a request for system information is sent via the resource indicated by the wake-up signal.

3. The UE according to claim 2, wherein, In order to send the request for system information, the one or more processors can operate individually or jointly to execute the code to enable the UE to: Send a preamble indicating a request for complete system information or a request for system information updates.

4. The UE of claim 2, wherein the request for system information is sent at least in part based on the expiration of system information stored at the UE.

5. The UE of claim 2, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive system information block in response to the request for system information.

6. The UE according to claim 5, wherein the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a wake-up signal monitoring configuration for paging signaling, or any combination thereof.

7. The UE of claim 6, wherein the system information block indicates carrier information for the random access channel configuration or the wake-up signal monitoring configuration for paging signaling, or both.

8. The UE of claim 7, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: One or more wake-up signal monitoring opportunities are monitored via a carrier indicated by the system information block, at least in part based on the identifier of the UE or the identifier of a subgroup including the UE, to obtain paging signaling.

9. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: One or more wake-up signal timings among a plurality of wake-up signal timings are monitored, wherein the plurality of monitoring timings between the first primary synchronization signal and the second primary synchronization signal are secondary synchronization signal timings, and wherein the first wake-up signal timing among the plurality of wake-up signal timings is offset from the secondary synchronization signal by a fixed duration in time.

10. The UE of claim 1, wherein the wake-up signal indicates timing synchronization information, cell prohibition information, the device type supported by the cell associated with the secondary synchronization signal, the presence of an auxiliary node for an environmental IoT device, information for in-frequency cell reselection, or any combination thereof.

11. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The first primary synchronization signal or the secondary synchronization signal or both are decoded at least in part based on on / off keying encoding or Manchester encoding or both.

12. The UE of claim 1, wherein the first primary synchronization signal is received during a time slot of a plurality of time slots in the timing of the first primary synchronization signal, and each of the plurality of time slots is associated with a different beam direction.

13. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: The waveform of the auxiliary synchronization signal is associated with the auxiliary synchronization signal sequence during the monitoring period.

14. The UE according to claim 1, wherein, In order to receive the secondary synchronization signal, the one or more processors can operate individually or jointly to execute the code to enable the UE to: The auxiliary synchronization signal is received during a time slot in a plurality of time slots in the monitoring timing, wherein each of the plurality of time slots is associated with a different beam direction.

15. The UE according to claim 1, wherein the first monitoring opportunity of the plurality of monitoring opportunities is offset from the first primary synchronization signal by a fixed duration in time.

16. The UE of claim 1, wherein the first time interval is based at least in part on the first periodicity and the number of the plurality of monitoring opportunities.

17. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: A first primary synchronization signal is output during a first primary synchronization signal timing period, wherein the first primary synchronization signal timing has a first periodicity; and During a transmission opportunity among a plurality of transmission opportunities between the first primary synchronization signal and the second primary synchronization signal, an auxiliary synchronization signal or a wake-up signal is output, wherein the successive transmission opportunities among the plurality of transmission opportunities are separated in time by a first time interval, and each of the plurality of transmission opportunities is associated with a different cell.

18. The network entity of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: In response to the wake-up signal, a request for system information is obtained via the resource indicated by the wake-up signal.

19. The network entity according to claim 18, wherein, In order to obtain the request for system information, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: Obtain a preamble indicating a request for complete system information or a request for system information updates.

20. The network entity of claim 18, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: In response to the request for system information, a system information block is output.

21. The network entity of claim 20, wherein the system information block indicates a system frame number, a resource pool configuration for environmental IoT devices, a random access channel configuration for initial access, a wake-up signal monitoring configuration for paging signaling, or any combination thereof.

22. The network entity of claim 21, wherein the system information block indicates carrier information for the random access channel configuration or the wake-up signal monitoring configuration for paging signaling, or both.

23. The network entity of claim 22, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: A wake-up signal for paging signaling is output via a carrier indicated by the system information block, at least in part based on the identifier of the user equipment (UE) or the identifier of a subgroup including the UE, during one or more wake-up signal transmission opportunities.

24. The network entity according to claim 18, wherein: The wake-up signal is output during one of the multiple wake-up signal timings. The plurality of transmission timings between the first primary synchronization signal and the second primary synchronization signal are secondary synchronization signal timings, and The first wake-up signal timing among the plurality of wake-up signal timings is offset from the auxiliary synchronization signal by a fixed duration in time.

25. The network entity of claim 18, wherein the wake-up signal indicates timing synchronization information, cell prohibition information, the device type supported by the cell associated with the secondary synchronization signal, the presence of an auxiliary node for an environmental IoT device, information for in-frequency cell reselection, or any combination thereof.

26. The network entity of claim 17, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The first primary synchronization signal or the secondary synchronization signal or both are encoded using on / off keying, Manchester encoding, or both.

27. The network entity according to claim 17, wherein: The first primary synchronization signal is output using the first beam direction during a time slot within a plurality of time slots in the timing of the first primary synchronization signal, and Each of the multiple time slots is associated with a different beam direction.

28. The network entity according to claim 17, wherein, In order to output the secondary synchronization signal, the one or more processors can operate individually or jointly to execute the code to enable the network entity to: The auxiliary synchronization signal is output during a time slot in a plurality of time slots in the transmission timing using a first beam direction, wherein each of the plurality of time slots is associated with a different beam direction and a different sequence of auxiliary synchronization signals.

29. A method for conducting wireless communication at a user equipment (UE), the method comprising: A first primary synchronization signal is received during a first primary synchronization signal timing period, wherein the first primary synchronization signal timing period has a first periodicity. as well as A secondary synchronization signal or wake-up signal is received during a monitoring period among a plurality of monitoring periods between the first primary synchronization signal and the second primary synchronization signal, wherein the consecutive monitoring periods among the plurality of monitoring periods are separated in time by a first time interval, and each monitoring period among the plurality of monitoring periods is associated with a different cell.

30. A method for conducting wireless communication at a network entity, the method comprising: A first master synchronization signal is output during a first master synchronization signal timing period, wherein the first master synchronization signal timing period has a first periodicity. as well as During a transmission opportunity among a plurality of transmission opportunities between the first primary synchronization signal and the second primary synchronization signal, an auxiliary synchronization signal or a wake-up signal is output, wherein the successive transmission opportunities among the plurality of transmission opportunities are separated in time by a first time interval, and each of the plurality of transmission opportunities is associated with a different cell.

Images