WO2022152850A1

WO2022152850A1 - Selective configuration and dynamic activation and deactivation of paging early indicator

Info

Publication number: WO2022152850A1
Application number: PCT/EP2022/050752
Authority: WO
Inventors: Andres Reial; Sina MALEKI; Ali Nader; Santhan THANGARASA; Ajit Nimbalker
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-01-15
Filing date: 2022-01-14
Publication date: 2022-07-21

Abstract

A method (1000) by a wireless device (110) includes determining (1002) a first set of Paging Occasions (POs) and receiving (1004), from a network node (160), a paging early indicator (PEI) configuration associated with a group of wireless devices and a second set of POs. The wireless device determines whether the wireless device belongs to the group of wireless devices associated with the PEI configuration. If so, the wireless device attempts to receive a PEI, and monitors at least one of the POs in the second set of POs if the PEI is received. If not, the wireless device monitors at least one of the POs in first set of POs. If a paging message is received in the first or second set of POs, the wireless device transmits, to a network node, a message comprising information related to a usage of the PEI.

Description

SELECTIVE CONFIGURATION AND DYNAMIC ACTIVATION AND DEACTIVATION OF PAGING EARLY INDICATOR

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for selective configuration and dynamic activation and deactivation of paging early indicator (PEI).

BACKGROUND

A 5^th Generation (5G)/New Radio (NR) user equipment (UE) in RRC IDLE and RRC INACTIVE states operates in a so-called discontinuous reception (DRX) mode enabling it to save power. During this mode, the UE occasionally wakes up according to a network (NW)- configured scheme and listens to a paging channel. In case the NW is interested in reaching the UE, the NW pages the UE at these configured occasions whereby the UE establishes a connection to the NW. The paging message from the NW can be either initiated by the Core NW (CN) or a base station such as, for example a gNodeB (gNB). More specifically, the CN-Initiated paging is used to reach the UEs in RRC IDLE state, whereas the gNB-Initiated paging, which may also be referred to as Radio Access Node (RAN) paging, is used to reach UEs in RRC INACTIVE state.

The paging message from the NW is carried out via a Physical Downlink Control Channel (PDCCH)/Physical Downlink Shared Channel (PDSCH) combination similar to other scheduled data in the downlink (DL). When the NW has DL data for a UE, the NW transmits on PDCCH, a Downlink Control Information (DCI) container with details about where and how the UE can find data in a PDSCH. Various formats of DCI exist in the 3GPP specifications; for the paging message a DCI format 1 0 is used for which the generated Cyclic Redundancy Check (CRC) bits of the DCI are scrambled with a specific value called Paging-Radio Network Temporary Identifier (P- RNTI) (OXFFFE).

The NW typically configures several paging occasions per DRX cycle. For example, the NW may configure 8 Paging Occasions (POs) within a DRX cycle of 1.28 seconds. The paging configuration, which specifies the amount of POs and positions in time, is broadcast over the air in system information (SI) as part of SIB1 contents, for example. When a UE registers in the NW, it gets assigned a UE identity called 5G-Shortened-Temporary Mobile Subscriber Identity (5G-S- TMSI). This identity is used by the UE and NW in a formula specified by 3^rd Generation Partnership Project (3GPP) to derive in which of the configured occasions the UE will listen for a potential paging message. It shall be noted that several UEs could be listening for a potential paging message at the very same occasion (i.e., in the same PO). In case the UEs detect a paging DCI (i.e. DCI 1 0 with P-RNTI-scrambled CRC), the UEs have to look in the payload of PDSCH to see whether their identity is present and, thus, if the paging message was intended for them.

The payload of the PDSCH might carry up to 32 identities. Thus, up to 32 UEs may be paged during the same occasion. Even though a UE’s 5G-S-TMSI ID is used in the formulas for deriving the occasion, the identity that the UE looks for inside the PDSCH may be of another type. For example, in case the UE is in RRC IDLE state it looks for its 5G-S-TMSI (i.e. CN-Initiated paging message). However, if the UE is in RRC INACTIVE state, the UE has to look for both for 5G-S-TMSI, and the RAN-assigned Inactive-Radio Network Temporary Identifier (I-RNTI) identity since a UE in RRC_INACTIVE state may be either paged by the CN or the RAN.

The contents of a 3 GPP Rel-16 DL paging-related DCI format 1-0 (CRC scrambled by P- RNTI) used for scheduling of paging-related PDSCH is discussed in 3GPP TS 38.212 and includes the following:

Short Messages Indicator (2 bits).

Short Messages (8 bits). If only the scheduling information for Paging is carried, this bit field is reserved. Bits 4-8 are reserved for future use

- Frequency domain resource assignment (variable bit length dependent on bandwidth (BW)). If only the short message is carried, this bit field is reserved.

Time domain resource assignment (4 bits). If only the short message is carried, this bit field is reserved.

- Virtual Resource Block (VRB)-to-Physical Resource Block (PRB) mapping (1 bit). If only the short message is carried, this bit field is reserved.

- Modulation and coding scheme (5 bits). If only the short message is carried, this bit field is reserved.

Transport Block (TB) scaling (2 bits). If only the short message is carried, this bit field is reserved.

- Reserved bits. 8 bits for operation in a cell with shared spectrum channel access; otherwise 6 bits.

Note that there exist several reserved bits for future usage. Channel Estimates for Paging Reception

In NR Release 15, multiple synchronization signals (i.e., synchronization signal blocks (SSBs)) may be configured per cell, spatially covering different regions. The SSBs are transmitted in an SSB burst fashion. A typical SSB burst periodicity is 20ms. For example, if only one SSB is transmitted in the cell (as discussed herein for simplicity’s sake), the same SSB is transmitted every 20ms in the cell. FIGURE 1 illustrates SSB transmissions for different Subcarrier Spacing (SCS).

Paging signaling (PDCCH and PDSCH) are specified to have a quasi -colocation relation with an SSB in a cell, meaning that a UE that receives a SSB with a certain receiver configuration can rely on that the same spatial RX configuration and Timing/Frequency (T/F) offsets will be valid for paging reception. For a UE in NR, in order to be able to receive the paging signaling properly, channel estimates are typically carried out on the SSB(s) prior to the PO occasion. The number of SSBs required for channel estimation prior to PO reception depends on UE perceived coverage level, whether the reception is for PDCCH only or both PDCCH/PDSCH, the hardware architecture (e.g. number of Rx chains) and alike.

Each PO monitoring operation is associated with significant processing at the UE. Specifically, the UE must wake ahead of the PO time to obtain T/F synchronization for the paging PDCCH reception, then collect the PDCCH samples and perform tentative decoding. Depending on the Signal-Interference-to-Noise Ratio (SINR), the UE may need to use more than one SSB for loop convergence in preparation for potential paging PDSCH reception, making the T/F sync overhead quite large compared to the PO monitoring (i.e. PO PDCCH reception) itself.

To potentially reduce that overhead, a PEI signal may be used to indicate to the UE whether paging signaling (PDCCH/PDSCH) is expected in an upcoming PO. If there is no paging signals to receive and, thus, the PEI does not indicate a need to monitor the PO, the UE may skip high- quality loop convergence efforts and instead go to deep sleep state (low power consuming state). If, on the other hand, the PEI indicates that a paging PDCCH/PDSCH is expected, the UE will prepare for possible PDSCH reception and monitor the PDCCH to find out whether it is being targeted.

In an exemplary implementation, the UE regularly decodes/searches for PEI at preconfigured occasions. In case there is imminent data to be scheduled for the UE by the NW, a PEI (which may also be referred to as Wake Up Signal (WUS)) is transmitted by the NW. Based on the PEI, the UE knows that it shall wake up, prepare itself for reception (perform channel estimate), and receive a potential message at specified occasion. FIGURE 2 illustrates PEI signals being transmitted by the NW in addition to existing paging-related transmission. Specifically, FIGURE 2 illustrates transmitting PEI at extra occasions prior to data scheduling.

Certain problems exist, however. For example, PEI transmission is a cost for the NW/gNB in idle mode, in terms of resources not available for data transmission, and due to the need to wake up from sleep states to perform additional transmissions. However, not all UEs in the NW need or are expected to utilize the transmitted PEI. Such UEs include, for example, UEs in good link conditions, UEs with advanced receivers/HW components, or UEs with certain use cases of traffic scenarios where Idle mode power consumption accounts for a small portion of total consumed power.

By default, PEI, if activated, is provided to all UEs in the NW or in a cell when they are paged. Currently, there are no mechanisms to limit the PEI-related overhead for the NW such as, for example, by avoiding PEI transmissions that are not required and/or utilized by UEs, although that may be desirable in some deployments or scenarios.

Accordingly, there is a need for methods for selective configuration of PEI transmissions that can reduce the PEI-related overhead for the NW.

Furthermore, PEI is useful in terms of power saving particularly for UEs of poor channel conditions such as, for example, UEs experiencing low SINRs, UEs with simple/less-capable hardware components, UEs with traffic models in which the UE spends considerable amount of time in Idle mode, etc. However, PEI may not be useful for UEs in other scenarios.

In addition, the network node may need momentarily to transmit a larger number of paging messages such as, for example, because of a higher paging rate. Thus to send an additional PEI for each paging message becomes a burden on the network. As such, it makes sense for the network node to sometimes deactivate PEI, nevertheless, it is only possible to turn off PEI transmissions by mechanisms such as Radio Resource Control (RRC) reconfiguration or System Information (SI) update, which are slow and costly from system perspective, e.g. requiring all UEs (including UEs of earlier release that do not understand PEI) to re-acquire SI.

Accordingly, there is a need for methods for a mechanism that enables the network node to rapidly activate and deactivate PEI (e.g. to follow network dynamics and changes in UE population targeted for paging), and inform UEs suitably without going through expensive SI update-based mechanism.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, certain embodiments provide techniques, methods, and solutions in the network node for enabling PEI for a subset of UEs or POs. As another example, certain embodiments provide techniques, methods, and solutions to enable the network node to dynamically activate or deactivate PEI. In particular, certain embodiments provide Layer 1 -based solutions to enable the network node to dynamically activate or deactivate PEI.

According to certain embodiments, a method by a wireless device includes determining a first set of POs. The wireless device receives, from a network node, a PEI configuration, which is associated with a group of wireless devices and a second set of POs. The wireless device determines whether the wireless device belongs to the group of wireless devices associated with the PEI configuration. If the wireless device belongs to the group wireless devices associated with the PEI configuration, the wireless device attempts to receive a PEI. If the PEI is received, the wireless device monitors at least one of the POs in the second set of POs. Conversely, if the wireless device does not belong to the group of wireless devices associated with the PEI configuration, the wireless device monitors at least one of the POs in first set of POs. If a paging message for the wireless device is received in a PO in the first set of POs or the second set of POs, the wireless device transmits, to a network node, a message comprising information related to a usage of the PEI.

According to certain embodiments, a wireless device includes processing circuitry configured to determine a first set of POs. The processing circuitry is configured to receive, from a network node, a PEI configuration, which is associated with a group of wireless devices and a second set of POs. The processing circuitry is configured to determine whether the wireless device belongs to the group of wireless devices associated with the PEI configuration. If the wireless device belongs to the group wireless devices associated with the PEI configuration, the processing circuitry is configured to attempt to receive a PEI. If the PEI is received, the processing circuitry is configured to monitor at least one of the POs in the second set of POs. Conversely, if the wireless device does not belong to the group of wireless devices associated with the PEI configuration, the processing circuitry is configured to monitor at least one of the POs in first set of POs. If a paging message for the wireless device is received in a PO in the first set of POs or the second set of POs, the processing circuitry is configured to transmit, to a network node, a message comprising information related to a usage of the PEI.

According to certain embodiments, a method by a network node includes determining a group of wireless devices for receiving a PEI. The determining includes obtaining information indicating whether the group of wireless devices is using PEI. The network node signals a PEI configuration to the group of wireless devices. The network node determines at least one paging occasion for which to transmit the PEI and transmits the PEI to the group of wireless devices. According to certain embodiments, a network node includes processing circuitry configured to determine a group of wireless devices for receiving a PEI. The determining includes obtaining information indicating whether the group of wireless devices is using PEI. The processing circuitry is configured to signal a PEI configuration to the group of wireless devices. The processing circuitry is configured to determine at least one paging occasion for which to transmit the PEI and transmit the PEI to the group of wireless devices.

Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments limit PEI transmissions to certain UEs, UE groups, or POs which benefit from PEI such that overall PEI overhead is reduced. As another example, a technical advantage may be that certain embodiments improve capacity since resources otherwise used for PEI can be used for data transmission. As still another example, a technical advantage may be that certain embodiments improve network energy efficiency since the network nodes may omit some PEI transmissions and remain in sleep states instead.

As yet another example, one technical advantage may be that certain embodiments provide a network node with methods with which it can activate or deactivate PEI dynamically without triggering SI updates. Thus, certain embodiments may allow a faster update mechanism, saving both network and UE resources. Furthermore, as another example, a technical advantage may be that certain embodiments affect only the UEs that are interested in receiving information related to PEI rather the complete UE population.

Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates SSB transmissions for different Subcarrier Spacing (SCS);

FIGURE 2 illustrates PEI signals being transmitted by the NW in addition to existing paging-related transmission;

FIGURE 3 illustrates a high-level logical flow of a method by a network node, according to certain embodiments;

FIGURE 4 illustrates interaction of dynamic activation/deactivation using a paging and PEI DCI, according to certain embodiments; FIGURE 5 illustrates interaction of dynamic activation/deactivation using a paging and PEI DCI, according to certain embodiments;

FIGURE 6 illustrates an example wireless network, according to certain embodiments;

FIGURE 7 illustrates an example network node, according to certain embodiments;

FIGURE 8 illustrates an example wireless device, according to certain embodiments;

FIGURE 9 illustrate an example user equipment, according to certain embodiments;

FIGURE 10 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

FIGURE 11 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;

FIGURE 12 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;

FIGURE 13 illustrates a method implemented in a communication system, according to one embodiment;

FIGURE 14 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 15 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 16 illustrates another method implemented in a communication system, according to one embodiment;

FIGURE 17 illustrates an example method by a wireless device, according to certain embodiments;

FIGURE 18 illustrates an example method by a network node, according to certain embodiments;

FIGURE 19 illustrates another example method by a wireless device, according to certain embodiments;

FIGURE 20 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 21 illustrates another example method by a network node, according to certain embodiments;

FIGURE 22 illustrates another example virtual apparatus, according to certain embodiments;

FIGURE 23 illustrates another example method by a wireless device, according to certain embodiments; FIGURE 24 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 25 illustrates another example method by a network node, according to certain embodiments;

FIGURE 26 illustrates another example virtual apparatus, according to certain embodiments;

FIGURE 27 illustrates another example method by a wireless device, according to certain embodiments;

FIGURE 28 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 29 illustrates another example method by a network node, according to certain embodiments;

FIGURE 30 illustrates another example virtual apparatus, according to certain embodiments;

FIGURE 31 illustrates another example method by a wireless device, according to certain embodiments;

FIGURE 32 illustrates an example virtual apparatus, according to certain embodiments;

FIGURE 33 illustrates another example method by a network node, according to certain embodiments; and

FIGURE 34 illustrates another example virtual apparatus, according to certain embodiments.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

In some embodiments, a more general term “network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, Master eNodeB (MeNB), a network node belonging to Master Cell Group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operation and Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. Evolved-Serving Mobile Location Centre (E-SMLC)), Minimization of Drive Tests (MDT), test equipment (physical node or software), etc.

In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, UE category Ml, UE category M2, Proximity Services UE (ProSe UE), Vehi cl e-to- Vehicle UE (V2V UE), Vehicle-to-Anything (V2X UE), etc.

Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general, “gNodeB” could be considered as device 1 and “UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.

According to certain embodiments, methods, systems, and techniques are provided to enable the NW to configure and transmit PEI only if there is substantial amount of UEs present in the cell that can benefit from PEI, so that PEI transmissions and spent resources are not wasted. According to certain embodiments, NW resources should be spent only if some high priority UEs (e.g. based on subscription) and/or otherwise considerable amount of UEs are using it. According to certain embodiments, the methods, systems, and techniques may be applied regardless of adopted PEI signal type (e.g. DCI- or sequence-based) and location in relation to POs.

Note that throughout the document, the term idle/IDLE addresses both RRC IDLE and RRC INACTIVE states.

Selective Configuration of PEI

For example, according to certain embodiments, methods, systems and techniques are provided for providing PEI to a subset of UEs or UE types. In a particular embodiment, the method may include: o Determining criteria for UE types that should be provided a PEI (poor link quality, reduced capability, sparse traffic pattems/short DRX cycle, . . .) o Determining whether those types of UEs are present and whether they are utilizing the PEI (via gNB procedures testing the UE with/without PEI, info from CN, UE reporting, NW statistics)

As another example, according to certain embodiments, methods, systems and techniques are provided for providing PEI in a subset of POs. In a particular embodiment, the method may include: o Selecting the pattern of PEI-assisted POs (group offset, group duration, group density) o Mapping UEs benefitting from PEI with those POs (CN-based UE ID/RNTI allocation)

As another example, according to certain embodiments, methods, systems and techniques are provided for signaling the selective PEI configuration to UEs. In particular embodiments, the method may include representing selective PEI information in SIB, via RRC dedicated signaling, DCI, etc.

According to certain embodiments, the methods, systems, and techniques may include one or more of:

• Signaling PEI configurations that apply only to certain UE types, or to certain PO subsets

• CN providing info about UE PEI capability or UE type at paging time

• UE feedback/request related to PEI usage

• NW (gNB) upon paging, experimenting with PEI removal (not transmitting) despite that it is configured to see if UEs actually use PEI. . . FIGURE 3 illustrates a high-level logical flow of a method 50 by a network node, according to certain embodiments. The method may include one or more of the illustrated steps.

In step 52, the network node determines for which UEs, UE categories, or UE types it is beneficial to provide PEI. More specifically, the network node determines which UEs or UE types should be provided PEI, given the degree of benefits for the UEs and associated network node resource tradeoffs.

In a particular embodiment, the network node may assign a benefit metric or category to each UE type, characterizing the utility of PEI for that type. The benefit metric may be based on packet switch (PS) gains from PEI for that type of UE, the number of UEs of that type in the system, cell, etc. For example, if the UE is a reduced capability UE (RedCap UE) with respect to, for example, an eMBB UE, then the UE may need more measurement time before a PO to decode the paging PDSCH. For example, the UE may need to measure 3 SSBs instead of 1 prior to PO processing. Or, in a particular embodiment, if the UE belongs to XR (e.g., Al, VR, MR) category and PS is an important criterion. Alternatively, the UE may be located at the cell edge thereby experiencing a lower SINR and, thus, need a longer a wake-up time to decode a single paging PDSCH.

In a particular embodiment, the network node may also estimate a NW cost metric associated with providing PEI to different UE types, based on e.g. the PEI transmission resources, gNB energy penalty due to waking up for PEI transmission, paging rates for the given UE type, the number of such UEs in the system, etc.

In a particular embodiment, the network node may then determine that UE types whose benefit metric exceeds their cost metric should be prioritized for PEI. Alternatively, the network node may value each of these benefits individually such as, for example, if the benefit metric exceeds a first threshold or the cost metric exceeds a second threshold. Yet in another approach, the network node may make this decision based on the benefit metric be more than the first threshold and the cost metric being more than the second threshold.

Some example UE types and categories that are likely to benefit from PEI may include:

• Cell-edge UEs or UEs with poor link conditions (e.g. SINR below a specific threshold, e.g., 0 dB), since paging reception requires extensive loop convergence processing • Redcap or other low-complexity UEs that experience lower SINR due to simplified receiver design, e.g., few RX branches, lower accuracy components, such as a lower accuracy LO, etc.

• UEs with long DRX cycles and/or low data transmission duty cycle, since idle mode operation constitutes a larger fraction of their total power consumption. E.g., the UE wakes up after a long DRX cycle, it may need more synchronization effort than a UE which wakes up after a shorter DRX cycle.

• UEs with short DRX and low paging rates, since most paging monitoring operations do not lead to paging reception and the PO monitoring constitutes unnecessary energy consumption. NW commitment to transmit PEI to these UEs will in fact be cheap in spite of short DRX, since PEI transmission will occur infrequently.

• Other UEs that have high idle mode energy weight in relation to total energy consumption, e.g., XR, a battery-powered sensor in a factory, etc.

Furthermore, in a particular embodiment, the network node may keep track of the amount of time the above identified UEs spend in the cell. E.g. a fast-moving UE that typically have shown to spend a few seconds in the cell may be excluded (or given a lower weight) from PEI transmission decisions.

For the case of a UE in an RRC inactive, the UE assistance information sent by the UE while it is connected to the network node can be used for UE categorization.

In a particular embodiment, the network node may determine whether to apply PEI to one or more UEs based on UE activity level, type of service or application or based on certain type of signal transmission periodicity (e.g. SSB periodicity).

• UE activity level comprises DRX cycle configuration from which network knows how frequently the UE is expected to be awake, how long the UE is going to be awake and its active time etc. For example, certain types of UEs (e.g. loT, RedCap type of devices) may be configured with long DRX cycles allowing them to sleep for longer time and save battery life while other type of UEs can be configured to wake up more frequently (e.g. handled devices). In one specific example, the NW node is may configure PEI only to UEs which are configured with long DRX cycles.

• Type of service/application comprises information about type of application or service being used by the UE such as temperature monitoring, in houses for alarm monitoring, in buildings for detecting activity, in farming fields etc. The information may also indicate the mobility state of the UE, e.g. whether it is stationary or highly moving UE. For example, the NW may configure PEI only when there are UEs which operate certain type of service/application. In one specific example, PEI can be applied for service type 1 and 2, but not for service type 3 and 4.

• Periodicity of certain types of signals includes how frequently they are transmitted to the UE. The said type of signals are used by the UE for detecting the presence of PEI or performing time- and/or frequency tracking prior to receiving PEI. In one specific example, the network node may only configure PEI UEs when the SSB transmission periodicity is greater than a certain thresholds, e.g. SSB transmission periodicity > X ms.

In particular embodiments, the network node may become aware of the type of the UEs in different ways. In one example embodiment, the UE may inform the network node explicitly of its type, e.g., Redcap, eMBB, XR, etc. The notification can be as part of the higher layer signaling at the time of connection establishment (e.g. via dedicated RACH resources), or e.g., as part of the capability report. In another example embodiment, the network node may deduce the type of UE based on its capability report, e.g., if the UE reports a capability of employing one receiver (RX) chain, then the NW may deduce that this is a Redcap UE, or belongs to the power consumption critical UEs.

At optional step 54, the network node may optionally determine whether the prioritized UE types selected in step 52 are currently in the cell or cell cluster coverage area. This can be done in various manners as a general status estimation (not associated with specific paging events):

• The UE can announce the capability of using PEI, or about its UE type when connecting to the network node.

• For inactive UEs, the RAN fetches the UE type distribution from the list of registered UEs in the RAN, in a given cell or cell cluster (paging area).

• For idle UEs, the CN can send an indication to RAN that there are prioritized UEs (e.g. Redcap UEs) located within the cluster of cells that constitutes the tracking or paging area. The CN may then also send an indication when the prioritized UEs have left the area.

• The network node uses its deployment knowledge to estimate a corresponding fraction of idle UEs in low SINR conditions and whether these UEs spend considerable amount of time in the cell. For example, the network node may know that it is covering an area where high-speed UEs constitute that majority of the UEs in the cell. As another example, the network node may know that it is deployed in an area covering certain portion of a highway/motorway in which UEs only spend few seconds in the cell. PEI transmission in such cell PEI is then not seen as beneficial. Conversely, the network node may know that is deployed in an area that is supposed to cover a large area e.g. in a rural area to cover 100s of km with potentially no neighboring cells meaning a high risk for UEs at cell edge experiencing poor coverage. In this latter case PEI transmission may be justified if UEs at cell edge have connected to the network node.

• The network node uses connected mode SINR distribution to estimate a corresponding fraction of idle UEs in low SINR conditions. (The same principle can be used for qualitative UE type criteria, like redcap UEs, or UEs with low traffic duty cycle.)

• The network node uses previous statistics re. UE constitution and paging activity during the given time of day, etc.

Alternatively, or additionally, the network node may determine the presence of a prioritized UE at the paging instance: o Request from CN includes a flag indicating that a prioritized UE is targeted, that a certain UE type is targeted, or that PEI should be transmitted.

■ Explicit indication before any paging, may be provided via e.g., N2 interface o The CN upon paging announce the PEI capability of the UE to RAN, so the RAN can configure/transmit PEI accordingly. The network node may upon the paging request from CN containing a list of UEs, treat the individual UEs of different capabilities differently such that non-PEI-capable UEs are paged immediately in their imminent PO whereas for PEI-capable UEs delay the paging process until imminent PEI occasions. o In some cases, use of PEI might be required in certain operation mode (e.g. SINR < XI dB) or to perform certain tasks or operation certain type of service/application (e.g. to operate loT type of services using RedCap). In these scenarios, the network node can expect the UE to be configured, or capable of receiving (decoding and processing) PEI. In optional step 56, the UE may further optionally obtain information whether UEs are utilizing the PEI that is being transmitted. One or more of the following approaches may be used:

• UEs can feed back to the network node that they perform PEI detection. This feedback can be provided, for example, during the connection setup (e.g., msg. 3 in the RA procedure) after the UE has been paged or via any other signaling such as assistance data provision while in connected o Such feedback may be provided for PEI linked to some POs but not all.

• In a scenario in which PEI is currently not configured/transmitted applicable for certain UEs, the UEs can inform the network node (in a similar manner as above case) whether they would actually benefit if PEI would have been transmitted.

• The network node can test the UE whether it really uses PEI such as, for example, by configuring but not transmitting PEI and see how the UE responds. If a UE is paged and it responds despite missing PEI, the network node can deduce that the UE skips PEI monitoring. Such testing is preferably done when there is no actual DL data for the UE that would require connecting. Alternatively, the network node may include additional commands in PEI which if the UE is not responsive to them, then the network node may deduce that the UE is not utilizing PEI.

In optional step 58, the network node optionally determines which POs will be signaled using PEI.

In a baseline embodiment, all POs may be preceded by PEI if they contain one or more prioritized UEs.

In another embodiment, a subset of POs but not all POs may be preceded by a PEI. The subset may be defined in multiple ways, some examples being:

• Every N-th PO, specified by parameters N and offset with regard to, for example, start of frame or frame group

• A contiguous group of POs, specified by group length M and offset of start of group with regard to, for example, start of frame or frame group

• Combination of the two, every N-th in a group of length M

• Specifically per individual PO

• Alternatively, the NW may determine the POs which are not associated with a PEI in similar ways as mentioned above. The CN/RAN may ensure that UEs of prioritized types are mapped to selected POs by assigning tailored UE IDs related to PO determination that result in the desired mapping according to the PO formula. The assignment may target a specific PO or any of the POs in the above defined PO subset.

In step 60, the network node provides selective PEI configuration info to the UEs.

In a particular embodiment, the PEI configuration is only applicable to a specific BWP.

In a particular embodiment, the PEI configuration, e.g. in SIB, is augmented with UE type list or PO subset list to which the configuration applies. Other UEs or other PO location may not assume that PEI is transmitted.

The UE type list may be classified according to UE category (e.g. Redcap), link condition (e.g. SINR<S1), DRX cycle length (e.g. period > Tl), or other criteria.

In a particular embodiment, the selective PEI UE type list may be a list of UE types where PEI is not provided, e g. URLLC or eMBB UEs.

If a UE type list is not provided, then in a particular example embodiment, PEI may be assumed to apply to all UE types.

The selective PEI configuration info may be provided via same mechanisms as the non- selective (conventional) PEI info.

Alternatively, in a particular embodiment, the selective PEI configuration can be based on one or more pre-configured parameters, e.g., as part of the standardization specifications. For example, the PEI or a variant of PEI may not be applicable to the eMBB UEs but to Redcap UEs, or that PEI is only applicable to DRX cycle above a first threshold, e.g., 2.56 sec.

In all aspects above, the network node may provide a dedicated configuration to the UE that overrides broadcast configuration for that UE. Such dedicated configuration be tailored for that UE based on historical behavior of the UE with respect to e.g., PEI misdetection rate, traffic model, movement behavior, known hardware architecture or alike.

In step 62, the network node performs paging operations, whereby paging prioritized UE types is preceded by PEI transmission while paging other types may not be.

In a particular embodiment, the network node provides PEI for all prioritized UE types in any PO instance where they are paged, while PO instances that do target prioritized UEs are not preceded by a PEI (or are not guaranteed to be preceded).

In another particular embodiment, the PO subset indicated for selective PO is always preceded by a PEI when paging transmission is present, while other POs are not guaranteed to be preceded by a PEI. In addition to selective configuration/transmission of PEI, the network node may also decide to deactivate PEI such as, for example, by removing the configuration, or other indications such as LI based signaling, according to certain embodiments. The network node may make this decision if no PEI eligible UEs are within a cell or cluster of cells. For example, if there is no Redcap UE in a cell or a cluster of cells or the number of Redcap UEs is below a specific level, then the network node may decide to deactivate/unconfigure PEI. Alternatively, the network node may test to see if at least a specific number of UEs within a cell or cluster of cells employ PEI by methods described earlier. If it turns out that this condition is not satisfied, then the network node may decide to deactivate or unconfigure PEI.

In some scenarios, there may be differences between selective PEI configurations between neighbor cells or neighboring paging areas. Then as the UE changes its paging/tracking area, the UE may inform the network node about the new camping cell. Thus, the network obtains information about the presence of the UE and applies the selective PEI policy that is in effect in the new area to future paging transmissions.

Dynamic Activation and Deactivation of PEI

According to certain other embodiments, methods and systems are provided for the dynamic activation and/or deactivation of DCI-based PEI. Particular embodiments may provide for the dynamic activation and/or deactivation of DCI-based PEI using a bitfield in the PEI DCI. Other embodiments may provide for the dynamic activation and/or deactivation of DCI-based PEI using a bitfield in paging DCI. Still other embodiments may provide for the dynamic activation and/or deactivation of DCI-based PEI using paging DCI and PEI DCI. Still other embodiments may additionally or alternatively use RNTLbased PEI availability signaling.

According to certain embodiments, methods and systems are provided for the dynamic activation and/or deactivation of RS-based PEI. Particular embodiments may provide for the dynamic activation and/or deactivation of RS-based PEI using a bitfield in the paging DCI. Other embodiments may provide for the dynamic activation and/or deactivation of RS-based PEI using a characteristic in a sequence such as, for example, a RS.

According to certain embodiments, methods and systems are provided for implicit activation and/or deactivation of PEI in the wireless device (such as, for example, a UE, based on configured and/or preconfigured triggers from the network and/or as internally decided by the wireless device. In particular embodiments, these methods and systems can be used to control activation and deactivation of PEI both on a cell-specific level (affecting all POs of the cell), a UE groupspecific, and/or down to individual PO level.

According to certain other embodiments, methods, systems, and techniques are provided to enable the NW to configure and transmit PEI only if there is substantial amount of UEs present in the cell that can benefit from PEI, so that PEI transmissions and spent resources are not wasted. NW resources should be spent only if some high priority UEs (e.g. based on subscription) and/or otherwise considerable amount of UEs are using it. According to certain embodiments, the methods, systems, and techniques may be applied regardless of adopted PEI signal type (e.g. DCI- or sequence-based) and location in relation to POs.

According to certain embodiments, methods, systems, and techniques are provided to enable the NW to dynamically activate or deactivate PEI. In a particular embodiment, the methods, systems, and techniques may be Layer 1 (Ll)-based. The underlying mechanisms are particularly disclosed within the following aspects:

• Dynamic activation/deactivation of DCI based PEI

- Dynamic activation/deactivation using a bitfield in PEI DCI

- Dynamic activation/deactivation using a bitfield in paging DCI

- Interaction of Dynamic activation/deactivation using a paging and PEI DCI

- RNTLbased PEI availability signaling

• Dynamic activation/deactivation of RS based PEI

- Dynamic activation/deactivation using a bitfield in paging DCI

- Dynamic activation/deactivation using a characteristic in a sequence, e.g., a RS

• Implicit PEI deactivation in UE based on (pre-)configured triggers from NW or internally decided by UE

These methods, systems, and techniques can be used to control activation and deactivation of PEI both on cell-specific level (affecting all POs of the cell), UE group-specific, and/or down to individual PO level.

According to certain embodiments, it may be assumed that the network node provides a PEI configuration, e.g., using higher layer signaling such as SI broadcast. Thereby, UEs can receive the PEI configuration, monitor PEI, and if PEI indicates that there is a paging message, monitor the associated PO. The PEI can be either based on a DCI (i.e., indication of PEI is conveyed through a DCI) or based on a sequence, such as a RS, e.g., SSB or Tracking Reference Signal (TRS) like sequences.

Typically, a network node configures or unconfigures PEI through a legacy SI update procedure. For example, if the network node wants to turn off PEI functionality, it must transmit an updated SI wherein PEI configuration is absent. Such procedure implies transmitting a PDCCH including a short message (systemlnfoModification) from the network node in all possible POs to reach all UEs of the cell. Thereby, UEs may understand that something will be changed on the broadcast channel at the upcoming modification period (each modification period being [2..16] x DRX cycle), at the next modification period. Thus, the UEs may re-read the system information blocks to check for potential updates. This is not only costly for the network node, but also requires all UEs, irrespective of whether they are capable/interested in PEI configuration, to re-read the broadcast system information. Furthermore, the broadcast system information is typically applicable to all/large range of POs rather than on individual PO level due to the vast amount of POs (up to 4 POs per 10ms frame within a DRX cycle) available in the cell (individual PO level configuration would consume excessive amount of bits on broadcast).

However, according to certain embodiments disclosed herein, various mechanisms are provided to enable the network node to activate or deactivate PEI for one or more POs. When a PEI is activated (e.g. for a PO), the UE can monitor PEI in the PEI occasion(s) corresponding to the PO. From network node perspective, when a PEI is activated and whenever the network node transmits a paging message in that PO, the network node also transmits a PEI in at least one PEI occasion(s) corresponding to the PO.

When a PEI is deactivated for a PO (e.g. for a PO), UE does not expect a PEI in PEI occasion(s) corresponding to the PO. From the network node perspective and when PEI is deactivated, when the network node transmits a paging message in a PO, the network node need not transmit a PEI in any PEI occasions associated with that PO.

FIGURE 4 illustrates a schematic example 60 of deactivation of PEI, according to certain embodiments. In the depicted example PEI is deactivated using an indication on paging DCI from the next PO associated with the same group of UEs.

According to certain embodiments, PEI is based on a DCI signal, and as such is associated with a specific RNTI, e.g., P-RNTI, and it may also include a non-zero payload. A UE in idle mode is expected to monitor a PEI DCI or a paging DCI. Dynamic activation/deactivation of PEI can be included in at least one of the PEI DCI and a paging DCI, e.g., as an additional bitfield. Below we discuss each of these possibilities. According to certain other embodiments, an additional bitfield is configured in PEI DCI which can indicate if the PEI is active or deactivated from one or more of the upcoming POs. The bitfield can be configured within PEI DCI as part of the higher layer PEI configuration e.g., in SI, and/or based on pre-configuration such as, for example, as in a standardization specification (e.g. the bitfield is always present when PEI is configured).

In a particular example embodiment, the bitfield can indicate if PEI is going to be deactivated from the next PO, or another PO (configurable by the network). E.g., a bit “1” may mean that PEI is deactivated, but a “0” bit may either mean that it is active at least for another PO, or reserved. (Alternatively, inverse polarity compared to the examples may be used here and elsewhere.)

In another example embodiment, the deactivation/activation may be associated with a validity timer. For example, a bit “1” may mean that PEI is deactivated for a specific duration of time after one or more of the upcoming POs. The duration of time during which the PEI is deactivated can be a number of ms, a number of POs, slots, frames, etc. An alternative bit can be either reserved or mean that PEI remains activated at least for the duration of the validity timer. The validity timer can be either configured as part of PEI configuration or can be based on preconfiguration such as, for example, a set of one or more validity timers as part of standardization documentations or a combination of both. Herein, it is recognized that the next PO can be the next PO in the cell or the next PO for the group of UEs that monitor this PEI. The interpretation or next PO can be either configured by the network node such as, for example, as part of higher layer signaling, or pre-configured such as, for example, as part of standardization documentations.

In an example particular embodiment, the UE acquires PEI configuration information that includes at least PEI resource information as well as a first parameter associated with activation/deactivation of PEI resources. UE monitors for a DCI and determines whether a PEI resource is activated or deactivated based on the detected DCI and the first parameter associated with activation/deactivation of PEI resources. The first parameter can be a bitfield pointer value (e.g. bitfield value 2). The UE determines that the bitfield corresponding to the bitfield pointer value in the detected DCI is set to a first value, where the first value corresponds to activation of PEI resources. The UE assumes the PEI resources are activated and monitors PEI in the corresponding PEI occasions. UE detects PEI in a PEI resource, and UE attempts to decode paging message in a corresponding PO associated the detected PEI. The UE detects another DCI. The UE determines that the bitfield corresponding to the bitfield pointer value in the detected DCI is set to a second value, the second value corresponding to deactivation of PEI resources. The UE assumes the PEI resources are deactivated and skips monitoring PEI in the corresponding PEI occasions. In the example scenario, UE stops monitoring of PEI in PEI resources if the UE does not detect PEI for a time duration that is based on the timer value (For example, 10 seconds). UE monitors paging in POs, and if the UE detects a paging DCI and the bitfield (corresponding to the bitfield pointer) in the detected paging DCI is set to a first value, the UE starts monitoring PEI in the PEI resources. UE detects PEI in a PEI resource, and UE attempts to decode paging message in a corresponding PO associated the detected PEI.

In another example embodiment, the bitfield may include one or more bits, with each combination indicating a different purpose. For example, the configuration may include 2 bits, and a bit combination of “11” may indicate PEI is deactivated until further notice, while a combination of “10” may indicate that PEI is deactivated for a first validity timer, or alternatively a bit combination of “01” may indicate that PEI is active for at least a second a validity timer. And finally, a bit combination of “00” may indicate PEI is active for the time being (until further notice), or it is reserved. In a general representation, multiple bits in the DCI may be used to specify one of the preconfigured timer durations (i.e. the time during which the PEI remains active or will be deactivated), depending on the chosen signaling polarity. The polarity itself may also be specified as part of PEI configuration in the SI or in the specification.

In another example embodiment, the network node may DTX transmission of the PEI activation/deactivation bitfield. In this case, the UE either follows the default configuration, or the latest indication in PEI activation/deactivation field, or potentially another operation configured by the network node. For example, if the PEI activation/deactivation bitfield is not transmitted (i.e., the associated bitfield in the payload is empty), the UE may assume that PEI is active for the time being if such an indication is configured by the network node or that the latest PEI explicitly indicated that PEI is active. As a related embodiment, one bit combination in the bitfield may be used to indicate no change to the current PEI activation state (e.g., previously launched timer duration).

The PEI adaptation bit fields may include a bit indicating whether the adaptation indication applies to the POs that the PEI addresses or to all POs in the system. Alternatively, this info may be provided in the PEI configuration in the SIB. If the adaptation indication applies only to a subset of POs, the UE may not assume the availability of other PEI transmissions for any receiver processing purposes.

In another example embodiment, when the UE receives a PEI deactivation, in one approach, the UE falls back to the default PO monitoring. Thus, the UE may fallback to monitoring every PO irrespective of PEI. In another approach, for example, if configured by the network node, or indicated in PEI DCI, the UE may assume that there is no paging for one or more upcoming POs or until PEI is transmitted again.

In another example embodiment, the PEI activation/deactivation is simply an indication that the associated part of the PEI configuration. For example, if PEI is active or not has changed and the UE should read that part of SIBn. The PEI adaptation bit value (0/1) is thus a trigger signal for relevant SI update and does not convey the actual PEI state info (active/inactive). For example, if the bit is 1, the UE reads PEI-related SIB info, where current PEI state and, for example, validity timer info will be provided. As such the UE does not have to read all the SIBs to get an update of SI. In one aspect, the configuration change is immediate, meaning that the update is immediately provided over the broadcast channel and the UE re-reads the information immediately, rather than having to wait until an upcoming modification period boundary. As can be understood, only the UEs that are consuming PEI are notified and re-read the broadcast information instead of the complete UE population of the cell.

In a particular example embodiment, which may be particularly preferable for PEI activation indication, an additional bitfield is configured in the paging DCI which can indicate if the PEI is going to be active or deactivated from one or more of the upcoming POs. The bitfield can be configured within the paging DCI either as part of the higher layer paging configuration such as, for example, in SI, or the bitfield can be automatically configured for paging based on pre-configuration, such as, for example, as in a standardization specification. Some examples are elaborated below but the approaches described above may be applicable to the following examples as well.

In a simple example embodiment, in a similar way as the case of PEI based indication, the bitfield can indicate if PEI is going to be deactivated from the next PO, or another PO (configurable by the network node). For example, a bit “1” may mean that PEI is deactivated, but a “0” bit may either mean that it is active at least for another PO or reserved. In another example embodiment, the deactivation/activation may be associated with a validity timer. For example, a bit “1” may mean that PEI is deactivated for a specific duration of time after one or more of the upcoming POs. The duration of time can be a number of ms, a number of POs, slots, frames, etc. An alternative bit can be either reserved or mean that PEI is active at least for the duration of the validity timer. The validity timer can be either configured as part of PEI configuration, or can be based on preconfiguration such as, for example, a set of one or more validity timers as part of standardization documentations or a combination of both.

In another example embodiment, the bitfield may include one or more bits, with each combination indicating a different purpose. For example, the configuration may include 2 bits, and a bit combination of “11” may indicate PEI is deactivated until further notice, while a combination of “10” may indicate that PEI is deactivated for a first validity timer, or alternatively a bit combination of “01” may indicate that PEI is active for at least a second a validity timer. And finally, a bit combination of “00” may indicate PEI is active for the time being, or it is reserved.

In another example embodiment, the network node may DTX transmission of the PEI activation/deactivation bitfield in the paging DCI. In this case, the UE either follows the default configuration, or the latest indication in PEI activation/deactivation field, or potentially another operation configured by the network node. For example, if the PEI activation/deactivation bitfield is not transmitted, then the UE may assume that PEI is active for the time being if such an indication is configured by the network node, or that the latest PEI explicitly indicated that PEI is active.

In another example embodiment, the PEI activation/deactivation bitfield may be applicable to all the UEs receiving the same paging DCI within a PO, or only to the group which is indicated potentially with another bitfield in PEI.

The PEI adaptation bit fields in the paging DCI may include a bit indicating whether the adaptation indication applies to the current PO or to all POs in the system. Alternatively, this info may be provided in the PEI configuration in the SIB. If the adaptation indication applies only to a subset of POs, the UE may not assume the availability of other PEI transmissions for any receiver processing purposes.

In another example embodiment, when the UE receives a PEI deactivation, in one approach, the UE falls back to the default PO monitoring, i.e., monitor every PO irrespective of PEI. In another approach, for example, if configured by the network node, or indicated in paging DCI, the UE may assume that there is no paging for one or more upcoming POs, or until PEI is transmitted again.

In another example embodiment, the PEI activation/deactivation in the paging DCI is simply an indication that the associated part of the PEI configuration such as, for example, if PEI is active or not has changed and the UE should read that part of e.g., SIBn. As such the UE does not have to read all the SIBs to get an update of SI. Some or all of the aspects of the PEI option described above are applicable here as related to immediate update of information.

In another example embodiment, the PEI activation/deactivation bitfield can be configured only for a paging DCI scheduling a paging PDSCH, or alternatively as a short message together with a short message based paging DCI. For example, the network node may wish to activate PEI from a next PO without necessarily needing to page any UE in that PO and, thus, it can send a short message paging DCI indicating that PEI is activated. In a related realization, the UE does not expect to receive contradictory indications if both paging DCI scheduling a paging PDSCH and a short message paging DCI are sent together.

FIGURE 5 illustrates an example 70 of interaction of dynamic activation/deactivation using a paging and PEI DCI, according to certain embodiments.

According to certain embodiments, the dynamic control of PEI is done through a mixture of the ON/OFF commands described earlier in PEI and PO DCIs. As such, even if a PEI configuration is broadcast, the UE cannot assume that PEI is transmitted for its assigned PO unless it has captured its PO DCI in which the current status (ON/OFF) is indicated. In case a UE entered a cell, has read the PEI configuration on broadcast channel, read/decoded at least one of its PO DCIs in which it said that PEI is currently ON, the UE can start relying on PEI. From now on, the UE can monitor PEIs in which an OFF indication (or a PEI configuration update indication) can make the UE to fallback to regular PO decoding.

It shall be noted that in the aspects above, if the UE for any reason ignored a PEI decoding (e.g. due to being occupied with other Rx activity), it shall fallback to regular PO decoding as there is otherwise a risk that the UE might have missed an OFF command in the PEI.

In a particular embodiment, the UE can acquire PEI configuration information that includes at least PEI resource information, a timer value, and a bitfield pointer within a paging DCI. UE stops monitoring of PEI in PEI resources if the UE does not detect PEI for a time duration that is based on the timer value (For example, 10 seconds). UE monitors paging in POs and, if the UE detects a paging DCI and the bitfield (corresponding to the bitfield pointer) in the detected paging DCI is set to a first value, the UE starts monitoring PEI in the PEI resources. UE detects PEI in a PEI resource, and UE attempts to decode paging message in a corresponding PO associated the detected PEI.

In one embodiment relating to the dynamic activation/deactivation using a paging DCI (described above), the UE may be configured with at least two RNTIs for PEI monitoring. If the first RNTI is detected, the UE may assume that PEI will also be activated in conjunction with the next PO. If the second RNTI is detected, the UE falls back to PO monitoring without relying on PEI information. The UE may tentatively perform PEI monitoring to again detect PEI with the first RNTI to return to PEI-assisted mode of operation.

According to certain embodiments, PEI is based on a sequence, e.g., a specific RS, such as SSB or TRS. For example, if the UE receives a TRS before a PO, then it indicates that there is a paging PDCCH transmitted. In this case the activation/deactivation can performed either associated with a sequence, or as part of a bitfield in the paging DCI as described herein. Since, the latter is basically done in the same way, only the mechanisms for the sequence-based PEI activation/deactivation indication are detailed below.

Dynamic activation/deactivation using a characteristic in a sequence, e.g., a RS

In a particular example scenario, the UE may receive a first sequence such as, for example, a RS signal with a first characteristic, e.g., a TRS with a first scrambling code, indicating that the UE can expect a paging. Furthermore, the UE may receive a second sequence with a second characteristic, where the second sequence indicate that PEI is deactivated from one or more of the upcoming POs (can be configurable by the network node or specified in standardization documents). Additionally, the UE may receive a PEI with a third sequence, with a third characteristic, where the third sequence indicates that PEI is (re)activated. In one specific realization, the first and the third sequence maybe similar.

The characteristic may not be limited to the sequence but may in general be any dimension in the TRS configuration (time location, frequency location, or code/sequence) specified in CSI- RS resource definition. To that effect, the UE may be configured with multiple resources and it may be monitoring multiple possible TRS transmissions. Tentative reception results are compared according to their quality and the resource with the highest quality (e.g. matched filter correlation output magnitude), optionally exceeding a threshold, is assumed to have been transmitted.

In another example embodiment, the activation or deactivation can be further associated with a validity timer. The validity timer can be configured by the network node or may be preconfigured such as, for example, as part of standardization documentations or a combination of both. For example, the network node may indicate an index in the standards. As such, the UE may receive a fourth sequence indicating that PEI is not transmitted for from one or more of the upcoming POs for a specific duration of time. Alternatively, the UE may receive a fifth sequence indicating that PEI is active for a specific validity timer. Note that the fourth or fifth sequence in this example can also replace the second or third sequence in the first example above.

In another example embodiment, the PEI activation/deactivation is simply an indication that the associated part of the PEI configuration, e.g., if PEI is active or not has changed and the UE should read that part of SIBn. As such the UE does not have to read all the SIBs to get an update of SI. For example, the UE may receive a sixth sequence indicating that the UE needs to reread a specific part of SIBn where PEI configuration is included.

In example embodiments above, it is assumed that the UE receives the associated configurations from higher layer signaling, e.g., SIB. Furthermore, another issue to look at is what happens when a UE just joins the cell and receives the underlying configuration. In this case, a specific indicator can be as part of the configuration letting the UE know if the PEI is currently active or not, and additionally when the indicator changes, then the NW is not required to start SI update. Alternatively, irrespective of PEI configuration, when the UE just joins a new cell, it is expected that the UE monitors paging, until it receives a first indication either in paging DCI or as part of PEI indicating if PEI is active or not.

Implicit PEI deactivation in UE based on (pre-)configured triggers from NW or internally decided by UE

According to certain embodiments, the UE may have been configured with certain triggers making it fall back to regular PO monitoring either temporarily or permanently depending on configuration. Such fallback mechanism need not necessarily be based on network configuration but may also take place in case the UE sees it fit as explained below.

Such triggers could be based on that the UE hasn’t received any PEI for X window duration or X times (X POs), in which case it assumes that it has probably missed PEI and should fall back for a certain amount of time (either configurable by the network node or decided by the UE e.g. until circumstances such as reception quality has improved). In one aspect, the window size X is configured by the network node. In another aspect, the window is derived by the UE itself based on historical typical PEI reception rate during same circumstances.

In another example embodiment, rather than a window, consecutive amount of PEI nonexistence (again configurable or based on UE history) triggers the behavior.

In yet another example embodiment, the UE falls back to regular PO monitoring in case one/several of the Rx quality related measurements (RSRP/RSRQ/SINR) fall below certain corresponding threshold (s) (peiMinRxQuality RSRP / RSRQ / SINR)

These configuration parameters mentioned above and configured by the network node can either be provided

• Via broadcast configuration in which case these configuration parameters are based on the typical values used by the group of UEs listening to those PO instances.

• Via dedicated signaling in which case these configuration parameters are tailored based on typical values for the specific UE that receives the dedicated message.

In another example embodiment, the UE does not completely fall back to regular PO monitoring in the cases above, but still decodes PEI and PO DCIs. In this aspect, PEI (either not received or received but not indicating paging message) shall by the UE be seen as help to avoid multiple SSB decoding needed for PDSCH decoding + the PDSCH decoding itself. Thus, in the identified cases:

• UEs always takes the PO PDCCH even if PEI was not received. In this case, the UE does not wake up to decode the SSBs in-between PEI and PO for the sake of PDSCH reception but still decodes the PO PDCCH. This way if UE has missed the PEI, there still is a chance to check in PO PDCCH whether the UE misdetected PEI. If PO PDCCH indicated paging message in this case, the paging PDSCH message is missed by the UE, but at least the UE now knows that it is experiencing misdetection can falls back to regular PO PDCCH processing.

• In one aspect, the UE behaves like the above bullet but not always, rather only in cases where there is potential risk for misdetection (e.g., when below the quality thresholds (peiMinRxQuality xxx) provided in PEI Fallback Config

FIGURE 6 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 6. For simplicity, the wireless network of FIGURE 6 only depicts network 106, network nodes 160 and 160b, and wireless devices 110. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 160 and wireless device 110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 160 and wireless device 110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

FIGURE 7 illustrates an example network node 160, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 7, network node 160 includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 illustrated in the example wireless network of FIGURE 7 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’ s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 160.

Processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include processing information obtained by processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 170 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 160 components, such as device readable medium 180, network node 160 functionality. For example, processing circuitry 170 may execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system on a chip (SOC).

In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 170 executing instructions stored on device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160 but are enjoyed by network node 160 as a whole, and/or by end users and the wireless network generally.

Device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 170. Device readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 170 and, utilized by network node 160. Device readable medium 180 may be used to store any calculations made by processing circuitry 170 and/or any data received via interface 190. In some embodiments, processing circuitry 170 and device readable medium 180 may be considered to be integrated.

Interface 190 is used in the wired or wireless communication of signalling and/or data between network node 160, network 106, and/or wireless devices 110. As illustrated, interface 190 comprises port(s)/terminal(s) 194 to send and receive data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or in certain embodiments a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal may then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to processing circuitry 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, instead, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 may be considered a part of interface 190. In still other embodiments, interface 190 may include one or more ports or terminals 194, radio front end circuitry 192, and RF transceiver circuitry 172, as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

Antenna 162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 162 may be coupled to radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

Power circuitry 187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power circuitry 187 may receive power from power source 186. Power source 186 and/or power circuitry 187 may be configured to provide power to the various components of network node 160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 186 may either be included in, or external to, power circuitry 187 and/or network node 160. For example, network node 160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 187. As a further example, power source 186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used. Alternative embodiments of network node 160 may include additional components beyond those shown in FIGURE 7 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface equipment to allow input of information into network node 160 and to allow output of information from network node 160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

FIGURE 8 illustrates an example wireless device 110. According to certain embodiments. As used herein, wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term wireless device may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a wireless device include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A wireless device may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a wireless device may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another wireless device and/or a network node. The wireless device may in this case be a machine-to- machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the wireless device may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A wireless device as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136 and power circuitry 137. Wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within wireless device 110.

Antenna 111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to wireless device 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 111 may be considered an interface.

As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprise one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 may be coupled to or a part of antenna 111. In some embodiments, wireless device 110 may not include separate radio front end circuitry 112; rather, processing circuitry 120 may comprise radio front end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered a part of interface 114. Radio front end circuitry 112 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to processing circuitry 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other wireless device 110 components, such as device readable medium 130, wireless device 110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 120 of wireless device 110 may comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and RF transceiver circuitry 122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and application processing circuitry 126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be a part of interface 114. RF transceiver circuitry 122 may condition RF signals for processing circuitry 120.

In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 120 alone or to other components of wireless device 110, but are enjoyed by wireless device 110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 120, may include processing information obtained by processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 120. In some embodiments, processing circuitry 120 and device readable medium 130 may be considered to be integrated.

User interface equipment 132 may provide components that allow for a human user to interact with wireless device 110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 132 may be operable to produce output to the user and to allow the user to provide input to wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed in wireless device 110. For example, if wireless device 110 is a smart phone, the interaction may be via a touch screen; if wireless device 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 132 is configured to allow input of information into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 132 is also configured to allow output of information from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface equipment 132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.

Auxiliary equipment 134 is operable to provide more specific functionality which may not be generally performed by wireless devices. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used, wireless device 110 may further comprise power circuitry 137 for delivering power from power source 136 to the various parts of wireless device 110 which need power from power source 136 to carry out any functionality described or indicated herein. Power circuitry 137 may in certain embodiments comprise power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 137 may also in certain embodiments be operable to deliver power from an external power source to power source 136. This may be, for example, for the charging of power source 136. Power circuitry 137 may perform any formatting, converting, or other modification to the power from power source 136 to make the power suitable for the respective components of wireless device 110 to which power is supplied.

FIGURE 9 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 200, as illustrated in FIGURE 7, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 9 is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.

In FIGURE 9, UE 200 includes processing circuitry 201 that is operatively coupled to input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221 or the like, communication subsystem 231, power source 233, and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 9, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information into UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 9, RF interface 209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface to network 243a. Network 243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 217 may be configured to interface via bus 202 to processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 may be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 may store, for use by UE 200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 221, which may comprise a device readable medium.

In FIGURE 9, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or different network or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 233 and receiver 235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 may include data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near- field network. Power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or partitioned across multiple components of UE 200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Further, processing circuitry 201 may be configured to communicate with any of such components over bus 202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 201 and communication subsystem 231. In another example, the non- computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 10 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of hardware nodes 330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized. The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 320 are run in virtualization environment 300 which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360 whereby application 320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 300, comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1 which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and/or instructions executable by processing circuitry 360. Software 395 may include any type of software including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 may be implemented on one or more of virtual machines 340, and the implementations may be made in different ways.

During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present a virtual operating platform that appears like networking hardware to virtual machine 340.

As shown in FIGURE 10, hardware 330 may be a standalone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 340, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to application 320 in FIGURE 10.

In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 may be coupled to one or more antennas 3225. Radio units 3200 may communicate directly with hardware nodes 330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signaling can be affected with the use of control system 3230 which may alternatively be used for communication between the hardware nodes 330 and radio units 3200.

FIGURE 11 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 11, in accordance with an embodiment, a communication system includes telecommunication network 410, such as a 3 GPP -type cellular network, which comprises access network 411, such as a radio access network, and core network 414. Access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 412.

Telecommunication network 410 is itself connected to host computer 430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 430 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between telecommunication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go via an optional intermediate network 420. Intermediate network 420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 420, if any, may be a backbone network or the Internet; in particular, intermediate network 420 may comprise two or more sub-networks (not shown).

The communication system of FIGURE 11 as a whole enables connectivity between the connected UEs 491, 492 and host computer 430. The connectivity may be described as an over- the-top (OTT) connection 450. Host computer 430 and the connected UEs 491, 492 are configured to communicate data and/or signaling via OTT connection 450, using access network 411, core network 414, any intermediate network 420 and possible further infrastructure (not shown) as intermediaries. OTT connection 450 may be transparent in the sense that the participating communication devices through which OTT connection 450 passes are unaware of routing of uplink and downlink communications. For example, base station 412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, base station 412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 491 towards the host computer 430.

FIGURE 12 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 12. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide a service to a remote user, such as UE 530 connecting via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the remote user, host application 512 may provide user data which is transmitted using OTT connection 550.

Communication system 500 further includes base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with host computer 510 and with UE 530. Hardware 525 may include communication interface 526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 500, as well as radio interface 527 for setting up and maintaining at least wireless connection 570 with UE 530 located in a coverage area (not shown in FIGURE 12) served by base station 520. Communication interface 526 may be configured to facilitate connection 560 to host computer 510. Connection 560 may be direct or it may pass through a core network (not shown in FIGURE 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 525 of base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already referred to. Its hardware 535 may include radio interface 537 configured to set up and maintain wireless connection 570 with a base station serving a coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 530 further comprises software 531, which is stored in or accessible by UE 530 and executable by processing circuitry 538. Software 531 includes client application 532. Client application 532 may be operable to provide a service to a human or non-human user via UE 530, with the support of host computer 510. In host computer 510, an executing host application 512 may communicate with the executing client application 532 via OTT connection 550 terminating at UE 530 and host computer 510. In providing the service to the user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both the request data and the user data. Client application 532 may interact with the user to generate the user data that it provides.

It is noted that host computer 510, base station 520 and UE 530 illustrated in FIGURE 12 may be similar or identical to host computer 430, one of base stations 412a, 412b, 412c and one of UEs 491, 492 of FIGURE 11, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 12 and independently, the surrounding network topology may be that of FIGURE 11.

In FIGURE 12, OTT connection 550 has been drawn abstractly to illustrate the communication between host computer 510 and UE 530 via base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 530 or from the service provider operating host computer 510, or both. While OTT connection 550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 550 between host computer 510 and UE 530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or in software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 511, 531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 520, and it may be unknown or imperceptible to base station 520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 511 and 531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 550 while it monitors propagation times, errors etc.

FIGURE 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12 For simplicity of the present disclosure, only drawing references to FIGURE 13 will be included in this section. In step 610, the host computer provides user data. In substep 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIGURE 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 14 will be included in this section. In step 710 of the method, the host computer provides user data. In an optional sub step (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

FIGURE 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 15 will be included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In substep 811 (which may be optional) of step 810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830 (which may be optional), transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 11 and 12. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section. In step 910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

FIGURE 17 depicts a method 1000 by a wireless device 110, according to certain embodiments. At step 1002, the wireless device 110 determines a first set of POs. At step 1004, the wireless device 110 receives, from a network node 160, a PEI configuration. The PEI configuration is associated with a group of wireless devices and the PEI configuration being associated with a second set of POs. At step 1006, the wireless device 110 determines whether the wireless device 110 belongs to the group of wireless devices associated with the PEI configuration.

At step 1008, if the wireless device belongs to the group wireless devices associated with the PEI configuration, the wireless device 110 attempts to receive a PEI, and if the PEI is received, the wireless device 110 monitors at least one of the POs in the second set of POs. Conversely, if the wireless device does not belong to the group of wireless devices associated with the PEI configuration, the wireless device 110 monitors at least one of the POs in first set of POs, at step 1010.

At step 1012, if a paging message for the wireless device 110 is received in the at least one monitored PO in the first set of POs or the second set of POs, the wireless device 110 transmits, to a network node 160, a message comprising information related to a usage of the PEI. In a particular embodiment, the wireless device 110 determines the first set of POs based on a UE ID associated with the wireless device 110.

In a particular embodiment, when the wireless device 110 determines, based on a UE ID, for example, that the wireless device 110 belongs to the group wireless devices associated with the PEI, the wireless device 110 determines to monitor a subset of POs either from the first or the second set of POs. The monitoring of the subset of the POs from the second set of POs is based on the reception of a PEI.

In a particular embodiment, the group of wireless devices comprises a minimum number of wireless devices 110 in a cell.

In a particular embodiment, the group of wireless devices comprises a number of wireless devices 110 with an ability to receive the PEI in a cell.

In a particular embodiment, the group of wireless devices comprises a number of high priority wireless devices in a cell.

In a particular embodiment, determining whether the wireless device 110 belongs to the group of wireless devices is based on a type of the wireless device 110.

In a particular embodiment, determining whether the wireless device 110 belongs to the group of wireless devices is based on a benefit metric characterizing a utility of the PEI for the wireless device 110.

In a particular embodiment, the wireless device 110 transmits information to the network node 160, and the information indicates at least one of the wireless device 110 is a prioritized UE; the wireless device 110 is a reduced UE capability; the wireless device 110 is a XR UE; a UE identifier associated with the wireless device 110; a presence of the wireless device 110 at a paging instance; a capability of the wireless device 110 to perform PEI detection; an indication that the wireless device 110 would benefit from receiving PEI; an indication that the wireless device 110 uses PEI; a location of the wireless device 110 with respect to a cell edge; a length of a discontinuous reception cycle of the wireless device 110; a value associated with a data transmission duty cycle of the wireless device 110; a paging rate of the wireless device 110; an idle mode energy weight of the wireless device 110; a type of service or application used by the wireless device 110; a signal transmission periodicity of the wireless device 110; an amount of time the wireless device 110 is in a cell; and an activity level of the wireless device 110.

In a particular embodiment, the PEI configuration is associated with a bandwidth part.

In a particular embodiment, the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be monitored. In a particular embodiment, the wireless device 110 receives, from the network node 160, at least one message indicating a deactivation of the PEI configuration.

In a further particular embodiment, the deactivation of the PEI configuration is based on a characteristic of the wireless device 110.

FIGURE 18 depicts a method 1100 by a network node 160, according to certain embodiments. At step 1102, the network node 160 determines a group of wireless devices 110 for receiving a PEI. The determining comprises obtaining information indicating whether the group of wireless devices 110 is using PEI. At step 1104, the network node 160 signals a PEI configuration to the group of wireless devices. At step 1106, the network node 160 determines at least one paging occasion for which to transmit the PEI. At step 1108, the network node 160 transmits the PEI to the group of wireless devices 110.

In a particular embodiment, obtaining the information comprises receiving the information from at least one wireless device 110, and the at least one wireless device is determined to be is included in the group of wireless devices based on the information.

In a particular embodiment, obtaining the information comprises autonomously determining whether the group of wireless device 110 is using the PEI.

In a particular embodiment, determining the group of wireless devices 110 for receiving the PEI comprises determining a number of wireless devices 110 with an ability to receive PEI in a cell.

In a particular embodiment, determining the group of wireless devices 110 for receiving the PEI comprises determining a number of high priority wireless devices 110 in a cell, and wherein the high priority wireless devices are utilizing the PEI.

In a particular embodiment, determining the group of wireless devices 110 for receiving the PEI includes determining a type of each wireless device 110 in the group of wireless devices 110, and each wireless device 110 is determined to be included in the group of wireless devices 110 based on the type of the respective wireless device 110.

In a further particular embodiment, the type of wireless device 110 may include and/or be based on at least one of: a reduced capability UE; a XR UE; and a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle being greater than a threshold; a length of a discontinuous reception cycle being less than a threshold; a value associated with a data transmission duty cycle being less than a threshold; a paging rate being less than a threshold; an idle mode energy weight being greater than a threshold; a type of service or application used by the wireless device; a signal transmission periodicity; an amount of time the wireless device is in a cell; and an activity level of the wireless device. In a particular embodiment, the network node 160 assigns a benefit metric to one or more of the wireless devices 110, and the benefit metric characterizes the utility or benefit for the wireless device 110 to receive PEI. Each wireless device 110 is included in the group of wireless devices 110 when the benefit metric is greater than a first threshold.

In a particular embodiment, the network node 160 assigns a cost metric to the one or more of the wireless devices 110, and the cost metric characterizing the cost of providing the PEI to each wireless device 110. Each wireless device 110 is included in the group of wireless devices 110 based on the cost metric.

In a further particular embodiment, at least one of the benefit metric and the cost metric is determined based on at least one of a number of types of wireless devices 110 in the group of wireless devices; PEI transmission resources; an energy penalty due to waking up for PEI transmission; a paging rate for a UE type associated with the group of wireless devices or anyone of the wireless devices in the group of wireless devices; and a number of wireless devices 110 in the system and/or cell.

In a particular embodiment, the information indicates at least one of the at least one wireless device 110 is a prioritized UE; the at least one wireless device 110 is a reduced UE capability; the at least one wireless device 110 is a XR UE; a UE identifier associated with the at least one wireless device 110; a presence of the at least one wireless device 110 at a paging instance; a capability of the at least one wireless device 110 to perform PEI detection; an indication that the at least one wireless device 110 would benefit from receiving PEI; an indication that the at least one wireless device 110 uses PEI; a location of the at least one wireless device 110 with respect to a cell edge; a length of a discontinuous reception cycle of the at least one wireless device 110 being greater than a threshold; a length of a discontinuous reception cycle of the at least one wireless device 110 being less than a threshold; a value associated with a data transmission duty cycle of a wireless device 110 being less than a threshold; a paging rate of the at least one wireless device 110 being less than a threshold; an idle mode energy weight of the at least one wireless device 110 being greater than a threshold; a type of service or application used by the at least one wireless device 110; a signal transmission periodicity of the at least one wireless device 110; an amount of time the at least one wireless device 110 is in a cell; and an activity level of the at least one wireless device 110.

In a particular embodiment, the PEI is transmitted based on information, and the information comprising at least one of at least one wireless device 110 in the group of wireless devices is in a cell or a coverage area; a number of wireless devices 110 within the group of wireless devices that are in the cell or the coverage area is greater than a first threshold; at least one wireless device 110 in the group of wireless devices has a cell quality value that is less than a second threshold; and a number of wireless devices 110 within the group of wireless that has a cell quality value that is less than a third threshold is greater than a fourth threshold.

In a further particular embodiment, the network node 160 receives the information from the at least one wireless device 110 and determines that the at least one wireless device 110 is in the cell or the coverage area based on the information.

In a particular embodiment, the network node 160 determines the at least one paging occasion for which to transmit the PEI comprises: determining that a subset of paging occasions for which to transmit the PEI.

In a particular embodiment, the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be transmitted.

In a particular embodiment, the network node 160 transmits, to at least one wireless device 110 that is not within the group of wireless devices, a page in a paging occasion without transmitting a PEI prior to transmitting the page.

In a particular embodiment, the network node 160 transmits, to at least one wireless device 110 in the group of wireless devices, at least one message indicating a deactivation of the PEI configuration.

In a particular embodiment, the deactivation of the PEI configuration is based on a characteristic of the at least one wireless device 110.

FIGURE 19 depicts another method 1200 by a wireless device 110, according to certain embodiments. At step 1202, the wireless device 110 receives, from a network node 160, a PEI configuration. The PEI configuration is associated with a group of wireless devices that comprises the wireless device 110. At step 1204, the wireless device 110 receives a PEI based on the PEI configuration.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group A and Group J embodiments described below and/or the claims provided herein.

FIGURE 20 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 8). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 8). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 19 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 19 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first receiving module 1110, second receiving module 1120, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first receiving module 1310 may perform certain of the receiving functions of the apparatus 1300. For example, first receiving module 1310 may receive, from a network node 160, a PEI configuration. The PEI configuration is associated with a group of wireless devices that comprises the wireless device 110.

According to certain embodiments, second receiving module 1320 may perform certain other of the receiving functions of the apparatus 1300. For example, second receiving module 1320 may receive a PEI based on the PEI configuration.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group A and/or Group J embodiments described below and/or the claims provided herein.

As used herein, the term module may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

FIGURE 21 depicts another method 1400 by a network node 160, according to certain embodiments. At step 1402, the network node 160 determines a group of wireless devices 110 for receiving a PEI. At step 1404, the network node 160 signals a PEI configuration to the group of wireless devices 110. At step 1406, the network node transmits the PEI to the group of wireless devices 110.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group B and/or Group J embodiments described below and/or the claims provided herein.

FIGURE 22 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 8). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 8). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 21 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 21 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause determining module 1510, signaling module 1520, transmitting module 1530, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, determining module 1510 may perform certain of the determining functions of the apparatus 1500. For example, determining module 1510 may determine a group of wireless devices for receiving a PEI.

According to certain embodiments, signaling module 1520 may perform certain of the signaling functions of the apparatus 1500. For example, signaling module 1520 may signal a PEI configuration to the group of wireless devices 110.

According to certain embodiments, transmitting module 1520 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1520 may transmit the PEI to the group of wireless devices 110. Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group B and/or Group J embodiments described below and/or the claims provided herein.

FIGURE 23 depicts another method 1600 by a wireless device 110, according to certain embodiments. At step 1602, the wireless device 110 receives, from a network node 160, DCI comprising a first indicator associated with an activation or deactivation of PEI in at least one PO.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group C and Group J Example Embodiments described below.

FIGURE 24 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 23 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 23 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1710 and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first receiving module 1710 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1710 may receive, from a network node 160, DCI comprising a first indicator associated with an activation or deactivation of PEI in at least one PO.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group C and Group J Example Embodiments described below. FIGURE 25 depicts another method 1800 by a network node 160, according to certain embodiments. At step 1802, the network node 160 transmits, to at least one wireless device 110, DCI comprising a first indicator associated with an activation or deactivation of PEI in at least one PO.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group D and Group J Example Embodiments described below.

FIGURE 26 illustrates a schematic block diagram of a virtual apparatus 1900 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 1900 is operable to carry out the example method described with reference to FIGURE 25 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 25 is not necessarily carried out solely by apparatus 1900. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1910 and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1910 may perform certain of the transmitting functions of the apparatus 1900. For example, transmitting module 1910 may transmit, to at least one wireless device, DCI comprising a first indicator associated with an activation or deactivation of PEI in at least one PO.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group D and Group J Example Embodiments described below.

FIGURE 27 depicts another method 2000 by a wireless device 110, according to certain embodiments. At step 2002, the wireless device 110 receives, from a network node 160, a first sequence with a first characteristic indicating that the wireless device 110 is to monitor at least one PO. At step 2004, the wireless device 110 receives, from the network node 160, a second sequence with a second characteristic indicating a deactivation of PEI for the at least one PO.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group E and Group J Example Embodiments described below.

FIGURE 28 illustrates a schematic block diagram of a virtual apparatus 2100 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 2100 is operable to carry out the example method described with reference to FIGURE 27 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 27 is not necessarily carried out solely by apparatus 2100. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first receiving module 2110, second receiving module 2120, and any other suitable units of apparatus 2100 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first receiving module 2110 may perform certain of the receiving functions of the apparatus 2100. For example, first receiving module 2110 may receive, from a network node, a first sequence with a first characteristic indicating that the wireless device is to monitor at least one PO.

According to certain embodiments, first receiving module 2120 may perform certain of the receiving functions of the apparatus 2100. For example, first receiving module 2120 may receive, from the network node, a second sequence with a second characteristic indicating a deactivation of PE) for the at least one PO.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group E and Group J embodiments described below. FIGURE 29 depicts another method 2200 by a network node 160, according to certain embodiments. At step 2202, the network node 160 transmits, to at least one wireless device 110, a first sequence with a first characteristic indicating that the at least one wireless device is to monitor at least one PO. At step 2204, the network node 160 transmits, to the at least one wireless device 110, a second sequence with a second characteristic indicating a deactivation of PEI for the at least one PO.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group F and Group J Example Embodiments described below.

FIGURE 30 illustrates a schematic block diagram of another virtual apparatus 2300 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 2300 is operable to carry out the example method described with reference to FIGURE 29 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 29 is not necessarily carried out solely by apparatus 2300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first transmitting module 2310, second transmitting module 2320, and any other suitable units of apparatus 2300 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first transmitting module 2310 may perform certain of the transmitting functions of the apparatus 2300. For example, first transmitting module 2310 may transmit, to at least one wireless device, a first sequence with a first characteristic indicating that the at least one wireless device is to monitor at least one PO.

According to certain embodiments, second transmitting module 2320 may perform certain other of the transmitting functions of the apparatus 2300. For example, second transmitting module 2320 may transmit, to the at least one wireless device, a second sequence with a second characteristic indicating a deactivation of PEI for the at least one PO.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group F and Group J Example Embodiments described below.

FIGURE 31 depicts another method 2400 by a wireless device 110, according to certain embodiments. At step 2402, the wireless device 110 detects a trigger event associated with an activation or deactivation of PEI for the at least one PO. At step 2404, the wireless device activates or deactivates the PEI for the at least one PO based on the trigger event.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group G and Group J Example Embodiments described below.

FIGURE 32 illustrates a schematic block diagram of a virtual apparatus 2500 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 2500 is operable to carry out the example method described with reference to FIGURE 31 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 31 is not necessarily carried out solely by apparatus 2500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause detecting module 2510, activating/deactivating module 2520, and any other suitable units of apparatus 2500 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, detecting module 2510 may perform certain of the detecting functions of the apparatus 2500. For example, detecting module 2510 may detect a trigger event associated with an activation or deactivation of PEI for the at least one PO.

According to certain embodiments, activating/deactivating module 2520 may perform certain of the activating/deactivating functions of the apparatus 2500. For example, activating/deactivating module 2520 may activate or deactivate the PEI for the at least one PO based on the trigger event.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group G and Group J Example Embodiments described below.

FIGURE 33 depicts a method 2600 by a network node 160, according to certain embodiments. At step 2602, the network node 160 configures a wireless device 110 to detect a trigger event associated with an activation or deactivation of PEI for the at least one PO. At step 2604, the network node configures the wireless device to activate or deactivate the PEI for the at least one PO based on the trigger event.

In various particular embodiments, the method may include one or more of any of the steps or features of the Group H and Group J Example Embodiments described below.

FIGURE 34 illustrates a schematic block diagram of a virtual apparatus 2700 in a wireless network (for example, the wireless network shown in FIGURE 5). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 110 or network node 160 shown in FIGURE 5). Apparatus 2700 is operable to carry out the example method described with reference to FIGURE 33 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 33 is not necessarily carried out solely by apparatus 2700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 2700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause first configuring module 2710, second configuring module 2720, and any other suitable units of apparatus 2700 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, first configuring module 2710 may perform certain of the configuring functions of the apparatus 2700. For example, first configuring module 2710 may configure a wireless device 110 to detect a trigger event associated with an activation or deactivation of PEI for the at least one PO.

According to certain embodiments, second configuring module 2720 may perform certain other of the configuring functions of the apparatus 2700. For example, second configuring module 2720 may configure the wireless device 110 to activate or deactivate the PEI for the at least one PO based on the trigger event.

Optionally, in particular embodiments, virtual apparatus may additionally include one or more modules for performing any of the steps or providing any of the features in the Group H and Group J Example Embodiments described below.

EXAMPLE EMBODIMENTS

Group A Example Embodiments

Example Embodiment Al. A method by a wireless device comprising: receiving, from a network node, a PEI) configuration. The PEI configuration being associated with a group of wireless devices that comprises the wireless device. Based on the PEI configuration, wireless device receives a PEI.

Example Embodiment A2. The method of Example Embodiment Al, wherein the group of wireless devices comprises a minimum number of wireless devices in a cell.

Example Embodiment A3. The method of any one of Example Embodiments Al to A2, wherein the group of wireless devices comprises a number of wireless devices with an ability to receive PEI in a cell.

Example Embodiment A4. The method of any one of Example Embodiments Al to A3, wherein the group of wireless devices comprises a number of high priority wireless devices in a cell.

Example Embodiment A5. The method of any one of Example Embodiments Al to A4, wherein the group of wireless devices comprises a number of prioritized wireless devices in a cell.

Example Embodiment A6. The method of Example Embodiment A5, wherein the prioritized wireless devices are utilizing PEI.

Example Embodiment A7. The method of any one of Example Embodiments Al to A6, wherein the wireless device is included in the group of wireless devices based on a type of the wireless device.

Example Embodiment A8. The method of any one of Example Embodiments Al to A7, wherein the wireless device is included in the group of wireless devices based on a benefit metric characterizing a utility of PEI for the wireless device. Example Embodiment A9. The method of any one of Example Embodiments A7 to A8, further comprising transmitting, to the network node, information indicating at least one of: the type of wireless device and information associated with the benefit metric.

Example Embodiment A10. The method of any one of Example Embodiments Al to A9, further comprising transmitting, to the network node, information wherein the information indicates at least one of: the wireless device is a prioritized UE; the wireless device is a reduced UE capability; the wireless device is a XR UE; a UE identifier associated with the wireless device; a presence of the wireless device at a paging instance; a capability of the wireless device to perform PEI detection; an indication that the wireless device would benefit from receiving PEI; an indication that the wireless device uses PEI; a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the wireless device; a value associated with a data transmission duty cycle of the wireless device; a paging rate of the wireless device; an idle mode energy weight of the wireless device; a type of service or application used by the wireless device; a signal transmission periodicity of the wireless device; an amount of time the wireless device is in a cell; and an activity level of the wireless device.

Example Embodiment Al l. The method of any one of Example Embodiments Al to A10, further comprising: based on the PEI configuration, determining a subset of paging occasions in which the wireless device will receive the PEI; and monitoring for the PEI in the subset of paging occasions.

Example Embodiment A12. The method of Example Embodiment Al l, wherein the subset of paging occasions comprises every A-th paging occasion of a plurality of paging occasions.

Example Embodiment A13. The method of Example Embodiment Al l, wherein the subset of paging occasions comprises a group of paging occasions, the group of paging occasions comprising a number, N, of contiguous paging occasions.

Example Embodiment A14. The method of Example Embodiment Al 1, wherein the subset of paging occasions comprises every A-th paging occasion of in a group of AT paging occasions.

Example Embodiment A15. The method of any one of Example Embodiments Al to A14, wherein the PEI configuration is associated with a bandwidth part.

Example Embodiment A16. The method of any one of Example Embodiments Al to A15, wherein the PEI configuration is received as system information.

Example Embodiment A17. The method of any one of Example Embodiments Al to A16, wherein the PEI configuration is received as a radio resource control message.

Example Embodiment A18. The method of any one of Example Embodiments Al to A17, wherein the PEI configuration is received as downlink control information. Example Embodiment A19. The method of any one of Example Embodiments Al to A18, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be monitored.

Example Embodiment A20. The method of any one of Example Embodiments Al to Al 9, wherein the PEI configuration comprises a list of UE identifiers to receive PEI.

Example Embodiment A21. The method of any one of Example Embodiments Al to A20, wherein the PEI indicates and/or is associated with a subsequent paging occasion, and the method further comprises receiving a first paging message in the subsequent paging occasion.

Example Embodiment A22. The method of any one of Example Embodiments Al to A21, further comprising receiving, from the network node, at least one message indicating a deactivation of the PEI configuration.

Example Embodiment A23. The method of Example Embodiment A22, wherein the deactivation of the PEI configuration is based on a characteristic of the wireless device.

Example Embodiment A24. The method of Example Embodiment A23, further comprising transmitting, to the network node, a message comprising the characteristic of the wireless device.

Example Embodiment A25. The method of any one of Example Embodiments Al to A24, wherein the network node comprises a gNodeB.

Example Embodiment A26. The method of any one of Example Embodiments Al to A25, wherein the wireless device comprises a user equipment (UE).

Example Embodiment A27. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Al to A26.

Example Embodiment A28. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Al to A26.

Example Embodiment A29. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Al to A26.

Example Embodiment A30. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Al to A26.

Group B Embodiments

Example Embodiment Bl. A method by a network node comprising: determining a group of wireless devices for receiving an PEI; signaling a PEI configuration to the group of wireless devices; and transmitting the PEI to the group of wireless devices. Example Embodiment B2. The method of Example Embodiment Bl, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of wireless devices in a cell.

Example Embodiment B3. The method of any one of Example Embodiments Bl to B2, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of wireless devices with an ability to receive PEI in a cell.

Example Embodiment B4. The method of any one of Example Embodiments Bl to B3, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of high priority wireless devices in a cell.

Example Embodiment B5. The method of any one of Example Embodiments Bl to B4, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of prioritized wireless devices in a cell.

Example Embodiment B6. The method of Example Embodiment B5, wherein determining the group of wireless devices for receiving the PEI further comprises determining if the prioritized wireless devices are utilizing PEI.

Example Embodiment B7. The method of any one of Example Embodiments Bl to B6, wherein determining the group of wireless devices for receiving the PEI comprises determining at least one wireless device for which it is beneficial to provide PEI.

Example Embodiment B8. The method of any one of Example Embodiments Bl to B7, wherein determining the group of wireless devices for receiving the PEI comprises: determining a type of each wireless device in the group of wireless devices, and wherein each wireless devices is determined to be included in the group of wireless devices based on the type of the respective wireless device.

Example Embodiment B9. The method of Example Embodiment B8, further comprising assigning a benefit metric to each type of wireless device, the benefit metric characterizing the utility of PEI for each type of wireless device.

Example Embodiment BIO. The method of any one of Example Embodiments B8 to B9, wherein the type of wireless device may include and/or be based on at least one of: a reduced capability user equipment (UE); a XR UE; a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle being greater than a threshold; a length of a discontinuous reception cycle being less than a threshold; a value associated with a data transmission duty cycle being less than a threshold; a paging rate being less than a threshold; an idle mode energy weight being greater than a threshold; a type of service or application used by the wireless device; a signal transmission periodicity; an amount of time the wireless device is in a cell; and an activity level of the wireless device.

Example Embodiment Bl 1. The method of any one of Example Embodiments B8 to BIO, further comprising receiving information from the wireless device, the information indicating the type of wireless device.

Example Embodiment B 12. The method of any one of Example Embodiments Bl to Bl 1, further comprising: assigning a benefit metric to each wireless device, the benefit metric characterizing the utility or benefit for each wireless device to receive PEI, and wherein each wireless device is included in the group of wireless devices when the benefit metric is greater than a first threshold.

Example Embodiment B 13. The method of any one of Example Embodiments Bl to Bl 2, further comprising: assigning a cost metric to the each wireless device, the cost metric characterizing the cost of providing the PEI to each wireless device, and wherein each wireless device is included in the group of wireless devices when the cost metric is greater than a second threshold.

Example Embodiment B 14. The method of any one of Example Embodiments Bl to B12, further comprising: assigning a cost metric to each wireless device, the cost metric characterizing the cost of providing the PEI to each wireless device, and wherein each wireless device is included in the group of wireless devices when the cost metric is less than a second threshold.

Example Embodiment B 15. The method of any one of Example Embodiments Bl to B 11 , further comprising: assigning a benefit metric to the group of wireless devices, the benefit metric characterizing the utility or benefit of receiving PEI by the group of wireless devices, and prior to signaling the PEI configuration to the group of wireless devices and/or transmitting the PEI to the group of wireless devices, determining that the benefit metric is greater than a first threshold.

Example Embodiment Bl 6. The method of any one of Example Embodiments Bl to Bl 1 and Bl 5, further comprising: assigning a cost metric to the group of wireless devices, the cost metric characterizing the cost of providing the PEI to the group of wireless devices, and prior to signaling the PEI configuration to the group of wireless devices and/or transmitting the PEI to the group of wireless devices, determining that the cost metric is greater than a second threshold.

Example Embodiment Bl 7. The method of any one of Example Embodiments Bl to Bl 1 and Bl 5, further comprising: assigning a cost metric to the group of wireless devices, the cost metric characterizing the cost of providing the PEI to the group of wireless devices, and prior to signaling the PEI configuration to the group of wireless devices and/or transmitting the PEI to the group of wireless devices, determining that the cost metric is less than a second threshold. Example Embodiment Bl 8. The method of any one of Example Embodiments Bl 1 to Bl 7, wherein at least one of the benefit metric and the cost metric is determined based on at least one of: a number of types of wireless devices in the group of wireless devices; PEI transmission resources; an energy penalty due to waking up for PEI transmission; a paging rate for a UE type associated with the group of wireless devices or anyone of the wireless devices in the group of wireless devices; a number of wireless devices in the system and/or cell.

Example Embodiment Bl 9. The method of any one of Example Embodiments Bl to Bl 8, further comprising receiving information associated with at least one wireless device, and wherein the at least one wireless device is included in the group of wireless devices based on the information.

Example Embodiment B20. The method of Example Embodiment Bl 9, wherein the information indicates at least one of: the at least one wireless device is a prioritized UE; the at least one wireless device is a reduced UE capability; the at least one wireless device is a XR UE; a UE identifier associated with the at least one wireless device; a presence of the at least one wireless device at a paging instance; a capability of the at least one wireless device to perform PEI detection; an indication that the at least one wireless device would benefit from receiving PEI; an indication that the at least one wireless device uses PEI; a location of the at least one wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the at least one wireless device being greater than a threshold; a length of a discontinuous reception cycle of the at least one wireless device being le ss than a threshold; a value associated with a data transmission duty cycle of a wireless device being less than a threshold; a paging rate of the at least one wireless device being less than a threshold; an idle mode energy weight of the at least one wireless device being greater than a threshold; a type of service or application used by the at least one wireless device; a signal transmission periodicity of the at least one wireless device; an amount of time the at least one wireless device is in a cell; and an activity level of the at least one wireless device.

Example Embodiment B21. The method of any one of Example Embodiments B 19 to B20, wherein the information is received from the at least one wireless device.

Example Embodiment B22. The method of any one of Example Embodiments B 19 to B20, wherein the information is received from a core network node.

Example Embodiment B23. The method of any one of Example Embodiments Bl to Bl 8, wherein the PEI is transmitted based on information, the information comprising at least one of: at least one wireless device in the group of wireless devices is in a cell or a coverage area; a number of wireless devices within the group of wireless devices that are in the cell or the coverage area is greater than a first threshold; at least one wireless device in the group of wireless devices has a cell quality value that is less than a second threshold; and a number of wireless devices within the group of wireless that has a cell quality value that is less than a third threshold is greater than a fourth threshold.

Example Embodiment B24. The method of Example Embodiment B23, further comprising: receiving the information; and determining that the at least one wireless device is in the cell or the coverage area based on the information.

Example Embodiment B25. The method of Example Embodiment B24, wherein the information is received from the at least one wireless device.

Example Embodiment B26. The method of Example Embodiment B24, wherein the information is received from a core network node.

Example Embodiment B27. The method of any one of Example Embodiments Bl to B26, further comprising determining at least one paging occasion for which to transmit the PEI.

Example Embodiment B28. The method of Example Embodiment B27, wherein determining the at least one paging occasion for which to transmit the PEI comprises: determining that the at least one paging occasion includes at least one wireless device within the group of wireless devices.

Example Embodiment B29. The method of Example Embodiment B27, wherein determining the at least one paging occasion for which to transmit the PEI comprises: determining that a subset of paging occasions for which to transmit the PEI.

Example Embodiment B30. The method of Example Embodiment B29, wherein the subset of paging occasions comprises every 7V-th paging occasion of a plurality of paging occasions.

Example Embodiment B31. The method of Example Embodiment B29, wherein the subset of paging occasions comprises a group of paging occasions, the group of paging occasions comprising a number of contiguous paging occasions.

Example Embodiment B32. The method of Example Embodiment B29, wherein the subset of paging occasions comprises every 7V-th paging occasion of in a group of AT paging occasions.

Example Embodiment B33. The method of any one of Example Embodiments Bl to B32, wherein the PEI configuration is associated with a bandwidth part.

Example Embodiment B34. The method of any one of Example Embodiments Bl to B33, wherein the PEI configuration is signaled as system information.

Example Embodiment B35. The method of any one of Example Embodiments Bl to B34, wherein the PEI configuration is signaled as a radio resource control message.

Example Embodiment B36. The method of any one of Example Embodiments Bl to B35, wherein the PEI configuration is signaled as downlink control information. Example Embodiment B37. The method of any one of Example Embodiments Bl to B36, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be transmitted.

Example Embodiment B38. The method of any one of Example Embodiments Bl to B37, wherein the PEI configuration comprises a list of UE identifiers to receive PEI.

Example Embodiment B39. The method of any one of Example Embodiments Bl to B38, wherein the PEI indicates and/or is associated with a subsequent paging occasion, and the method further comprises transmitting a first paging message in the subsequent paging occasion.

Example Embodiment B40. The method of any one of Example Embodiments Bl to B39, further comprising transmitting, to at least one wireless device that is not within the group of wireless devices, a page in a paging occasion without transmitting a PEI prior to transmitting the page.

Example Embodiment B41. The method of any one of Example Embodiments Bl to B40, further comprising transmitting, to at least one wireless device in the group of wireless devices, at least one message indicating a deactivation of the PEI configuration.

Example Embodiment B42. The method of Example Embodiment B41, wherein the deactivation of the PEI configuration is based on a characteristic of the at least one wireless device.

Example Embodiment B43. The method of any one of Example Embodiments B 1 to B40, further comprising transmitting, to the group of wireless devices, at least one message indicating a deactivation of the PEI configuration.

Example Embodiment B44. The method of Example Embodiment B43, wherein the deactivation of the PEI configuration is based on a characteristic of at least one wireless device in the group of wireless devices.

Example Embodiment B45. The method of any one of Example Embodiments Bl to B44, wherein the network node comprises a gNodeB.

Example Embodiment B46. The method of any one of Example Embodiments Bl to B45, wherein at least one wireless device in the group of wireless devices comprises a user equipment (UE).

Example Embodiment B47. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments Bl to B46.

Example Embodiment B48. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Bl to B46. Example Embodiment B49. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Bl to B46.

Example Embodiment B50. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Bl to B49.

Group C Example Embodiments

Example Embodiment Cl . A method by a wireless device comprising: receiving, from a network node, Downlink Control Information (DCI) comprising a first indicator associated with an activation or deactivation of (PEI) in at least one PO.

Example Embodiment C2. The method of Example Embodiment Cl, wherein the DCI comprises at least one of: PEI-DCI and paging DCI.

Example Embodiment C3. The method of any one of Example Embodiments Cl to C2, wherein the first indicator is associated with at least one bitfield in the DCI.

Example Embodiment C4. The method of Example Embodiment C3, further comprising determining, based on a presence of the bitfield, that PEI is active in the at least one PO.

Example Embodiment C5. The method of Example Embodiment C3, further comprising determining, based on an empty bitfield, that PEI is active in the at least one PO.

Example Embodiment C6. The method of Example Embodiment C3, further comprising receiving, from the network node, a higher layer signal configuring the at least one bitfield.

Example Embodiment C7. The method of Example Embodiment C6, wherein the high layer signal comprises system information.

Example Embodiment C8. The method of any one of Example Embodiments C6 to C7, further comprising determining, based on the higher layer signal, whether the at least one PO comprises only POs associated with the PEI or all POs.

Example Embodiment C9. The method of Example Embodiment C3, further comprising determining, based on a bit value in the bitfield, whether PEI is activated or deactivated in the at least one PO.

Example Embodiment CIO. The method of Example Embodiment C9, wherein a bit value of 1 indicates that PEI is deactivated or a bit value of 0 indicates that the PEI is active in the at least one PO. Example Embodiment Cl 1. The method of Example Embodiment C9, wherein a bit value of 0 indicates that PEI is deactivated or a bit value of 1 indicates that the PEI is active in the at least one PO.

Example Embodiment C12. The method of Example Embodiment C3, further comprising determining, based on an empty bit in the bit field, that the PEI is activated or deactivated in the at least one PO.

Example Embodiment C13. The method of Example Embodiment C3, wherein the bitfield comprises a plurality of bits and the method further comprises: determining, based on a combination of bit values in the plurality of bits, whether PEI is activated or deactivated in the at least one PO.

Example Embodiment C14. The method of Example Embodiment C3, wherein the bitfield comprises a plurality of bits and wherein: at least one bit in the plurality of bits indicates whether PEI is activated or deactivated in the at least one PO, and at least one bit indicates that the at least one PO includes only POs associated with the PEI.

Example Embodiment Cl 5. The method of Example Embodiment C3, wherein the bitfield comprises a plurality of bits and wherein: at least one bit in the plurality of bits indicates whether PEI is activated or deactivated in the at least one PO, and at least one bit indicates that the at least one PO includes all POs.

Example Embodiment Cl 6. The method of any one of Example Embodiments Cl to Cl 5 wherein the at least one PO comprises at least a next PO.

Example Embodiment Cl 7. The method of any one of Example Embodiments Cl to Cl 6, wherein the first indicator is valid for a duration of time, and the method further comprises starting a validity timer when the first indicator is received.

Example Embodiment Cl 8. The method of Example Embodiment C17, further comprising determining, based on the validity timer and whether the duration of time has expired, whether PEI is activated or deactivated in at least one additional PO.

Example Embodiment Cl 9. The method of any one of Example Embodiments Cl to Cl 8, further comprising receiving, from the network node, PEI configuration information, wherein the PEI configuration information comprises at least one PEI resource, and wherein the first indicator indicates an activation or deactivation of the at least one PEI resource.

Example Embodiment C20. The method of any one of Example Embodiments Cl to Cl 9, further comprising falling back to default PO monitoring when the first indicator indicates a deactivation of PEI. Example Embodiment C21. The method of Example embodiment C20, wherein default PO monitoring comprises monitoring all POs.

Example Embodiment C22. The method of Example embodiment C20, wherein default PO monitoring comprises not monitoring POs until a second indicator indicates that PEI is activated.

Example Embodiment C23. The method of any one of Example Embodiments Cl to C22, further comprising determining, based on the first indicator associated with the activation or deactivation of PEI, to read system information to determine whether PEI is activated or deactivated.

Example Embodiment C24. The method of any one of Example Embodiments Cl to C23, wherein the first indicator is applicable to all wireless devices receiving the DCI within a paging occasion.

Example Embodiment C25. The method of any one of Example Embodiments Cl to C23, wherein the first indicator is applicable to a first group of wireless devices that includes the wireless device.

Example Embodiment C26. The method of Example Embodiment C25, wherein the DCI comprises a third indicator associated with an activation or deactivation of PEI in at least one PO for a second group of wireless devices that does not include the wireless device.

Example Embodiment C27. The method of any one of Example Embodiments Cl to C26, wherein the PEI is DCI-based PEI.

Example Embodiment C28. The method of any one of Example Embodiments Cl to C27, wherein the DCI comprises paging DCI and the at least one PO is transmitted on a physical downlink shared channel.

Example Embodiment C29. The method of any one of Example Embodiments C28, wherein the DCI comprises a short message based paging DCI.

Example Embodiment C30. The method of any one of Example Embodiments C28, further comprising: when the first indicator comprises a first one of the plurality of RNTIs, determining that the PEI is activated for the at least one PO, and when the first indicator comprises a second one of the plurality of RNTIs, determining that the PEI is deactivated for the at least one PO.

Example Embodiment C31. The method of any one of Example Embodiments C28 to C30, wherein the PEI is sequence-based.

Example Embodiment C32. The method of any one of Example Embodiments Cl to C31, wherein the wireless device comprises a UE. Example Embodiment C33. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C32.

Example Embodiment C34. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C32.

Example Embodiment C35. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C32.

Example Embodiment C36. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C32.

Group D Embodiments

Example Embodiment DI. A method by a network node comprising: transmitting, to at least one wireless device, DCI comprising a first indicator associated with an activation or deactivation of PEI in at least one PO.

Example Embodiment D2. The method of Example Embodiment DI, wherein the DCI comprises at least one of PEI-DCI and paging DCI.

Example Embodiment D3. The method of any one of Example Embodiments DI to D2, wherein the first indicator is associated with at least one bitfield in the DCI.

Example Embodiment D4. The method of Example Embodiment D3, wherein a presence of the bitfield indicates that PEI is active in the at least one PO.

Example Embodiment D5. The method of Example Embodiment D3, wherein an empty bitfield indicates that PEI is active in the at least one PO.

Example Embodiment D6. The method of any one of Example Embodiments D3, further comprising transmitting, to the at least one wireless device, a higher layer signal configuring the at least one bitfield.

Example Embodiment D7. The method of Example Embodiment D6, wherein the high layer signal comprises system information.

Example D8. The method of any one of Example Embodiments D6 to D7, wherein the higher layer signal indicates whether the at least one PO comprises only POs associated with the PEI or all POs.

Example D9. The method of Example Embodiment D3, wherein a bit value in the bitfield indicates whether PEI is activated or deactivated in the at least one PO. Example DIO. The method of Example Embodiment D9, wherein a bit value of 1 indicates that PEI is deactivated or a bit value of 0 indicates that the PEI is active in the at least one PO.

Example Dl l. The method of Example Embodiment D9, wherein a bit value of 0 indicates that PEI is deactivated or a bit value of 1 indicates that the PEI is active in the at least one PO.

Example D12. The method of Example Embodiment D3, wherein an empty bit in the bit field indicates that the PEI is activated or deactivated in the at least one PO.

Example Embodiment D13. The method of Example Embodiment D3, wherein the bitfield comprises a plurality of bits and wherein a combination of bit values in the plurality of bits indicates whether PEI is activated or deactivated in the at least one PO.

Example Embodiment DI 4. The method of Example Embodiment D3, wherein the bitfield comprises a plurality of bits and wherein: at least one bit in the plurality of bits indicates whether PEI is activated or deactivated in the at least one PO, and at least one bit indicates that the at least one PO includes only POs associated with the PEI.

Example Embodiment DI 5. The method of Example Embodiment D3, wherein the bitfield comprises a plurality of bits and wherein: at least one bit in the plurality of bits indicates whether PEI is activated or deactivated in the at least one PO, and at least one bit indicates that the at least one PO includes all POs.

Example Embodiment DI 6. The method of any one of Example Embodiments DI to DI 5 wherein the at least one PO comprises at least a next PO.

Example Embodiment DI 7. The method of any one of Example Embodiments DI to DI 6, wherein the first indicator is valid for a duration of time, and the method further comprises starting a validity timer when the first indicator is transmitted.

Example Embodiment DI 8. The method of Example Embodiment DI 7, further comprising determining, based on the validity timer and whether the duration of time has expired, whether PEI is activated or deactivated in at least one additional PO.

Example Embodiment DI 9. The method of any one of Example Embodiments DI to DI 8, further comprising transmitting PEI configuration information to the wireless device, the PEI configuration information comprising at least one PEI resource, and wherein the first indicator indicates an activation or deactivation of the at least one PEI resource.

Example Embodiment D20. The method of any one of Example Embodiments DI to DI 9, further comprising configuring the wireless device to fallback to default PO monitoring when the first indicator indicates a deactivation of PEI.

Example Embodiment D21. The method of Example Embodiment D20, wherein default PO monitoring comprises monitoring all POs. Example Embodiment D22. The method of Example Embodiment D20, wherein default PO monitoring comprises not monitoring POs until a second indicator indicates that PEI is activated.

Example Embodiment D23. The method of any one of Example Embodiments DI to D22, wherein the first indicator associated with the activation or deactivation of PEI indicates that the wireless device is to read system information to determine whether PEI is activated or deactivated.

Example Embodiment D24. The method of any one of Example Embodiments DI to D23, wherein the first indicator is applicable to all wireless devices receiving the DCI within a paging occasion.

Example Embodiment D25. The method of any one of Example Embodiments DI to D23, wherein the first indicator is applicable to a first group of wireless devices.

Example Embodiment D26. The method of Example Embodiment D25, wherein the DCI comprises a third indicator associated with an activation or deactivation of PEI in at least one PO for a second group of wireless devices.

Example Embodiment D27. The method of any one of Example Embodiments DI to D26, wherein the PEI is DCI-based PEI.

Example Embodiment D28. The method of any one of Example Embodiments DI to D27, wherein the DCI comprises paging DCI and the at least one PO is transmitted on a physical downlink shared channel.

Example Embodiment D29. The method of any one of Example Embodiments D28, wherein the DCI comprises a short message based paging DCI.

Example Embodiment D30. The method of any one of Example Embodiments D28, further comprising configuring the at least one wireless device with a plurality of RNTIs, and wherein: when the first indicator comprises a first one of the plurality of RNTIs, the PEI is activated for the at least one PO, and when the first indicator comprises a second one of the plurality of RNTIs, the PEI is deactivated for the at least one PO.

Example Embodiment D31. The method of any one of Example Embodiments D28 to D30, wherein the PEI is sequence-based.

Example Embodiment D32. The method of any one of Example Embodiments DI to D31, wherein the network node comprises a gNodeB.

Example Embodiment D33. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D32.

Example Embodiment D34. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D32. Example Embodiment D35. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D32.

Example Embodiment D36. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments DI to D32.

Group E Example Embodiments

Example Embodiment El. A method by a wireless device comprising: receiving, from a network node, a first sequence with a first characteristic indicating that the wireless device is to monitor at least one PO; and receiving, from the network node, a second sequence with a second characteristic indicating a deactivation of PEI for the at least one PO.

Example Embodiment E2. The method of Example Embodiment El, wherein at least one of the first sequence and the second sequence comprises a RS.

Example Embodiment E3. The method of any one of Example Embodiments El to E2, wherein at least one of the first sequence and the second sequence comprises a SSB.

Example Embodiment E4. The method of any one of Example Embodiments El to E3, wherein at least one of the first sequence and the second sequence comprises a TRS.

Example Embodiment E5. The method of any one of Example Embodiments El to E4, further comprising receiving, from the network node, a third sequence with a third characteristic indicating a reactivation of the PEI for the at least one additional PO.

Example Embodiment E6. The method of Example Embodiment E5, wherein the third sequence is the same as the first sequence.

Example Embodiment E7. The method of any one of Example Embodiments El to E6, wherein the first characteristic comprises a first scrambling code and the second sequence comprises a second scrambling code.

Example Embodiment E8. The method of any one of Example Embodiments El to E6 wherein each of the first and second characteristics are associated with at least one of: a time location, a frequency location, or a code/sequence.

Example Embodiment E9. The method of any one of Example Embodiments El to E8 wherein each of the first and second characteristics are associated with at least one parameter of a RS configuration. Example Embodiment E10. The method of any one of Example Embodiments El to E9 wherein each of the first and second characteristics are associated with at least one parameter of a CSI-RS resource definition.

Example Embodiment El l. The method of any one of Example Embodiments El to E10, wherein the second sequence with the second characteristic indicating the deactivation of the PEI for the at least one PO is valid for a duration of time, and the method further comprises starting a validity timer when the second sequence with the second characteristic is transmitted.

Example Embodiment E12. The method of Example Embodiment El l, further comprising: determining, based on the validity timer, whether the duration of time has expired, and if the duration of time has expired, reactivating the PEI for at least one additional PO.

Example Embodiment El 3. The method of any one of Example Embodiments El to El 2, further comprising determining, based on the second sequence with the second characteristic, to read system information to determine whether PEI is activated or deactivated for the at least one PO.

Example Embodiment E14. The method of any one of Example Embodiments El to E13, further comprising receiving, from the network node, a higher layer signal configuring the at least one wireless device with at least one of: the first sequence, the second sequence, the first characteristic, and the second characteristic.

Example Embodiment El 5. The method of Example Embodiment E14, wherein the high layer signal comprises system information.

Example Embodiment E16. The method of any one of Example Embodiments El to E15, wherein the wireless device comprises a UE.

Example Embodiment E17. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments El to El 6.

Example Embodiment El 8. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments El to E16.

Example Embodiment E19. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments El to E16.

Example Embodiment E20. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments El to El 6.

Group F Embodiments Example Embodiment Fl. A method by a network node comprising: transmitting, to at least one wireless device, a first sequence with a first characteristic indicating that the at least one wireless device is to monitor at least one PO; and transmitting, to the at least one wireless device, a second sequence with a second characteristic indicating a deactivation of PEI for the at least one PO.

Example Embodiment F2. The method of Example Embodiment Fl, wherein at least one of the first sequence and the second sequence comprises a RS.

Example Embodiment F3. The method of any one of Example Embodiments Fl to F2, wherein at least one of the first sequence and the second sequence comprises a SSB.

Example Embodiment F4. The method of any one of Example Embodiments Fl to F3, wherein at least one of the first sequence and the second sequence comprises a TRS.

Example Embodiment F5. The method of any one of Example Embodiments Fl to F4, further comprising transmitting, to the at least one wireless device, a third sequence with a third characteristic indicating a reactivation of the PEI for the at least one additional PO.

Example Embodiment F6. The method of Example Embodiment F5, wherein the third sequence is the same as the first sequence.

Example Embodiment F7. The method of any one of Example Embodiments Fl to F6, wherein the first characteristic comprises a first scrambling code and the second sequence comprises a second scrambling code.

Example Embodiment F8. The method of any one of Example Embodiments Fl to F6 wherein each of the first and second characteristics are associated with at least one of a time location, a frequency location, or a code/sequence.

Example Embodiment F9. The method of any one of Example Embodiments Fl to F8 wherein each of the first and second characteristics are associated with at least one parameter of a RS configuration.

Example Embodiment Fl 0. The method of any one of Example Embodiments Fl to F9 wherein each of the first and second characteristics are associated with at least one parameter of a CSI-RS resource definition.

Example Embodiment Fl 1. The method of any one of Example Embodiments Fl to F10, wherein the second sequence with the second characteristic indicating the deactivation of the PEI for the at least one PO is valid for a duration of time, and the method further comprises starting a validity timer when the second sequence with the second characteristic is transmitted. Example Embodiment Fl 2. The method of Example Embodiment Fl 1, further comprising determining, based on the validity timer, whether the duration of time has expired, and if the duration of time has expired, reactivating the PEI for at least one additional PO.

Example Embodiment F 13. The method of any one of Example Embodiments Fl to F12, wherein the second sequence with the second characteristic indicating the deactivation of the PEI for the at least one PO indicates that the wireless device is to read system information to determine whether PEI is activated or deactivated.

Example Embodiment F 14. The method of any one of Example Embodiments Fl to F13, further comprising transmitting, to the at least one wireless device, a higher layer signal configuring the at least one wireless device with at least one of: the first sequence, the second sequence, the first characteristic, and the second characteristic.

Example Embodiment Fl 5. The method of Example Embodiment F14, wherein the high layer signal comprises system information.

Example Embodiment Fl 6. The method of any one of Example Embodiments Fl to Fl 5, wherein the network node comprises a gNodeB.

Example Embodiment Fl 7. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments Fl to Fl 6.

Example Embodiment Fl 8. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Fl to Fl 6.

Example Embodiment Fl 9. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Fl to F16.

Example Embodiment F20. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Fl to Fl 6.

Group G Example Embodiments

Example Embodiment Gl. A method by a wireless device comprising: detecting a trigger event associated with an activation or deactivation of PEI for the at least one O); and activating or deactivating the PEI for the at least one PO based on the trigger event.

Example Embodiment G2. The method of Example Embodiment Gl, wherein detecting the trigger event comprises determining that a PEI has not been detected for at least a first duration of time. Example Embodiment G3. The method of Example Embodiment Gl, wherein detecting the trigger event comprises determining that a minimum number of PEIs have not been detected during at least a first duration of time.

Example Embodiment G4a.The method of any one of Example Embodiments G2 or G3, further comprising receiving the first duration of time from a network node.

Example Embodiment G4b. The method of Example Embodiment G4a, wherein the first duration of time is received via a broadcast message.

Example Embodiment G4c. The method of Example Embodiment G4a, wherein the first duration of time is received via dedicated signaling.

Example Embodiment G5. The method of any one of Example Embodiments G2 or G3, further comprising determining the first duration of time based on measurement associated with a PEI reception rate.

Example Embodiment G6. The method of Example Embodiment Gl, wherein detecting the trigger event comprises determining that a PEI has not been detected for during a threshold number of POs.

Example Embodiment G7. The method of any one of Example Embodiments Gl to G6, wherein detecting the trigger event comprises determining that at least one signal quality measurement is below a minimum threshold value.

Example Embodiment G8. The method of Example Embodiment G7, wherein the at least one signal quality measurement comprises at least one of a RSRP, a RSRQ, and a SINR.

Example Embodiment G9. The method of any one of Example Embodiments Gl to G8, further comprising starting a validity timer in response to detecting a trigger event, the validity timer measuring a second duration of time associated with the activation or deactivation of the PEI for the at least one PO.

Example Embodiment GIO. The method of Example Embodiment G9, further comprising: determining, based on the validity timer, that the second duration of time has expired, and taking at least one action in response to determining that the second duration of time has expired, wherein the at least one action comprises: if the PEI was deactivated in response to detecting the at least one trigger event, reactivating the PEI for at least one additional PO, or if the PEI was activated in response to detecting the at least one trigger event, deactivating the PEI for at least one additional PO.

Example Embodiment Gl 1. The method of any one of Example Embodiments G9 to GIO, wherein the second duration of time is received via a broadcast message. Example Embodiment G12. The method of any one of Example Embodiments G9 to GIO, wherein the second duration of time is received via dedicated signaling.

Example Embodiment G13. The method of any one of Example Embodiments G1 to G12, further comprising, in response to the deactivation of the PEI, monitoring all POs for a paging message.

Example Embodiment G14. The method of any one of Example Embodiments G1 to G12, further comprising, in response to the activation of the PEI, monitoring only POs for a paging message that are associated with a received PEI.

Example Embodiment G15. The method of any one of Example Embodiments G1 to G14, further comprising receiving information configuring the wireless device with the trigger event.

Example Embodiment G16. The method of Example Embodiment G15, wherein the information configuring the wireless device with the trigger event is received via a broadcast message.

Example Embodiment G17. The method of Example Embodiment G15, wherein the information configuring the wireless device with the trigger event is received via dedicated signaling.

Example Embodiment G18. The method of any one of Example Embodiments G1 to G17, further comprising: while PEI is deactivated for the at least one PO, receiving and decoding downlink control information (DCI), and wherein the DCI comprises at least one of PEI DCI and PO DCI.

Example Embodiment G19. The method of Example Embodiment El 8, wherein the DCI is received on a PO-PDCCH.

Example Embodiment G20. The method of any one of Example Embodiments El to El 9, wherein the wireless device comprises a UE.

Example Embodiment G21. A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments G1 to G20.

Example Embodiment G22. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments G1 to G20.

Example Embodiment G23. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments G1 to G20.

Example Embodiment G24. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments G1 to G20. Group H Embodiments

Example Embodiment Hl. A method by a network node comprising: configuring a wireless device to detect a trigger event associated with an activation or deactivation of PEI for the at least one PO; and configuring the wireless device to activate or deactivate the PEI for the at least one PO based on the trigger event.

Example Embodiment H2. The method of Example Embodiment Hl, wherein configuring the wireless device to detect the trigger event comprises configuring the wireless device to determine that a PEI has not been detected for at least a first duration of time.

Example Embodiment H3. The method of Example Embodiment Hl , wherein configuring the wireless device to detect the trigger event comprises configuring the wireless device to determine that a minimum number of PEIs have not been detected during at least a first duration of time.

Example Embodiment H4a.The method of any one of Example Embodiments H2 or H3, further comprising transmitting the first duration of time to the wireless device.

Example Embodiment H4b. The method of Example Embodiment H4a, wherein the first duration of time is transmitted via a broadcast message.

Example Embodiment H4c. The method of Example Embodiment H4a, wherein the first duration of time is transmitted via dedicated signaling.

Example Embodiment H5. The method of any one of Example Embodiments H2 or H3, further comprising configuring the wireless device to determine the first duration of time based on measurement associated with a PEI reception rate.

Example Embodiment H6. The method of Example Embodiment Hl, wherein configuring the wireless device to detect the trigger event comprises configuring the wireless device to determine that a PEI has not been detected for during a threshold number of POs.

Example Embodiment H7. The method of any one of Example Embodiments Hl to H6, wherein configuring the wireless device to detect the trigger event comprises configuring the wireless device to determine that at least one signal quality measurement is below a minimum threshold value.

Example Embodiment H8. The method of Example Embodiment H7, wherein the at least one signal quality measurement comprises at least one of a RSRP, a RSRQ, and a SINR.

Example Embodiment H9. The method of any one of Example Embodiments Hl to H8, further comprising configuring the wireless device to start a validity timer in response to detecting a trigger event, the validity timer measuring a second duration of time associated with the activation or deactivation of the PEI for the at least one PO.

Example Embodiment H10. The method of Example Embodiment H9, further comprising configuring the wireless device to: determine, based on the validity timer, that the second duration of time has expired, and take at least one action in response to determining that the second duration of time has expired, wherein the at least one action comprises: if the PEI was deactivated in response to detecting the at least one trigger event, reactivating the PEI for at least one additional PO, or if the PEI was activated in response to detecting the at least one trigger event, deactivating the PEI for at least one additional PO.

Example Embodiment Hl 1. The method of any one of Example Embodiments H9 to H10, further comprising transmitting an indication of the second duration of time to the at least one wireless device via a broadcast message.

Example Embodiment H12. The method of any one of Example Embodiments H9 to H10, further comprising transmitting an indication of the second duration of time via dedicated signaling.

Example Embodiment H13. The method of any one of Example Embodiments Hl to H12, further comprising configuring the wireless device to monitor all POs for a paging message in response to the deactivation of the PEI.

Example Embodiment H14. The method of any one of Example Embodiments Hl to H12, further comprising configuring the wireless device to monitor only POs for a paging message that are associated with a received PEI in response to activation of the PEI.

Example Embodiment H15. The method of any one of Example Embodiments Hl to H14, further comprising transmitting information configuring the wireless device with the trigger event.

Example Embodiment Hl 6. The method of Example Embodiment Hl 5, wherein the information configuring the wireless device with the trigger event is transmitted via a broadcast message.

Example Embodiment Hl 7. The method of Example Embodiment Hl 5, wherein the information configuring the wireless device with the trigger event is transmitted via dedicated signaling.

Example Embodiment Hl 8. The method of any one of Example Embodiments Hl to Hl 7, further comprising configuring the wireless device to: while PEI is deactivated for the at least one PO, receive and decode CI), and wherein the DCI comprises at least one of PEI DCI and PO DCI.

Example Embodiment Hl 9. The method of Example Embodiment Hl 8, wherein the DCI is received on a PO-PDCCH. Example Embodiment H20. The method of any one of Example Embodiments Hl to Hl 9, wherein the network node comprises a gNodeB.

Example Embodiment H21. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments Hl to H20.

Example Embodiment H22. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Hl to H20.

Example Embodiment H23. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Hl to H20.

Example Embodiment H24. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Hl to H20.

Group J Example Embodiments

Example Embodiment JI . A wireless device comprising: processing circuitry configured to perform any of the steps of any of the Group A, C, E, and G Example Embodiments; and power supply circuitry configured to supply power to the wireless device.

Example Embodiment J2. A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, D, F, and H Example Embodiments; power supply circuitry configured to supply power to the wireless device.

Example Embodiment J3. A wireless device, the wireless device comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A, C, E, and G Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the wireless device to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the wireless device that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the wireless device.

Example Embodiment J4. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a wireless device, wherein the cellular network comprises a network node having a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of the Group B, D, F, and H Example Embodiments.

Example Embodiment J5. The communication system of the previous embodiment further including the network node.

Example Embodiment J6. The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment J7. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device comprises processing circuitry configured to execute a client application associated with the host application.

Example Embodiment J8. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the network node performs any of the steps of any of the Group B, D, F, and H Example Embodiments.

Example Embodiment J9. The method of the previous embodiment, further comprising, at the network node, transmitting the user data.

Example Embodiment JI 0. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the wireless device, executing a client application associated with the host application.

Example Embodiment JI 1. A wireless device configured to communicate with a network node, the wireless device comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

Example Embodiment J12. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a wireless device, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s components configured to perform any of the steps of any of the Group A, C, E, and G Example Embodiments.

Example Embodiment JI 3. The communication system of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the wireless device. Example Embodiment J14. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application.

Example Embodiment JI 5. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the wireless device via a cellular network comprising the network node, wherein the wireless device performs any of the steps of any of the Group A, C, E, and G Example Embodiments.

Example Embodiment JI 6. The method of the previous embodiment, further comprising at the wireless device, receiving the user data from the network node.

Example Embodiment JI 7. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the wireless device comprises a radio interface and processing circuitry, the wireless device’s processing circuitry configured to perform any of the steps of any of the Group A, C, E, and G Example Embodiments.

Example Embodiment JI 8. The communication system of the previous embodiment, further including the wireless device.

Example Embodiment JI 9. The communication system of the previous 2 embodiments, further including the network node, wherein the network node comprises a radio interface configured to communicate with the wireless device and a communication interface configured to forward to the host computer the user data carried by a transmission from the wireless device to the network node.

Example Embodiment J20. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

Example Embodiment J21. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the wireless device’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data. Example Embodiment J22. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving user data transmitted to the network node from the wireless device, wherein the wireless device performs any of the steps of any of the Group A, C, E, and G Example Embodiments.

Example Embodiment J23. The method of the previous embodiment, further comprising, at the wireless device, providing the user data to the network node.

Example Embodiment J24. The method of the previous 2 embodiments, further comprising: at the wireless device, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

Example Embodiment J25. The method of the previous 3 embodiments, further comprising: at the wireless device, executing a client application; and at the wireless device, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.

Example Embodiment J26. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a wireless device to a network node, wherein the network node comprises a radio interface and processing circuitry, the network node’s processing circuitry configured to perform any of the steps of any of the Group B, D, F, and H Example Embodiments.

Example Embodiment J27. The communication system of the previous embodiment further including the network node.

Example Embodiment J28. The communication system of the previous 2 embodiments, further including the wireless device, wherein the wireless device is configured to communicate with the network node.

Example Embodiment J29. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the wireless device is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Example Embodiment J30. A method implemented in a communication system including a host computer, a network node and a wireless device, the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the network node has received from the wireless device, wherein the wireless device performs any of the steps of any of the Group A, C, E, and G Example Embodiments.

Example Embodiment J31. The method of the previous embodiment, further comprising at the network node receiving the user data from the wireless device.

Example Embodiment J32. The method of the previous 2 embodiments, further comprising at the network node, initiating a transmission of the received user data to the host computer.

Example Embodiment J33. The method of any of the previous embodiments, wherein the network node comprises a base station.

Example Embodiment J34. The method of any of the previous embodiments, wherein the wireless device comprises a user equipment (UE).

Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.

Claims

88 CLAIMS

1. A method (1000) by a wireless device (110) comprising: determining (1002) a first set of paging occasions (POs); receiving (1004), from a network node (160), a paging early indicator (PEI) configuration, the PEI configuration being associated with a group of wireless devices and the PEI configuration being associated with a second set of POs; determining (1006) whether the wireless device belongs to the group of wireless devices associated with the PEI configuration; wherein if the wireless device belongs to the group wireless devices associated with the PEI configuration, the method further comprises attempting (1008) to receive a PEI, and wherein if the PEI is received, the method further comprises monitoring at least one of the POs in the second set of POs; wherein if the wireless device does not belong to the group of wireless devices associated with the PEI configuration, the method further comprises monitoring (1010) at least one of the POs in first set of POs; and wherein if a paging message for the wireless device is received in the at least one monitored PO in the first set of POs or the second set of POs, the method further comprises transmitting (1012), to a network node, a message comprising information related to a usage of the PEI.

2. The method of Claim 1, further comprising determining the first set of POs based on a UE ID associated with the wireless device.

3. The method in Claim 1, wherein when, based on a UE ID, the wireless device belongs to the group wireless devices associated with the PEI, the method further comprises determining to monitor a subset of POs either from the first or the second set of POs, wherein the monitoring of the subset of the POs from the second set of POs is based on the reception of a PEI.

4. The method of any one of Claims 1 to 3, wherein the group of wireless devices comprises a minimum number of wireless devices in a cell.

5. The method of any one of Claims 1 to 4, wherein the group of wireless devices comprises a number of wireless devices with an ability to receive the PEI in a cell.

6. The method of any one of Claims 1 to 5, wherein the group of wireless devices comprises a number of high priority wireless devices in a cell.

7. The method of any one of Claims 1 to 6, wherein determining whether the wireless device belongs to the group of wireless devices is based on a type of the wireless device. 89

8. The method of any one of Claims 1 to 7, wherein determining whether the wireless device belongs to the group of wireless devices is based on a benefit metric characterizing a utility of the PEI for the wireless device.

9. The method of any one of Claims 1 to 8, further comprising transmitting information to the network node, wherein the information indicates at least one of: the wireless device is a prioritized UE; the wireless device is a reduced UE capability; the wireless device is a XR UE; a UE identifier associated with the wireless device; a presence of the wireless device at a paging instance; a capability of the wireless device to perform PEI detection; an indication that the wireless device would benefit from receiving PEI; an indication that the wireless device uses PEI; a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the wireless device; a value associated with a data transmission duty cycle of the wireless device; a paging rate of the wireless device; an idle mode energy weight of the wireless device; a type of service or application used by the wireless device; a signal transmission periodicity of the wireless device; an amount of time the wireless device is in a cell; and an activity level of the wireless device.

10. The method of any one of Claims 1 to 9, wherein the PEI configuration is associated with a bandwidth part.

11. The method of any one of Claims 1 to 10, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be monitored.

12. The method of any one of Claims 1 to 11, further comprising receiving, from the network node, at least one message indicating a deactivation of the PEI configuration.

13. The method of Claim 12, wherein the deactivation of the PEI configuration is based on a characteristic of the wireless device.

14. A method (1100) by a network node (160) comprising: 90 determining (1102) a group of wireless devices (110) for receiving a paging early indicator (PEI), wherein the determining comprises obtaining information indicating whether the group of wireless devices is using PEI; signaling (1104) a PEI configuration to the group of wireless devices; determining (1106) at least one paging occasion for which to transmit the PEI; and transmitting (1108) the PEI to the group of wireless devices.

15. The method of Claim 14, wherein obtaining the information comprises receiving the information from at least one wireless device, and wherein the at least one wireless device is included in the group of wireless devices based on the information.

16. The method of Claim 14, wherein obtaining the information comprises autonomously determining whether the group of wireless device is using the PEI.

17. The method of any one of Claims 14 to 16, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of wireless devices with an ability to receive PEI in a cell.

18. The method of any one of Claims 14 to 17, wherein determining the group of wireless devices for receiving the PEI comprises determining a number of high priority wireless devices in a cell, the high priority wireless devices utilizing the PEI.

19. The method of any one of Claims 14 to 18, wherein determining the group of wireless devices for receiving the PEI comprises: determining a type of each wireless device in the group of wireless devices, and wherein each wireless devices is determined to be included in the group of wireless devices based on the type of the respective wireless device.

20. The method of Claim 19, wherein the type of wireless device may include and/or be based on at least one of: a reduced capability user equipment (UE); a XR UE; and a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle being greater than a threshold; a length of a discontinuous reception cycle being less than a threshold a value associated with a data transmission duty cycle being less than a threshold; a paging rate being less than a threshold; an idle mode energy weight being greater than a threshold; 91 a type of service or application used by the wireless device; a signal transmission periodicity; an amount of time the wireless device is in a cell; and an activity level of the wireless device.

21. The method of any one of Claims 14 to 20, further comprising: assigning a benefit metric to one or more of the wireless devices, the benefit metric characterizing the utility or benefit for the wireless device to receive PEI, and wherein each wireless device is included in the group of wireless devices when the benefit metric is greater than a first threshold.

22. The method of any one of Claims 14 to 20, further comprising: assigning a cost metric to the one or more of the wireless devices, the cost metric characterizing the cost of providing the PEI to each wireless device, and wherein each wireless device is included in the group of wireless devices based on the cost metric.

23. The method of any one of Claims 21 to 22, wherein at least one of the benefit metric and the cost metric is determined based on at least one of: a number of types of wireless devices in the group of wireless devices;

PEI transmission resources; an energy penalty due to waking up for PEI transmission; a paging rate for a UE type associated with the group of wireless devices or anyone of the wireless devices in the group of wireless devices; and a number of wireless devices in the system and/or cell.

24. The method of any one of Claims 14 to 23, wherein the information indicates at least one of: the at least one wireless device is a prioritized UE; the at least one wireless device is a reduced UE capability; the at least one wireless device is a XR UE; a UE identifier associated with the at least one wireless device; a presence of the at least one wireless device at a paging instance; a capability of the at least one wireless device to perform PEI detection; an indication that the at least one wireless device would benefit from receiving PEI; an indication that the at least one wireless device uses PEI; 92 a location of the at least one wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the at least one wireless device being greater than a threshold; a length of a discontinuous reception cycle of the at least one wireless device being less than a threshold ; a value associated with a data transmission duty cycle of a wireless device being less than a threshold; a paging rate of the at least one wireless device being less than a threshold; an idle mode energy weight of the at least one wireless device being greater than a threshold; a type of service or application used by the at least one wireless device; a signal transmission periodicity of the at least one wireless device; an amount of time the at least one wireless device is in a cell; and an activity level of the at least one wireless device.

25. The method of any one of Claims 14 to 24, wherein the PEI is transmitted based on information, the information comprising at least one of: at least one wireless device in the group of wireless devices is in a cell or a coverage area, a number of wireless devices within the group of wireless devices that are in the cell or the coverage area is greater than a first threshold; at least one wireless device in the group of wireless devices has a cell quality value that is less than a second threshold; and a number of wireless devices within the group of wireless that has a cell quality value that is less than a third threshold is greater than a fourth threshold.

26. The method of Claim 25, further comprising: receiving the information from the at least one wireless device; and determining that the at least one wireless device is in the cell or the coverage area based on the information.

27. The method of any one of Claims 14 to 26, wherein determining the at least one paging occasion for which to transmit the PEI comprises: determining that a subset of paging occasions for which to transmit the PEI.

28. The method of any one of Claims 14 to 27, wherein the PEI configuration is associated with a bandwidth part. 93

29. The method of any one of Claims 14 to 28, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be transmitted.

30. The method of any one of Claims 14 to 29, further comprising transmitting, to at least one wireless device that is not within the group of wireless devices, a page in a paging occasion without transmitting a PEI prior to transmitting the page.

31. The method of any one of Claims 14 to 30, further comprising transmitting, to at least one wireless device in the group of wireless devices, at least one message indicating a deactivation of the PEI configuration.

32. The method of Claim 31, wherein the deactivation of the PEI configuration is based on a characteristic of the at least one wireless device.

33. A wireless device (110) comprising: processing circuitry (120) configured to: determine a first set of paging occasions (POs); receive, from a network node (160), a paging early indicator (PEI) configuration, the PEI configuration being associated with a group of wireless devices and the PEI configuration being an associated with a second set of POs; determine whether the wireless device belongs to the group of wireless devices associated with the PEI configuration; wherein if the wireless device belongs to the group wireless devices associated with the PEI configuration, the processing circuitry is configured to attempt to receive a PEI, and wherein if the PEI is received, the processing circuitry is configured to monitor at least one of the POs in the second set of POs; wherein if the wireless device does not belong to the group of wireless devices associated with the PEI configuration, the processing circuitry is configured to monitor at least one of the POs in first set of POs; and wherein if a paging message for the wireless device is received in the at least one monitored PO in the first set of POs or the second set of POs, the processing circuitry is configured to transmit, to a network, a message comprising information related to a usage of the PEI.

34. The wireless device of Claim 33, wherein the processing circuitry is configured to determine the first set of POs based on a UE ID associated with the wireless device.

35. The wireless device of Claim 33, wherein when, based on a UE ID, the wireless device belongs to the group wireless devices associated with the PEI, the processing circuitry is 94 configured to determine to monitor a subset of POs either from the first or the second set of POs, wherein the monitoring of the subset of the POs from the second set of POs is based on the reception of a PEI.

36. The wireless device of any one of Claims 33 to 35, wherein the group of wireless devices comprises a minimum number of wireless devices in a cell.

37. The wireless device of any one of Claims 33 to 36, wherein the group of wireless devices comprises a number of wireless devices with an ability to receive the PEI in a cell.

38. The wireless device of any one of Claims 33 to 37, wherein the group of wireless devices comprises a number of high priority wireless devices in a cell.

39. The wireless device of any one of Claims 33 to 38, wherein determining whether the wireless device belongs to the group of wireless devices is based on a type of the wireless device.

40. The wireless device of any one of Claims 33 to 39, wherein determining whether the wireless device belongs to the group of wireless devices is based on a benefit metric characterizing a utility of the PEI for the wireless device.

41. The wireless device of any one of Claims 33 to 40, wherein the processing circuitry is configured to transmit information to the network node, wherein the information indicates at least one of the wireless device is a prioritized UE; the wireless device is a reduced UE capability; the wireless device is a XR UE; a UE identifier associated with the wireless device; a presence of the wireless device at a paging instance; a capability of the wireless device to perform PEI detection; an indication that the wireless device would benefit from receiving PEI; an indication that the wireless device uses PEI; a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the wireless device; a value associated with a data transmission duty cycle of the wireless device; a paging rate of the wireless device; an idle mode energy weight of the wireless device; a type of service or application used by the wireless device; a signal transmission periodicity of the wireless device; 95 an amount of time the wireless device is in a cell; and an activity level of the wireless device.

42. The wireless device of any one of Claims 33 to 41, wherein the PEI configuration is associated with a bandwidth part.

43. The wireless device of any one of Claims 33 to 42, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be monitored.

44. The wireless device of any one of Claims 33 to 43, wherein the processing circuitry is configured to receive, from the network node, at least one message indicating a deactivation of the PEI configuration.

45. The wireless device of Claim 44, wherein the deactivation of the PEI configuration is based on a characteristic of the wireless device.

46. A network node (160) comprising: processing circuitry (170) configured to: determine a group of wireless devices (110) for receiving an paging early indicator (PEI), wherein the determining comprises obtaining information indicating whether the group of wireless devices is using PEI; signal a PEI configuration to the group of wireless devices; determine at least one paging occasion for which to transmit the PEI; and transmit the PEI to the group of wireless devices.

47. The network node of Claim 46, wherein when obtaining the information the processing circuitry is configured to receives the information from at least one wireless device, and wherein the at least one wireless device is included in the group of wireless devices based on the information.

48. The network node of Claim 46, wherein when obtaining the information the processing circuitry is configured to autonomously determine whether the group of wireless device is using the PEI.

49. The network node of any one of Claims 46 to 48, wherein when determining the group of wireless devices for receiving the PEI the processing circuitry is configured to determine a number of wireless devices with an ability to receive PEI in a cell.

50. The network node of any one of Claims 46 to 49, wherein when determining the group of wireless devices for receiving the PEI the processing circuitry is configured to determine a number of high priority wireless devices in a cell, the high priority wireless devices utilizing the PEI.

51. The network node of any one of Claims 46 to 50 wherein when determining the group of wireless devices for receiving the PEI the processing circuitry is configured to: determine a type of each wireless device in the group of wireless devices, and wherein each wireless devices is determined to be included in the group of wireless devices based on the type of the respective wireless device.

52. The network node of Claim 51, wherein the type of wireless device may include and/or be based on at least one of: a reduced capability user equipment (UE); a XR UE; and a location of the wireless device with respect to a cell edge; a length of a discontinuous reception cycle being greater than a threshold; a length of a discontinuous reception cycle being less than a threshold a value associated with a data transmission duty cycle being less than a threshold; a paging rate being less than a threshold; an idle mode energy weight being greater than a threshold; a type of service or application used by the wireless device; a signal transmission periodicity; an amount of time the wireless device is in a cell; and an activity level of the wireless device.

53. network node of any one of Claims 46 to 52, wherein the processing circuitry is configured to: assign a benefit metric to one or more of the wireless devices, the benefit metric characterizing the utility or benefit for the wireless device to receive PEI, and wherein each wireless device is included in the group of wireless devices when the benefit metric is greater than a first threshold.

54. The network node of any one of Claims 46 to 53, wherein the processing circuitry is configured to: assign a cost metric to the one or more of the wireless devices, the cost metric characterizing the cost of providing the PEI to each wireless device, and wherein each wireless device is included in the group of wireless devices based on the cost metric.

55. The network node of any one of Claims 53 to 54, wherein at least one of the benefit metric and the cost metric is determined based on at least one of: a number of types of wireless devices in the group of wireless devices;

56. The network node of Claim 55, wherein the information indicates at least one of: the at least one wireless device is a prioritized UE; the at least one wireless device is a reduced UE capability; the at least one wireless device is a XR UE; a UE identifier associated with the at least one wireless device; a presence of the at least one wireless device at a paging instance; a capability of the at least one wireless device to perform PEI detection; an indication that the at least one wireless device would benefit from receiving PEI; an indication that the at least one wireless device uses PEI; a location of the at least one wireless device with respect to a cell edge; a length of a discontinuous reception cycle of the at least one wireless device being greater than a threshold; a length of a discontinuous reception cycle of the at least one wireless device being less than a threshold ; a value associated with a data transmission duty cycle of a wireless device being less than a threshold; a paging rate of the at least one wireless device being less than a threshold; an idle mode energy weight of the at least one wireless device being greater than a threshold; a type of service or application used by the at least one wireless device; a signal transmission periodicity of the at least one wireless device; an amount of time the at least one wireless device is in a cell; and an activity level of the at least one wireless device. 98

57. The network node of any one of Claims 46 to 56, wherein the PEI is transmitted based on information, the information comprising at least one of: at least one wireless device in the group of wireless devices is in a cell or a coverage area, a number of wireless devices within the group of wireless devices that are in the cell or the coverage area is greater than a first threshold; at least one wireless device in the group of wireless devices has a cell quality value that is less than a second threshold; and a number of wireless devices within the group of wireless that has a cell quality value that is less than a third threshold is greater than a fourth threshold.

58. The network node of Claim 57, wherein the processing circuitry is configured to: receive the information from the at least one wireless device; and determine that the at least one wireless device is in the cell or the coverage area based on the information.

59. The network node of any one of Claims 46 to 58, wherein when determining the at least one paging occasion for which to transmit the PEI the processing circuitry is configured to: determine that a subset of paging occasions for which to transmit the PEI.

60. The network node of any one of Claims 46 to 59, wherein the PEI configuration is associated with a bandwidth part.

61. The network node of any one of Claims 46 to 60, wherein the PEI configuration comprises a list of UE types to receive PEI and/or a list of paging occasions for which PEI is to be transmitted.

62. The network node of any one of Claims 46 to 61, wherein the processing circuitry is configured to transmit, to at least one wireless device that is not within the group of wireless devices, a page in a paging occasion without transmitting a PEI prior to transmitting the page.

63. The network node of any one of Claims 46 to 62, wherein the processing circuitry is configured to transmit, to at least one wireless device in the group of wireless devices, at least one message indicating a deactivation of the PEI configuration.

64. The network node of Claim 63, wherein the deactivation of the PEI configuration is based on a characteristic of the at least one wireless device.