User alerts for network coverage changes

By detecting network coverage changes in user equipment (UE) and configuring a warning mechanism, the problem of frequent inspection of monitors when users move between different network coverages is solved, improving user experience and reducing power consumption.

CN118923146APending Publication Date: 2024-11-08APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028726.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-28
Filing Date
2023-03-27
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

When users move between different types of network coverage, they often need to frequently turn on the monitor to check the network coverage type, which leads to inconvenience and may lead to power loss of user equipment (UE), especially in the case of long or frequent service-free or limited service. .

Method used

User Equipment (UE) detects network coverage changes, configures to respond to user events to alert users of network coverage changes, and performs autonomous operations when overlays are switched from one type to another, such as generating visual or audio warnings to prevent users from frequent Check the monitor.

Benefits of technology

Improve user experience, reduce power consumption of UE, and promptly notify users when network coverage changes, enhancing user experience in the absence of service or limited service.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923146A_ABST
    Figure CN118923146A_ABST
Patent Text Reader

Abstract

A user equipment (UE) configured to identify a user event when the UE is in a first type of network coverage, where the UE enables a feature configured to alert a user of a change in network coverage in response to the user event; identifying a network coverage change from the first type of network coverage to a second type of network coverage; and generating an alert in response to identifying the network coverage change, wherein the alert is configured to notify a user of the UE of the network coverage change.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Priority / Incorporated by Reference

[0002] This application claims priority to U.S. Provisional Application No. 63 / 269,990, filed on March 28, 2022, and entitled “User Alert for Change in Network Coverage,” which is incorporated herein by reference in its entirety. Background Art

[0003] User equipment (UE) can connect to a variety of different types of networks. Under conventional circumstances, a user may only be aware of a network coverage change if the user turns on the display of the UE to check for a visual indication of the type of available network coverage (e.g., no service, 5G, LTE, 3G, etc.). Not only is this inconvenient for the user when experiencing prolonged or frequent no service or limited service situations, but frequently turning on the display to check for desired network coverage may cause the UE to experience power loss. Summary of the invention

[0004] Some exemplary embodiments are directed to a method performed by a user equipment (UE). The method includes: identifying a user event when the UE is in a first type of network coverage, wherein the UE enables a feature configured to alert a user of a network coverage change in response to the user event; identifying a network coverage change from the first type of network coverage to a second type of network coverage; and generating an alert in response to identifying the network coverage change, wherein the alert is configured to notify a user of the UE of the network coverage change.

[0005] Other exemplary embodiments relate to a processor configured to: identify a user event when a UE is in a first type of network coverage, wherein the UE enables a feature configured to alert a user of a network coverage change in response to the user event; identify a network coverage change from the first type of network coverage to a second type of network coverage; and generate an alert in response to identifying the network coverage change, wherein the alert is configured to notify a user of the UE of the network coverage change. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0007] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0008] Figure 3 Methods for alerting users of changes in network coverage are shown according to various exemplary embodiments.

[0009] Figure 4Methods for generating notifications for service restoration according to various exemplary embodiments are shown.

[0010] Figure 5 Exemplary deployment scenarios according to various exemplary embodiments are shown.

[0011] Figure 6 Methods for generating notifications for emergency service restoration are shown according to various exemplary embodiments.

[0012] Figure 7 Exemplary deployment scenarios according to various exemplary embodiments are shown.

[0013] Figure 8 Methods for generating a notification of the availability of a preferred radio access technology (RAT) according to various exemplary embodiments are shown.

[0014] Fig. 9 Exemplary deployment scenarios according to various exemplary embodiments are shown. DETAILED DESCRIPTION

[0015] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments introduce techniques for improving user experience associated with scenarios where a user equipment (UE) moves between different types of network coverage.

[0016] The exemplary embodiments are described with reference to user equipment (UE). However, reference to UE is provided for illustrative purposes. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, UE described herein is used to represent any electronic component.

[0017] The exemplary embodiments are also described with reference to various types of radio access technologies (RATs). For example, reference may be made to fifth generation (5G) networks such as New Radio (NR), fourth generation (4G) networks such as Long Term Evolution (LTE), and traditional networks such as, but not limited to, third generation (3G) Wideband Code Division Multiple Access (WCDMA) networks and second generation (2G) Global System for Mobile Communications (GSM) networks. Throughout the specification, any reference to a particular RAT is provided for illustrative purposes only, and those skilled in the art will appreciate that the exemplary embodiments may apply to any suitable RAT.

[0018] The exemplary embodiments are further described with reference to a scenario where a UE moves between different types of network coverage. For example, at a first time, the UE may identify that one or more different types of networks are available. However, the available networks may not provide access to the services that the user intends to utilize. At a second time, the UE may move to a different location and then identify a new type of network coverage that is now available that can provide access to the services that the user intends to utilize.

[0019] Under conventional circumstances, when a UE moves to a new type of network coverage, the user may only be aware of the coverage change if the user turns on the display of the UE to check for a visual indication of the type of available network coverage (e.g., no service, 5G, LTE, 3G, etc.) This is not only inconvenient for the user, but frequently turning on the display to check for desired network coverage may cause the UE to experience power loss.

[0020] The exemplary embodiments introduce techniques for alerting users of changes in network coverage. These exemplary techniques can enhance the user experience associated with UEs that do not have service or have limited service by alerting users and / or autonomously performing operations when new types of network coverage become available. In some examples, the network coverage change can be described as a transition from no coverage to a specific RAT (e.g., 5G NR, LTE, traditional, etc.). In other examples, the coverage change can be described as a transition from no coverage to a type of public land mobile network (PLMN) (e.g., home PLMN (HPLMN), visited PLMN (VPLMN), etc.). In another example, the coverage change can be described as a transition from a first RAT to a second different RAT. Although the exemplary embodiments can provide benefits to these types of scenarios, the exemplary embodiments are not limited to any specific type of change in network coverage and / or available network services.

[0021] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for purposes of illustration, only an example with a single UE 110 is provided.

[0022] UE 110 may be configured to communicate with one or more networks. In the example of network arrangement 100, the networks with which UE 110 may wirelessly communicate are LTE radio access network (RAN) 120, traditional RAN 122, and 5G new radio (NR) RAN 124. However, UE 110 may also communicate with other types of networks, and UE 110 may also communicate with the network via a wired connection. With respect to the exemplary embodiment, UE 110 may establish a connection with LTE-RAN 120, traditional RAN 122, and / or 5G NR-RAN 124. Thus, UE 110 may have an LTE chipset for communicating with LTE-RAN 120, a traditional chipset for communicating with traditional RAN 122, and a 5G NR chipset for communicating with 5G NR-RAN 124.

[0023] In the network arrangement 100, reference to a single traditional RAN 122 is provided for illustration purposes only, and the term traditional RAN (or network) is applicable to various types of networks. For example, the traditional RAN 122 may represent a 3G WCDMA network or a 2G GSM network. Therefore, in an actual network arrangement, there may be multiple traditional RANs deployed near the UE 110.

[0024] The LTE-RAN 120, the legacy RAN 122, and the 5G NR RAN 124 may be parts of cellular networks that may be deployed by cellular providers such as Verizon, AT&T, T-Mobile, etc. These networks 120, 122, and 124 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets.

[0025] UE 110 may connect to LTE-RAN 120 via base station 120A. Those skilled in the art will appreciate that any relevant process may be performed for UE 110 to connect to LTE-RAN 120. For example, as discussed above, LTE-RAN 120 may be associated with a particular cellular provider, where UE 110 and / or its user has a contract and credential information (e.g., stored on a SIM card). Once the presence of LTE-RAN 120 is detected, UE 110 may send corresponding credential information to associate with LTE-RAN 120. More specifically, UE 110 may be associated with a particular base station (e.g., base station 120A of LTE-RAN 120). Similarly, UE 110 may also connect to traditional RAN 122 via base station 124A or to 5G NR RAN 124 via base station 122A.

[0026] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and traffic of a cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0027] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. Figure 1 100 is used to describe the UE 110. The UE 110 may represent any electronic device and may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 may include, for example, an audio input device, an audio output device, a battery providing a limited power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, a sensor for detecting the status of the UE 110, and the like.

[0028] Processor 205 may be configured to execute multiple engines of UE 110. For example, the engines may include coverage warning engine 235. Coverage warning engine 235 may perform various operations such as, but not limited to, detecting different types of network coverage, generating warnings to a user indicating changes in network coverage, and autonomously triggering operations (e.g., without user intervention) based on identifying changes in network coverage types.

[0029] The above-mentioned engine 235 is merely exemplary as an application (e.g., a program) executed by the processor 205. The functions associated with the engine may also be represented as an independent combined component of the UE 110, or may be a modular component coupled to the UE 110, for example, an integrated circuit with or without firmware. For example, an integrated circuit may include an input circuit for receiving a signal and a processing circuit for processing signals and other information. The engine may also be embodied as an application or an independent application. In addition, in some UEs, the functions described for the processor 205 are split between two or more processors such as a baseband processor and an application processor. The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0030] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables a user to input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the LTE-RAN 120, the traditional RAN 122, the 5GNRRAN 124, etc. Therefore, the transceiver 225 may operate on multiple different frequencies or channels (e.g., a continuous set of frequencies).

[0031] Figure 3 A method 300 for alerting a user to a change in network coverage is shown according to various exemplary embodiments. Figure 1 The network layout of 100 and Figure 2 The method 300 is described with reference to the UE 110 of FIG.

[0032] In 305, UE 110 identifies a first type of network coverage. For example, UE 110 may tune its transceiver 225 and scan various frequencies to find signals broadcast by base stations. UE 110 may receive signals indicating that a type of network coverage is available (e.g., synchronization signal blocks (SSBs), primary synchronization signals (PSSs), secondary synchronization signals (SSSs), physical broadcast channels (PBCHs), system information blocks (SIBs), layer 1 (L1) signals, layer 2 (L2) signals, layer 3 (L3) signals, etc.) from zero or more base stations. In addition, UE 110 may collect measurement data associated with base stations (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ), etc.). UE 110 may use information from these types of signals and / or measurement data to determine whether any base stations are available for UE 110. However, the manner in which UE 110 identifies that a particular network is available and collects measurement data is beyond the scope of the exemplary embodiment. The exemplary embodiment may identify that a particular network (or no network) is available in any suitable manner.

[0033] As will be referred to below Figures 4 to 9 As described in detail, in some examples, the first type of network coverage may be no coverage. In other examples, the first type of network coverage may be a PLMN and / or RAT that does not access a network service (e.g., a voice call, a data session, a specific application, etc.) that the user intends to utilize.

[0034] In 310, UE 110 receives an indication that a user wishes to be alerted when a second type of network coverage becomes available. The user may wish to be alerted about any of a variety of different types of network coverage. In other examples, the user may wish to be alerted when a specific PLMN, RAT, network slice, and / or protocol data unit (PDU) session that is expected to provide access to a network service that the user intends to utilize is available (e.g., a voice call, an emergency call, a data session, a specific application, etc.). UE 110 may be configured to generate an alert in response to any change in network coverage or only certain types of changes. The user may specify the type of change for which the user wishes to be alerted, or the type of change may be pre-configured at UE 110.

[0035] Exemplary embodiments are described with reference to "user events." As will be described in detail below, the term "user event" refers to an action, operation, or condition that is configured to trigger the alert functionality described herein. Thus, when a second type of network coverage becomes available, a user may indicate to UE 110 that the user wishes to receive an alert (e.g., 310 of method 300). Subsequently, when coverage changes, a user event may occur that triggers UE 110 to generate an alert. In some embodiments, when a user provides an indication to UE 110 that they wish to receive an alert about a change in network coverage, the user may specify the type of action, operation, and / or condition that is to trigger the alert functionality. In other embodiments, the indication provided by the user of a desire to receive an alert about a change in network coverage and a user event may be the same action, operation, or condition. Additional details regarding the scope of the term "user event" are provided below. The following reference is made to Figure 4 Method 400, Figure 6 Method 600 and Figure 8 Method 800 provides a specific example of a user event.

[0036] According to some exemplary embodiments, the user interface (UI) of UE 110 may be configured to display a notification requesting the user to select whether the user wants to enable triggering of warnings when network coverage changes. User input in response to the request may be considered a user event. This is an example of an action that may be considered a user event and an indication provided by the user that he or she wishes to be warned about a warning network coverage change. In another example, as an alternative to UE 110 displaying a notification, the user may manually configure settings to warn the user of network coverage changes and / or specify one or more different types of user events that may trigger warning functionality.

[0037] UE 110 may display a notification to the user in response to any of a variety of different predetermined conditions. For example, consider a scenario where UE 110 has no service and display device 215 of UE 110 is deactivated or dormant. Then, while UE 110 has no service, the user activates display device 215. In response to the user activating the screen, UE 110 may generate a notification requesting the user to indicate whether the user wants to enable triggering of a warning when second type network coverage becomes available.

[0038] To provide another example of the type of predetermined conditions that may trigger the above notification, consider a scenario where UE 110 has no service, has limited service, or is connected to a specific RAT. The user intends to utilize an application or a feature of an application that is not supported by the current RAT or service state. For example, the user may launch an application to perform a voice call. However, due to the current RAT, no service, or limited service state, UE 110 may not be able to establish and / or maintain a session for the voice call. In response to UE 110 being unable to establish or maintain a session for the voice call, UE 110 may automatically display a notification and request the user to select whether the user wants to enable triggering of a warning when a second type of network coverage becomes available. As will be described in detail below, as an alternative to triggering the above-mentioned notification, UE 110 may consider a user event that fails to establish and / or maintain a user-requested session, and automatically generate a warning when the second type of network coverage becomes available without any explicit indication from the user.

[0039] Under another exemplary predetermined condition, after UE 110 detects no service, limited service, RAT type, or PLMN type for a predetermined duration, UE 110 may be triggered to display a notification to the user. Under another exemplary predetermined condition, UE 110 may be triggered to display a notification to the user UE 110 based on UE 110 detecting no service, limited service, RAT type, or PLMN type (X) times within a time window (Y). Additional exemplary predetermined conditions for triggering a notification may include, but are not limited to: a user activating a lock screen a predetermined number of times when deployed within the first type of network coverage; a user unlocking UE 110 a predetermined number of times when deployed within the first type of network coverage; a user launching or opening an application of UE 110 a predetermined number of times when deployed within the first type of network coverage; a combination of any of these actions; or any other suitable indication that the user wants to utilize UE 110 but UE 110 may not be able to perform the desired function due to the first type of network coverage.

[0040] As an alternative or in addition to the above exemplary notification-based mechanism, UE 110 may be configured to automatically alert the user based on the occurrence of a user event when the second type of network coverage becomes available. The user may manually configure which types of actions, operations, and / or conditions will be considered user events, and / or UE 110 may be configured with one or more user events that trigger UE 110 to automatically generate an alert when the second type of network coverage becomes available without any explicit indication from the user.

[0041] As described above, in some examples, a user event may be a failure of UE 110 to maintain and / or establish a session. Thus, a user event may be an attempt by a user to utilize an application (e.g., a voice call, a data session, etc.) that is not supported by the current type of network coverage or an application that experiences a specific number of connectivity issues within a specific time window. In another example, a user event may be a user activating display device 215 and / or unlocking UE 110 a predetermined number of times within a predetermined time window. For example, if a user activates display device 215 (N) times within a time window (W) while UE 110 has no service or has limited service, UE 110 may be triggered to generate a warning to the user when network coverage changes. In another example, a user event may be a UE 110 detecting no service, limited service, RAT type, or PLMN type within a predetermined duration, and / or a UE 110 detecting no service, limited service, RAT type, or PLMN type (X) times within a time window (Y).

[0042] The above examples may allow UE 110 to warn the user of situations where UE 110 may frequently experience no service, limited service, one type of RAT or one type of PLMN, or experience less than satisfactory coverage of a particular type of network coverage for a longer period of time. However, the exemplary embodiments are not limited to the examples provided above. UE 110 may be configured to provide network coverage warnings based on user input, preconfigured settings, predetermined conditions, any combination thereof, or any other suitable type of trigger condition.

[0043] The exemplary embodiments are not limited to the examples provided above.UE 110 may be configured to provide network coverage warnings based on user input, preconfigured settings, predetermined conditions, any combination thereof, or any other suitable type of triggering condition.

[0044] In 315, UE 110 identifies a change in network coverage. For example, when UE 110 is deployed within a first type of network coverage, UE 110 may scan various frequencies to search for signals broadcast by base stations to which UE 110 is not currently connected. UE 110 may receive signals from one or more base stations indicating that a type of network coverage is available. In addition, UE 110 may also collect measurement data associated with the base stations. UE 110 may then utilize information from these types of signals and / or measurement data to determine whether any different types of networks are available. However, as described above, the manner in which UE 110 identifies that coverage is available and collects measurement data is beyond the scope of the exemplary embodiment. The exemplary embodiment may identify that the type of network coverage is available in any appropriate manner.

[0045] In some embodiments, the network coverage change may be a transition of UE 110 from no coverage to a certain coverage area of ​​a VPLMN that only allows UE 110 to make emergency calls. In other embodiments, the coverage change may be a transition of UE 110 from no coverage to a network that is expected to provide normal services to UE 110. In another embodiment, the coverage change may be a transition of UE 110 from one RAT to a certain coverage area of ​​a different RAT (e.g., from legacy to LTE or 5G, from LTE to 5G, etc.). In another embodiment, the change in network conditions may also mean the activation of a previously rejected PDU session, packet data network (PDN), or network slice. However, these examples are provided for illustrative purposes only, and the exemplary embodiments may be applicable to any type of change in network coverage experienced by UE 110.

[0046] In 320, UE 110 generates a warning to notify the user that a network coverage change has occurred. UE 110 can generate warnings in a variety of different ways. For example, UE 110 can generate a warning in the form of an audio output (e.g., a ringtone, a beep, a click, etc.). In another example, UE 110 can generate a warning in the form of a visual warning (e.g., a pop-up message, activating display device 215, a notification, etc.). For example, UE 110 can generate a notification on display device 215 to warn the user that a coverage change has occurred. In another example, UE 110 can generate a warning in the form of vibration. Therefore, UE 110 can vibrate as a way to warn the user when a coverage change has occurred. The exemplary embodiments are not limited to the examples provided above. UE 110 can be configured to provide a warning to the user using any combination of one or more examples provided above or in any other appropriate manner.

[0047] In some embodiments, as an alternative or in addition to alerting the user of a coverage change, UE 110 may be configured to autonomously perform a specific operation. The type of operation may be specified by a user input in response to a notification displayed on the UI of UE 110 or by a preconfigured setting. In addition, the type of operation performed by UE 110 in response to a coverage change may be based on one or more attempts to identify a second type of network coverage or to utilize an application or a feature of an application when UE 110 is deployed within the first type of network coverage. For example, UE 110 may be configured to autonomously initiate a voice call or send a message when UE 110 identifies that the second type of network coverage is available. In another example, UE 110 may be configured to autonomously launch an application when UE 110 identifies that the second type of network coverage is available. The type of operation triggered by UE 110 may be based on user input, preconfigured settings, attempts to utilize an application when UE 110 is deployed within the first type of network coverage, or any other appropriate basis.

[0048] Figure 4 A method 400 for generating a notification for service restoration according to various exemplary embodiments is shown. The method 400 provides an example of utilizing exemplary techniques within the context of a particular type of deployment scenario. As will be described in detail below, the method 400 is described with reference to a scenario in which a UE 110 travels through an area without network coverage and an area in which network coverage should allow the UE 110 to access services (e.g., voice calls, data sessions, etc.) that are normally expected to be available via a network connection.

[0049] Figure 5 An exemplary deployment scenario 500 according to various exemplary embodiments is shown. The deployment scenario 500 provides a context for the description of the method 400 provided below. In the deployment scenario 500, the first area 505 represents a geographical area in which there is no network coverage. The second area 510 represents a geographical area in which a network coverage type that allows UE 110 to access services that are usually expected to be available via a network connection (e.g., normal services, traditional RAN 122, LTE RAN 120, 5G NR RAN 124, etc.) is available. The deployment scenario 500 also includes a third area 515, which represents a geographical location in which a network coverage type that allows UE 110 to access services that are usually expected to be available via a network connection is available. This type of network coverage may be the same or different from the type of network coverage corresponding to the second area 510.

[0050] The deployment scenario 500 also includes a path 520 representing the path that the UE 110 travels. The path 520 includes a point 525 representing the point at which the user intends to make a voice call or initiate a data session. However, since the UE 110 has no service when it is deployed in the first area 505, the UE 110 cannot perform a voice call or establish a data session. Under normal circumstances, a user can enter and exit different types of network coverage 505-515 without knowing when the network coverage changes. Therefore, if the user is to check the display device 215 of the UE 110 when the UE 110 is deployed in the area 510 or 515, the user may only know the existence of the network that allows the UE 110 to access the network service that the user intends to utilize. The method 400 will be described with reference to the deployment scenario 500. However, the exemplary embodiment is not limited to this type of deployment scenario and is applicable to any scenario in which the UE 110 moves between different types of network coverage.

[0051] Returning to method 400, at 410, UE 110 identifies that there is no available network coverage. For example, UE 110 may tune its transceiver 225 to scan various frequencies and search for base stations. However, during the search, UE 110 may not receive any signals, or UE 110 may receive a signal from a base station but the measurement data associated with the signal (or base station) does not meet a threshold.

[0052] To provide an example, deployment scenario 500 may include path 520 representing a path that a user would take while hiking. Once the user enters first area 505, UE 110 identifies a first type of network coverage (e.g., no service, limited service, etc.). As described above, in deployment scenario 500, first area 505 is an area without network coverage.

[0053] At 420, a user event occurs. As described above, a user event may be an action, operation, and / or condition that enables triggering an alert when network coverage changes. For example, at point 525, a user may attempt to utilize an application while being deployed within the first area 505. The user may attempt to make a voice call, use a navigation application, post a photo to social media, or use any other type of application. However, since there is no network coverage in area 505, the user may not be able to utilize the application as they expected. Failure to establish and / or maintain a session for a desired application may be considered a user event that triggers UE 110 to generate an alert when a network coverage change occurs.

[0054] In another example, the user event may be a user input provided in response to requesting the user to select whether the user wishes to receive a notification of a warning about a change in network coverage. The notification may be triggered based on any appropriate type of predetermined condition. For example, at point 525, the user may attempt to make a voice call using an application while being deployed in the first area 505. Since there is no network coverage in the first area 505, the call is unsuccessful. This may trigger the UE 110 to generate a notification requesting the user to select whether the user wishes to receive a warning when there is a change in network coverage.

[0055] As described above, exemplary embodiments are not limited to these types of user events. In other examples, the user event may be a user activating a display and / or unlocking a lock screen a predetermined number of times when deployed within the first type of network coverage. Advantageously, the warning mechanism prevents the user from frequently turning on the display to check for desired coverage and thus prevents UE 110 from experiencing power consumption.

[0056] In 430, UE 110 identifies a network coverage change. For example, the user may move to point 530 within the second area 510 or point 535 within the third area 515. In 440, UE 110 generates a warning to notify the user of the network coverage change. For example, when the user enters the second area 510 or the third area 515, the user may be warned of the network coverage change. The warning may be provided in any of a variety of different ways. In one example, UE 110 may notify the user via an audio, visual, or vibration warning. In another example, UE 110 may warn the user and initiate a call or data session that previously failed when the user was deployed in the first area 505.

[0057] In some embodiments, UE 110 may notify the user when network coverage has not changed within a specific duration. The purpose of doing so is to prevent the user from frequently checking display device 215 to find an indication of a service change after the user indicates that the user wishes to receive an alert about a change in network coverage. For example, UE 110 may be configured to generate an alert when network coverage has not changed after the user is deployed in the first area 505 for (X) duration. The alert may be different from an alert indicating a change in network coverage. Those of ordinary skill in the art will appreciate that these methods of notifying the user are exemplary and other methods may be implemented.

[0058] Figure 6 A method 600 for generating a notification for emergency service restoration according to various exemplary embodiments is shown. The method 600 provides an example of utilizing exemplary techniques within the context of a particular type of deployment scenario. As will be described in detail below, the method 600 is described with reference to a scenario in which a UE 110 travels through an area with no network coverage, an area with VPLMN coverage that only allows the UE 110 to access emergency services, and an area with HPLMN coverage that allows the UE 110 to access services that are normally expected to be available via its HPLMN (e.g., voice calls, data sessions, etc.).

[0059] Figure 7An exemplary deployment scenario 700 according to various exemplary embodiments is shown. The deployment scenario 700 provides a context for the description of the method 600 provided below. In the deployment scenario 700, the first area 705 represents a geographical area in which there is no network coverage. The second area 710 represents a geographical area in which there is a VPLMN that only allows UE 110 to access emergency services. The deployment scenario 700 also includes a third area 715, which represents a geographical area in which there is a HPLMN that allows UE 110 to access services (e.g., voice calls, data sessions, etc.) that are usually expected to be available via its HPLMN. The deployment scenario 700 also includes a path 720 representing a path traveled by a user. The path 720 includes a point 725 representing a point at which the user intends to make an emergency call. However, since there is no service when UE 110 is deployed within the first area 705, UE 110 cannot perform an emergency call. The method 600 will be described with reference to the deployment scenario 700. However, the exemplary embodiments are not limited to this type of deployment scenario and are applicable to any scenario in which UE 110 moves between different types of network coverage.

[0060] Returning to method 600, at 610, UE 110 identifies that there is no network coverage. To provide an example, deployment scenario 700 may include a path 720 representing a path that a user would take while hiking. Once the user enters a first area 705, UE 110 identifies a first type of network coverage (e.g., no service, limited service, etc.). As described above, in deployment scenario 700, first area 705 is an area without network coverage.

[0061] In 620, a user event occurs. As described above, a user event may be an action, operation, and / or condition that enables triggering an alert when network coverage changes. For example, a user may attempt to make an emergency call. However, since there is no network coverage in area 705, UE 110 may not be able to make the emergency call. Therefore, failure to establish and / or maintain a session for an emergency call may be considered a user event that triggers UE 110 to generate an alert when a network coverage change occurs.

[0062] In another example, the user event can be a user input provided in response to requesting the user to select whether the user wishes to receive notifications of warnings about changes in network coverage. The notification can be triggered based on any appropriate type of predetermined condition (e.g., failure to establish and / or maintain a session for emergency calls).

[0063] In some scenarios, the user may activate the display and notice an icon indicating that the UE 110 currently has no service. This may prevent the user from attempting to make an emergency call (or utilizing another service that requires a network connection). Thus, in some embodiments, the user event may be that the user activates the display device 215 of the UE 110 and / or unlocks the lock screen a predetermined number of times when deployed within the first type of network coverage. In other embodiments, the user activating the display device 215 of the UE 110 and / or unlocking the lock screen a predetermined number of times when deployed within the first type of network coverage may trigger the UE 110 to display a notification requesting the user to select whether the user wishes to be warned when network coverage changes. If the user knows that the UE 110 will provide an audio or vibration warning when network coverage changes, the user may be prevented from frequently turning on the display to check the desired coverage and thus preventing the UE 110 from experiencing power consumption.

[0064] In 630, UE 110 identifies a change in network coverage. For example, the user may move to point 730 within second area 710. As described above, area 710 corresponds to a VPLMN in which UE 110 is only allowed to access emergency services.

[0065] In 640, UE 110 generates an alert to notify the user of the network coverage change. To provide an example, when the user enters the second area 710, the user may be alerted to the network coverage change. The alert may be provided in any of a variety of different ways. For example, UE 110 may notify the user via an audio, visual and / or vibration alert. In some embodiments, in response to the network coverage change, UE 110 may alert the user and initiate an emergency call that previously failed when the user was deployed in the first area 705.

[0066] Figure 8 A method 800 for generating a notification of the availability of a preferred RAT according to various exemplary embodiments is shown. The method 800 provides an example of utilizing exemplary techniques within the context of a particular type of deployment scenario. As will be described in detail below, the method 800 is described with reference to a scenario in which a UE 110 travels through an area with legacy RAT coverage (e.g., a 3G network, a 2G network, etc.), LTE RAT coverage, and 5G NR RAT coverage. Some applications or features of applications may only be supported by a particular type of RAT. Therefore, a user may intend to utilize an application or feature of an application that is not supported by the current RAT.

[0067] Fig. 9An exemplary deployment scenario 900 according to various exemplary embodiments is shown. The deployment scenario 900 provides context for the description of the method 800 provided below. In the deployment scenario 900, a first area 905 represents a geographic area in which there is legacy RAT coverage. However, the legacy RAT coverage does not support access to applications or features of applications that the user intends to utilize. A second area 910 represents a geographic area in which there is LTE RAT coverage that allows the UE 110 to utilize applications that are supported by the LTE RAT but not supported by the legacy RAT. The deployment scenario 900 also includes a third area 915, which represents a geographic area in which there is 5G NR RAT coverage that allows the UE 110 to access applications that are supported by the 5G RAT but not supported by the legacy RAT or 4G RAT.

[0068] Deployment scenario 900 also includes a path 920 representing a path traveled by a user. Path 920 includes points 925 representing points at which the user intends to use an application that is not supported by the legacy RAT. However, because UE 110 is deployed in first area 905, UE 110 cannot utilize the application as they intended. Method 800 will be described with reference to deployment scenario 900. However, exemplary embodiments are not limited to this type of deployment scenario and may be applicable to any scenario in which UE 110 moves between different types of RATs. For example, exemplary embodiments may be applicable to a scenario in which a user moves between LTE RAT coverage and 5G NR coverage.

[0069] Returning to method 800, in 810, UE 110 identifies a first type of RAT. To provide an example, deployment scenario 900 may include a path 920 representing a path that a user would take while hiking. Once the user enters first area 905, UE 110 identifies a legacy RAT. As described above, in deployment scenario 900, first area 905 is an area with legacy RAT coverage.

[0070] At 820, a user event occurs. As described above, a user event may be an action, operation, and / or condition that enables triggering an alert when network coverage changes. For example, at point 925, a user may attempt to utilize an application while deployed within a first area 905. However, the application may only be supported by RATs higher than the first type of RAT (e.g., LTE RAT, 5G NRRAT, etc.). Since the available RATs in area 905 are legacy RATs, UE 110 may not be able to establish a session type that would allow the user to utilize the preferred application as they intended. Therefore, failure to establish and / or maintain a session or access a particular network slice of an application may be considered a user event that triggers UE 110 to generate an alert when network coverage changes.

[0071] In another example, the user event may be a user input provided in response to requesting the user to select whether the user wishes to be notified of a warning about a change in network coverage. The notification may be triggered based on any appropriate type of predetermined condition (e.g., failure to establish and / or maintain a session for a particular application or feature of an application). For example, a user may attempt to utilize a preferred application supported by a RAT higher than the first type of RAT (e.g., 4G RAT, 5G RAT, etc.) within the first area 905. Because the RAT in the first area 905 is a legacy RAT, the UE 110 cannot establish a session and / or access the network slice required to utilize the desired application. This may trigger the UE 110 to generate a notification requesting the user to select whether the user wishes to be warned when a change in RAT occurs.

[0072] In 830, UE 110 identifies a RAT coverage change. For example, the user may move to point 930 within the second area 910 where there is LTE coverage or point 935 within the third area 915 where there is 5G NR coverage.

[0073] At 840, UE 110 generates an alert for the user based on identifying the coverage change. UE 110 may consider the type of RAT and the type of application that the user intends to utilize before generating the alert. For example, if UE 110 receives an indication that the user intends to utilize an application that prefers 5G NR RAT, UE 110 may not alert the user of the change in RAT if the RAT is LTE.

[0074] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0075] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.

[0076] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0077] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method performed by a user equipment (UE), the method comprising: identifying a user event when the UE is in a first type of network coverage, wherein the UE enables a feature configured to alert a user of a network coverage change in response to the user event; identifying the change in network coverage from the first type of network coverage to a second type of network coverage; as well as An alert is generated in response to identifying the network coverage change, wherein the alert is configured to notify a user of the UE of the network coverage change.

2. The method of claim 1, wherein the user event comprises a failure to establish or maintain a session for a voice call. 3 . The method of claim 2 , wherein the first type of network coverage is no network coverage, and the second type of network coverage includes a network providing voice call service. The method of claim 1 , wherein the user event comprises a failure to establish or maintain a session for an emergency call. 5 . The method of claim 4 , wherein the first type of network coverage is no network coverage, and the second type of network coverage allows the UE to access emergency services.

6. The method of claim 1, wherein the user event comprises a failure to establish or maintain a session for an application.

7. The method of claim 6, wherein the first type of network coverage is a legacy radio access technology (RAT), and the second type of network coverage is a long term evolution (LTE) RAT or a fifth generation (5G) new radio (NR) RAT. The method of claim 1 , wherein the alert comprises one of an audio output and a vibration.

9. The method according to claim 1, further comprising: In response to identifying the network coverage change, an operation is performed without user intervention, wherein the operation includes initiating one of a voice call, a data session, or an emergency call.

10. The method of claim 9, wherein the operation is pre-attempted prior to a change in the network coverage.

11. The method of claim 1, wherein the user event comprises activating a display of the UE or unlocking the UE a predetermined number of times when the UE is deployed within the first type of network coverage.

12. The method of claim 1, wherein the user event comprises receiving user input in response to a request for the user to enable the feature configured to alert the user to the change in network coverage, and Wherein in response to a predetermined condition, the request is displayed at the UE.

13. The method of claim 12, wherein the predetermined condition is based on one or more of: a type of network coverage that is unavailable, a duration for which the UE is deployed within the first type of network coverage, a number of times a display device of the UE is activated, a number of times the UE is unlocked, a failure to establish a communication session when deployed in the first type of network, or a number of times the UE identifies the first type of network coverage within a certain time window.

14. A processor of a user equipment (UE), the processor being configured to: identifying a user event when the UE is in a first type of network coverage, wherein the UE enables a feature configured to alert a user of a network coverage change in response to the user event; identifying the change in network coverage from the first type of network coverage to a second type of network coverage; as well as An alert is generated in response to identifying the network coverage change, wherein the alert is configured to notify a user of the UE of the network coverage change.

15. The processor of claim 14, wherein the user event comprises one of: a failure to establish or maintain a session for a voice call, a failure to establish or maintain a session for an emergency call, or a failure to establish or maintain a session for an application.

16. The processor of claim 14, wherein the processor is further configured to: In response to identifying the network coverage change, an operation is performed without user intervention, wherein the operation includes initiating one of a voice call, a data session, or an emergency call.

17. The processor of claim 16, wherein the operation is pre-attempted prior to a change in the network coverage.

18. The processor of claim 14, wherein the user event comprises activating a display of the UE or unlocking the UE a predetermined number of times when the UE is deployed within the first type of network coverage.

19. The processor of claim 14, wherein the user event comprises receiving a user input in response to a request for the user to enable the feature configured to alert the user to the change in network coverage, and Wherein in response to a predetermined condition, the request is displayed at the UE.

20. The processor of claim 19, wherein the predetermined condition is based on one or more of: a type of network coverage that is unavailable, a duration for which the UE is deployed within the first type of network coverage, a number of times a display device of the UE is activated, a number of times the UE is unlocked, a failure to establish a communication session when deployed in the first type of network, or a number of times the UE identifies the first type of network coverage within a certain time window.