Method and apparatus to redirect LP-WUS user equipment in system information block
By using flags in system information to prioritize frequencies for LP-WUS monitoring, LP-WUS UEs are redirected to less congested frequencies, addressing power inefficiencies and network congestion in urban environments.
Patent Information
- Application Number
- PCT/IB2026/054527
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-07
- Publication Date
- 2026-11-12
AI Technical Summary
LP-WUS UEs face challenges in urban environments where mid-band cells are prevalent, leading to reduced coverage and congestion issues, as they cannot utilize LP-WUS when camped on mid-band cells, resulting in inefficient power consumption and potential network overload.
Implementing flags or indications in system information to prioritize or deprioritize frequencies for LP-WUS monitoring based on congestion status, allowing UEs to redirect to less congested frequencies, thereby optimizing cell reselection and reducing network congestion.
Enables efficient power management by ensuring LP-WUS UEs camp on optimal frequencies, preventing reselection to congested cells, and maintaining network stability by dynamically adjusting frequency prioritization based on congestion.
Smart Images

Figure IB2026054527_12112026_PF_FP_ABST
Abstract
Description
METHOD AND APPARATUS TO REDIRECT LP-WUS USER EQUIPMENT IN SYSTEM INFORMATION BLOCK RELATED APPLICATIONS
[0001] This application claims the benefit of U.S. Provisional Patent Application No.63 / 802,702, filed May 9, 2025, the disclosure of which is hereby incorporated herein by reference in its entirety.TECHNICAL FIELD
[0002] The present disclosure relates to a wireless communication system and, more specifically, to Low Power Wake-Up Signal (LP-WUS) monitoring in a wireless communication system.BACKGROUND
[0003] Low Power Wake Up Signal (LP-WUS) in 3rdGeneration Partnership Project (3GPP) New Radio (NR) improves the User Equipment (UE) power saving when the UE is in Radio Resource Control (RRC) idle state (RRC IDLE) or RRC inactive state (RRC INACTIVE) and the UE monitors paging. With LP-WUS, the UE has a separate receiver Wake-Up Radio (WUR), with a Low power Radio (LR) that monitors LP-WUS. When LP-WUS is detected and the subgroup information in the detected LP-WUS indicates that the UE should wake-up, then the UE receives the Paging Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) during the following Paging Occasion (PO) in the Discontinuous Reception (DRX) cycle using the Main Radio (MR). Typically, the UE is not paged during every PO, i.e. the MR can remain in sleep mode for multiple / many DRX cycles and save power. The LR consumes much less power compared to the MR (e.g., factor 10 to 100).
[0004] Two types of UE subgroupings can be used: UE Identity (UE-ID) based and / or Core Network (CN)-assigned subgrouping. With UE-ID based subgrouping, the UE is assigned a subgroup ID based on its UE-ID, i.e. the UEs are “randomly” divided over the subgroups. With CN-assigned subgrouping, the UE receives a subgroup ID from the CN during registration. When the UE supports LP-WUS, then the UE supports UE-ID based subgrouping. The UE may optionally in addition support CN-assigned subgrouping. The NR base station (gNB) can configure the use of UE-ID based and / or CN-assigned based subgrouping in the cell. When the UE has a CN-assigned subgroup ID and the cell supports CN-assigned subgrouping, then the UE uses the CN-assigned subgroup ID to monitor paging. Otherwise, UE-ID based subgrouping is used.
[0005] Due to its signal characteristics, LP-WUS may not provide full cell coverage, i.e. near the cell border there is no LP-WUS coverage. Thus, an entry condition (i.e. MR Reference Signal Received Power (RSRP) or Reference Signal Received Quality (RSRQ) threshold and optionally an LR RSRP or 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), the LR performs serving cell measurements using LP-Synchronization Signal (SS) or SS / Physical Broadcast Channel (PBCH) 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. can be deactivated.
[0006] The UE indicates via UE capability signaling when it supports LP-WUS in RRC IDLE and RRC INACTIVE. The UE may not support LP-WUS in all the bands that the UE supports, i.e. the LP-WUS capability is indicated per band (similar as with Paging Early Indication (PEI)) as shown in the excerpt from section 6.3.3 in 3GPP Technical Specification (TS) 38.331 vl8.5.1 shown in Figure 1.
[0007] 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 (capacity layer).
[0008] An LP-WUS UE performs cell (re-)selection as other UEs, (see section 5.2 in 3 GPP TS 38.304 V18.4.0) i.e. based on absolute frequency priorities provided in System Information Block 4 (SIB4) and based on dedicated frequency priorities provided in the RRC Release message (RRCRelease), if provided in cellReselectionPriorities. Furthermore, in case RedirectedCarrierlnfo is provided in RRCRelease, the UE tries to select a suitable cell on that frequency.
[0009] Using load balancing, the network (NW) tries to distribute the UEs over the available system resources in idle / inactive, i.e. available cells:- Using higher absolute frequency priorities in System Information Block (SIB) for midband cells, the UE reselects to a midband cell when it is inside midband coverage.- Using redirection info and (even higher) dedicated priorities in RRCRelease, the NW can redirect the UE to a frequency / cell based on the current load distribution.
[0010] In case the UE only supports LP-WUS in low band, then the UE cannot use LP-WUS when camped on a midband cell, i.e. reducing the benefit of the feature. For example, Figure 2 illustrates a scenario in which mid-band cells are present in an urban environment and in whichUEs that only support LP-WUS in low band are not able to use LP-WUS when camped on any of the midband cells. In urban environments most UEs are camped on midband.
[0011] The following options / solutions to mitigate the LP-WUS band restrictions have been identified and evaluated (see 3GPP document RP-242656):- Solution 1: MR is prioritized (via SIBs) to camp on the same band as LR (System information, Paging, Random Access Channel (RACH) on LR band).Solution 2: MR is prioritized to camp on the same band as LR (System information, Paging on LR band; and RACH on another MR band based on reselection criteria).Solution 3: MR is not prioritized to camp on the same band as LR but can be redirected via dedicated signaling depending on LR band load (up to gNB implementation).
[0012] A short comparison of the aforementioned solutions is provided in Table 1 below:Table 1 : Comparison of Solutions to Mitigate LP-WUS Band Restrictions Description ComparisonSolution 1 Indicated in SIB that an LP-WUS May cause congestion on LP-WUS UE is allowed to prioritize a frequency when a lot of LP-WUS frequency where it can monitor LP- UEs re-select that the LP-WUS WUS. frequency.Solution 2 An LP-WUS UE monitors LP-WUS Complex solution with different and paging on the LP-WUS issues to be resolved.frequency, but responds to pagingon another frequency e.g. midband.Solution 3 LP-WUS UE is redirected to LP- No specification impact (and WUS frequency and provided with a already supported in some networks higher dedicated frequency priority for load balancing but not in RRCRelease, when the LP-WUS specifically for LP-WUS frequency is not congested. frequencies).
[0013] RAN2 agreed to rely on solution 3 (see 3GPP document R2-2501443). Specifically, RAN2 stated the following:- RAN2 understands that UE can report which band(s) is supported by LR to NW.- RAN2 understands that any potential overload issues could be addressed by the current mechanism in the 3GPP NR specification.
[0014] Solutions 1 and 3 are similar in the sense that both solutions redirect LP-WUS UEs to a frequency where they can monitor LP-WUS. With solution 3, the redirection is per UE, while with solution 1 the redirection is for all the LP-WUS UEs that are camped on the cell. With solution 1, it is also possible to take congestion on the LP-WUS frequency into account, i.e. the SIB information can be modified when the congestion on the LP-WUS frequency changes. Note that redirection of (LP-WUS) UEs from an (LP-WUS) frequency that is not congested is part of the normal load balancing implemented in the NW.
[0015] In regard to low band congestion information, typically, the UE is configured with Carrier Aggregation (CA) or Dual Connectivity (DC) when in connected mode. In case the low band and midband cells are co-located, then the gNB receives measurement reporting from the low band cell, and the gNB may know whether the low band is congested or not. The gNB may not have measurement reports from low band nor congestion information from low band when the midband cells are configured standalone. See Figure 3 as an example.
[0016] In case of standalone midband, either LP-WUS UEs are not redirected to low band or there is “blind” redirection. Congestion is cell specific, e.g. congestion is experienced in one or multiple neighboring cells due to a high number of UEs present in the cell. Congestion is typically not experienced on all the cells on the frequency.
[0017] Typically, the coverage area of midband cells is considerably smaller compared to low band cells. Furthermore, the coverage area of a midband cell may include more than one low band cell.
[0018] When content in System Information (SI) changes, the UE is informed about this via Paging, i.e. in Paging PDCCH (also known as a short message) the is a flag set “SI change”, which indicates to the UE that something in system information has changed. The UE is then required to acquire the Master Information Block (MIB) and SIB 1 (SIB1) and check the scheduling information in SIB1 to see which SIBs have changed, i.e. the valueTag of a SIB is incremented when it is changed. Next, the UE acquires the SIBs that have changed. Normally the system information content does not change often, if at all. Except for Earthquake and Tsunami Warning System (ETWS) / Commercial Mobile Alert System (CMAS) warning messages, i.e. especially CMAS alerts in the United States of America (USA) may be continuously updated 24 / 7 e.g. Amber alerts.SUMMARY
[0019] Systems and methods are disclosed for redirecting a low power wakeup signal (LP-WUS) wireless device. In one embodiment, a method performed by a wireless device for LP-WUS monitoring comprises receiving, on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring. The method further comprises initiating a cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring. The method further comprises, while performing the cell reselection to the second cell, receiving, on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring and, in response to receiving the second indication, aborting the cell reselection. In this manner, a LP-WUS wireless device initiating inter-frequency cell re-selection can be prevented from reselecting to a congested cell. This enables redirection to an LP-WUS frequency when congestion status is unknown on the frequency / cell redirecting the UE.
[0020] In one embodiment, the system information comprising the first indication is either: a System Information Block 1 (SIB1) or similar SIB containing cell selection information received on the first cell or a System Information Block 4 (SIB4) or similar SIB containing cell reselection parameters received on the first cell.
[0021] In one embodiment, the first indication is an explicit indication that the certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring.
[0022] In one embodiment, the system information comprising the second indication is a SIB 1 or similar SIB containing cell selection information received on the second cell.
[0023] In one embodiment, the first indication is received in inter-frequency carrier frequency list or a LP-WUS configuration information element.
[0024] In one embodiment, the second indication is received in an LP-WUS configuration information element.
[0025] In one embodiment, separate first indications are received for each frequency on which the wireless device supports LP-WUS monitoring.
[0026] In one embodiment, the first indication indicates that the certain frequency is not congested.
[0027] In one embodiment, the second indication indicates that the certain frequency is congested.
[0028] In one embodiment, receiving the system information comprising the first indication comprises re-acquiring all system information on the first cell.
[0029] In one embodiment, receiving the system information comprising the second indication comprises re-acquiring all system information on the second cell.
[0030] In one embodiment, receiving the system information comprising the first indication comprises receiving a portion of the system information that has been updated.
[0031] In one embodiment, receiving the system information comprising the second indication comprises receiving a portion of the system information that has been updated.
[0032] Corresponding embodiments of a wireless device are also disclosed. In one embodiment, a wireless device for LP-WUS monitoring comprises a communication interface comprising a transmitter and a receiver. The wireless device further comprises processing circuitry associated with the communication interface, wherein the processing circuitry is configured to cause the wireless device to receive, on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring. The processing circuitry is further configured to cause the wireless device to initiate a cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring. The processing circuitry is further configured to cause the wireless device to, while performing the cell reselection to the second cell, receive, on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring and, in response to receiving the second indication, abort the cell reselection.
[0033] In another embodiment, a method performed by a wireless device for LP-WUS monitoring comprises receiving, on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring and performing a first cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring. The method further comprises, while camping on the second cell, receiving, on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring and, in response to receiving the second indication, performing a second cell reselection to another frequency.
[0034] In one embodiment, the system information comprising the first indication is either: a SIB 1 or similar SIB containing cell selection information received on the first cell or a SIB4 or similar SIB containing cell reselection parameters received on the first cell.
[0035] In one embodiment, the first indication is an explicit indication that the certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring.
[0036] In one embodiment, the system information comprising the second indication is a SIB 1 or similar SIB containing cell selection information received on the second cell.
[0037] Corresponding embodiments of a wireless device are also disclosed. In one embodiment, a wireless device for LP-WUS monitoring comprising a communication interface comprising a transmitter and a receiver. The UE further comprises processing circuitry associated with the communication interface, wherein the processing circuitry is configured to cause the wireless device to receive, on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring and perform a first cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring. The processing circuitry is further configured to cause the wireless device to, while camping on the second cell, receive, on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring and, in response to receiving the second indication, perform a second cell reselection to another frequency.
[0038] Embodiments of a method performed by a network node are also disclosed. In one embodiment, a method performed by a network node for enabling LP-WUS monitoring comprises transmitting, on a cell that is on a certain frequency, system information comprising an indication that prioritization of the certain frequency for cell reselection for LP-WUS monitoring is not allowed.
[0039] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for enabling LP-WUS monitoring comprises processing circuitry configured to cause the network node to transmit, on a cell that is on a certain frequency, system information comprising an indication that prioritization of the certain frequency for cell reselection for LP-WUS monitoring is not allowed.BRIEF DESCRIPTION OF THE DRAWINGS
[0040] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0041] Figure 1 illustrates an excerpt from section 6.3.3 in 3rdGeneration Partnership Project (3 GPP) Technical Specification (TS) 38.331 vl8.5.1.
[0042] Figure 2 illustrates a scenario in which mid-band cells are present in an urban environment and in which User Equipments (UEs) that only support Low Power Wake-Up Signal (LP-WUS) in low band are not able to use LP-WUS when camped on any of the midband cells.
[0043] Figure 3 illustrates an example in which a UE is configured with Carrier Aggregation (CA) or Dual Connectivity (DC) when in connected mode.
[0044] Figure 4 illustrates a problem with LP-WUS monitoring where a UE may reselect to a cell on a LP-WUS frequency that is congested.
[0045] Figure 5 is a flow chart that illustrates the operation of a UE, in accordance with an exemplary embodiment of the present disclosure.
[0046] Figure 6 is a flow chart that illustrates the operation of a UE, in accordance with another exemplary embodiment of the present disclosure.
[0047] Figure 7 shows an example of a communication system in accordance with some embodiments of the present disclosure.
[0048] Figure 8 is another example of a communication system 800 according to some embodiments.
[0049] Figure 9 shows a wireless device, which may be configured to operate in the communication system of Figure 7 or in the communication system of Figure 8.
[0050] Figure 10 shows a network node in accordance with some embodiments of the present disclosure.
[0051] Figure 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
[0052] Figure 12 illustrates a method in accordance with some embodiments of the present disclosure.DETAILED DESCRIPTION
[0053] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.
[0054] Some of the embodiments contemplated herein will now be described 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.
[0055] There currently exist certain challenge(s). For example, some network implementations may not have implemented redirection and dedicated priorities in the Radio Resource Control (RRC) Release message (RRCRelease) for load balancing purposes. For suchnetworks, it may be simpler to introduce redirection information in a System Information Block (SIB) for Low Power Wake-Up Signaling (LP-WUS). However, redirection information in SIB towards LP-WUS frequency(ies) may not be sufficient when:Congestion status on the LP-WUS frequency is missing (e.g. standalone midband) The cell overlaps with more than one cell on the LP-WUS frequency.In these use cases, the UE may reselect to a cell on the LP-WUS frequency that is congested causing further congestion, while an LP-WUS UE is able to receive paging on a frequency where LP-WUS is not supported. This problem is illustrated in Figure 4. As illustrated in Figure 3, the low band cell on the left is congested but the standalone midband cell that overlaps this low band cell does know have congestion information for the low band frequency. Thus, an LP-WUS UE may reselect to this low-band cell that is already congested which will cause further congestion.
[0056] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, certain embodiments introduce flags or indications in system information broadcast to indicate, for example, whether a UE supporting LP-WUS in a particular band is allowed to consider the frequency to be prioritized during cell reselection (Ipwus-PrioritizationAllowed). As another example, whether the UE cannot consider a frequency to be a prioritized frequency for LP-WUS monitoring. The UE can monitor LP-WUS on the particular frequency but it cannot be considered a prioritized frequency when doing a cell reselection. That is, the UE will move away when it eventually finds a higher priority frequency. This can be useful to move UEs immediately out from a congested frequency, when needed (Ipwus-Pri oritizati onN ot All owed) .
[0057] An LP-WUS UE is allowed to consider the LP-WUS frequency the highest priority frequency when Ipwus-Pri oritizati onAllowed is present in lpwus-Config-rl9 in SIB 1 and the UE monitors LP-WUS for paging.
[0058] An LP-WUS UE initiates cell reselection to a frequency indicated in SIB 4 (SIB4) with Ipwus-PrioritizationAllowed set when it is camped on a frequency where it cannot monitor LP-WUS (either LP-WUS is not configured or the UE does not support LP-WUS on this frequency / band). The UE aborts this cell reselection when Ipwus-PrioritizationNotAllowed is present in lpwus-Config-rl9 in SIB1.
[0059] Certain embodiments may provide one or more of the following technical advantage(s). For example, LP-WUS UEs can initiate cell re-selection to a frequency where they can monitor LP-WUS for paging. This redirection can be dependent on whether the LP-WUS frequency is congested or not. As another example, an LP-WUS UE initiating inter-frequency cell re-selection can be prevented from reselecting to a congested cell. This enables redirection to anLP-WUS frequency when congestion status is unknown on the frequency / cell redirecting the UE. This enables redirection when congestion status is known on the frequency / cell redirecting the UE, but the redirecting cell covers both a congested and uncongested cell. As another example, when the LP-WUS frequency / cell becomes congested, LP-WUS UEs camped on the cell can be triggered to reselect to another frequency.
[0060] Certain embodiments allow the network / gNB to be able to indicate in system information whether a particular frequency is allowed to be prioritized for LP-WUS monitoring by the UE when doing a cell reselection. LP-WUS monitoring in this context means the UE can expect the network / gNB / base station to send LP-WUS to indicate to the UE whether it should monitor paging in the cell (as described in the background section). In some embodiments, there is an explicit indication or flag which is used to indicate the UE can consider a frequency to be the highest priority frequency during cell reselection. In some embodiments, an explicit indication or flag is used to indicate a frequency cannot be considered to be the highest priority frequency by the UE during cell reselection. In another embodiment, absence of an indication or a flag is considered to be an indication that the UE can prioritize a particular frequency during the cell reselection.
[0061] In some embodiments, a flag, such as Ipwus-PrioritizationAllowed or Ipwus-PrioritizationNotAllowed, may be used for each inter-frequency in interFreqCarrierFreqList in SIB4 to indicate whether an LP-WUS UE supporting LP-WUS on that carrier / band is allowed to consider that frequency to have the highest priority while the UE is monitoring LP-WUS for paging. If the UE considers the LP-WUS frequency to have the highest priority, then the UE will initiate cell reselection to that frequency, i.e. the UE will try to find a suitable cell on that frequency.
[0062] In some embodiments, a flag, such as Ipwus-PrioritizationAllowed or Ipwus-PrioritizationNotAllowed, may be used in lpwus-Config-rl9 in SIB1 to indicate whether an LP-WUS UE is allowed to consider this frequency to have the highest priority to enable the UE to monitor LP-WUS, i.e. this flag confirms that the LP-WUS frequency is or is not congested and the UE may monitor LP-WUS on that frequency. For example, if the Ipwus-PrioritizationNotAllowed flag is set the UE is not allowed to consider the frequency to have the highest priority to monitor LP-WUS. If the UE initiated cell reselection as described above, then the UE will abort the cell reselection. If the LP-WUS UE is already camped on the frequency, and the Ipwus-PrioritizationNotAllowed flag is set, then normal cell re-selection rules apply to the UE, i.e. the LP-WUS UE will re-select from the frequency as soon as it finds a suitable cell on another higher priority frequency. This is illustrated in Figure 5 for the scenario in which the set Ipwus-PrioritizationNotAllowed flag is received by UE after the UE has initiated cell reselection as described above and, in response, aborts the cell reselection. As illustrated, the UE receives system information (e.g., SIB1 which contains cell selection information or SIB4 which contains cell reselection parameters) comprising a first indication (Ipwus-PrioritizationAllowed) on a first cell, where the first indication indicates that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring (step 500). The UE initiates a cell reselection to a cell on the certain frequency that is indicated by the first indication (Ipwus-PrioritizationAllowed) to be allowed to be prioritized for cell reselection for LP-WUS monitoring (step 502). While performing the cell reselection, the UE receives, on a second cell (i.e., a target cell for the cell reselection), system information (e.g., SIB1) comprising a second indication (Ipwus-PrioritizationNotAllowed flag which is set) that indicates that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring (step 504). The second indication indicates that the frequency is congested and the UE may not monitor LP-WUS on this frequency. In response to receiving the second indication, the UE aborts the cell reselection (step 506). Figure 6 illustrates the other scenario described above in which the set Ipwus-PrioritizationNotAllowed flag is received by the UE while the UE is already camped on the frequency. As illustrated in Figure 6, the UE receives a first indication (Ipwus-PrioritizationAllowed) on a first cell, where the first indication indicates that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring (step 600). The UE performs a cell reselection to a second cell on the certain frequency that is indicated by the first indication (Ipwus-PrioritizationAllowed) to be allowed to be prioritized for cell reselection for LP-WUS monitoring (step 602). Sometime after the cell reselection is complete (while the UE is camped on the second cell on the certain frequency and possibly performing LP-WUS monitoring on the second cell), the UE receives, on a cell on that frequency, system information comprising a second indication (Ipwus-PrioritizationNotAllowed flag which is set) that indicates that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring (step 604). The second indication indicates that the frequency is congested and the UE may not monitor LP-WUS on this frequency. In response to receiving the second indication, the UE may assume that the current frequency is no longer prioritized for cell reselection for LP-WUS monitoring, when performing cell reselection (step 606).
[0063] In some embodiments, the entry condition to monitor LP-WUS does not need to be met for the UE to consider the LP-WUS frequency the highest priority frequency. This allows an LP-WUS UE to camp on the LP-WUS frequency outside LP-WUS coverage, i.e. when the LP-WUS UE is roaming, it performs intra-frequency cell reselection on low band, i.e. inter-frequencycell reselection between load and midband is avoided. Inter-frequency cell reselection is more power consuming, and takes longer time (i.e. increased probability of missed paging).
[0064] In some embodiments, enabling or disabling the flags or indications related to prioritization (as described above) in the system information trigger the system information change procedure, and UEs are required to re-acquire all system information (this is existing behavior). Alternatively, a mechanism is specified wherein the UE does not need to use the existing procedure to acquire system information but is indicated which particular part of system information has changed directly. Furthermore, the UE could be directly informed if the prioritization status of a particular frequency is changed. For example, the UE is directly informed using the Short Message mechanism (3GPP TS 38.331 clause 6.5) to indicate the cell and / or frequency the UE currently camps on should not be used for prioritization due to congestion, effectively meaning the UE should reselect to some other cell and / or frequency. A reserved bit from the current Short Message mechanism can defined and specified to be used for this purpose.
[0065] In some embodiments, to reduce the paging load due to congestion status changes on the LP-WUS frequency, the UEs are not informed via Paging (Si-change) when the LP-WUS frequency becomes un-congested again, but Paging (Si-change) is only used when the LP-WUS frequency becomes congested. In the latter cases there is an urgency to inform the LP-WUS to disperse from the LP-WUS frequency. In the former case there is no such urgency, i.e. LP-WUS UEs can receive Paging without LP-WUS monitoring. When the UE reselects to a cell, or when the UE returns from connected mode, the UE is required to acquire MIB and SIB1 of the cell. In other words, due to mobility and traffic UEs will eventually learn about the changed status of Ipwus-PrioritizationNotAllowed in SIB1.
[0066] Figure 7 shows an example of a communication system 700 in accordance with some embodiments.
[0067] In the example, the communication system 700 includes a telecommunications network 702 that includes an access network 704, such as a radio access network (RAN), and a core network 706, which includes one or more core network nodes 708. The access network 704 includes one or more access network nodes or base stations of various types, access network nodes 710A and 710B are depicted (which may be collectively referred to as network nodes 710), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 704 may include more than one access network technology. The network nodes 710 of access network 704 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 712A,712B, 712C, and 712D (one or more of which may be generally referred to as UEs 712) to the core network 706 over one or more wireless connections.
[0068] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 702 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 702 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 702, including one or more access network nodes 710 and / or core network nodes 708.
[0069] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.
[0070] The network nodes 710 facilitate direct or indirect connection of one or more UEs 712 to the core network 706 over one or more wireless connections. 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 700 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 wirelessconnections. The communication system 700 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.
[0071] The UEs 712 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 710 and other communication devices. Similarly, the network nodes 708, 710 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 702) with the UEs 712 and / or with other network nodes or equipment in the telecommunications network 702 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 702. More specifically, UEs 712 may send messages, data, and / or other signals to network nodes 708, 710 or other elements of the telecommunications network 702 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 708, 710 may send messages, data, and other signals to UEs 712, other network nodes 708, 710, and other devices in telecommunications network 702 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 712 by transmitting the message to an access network node 710 that will then transmit the message to the intended UE 712. Similarly, a core network node 108 may receive a particular message from a UE 712 by receiving the message from an access network node 710 that itself received the message from the UE 712.
[0072] In the depicted example, the core network 706 connects elements of the access network 704 (e.g., one or more of the network nodes 710) to one or more host computing systems, such as host 716. 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 706 includes one or more core network nodes (e.g., core network node 708) of various types, one or more of which may be generally referred to as network nodes 708. Network nodes 708 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 708. Example core network nodes provide functions of one or more of a Mobile Switching 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).
[0073] The host 716 may be under the ownership or control of a service provider other than an operator or provider of the access network 704 and / or the telecommunications network 702. The host 716 may be operated by the service provider or on behalf of the service provider. The host 716 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.
[0074] As a whole, the communication system 700 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 700 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 (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 700 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 700 supporting different standards, protocols, or rule sets.
[0075] As one example, in certain embodiments, access network 704 may contain some access network nodes 710 that support 3 GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 710 support (or the same access network nodes 710 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 702 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations ormay include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.
[0076] Telecommunications network 702 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 702. For example, the telecommunications network 702 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) / Massive loT services to yet further UEs.
[0077] In some examples, one or more of the UEs 712 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 704 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 704. 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).
[0078] In the example, the hub 714 communicates with the access network 704 to facilitate indirect communication between one or more UEs (e.g., UE 712C and / or 712D) and network nodes (e.g., network node 710B). In some examples, the hub 714 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 714 may be a broadband router enabling access to the core network 706 for the UEs. As another example, the hub 714 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 710, or by executable code, script, process, or other instructions in the hub 714.
[0079] As another example, the hub 714 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 714 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 714 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 714 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 714 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.
[0080] The hub 714 may have a constant / persistent or intermittent connection to the network node 710B. The hub 714 may also allow for a different communication scheme and / or schedulebetween the hub 714 and UEs (e.g., UE 712C and / or 712D), and between the hub 714 and the core network 706. In other examples, the hub 714 is connected to the core network 706 and / or one or more UEs via a wired connection. Moreover, the hub 714 may be configured to connect to an M2M service provider over the access network 704 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 710 while still connected via the hub 714 via a wired or wireless connection. In some embodiments, the hub 714 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 710B. In other embodiments, the hub 714 may be a nondedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 710B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.
[0081] Figure 8 is another example of a communication system 800 according to some embodiments. As used herein, the communication system 800 includes multiple access points (APs) 810 (with four exemplary APs 810A, 810B, 810C, and 810D being depicted) and multiple wireless devices, referred to in the context of communication system 800 as stations (STAs) 812 (referred to individually as ST A 812A, ST A 812B, STA 812C, ST A 812D, and ST A 812E). ST A 812A is served by AP 810A in a first basic service set (BSS) 820A. STA 812B and STA 812C are served by AP 810B in a second BSS, BSS 820B. STA 812D is served by AP 810C in a third BSS, BSS 820C. STA 812E is served by AP 810D in a fourth BSS, BSS 820D. Stations 812 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 812 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.
[0082] Each of STAs 812 may connect through a radio link to one of APs 810. For example, depending on location or channel conditions experienced by a given STA 812, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.
[0083] Each AP 810 may provide data connectivity to STAs 812 connected to a particular AP 810. As illustrated, APs 810 may be connected to a data network 830. In this way, APs 810 mayalso provide data connectivity between STAs 812 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 812 and its serving AP 810 may be used for providing various kinds of services to STA 812, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 812 and / or on a device linked to STA 812. By way of example, Figure 8 illustrates an application service platform 832 provided in data network 830. The application(s) executed on STA 812 and / or on one or more other devices linked to STA 812 may use the radio link for data communication with one or more other STA 812 and / or the application service platform 832, thereby enabling utilization of the corresponding service(s) at STA 812.
[0084] Figure 9 shows a wireless device 900, which may be configured to operate in communication system 700 of Figure 7 or in communication system 800 of Figure 80. The wireless device 900 may be alternatively referred to as a UE 900, like a UE 712 within the context of communication system 700, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA 812 within the context of the communication system 800, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device 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, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of 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.
[0085] A wireless device 900 may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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, wireless device 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 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 sprinklercontroller). Alternatively, wireless device 900 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).
[0086] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 900. Further, certain embodiments of wireless devices 900 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0087] The processing circuitry 902 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 910. The processing circuitry 902 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), together with appropriate software; or any combination of the above. For example, the processing circuitry 902 may include multiple central processing units (CPUs).
[0088] In the example, the input / output interface 906 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 wireless device 900. 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 outputdevice 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.
[0089] In some embodiments, the power source 908 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 to supply power to circuitry or to charge an associated battery. The power source 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.
[0090] The memory 910 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 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.
[0091] The memory 910 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 hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as 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 910 may allow wireless device 900 to access instructions, 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 910, which may be or comprise a device-readable storage medium.
[0092] The processing circuitry 902 may be configured to communicate with an access network or other network via or using the communication interface 912. The communicationinterface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 wireless device or a network node in an access network). Each transceiver may include a transmitter 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
[0093] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), 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 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.
[0094] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. In particular embodiments, such 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).
[0095] As another example, wireless device 900 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, wireless device 900 may comprise a motor thatadjusts 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.
[0096] Wireless device 900, 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, 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 wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking 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. In particular embodiments, wireless device 900 represents an loT device that 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 example embodiment of wireless device 900 shown in Figure 9.
[0097] As yet another specific example, in an loT scenario, wireless device 900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 900 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, wireless device 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 may 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.
[0098] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 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 wireless device 900 can also include more than one of the functionalities described above. Forexample, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
[0099] Figure 10 shows a network node 1000 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 telecommunications network. In accordance with respective embodiments, network node 1000 may be configured to operate in communication system 700 of Figure 7, like network nodes 708 or 710, or in communication system 800 of Figure 8, like an AP 810 or a station 812. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).
[0100] Network nodes 1000 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. Network node 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) 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).
[0101] Other examples of network nodes 1000 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).
[0102] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 1000.
[0103] The network node 1000 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 1000 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), 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 1000.
[0104] The processing circuitry 1002 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 components, such as the memory 1004, to provide network node 1000 functionality.
[0105] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
[0106] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any othervolatile 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 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.
[0107] The communication interface 1006 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 1000 may be capable of wireless communication and communication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.
[0108] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
[0109] The antenna 1010 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through one or more interfaces or ports.
[0110] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 1000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.[OHl] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 1008. As a further example, the power source 1008 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.
[0112] Embodiments of the network node 1000 may include additional components beyond those shown in Figure 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
[0113] Figure 11 is a block diagram illustrating a virtualization environment 1100 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1100 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.
[0114] Applications 1102 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.
[0115] Hardware 1104 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1106 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 1108 A and VM 1108B (which may be collectively referred to as VMs 1108), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 1106 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 1108.
[0116] The VMs 1108 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 1106. Different embodiments of the instance of a virtual appliance 1102 may be implemented on one or more of VMs 1108, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physicalswitches, and physical storage, which can be located in data centers, and customer premise equipment.
[0117] In the context of NFV, each of the VMs 1108 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1108, and that part of hardware 1104 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 1108 on top of the hardware 1104 and corresponds to an application 1102.
[0118] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.
[0119] Figure 12 depicts a method in accordance with particular embodiments. For purposes of simplifying the discussion, the steps performed by a user equipment (noted with a “(UE)” following the reference number) and a network node (noted with a “(NN)” following the reference number) have been combined in the above flow chart. Thus, neither a user equipment nor a network node will perform all the steps of Figure 12. As depicted, the method begins at step 1210 where the network node transmits an indication regarding one or more frequencies used for LP-WUS. In some embodiments the network node may use the indication to manage congestion. For example, if a frequency is congested, the network node may indicate that the congested frequency is not to be prioritized for LP-WUS, or conversely if a frequency is under utilized, the indication may indicate to prioritize that frequency.
[0120] At step 1220, the UE receives the indication regarding LP-WUS monitoring. The indication may be transmitted by the network node and received by the UE via system information (e.g., SIB1 or SIEM). In some embodiments, the indication comprises an explicit indication thatthe one or more frequencies can be prioritized for LP-WUS monitoring or that one or more frequencies can not be prioritized for LP-WUS monitoring. These indications may be provided per frequency (e.g., for each frequency for which the UE supports LP-WUS). In some embodiments the indication comprises an Ipwus-PrioritizationAllowed or Ipwus-PrioritizationNotAllowed flag. The presence or the absence of such a flag may indicate whether or not certain frequencies can be prioritized for LP-WUS. In some embodiments the indication is received in interFreqCarrierFreqList or lpwus-Config-rl9. In some embodiments, the indication is received while re-acquiring all system information. For example, in a normal system information update message. In some embodiments the indication is received along with only those portions of the system information that have updated. For example, a Short Message may be used to inform the UE of only those aspects of the system information which have changed.
[0121] At step 1230 the UE enters a lower power mode (e.g., idle or inactive state).
[0122] At step 1240 the network node receives the indication the UE has entered a low power mode. The order of these two steps may be reversed. That is, the UE may send an indication that it is about to enter a particular lower power mode and then after the indication has been provided, the UE may entered the indicated lower power mode.
[0123] At step 1250 the UE monitors one or more frequencies for the LP-WUS. This may be based on information from the indication received at step 1220. The UE may be monitoring the LP-WUS for an indication that it should start monitoring for paging. As discussed above, paging uses more energy, so by waiting for a LP-WUS signal before monitoring for the regular paging the UE can save energy. In some embodiments, the monitoring of the LP-WUS may include camping on a LP-WUS frequency even though the UE is outside of a LP-WUS coverage area.
[0124] At step 1260 the network node transmits the LP-WUS. Receiving the LP-WUS may lead to the UE initiating a cell reselection process. In some embodiments / scenarios, the UE may abort a cell reselection process if it receives an indication (e.g., similar to step 1220) that the frequency it is using is not to be prioritized.
[0125] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information toinformation stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
[0126] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.
[0127] Some exemplary embodiments of the present disclosure are as follows:Group A Embodiments
[0128] Embodiment 1: A method performed by a wireless device for using a low power wakeup signal, the method comprising: receiving an indication regarding the use of one or more frequencies for low power wake-up signal (LP-WUS) monitoring; entering a lower power mode; and monitoring one or more frequencies for a LP-WUS based on the indication.
[0129] Embodiment 2: The method of 1 wherein the indication is received via system information.
[0130] Embodiment 3: The method of any of 1-2 wherein the indication comprises an explicit indication that the one or more frequencies can be prioritized for LP-WUS monitoring.
[0131] Embodiment 4: The method of any of 1-2 wherein the indication comprises an explicit indication that the one or more frequencies can not be prioritized for LP-WUS monitoring.
[0132] Embodiment 5: The method of any of 1-4 wherein monitoring one or more frequencies for a LP-WUS based on the indication comprises monitoring the one or more frequencies for an indication that the wireless device should start monitoring for paging.
[0133] Embodiment 6: The method of any of 1-5 wherein the indication comprises an Ipwus-PrioritizationAllowed or Ipwus-PrioritizationNotAllowed flag or the absence of such a flag.
[0134] Embodiment 7: The method of any of 1-6 wherein the indication is received via SIB1 or SIB4.
[0135] Embodiment 8: The method of any of 1-6 wherein the indication is received in interFreqCarrierFreqList or lpwus-Config-rl9.
[0136] Embodiment 9: The method of any of 1-8 wherein the indication is provided for each frequency on which the wireless device supports LP-WUS monitoring.
[0137] Embodiment 10: The method of any of 1-9 wherein the indication indicates that the frequency is or is not congested.
[0138] Embodiment 11: The method of any of 1-10 further comprising aborting a cell reselection process based on the indication.
[0139] Embodiment 12: The method of any of 1-11 further comprising camping on a LP-WUS frequency outside of a LP-WUS coverage area.
[0140] Embodiment 13: The method of any of 1-12 wherein the indication is received while re-acquiring all system information.
[0141] Embodiment 14: The method of any of 1-12 wherein the indication is received along with only those portions of the system information that have updated.
[0142] Embodiment 15: The method of 14 wherein the indication is received via Short Message.
[0143] Embodiment 16: The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.Group B Embodiments
[0144] Embodiment 17: A method performed by a network node for using a low power wake up signal, the method comprising: transmitting to a wireless device an indication regarding the use of one or more frequencies for low power wake-up signal (LP-WUS) monitoring.
[0145] Embodiment 18: The method of 17 wherein the indication is transmitted via system information.
[0146] Embodiment 19: The method of any of 17-18 wherein the indication comprises an explicit indication that the one or more frequencies can be prioritized for LP-WUS monitoring.
[0147] Embodiment 20: The method of any of 11-18 wherein the indication comprises an explicit indication that the one or more frequencies can not be prioritized for LP-WUS monitoring.
[0148] Embodiment 21: The method of any of 17-20 further comprising receiving an indication that the wireless device has entered a low power mode.
[0149] Embodiment 22: The method of any of 17-21 further comprising transmitting a LP-WUS.
[0150] Embodiment 23: The method of any of 17-22 wherein the indication comprises an Ipwus-PrioritizationAllowed or Ipwus-PrioritizationNotAllowed flag or the absence of such a flag.
[0151] Embodiment 24: The method of any of 17-23 wherein the indication is transmitted via SIB1 or SIB4.
[0152] Embodiment 25: The method of any of 17-23 wherein the indication is transmitted in interFreqCarrierFreqList or lpwus-Config-rl9.
[0153] Embodiment 26: The method of any of 17-25 wherein the indication is provided for each frequency on which the wireless device supports LP-WUS monitoring.
[0154] Embodiment 27: The method of any of 1-26 wherein the indication indicates that the frequency is or is not congested.
[0155] Embodiment 28: The method of any of 1-27 wherein the indication is transmitted along with other system information, including system information that has not changed.
[0156] Embodiment 29: The method of any of 1-27 wherein the indication is transmitted along with only those portions of the system information that have updated.
[0157] Embodiment 30: The method of 29 wherein the indication is transmitted via Short Message.
[0158] Embodiment 31 : The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.Group C Embodiments
[0159] Embodiment 32: A wireless device for using a low power wake up signal, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.
[0160] Embodiment 33: A network node for using a low power wake up signal, 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.
[0161] Embodiment 34: A wireless device for using a low power wake up signal, 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 of information 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; and a power source connected to the processing circuitry and configured to supply power to the UE.
Claims
CLAIMS1. A method performed by a wireless device for low power wakeup signal, LP-WUS, monitoring, the method comprising:receiving (500), on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring;initiating (502) a cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring;while performing the cell reselection to the second cell, receiving (504), on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring; andin response to receiving the second indication, aborting (506) the cell reselection.
2. The method of claim 1, wherein the system information comprising the first indication is either:a System Information Block 1, SIB1, or similar SIB containing cell selection information received on the first cell, ora System Information Block 4, SIB4, or similar SIB containing cell reselection parameters received on the first cell.
3. The method of claim 1 or 2, wherein the first indication is an explicit indication that the certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring.
4. The method of any of claims 1 to 3, wherein the system information comprising the second indication is a System Information Block 1, SIB1, or similar SIB containing cell selection information received on the second cell.
5. The method of any of claims 1 to 4, wherein the first indication is received in interfrequency carrier frequency list or a LP-WUS configuration information element.
6. The method of any of claims 1 to 5, wherein the second indication is received in an LP-WUS configuration information element.
7. The method of any of claims 1 to 6, wherein separate first indications are received for each frequency on which the wireless device supports LP-WUS monitoring.
8. The method of any of claims 1 to 7, wherein the first indication indicates that the certain frequency is not congested.
9. The method of any of claims 1 to 8, wherein the second indication indicates that the certain frequency is congested.
10. The method of any of claims 1 to 9, wherein receiving the system information comprising the first indication comprises re-acquiring all system information on the first cell.
11. The method of any of claims 1 to 10, wherein receiving the system information comprising the second indication comprises re-acquiring all system information on the second cell.
12. The method of any of claims 1 to 9, wherein receiving the system information comprising the first indication comprises receiving a portion of the system information that has been updated.
13. The method of any of claims 1 to 9, wherein receiving the system information comprising the second indication comprises receiving a portion of the system information that has been updated.
14. A wireless device (900) for low power wakeup signal, LP-WUS, monitoring, the wireless device (900) comprising:a communication interface (912) comprising a transmitter (918) and a receiver (920); and processing circuitry (902) associated with the communication interface (912), the processing circuitry (902) configured to cause the wireless device (900) to:receive (500), on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring;initiate (502) a cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP- WUS monitoring;while performing the cell reselection to the second cell, receive (504), on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring; andin response to receiving the second indication, abort (506) the cell reselection.
15. A method performed by a wireless device for low power wakeup signal, LP-WUS, monitoring, the method comprising:receiving (600), on a first cell, system information comprising a first indication that a certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring;performing (602) a first cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP-WUS monitoring;while camping on the second cell, receiving (604), on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring; andin response to receiving the second indication, performing (606) a second cell reselection to another frequency.
16. The method of claim 15, wherein the system information comprising the first indication is either:a System Information Block 1, SIB1, or similar SIB containing cell selection information received on the first cell, ora System Information Block 4, SIB4, or similar SIB containing cell reselection parameters received on the first cell.
17. The method of claim 15 or 16, wherein the first indication is an explicit indication that the certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring.
18. The method of any of claims 15 to 17, wherein the system information comprising the second indication is a System Information Block 1, SIB1, or similar SIB containing cell selection information received on the second cell.
19. A wireless device (900) for low power wakeup signal, LP-WUS, monitoring, the wireless device (900) comprising:a communication interface (912) comprising a transmitter (918) and a receiver (920); and processing circuitry (902) associated with the communication interface (912), the processing circuitry (902) configured to cause the wireless device (900) to:receive (600), on a first cell, system information comprising a first indication thata certain frequency is allowed to be prioritized for cell reselection for LP-WUS monitoring; perform (602) a first cell reselection to a second cell on the certain frequency that is indicated by the first indication to be allowed to be prioritized for cell reselection for LP- WUS monitoring;while camping on the second cell, receive (604), on the second cell, system information comprising a second indication that the certain frequency is not allowed to be prioritized for cell reselection for LP-WUS monitoring; andin response to receiving the second indication, perform (606) a second cell reselection to another frequency.
20. A method performed by a network node for enabling low power wake up signal, LP-WUS, monitoring, the method comprising:transmitting, on a cell that is on a certain frequency, system information comprising an indication that prioritization of the certain frequency for cell reselection for LP-WUS monitoring is not allowed.
21. A network node for enabling low power wake up signal, LP-WUS, monitoring, the network node comprising processing circuitry configured to cause the network node to:transmit, on a cell that is on a certain frequency, system information comprising an indication that prioritization of the certain frequency for cell reselection for LP-WUS monitoring is not allowed.
