Avoiding missed paging when using wakeup signal

Abstract

According to some embodiments, a method is performed by a user equipment (UE) for avoiding missed paging. The method comprises determining whether a network node will forward a first report received from the UE,. The first report comprises an indication that the UE supports indirect paging. Upon determining that the network node will forward the first report, the method comprises transmitting the first report to the network node. Upon determining that the network node will not forward the first report, the method comprises refraining from transmitting the first report.

Description

P113304W0011 of 37Avoiding Missed Paging When Using Wakeup SignalTECHNICAL FIELD

[0001] The present disclosure generally relates to communication networks, and more specifically to methods and apparatus for avoiding missed paging when using paging early indicator (PEI) or low-power wakeup signal (LP-WUS).BACKGROUND

[0002] Third Generation Partnership Project (3GPP) wireless networks include power saving features. Low-power wakeup signal (LP-WUS) in New Radio (NR) improves the user equipment (UE) power saving when the UE is in RRC IDLE or RRC INACTIVE. With LP-WUS the UE has a separate receiver wakeup radio (WUR), with a low-power radio (LR) that monitors LP-WUS. When LP-WUS is detected and the subgroup information in LP-WUS indicates that the UE should wake-up, then the UE wakes up the main radio (MR) in time to receive the paging physical downlink control channel (PDCCH)Zphysical downlink shared channel (PDSCH) during the following paging occasion (PO) in the discontinuous reception (DRX) cycle. Typically the UE is not paged during every PO, i.e. the MR can remain in sleep mode across multiple / many DRX cycles and save power. The LR consumes much less power than the MR (factor 10 to 100). LP-WUS is currently being standardized in 3GPP Release 19.

[0003] An entry condition (i.e. MR reference signal receive power (RSRP) / reference signal receive quality (RSRQ) threshold and optionally an LR RSRP / RSRQ threshold) and exit condition (i.e. LR threshold) is used to determine when the UE is allowed to use LP-WUS in RRC IDLE or RRC INACTIVE. When the UE is above the entry threshold(s), and the LR performs serving cell measurements using low -power synchronization signal (LP-SS) or synchronization signal block (SSB) and the LR uses LP-WUS to monitor paging, then the MR is not required to perform serving cell measurements nor paging monitoring, i.e., the UE can deactivate its MR.

[0004] 3 GPP Release 17 introduces a type of WUS for NR, then called ‘Paging Early Indication’ (PEI). However, since at the time no coverage enhancement was specified for NR, the only gain for Release 17 PEI was for scenarios where a small fraction of UEs in bad coverage suffered from large synchronization error due to the use of long DRX cycles. The gain for such UEs was that with the use of PEI they would typically only have to acquire one SSB before decoding PEI, instead of up to 3 SSBs if PEI is not used (value according to UE vendors). So, for most UEs, Release 17 PEI will result in gains or increased performance.P113304W0012 of 37

[0005] After a UE is released, to either RRC IDLE or RRC INACTIVE, the UE selects a cell to camp on. With cell selection the UE is required to find a suitable cell, see 38.304, i.e. basically the UE has to find a cell where the signal strength is of a minimum quality. The UE typically selects the same cell as in RRC_CONNECTED, i.e. the PCell. There is no particular reason for the UE to select another neighbor cell, and typically the PCell from RRC CONNECTED is suitable to camp on.

[0006] Paging messages allow the network to reach UEs in RRC IDLE and in RRC INACTIVE state, and to notify UEs in RRC IDLE, RRC INACTIVE and RRC_CONNECTED state of system information change (see clause 7.3.3) and earthquake and tsunami warning system (ETWS) / commercial mobile alert system (CMAS) indications (see clause 16.4) through Short Messages. Both Paging messages and Short Messages are addressed with paging radio network temporary identifier (P-RNTI) on PDCCH, but while the former is sent on PCCH, the latter is sent over PDCCH directly (see clause 6.5 of TS 38.331).

[0007] While in RRC IDLE a UE monitors the paging channels for core network (Coinitiated paging. While in RRC INACTIVE with no ongoing small data transmission (SDT) procedure (see clause 18.0) the UE monitors paging channels for radio access network (RAO-initiated paging and CN-initiated paging. A UE needs not monitor paging channels continuously though; paging DRX is defined where the UE in RRC IDLE or RRC INACTIVE is only required to monitor paging channels during one paging occasion (PO) per DRX cycle (see TS 38.304).

[0008] When the UE is released (state changes from RRC CONNECTED to RRC IDLE) the “last visited cell” information, i.e. the cell where the UE was last in RRC_CONNECTED, is transmitted to the CN. The CN can use this information when it needs to page the UE, i.e. when the UE has not moved then the UE will reply to paging in this cell. The paging load can thereby be reduced, i.e. only when the UE does not respond to the initial paging attempt, the network pages the UE in all the cells of the registration area. The UE informs the CN when it changes registration area. The same paging principles apply when the UE is in RRC INACTIVE and the UE updates the RAN when it changes the configured RAN notification area (RNA).

[0009] When a UE is configured with PEI and is camping on a cell supporting PEI, the UE does not monitor paging directly but instead monitors for a PEI signal a time offset before its legacy or normal paging occasion. If the UE receives a PEI, the UE monitors its paging occasion for the paging. If the UE does not receive the PEI, the UE will not monitor its paging occasion.

[0010] When a UE is configured with LP-WUS and is camping on a cell supporting LP-WUS, the UE does not monitor paging directly but instead monitors for a LP-WUS signal a time offset before its legacy or normal paging occasion. If the UE receives a LP-WUS, the UE monitors itsP113304W0013 of 37paging occasion for the paging. If the UE does not receive the LP-WUS, the UE may not monitor its paging occasion.

[0011] If both PEI and LP-WUS are configured, the UE can first monitor LP-WUS, and if a LP-WUS signal indicating the UEs LP-WUS subgroup the UE may further monitor for PEI, and if receiving a PEI indicating the UEs PEI subgroup monitor the paging occasion.

[0012] UE capability signaling is described in 3GPP TS 23.501. A UE needs to register with the network to receive services that require registration. The UE sends its capabilities to the CN (access and mobility management function (AMF)) upon initial registration. The capabilities are stored in the AMF as long as the UE is in RM-REGISTERED state. Once registered and if applicable the UE updates its registration with the network (see TS 23.502 ): periodically, to remain reachable (periodic registration update); upon mobility (mobility registration update); or to update its capabilities or re-negotiate protocol parameters (mobility registration update).

[0013] When the UE needs to update its capabilities, the UE perform the registration procedure with the registration type set to mobility registration update and it also includes "UE Radio Capability Update."

[0014] The AMF deletes the UE radio capability when the UE registration management (RM) state in the AMF transitions to RM-DEREGISTERED. When the AMF receives Registration Request with the Registration type set to Initial Registration or when the AMF receives the first Registration Request after E-UTRA / EPC Attach with Registration type set to Mobility Registration Update, the AMF deletes the UE radio capability.

[0015] If the UE's NG-RAN or E-UTRAN UE Radio Capability information changes while in CM-IDLE state, the UE shall perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update." When the AMF receives Mobility Registration Update Request with "UE Radio Capability Update" requested by the UE, the AMF shall delete any UE Radio Capability information that the AMF has stored for the UE. If the UE's NG-RAN UE Radio Capability information changes when the UE is in CM-IDLE with Suspend, non-access stratum (NAS) shall trigger access stratum (AS) to establish a new Radio Resource Control (RRC) connection and not resume the existing one to perform the Registration procedure with the Registration type set to Mobility Registration Update including "UE Radio Capability Update." As a result, the access stratum in the UE will discard the AS information and establish a new RRC connection as defined in TS 36.331.

[0016] If the trigger to change the UE's NG-RAN or E-UTRAN UE Radio Capability information happens when the UE is in CM-CONNECTED state, the UE shall first enter CM-P113304W0014 of 37IDLE state and then perform the Registration procedure with the Registration type set to Mobility Registration Update and it also includes "UE Radio Capability Update."

[0017] The RAN stores the UE Radio Capability information, received in the N2 message or obtained from the UE, for the duration of the UE staying in RRC CONNECTED or RRC_INACTIVE state. Before any 5G SRVCC handover attempt from NG-RAN to UTRAN, the RAN retrieves the UE's UTRA UE Radio Capabilities from the UE.

[0018] If the AMF sends N2 REQUEST (i.e. INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY CHECK REQUEST) message to NG-RAN without UE Radio Capability information in that message and there is no UE Radio Capability information available in RAN, this triggers the RAN to request the UE Radio Capability from the UE and to upload it to the AMF in the N2 UE RADIO CAPABILITY INFO INDICATION message. The capability information for a UE includes: receiving WUS Assistance Information (E-UTRA); Paging Subgrouping Support Indication (NR); and / or LP-WUS Paging Subgrouping Support Indication.

[0019] To support the LP-WUS, LP-WUS Paging Subgrouping Support Indication and the LP-WUS Assistance Information is used by the AMF and NG-RAN to help determine whether LP-WUS applies to the UE and which paging subgroup is used when paging the UE (see TS 38.300).

[0020] In the Registration Request message, the UE includes the LP-WUS Paging Subgrouping Support Indication if the UE supports LP-WUS Paging Subgrouping. If the UE includes LP-WUS Paging Subgrouping Support Indication, the UE may also include the paging probability information to assist the AMF. The AMF supporting LP-WUSPS stores the UE provided LP-WUS Support Indication in the UE context and the AMF determines AMF LP-WUSPS Assistance Information based on this indication. The AMF may further consider the local configuration, the UE's paging probability information if provided, information provided by the RAN (e.g., any of the Information On Recommended Cells And RAN nodes For Paging), and / or previous statistical information for the UE to determines AMF LP-WUSPS Assistance Information. The AMF LP-WUS PS Assistance Information includes the Paging Subgroup ID.

[0021] To support the Paging Early Indication with Paging Subgrouping (PEIPS), Paging Subgrouping Support Indication and the PEIPS Assistance Information is used by the AMF and NG-RAN to help determine whether PEIPS applies to the UE and which paging subgroup used when paging the UE (see TS 38.300).

[0022] In the Registration Request message, the Paging Subgrouping Support Indication indicates whether the UE supports PEIPS with AMF PEIPS Assistance Information. If the UE includes Paging Subgrouping Support Indication, the UE may also include the paging probabilityP113304W0015 of 37information to assist the AMF. If the AMF supports PEIPS assistance and if the UE provided Paging Subgrouping Support Indication, the AMF stores the indication in the UE context in AMF. The AMF may use local configuration, the UE's paging probability information if provided, information provided by the RAN (e.g., any of the Information On Recommended Cells And RAN nodes For Paging) and / or previous statistical information for the UE to determine the AMF PEIPS Assistance Information. The AMF PEIPS Assistance Information includes the Paging Subgroup ID.

[0023] Exactly what capability information will be defined for Release 19 is still under discussion. There are for example discussions of indicating minimum wake-up delay (RRC Idle and RRC Inactive), time gap between LP-WUS reception and PDCCH monitoring with MR (RRC Connected) and which bands where LP-WUS is supported and LP-WUS band restrictions.

[0024] In the UE capability the UE indicates to the network when the UE supports LP-WUS. The UE indicates in a band-list for which of the supported bands by the UE the UE supports LP-WUS. The following is an example Abstract Syntax Notation for UE capability.UE-RadioPagingInfo-rl7 ::= SEQUENCE {— R1 29-1: Paging enhancementpei-SubgroupingSupportBandList-rl7 SEQUENCE (SIZE (E.maxBands)) OF FreqBandlndicatorNR OPTIONAL,... ,[lpwus-SubgroupingSupportBandList-rl9 SEQUENCE (SIZE (E.maxBands)) OF FreqBandlndicatorNR OPTIONAL,]}maxBands INTEGER : := 1024 — Maximum number of supported bands in UE capability. FreqBandlndicatorNR : := INTEGER ( 1..1024)

[0025] It may be more complex and costly for the UE to implement LP-WUS in higher bands, and the LP-WUS coverage in higher bands may be reduced. For example, the UE may only support LP-WUS in low-band (coverage layer), and the UE does not support LP-WUS in mid-band.

[0026] A number of relevant 3GPP agreements have been reached as shown below.

[0027] For RRC CONNECTED mode, support UE capability report for determination of minimum time gap between LP-WUS reception and MR to start PDCCH monitoring.

[0028] For the wakeup delay, a UE reports one value from X candidate values for the wakeup delay via UE capability reporting. This applies for IDLE / INACTIVE mode.P113304W0016 of 37

[0029] Wakeup delay refers to minimum gap time between LP-WUS reception and MR to start PDCCH monitoring

[0030] As one option, for RRC CONNECTED mode, UE reports one value for each subcarrier spacing (SCS) from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting.

[0031] As another option, for RRC CONNECTED mode, UE reports multiple values for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting. Different minimum time gaps correspond to different sleep states.

[0032] Support 3 candidate values for the wakeup delay capability a UE reports, two values for ultra-deep sleep state and one value for deep sleep state.

[0033] For RRC CONNECTED mode, UE reports one value for each SCS from X candidate values for the determination of the minimum time gap between LP-WUS reception and MR to start PDCCH monitoring via UE capability reporting.

[0034] UE can indicate its preference for configured time offset between LP-WUS and PDCCH reception using UAI mechanism. UAI is optional.

[0035] For RRC connected, LP-WUS frequency resource can be outside of active downlink (DL) bandwidth part (BWP), but has to be within the same carrier as the active DL BWP.

[0036] Basic capability is LP-WUS, if present, frequency resource within active DL BWP. LP-WUS frequency resource outside of active DL BWP is subject to separate UE capability.

[0037] UE capability report on the wakeup delay may include the following options. As one option, for the 3 candidate values for the wake-up delay capability report, support {[70ms], [500ms] and [900ms]}. The reported values assume SSB periodicity of 20ms, where [70ms] assumes [3] SSBs needed for synchronization, [500ms] and [900ms] assume [5] SSBs needed for synchronization .

[0038] For the case when UE is configured with NR-dual connectivity (DC) with carrier aggregation (CA) without dual DRX groups or without CA in RRC CONNECTED mode, LP-WUS can be configured on a serving cell per cell-group. This does not imply that LP-WUS has to be configured on both cell groups. LP-WUS indication is applicable to all serving cells in the cell-group. There is no impact to PDCCH monitoring behavior related to SCell dormancy / activation / deactivation .

[0039] For the X = [2, 3] candidate values for the UE capability report on the minimum time gap for each SCS, consider {0.25, 0.5, 1, 2, 3, 6, 10, 20, 30, 40}ms. Other values are not precluded.P113304W0017 of 37

[0040] Only for reported value of [20ms,] 30ms and 40ms (if supported), the reported values assume SSB periodicity of 20ms and ensures SSB(s) before PDCCH reception and during time gap.

[0041] The network does not need to be aware of whether the UE is monitoring LP-WUS or not in RRC IDLE / INACTIVE.

[0042] A UE can report which band(s) is supported by LRto the network.

[0043] There currently exist certain challenges. For example, for the network to page a UE using either PEI or LP-WUS, the UE needs to indicate to the network that it is PEI or LP-WUS capable. This is done by the UE when the UE registers to the network using UE capability reporting in a UECapability Information message. After receiving the UECapabilitylnformation message, the gNB decodes it and accordingly generates the UERadioPaginglnformation inter-node message which contains the UE’s paging related capabilities including the LP-WUS capability. Then the gNB transfers this message to the CN and / or other gNBs. A problem arises if the transmission of the UECapabilitylnformation message is done to a gNB that does not comprehend and / or fails to forward this information to other gNBs and to the CN. In such a case, when the CN pages a UE supporting PEI / LP-WUS but without being able to forward this information to the paging gNB, the UE will not receive a PEI or LP-WUS indication and therefore the UE misses the paging. This is illustrated in Figure 1, which is reproduced from 3GPP contribution R2-2500302.SUMMARY

[0044] As described above, certain challenges currently exist with missed paging when using paging early indicator (PEI) or low-power wakeup signal (LP-WUS). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, when an LP-WUS user equipment (UE) reports its LP-WUS capability to the network, the UE may assume that the information is forwarded if the cell the UE is sending the LP-WUS capability to is configured with LP-WUS. In this case, the UE can use LP-WUS on all cells the UE later camps on that are configured with LP-WUS. When the UE reports its capability to a cell that is not configured with LP-WUS, the UE does not assume that this capability is forwarded to the core network (CN). In this case the UE does not use LP-WUS when re-selecting to a new cell that has LP-WUS configured. Instead, the UE first reports its capabilities to this cell. After this the UE may assume that the capability information is forwarded to other gNBs and CN and hence that the UE capability to support LP-WUS is known to the network.P113304W0018 of 37

[0045] In other words, a UE does not use LP-WUS before the UE has reported its LP-WUS capability to a cell that will forward the capability information to other gNBs. The indication that the cell will forward the UEs LP-WUS capability may be that the cell supports LP-WUS.

[0046] According to some embodiments, a method is performed by a user equipment (UE) for avoiding missed paging. The method comprises determining whether a network node will forward a first report received from the UE. The first report comprises an indication that the UE supports indirect paging. Upon determining that the network node will forward the first report, the method comprises transmitting the first report to the network node. Upon determining that the network node will not forward the first report, the method comprises refraining from transmitting the first report.

[0047] In particular embodiments, the method further comprises, upon determining that the network node will forward the first report, monitoring for an indirect paging signal (e.g., LP-WUS or PEI).

[0048] In particular embodiments, upon determining that the network node will not forward the first report, the method comprises monitoring for a direct paging signal.

[0049] In particular embodiments, determining whether the network node will forward the first report comprises determining whether the network node supports indirect paging.

[0050] In particular embodiments, determining whether the network node will forward the first report comprises receiving a system information message comprising an indication that the network node will or will not forward the first report.

[0051] In particular embodiments, determining whether the network node will forward the first report comprises determining whether the network node is associated with a particular network operator.

[0052] In particular embodiments, determining whether the network node will forward the first report is based on a physical cell identifier (PCI) associated with the network node.

[0053] In particular embodiments, determining whether the network node will forward the first report is based on a specification release number associated with the network node.

[0054] In particular embodiments, determining whether the network node will forward the first report is based on a previous indication saved by the UE associated with the network node.

[0055] In particular embodiments, determining whether the network node will forward the first report is based on information received regarding neighbor cells.

[0056] According to some embodiments, a user equipment comprises processing circuitry operable to perform any of the user equipment methods described above.P113304W0019 of 37

[0057] According to some embodiments, a method is performed by a network node. The method comprises providing a UE with an indication that the network node supports forwarding a first report to one or more additional network nodes. The first report comprises an indication that the UE supports indirect paging. The method further comprises receiving the first report from the UE and forwarding the first report to at least one additional network node.

[0058] In particular embodiments, the method further comprises transmitting an indirect paging signal (e.g., LP-WUS or PEI) to the UE.

[0059] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting an indication to the UE that the network node supports indirect paging.

[0060] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting a system information message comprising an indication that the network node will forward the first report.

[0061] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing an indication that the network node is associated with a particular network operator.

[0062] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a PCI associated with the network node to the UE.

[0063] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a specification release number associated with the network node to the UE.

[0064] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting information regarding neighbor cells to the UE.

[0065] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0066] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the user equipment described above.

[0067] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable,P113304W00110 of 37when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0068] Certain embodiments may provide one or more of the following technical advantages. For example, there is reduced risk that a UE is using LP-WUS to deduce if the UE should monitor paging when the network is unaware that the UE supports LP-WUS. Hereby it is avoided that the UE becomes unreachable. Certain embodiments rely on a minimum of signaling because there is no new signaling from the network to the UE. Only the UE capabilities need to be resent once the UE re-selects to a LP-WUS capable cell. The UE can use LP-WUS once the UE re-selects to a cell supporting LP-WUS and reports its capabilities to this cell.BRIEF DESCRIPTION OF THE DRAWINGS

[0069] The present disclosure may be best understood by way of example with reference to the following description and accompanying drawings that are used to illustrate embodiments of the present disclosure. In the drawings:Figure 1 is a network diagram illustrating a scenario where a legacy base station does not forward a user equipment (UE) capability regarding paging early indication (PEI) or low-power wakeup signal (LP-WUS) capabilities to other base stations;Figure 2 is a sequence diagram illustrating UE capability reporting, according to particular embodiments;Figure 3 shows an example of a communication system, according to certain embodiments; Figure 4 shows a user equipment (UE), according to certain embodiments;Figure 5 shows a network node, according to certain embodiments;Figure 6 is a block diagram of a host, according to certain embodiments;Figure 7 is a flowchart illustrating an example method in a user equipment, according to certain embodiments;Figure 8 is a flowchart illustrating an example method in a source network node, according to certain embodiments; andFigure 9 is a flowchart illustrating an example method in a target network node, according to certain embodiments.DETAILED DESCRIPTION

[0070] As described above, certain challenges currently exist with missed paging when using paging early indicator (PEI) or low-power wakeup signal (LP-WUS). Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example,P113304W00111 of 37when an LP-WUS user equipment (UE) reports its LP-WUS capability to the network, the UE may assume that the information is forwarded if the cell the UE is sending the LP-WUS capability to is configured with LP-WUS. In this case, the UE can use LP-WUS on all cells the UE later camps on that are configured with LP-WUS. When the UE reports its capability to a cell that is not configured with LP-WUS, the UE does not assume that this capability is forwarded to the core network (CN). In this case the UE does not use LP-WUS when re-selecting to a new cell that has LP-WUS configured. Instead, the UE first reports its capabilities to this cell. After this the UE may assume that the capability information is forwarded to other gNBs and CN and hence that the UE capability to support LP-WUS is known to the network.

[0071] Particular embodiments are described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0072] In the below embodiments, the capabilities referred to are LP-WUS and PEI. This does not limit the embodiments to these capabilities. The embodiments are equally valid also for other capabilities. Particular embodiments may also be applied to LP-WUS or PEI separately. An example is illustrated in Figure 2.

[0073] Figure 2 is a sequence diagram illustrating UE capability reporting, according to particular embodiments. In the illustrated example, the UE is moving from left to right.

[0074] In some embodiments (detection that cell does not forward capabilities), the UE detects that the UE is performing initial registration to a gNB or cell that does not forward LP-WUS or PEI capability to the CN. The detection that the gNB or cell which does not forward LP-WUS or PEI capability to the CN may be one or a combination of the following conditions:• The gNB or cell does not support LP-WUS and / or PEI, i.e. there is no configuration of LP-WUS or PEI in system information (SI). This may indicate that the cell only supports forwarding of capabilities other than LP-WUS or PEI.• The gNB or cell configures or has configured UE with LP-WUS and / or PEI and additionally indicates it will not forward the UE LP-WUS and / or PEI capabilities to other gNBs or cells or to the core network. The indication may be, e.g., a flag in broadcast system information. In one alternative, a flag in system information may indicate whether the core network or public land mobile network (PLMN) the gNB or cell belongs to does not support storing and handling of the (radio) paging capability information.• The physical cell identifier (PCI) is within certain intervals. There may be a list of PCIs of cells that support or not support forwarding of LP-WUS or PEI capabilities.• The cell belongs to a specific PLMN.P113304W00112 of 37• The cell belongs to a specific operator. For example, it may be known that specific operators do or do not support forwarding of LP-WUS or PEI capabilities.• The cell is of a specific type. The type in this case may be that the cell does not support any features from a specific release, e.g. Release 17 for PEI or Release-19 for LP-WUS. In case only features of older releases, i.e. pre-Release 17 for PEI or pre Release-19 for LP-WUS are supported in the cell, the UE may detect that the cell will not forward these capabilities.• The UE mobility history information, i.e. the UE has internally stored which gNBs or cells support the functionality and which do not when the UE previously visited the gNBs or cells.• Information signaled in system information about the functionality implemented in neighboring cells: The neighbor cell list provided in system information includes information whether the neighbor cell can use LP-WUS and / or PEI functionality and additionally process the information about LP-WUS and / or PEI capability of a UE received from another cell or from the core network.

[0075] In some embodiments (lean signaling), when a UE, performing initial registration to a gNB or cell detects that the gNB / cell does not forward LP-WUS or PEI capability to the CN, the UE does not include the LP-WUS capabilities when reporting its capabilities. Therefore, the UE may reduce the amount of capability signaling to the network and thereby reduce the signaling, i.e. omitting parts that are not used by the current gNB or cell.

[0076] In some embodiments (avoiding missed paging), when the UE has detected that the UE has registered to a gNB or cell that does not forward LP-WUS or PEI capability to the CN, the UE refrains from using LP-WUS or PEI after re-selecting to a new cell that supports LP-WUS or PEI.

[0077] In some embodiments (ensuring that the capabilities will be forwarded to CN), when the UE has detected that the UE has registered to a gNB or cell that does not forward LP-WUS or PEI capability to the CN, the UE re-registers to the network after re-selecting to a new cell that supports forwarding of LP-WUS or PEI capability to the CN. The detection of a cell or gNB that supports forwarding of LP-WUS or PEI capability to the CN may be one or a combination of the following conditions:• The gNB or cell supports LP-WUS or PEI, i.e. there is a configuration of LP-WUS or PEI in SI. This can indicate that the cell supports forwarding of capabilities of LP-WUS or PEI.• The gNB or cell configures or has configured the UE with LP-WUS and / or PEI and additionally indicates it will not forward the UE LP-WUS and / or PEI capabilities to other gNBs or cells or to the core network. The indication may be, e.g., a flag in broadcast systemP113304W00113 of 37information. In one alternative, a flag in system information may indicate whether the core network or PLMN the gNB or cell belongs to does not support storing and handling of the (radio) paging capability information.• The PCI is within certain intervals. There may be a list of PCIs of cells that support forwarding of LP-WUS or PEI capabilities.• The cell belongs to a specific PLMN.• The cell belongs to a specific operator. For example, it may be known that specific operators support forwarding of LP-WUS or PEI capabilities in all cells.• The cell is of a specific type. The type in this case may be that the cell does support a feature from a specific release, e.g. Release 17 for PEI or Release- 19 for LP-WUS. In case a feature of a newer release, i.e. Release 17 or later for PEI or Release-19 for LP-WUS are supported in the cell, the UE may detect that the cell will forward these capabilities.• The UE mobility history information, i.e.. the UE has internally stored which gNBs or cells support the functionality and which do not when the UE previously visited the gNBs or cells.• Information signaled in system information about the functionality implemented in neighboring cells: The neighbor cell list provided in system information includes information whether the neighbor cell can use LP-WUS and / or PEI functionality and additionally process the information about LP-WUS and / or PEI capability of a UE received from another cell or from the core network.

[0078] In some embodiments (using PEI or LP-WUS after ensuring the capabilities are forwarded), when the UE has re-registered to a gNB or cell that supports forwarding of LP-WUS or PEI capability to the CN, the UE uses LP-WUS or PEI according to the configuration of the cell where it is camping. Re-registration may mean that the UE first deregisters and then performs a new initial registration or that the UE performs a Mobility Registration Update or a Periodic Registration Update.

[0079] In some embodiments, the UE tries to register (initial registration or re-registration) to a cell that supports LP-WUS or PEI. This means that the UE does not necessarily register to the best cell or on the prioritized frequency. Instead, the UE selects a cell for registration that is sufficiently good, e.g. has an RSRP and or RSRQ above a specified threshold. Compared to the legacy cell search procedure, the UE will after reading the SIB and the SIB does not include LP-WUS or PEI configuration try to find a different cell on the same or different frequency which supports LP-WUS or PEI.P113304W00114 of 37

[0080] Figure 3 shows an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0081] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, 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. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0082] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0083] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a MobileP113304W00115 of 37Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0084] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0085] As a whole, the communication system 100 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0086] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0087] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or externalP113304W00116 of 37event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi -radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0088] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0089] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.P113304W00117 of 37

[0090] Figure 4 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0091] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

[0092] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 2. 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.

[0093] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware -implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), togetherP113304W00118 of 37with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0094] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include 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. An input device may allow a user to capture information into the UE 200. Examples of an input device 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, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0095] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0096] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0097] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hardP113304W00119 of 37disk 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 tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and 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 as or in the memory 210, which may be or comprise a device -readable storage medium.

[0098] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0099] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, 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. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.P113304W00120 of 37

[0100] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0101] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0102] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 2.

[0103] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UEP113304W00121 of 37may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0104] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0105] Figure 5 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication 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 NRNodeBs (gNBs)).

[0106] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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).

[0107] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, 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), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).P113304W00122 of 37

[0108] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 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 the network node 300 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) 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 300.

[0109] The processing circuitry 302 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 300 components, such as the memory 304, to provide network node 300 functionality.

[0110] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC).In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 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 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.[oni] The memory 304 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, aP113304W00123 of 37flash 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 the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0112] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0113] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).P113304W00124 of 37

[0114] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0115] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0116] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0117] Embodiments of the network node 300 may include additional components beyond those shown in Figure 5 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, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0118] Figure 6 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 1, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server,P113304W00125 of 37a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0119] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 3, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0120] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0121] Figure 7 is a flowchart illustrating an example method 700 in a user equipment, according to certain embodiments. In particular embodiments, one or more steps of Figure 7 may be performed by UE 200 described with respect to Figure 4.

[0122] The method begins at step 712, where the user equipment (e.g., UE 200) determines whether a network node will forward a first report received from the UE (e.g., forward to other radio access network nodes and / or core network nodes). The first report comprises an indication that the UE supports indirect paging (e.g., supports LP-WUS and / or PEI).

[0123] In particular embodiments, determining whether the network node will forward the first report comprises determining whether the network node supports indirect paging.P113304W00126 of 37

[0124] In particular embodiments, determining whether the network node will forward the first report comprises receiving a system information message comprising an indication that the network node will or will not forward the first report.

[0125] In particular embodiments, determining whether the network node will forward the first report comprises determining whether the network node is associated with a particular network operator.

[0126] In particular embodiments, determining whether the network node will forward the first report is based on a physical cell identifier (PCI) associated with the network node.

[0127] In particular embodiments, determining whether the network node will forward the first report is based on a specification release number associated with the network node.

[0128] In particular embodiments, determining whether the network node will forward the first report is based on a previous indication saved by the UE associated with the network node (e.g., the UE previously visited the network node or cell).

[0129] In particular embodiments, determining whether the network node will forward the first report is based on information received regarding neighbor cells.

[0130] In particular embodiments, the UE determines whether the network node will forward the first report according to any of the embodiments and examples described herein. For example, more detailed examples are described with respect to Figure 2.

[0131] At step 714, upon determining that the network node will forward the first report, the UE transmits the first report to the network node. The method may then continue to step 718.

[0132] At step 716, upon determining that the network node will not forward the first report, the UE refrains from transmitting the first report. In particular embodiments, upon determining that the network node will not forward the first report, the method comprises monitoring for a direct paging signal. For example, the UE will not monitor for LP-WUS or PEI, and instead monitors for paging in a paging occasion.

[0133] At step 718, upon determining that the network node will forward the first report at previous step 714, the UE monitors for an indirect paging signal (e.g., LP-WUS or PEI).

[0134] In some embodiments (avoiding missed paging), when the UE determines that the UE has registered to a network node or cell that does not forward LP-WUS or PEI capability to one or more other network nodes, the UE refrains from using LP-WUS or PEI after reselecting to a new cell that supports LP-WUS or PEI. The UE may reregister to the network after reselecting to anew cell that supports forwarding of LP-WUS or PEI capability to one or more other network nodes.P113304W00127 of 37

[0135] Modifications, additions, or omissions may be made to method 700 of Figure 7. Additionally, one or more steps in the method of Figure 7 may be performed in parallel or in any suitable order.

[0136] Figure 8 is a flowchart illustrating an example method 800 in a network node, according to certain embodiments. In particular embodiments, one or more steps of Figure 8 may be performed by network node 300 described with respect to Figure 5.

[0137] The method begins at step 812, where the network node (e.g., network node 300) provides a UE with an indication that the network node supports forwarding a first report to one or more additional network nodes. The first report comprises an indication that the UE supports indirect paging.

[0138] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting an indication to the UE that the network node supports indirect paging.

[0139] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting a system information message comprising an indication that the network node will forward the first report.

[0140] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing an indication that the network node is associated with a particular network operator.

[0141] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a PCI associated with the network node to the UE.

[0142] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a specification release number associated with the network node to the UE.

[0143] In particular embodiments, providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting information regarding neighbor cells to the UE.

[0144] In particular embodiments, the network node provides the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes according to any of the embodiments and examples described herein. For example, more detailed examples are described with respect to Figure 2.

[0145] At step 814, the network node receives the first report from the UE.P113304W00128 of 37

[0146] At step 816, the network node forwards the first report to at least one additional network node (e.g., a radio access network node or a core network node).

[0147] At step 818, the network node may transmit an indirect paging signal (e.g., LP-WUS or PEI) to the UE.

[0148] Modifications, additions, or omissions may be made to method 800 of Figure 8. Additionally, one or more steps in the method of Figure 8 may be performed in parallel or in any suitable order.

[0149] Some example embodiments are described below.Group A Embodiments1. A method performed by a wireless device for avoiding missed paging, the method comprising:determining whether a network node will forward a first report received from the wireless device;upon determining that the network node will forward the first report, transmitting the first report to the network node; andupon determining that the network node will not forward the first report, refraining from transmitting the report.2. The method of 1 wherein upon determining that the network node will forward the report, monitoring for an indirect paging signal.3. The method of any of 1-2 wherein monitoring for an indirect paging signal comprises monitoring for a low power wake-up signal (LP-WUS) or a paging early indication (PEI).4. The method of 1 wherein upon determining that the network node will not forward the report monitoring for a direct paging signal despite the wireless device supporting indirect paging.5. The method of any of 1-4 further comprising transmitting a message indicating that the wireless devices supports LP-WUS and / or PEI or including such an indication in the first report.6. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises determining whether the network node is configured for or supports LP-WUS and / or PEI.P113304W00129 of 377. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises receiving a system information message that comprises an indication that the network node will or will not forward the first report.8. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises determining whether the network node is associated with a cell that belongs to a specific public land mobile network (PLMN) or a specific operator.9. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises determining whether the physical cell identity (PCI) is within a certain interval.10. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises determining which 3GPP release is supported by the network node.11. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises checking where the wireless device has saved a prior indication that the network node will forward the first report.12. The method of any of 1-5 wherein determining whether the network node will forward the first report comprises determining functionality implemented by one or more neighboring cells.13. The method of 12 wherein determining functionality implemented by one or more neighboring cells comprises receiving system information comprising an indication of the functionality implemented by the one or more neighboring cells.14. The method of any of 1 - 13 wherein upon determining that the network node will not forward the report, refraining from providing the network node with an indication that the wireless device supports LP-WUS and / or PEI.15. The method of any of 1-14 wherein upon determining that the network node will forward the report, monitoring for the direct paging signal upon the wireless device determining that a prior network node to which the wireless device was associated did not forward reports.P113304W00130 of 3716. The method of any of 1 - 15 further comprising selecting a cell with which to register, wherein the wireless selects a cell based in part on whether the cell supports LP-WUS and / or PEI.17. The method of 16 wherein the wireless device selects a cell that does not have the best signal or that does not use a prioritized frequency.18. The method of any of 1-17 wherein the report comprises a report of the capabilities of the wireless device including low power capabilities.19. The method of 18 wherein the capabilities comprise LP-WUS and / or PEI capabilities.20. The method of any of 1-19 wherein determining whether the network node will forward the first report comprises combining two or more of the options above.21. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host via the transmission to the network node.Group B Embodiments22. A method performed by a network node for avoiding missed paging, the method comprising:providing a wireless device with an indication that the network node supports forwarding a first report to one or more additional network nodes;receiving the first report; andforwarding the first report to at least one additional network node.23. The method of 22 further comprising using a low power wake-up signal (LP-WUS) or a paging early indication (PEI) to reach the wireless device.24. The method of any of 22-23 further comprising receiving a message indicating that the wireless devices supports LP-WUS and / or PEI.25. The method of any of 22-24 wherein providing the wireless device with an indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing the wireless device with an indication that the network node is configured forP113304W00131 of 37or supports LP-WUS and / or PEI.26. The method of any of 22-24 wherein providing the wireless device with an indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting a system information message that comprises an indication that the network node will or will not forward the first report.27. The method of any of 22-24 wherein providing the wireless device with an indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing the wireless device with an indication of the functionality implemented by one or more neighboring cells.28. The method of any of the previous embodiments, further comprising:obtaining user data; andforwarding the user data to a host or a user equipment.Group C Embodiments29. A wireless device for avoiding missed paging, comprising:processing circuitry configured to perform any of the operations of any of the Group A embodiments; anda power source configured to supply power to the processing circuitry.30. A network node for avoiding missed paging, the network node comprising:processing circuitry configured to perform any of the operations of any of the Group B embodiments;a power source circuitry configured to supply power to the processing circuitry.31. A wireless device for avoiding missed paging, the wireless device comprising:one or more antennas;communication interface connected to the one or more antennas and to processing circuitry;the processing circuitry being configured to perform any of the operations of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input ofP113304W00132 of 37information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda power source connected to the processing circuitry and configured to supply power to the UE.

[0150] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0151] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0152] 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 scope of this disclosure, as defined by the claims below.

Claims

1. P113304W00133 of 37Claims1. A method (700) performed by a user equipment (UE) for avoiding missed paging, the method comprising:determining (712) whether a network node will forward a first report received from the UE, the first report comprising an indication that the UE supports indirect paging;upon determining that the network node will forward the first report, transmitting (714) the first report to the network node;upon determining that the network node will not forward the first report, refraining (716) from transmitting the first report.

2. The method of claim 1, further comprising upon determining that the network node will forward the first report, monitoring (718) for an indirect paging signal.

3. The method of claim 2, wherein the indirect paging signal comprises a low power wake-up signal (LP-WUS) or a paging early indication (PEI).

4. The method of any one of claims 1 -3 , wherein upon determining that the network node will not forward the first report, monitoring (720) for a direct paging signal.

5. The method of any one of claims 1-4, wherein determining whether the network node will forward the first report comprises determining whether the network node supports indirect paging.

6. The method of any one of claims 1-5, wherein determining whether the network node will forward the first report comprises receiving a system information message comprising an indication that the network node will or will not forward the first report.

7. The method of any one of claims 1-6, wherein determining whether the network node will forward the first report comprises determining whether the network node is associated with a particular network operator.

8. The method of any one of claims 1-7, wherein determining whether the network node will forward the first report is based on a physical cell identifier (PCI) associated with the networkP113304W00134 of 37node.

9. The method of any one of claims 1-8, wherein determining whether the network node will forward the first report is based on a specification release number associated with the network node.

10. The method of any one of claims 1-9, wherein determining whether the network node will forward the first report is based on a previous indication saved by the UE associated with the network node.

11. The method of any one of claims 1-10, wherein determining whether the network node will forward the first report is based on information received regarding neighbor cells.

12. A user equipment (200) comprising processing circuitry (202) operable to: determine whether a network node (300) will forward a first report received from the UE, the first report comprising an indication that the UE supports indirect paging;upon determining that the network node will forward the first report, transmit the first report to the network node;upon determining that the network node will not forward the first report, refrain from transmitting the first report.

13. The user equipment of claim 12, the processing circuitry further operable to perform the steps of any one of claims 2-11.P113304W00135 of 3714. A method (800) performed by a network node, the method comprising: providing (812) a user equipment (UE) with an indication that the network node supports forwarding a first report to one or more additional network nodes, the first report comprising an indication that the UE supports indirect paging;receiving (814) the first report from the UE; andforwarding (816) the first report to at least one additional network node.

15. The method of claim 14, further comprising transmitting (818) an indirect paging signal to the UE.

16. The method of claim 15, wherein the indirect paging signal comprises a low power wake-up signal (LP-WUS) or a paging early indication (PEI).

17. The method of any one of claims 14-16, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting an indication to the UE that the network node supports indirect paging.

18. The method of any one of claims 14-17, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting a system information message comprising an indication that the network node will forward the first report.

19. The method of any one of claims 14-18, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing an indication that the network node is associated with a particular network operator.

20. The method of any one of claims 14-19, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a physical cell identifier (PCI) associated with the network node to the UE.

21. The method of any one of claims 14-20, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises providing a specification release number associated with the network node to the UE.P113304W00136 of 3722. The method of any one of claims 14-21, wherein providing the UE with the indication that the network node supports forwarding the first report to one or more additional network nodes comprises transmitting information regarding neighbor cells to the UE.

23. A network node (300) comprising processing circuitry (302) operable to: provide a user equipment (UE) (200) with an indication that the network node supports forwarding a first report to one or more additional network nodes, the first report comprising an indication that the UE supports indirect paging;receive the first report from the UE; andforward the first report to at least one additional network node.

24. The network node of claim 23, the processing circuitry operable to perform the steps of any one of claims 15-22.

Images