Systems, Methods, and Devices for Adaptive Paging Early Indication (pei)

This application claims the benefit of U.S. Provisional Application No. 63/676,650, filed Jul. 29, 2024, the content of which is herein incorporated by reference in its entirety for all purposes.

This disclosure relates to wireless communication networks and mobile device capabilities.

Wireless communication networks and wireless communication services are becoming increasingly dynamic, complex, and ubiquitous. For example, some wireless communication networks can be developed to implement fourth generation (4G), fifth generation (5G) or new radio (NR) technology. Such technology can include solutions for enabling user equipment (UE) and network devices, such as base stations, to communicate with one another. Some scenarios can involve indicating messages to a UE.

The following detailed description refers to the accompanying drawings. Like reference numbers in different drawings can identify the same or similar features, elements, operations, etc. Additionally, the present disclosure is not limited to the following description as other implementations can be utilized, and structural or logical changes made, without departing from the scope of the present disclosure.

Telecommunication networks can include user equipment (UEs) capable of communicating with base stations and/or other network access nodes. UEs and base stations can implement various techniques and communications standards for enabling UEs and base stations to discover one another, establish and maintain connectivity, and exchange information in an ongoing manner. Objectives of such techniques can include adapting paging early indications (PEI) according to power consumption.

A UE can operate in various energy states, such as an idle/inactive (collectively referred to herein as idle state) state or an active state. While in the idle state, the UE conserves power, and while in the active state, the UE receives communications from the base station. The UE may transition from an idle state to an active state to receive communications. For example, the UE can enter an active state to receive synchronization signal blocks (SSBs) that indicate to the UE information about communicating with the base station. Paging messages can be sent during paging occasions by the base station when the UE is in the idle state to notify the UE of upcoming messages that require the UE to be in an active state.

In some examples, the base station can transmit a paging early indication (PEI) to notify the UE in advance of paging occasions. In order to receive the PEI, the UE can pre-sync by monitoring for and decoding an SSB. The UE, while in an idle state, can monitor for the PEI. If the UE detects and decodes the PEI, the UE monitors for and decodes the next paging occasion. If the UE does not detect or decode the PEI, the UE can remain in an idle state and skip detecting and decoding the next paging occasion, resulting in power savings. The PEI can be signaled via downlink (DL) control information (DCI) via the physical DL control channel (PDCCH), or via a reference signal (RS).

However, various factors can affect the amount of power saved, such as the interval between the PEI and SSB, and the interval between the PEI and paging occasion (PO). For example, if the PEI and SSB are farther apart, the UE enters and exits sleep states inefficiently in order to decode the signals. The interval between the PEI and the PO can affect power savings and cost similarly. Another factor can be the paging rate (e.g., how often the UE receives PEIs). That is, it may be inefficient for the UE to monitor for and decode PEIs if there is a higher paging rate. Thus, in some scenarios, implementing PEIs may not result in power savings or an advantage for the UE.

One or more of the techniques described herein address the foregoing deficiencies by providing solutions for adaptive PEI that can involve adjusting PEI monitoring and skipping pre-syncing. For example, the UE can disable or enable PEI monitoring according to network configuration factors, such as a power value, SSB reselection, and paging rate. The UE can calculate a power value by comparing the interval between the SSB and PEI, and the interval between the SSB and PO. In some examples, the UE can reselect an SSB and can calculate a power value based on the reselected SSB. Based on the power value, the UE can determine whether to enable or disable PEI monitoring. In some examples, the UE can calculate a paging rate threshold, and enable or disable PEI monitoring based on the paging rate in relation to the paging rate threshold. In some examples, the UE can refrain from pre-syncing prior to receiving PEI messages. For example, the UE can skip pre-syncing before PEI decoding when there is a PEI decoding failure. Adjusting PEI monitoring and skipping pre-syncing can result in power savings for the UE.

1 FIG. 100 110 120 130 is a diagram of an example of an overviewadaptive PEI according to one or more implementations described herein. As shown, a UE can receive communications from a base station. UE can monitor for and decode the communications from the base station. For example, UE can monitor for and decode SSB, monitor PEI occasionand decode the PEI, and monitor paging occasionand decode the paging message.

110 1 120 140 2 110 1 110 2 140 1 140 1 110 2 110 3 120 110 1 130 110 2 110 1 SSB-and PEI occasioncan be separated by time gap-. SSB-and SSB-can be separated by time gap-, which is the same as the time gap-between SSB-and-. The UE can pre-sync prior to PEI occasionby decoding SSB-and can pre-sync prior to paging occasionby decoding SSB-. Pre-synching can synchronize timing and frequency in order to provide better conditions for protentional paging decoding, such as for physical DL shared channel (PDSCH) paging decoding. For an SSB-based pre-sync, the UE can wake up to decode SSB-, resulting in power consumption.

140 110 1 120 110 1 120 140 2 110 1 120 140 4 140 2 110 2 130 110 2 130 140 3 140 5 110 2 130 A time gapbetween SSB-and PEI occasionscan vary, which can affect UE power use and efficiency. For example, with reference to Example A, SSB-and PEI occasioncan be separated by time gap-. With reference to Example B, SSB-and PEI occasioncan be separated by time gap-, which can be larger than time gap-. Similarly, a time gap between SSB-and paging occasionscan vary, affecting UE power use and efficiency. For example, with reference to Example A, SSB-and paging occasioncan be separated by time gap-, which can be larger than time gap-between SSB-and paging occasionof Example B.

110 1 120 110 2 130 110 1 140 4 140 4 140 2 120 170 140 4 110 1 170 140 5 110 2 130 Example B describes a long interval between SSB-and PEI occasion, and a short interval between SSB-and paging occasion. In such an example, a PEI frame offset parameter can be set to a smaller value (e.g., pei-FrameOffset-r17=1) than a paging frame offset parameter (e.g., nAndPaingFramOffset->oneT=2). The differences in intervals can result in the PEI decoding consuming more power than direct paging decoding. In such scenarios, PEI decoding can include the pre-sync decoding of SSB-, resulting in higher power overhead due to the larger time gap-. For example, the UE can remain in an active state for the duration of time gap-, which is a longer duration than time gap-of Example A, resulting in greater power consumption. If the PEI occasionwere removed, or disabled, as shown by disabled PEI occasion, the UE may not remain in an active state for time gap-. Thus, in Example B, it can be advantageous not to monitor for and decode SSB-. Disabled PEI occasioncan also be advantageous due to the shorter duration of time gap-, which enables the UE to enter an active state to monitor for and receive SSB-and paging occasionand quickly return to an idle state.

120 120 140 1 140 2 140 3 140 4 140 5 120 Table 1 describes Examples A and B with and without PEI occasions. Table 1 describes an example paging rate of 18.35%. Table 1 describes the effect of enabling/disabling PEI occasionmonitoring and decoding for various discontinuous reception (DRX) cycles. Time gap-can be 20 milliseconds (ms), time gap-can be 2 ms, time gap-can be 10 ms, time gap-can be 5 ms, and time gap-can be 2 ms. For Example B, monitoring PEI occasionresults increased power consumption and reduced power savings.

TABLE 1 Example A Example B DRX Power Power Saving Power Power Saving PEI 640 1.563 1.3438 Disabled 1280 1.9481 0.939 2560 0.7241 0.6695 5120 0.6074 0.5802 PEI 640 1.4661 6.2% 1.5202 −13.13% Enabled 1280 1.0002 4.57% 1.0192 −8.54 2560 0.7001 3.31% 0.7096 5.99% 5120 0.5954 1.98% 0.6002 −3.54%

120 130 120 150 130 160 110 110 1 120 1 150 130 1 160 In some examples, PEI occasionsand paging occasioncan have multiple occasions with a search space. For example, PEI occasioncan include multiple occasions within PEI search space. Paging occasioncan include multiple occasions within paging occasion search space. SSBcan indicate which portion of the search space to monitoring for the occasion. For example, SSB-can indicate to search a first PEI occasion-of PEI search space, which corresponds to paging occasion-of the paging occasion search space.

140 110 1 120 110 2 130 110 110 110 120 3 130 3 110 When there is SSB re-selection, there can be a change to time gaps, or intervals between SSB-and PEI occasionand the interval between SSB-and paging occasion. In such examples, reselected SSBcan indicate to search different portions of the search spaces than a previously selected SSB. Switching from the first SSB to the second SSB can result in a change of the intervals due to the difference in time between the different portions of the search space, which can result in power inefficiencies. For example, the reselected SSBcan indicate to search PEI occasion-and paging occasion-, which are farther away from their respective SSBs.

120 1 130 1 120 3 130 3 For example, Table 2 describes power saving with regard to monitoring either PEI occasion-and paging occasion-or PEI occasion-and paging occasion-. Monitoring the third occasions results in greater power savings for UE.

TABLE 2 Monitoring the First Monitoring the Third Occasions of the Occasion of the Search Spaces Search Spaces DRX Power Power Saving Power Power Saving PEI 640 1.3161 1.5364 Disabled 1280 0.9298 1.0294 2560 0.6649 0.7147 5120 0.5778 0.6027 PEI 640 1.3913 −5.71% 1.5185 1.17% Enabled 1280 0.9674 −4.04% 1.0172 1.19% 2560 0.6837 −2.83% 0.7086 0.85% 5120 0.5872 −1.63% 0.5997 0.50%

120 120 130 130 In some examples, the UE can monitor PEI occasionsaccording to a paging rate. For example, the UE can monitor every other paging occasion, resulting in a paging rate of 50%, or every fourth PEI occasion, resulting in a paging rate of 25%. A higher paging rate, or monitoring paging occasionwith higher frequency, can increase power use. Table 3 describes the effects of varying paging rates on power savings. Reducing the paging rate can result in power savings.

TABLE 3 Paging rate of 5% Paging rate of 18.35% Paging rate of 50%. Power Power Power DRX Power Saving Power Saving Power Saving PEI 640 1.563 1.563 1.563 Disabled 1280 1.0481 1.0481 1.0481 2560 0.7241 0.7241 0.7241 5120 0.6074 0.6074 0.6074 PEI 640 1.3771 11.89% 1.4661 6.2% 1.6771 −7.30% Enabled 1280 0.9557 8.82% 1.0002 4.57% 1.1056 −5.49% 2560 0.6778 6.39% 0.7001 3.31% 0.7528 −3.96% 5120 0.5843 3.8% 0.5954 1.98% 0.6218 −2.37%

120 120 120 170 Techniques described herein can be applied to increase power savings through adaptive PEI. For example, the UE can determine whether to enabling monitoring of PEI occasionor to disable monitoring of PEI occasions. The UE can use various power factors, such as paging rate, to adjust PEI occasionmonitoring. For example, for some configurations and high paging rate, there is a power cost to the UE (e.g., Table 3, paging rate of 50%). In such examples, it can be advantageous to skip PEI monitoring occasion, as shown by disabled PEI occasion. In some examples, the UE can determine whether to skip pre-syncing to reduce power consumption and increase power savings. Such techniques and many other features and aspects of the techniques described herein are presented below with reference to remaining Figures.

2 FIG. 200 200 210 210 2 210 210 220 230 240 250 is an example networkaccording to one or more implementations described herein. Example networkcan include UEs,-, etc. (referred to collectively as “UEs” and individually as “UE”), a radio access network (RAN), a core network (CN), application servers, and external networks.

200 200 The systems and devices of example networkcan operate in accordance with one or more communication standards, such as 2nd generation (2G), 3rd generation (3G), 4th generation (4G) (e.g., long-term evolution (LTE)), and/or 5th generation (5G) (e.g., new radio (NR)) communication standards of the 3rd generation partnership project (3GPP). Additionally, or alternatively, one or more of the systems and devices of example networkcan operate in accordance with other communication standards and protocols discussed herein, including future versions or generations of 3GPP standards (e.g., sixth generation (6G) standards, seventh generation (7G) standards, etc.), institute of electrical and electronics engineers (IEEE) standards (e.g., wireless metropolitan area network (WMAN), worldwide interoperability for microwave access (WiMAX), etc.), and more.

210 210 210 As shown, UEscan include smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more wireless communication networks). Additionally, or alternatively, UEscan include other types of mobile or non-mobile computing devices capable of wireless communications, such as personal data assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, etc. In some implementations, UEscan include internet of things (IoT) devices (or IoT UEs) that can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. Additionally, or alternatively, an IoT UE can utilize one or more types of technologies, such as machine-to-machine (M2M) communications or machine-type communications (MTC) (e.g., to exchanging data with an MTC server or other device via a public land mobile network (PLMN)), proximity-based service (ProSe) or device-to-device (D2D) communications, sensor networks, IoT networks, and more. Depending on the scenario, an M2M or MTC exchange of data can be a machine-initiated exchange, and an IoT network can include interconnecting IoT UEs (which can include uniquely identifiable embedded computing devices within an Internet infrastructure) with short-lived connections. In some scenarios, IoT UEs can execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

210 210 212 210 222 222 UEscan communicate and establish a connection with one or more other UEsvia one or more wireless channels, each of which can comprise a physical communications interface/layer. The connection can include an M2M connection, MTC connection, D2D connection, SL connection, etc. The connection can involve a PC5 interface. In some implementations, UEscan be configured to discover one another, negotiate wireless resources between one another, and establish connections between one another, without intervention or communications involving RAN nodeor another type of network node. In some implementations, discovery, authentication, resource negotiation, registration, etc., can involve communications with RAN nodeor another type of network node.

210 212 210 222 222 210 210 210 210 210 222 210 UEscan use one or more wireless channelsto communicate with one another. As described herein, UEcan communicate with RAN nodeto request SL resources. RAN nodecan respond to the request by providing UEwith a dynamic grant (DG) or configured grant (CG) regarding SL resources. A DG can involve a grant based on a grant request from UE. A CG can involve a resource grant without a grant request and can be based on a type of service being provided (e.g., services that have strict timing or latency requirements). UEcan perform a clear channel assessment (CCA) procedure based on the DG or CG, select SL resources based on the CCA procedure and the DG or CG; and communicate with another UEbased on the SL resources. The UEcan communicate with RAN nodeusing a licensed frequency band and communicate with the other UEusing an unlicensed frequency band.

210 220 214 1 214 2 222 1 222 2 230 210 210 UEscan communicate and establish a connection with (e.g., be communicatively coupled) with RAN, which can involve one or more wireless channels-and-, each of which can comprise a physical communications interface/layer. In some implementations, a UE can be configured with dual connectivity (DC) as a multi-radio access technology (multi-RAT) or multi-radio dual connectivity (MR-DC), where a multiple receive and transmit (Rx/Tx) capable UE can use resources provided by different RAN network nodes (e.g., RAN network nodes-and-) that can be connected via non-ideal backhaul (e.g., where one network node provides NR access and the other network node provides either E-UTRA for LTE or NR access for 5G). In such a scenario, one network node can operate as a master node (MN) and the other as the secondary node (SN). The MN and SN can be connected via a network interface, and at least the MN can be connected to the CN. Additionally, at least one of the MN or the SN can be operated with shared spectrum channel access, and functions specified for UEcan be used for an integrated access and backhaul mobile termination (IAB-MT). Similar for UE, the IAB-MT can access the network using either one network node or using two different nodes with enhanced dual connectivity (EN-DC) architectures, new radio dual connectivity (NR-DC) architectures, or the like. In some implementations, a base station (as described herein) can be an example of network RAN network nodes.

210 216 218 210 216 216 218 216 216 220 230 210 220 216 210 220 210 218 218 2 FIG. As shown, UEcan also, or alternatively, connect to access point (AP)via connection interface, which can include an air interface enabling UEto communicatively couple with AP. APcan comprise a wireless local area network (WLAN), WLAN node, WLAN termination point, etc. The connectioncan comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, and APcan comprise a wireless fidelity (Wi-Fi®) router or other AP. While not explicitly depicted in, APcan be connected to another network (e.g., the Internet) without connecting to RANor CN. In some scenarios, UE, RAN, and APcan be configured to utilize LTE-WLAN aggregation (LWA) techniques or LTE WLAN radio level integration with IPsec tunnel (LWIP) techniques. LWA can involve UEin RRC_CONNECTED being configured by RANto utilize radio resources of LTE and WLAN. LWIP can involve UEusing WLAN radio resources (e.g., connection interface) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., Internet Protocol (IP) packets) communicated via connection interface. IPsec tunneling can include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

220 222 1 222 2 222 222 214 1 214 2 210 220 222 222 222 222 222 RANcan include one or more RAN nodes-and-(referred to collectively as RAN nodes, and individually as RAN node) that enable channels-and-to be established between UEsand RAN. A RAN nodecan be a base station and may be referred to herein as base station. RAN nodescan include network access points configured to provide radio baseband functions for data and/or voice connectivity between users and the network based on one or more of the communication technologies described herein (e.g., 2G, 3G, 4G, 5G, WiFi®, etc.). As examples therefore, a RAN node can be an E-UTRAN Node B (e.g., an enhanced Node B, eNodeB, eNB, 4G base station, etc.), a next generation base station (e.g., a 5G base station, NR base station, next generation eNBs (gNB), etc.). RAN nodescan include a roadside unit (RSU), a transmission reception point (TRxP or TRP), and one or more other types of ground stations (e.g., terrestrial access points). In some scenarios, RAN nodecan be a dedicated physical device, such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or the like having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

222 222 222 222 222 Some or all of RAN nodes, or portions thereof, can be implemented as one or more software entities running on server computers as part of a virtual network, which can be referred to as a centralized RAN (CRAN) and/or a virtual baseband unit pool (vBBUP). In these implementations, the CRAN or vBBUP can implement a RAN function split, such as a packet data convergence protocol (PDCP) split wherein radio resource control (RRC) and PDCP layers can be operated by the CRAN/vBBUP and other Layer 2 (L2) protocol entities can be operated by individual RAN nodes; a media access control (MAC)/physical (PHY) layer split wherein RRC, PDCP, radio link control (RLC), and MAC layers can be operated by the CRAN/vBBUP and the PHY layer can be operated by individual RAN nodes; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer can be operated by the CRAN/vBBUP and lower portions of the PHY layer can be operated by individual RAN nodes. This virtualized framework can allow freed-up processor cores of RAN nodesto perform or execute other virtualized applications.

222 220 222 210 230 In some implementations, an individual RAN nodecan represent individual gNB-distributed units (DUs) connected to a gNB-control unit (CU) via individual F1 or other interfaces. In such implementations, the gNB-DUs can include one or more remote radio heads or radio frequency (RF) front end modules (RFEMs), and the gNB-CU can be operated by a server (not shown) located in RANor by a server pool (e.g., a group of servers configured to share resources) in a similar manner as the CRAN/vBBUP. Additionally, or alternatively, one or more of RAN nodescan be next generation eNBs (i.e., gNBs) that can provide evolved universal terrestrial radio access (E-UTRA) user plane and control plane protocol terminations toward UEs, and that can be connected to a 5G core network (5GC)via an NG interface.

222 210 222 220 210 222 Any of the RAN nodescan terminate an air interface protocol and can be the first point of contact for UEs. In some implementations, any of the RAN nodescan fulfill various logical functions for the RANincluding, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. UEscan be configured to communicate using orthogonal frequency-division multiplexing (OFDM) communication signals with each other or with any of the RAN nodesover a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a single carrier frequency-division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink (SL) communications), although the scope of such implementations may not be limited in this regard. The OFDM signals can comprise a plurality of orthogonal subcarriers.

222 210 In some implementations, a downlink resource grid can be used for downlink transmissions from any of the RAN nodesto UEs, and uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid (e.g., a resource grid or time-frequency resource grid) that represents the physical resource for downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block can comprise a collection of resource elements (REs); in the frequency domain, this can represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

222 210 Further, RAN nodescan be configured to wirelessly communicate with UEs, and/or one another, over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”), an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”), or combination thereof. A licensed spectrum can correspond to channels or frequency bands selected, reserved, regulated, etc., for certain types of wireless activity (e.g., wireless telecommunication network activity), whereas an unlicensed spectrum can correspond to one or more frequency bands that are not restricted for certain types of wireless activity. Whether a particular frequency band corresponds to a licensed medium or an unlicensed medium can depend on one or more factors, such as frequency allocations determined by a public-sector organization (e.g., a government agency, regulatory body, etc.) or frequency allocations determined by a private-sector organization involved in developing wireless communication standards and protocols, etc.

210 210 210 222 210 210 The PDSCH can carry user data and higher layer signaling to UEs. The physical downlink control channel (PDCCH) can carry information about the transport format and resource allocations related to the PDSCH channel, among other things. The PDCCH can also inform UEsabout the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information related to the uplink shared channel. Typically, downlink scheduling (e.g., assigning control and shared channel resource blocks to UEwithin a cell) can be performed at any of the RAN nodesbased on channel quality information fed back from any of UEs. The downlink resource assignment information can be sent on the PDCCH used for (e.g., assigned to) each of UEs.

210 210 One or more of the techniques, described herein, can enable UEto engage in adaptive PEI, including determining whether to disable or enable PEI monitoring, skip monitoring occasions, and determine whether to skip pre-syncing. For example, UEcan use various factors, such as intervals between occasions, power usage profiles, paging rate thresholds, SSB, paging, and PEI schedules or configurations, etc., to determine whether monitoring results in power savings. These and many other features and aspects of the techniques described herein are presented below with reference to remaining Figures.

222 223 223 223 222 230 222 230 224 226 228 The RAN nodescan be configured to communicate with one another via interface. In implementations where the system is an LTE system, interfacecan be an X2 interface. In NR systems, interfacecan be an Xn interface. The X2 interface can be defined between two or more RAN nodes(e.g., two or more eNBs/gNBs or a combination thereof) that connect to evolved packet core (EPC) or CN, or between two eNBs connecting to an EPC. The RAN nodescan be configured to communicate with the CNvia various interfaces, such as physical interfaces, including interface, interface, and interface.

210 210 In some implementations, the X2 interface can include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U can provide flow control mechanisms for user data packets transferred over the X2 interface and can be used to communicate information about the delivery of user data between eNBs or gNBs. For example, the X2-U can provide specific sequence number information for user data transferred from a master eNB (MeNB) to a secondary eNB (SeNB); information about successful in sequence delivery of PDCP packet data units (PDUs) to a UEfrom an SeNB for user data; information of PDCP PDUs that were not delivered to a UE; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C can provide intra-LTE access mobility functionality (e.g., including context transfers from source to target eNBs, user plane transport control, etc.), load management functionality, and inter-cell interference coordination functionality.

220 230 230 232 210 230 220 230 230 230 230 As shown, RANcan be connected (e.g., communicatively coupled) to CN. CNcan comprise a plurality of network elements, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs) who are connected to the CNvia the RAN. In some implementations, CNcan include an evolved packet core (EPC), a 5G CN, and/or one or more additional or alternative types of CNs. The components of the CNcan be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some implementations, network function virtualization (NFV) can be utilized to virtualize any or all the above-described network node roles or functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CNcan be referred to as a network slice, and a logical instantiation of a portion of the CNcan be referred to as a network sub-slice. Network Function Virtualization (NFV) architectures and infrastructures can be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

230 240 250 234 236 238 240 230 240 210 230 250 210 As shown, CN, application servers, and external networkscan be connected to one another via interfaces,, and, which can include IP network interfaces. Application serverscan include one or more server devices or network elements (e.g., virtual network functions (VNFs) offering applications that use IP bearer resources with CN(e.g., universal mobile telecommunications system packet services (UMTS PS) domain, LTE PS data services, etc.). Application serverscan also, or alternatively, be configured to support one or more communication services (e.g., voice over IP (VOIP) sessions, push-to-talk (PTT) sessions, group communication sessions, social networking services, etc.) for UEsvia the CN. Similarly, external networkscan include one or more of a variety of networks, including the Internet, thereby providing the mobile communication network and UEsof the network access to a variety of additional services, information, interconnectivity, and other network features.

3 FIG. 2 FIG. 3 FIG. 3 FIG. 300 300 210 300 300 300 300 is a diagram of an example of processfor adaptive PEI according to one or more implementations described herein. Processcan be implemented by UE. In some implementations, some or all of processcan be performed by one or more other systems or devices, including one or more of the devices of. Additionally, processcan include one or more fewer, additional, differently ordered and/or arranged operations than those shown in. In some implementations, some or all of the operations of processcan be performed independently, successively, simultaneously, etc., of one or more of the other operations of process. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in.

300 210 300 310 210 222 222 222 210 310 As shown, processcan include enabling or disabling PEI monitoring. PEI monitoring, as referred to herein, can include receiving and decoding PEI occasions, such as to determine whether PEI occasions include a PEI. In some examples, UEcan disable PEI monitoring when the network configuration is improper. Processcan include receiving or reselecting an SSB (block). For example, UEcan receive system information block 1 (SIB1) from base station. Alternatively, UE can reselect an SSB from base station. Reselecting a SSB can include selecting one of multiple SSBs transmitted by base station. In some examples, UEcan receive an SSB with different signal timing than a previously received SSB (block).

300 315 210 210 210 Processcan also include calculating an SSB-PEI interval and SSB-PO interval (at). For example, UEcan calculate or otherwise determine a power value according to a power model and a current configuration or schedule of SSBs, PEIs, and POs. A power model can include power use related to various states that correspond to signaling at UE. To calculate the power value, UEcan calculate or determine the interval, or time, between the SSB and PEI occasion (SSB-PEI interval) and the interval, or time, between the SSB and the paging occasion (SSB-PO interval).

300 320 210 320 300 330 210 Processcan include evaluating the SSB-PEI interval relative to the SSB-PO interval (block). For example, UEcan determine whether the SSB-PEI interval is greater than the SSB-PO interval. When the SSB-PEI interval is greater than the SSB-PO interval (block—YES), processcan include disabling PEI monitoring (block). For example, UEcan disable PEI monitoring in response to determining that monitoring PEI involves too much power relative to monitoring for PO instead.

300 325 210 210 300 210 310 210 When the SSB-PEI interval is less than the SSB-PO interval, processcan include disabling PEI monitoring (block). For example, UEcan enable PEI monitoring in response to determining that the power involved in monitoring PEI is warranted. A larger SSB-PEI interval can indicate that the power value does not result in power savings for UE, and enabling PEI would result in power loss. A larger SSB-PO interval can indicate that the power value results in power savings if PEI monitoring is enabled. While not shown, processcan include UEreselecting the SSB (block). Reselection can result in changes to the SSB-PEI interval, the SSB-PO interval, or both, which can affect the power value and power savings. Thus, UEcan determine whether to enable PEI or disable PEI after reselecting the SSB.

4 FIG. 2 FIG. 4 FIG. 4 FIG. 400 400 210 400 400 400 400 is a diagram of an example of processfor adaptive PEI according to one or more implementations described herein. Processcan be implemented by UE. In some implementations, some or all of processcan be performed by one or more other systems or devices, including one or more of the devices of. Additionally, processcan include one or more fewer, additional, differently ordered and/or arranged operations than those shown in. In some implementations, some or all of the operations of processcan be performed independently, successively, simultaneously, etc., of one or more of the other operations of process. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in.

210 210 210 210 210 210 As described below, UEcan determine whether to enable or disable PEI monitoring based on paging rate factors, such as a paging rate threshold, total paging decoding number, and paging decoding rate. The paging rate threshold (T) can indicate a paging decoding rate at which UEcould save power by enabling PEI. The paging rate threshold can be determined according to a power model, paging configuration, and PEI configuration. A power model can include power use related to various states of UEthat correspond to signaling. For example, UEcan have a higher power use when decoding SSBs in an active state, and a lower power use when in an idle state between paging occasions and SSBs. Paging configuration and PEI configuration can include the timing or schedule of paging occasions, SSBs, and PEI occasions. In some examples, UEcan calculate the paging rate threshold prior to, during, or after the paging cycle. In some examples, UEcan identify or detect a paging configuration change and calculate a paging rate threshold based on a change in a paging configuration. A paging configuration can include time between paging occasions (e.g., a paging cycle).

400 210 410 400 210 415 415 400 210 420 425 415 400 210 420 425 Processcan include UEparticipating in a paging cycle (at). The paging cycle can be the distance between each paging occasion and can include SSBs and PEI occasions. Processcan include UEdetermining whether it is beneficial or necessary to decode a paging occasion (at). In response to determining to decode the paging occasions (at—YES) processcan include UEcalculating a total paging decoding number (at) and calculate the paging decoding rate (at). In response to determining to not to decode the paging occasion (at—NO) processcan include UErefraining from calculating the total paging decoding number (at) and calculating the paging decoding rate (at).

400 210 420 210 3 210 210 3 4 210 425 210 210 Processcan include UEcan calculate the total paging decoding number according to the time window (at). The time window can include multiple paging cycles or multiple paging occasions. The total paging decoding number can be the number of paging occasions UEdecodes within the time window (or length of time). For example, there may be 4 scheduled paging occasions, but the network only indicatespaging signals to UE, so UEonly receives and decodesof thescheduled paging occasions. UEcan calculate the paging decoding rate by dividing the total decoded paging by the length of the paging cycle (at). The paging decoding rate can indicate how often UEdecodes paging occasions. For example, if the total paging decoding number is 3, and the length of the paging cycle is 40 ms, UEcan divide 3 by 40 ms to determine the paging decoding rate.

400 210 430 400 210 435 210 435 400 210 410 400 210 440 210 400 210 410 Processcan include UEcomparing the paging decoding rate to the paging rate threshold (at). When the paging decoding rate is not greater than the paging rate threshold, processcan include UEenabling PEI monitoring (at). When the paging decoding rate is less than the paging rate threshold, enabling PEI monitoring can result in power savings for UE. After enabling PEI monitoring (at) processcan include UEexecuting subsequent paging cycles according to the enabled PEI monitoring setting (at). When the paging decoding rate is greater than the paging rate threshold, processcan include UEdisabling PEI monitoring (at). When the paging decoding rate is greater than the paging rate threshold, PEI monitoring can result in power loss at UE. After disabling PEI monitoring, processcan include UEengaging with subsequent paging cycles according to the disabled PEI monitoring setting (at).

5 FIG. 500 500 210 510 1 550 510 540 545 210 210 510 1 550 210 510 3 530 570 560 is a diagram of an examplefor adaptive PEI according to one or more implementations described herein. Exampledepicts PEI-based adaptive pre-sync reduction. For example, UEcan skip or refrain from decoding SSB-, as shown by skipped pre-sync, which can result in UE power savings. SSBscan be separated by an interval, or time gap. UE power profiledescribes power consumption of UEwhen UEskips SSB-, shown by skipped pre-sync. In some examples, UEcan skip or refrain from decoding SSB-, such as when paging is not available at paging occasion(at) which can result further UE power savings. Reduction of UE power use is shown by UE power profile when paging is not available.

510 1 550 520 520 210 530 210 510 3 530 Reducing pre-syncing can be applicable to physical downlink control channel (PDCCH) PEI decoding, which can be more robust to frequency and timing errors than PDSCH paging and may not require pre-syncing for every paging occasion. Thus, skipping or refraining from decoding SSB-, resulting in skipped pre-sync, may not result in reduced UE performance for decoding the PEI occasion. When PEI occasionindicates to UEto monitor for paging occasion, UEcan execute pre-sync by decoding SSB-prior to receiving paging occasion.

210 550 210 510 3 530 530 210 510 3 530 570 In some examples, such as when UEskips pre-sync, UEcan execute pre-sync SSB-before paging occasionwhen there is a PEI decoding failure or a PEI decoding pass that indicates a paging reception. A PEI decoding failure can happen when energy of the DCI is lower than a threshold. In examples, such as when there is not paging available at paging occasion, UEcan skip decoding SSB-and paging occasion(at).

6 FIG. 600 600 510 210 620 510 510 520 520 530 530 210 620 630 is a diagram of an examplefor adaptive PEI according to one or more implementations described herein. Exampledescribes PEI-based adaptive pre-sync reduction based on a pre-sync trigger. When executing a pre-sync, or decoding of SSB, UEcan start or restart a pre-sync timer. Decoding SSBcan include monitoring for and decoding SSB, decoding PEI occasioncan include monitoring for PEI occasionand decoding the associated received signal and message, and decoding paging occasioncan include monitoring for paging occasionand decoding the associated received signal and message. In some examples, such as the case of a low paging rate, pre-syncing occasionally can be necessary for UEaccuracy. The length of the pre-sync paging occasion timerand pre-sync PEI timercan be larger for PDCCH decoding.

210 520 1 620 1 210 510 1 530 1 210 620 1 520 1 620 1 210 520 210 510 2 520 510 3 530 As described with reference to Example A, UEcan decode PEI occasion-and start pre-sync timer-. UEcan then decode SSB-and paging occasion-. In some examples, UEcan start pre-sync timer-prior to decoding PEI occasion-. While the pre-sync timer-is active, and has not expired, UEcan skip pre-syncing prior to the PEI occasions. For example, UEcan skip (e.g., refrain from decoding) SSB-prior to PEI occasionand skip SSB-prior to paging occasion.

210 610 510 520 620 210 520 210 510 2 520 2 210 520 2 210 510 3 520 3 210 520 3 As shown in Example A, UEcan, for each paging cycleand after skipping the pre-sync SSBprior to PEI occasion, determine whether there has been a PEI decoding fail, or if there has been a PEI decode pass and paging is available. When neither of these conditions are met, and the pre-sync timerhas not expired, UEskips pre-syncing, or decoding the SSB, prior to PEI occasion. For example, UEcan skip pre-sync SSB-, and attempt to decode PEI occasion-. UEcan determine that PEI decoding of PEI occasion-did not fail, the PEI decoding passed, but there is not paging available. UEcan skip SSB-and attempt to decode the subsequent PEI occasion-. UEcan determine that PEI decoding of PEI occasion-did not fail, the PEI decoding passed, but there is not paging available.

210 210 510 530 510 530 210 510 620 530 210 620 510 210 510 4 520 4 210 530 2 210 510 5 530 2 210 520 4 620 2 210 530 2 In some examples, when UEdetermines there was PEI decoding fail or PEI decoding passed and there is paging available, UEdetermines if there is SSBprior to paging occasion. When there is an SSBprior to paging occasion, UEcan decode SSBand restart pre-sync timer, and decoding paging occasion. In some examples, UEcan restart pre-sync timeprior to SSB. As show in Example A, UEcan skip SSB-, and attempt to decode PEI occasion-. UEcan determine that either PEI decoding failed or PEI decoding passed and paging is available at paging occasion-. UEcan determine that SSB-exists prior to paging occasion-. UEcan perform a pre-sync by decoding PEI occasion-and restart pre-sync timer-. UEcan decode paging occasion-.

620 210 520 510 520 620 3 210 530 610 210 530 510 210 620 520 6 210 520 510 6 520 7 210 510 7 530 3 210 530 3 In some examples, pre-sync timecan be expired. In such examples, UEcan perform a pre-sync prior to PEI occasionby decoding the SSBthat occurs prior to the PEI occasionand starting (e.g., restarting) pre-sync timer-. In some examples, UEcan decode paging occasionwithin the same paging cycleas the pre-sync. In some examples, UEcan skip pre-syncing prior to paging occasion, or skip decoding SSB. As shown with reference to Example B, UEcan determine the pre-sync timeris expired, such as at PEI occasion-. UEcan, at the next paging cycle, perform pre-syncing prior to the PEI occasionby decoding SSB-that occurs prior to PEI occasion-. In some examples, UEcan skip decoding SSB-, or refrain from pre-syncing prior to paging occasion-. UEcan decode paging occasion-.

210 620 3 510 6 210 620 3 520 7 210 620 3 520 8 520 9 210 520 10 520 10 530 4 510 8 530 4 210 510 8 620 4 530 4 In some examples, UEcan start pre-sync timer-after decoding SSB-. In some examples, UE-can start pre-sync timer-after PEI occasion-. In example B, similarly to Example A, UEcan, during the duration of pre-sync timer-, skip pre-syncing prior to PEI occasions-and PEI occasion-. UEcan, based on PEI decoding fail of PEI occasion-or PEI decoding pass of PEI occasion-when paging is available at paging occasion-, determine that SSB-exists, or occurs, prior to paging occasion-. UEcan decode SSB-, or perform a pre-sync, restart pre-sync timer-, and decode paging occasion-.

7 FIG. 2 FIG. 7 FIG. 7 FIG. 7 FIG. 6 FIG. 700 700 210 700 700 700 700 is a diagram of an example processfor adaptive PEI according to one or more implementations described herein. Processcan be implemented by UE. In some implementations, some or all of processcan be performed by one or more other systems or devices, including one or more of the devices of. Additionally, processcan include one or more fewer, additional, differently ordered and/or arranged operations than those shown in. In some implementations, some or all of the operations of processcan be performed independently, successively, simultaneously, etc., of one or more of the other operations of process. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in.can be an example of PEI-based adaptive pre-sync reduction as described above with reference to.

700 210 710 210 715 700 210 715 715 700 210 720 745 210 720 210 745 210 Processcan include UEinitiating a pre-sync timer (at). For example, UEcan identify or detect when the pre-sync timer has expired (at). Processcan include UEdetermining whether the pre-sync timer has expired (at). When the pre-sync timer has expired (at—YES) processcan include UEperforming a pre-sync before a PEI (at) and in accordance with the PEI, decoding a subsequent paging message (at). For example, the pre-sync may include decoding an SSB that occurs prior to the next occurring PEI occasion. In some examples, UEcan restart the pre-sync timer before or after performing the pre-sync, before or after the PEI occasion, before or after decoding a PEI signal corresponding to the PEI occasion, or before or after decoding the paging message (at). In some examples, UEcan decode the PEI signal (e.g., message) of the PEI occasion after the SSB and prior to decoding the paging message (at). In some examples, UEcan refrain from, or skip, monitoring and decoding the pre-sync, or SSB, the occurs after the PEI occasions and prior to the paging occasion.

715 700 210 725 725 700 210 730 700 210 When the pre-sync timer has not expired (at—NO) processcan include UEskipping (e.g., refraining from) monitoring for, decoding, or both, the pre-syncing before the PEI occasion (at). Pre-syncing can include decoding an SSB that occurs prior to the PEI occasion (at). Processcan include UEdetermining whether there was a PEI decoding failure or whether there was a PEI decoding pass and a paging occasion is available (at). In some examples, processcan include UEdecoding the PEI signal (e.g., message) associated with the PEI paging occasion occurring after the pre-sync.

730 700 210 715 730 700 210 735 735 700 210 715 735 700 210 740 700 210 745 When there was not a decoding failure or decoding pass with an available paging occasion (at—NO), processcan include UEdetermining whether the pre-sync timer has expired (at). When there was a decoding failure or decoding pass with an available paging occasion (at—YES), processcan include UEdetermining whether an SSB exists prior to the paging occasion (at). When an SSB does not occur prior to the paging occasion (at—NO), pre-sync prior to the paging occasion can be possible and processcan include UEchecking whether the pre-sync timer has expired (at). When an SSB does exist prior to the paging occasion (block—YES), processcan include UEperforming the pre-sync (e.g., to decode a subsequent SSB that occurs after the PEI occasion and prior to the paging occasion) and reinitiating the pre-sync timer (at). Processcan include UEdecoding the paging message after performing the pre-sync and restarting the pre-sync timer (at).

Reducing pre-syncs can result in power savings, as shown in the following Table 4. Table 4 describes power saving based on various paging rates and whether PEI is enabled with or without pre-sync reduction.

TABLE 4 Power for PEI Power for PEI Enabled with Paging Enabled with Pre-Sync Power Rate Pre-Sync reduction Saving 640 1.5606 1.3052 16.37% 1280 1.0394 0.8965 13.75% 2569 0.7197 0.6482 9.93% 5120 0.6052 0.5695 5.90% 10240 0.548 0.5302 3.25%

8 FIG. 800 802 804 806 808 810 812 800 800 802 800 800 is a diagram of an example of components of a device according to one or more implementations described herein. In some implementations, the devicecan include application circuitry, baseband circuitry, RF circuitry, front-end module (FEM) circuitry, one or more antennas, and power management circuitry (PMC)coupled together at least as shown. The components of the illustrated devicecan be included in a UE or a RAN node. In some implementations, the devicecan include fewer elements (e.g., a RAN node may not utilize application circuitry, and instead include a processor/controller to process IP data received from a CN or an Evolved Packet Core (EPC)). In some implementations, the devicecan include additional elements such as, for example, memory/storage, display, camera, sensor (including one or more temperature sensors, such as a single temperature sensor, a plurality of temperature sensors at different locations in device, etc.), or input/output (I/O) interface. In other implementations, the components described below can be included in more than one device (e.g., said circuitries can be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

802 802 800 802 The application circuitrycan include one or more application processors. For example, the application circuitrycan include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) can include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors can be coupled with or can include memory/storage and can be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device. In some implementations, processors of application circuitrycan process IP data packets received from an EPC.

804 804 806 806 804 802 806 804 804 804 804 804 804 804 806 804 804 804 804 804 The baseband circuitrycan include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitrycan include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitryand to generate baseband signals for a transmit signal path of the RF circuitry. Baseband circuitrycan interface with the application circuitryfor generation and processing of the baseband signals and for controlling operations of the RF circuitry. For example, in some implementations, the baseband circuitrycan include a 3G baseband processorA, a 4G baseband processorB, a 5G baseband processorC, or other baseband processor(s)D for other existing generations, generations in development or to be developed in the future (e.g., 5G, 6G, etc.). The baseband circuitry(e.g., one or more of baseband processorsA-D) can handle various radio control functions that enable communication with one or more radio networks via the RF circuitry. In other implementations, some or all of the functionality of baseband processorsA-D can be included in modules stored in the memoryG and executed via a Central Processing Unit (CPU)E. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some implementations, modulation/demodulation circuitry of the baseband circuitrycan include Fast-Fourier Transform (FFT), precoding, or constellation mapping/de-mapping functionality. In some implementations, encoding/decoding circuitry of the baseband circuitrycan include convolution, tail-biting convolution, turbo, Viterbi, or Low-Density Parity Check (LDPC) encoder/decoder functionality. Implementations of modulation/demodulation and encoder/decoder functionality are not limited to these examples and can include other suitable functionality in other implementations.

804 210 210 210 210 210 210 210 In some implementations, memoryG can receive and/or store information and instructions for enabling UE, and/or one or more components thereof, to engage in adaptive PEI. For example, the information and instructions can cause and/or enable UEto determine whether the network configuration and power model for communications is power efficient. If UEdetermines the network configuration is power efficient, UEcan enable PEI monitoring. Otherwise, UEcan disable PEI monitoring. In some examples, UEcan determine whether to enable or disable PEI monitoring based on the selected SSB or paging rate. In some examples, the information and instructions can cause and/or enable UEto perform PEI-based adaptive pre-sync reduction by skipping pre-syncs.

804 804 804 804 802 In some implementations, the baseband circuitrycan include one or more audio digital signal processor(s) (DSP)F. The audio DSPsF can include elements for compression/decompression and echo cancellation and can include other suitable processing elements in other implementations. Components of the baseband circuitry can be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some implementations. In some implementations, some or all of the constituent components of the baseband circuitryand the application circuitrycan be implemented together such as, for example, on a system on a chip (SOC).

804 804 804 In some implementations, the baseband circuitrycan provide for communication compatible with one or more radio technologies. For example, in some implementations, the baseband circuitrycan support communication with a NG-RAN, an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN), etc. Implementations in which the baseband circuitryis configured to support radio communications of more than one wireless protocol can be referred to as multi-mode baseband circuitry.

806 806 806 808 804 806 804 808 RF circuitrycan enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various implementations, the RF circuitrycan include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitrycan include a receive signal path which can include circuitry to down-convert RF signals received from the FEM circuitryand provide baseband signals to the baseband circuitry. RF circuitrycan also include a transmit signal path which can include circuitry to up-convert baseband signals provided by the baseband circuitryand provide RF output signals to the FEM circuitryfor transmission.

806 806 806 806 806 806 806 806 806 806 806 808 806 806 806 804 806 In some implementations, the receive signal path of the RF circuitrycan include mixer circuitryA, amplifier circuitryB and filter circuitryC. In some implementations, the transmit signal path of the RF circuitrycan include filter circuitryC and mixer circuitryA. RF circuitrycan also include synthesizer circuitryD for synthesizing a frequency for use by the mixer circuitryA of the receive signal path and the transmit signal path. In some implementations, the mixer circuitryA of the receive signal path can be configured to down-convert RF signals received from the FEM circuitrybased on the synthesized frequency provided by synthesizer circuitryD. The amplifier circuitryB can be configured to amplify the down-converted signals and the filter circuitryC can be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals can be provided to the baseband circuitryfor further processing. In some implementations, the output baseband signals can be zero-frequency baseband signals, although this is not a requirement. In some implementations, mixer circuitryA of the receive signal path can comprise passive mixers, although the scope of the implementations is not limited in this respect.

806 806 808 804 806 In some implementations, the mixer circuitryA of the transmit signal path can be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitryD to generate RF output signals for the FEM circuitry. The baseband signals can be provided by the baseband circuitryand can be filtered by filter circuitryC.

806 806 806 806 806 806 806 806 In some implementations, the mixer circuitryA of the receive signal path and the mixer circuitryA of the transmit signal path can include two or more mixers and can be arranged for quadrature down conversion and up conversion, respectively. In some implementations, the mixer circuitryA of the receive signal path and the mixer circuitryA of the transmit signal path can include two or more mixers and can be arranged for image rejection (e.g., Hartley image rejection). In some implementations, the mixer circuitryA of the receive signal path and the mixer circuitryA can be arranged for direct down conversion and direct up conversion, respectively. In some implementations, the mixer circuitryA of the receive signal path and the mixer circuitryA of the transmit signal path can be configured for super-heterodyne operation.

806 804 806 In some implementations, the output baseband signals, and the input baseband signals can be analog baseband signals, although the scope of the implementations is not limited in this respect. In some alternate implementations, the output baseband signals, and the input baseband signals can be digital baseband signals. In these alternate implementations, the RF circuitrycan include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitrycan include a digital baseband interface to communicate with the RF circuitry.

In some dual-mode implementations, a separate radio IC circuitry can be provided for processing signals for each spectrum, although the scope of the implementations is not limited in this respect.

806 806 In some implementations, the synthesizer circuitryD can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the implementations is not limited in this respect as other types of frequency synthesizers can be suitable. For example, synthesizer circuitryD can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

806 806 806 806 The synthesizer circuitryD can be configured to synthesize an output frequency for use by the mixer circuitryA of the RF circuitrybased on a frequency input and a divider control input. In some implementations, the synthesizer circuitryD can be a fractional N/N+1 synthesizer.

804 802 802 In some implementations, frequency input can be provided by a voltage-controlled oscillator (VCO), although that is not a requirement. Divider control input can be provided by either the baseband circuitryor the applications circuitrydepending on the desired output frequency. In some implementations, a divider control input (e.g., N) can be determined from a look-up table based on a channel indicated by the applications circuitry.

806 806 Synthesizer circuitryD of the RF circuitrycan include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some implementations, the divider can be a dual modulus divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some implementations, the DMD can be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example implementations, the DLL can include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these implementations, the delay elements can be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

806 806 In some implementations, synthesizer circuitryD can be configured to generate a carrier frequency as the output frequency, while in other implementations, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some implementations, the output frequency can be a LO frequency (fLO). In some implementations, the RF circuitrycan include an IQ/polar converter.

808 810 806 808 806 810 806 808 806 808 FEM circuitrycan include a receive signal path which can include circuitry configured to operate on RF signals received from one or more antennas, amplify the received signals and provide the amplified versions of the received signals to the RF circuitryfor further processing. FEM circuitrycan also include a transmit signal path which can include circuitry configured to amplify signals for transmission provided by the RF circuitryfor transmission by one or more of the one or more antennas. In various implementations, the amplification through the transmit or receive signal paths can be done solely in the RF circuitry, solely in the FEM circuitry, or in both the RF circuitryand the FEM circuitry.

808 806 808 806 810 In some implementations, the FEM circuitrycan include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry can include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry). The transmit signal path of the FEM circuitrycan include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas).

812 804 812 812 800 812 In some implementations, the PMCcan manage power provided to the baseband circuitry. In particular, the PMCcan control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMCcan often be included when the deviceis capable of being powered by a battery, for example, when the device is included in a UE. The PMCcan increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

8 FIG. 812 804 812 802 806 808 Whileshows the PMCcoupled only with the baseband circuitry. However, in other implementations, the PMCcan be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry, RF circuitry, or FEM circuitry.

812 800 800 800 In some implementations, the PMCcan control, or otherwise be part of, various power saving mechanisms of the device. For example, if the deviceis in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it can enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the devicecan power down for brief intervals of time and thus save power.

800 800 800 If there is no data traffic activity for an extended period of time, then the devicecan transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The devicegoes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The devicemay not receive data in this state; in order to receive data, it can transition back to RRC_Connected state.

An additional power saving mode can allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is unreachable to the network and can power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

802 804 804 804 Processors of the application circuitryand processors of the baseband circuitrycan be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry, alone or in combination, can be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the baseband circuitrycan utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 can comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 can comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 can comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

9 FIG. 8 FIG. 900 804 804 804 804 804 804 940 940 804 is a diagram of example interfacesof baseband circuitry according to one or more implementations described herein. As discussed above, the baseband circuitryofcan comprise processorsA throughE and a memoryG utilized by said processors. Each of the processorsA throughE can include a memory interface,A throughE, respectively, to send/receive data to/from the memoryG.

804 222 210 210 260 210 260 222 222 260 222 260 222 210 210 222 260 In some implementations, memoryG can receive, store, and/or provide information and instructions for RIS selection. For example, base stationcan communicate RIS selection information to UE, and UEcan select one or more RISsbased on the RIS selection information and/or additional criteria. UEcan indicate the selected RISsto base station, and base stationcan select one or more RISs. Base stationcan also, or alternatively, configure one or more RISsfor communications between base stationand UE. The information and instructions can also cause or enable UE, base station, and/or RISto perform one or more additional, alternative, or different operations described herein.

804 852 804 954 802 956 806 958 960 812 8 FIG. 8 FIG. The baseband circuitrycan further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface(e.g., an interface to send/receive data to/from memory external to the baseband circuitry), an application circuitry interface(e.g., an interface to send/receive data to/from the application circuitryof), an RF circuitry interface(e.g., an interface to send/receive data to/from RF circuitryof), a wireless hardware connectivity interface(e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface(e.g., an interface to send/receive power or control signals to/from the PMC).

10 FIG. 10 FIG. 1000 1010 1010 1030 1040 1000 is a block diagram illustrating components, according to some example implementations, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically,shows a diagrammatic representation of hardware resourcesincluding one or more processors (or processor cores), one or more memory/storage devices, and one or more communication resources, each of which can be communicatively coupled via a bus. For implementations where node virtualization (e.g., NFV) is utilized, a hypervisor can be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources.

1010 1012 1014 The processors(e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) can include, for example, a processorand a processor.

1010 1010 The memory/storage devicescan include main memory, disk storage, or any suitable combination thereof. The memory/storage devicescan include, but are not limited to any type of volatile or non-volatile memory such as dynamic random-access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

1010 1055 210 In some implementations, memory/storage devicesreceive and/or store information and instructionsfor adaptive PEI. For example, UEcan receive, such as from a base station, SSBs, PEI messages, and paging messages. These and many other features and examples are discussed herein.

1030 1004 1006 1008 1030 The communication resourcescan include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devicesor one or more databasesvia a network. For example, the communication resourcescan include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

1050 1010 1050 1010 1010 1050 1000 1004 1006 1010 1010 1004 1006 Instructionscan comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processorsto perform any one or more of the methodologies discussed herein. The instructionscan reside, completely or partially, within at least one of the processors(e.g., within the processor's cache memory), the memory/storage devices, or any suitable combination thereof. Furthermore, any portion of the instructionscan be transferred to the hardware resourcesfrom any combination of the peripheral devicesor the databases. Accordingly, the memory of processors, the memory/storage devices, the peripheral devices, and the databasesare examples of computer-readable and machine-readable media.

11 FIG. 2 FIG. 11 FIG. 11 FIG. 1100 210 1100 1100 1100 1100 is a diagram of an example process for adaptive PEI according to one or more implementations described herein. Processcan be implemented by UE, baseband circuitry, or both. In some implementations, some or all of processcan be performed by one or more other systems or devices, including one or more of the devices of. Additionally, processcan include one or more fewer, additional, differently ordered and/or arranged operations than those shown in. In some implementations, some or all of the operations of processcan be performed independently, successively, simultaneously, etc., of one or more of the other operations of process. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in.

1100 1110 1100 1120 1100 1130 1100 1140 1100 1150 Processcan include initiating a pre-sync timer comprising a duration of one or more paging cycles (block). Processcan include refraining decoding a first SSB relative to initiation of the pre-sync timer and prior to a first PEI occasion (block). Processcan include decoding a second SSB relative to the initiation of the pre-sync timer and the first SSB (block). Processcan include restarting the pre-sync timer in response to decoding the second SSB (block). Processcan include decoding a paging signal corresponding to a paging occasion indicated by the second SSB (block).

12 FIG. 2 FIG. 12 FIG. 12 FIG. 1200 210 1200 1200 1200 1200 is a diagram of an example process for adaptive PEI according to one or more implementations described herein. Processcan be implemented by UE. In some implementations, some or all of processcan be performed by one or more other systems or devices, including one or more of the devices of. Additionally, processcan include one or more fewer, additional, differently ordered and/or arranged operations than those shown in. In some implementations, some or all of the operations of processcan be performed independently, successively, simultaneously, etc., of one or more of the other operations of process. As such, the techniques described herein are not limited to a number, sequence, arrangement, timing, etc., of the operations or processes depicted in.

1200 1210 1200 1220 1200 1230 Processcan include determining a first interval between a first SSB and a PEI occasion (block). Processcan include determining a second interval between a second SSB and a paging occasion (block). Processcan include enabling PEI monitoring based on an evaluation of the first interval relative to the second interval (block).

Examples and/or implementations herein can include subject matter such as a method, means for performing acts or blocks of the method, at least one machine-readable medium including executable instructions that, when performed by a machine (e.g., a processor (e.g., processor, etc.) with memory, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like) cause the machine to perform acts of the method or of an apparatus or system for concurrent communication using multiple communication technologies according to implementations and examples described.

210 210 In example 1, which can also include one or more of the examples described herein, a UE (e.g., UE) can comprise: a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UEto: initiate a pre-sync timer comprising a duration of one or more paging cycles; refrain from decoding a first SSB relative to initiation of the pre-sync timer and prior to a first PEI occasion; decode a second SSB relative to the initiation of the pre-sync timer and the first SSB; restart the pre-sync timer in response to decoding the second SSB; and decode a paging signal corresponding to a paging occasion indicated by the second SSB, the paging occasion comprising a first paging occasion of a sequence of paging occasions indicated by the second SSB.

210 In example 2, which can also include one or more of the examples described herein, the one or more processors are further configured to cause UEto: decode a PEI signal corresponding to the first PEI occasion.

In example 3, which can also include one or more of the examples described herein, refraining from decoding the first SSB is further based on the pre-sync timer not being expired.

In example 4, which can also include one or more of the examples described herein, decoding the paging signal is based on failure to decode a PEI signal associated with the first PEI occasion.

In example 5, which can also include one or more of the examples described herein, decoding the paging signal is based on refraining from decoding a PEI signal corresponding to the first PEI occasion and availability of the paging occasion.

In example 6, which can also include one or more of the examples described herein, decoding the second SSB is based on the second SSB occurring prior to the paging occasion.

In example 7, which can also include one or more of the examples described herein, restarting the pre-sync timer is based on the second SSB occurring prior to the paging occasion.

In example 8, which can also include one or more of the examples described herein, wherein a paging cycle of the one or more paging cycles comprises a time from an end of the first SSB to an end of the second SSB.

210 In example 9, which can also include one or more of the examples described herein, one or more processors are further configured to cause UEto: detect expiration of the pre-sync timer; decode a third SSB based on expiration of the pre-sync timer and the third SSB occurring prior to the following PEI occasion; and decoding a second paging message.

210 210 In example 10, which can also include one or more of the examples described herein, UEcan comprise a memory; and one or more processors configured to, when executing instructions stored in the memory, cause UEto: determine a first interval between a first SSB and a PEI occasion; determine a second interval between a second SSB and a paging occasion; and enable PEI monitoring based on an evaluation of the first interval relative to the second interval.

In example 11, which can also include one or more of the examples described herein, the evaluation of the first interval and the second interval comprises determining that the second interval is larger than the first interval.

In example 12, which can also include one or more of the examples described herein, determining the first interval and the second interval is based on receiving a system information block.

In example 13, which can also include one or more of the examples described herein, determining the first interval and the second interval is based on reselection of the first SSB.

210 In example 14, which can also include one or more of the examples described herein, the one or more processors are further executable to cause UEto: determine a paging rate threshold based on a power model and PEI configuration; and determine a paging decoding rate based on a total paging decoding number and a time window, wherein enabling PEI monitoring is further based on an evaluation of the paging decode rate relative to the paging rate threshold.

In example 15, which can also include one or more of the examples described herein, the total paging decoding number comprises a number of decoded paging signals corresponding to respective paging occasions.

In example 16, which can also include one or more of the examples described herein, the time window comprises one of more paging cycles, a paging cycle of the one or more paging cycles comprising a time between paging occasions.

210 In example 17, which can also include one or more of the examples described herein, the one or more processors are further executable to cause UEto: detect a change to a paging configuration; and determine the paging rate threshold based on the change to the paging configuration.

210 In example 18, which can also include one or more of the examples described herein, the one or more processors are further executable to cause UEto: initiate a pre-sync timer comprising a duration of one or more paging cycles; and refrain from decoding the first SSB relative to initiation of the pre-sync timer and prior to the PEI occasion.

210 In example 19, which can also include one or more of the examples described herein, the one or more processors are further executable to cause UEto: decode the second SSB relative to the initiation of the pre-sync timer and the first SSB; restart the pre-sync timer in response to decoding the second SSB; and decode a paging signal corresponding to a paging occasion indicated by the second SSB, the paging occasion comprising a first paging occasion of a sequence of paging occasions indicated by the second SSB.

In example 20, which can also include one or more of the examples described herein, base baseband circuitry can comprise a memory; and one or more processors configured to, when executing instructions stored in the memory, cause the baseband circuitry to: initiate a pre-sync timer comprising a duration for one or more paging cycles; refrain from decoding a first SSB relative to initiation of the pre-sync timer and prior to a first PEI occasion; decode a second SSB relative to the initiation of the pre-sync timer and the first SSB; restart the pre-sync timer in response to decoding the second SSB; and decode a paging signal corresponding to a paging occasion indicated by the second SSB, the paging occasion comprising a first paging occasion of a sequence of paging occasions indicated by the second SSB.

The examples discussed above also extend to method, computer-readable medium, and means-plus-function claims and implementations, any of which can include one or more of the features or operations of any one or combination of the examples mentioned above.

The above description of illustrated examples, implementations, aspects, etc., of the subject disclosure, including what is described in the Abstract, is not intended to be exhaustive or to limit the disclosed aspects to the precise forms disclosed. While specific examples, implementations, aspects, etc., are described herein for illustrative purposes, various modifications are possible that are considered within the scope of such examples, implementations, aspects, etc., as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described in connection with various examples, implementations, aspects, etc., and corresponding Figures, where applicable, it is to be understood that other similar aspects can be used or modifications and additions can be made to the disclosed subject matter for performing the same, similar, alternative, or substitute function of the subject matter without deviating therefrom. Therefore, the disclosed subject matter should not be limited to any single example, implementation, or aspect described herein, but rather should be construed in breadth and scope in accordance with the appended claims below.

In particular regard to the various functions performed by the above described components or structures (assemblies, devices, circuits, systems, etc.), the terms (including a reference to a “means”) used to describe such components are intended to correspond, unless otherwise indicated, to any component or structure which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations. In addition, while a particular feature can have been disclosed with respect to only one of several implementations, such feature can be combined with one or more other features of the other implementations as can be desired and advantageous for any given application.

As used herein, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, to the extent that the terms “including”, “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Additionally, in situations wherein one or more numbered items are discussed (e.g., a “first X”, a “second X”, etc.), in general the one or more numbered items can be distinct, or they can be the same, although in some situations the context can indicate that they are distinct or that they are the same.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.