[go: up one dir, main page]

WO2024254196A1 - Points de cheminement pour une dernière connectivité de réseau connue - Google Patents

Points de cheminement pour une dernière connectivité de réseau connue Download PDF

Info

Publication number
WO2024254196A1
WO2024254196A1 PCT/US2024/032631 US2024032631W WO2024254196A1 WO 2024254196 A1 WO2024254196 A1 WO 2024254196A1 US 2024032631 W US2024032631 W US 2024032631W WO 2024254196 A1 WO2024254196 A1 WO 2024254196A1
Authority
WO
WIPO (PCT)
Prior art keywords
location
mobile device
user
information
locations
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/032631
Other languages
English (en)
Inventor
Jared K. Mcgann
Stephen P. Jackson
Adam M. DRISCOLL
Alexandru Popovici
Nicholas D. FELTON
Todd R. GROOMS
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/733,658 external-priority patent/US20240405900A1/en
Application filed by Apple Inc filed Critical Apple Inc
Publication of WO2024254196A1 publication Critical patent/WO2024254196A1/fr
Anticipated expiration legal-status Critical
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/024—Guidance services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/63—Location-dependent; Proximity-dependent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/025—Services making use of location information using location based information parameters

Definitions

  • a system of one or more computers can be configured to perform particular operations or actions by virtue of having software, firmware, hardware, or a combination of them installed on the system that in operation causes or cause the system to perform the actions.
  • One or more computer programs can be configured to perform particular operations or actions by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
  • One general aspect includes a method performed by one or more processors of a first mobile device.
  • the method also includes monitoring a strength of a network wireless signal.
  • the method also includes storing a first previous location of the first mobile device at a first previous time when the strength of the network wireless signal was above a threshold.
  • the method also includes receiving a request to provide information about previous network connectivity of the first mobile device.
  • the method also includes responsive to the request, retrieving the first previous location.
  • the method also includes providing the first previous location to a user of the first mobile device.
  • Other embodiments of this aspect include corresponding computer systems, apparatus, and computer programs recorded on one or more computer storage devices, each configured to perform the actions of the methods.
  • Another general aspect includes a method performed by one or more processors of a first mobile device.
  • the method also includes receiving a target altitude.
  • the method also includes monitoring a current altitude of the first mobile device.
  • the method also includes providing a first notification when the current altitude matches the target altitude.
  • the method also includes disabling notifications after the first notification.
  • the method also includes continuing to monitor the current altitude of the first mobile device.
  • the method also includes enabling notifications when the current altitude differs from the target altitude by more than a threshold amount.
  • FIG. 1 is a block diagram of a network operating environment for electronic devices, according to an embodiment.
  • FIG. 2 is a block diagram for location services, according to an embodiment.
  • FIG. 3A-3B depict user interfaces for location services, in accordance with an embodiment.
  • FIG. 4 is a flow chart illustrating a location services approach, according to an embodiment.
  • FIG. 5 is a diagram illustrating waypoints for the last known network connectivity and backtracking, according to some embodiments.
  • FIG. 6 shows a diagram for providing location information about when a network signal was last available, according to some embodiments.
  • FIG. 7 is a flowchart illustrating a method for providing location information about when a network signal was last available, according to some embodiments.
  • FIG. 8 is a flowchart illustrating a method for providing location information with privacy safeguards, according to some embodiments.
  • FIGS. 9A-9Q illustrates exemplary user interfaces for transitioning among different views of indications of locations, in accordance with some embodiments.
  • FIG. 10 is a flow diagram illustrating methods of transitioning among different views of indications of locations, in accordance with some embodiments.
  • FIG. 11 illustrates a vertical geofence at a target altitude (elevation) and alerts when the target altitude is reached, according to some embodiments.
  • FIG. 12 illustrates the vertical geofence notifications when a user travels above and below a target altitude, according to some embodiments
  • FIG. 13 illustrates a mechanism to prevent unwanted notifications, according to some embodiments.
  • FIG. 14 illustrates a mechanism to prevent unwanted notifications using a vertical geofence signal, according to some embodiments
  • FIG. 15 shows the operation of a framework to track altitude and provide notifications, according to some embodiments.
  • FIG. 16 is a flowchart illustrating a method of triggering an alert at a target altitude, according to some embodiments.
  • FIG. 17 is a block diagram of an example device, which may be a mobile device, according to some embodiments.
  • a waypoint is an intermediate point or place on a route or on a path the user traveled that may be defined by a set of coordinates (e.g., latitude and longitude, a GPS point, etc.) to identify the point in physical space.
  • a navigation application may use the coordinates of the waypoint position to track and display distance and bearing information of the waypoint position as compared to a current position of the electronic device.
  • Bearing information provides a compass direction from an electronic device position to a waypoint position.
  • the bearing information is the horizontal angle between the waypoint position and a direction of travel of the electronic device, or the horizontal angle between the electronic device determined position and magnetic north or true north, depending on the implementation.
  • Relative bearing refers to the angle between the electronic device direction of travel and the location of waypoint position.
  • device context is a set of conditions that when met determine which location type (e.g., urban, or back country) a mobile device is in.
  • the location type can be determined using motion classification (e.g., driving, walking, stationary, etc.), wireless signals (e.g., Wi-Fi, cellular, Bluetooth, and the like) and how many, and a map tile category (e.g., whether tile is classified as urban or not). Data may be analyzed to determine if the device context exists to trigger a change in the location type.
  • Location services may request waypoint information including, but not limited to, positioning information, and bearing information (e.g., GPS data, GPS points, etc.) repeatedly over a period of time to assist with tracking and navigation to the waypoint position.
  • the electronic device may provide directions to a waypoint position, a trajectory of travel to the waypoint position, and a distance to the waypoint position.
  • the electronic device may repeatedly request positioning information for a current position of the electronic device while the user is in transit in order to continuously calculate the distance relative to the waypoint position.
  • bearing information may be calculated repeatedly with received positioning information.
  • two types of waypoint positions may be created: a cellular waypoint for tracking cellular connectivity and an SOS waypoint for tracking SOS connectivity.
  • the waypoint information may include times and/or locations when a mobile device (e.g., a wearable device such as a watch) or a companion device (e.g., a phone or a tablet paired with the device) last had a network signal, e.g., a cellular signal or other wide area network signal.
  • Signal reception can be tracked, e.g., using the same modules for providing signal strength to a display on the mobile device or the companion device.
  • the signal strength can be monitored and saved periodically, potentially only saving the times and/or locations when the signal strength fell below a threshold.
  • the signal strength can be saved as a bit flag indicating that the signal was above or below the threshold or saved a numerical value.
  • a time and a signal strength can be saved in a first table or database. For example, one or more times and/or locations when the mobile device last had a network signal above a threshold can be saved.
  • the locations of the mobile device can be saved separately (e.g., in a second table or database) from the time events for network signal strength (e.g., in a first table or database).
  • This location database can be saved in a secure storage that is accessible only by certain system routines, which can provide such information to a user only when certain criteria is met (e.g., location type is one where signal is likely to be lost, such as in a non-urban location state).
  • the times when the signal strength was last above a threshold can be used to retrieve the corresponding location from the second table that includes time as a field.
  • the location at the last available network wireless signal can be provided only when the device is classified to be in a non-urban location state (e.g., a rural state, a backcountry state, etc.).
  • a state also called a location type
  • motion classification e.g., driving, walking, stationary, etc.
  • wireless signals e.g., Wi-Fi, cellular, Bluetooth, and the like
  • a map tile category e.g., whether tile is classified as urban or not.
  • access to the location information may be restricted to a specific time that is determined to be still in a non-urban location state instead of all recorded history. In this manner, the information about the locations is only provided when needed, thereby reducing chances such location information could be misused.
  • the mobile device can retrieve one or more previous locations when the mobile device had an available signal (i.e., a signal was above a threshold). These locations can be displayed as waypoints on a device. Multiple locations can be retrieved, for example, in case it is easier or faster for the user of the mobile device to reach an earlier location with an available signal, as may occur when hiking.
  • the waypoints can be displayed with an icon or text indicating that the waypoint indicated a previous location having an available signal. In some embodiments, for privacy, the waypoints may be displayed in stages if the signal strength of a particular waypoint has changed when the mobile device reaches that particular waypoint.
  • more than one type of network signal can be monitored.
  • an out of network signal e.g., for any other carrier than the mobile device uses
  • a display of a waypoint (e.g., the available signal waypoint) can be provided in a compass application or a map application.
  • the previous locations that are saved in the second database can be used to provide a path for the user to backtrack to the last known location with a signal.
  • the current altitude of a mobile device may be monitored to trigger an alert (or notification) when the device reaches a target altitude.
  • a programmable threshold amount of altitude may be added around the monitored altitude to reduce unwanted notifications by enabling and disabling notifications at appropriate times.
  • the network wireless signals can be vital and potentially life-saving when the user of a mobile device is in a non-urban location (or backcountry) state.
  • the automatically generated cellular/SOS waypoints can also avoid distracting the user of the mobile device while hiking in difficult or unfamiliar terrain.
  • An electronic device e.g., a mobile device
  • location services such as location services
  • externally accessible services e.g., telephony service, storage service, and device locator service
  • network connection e.g., internet
  • FIG. 1 is a block diagram of a network operating environment 100 for electronic devices, according to an embodiment.
  • the network operating environment 100 includes electronic devices 102, such as a mobile device.
  • Mobile devices can be any electronic device 102 capable of communicating over a wireless network and/or a wireless accessory device.
  • Some examples of mobile devices include, but are not limited to, the following: a smartphone, a tablet computer, a notebook computer, a wearable device (e.g., smartwatch or other wearable computing accessory), a mobile media player, a personal digital assistant, AirPods®, EarPods®, PowerBeats®, AirTag®, locator tags, headphones, head mounted display, health equipment, speakers, and other similar devices.
  • an accessory device may be paired with electronic device 102.
  • accessory devices may be devices such as Apple AirPods®, EarPods®, PowerBeats®, exercise equipment, vehicles, bicycles, scooters, smart televisions, HomePod®, HomePod mini®, automated assistant devices, home security systems, and/or any other mobile accessory device.
  • Each of electronic devices 102 optionally can include a user interface, such as user interface 104 of electronic device 102. In other embodiments, an electronic device 102, may not have a user interface.
  • Electronic devices 102 may be a third-party device that utilizes an application programming interface to access device locator services. The third-party device may be provided by a different device manufacturer or be part of a different ecosystem (e.g., operating system) from electronic device 102.
  • Electronic device 102 can communicate over one or more wired and/or wireless networks 110 to perform data communication.
  • a wireless network 112 e.g., cellular network, Wi-Fi network
  • a wide area network 114 such as the Internet
  • an access device 118 such as a mobile hotspot wireless access device, can provide communication access to the wide area network 114.
  • the gateway 116 and access device 118 can then communicate with the wide area network 114 over a combination of wired and/or wireless networks.
  • both voice and data communications can be established over the wireless network 112 and/or the access device 118.
  • electronic device 102 can place and receive phone calls (e.g., using VoIP protocols), send and receive e-mail messages (e.g., using POP3 protocol), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network 112 (as shown with 120), gateway 116, and wide area network 114 (e.g., using TCP/IP or UDP protocols).
  • electronic device 102 can place and receive phone calls, send, and receive e- mail messages, and retrieve electronic documents over the access device 118 and the wide area network 114.
  • electronic device 102 can be physically connected to the access device 118 using one or more cables, for example, where the access device 118 is a personal computer. In this configuration, electronic device 102 can be referred to as a "tethered" device. In one embodiment, electronic device 102 can communicate with accessory devices via a wireless peer-to-peer connection. The wireless peer-to-peer connection (not shown) can be used to synchronize data between the devices.
  • Electronic device 102 can communicate with one or more services, such as a telephony service 130, a messaging service 140, a media service 150, a storage service 160, and a device locator service 170 over the one or more wired and/or wireless networks 110.
  • the telephony service 130 can enable telephonic communication between electronic devices or between an electronic device and a wired telephonic device.
  • the telephony service 130 can route voice over IP (VoIP) calls over the wide area network 114 or can access a cellular voice network (e.g., wireless network 112).
  • VoIP voice over IP
  • the messaging service 140 can, for example, provide e-mail and/or other messaging services.
  • the media service 150 can, for example, provide access to media files, such as song files, audio books, movie files, video clips, and other media data.
  • the storage service 160 can provide network storage capabilities to electronic device 102 to store documents and media files.
  • the device locator service 170 can enable a user to locate a lost or misplaced device that was, at least at some point, connected to the one or more wired and/or wireless networks 110.
  • Other services can also be provided, including a software update service to update operating system software or client software on the electronic devices.
  • the messaging service 140, media service 150, storage service 160, and device locator service 170 can each be associated with a cloud service provider, where the various services are facilitated via a cloud services account associated with the electronic devices 102.
  • Electronic device 102 may have applications, services, application programming interfaces, and functionality locally accessible on the devices including and/or utilizing location services 180.
  • Electronic devices 102 may offer one or more device locator applications 190 (e.g., a “Find my” application, a “Compass” application, a mapping application, etc.) to utilize device locator services 170 and location services 180 to locate accessory devices, provide a mapping application, and a navigation application.
  • the navigation application e.g., a “Compass” application to aid the user in navigating and backtracking to historical positions on their route.
  • the navigation application is an application that shows the cardinal directions used for navigation and geographic orientation using any number of methods including gyroscopes, magnetometers and/or positioning systems (e.g., GPS receivers).
  • the mapping application is an application that uses maps delivered by a geographic information system (GIS).
  • GIS geographic information system
  • the backtrack route may be the set of historical positions obtained over a window of time that allows the user to retrace their steps.
  • Locally accessible data may be stored on defined locations, such as known locations 182 and safe, trusted locations 184.
  • Machine learning algorithms 186 may be used to classify locations, infer relationships between a user and locations, provide path reconstruction and/or distance estimates in embodiments. In some embodiments, machine learning algorithms 186 may be used to provide an estimate for a distance with a set of features, including, but not limited to, intermittently received position fixes for a path and a straightness metric for a set of position fixes.
  • machine learning algorithms 186 may be used to identify known locations 182, and/or trusted locations 184.
  • cluster data analysis may be used to identify, classify, and provide semantic labels for locations, such as locations frequented by a user.
  • Safe, trusted locations 184 may be designated explicitly or confirmed as such by a user of the electronic device 102 after data analysis.
  • the known locations 182 or the trusted locations 184 may be classified offline and provided by device locator service 170 or a third-party (e.g., a database with map information).
  • cluster analysis is provided as an example of machine learning algorithms that may be used, those with skill in the art will recognize that other algorithms may be used to identify potential known or trusted locations.
  • On-device heuristics and/or machine learning models may be used to infer relationships between a user and locations based on analysis of the locally stored data on frequented locations including frequently visited locations by the user, known locations, and/or any other locations.
  • a frequently visited location such as a home, a vehicle, a workplace, any location frequented by a user with electronic device (e.g., accessory devices, and electronic device 102) and/or any other location designated as a trusted location 184 by the user.
  • Known locations 182 may be business locations, public spaces, parks, museums, and/or any other location that may be frequented by a user.
  • Defined locations may have associated fence information that provides a set of conditions, if detected, allow for designating or classifying an electronic device relative to a region of physical space for at least a portion of the defined location.
  • fence information may provide the conditions for classifying the electronic device as either inside or outside a region of physical space associated with the defined location.
  • fence information may provide the conditions for classifying the electronic device as transitioning between inside or outside the region of the defined location.
  • fence information may be a geofence with boundary information for the defined location, such as a point location and the extents of the region from the point location (e.g., a circular region defined with a radius from the point location, a polygon shape with distance measurements from the point location, etc.).
  • Fence information may include a set of sensor measurements received by electronic devices (e.g., fingerprint data including radio frequency (RF) scan data, such as Wi-Fi scan traces, etc.) that are characteristic of a particular region of the defined location.
  • Fence information for the respective defined locations may be stored along with classification type for the location and any semantic label assigned to the location.
  • Boundary information may include a defined set of boundaries or a radius distance around a point location to allow for creation of a fence for the location.
  • the fence is a virtual perimeter for a real-world geographic area.
  • GPS Global positioning system
  • Machine learning algorithms 186 may include on-device heuristics, machine learning algorithms, or a combination thereof to analyze and assign a label describing a user context, such as a location status.
  • the location status may be a label for a user context (e.g., set of conditions, a motion classification) in which specific positioning techniques and resources of the electronic device are used to obtain positioning information.
  • the location status may define a current location state and/or a prediction of a change in location state of a user while traveling with the electronic device.
  • the user context may indicate movement or travel of an electronic device to allow the electronic device to be designated as having a motion classification, such as “in transit,” “settled” in a particular defined location for a time period, or any other defined motion classification.
  • Analysis may be performed using a variety of signals from contextual user data sources available to the electronic device 102, including, but not limited to, the following: sensor data, positioning data, calendar data, transit card usage data, application data, historical data on patterns/routines of travel, wireless connection status with accessory devices and/or services (e.g., Bluetooth connection status), device location history, and/or any other data accessible to the electronic device 102.
  • the wireless connection status with various devices may indicate that the device is settled or “in transit.”
  • a loss of a connection to an appliance, a security system, a heating/cooling systems, vehicles, other modes of transport, and/or any other devices may indicate that the electronic device is “in transit.”
  • an electronic device 102 may be classified with a “settled” semantic label after remaining within the geographic boundaries that define a location (e.g., the trusted location 184) for a defined time period.
  • received positioning data for the electronic device 102 may indicate the electronic device 102 remained within the boundaries of a fence for a particular location for a duration of time (e.g., 5 minutes).
  • Sensor data such as accelerometer data, may indicate that the electronic device 102 is at rest to support an inference of being settled.
  • Application data may support the inference that the electronic device 102 is settled, such as the electronic device being located at a calendar appointment location.
  • Application data indicating a type of application in use may also provide an inference of the device being settled, such as using a media application.
  • Historical data for the user on routines or patterns in travel may be used to determine whether the electronic device 102 is settled, such as a bedtime routine at a home or a hotel location.
  • Electronic device 102 may be classified as having an “in transit” label based on prior detected behavior, patterns, or routines for the user, and analyzed on electronic device 102. For example, the user may have routine of going to work around the same time every day and an “in transit” state may be assigned if the data on the device supports that the pattern is being repeated. A speed at which the electronic device is moving or entering and exiting known geographic areas (e.g., using fences) may allow for the inferring that the electronic device 102 is in transit.
  • the electronic device 102 may be given the motion classification of “in transit.” Similarly, if transit applications/cards are used/in use, then the electronic device 102 may be designated as “in transit”.
  • Electronic device 102 may be classified as a “threshold distance,” “near an entry,” “near an exit,” “entry” and/or “exit” of a set of locations or a particular location based on crossing fence boundaries for the respective location or set of locations and/or detecting a pattern of sensor values that are characteristic of being in a location, such as Wi-Fi scan results characteristic of being inside a location or transitioning into a location.
  • FIG. 2 is a block diagram for location services, according to an embodiment.
  • Location services 180 may include an event monitor module 264 (e.g., a fence event monitor, location status monitor, sensor monitor, etc.) that may aid in determining when power and performance modes should be adjusted for determining positioning and/or bearing information.
  • Event monitor module 264 may rely on data from contextual user data sources to serve as cues for user context and event monitor module 264 may use heuristics and/or machine learning algorithms 186 to determine user contexts that trigger adjustment of modes.
  • user context and a location state may determine adjustments to power and performance modes executed on the electronic device 102.
  • the location state of the user of is either in a defined location or traveling between locations. By taking into consideration the location state of the user and user context (e.g., information from motion sensors, application data), positioning and/or bearing information may be provided in anticipation of the user needing the information.
  • the events monitor module 264 may use data to determine adjustments to modes that may impact power or performance for the operation of the electronic device 102.
  • the user context of the electronic device 102 may include a designation of “in transit” using a motion classifier 280 and wireless connection status data that a Bluetooth connection is lost between the electronic device 102 and an accessory device, such as a vehicle entertainment system.
  • the events monitor module 264 may determine from one or more contextual user data sources (e.g., motion classifier, wireless connection status) that there is at least one indication that there will be a change in location status and/or motion classification of the electronic device 102, such as the electronic device 102 may be “in transit to a defined location” because the user is “in transit” and lost the Bluetooth connection to the vehicle entertainment system, so the user may have exited the vehicle and is in transit to a location.
  • Crossing fence boundaries for one or more defined locations may indicate that the user intends to enter a defined location.
  • User contextual data such as crossing fence boundaries, exiting a vehicle, exiting a transit station, user routines, sensor data, application data, etc., may be analyzed to predict that the electronic device is a threshold distance from a defined location and that the mode for electronic device should be adjusted.
  • events monitor module 264 may detect from user contextual data that the user is in a remote location (e.g., wilderness), on an unfamiliar route, and/or unlikely to charge their device for an extended period of time.
  • a variety of signals from user contextual data may indicate that the user will be unlikely to charge their device, such as application data indicating a user tracking a workout, a maps application with a hiking path selected for display, a loss of cellular service, and/or any other data accessible on the device that provides context for activities of a user.
  • the user may select a mode that indicates the user will not be able to recharge the electronic device 102.
  • the visit monitor module 270 may utilize event monitor module 264, fence information 290, and entry detection module 266 to accurately detect entry to a defined location and reduce latency for provision of positioning information by predicting the user will request the positioning data.
  • the visit monitor module 270 may retrieve fence information 290 to define a more precise boundary for a defined location when the electronic device 102 is detected crossing a more coarse-grained geofence boundary, as detected using the entry detection module 266.
  • the visit monitor module 270 may retrieve expected sensor data (e.g., fingerprint data) characteristic of an electronic device 102 with the location status.
  • the proactive services 268 may be used to predict what applications and/or services that the user may want to access with a given user context, motion classification, and/or location status. For example, the user may want to access a particular application just prior to or upon entry to a location. Proactive services 268 may select applications based on user history of application selection or suggest a new application associated with a particular defined location.
  • the electronic device 102 may detect a set of conditions that allow for an inference that user may request a backtrack route to allow for retracing their steps and the electronic device 102 may initiate an extended power saving mode to obtain the positioning information so as not to affect the performance of the electronic device 102.
  • proactive service 268 may adjust a rate for periodic requests for determining positioning information.
  • a machine learning model 240 may be used to reconstruct a path from user accessible data and estimate a distance for the path taken by the user.
  • map data accessed by a mapping application 250 is used to estimate distances.
  • the mapping application is an application that uses maps delivered by a geographic information system (GIS).
  • GIS geographic information system
  • the navigation application 220 may provide heading or direction (e.g., degrees from magnetic north) information for the electronic device 102 that is collected as the user is traveling, and the heading data is averaged to eliminate errors in heading information collected due to variations in heading measurements collected due to movement of the device (e.g., jostling of device, swinging of hand if device worn on wrist of user, etc.) as the user travels along their trajectory.
  • Proactive services 268 and event monitor module 264 may use a motion classifier 280, density classifier 282, and a backtrack classifier 278.
  • a motion classifier 280 that has been trained on a feature set from data obtained using electronic device sensors may provide information on whether electronic device 102 is stationary or in transit with a user. While embodiments are not limited to a specific sensor type, specific sensor data representations, or specific features, exemplary sensors, and features are described herein that are capable of distinguishing between specific movements within the sensor data.
  • the motion classifier can analyze provided features from sensor data using one or more models that are trained to perform identification of motion type based on the supplied features.
  • the electronic device can receive motion classification from the electronic device or from a server indicating that the mobile device is traveling in a particular mode of transport.
  • the backtrack classifier 278 classifies obtained historical positions for the mobile device 102 as potentially part of a backtrack route for a user of the electronic device 102..
  • a density classifier 282 that has been trained on a feature set from data obtained using electronic device sensors may provide information on the density of structures and/or population for a given geographic area.
  • Features considered when classifying the geographic area include, but are not limited to, the following: wireless access point density, radio frequency signal (e.g., Bluetooth, UWB, etc.) density information, and/or map data on density and landscape to provide information on whether electronic device 102 is in a dense or a sparse geographic area.
  • Locations services in an electronic device may be accessible through a user interface that includes complications displaying information for corresponding applications.
  • complications e.g., corresponding to a navigation application
  • waypoints can be displayed as icons.
  • FIG. 3A depicts a user interface 201 for location services in accordance with an embodiment.
  • the user interface 104 depicted is a smart watch face with location services complications 203, 205, 207, and 209.
  • a “complication” is an object on a watch face that represents and displays information for an application and does not tell time, such as a date, weather information, atmospheric pressure, calendar information, a navigation application 220, a waypoint, etc.
  • a particular complication corresponds to a particular application (e.g., navigation application) that may be executed on the device displaying the watch face.
  • the complication can be displayed within a particular “style window” of a watch face.
  • a “style window” can correspond to a part of a watch face that is designated to display the complication.
  • a user can configure a watch face by determining which information (e.g., by selecting a watch application) is to be displayed in a particular style window.
  • the term “affordance” refers to a user-interactive graphical user interface object that can optionally be displayed on the display screen of electronic device 102. For example, an image (e.g., icon), a button, and text (e.g., hyperlink) can optionally each constitute an affordance.
  • the complications 203, 205, and 207 are deactivated and the corresponding application (e.g., navigation application 220 with waypoints) is not servicing requests for the deactivated complications on the electronic device 102.
  • the deactivated complications 203, 205, and 207 may be greyed out with a particular shading to indicate that the navigation application 220 is not servicing requests for the complication.
  • the complications 203, 205, and 207 represent navigation applications 220, and upon selection of the affordance corresponding to the respective complication, the bearing information is provided for a user selected waypoint position.
  • a dynamic waypoint complication the user may be presented with a dialog (e.g., user interface) to select a waypoint position for the complication to be displayed on the watch face upon activation.
  • the waypoint position may have already been assigned for the complication or the complication is predefined, and the navigation application 220 may provide bearing information for the respective waypoint.
  • a predefined or default complication may be for a car position and/or a home location.
  • a user may select waypoints for a campsite and/or a park that may have been defined when the user was hiking and the user may want to select the waypoints to find their way back.
  • complication 209 is activated and displays bearing information from true north for the electronic device 102 using the navigation application 220.
  • the complications can be activated by interacting with the affordance representing the complication. For example, if the user selects the affordance representing complication 203 for the “Park” waypoint FIG. 3A, then the navigation application 220 services requests for the waypoint information (e.g., direction to the “Park” waypoint 302 and distance to waypoint 304 in the activated complication 301) and the information is displayed in activated complication 301 in FIG. 3B corresponding to deactivated complication 203 in FIG. 3 A.
  • waypoint information e.g., direction to the “Park” waypoint 302 and distance to waypoint 304 in the activated complication 301
  • FIG. 3B depicts a user interface 300 for location services in accordance with an embodiment.
  • the user interface 104 depicts activated complications: 301 (corresponding to deactivated complication 203 in FIG. 3A), 304 (corresponding to deactivated complication 205 in FIG. 3A), 209, and 306 (corresponding to 207 in FIG. 3A).
  • icons for waypoints are predefined (e.g., a car icon for a parked car, a house icon for a user’s home or a campsite 306, a leaf icon for a park location 301, etc.) or assigned by the user (e.g., a sign with a particular color 304).
  • the navigation application 220 provides the bearing information by displaying marker 302 within the complication to represent how far to the right the waypoint position is for the “Park” waypoint 301 from the user’s current position.
  • the complications may be updated with information for requests at a first time period (e.g., every 15 minutes), but the frequency may decrease or increase based on the motion classification and/or mode of transport.
  • complications 304, 209, and 306 may be serviced by duty cycled requests operating at a first time period (e.g., every 15 minutes), and complication 301 may be serviced with requests that occur at a first time interval value (e.g., every 1 second) because the user is moving toward the waypoint.
  • a first time interval value e.g., every 1 second
  • the user interface for a targeted view of the waypoint may be provided, as shown in FIG. 4.
  • Embodiments provided herein describe obtaining positioning information from a global navigation satellite system (GNSS), such as a global positioning system (GPS), when one or more backtracking conditions are met.
  • GNSS global navigation satellite system
  • GPS global positioning system
  • One or more backtracking conditions are a set of conditions that allow for an inference that a user is on a route that is unfamiliar, in the wilderness, part of an exercise session, unable to recharge their device for an extended period of time, and/or engaging in any other activity that may require retracing the steps taken on the route.
  • a prediction is made that a user may need historical positioning information to be able to retrace their steps with the backtrack route and request the electronic device proactively obtain the historical positioning information.
  • the backtrack route may be the set of historical positions obtained over a lookback window of time that allows the user to retrace their steps.
  • the lookback window is the set of historical positions over an immediate period of time that are likely to be needed in order to retrace their steps while preserving the privacy of the user from a bad actor seeking more than the recent backtrack route.
  • the lookback window of positions returned upon request is adjusted (e.g., truncated, pruned, etc.) to provide positioning information only pertinent to the immediate need for the backtrack route.
  • non-stop or continuous collection of positioning information may drain resources (e.g., battery, processor usage, etc.) when a user is unable to recharge their device (such as while in the wilderness or lost), the electronic device may obtain position information in a power conserving extended mode when one or more backtrack conditions are met.
  • resources e.g., battery, processor usage, etc.
  • the one or more backtrack conditions may include, but are not limited to, the following: in transit (e.g., not stationary) motion classification, threshold period of time without network access, sparse (e.g., not densely populated or density of manmade structures in the area, etc.) environment classification, and threshold distance from a frequented location and/or location that is part of a user routine. While specific categories of conditions are provided, those with skill in the art will recognize that any other user contextual data may supplement and/or form the basis of an inference that the user will request historical positioning information for backtracking.
  • the one or more backtrack conditions detected are a subset of conditions that may be determined from analysis of accessible user contextual data as indicated in FIG. 3 with the extended mode.
  • the set of conditions for inferring that a user is lost prior to collection of historical positions and the subsequent review of conditions before responding to a request for historical positions may be practiced with any implementation for collection of historical positions.
  • the motion type classification condition is met if the electronic device 102 receives a motion classification of not stationary and/or is “in transit.”
  • the motion type classification condition is met if the mode of transport is a human-powered (e.g., on foot, a bicycle, a skateboard, etc.) or motor-assisted vehicle (e.g., a motor-assisted bicycle) and not a motorized vehicle or automotive vehicle (e.g., car, airplane, electric vehicle).
  • a motion classifier 280 that has been trained on a feature set from data obtained using electronic device sensors may provide information on whether electronic device 102 is stationary or in transit, including a mode of transport.
  • the motion classification may indicate an inference of the activity or mode of transport for the user while in transit, including, but not limited to, the following: walking, on a bicycle, on exercise equipment, on a scooter, on a skateboard, within a vehicle, on an airplane, on a transit vehicle, on a train, on a subway, human-powered vehicle, motor-assisted vehicle, electric-assisted vehicle, automotive vehicle, and/or any other motion classification.
  • the network access backtrack condition is met if the electronic device 102 is not in communication range to a wireless access point in a geographic area (e.g., internet access, WiFi, cellular network access points, etc.) or the geographic area has a relatively lower access point density as compared to a defined access point density threshold.
  • the electronic device 120 can, for example, conduct one or more wireless surveys to probe the geographic area for the presence of wireless access points while the device is in transit for a span of time. For example, the electronic device 120 can continuously, periodically, or intermittently search for wireless signals transmitted using one or more frequency bands designated for wireless communications. If the observed number of access points is lower than the defined access point density threshold for the span of time, then the network access backtrack condition is met.
  • the electronic device 102 determines if the type of environment backtrack condition is met based on a classification for the geographic area as having a sparse density of structures in the geographic area using the density classifier 282.
  • the density classifier 282 that has been trained on a feature set from data obtained using electronic device sensors may on wireless access point density, radio frequency signal (e.g., Bluetooth, UWB, etc.) density information, and map data on density and landscape to provide information on whether electronic device 102 is in a dense or a sparse geographic area.
  • the density of wireless access points in the region is a feature provided in the classification for the density of structures in the geographic area.
  • a map tile service can provide a tile-based mapping service to the electronic devices 102 that enables the electronic device 102 to retrieve map data and metadata for a geographic region of the electronic device 102 or a region that is being searched by the electronic device 102.
  • the map tile metadata can be retrieved from a remote map tile database or a local (e.g., cached) subset of the map tile database.
  • the metadata can include a classification of the current map tile or sub-tile.
  • the map tile metadata can also include digital elevation model (DEM) data that indicates a surface model including structures for the estimated geographic region and can be a feature for the density classifier 282.
  • DEM digital elevation model
  • the electronic device 102 is beyond a threshold distance from a frequented location, a location that is part of a user routine, a safe or trusted location, then the backtrack conditions met may be analyzed to determine if enough conditions are met to proceed with proactively obtaining historical positioning information.
  • the electronic device 102 receives at least one historical position from a set of historical positions for the lookback period of time (402). Although described with reference to classification of a single historical position, those with skill in the art will recognize that a plurality of historical positions may be classified to determine the lookback window of historical positions to include in the backtrack route.
  • the electronic devices may classify the at least one historical position as a candidate position for a backtrack route based on one or more features (e.g., signals) observed at the time of collection for the historical position (e.g., duration of lookback window, no location further than 250 km, no locations before in vehicle, etc.) (403).
  • features e.g., signals
  • duration of lookback window e.g., no location further than 250 km, no locations before in vehicle, etc.
  • features considered when classifying the historical position include, but are not limited to, the following: duration of time included in lookback window, distance from a frequented, safe, and/or trusted location, position information collected prior to and after entry of a motorized-vehicle (e.g., automobile, airplane, etc.) and/or electric-vehicle, density of structures classification (e.g., urban area, etc.), access point density, motion classification, mode of transport classification, user activity (e.g., hiking event from calendar data), and/or any other feature that may indicate a user may need a backtrack route.
  • a motorized-vehicle e.g., automobile, airplane, etc.
  • electric-vehicle e.g., a motorized-vehicle
  • density of structures classification e.g., urban area, etc.
  • access point density e.g., motion classification
  • mode of transport classification e.g., hiking event from calendar data
  • user activity e.g., hiking event from calendar
  • the most recent historical position considered as a lookback window candidate may not as far back in the past as a max duration from a current time.
  • historical positions that are greater than a max distance from a current position may be excluded from consideration as a candidate for the lookback window.
  • Position information acquired during a flight and/or other trip within a vehicle may be truncated from the lookback window and deemed not a candidate for the lookback window.
  • the historical positions not beyond a trusted threshold distance may be truncated from the lookback window.
  • An access point density and density of structures classification indication that the user may be in an urban location may allow for truncating the lookback window with associated positions.
  • the features described are examples and any number of the described features may or may not be used by the backtrack classifier 278 to determine the lookback window.
  • the electronic device 102 determines whether to provide the at least one historical position as part of the lookback window based on a classification (404).
  • the classification of historical positions in the lookback window begins from a prior classified historical position in the lookback window and the classification continues until a most recent candidate is identified.
  • the historical positions prior to the most recent classified candidate may be purged.
  • the application requesting access to the lookback window must possess an entitlement.
  • the entitlement may identify the application as having a right or a privileged to access positioning information. If the user requests via an application access to historical positioning information, then the lookback window positioning information may be provided opportunistically as opposed to requiring the user to request duplicate efforts to obtain historical positioning information.
  • Embodiments provided herein describe automatically generated waypoints for tracking the last known locations with wireless network signals.
  • the time and location information related to these waypoints may be stored in a secured storage/database with privacy safeguards.
  • a navigation application e.g., compass application or map application
  • a backtrack route to one or more of these waypoints can be displayed on the mobile device.
  • FIG. 5 is a diagram illustrating waypoints for the last known network connectivity and backtracking, according to some embodiments.
  • FIG. 5 shows an urban location 510 and a non- urban location 512.
  • An urban location may have many building structures, network wireless signals (e.g., cellular connection and Wi-Fi), and motion activities using motor-assisted vehicles.
  • a non-urban location may be in a remote area with few building structures, spotty network wireless signal, and human-powered activities (e.g., biking, running, hiking).
  • a user of a mobile device 530 may travel from the urban location 510 to the non-urban location 512 through a country road 514 with a few rest places (e.g., 520).
  • a few waypoints may be marked along the path that the user of the mobile device 530 travel.
  • waypoint Wl is just outside the urban location 510 and may have a cellular connection.
  • W2 is after a rest place 520, which has a Wi-Fi signal.
  • W3 and W4 are inside the non-urban location 512.
  • W2’ may or may not exist during a transition from an urban location to a non-urban location.
  • Waypoint W4 may be created if the user takes route B instead of route A. Further details about the waypoint creation are described below.
  • the techniques or embodiments disclosed in the present disclosure may allow the user to find a path to backtrack to a last known location (e.g., W3 or W4 of FIG. 5) with a network connection that has adequate network wireless signal (e.g., either a cellular internet connection or a SOS connection) for sending an emergency message or making an emergency call.
  • a network connection that has adequate network wireless signal (e.g., either a cellular internet connection or a SOS connection) for sending an emergency message or making an emergency call.
  • the user may launch an application, such as a compass application or a map application, on a user’s mobile device (e.g., a mobile phone, a watch, or a companion device).
  • the launched application may access a secured database (or storage) and determine whether the user has permission to access certain waypoint information (e.g., historical information related to time, locations, signal strength, signal type, etc.) based on the user’s status (e.g., a non- urban location state), and then display a backtrack path from the current location to a previous location (i.e., a waypoint) with adequate network wireless signal strength (e.g., above a threshold) for making the communication.
  • waypoint information e.g., historical information related to time, locations, signal strength, signal type, etc.
  • waypoints can be automatically created for tracking the last known locations with wireless network signals.
  • the techniques disclosed in the present disclosure can automatically create two types of system waypoints: a cellular waypoint for tracking cellular connectivity and an SOS waypoint for tracking SOS connectivity.
  • SOS is common name of the international Morse code distress signal.
  • a SOS connectivity may refer to a network wireless signal allowing a user to send an emergency message or make an emergency phone call.
  • the network wireless signal for SOS purposes may include, but is not limited to, an in-network signal provided by the user’s subscribed wireless carrier, an out-of-network signal provided by other wireless carriers, and a satellite signal. In some countries, for example, U.S., Canada, and Australia, a user can make a cross-carrier emergency call.
  • cellular connectivity typically refers to the in-network signal provided by the user’s subscribed wireless carrier.
  • a mobile device employing the disclosed techniques can track all types of network wireless signals, and automatically determine which type of waypoint to create, and create accordingly. For example, a cellular waypoint is automatically created when an in-network cellular signal goes below a threshold. An SOS waypoint is automatically created when out-of-network signals and/or a satellite signal drop below a threshold.
  • the signal reception, including its strength, of both types of network wireless signal (cellular and SOS) is continuously monitored and tracked.
  • the signal strength may be saved into a database in various representations, such as a bit flag indicating that the signal was above or below the threshold or a numerical value. For example, a signal strength may be saved as one, two, or three bars. In another example, the signal strength may be saved as numerical value, 1, 2, or 3.
  • the location services may create a waypoint (either a cellular waypoint or SOS waypoint), such as waypoints W1 to W4 of FIG. 5, on the path that the user travels.
  • a threshold e.g., two bars or value 2
  • the location services may create a waypoint (either a cellular waypoint or SOS waypoint), such as waypoints W1 to W4 of FIG. 5, on the path that the user travels.
  • the waypoint indicates that a cellular or SOS network wireless signal may be above the threshold for communication right before the marked location on the path.
  • a user of a mobile device may be hiking on a trail above a hill with a cellular connection.
  • the signal strength of the user’s in-network wireless signal drops below two bars, and the user’s mobile device may automatically generate a cellular waypoint (e.g., waypoint W3 of FIG.
  • information related to waypoints may be stored in a secured storage/ database with privacy safeguards.
  • time and location information may be stored separately, and a location state (e.g., urban, or non- urban) of the mobile device may be determined for information access and display purposes.
  • FIG. 6 shows a diagram 600 for providing location information about when a network signal was last available, according to an embodiment.
  • diagram 600 includes a secure storage 630, which further includes two tables or databases, a first table/database 632 and a second table/database 634.
  • the secure storage 630 may contain a single database partitioned into two securely isolated portions.
  • the secure storage (or database) 630 may be shared by multiple mobile devices. As shown in FIG. 6, two mobile devices, a first mobile device 610 (e.g., a wearable device) and a second mobile device 620 (e.g., a mobile phone), access the shared secure storage 630.
  • the first mobile device 610 may further include a location state classifier 612.
  • the location state classifier may classify the location state (e.g., urban location or non-urban location) of the first mobile device 610. Further details describing the classification process are described below.
  • the signal strength may be saved in the secure database (or storage) 630 shared between mobile devices of a user, such as mobile phone, watch, or other companion devices. These companion devices can communicate with each other locally, such as by using Bluetooth, even without a cellular signal or internet.
  • the shared storage can be synchronized between the companion devices, such that when one mobile device is unavailable, for example, due to lack of power, another mobile device can still access the shared storage.
  • the shared secure storage may also contain other waypoint information including, but not limited to, time, locations, signal strength, cellular state (e.g., connected, disconnected, roaming, airplane mode), motion classification (e.g., driving, running, walking, stationary, etc.), sequence or order of events (e.g., driving then walking, or in-network connection followed by out-of-network connection), network wireless signal type (e.g., cellular or SOS), map tile category, and altitude, although only signal strength and location information are shown in FIG. 6.
  • the waypoint information may be saved for a period of time (e.g., ranging from a week to a month) before new information can overwrite previously saved old information.
  • one of the mobile devices can store the waypoint information into and retrieve it from the shared storage while another can only store the waypoint information into the shared storage.
  • the first mobile device 610 may be a wearable device, such as a watch, and can store signal strength and location information into the shared storage 630, and retrieve the stored location information for location state classifier 612 to analyze and use.
  • the second mobile device 620 may be a mobile phone, a companion device of the first mobile device 610, can also store signal strength and location information into the shared storage 630, when the first mobile device 610 has a weak signal or lack power.
  • two tables can be used to store the signal strength (e.g., received signal strength indicator (RSSI)) and location separately.
  • RSSI received signal strength indicator
  • FIG. 6 when two tables are used, storing a previous location (e.g., a cellular waypoint or an SOS waypoint, such as W3 of FIG. 5) can include storing, in a first table 632, strength information of the network wireless signal at one or more times (depicted as time- RSSI), and include storing, in a second table 634, locations of the first mobile device at the one or more times (depicted as time-location).
  • the shared storage 630 may be synchronized between the first mobile device 610 (e.g., a watch) and the second mobile device 620 (e.g., a mobile phone) of a user.
  • access to the second table 634 of the secure storage 630 is accessible only by certain system routines, which can provide such information to a user only when certain criteria are met, for example, location type is one where the signal is likely to be lost, such as in a non-urban location state.
  • location type is one where the signal is likely to be lost, such as in a non-urban location state.
  • the location services may allow the compass application launched by the user to access the second table 634 for the location information, for example, using a timestamp to make an API request to retrieve location information from the second table.
  • the first mobile device 610 can use a location state classifier 612 of the location services to determine whether to provide a previous location (e.g., a cellular waypoint or an SOS waypoint) to the user.
  • location state classifier 612 can determine whether the first mobile device is within a non-urban location state.
  • the location information can only be exposed when it is likely needed; for example, the user needs to make an emergency call in an area where the signal is lost or sparse.
  • the previous location can be retrieved based on the location (e.g., W3 of FIG. 5) being a non- urban location state.
  • the location information is continuously and periodically tracked, but the access to the location information may be restricted.
  • the location services may place a limit (or threshold) on how far back in time the stored location information in the secured storage 630 can be accessed based on the historical information.
  • the access limit may be the earliest time when the mobile device is considered to be in a non-urban location state. For example, continuing with the above example, in FIG. 5, when the user of the mobile device 530 on the hiking trail 540 launches the compass application at 2:30 PM.
  • the location services may perform a check to determine whether the user is in a non-urban location state.
  • the location services additionally checked the logged historical information and found that the user was driving (e.g., 522) at 1:30 PM with a cellular connection before waypoint W2 of FIG.
  • the compass application may be allowed to access the second table 634 with location information for only up to 1 :30 PM (or up to waypoint W2 of FIG. 5) because driving is a motion state considered less likely to be in a non-urban location state.
  • the compass application may display a backtrack route to a waypoint position (e.g., a previous location associated with the most recent waypoint or closest waypoint) with a cellular connection (i.e., cellular waypoint) or SOS connection (SOS waypoint), but not the path beyond that waypoint position because the limited access to location information in the second table 634.
  • a waypoint position e.g., a previous location associated with the most recent waypoint or closest waypoint
  • a cellular connection i.e., cellular waypoint
  • SOS connection SOS waypoint
  • the location services ensure two things when the compass application requests database access: first, the user is in a non-urban location state, and second, the database access for location information is only available back in time to the point the user location state changed from urban to non-urban. In this manner, the information about the locations is only provided when needed and enough for use, thereby reducing the chances such location information could be misused.
  • all cellular/SOS waypoints within the non-urban location state may be displayed, but other waypoints during the transition between an urban location state and a non-urban location state are displayed in stages (i.e., staged display).
  • staged display i.e., staged display.
  • waypoints W4, W3, and W2’ if determined to be in the non-urban location state
  • Waypoint W2 is not displayed until the user of mobile device reaches W2’ waypoint position, and W2 is needed due to weak signals at W2’. Further details about the backtrack route display are described below.
  • Location state classification refers to determining a location category (e.g., urban, or non-urban) that a mobile device belongs to.
  • the location category may be used as part of the privacy safeguards discussed earlier.
  • determining a mobile device e.g., the first mobile device 610) is within a non-urban location state by the location state classifier 612 can use one or more of:
  • one or more motion states e.g., walking, running, biking, driving, stationary, etc.
  • a map tile may be generated by a tile-based mapping service that can retrieve map data and metadata for a geographic region around a mobile device based on GPS information.
  • the location state classifier 612 may determine the location state of the first mobile device, using network wireless signal, motion state, map tile, and a combination of one or more of these information.
  • location state determination as an example, the detection of a network wireless signal, such as a Wi-Fi connection (e.g., 520 of FIG. 5), may indicate that a mobile device is in an urban location state.
  • the location at waypoint W2’ may be determined to be in non-urban location state.
  • network wireless signals detected at the time or before the waypoint information is requested can help determine the location state of the mobile device.
  • a motion state or classification such as driving (e.g., 522 of FIG. 5) is more likely to be in an urban location state, while walking, biking, or running, is more likely to be in a non-urban location state.
  • the motion state shortly before the waypoint information is requested can help determine the location state of the mobile device because the user of the mobile device may stop its activity to make the request.
  • the classification of one or more map tiles within which the mobile device resided may indicate a non-urban location (e.g., 512) state because of no building structure (e.g., 504) in the geographic region covered by the map tile(s) or high altitude (e.g., 506).
  • a map tile may be generated by a tile-based mapping service.
  • a map tile can be a geographic region covering the mobile device, where the region may be a square with roughly five to ten miles in length for each side, or in other shapes (e.g. , rectangular, circle, hexagon, etc.).
  • the size of the geographic region may vary depending on the location state.
  • the size of geographic region may be smaller for an urban location, such as five mile in length, because more data, such as buildings, streets, highways, parks, etc. is associated with a tile.
  • the size may be larger for a non-urban location, such as 50 miles or more in length, if the landscape has little changes.
  • the map tiles may be cached in the secured storage/database for the mobile device at any time when network wireless signal and power are available for such service.
  • the map tile may also include altitude information.
  • the signal strength and motion state may be precomputed and incorporated into the tile-based mapping service to generate map tiles.
  • a backtrack route (or a path) from the current location (e.g., 540 of FIG. 5) of a mobile device to the latest (or the most recent or the last created) cellular/SOS waypoint (e.g., waypoint W3 for route A of FIG. 5) may be displayed on a requesting user’s mobile device (e.g., 610 of FIG. 6).
  • the most recent waypoint is also the nearest (or closest in distance) to the current location.
  • the more recent waypoint and the nearest waypoint may be different. For example, in FIG.
  • the nearest cellular waypoint and the most recent cellular waypoint are the same, which is waypoint W3.
  • the nearest cellular waypoint and the most recent cellular waypoint are the same, which is waypoint W3.
  • the nearest cellular waypoint and the most recent cellular waypoint can be different.
  • multiple waypoints e.g., both the nearest and most recent cellular waypoints
  • the backtrack routes may be displayed in three dimensions, including the elevation of the waypoint to indicate the terrain of the routes.
  • a set of previous locations (or waypoints) within the non-urban location state may be retrieved.
  • a path between a current location (e.g., 540 of FIG. 5) and the first cellular/SOS waypoint determined to be in the non-urban location state (e.g., assuming waypoint W2 is determined as a non-urban location) may be displayed.
  • the other waypoints e.g., waypoints W2’, W3 and W4 may be included in the displayed path.
  • a cellular/SOS waypoint can be displayed with an icon or text indicating that the waypoint was a previous location having an available network wireless signal. Other previous locations that are deemed urban location states, regardless of cellular connection, are not displayed.
  • a message can be sent.
  • the message can be an emergency message.
  • the emergency message can be an emergency phone call.
  • FIG. 7 is a flowchart illustrating a method 700 for providing location information about when a network signal was last available, according to some embodiments.
  • one or more method blocks of the method 700 may be performed by one or more processors of a first mobile device. Additionally, or alternatively, one or more method blocks of the method 700 may be performed by one or more components of a mobile device, such as processor 1918 of FIG. 19.
  • the first mobile device can be a wearable device (e.g., a watch).
  • a strength of a network wireless signal is monitored. Such monitoring can use the same modules that measure the strength for display on a screen.
  • FIG. 6 shows bars corresponding to network strength.
  • the signal strength can be monitored using signals received by the first mobile device 610, at the second mobile device 620, or both.
  • the strength of the network wireless signal can be monitored at a second mobile device that is in local communication with the first mobile device (e.g., paired via Bluetooth).
  • the network wireless signal can be for cellular connectivity or SOS connectivity.
  • the signal may be an in-network signal or an out-of-network signal (i.e., a different carrier than what the user of the first mobile device subscribes to).
  • the cellular connectivity and SOS connectivity may overlap if the in-network signal is available.
  • these two different signals can have locations that are provided with different icons or text to a user.
  • a first previous location of the first mobile device is stored at a first previous time when the strength of the network wireless signal was above a threshold.
  • the first previous location can be measured using GPS.
  • Storing the first previous location uses a shared storage /database (e.g., 630 of FIG. 6) between the first mobile device and the second mobile device.
  • the first previous time may be the first time that a cellular or SOS waypoint (or the first previous location) is created in a non-urban location state when the network wireless signal changes from above a threshold to below a threshold.
  • the first previous time and the first previous location may be the time and location a cellular/SOS waypoint (e.g., the most recent waypoint or the closest waypoint) is created in a non-urban location state.
  • the signal strength (RS SI) may be stored in a first table (e.g., 632 of FIG. 6) and location information may be stored in a second table (e.g., 634 of FIG. 6) for privacy purposes. Access to the location information in the second table may be permitted only when certain criteria are met, such as non-urban location state.
  • a request to provide information about the previous network connectivity of the first mobile device is received.
  • a user of a mobile device likes to make a communication (e.g., a phone call or text message) but no network wireless signal is available
  • the user may launch an application, such as a compass application or a map application, which automatically requests location services to obtain information about previous network connectivity, such as a cellular waypoint or an SOS waypoint.
  • the first previous location is retrieved responsive to the request.
  • the location services may access the secure storage 630 to retrieve signal strength information from the first table 632, and location information from the second table 634 upon determining, by the location state classifier 612, that the first mobile device is in a non-urban location state.
  • a set of previous locations in a non-urban location state between a current location of the first mobile device and the first previous location may be retrieved.
  • the first previous location is provided to a user of the first mobile device.
  • the compass application or map application may display a path (or backtrack route) from the current location to the first previous location .
  • a path from the current location (540) to the very first waypoint created (e.g., W2 of FIG. 5) in a non-urban location may be displayed along with other waypoints (e.g., W2’ and W3, and/or W4) in the path.
  • waypoints may be displayed in stages by displaying the latest (or the nearest) waypoint. Other waypoints created earlier than the latest waypoint may not be displayed unless needed. For example, in FIG. 5, if the user reaches the displayed waypoint (e.g., W3 of FIG. 5) but the signal strength at that waypoint has changed (e.g., weaker than previously observed), the location services may retrieve more location information from the secure storage 630 for the application to display next cellular or SOS waypoint (e.g., W2 or W2’ of FIG. 5) if the mobile device is still in non-urban location state.
  • the location services may retrieve more location information from the secure storage 630 for the application to display next cellular or SOS waypoint (e.g., W2 or W2’ of FIG. 5) if the mobile device is still in non-urban location state.
  • FIG. 8 is a flowchart illustrating a method 800 for providing location information with privacy safeguards, according to some embodiments.
  • FIG. 8 describes further details in block 740 of FIG. 7.
  • a non-urban location state may indicate that network wireless signals are more likely to be lost. Thus, a user of the first mobile device has the need to access the location information of the first mobile device.
  • a limitation is placed for accessing more location information that is beyond the first previous time and does not fall within the non-urban location state.
  • historical information e.g., location information
  • information about waypoint W1 may be restricted for access because its associated time is determined to be in an urban location state.
  • the processing proceeds to block 860.
  • access requests to the secured storage for information fall outside a non-urban location state may be denied, and the corresponding waypoints cannot be displayed either.
  • the location services may further request identification information (e.g., biometric data, password, etc.) from the requesting user for access to safeguard the privacy.
  • identification information e.g., biometric data, password, etc.
  • a prompt may be displayed on the mobile device asking whether the user likes to see the information. For example, when the user tries to make a phone call or send a text message but fails, a notification or prompt can also be displayed asking whether the user would like to find an available service (e.g., cellular waypoint). Once the user answers the prompt and requests the information, the backtrack route display process described above (e.g., FIG. 7) will follow.
  • the backtracking feature may automatically start and prompt the user at the appropriate time.
  • the backtracking feature may be started either manually or automatically. For example, if the user starts the backtracking feature manually before engaging in an activity, the backtracking feature may not stop unless the user stops it. However, if the backtracking feature starts automatically in a non-urban location as described above, the backtracking feature may end automatically if the user does not access the feature.
  • FIGS. 9A-9Q illustrate exemplary user interfaces for transitioning among different views of indications of locations, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 10.
  • Numeric direction indicator 912C indicates numeric degree to which device 2000 is pointing.
  • Location indicators 920A-920E each correspond to a different location (e.g., a historical location at which the user has placed a waypoint marker and/or a location of significance (e.g., last known cell service and/or where the user’s car is parked)).
  • location indicators 920A-920E are distributed around a circle, with each of their locations representing the direction in which a corresponding respective physical location (e.g., a campground, last known cell service location, and/or the user’s vehicle) is located.
  • hybrid view 912 provides the user with information about the direction of the various locations with respect to the current location of device 2000
  • hybrid view 912 does not provide information about the distances to the various locations and does not provide information about (absolute or relative) elevations of the various locations.
  • Current elevation option 930 indicates the current elevation of device 2000 in relation to sea level (e.g., 85 feet above sea level).
  • Backtrack affordance 2014 when activated, causes device 2000 to display information about a path that device 2000 traversed to arrive at the current location (e.g., as described in greater detail with respect to historic location indicator 2028, above).
  • New waypoint affordance 2058 when activated, initiates a process to add a new waypoint.
  • device 2000 detects tap input 950C on current elevation option 930 and, in response, device 2000 displays elevation view 916.
  • device 2000 detects rotation 950D (e.g., a clockwise rotation) of rotational element 2032 (e.g., a rotatable input mechanism and/or a crown).
  • rotational 950D e.g., a clockwise rotation
  • device 2000 transitions from displaying hybrid view 912 to displaying distance view 914, as shown in FIG. 9D.
  • distance view 914 provides the user with information about the distance and direction of the various locations represented by location indicators 920A-920E and the current location of device 2000.
  • the positions of location indicators 920A-920E do not indicate the elevations (e.g., with respect to sea level and/or in relation to the current elevation of device 2000) of the locations corresponding to location indicators 920A-920E.
  • device 2000 detects rotation 950E of rotational element 2032 (e.g., a rotatable input mechanism and/or a crown).
  • device 2000 transitions from displaying distance view 914 to displaying hybrid view 912, as shown in FIG. 9C.
  • device 2000 changes a scale (e.g., zooms out) of distance view 914.
  • device 2000 detects tap input 950F on current elevation option 930 and, in response, device 2000 transitions from displaying distance view 914 to displaying elevation view 916, as shown in FIG. 9G.
  • elevation view 916 is a simulated three- dimensional view and/or a perspective view that includes location indicators 920A-920E.
  • the positions of location indicators 920A-920E and current location indication 932 indicate the elevations (e.g., with respect to the lowest elevation among the locations and device 2000, with respect to sea level, and/or in relation to the current elevation of device 2000) of the locations corresponding to location indicators 920A-920E and the current location of device 2000.
  • the positions of location indicators 920A-920E indicate the directions and distances among the locations corresponding to location indicators 920A-920E and the directions and distances to the locations from the current location.
  • elevation view 916 provides the user with information about the distance, direction, and elevation of the various locations represented by location indicators 920A-920E and the current location of device 2000.
  • device 2000 in transitioning from distance view 914 to elevation view 916, displays an animation that tilts circle 934 into a perspective view to represent a base plane, as shown in FIGS. 9D-9G.
  • device 2000 in transitioning from distance view 914 to elevation view 916, displays an animation that raises respective indicators of locations (e.g., 920A and 920B) that are within an area defined by (between) 936 and optionally raises current location indicator 932, as shown in FIGS. 9D-9G.
  • the respective indicators of locations and current location indicator 932 are raised a respective amount that is based on an elevation of the respective locations corresponding to the indicators. For example, at FIG.
  • location indicator 920A and location indicator 920B have raised the same amount
  • location indicator 920A has ceased rising and location indicator 920B has raised up further, indicating that location indicator 920B corresponds to a location that is at a higher elevation than the location that corresponds to location indicator 920 A.
  • the various location indicators rise at the same level, but for different durations (and thus rise different distances) based on the respective elevations of the locations corresponding to the various location indicators.
  • 934 represents a base plane with an elevation that is based on (equal to) the lowest elevation from among the current location and the locations represented by location indicators that are contained within the area defined by (between) 936.
  • the elevation (e.g., relative to sea level and/or another elevation) of respective indications are represented by respective lines (e.g., vertical lines) that extend from base plane 934 and the length of the lines are in proportion to the elevations (e.g., relative elevations) of the locations corresponding to the respective indications.
  • device 2000 displays direction and distance information about the locations corresponding to location indicators 920C-920E, without raising location indicators 920C-920E to show corresponding elevation information (e.g., because location indicators 920C-920E are not within the area defined by 936).
  • device 2000 detects tap input 950G on current elevation option 930 and, in response, device 2000 transitions from displaying elevation view 916 to displaying distance view 914 (e.g., reverses the animation of FIGS. 9D-9G), as shown in FIG. 9D.
  • device 2000 detects rotation 950H and, in response, changes a scale (e.g., zooms in or out, based on direction of rotation) of elevation view 916.
  • changes a scale e.g., zooms in or out, based on direction of rotation
  • changing a scale of elevation view 916 causes additional location indicators to be displayed (e.g., within area defined by (between) 936) and/or causes some location indicators to no longer be displayed.
  • device 2000 detects rotation 9501 of device 2000, causing device 2000 to go from pointing to northwest to pointing to southeast.
  • device 2000 updates the positions of location indicators 920A-920E in elevation view 916, which moves location indicators 920A and 920B out of the area defined by 936 and brings location indicator 920D into the area defined by 936, as shown in FIG. 91.
  • device 2000 lowers location indicators 920A and 920B to base plane 934 and optionally raises location indication 920D above base plane 934 to represent the elevation of the location corresponding to location indication 920D, as shown in the animation at FIGS. 9G-9I.
  • Base plane 934 represents the lowest of elevations of the current location and the locations with indicators within the area defined by 936 (e.g., in FIG. 9H the elevation of base plane 934 correspond to the lower of the elevations of the current location of device 2000 and the elevation of the location corresponding to location indication 920D). Thus, in some embodiments, the elevation of base plane 934 changes when device 2000 rotates and/or when the scale of elevation view 916 changes.
  • device 2000 displays (for a predetermined amount of time) (on display 2001 adjacent to 920D) numeric indication 938 (e.g., “200 ft”) of the elevation (e.g., above sea level) of the location corresponding to location indicator 920D.
  • numeric indication 938 e.g., “200 ft”
  • device 2000 ceases to display numeric indication 938.
  • device 2000 detects tap input 950J on backtrack affordance 2014.
  • device 2000 displays path 940 that shows the path that device 2000 traveled to arrive at the current location. As shown in FIG.
  • location indicator 920D corresponds to a location at which cellular service was last available
  • device 2000 automatically added location indicator 920D corresponding to the location at which cellular service was last available as a waypoint, thereby allowing the user to backtrack to that location to make a call (e.g., an emergency call).
  • a call e.g., an emergency call
  • device 2000 detects tap input 950K on base plane 934 (and/or on a displayed location indicator (e.g., 920 A)) and, in response, displays waypoints menu 942, as shown in FIG. 9L.
  • waypoints menu 942 includes first option 942A that corresponds to waypoints (e.g., user selected and automatically added, such as last location of cellular service) and second option 942B that corresponds to nearby (e.g., within a threshold distance) points of interest.
  • first option 942A that corresponds to waypoints (e.g., user selected and automatically added, such as last location of cellular service)
  • second option 942B that corresponds to nearby (e.g., within a threshold distance) points of interest.
  • device 2000 detects tap input 950L on first option 942A and, in response, device 2000 displays (e.g., scrollable) list 944 of locations (waypoints) that correspond to location indicators 920A-920E.
  • list 944 includes items 944A-944E.
  • Device 2000 detects tap input 950M on item 944A and, in response, displays a targeted navigational interface 2094 for navigating to the location corresponding to item 944A, as shown in FIG. 9N.
  • device 2000 detects one or more inputs (e.g., including tap input 950N on information object 946) and, in response, displays option 948 for setting an elevation alert, as shown in FIG. 90.
  • device 2000 detects tap input 9500 on option 948, which displays elevation setting user interface 960.
  • device 2000 receives inputs 950P and 950Q to set a target elevation of 300 feet. Subsequently, device 2000 monitors the current elevation of device 2000.
  • device 2000 detects that device 2000 has reached (or crossed) the target elevation and, in response, outputs alert 962 indicating that the target elevation has been reached.
  • FIG. 10 is a flow diagram illustrating methods of transitioning among different views of indications of locations, in accordance with some embodiments.
  • Method 1000 is performed at a computer system (e.g., 1 lOOand/or 2000) (e.g., a smartwatch, a smartphone, a tablet, a laptop computer, and/or a head mounted device (e.g., a head mounted augmented reality and/or extended reality device)) that is in communication with a display generation component (e.g., 2001) (e.g., a display controller, a touch-sensitive display system, a monitor, and/or a head mounted display system) and one or more input devices (e.g., 2001 and/or 2032) (e.g., a touch- sensitive surface, a keyboard, a rotatable input mechanism, and/or a mouse).
  • a computer system e.g., 1 lOOand/or 2000
  • a smartwatch e.g., a smartphone, a tablet,
  • method 1000 provides an intuitive way for transitioning among different views of indications of locations. The method reduces the cognitive burden on a user that views indications of locations, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to view indications of locations faster and more efficiently conserves power and increases the time between battery charges.
  • the computer system displays (1002), via the display generation component (e.g., 2001), a first view (e.g., 914 at FIG. 9D) (e.g., a two-dimensional view) that concurrently includes one or more indications (e.g., 920A-920E at FIG. 9D) of one or more locations (e.g., indications of one or a plurality of historic locations that the computer system has been and/or indications of waypoints and/or a first indication for a first location and a second indication for a second location) and an indication (e.g., 932 at FIG. 9D) of a current location of the computer system.
  • a first view e.g., 914 at FIG. 9D
  • a two-dimensional view e.g., a two-dimensional view
  • one or more indications e.g., 920A-920E at FIG. 9D
  • locations e.g., indications of one or a plurality of historic locations that the computer system
  • the displayed relationships (1004) e.g., distances between and/or relative positions of in the first view (e.g., 914 at FIG. 9D) among the one or more indications (e.g., 920A-920E at FIG. 9D) of the one or more locations (e.g., a location of a parked car, a location of a trail head, and/or a location of a point of interest) and the indication (e.g., 932 at FIG.
  • 9D of the current location correspond to (e.g., are based on and/or are to scale with) distance relationships and relative position relationships (e.g., based on location data (e.g., geographic location data, either estimated (e.g., based on data from one sensor type (e.g., gyroscope or accelerometer sensors)) or actual (e.g., based a different sensor type (e.g., GPS sensor)))) among the one or more locations and the current location of the computer system (e.g., 2000) without the displayed relationships in the first view (e.g., 914 at FIG. 9D) corresponding to elevation relationships among the one or more locations and the current location of the computer system.
  • location data e.g., geographic location data, either estimated (e.g., based on data from one sensor type (e.g., gyroscope or accelerometer sensors)) or actual (e.g., based a different sensor type (e.g., GPS sensor))
  • the first view is a two-dimensional view that includes indications of various locations.
  • the indications are arranged to show the relative distances between the various locations and to show the relative positions of the various positions of the locations with respect to each other.
  • the indications are not arranged in a manner to reflect/disclose elevations of the various locations (e.g., absolute elevations or elevations relative to each other).
  • the computer system While displaying the first view (e.g., 914 at FIG. 9D), the computer system (e.g., 2000) detects (1006), via the one or more input devices, a first input (e.g., 950F and/or 950E). [0152] In response to detecting the first input (e.g., 950F and/or 950E), the computer system (e.g., 2000) transitions (1008) (e.g., FIGS. 9D-9G) from displaying the first view (e.g., 914 at FIG. 9D) to displaying, via the display generation component, a second view (e.g., 916 at FIG.
  • a first input e.g., 950F and/or 950E
  • the computer system transitions (1008) (e.g., FIGS. 9D-9G) from displaying the first view (e.g., 914 at FIG. 9D) to displaying, via the display generation component, a second view (e.g.
  • the one or more indications e.g., 920A-920E at FIG. 9G
  • the one or more locations e.g., indications of one or a plurality of historic locations that the computer system has been and/or indications of waypoints
  • the indication e.g., 932 at FIG. 9G
  • 9G of the current location correspond to (e.g., are based on and/or are to scale with) distance relationships, relative position relationships, and elevation relationships (e.g., based on location data (e.g., geographic location data, either estimated (e.g., based on data from one sensor type (e.g., gyroscope or accelerometer sensors)) or actual (e.g., based a different sensor type (e.g., GPS sensor)))) among the one or more locations and the current location of the computer system.
  • Displaying the second view that includes elevation relationships provides the user with visual feedback about the relative elevations among the various locations, thereby providing improved visual feedback.
  • transitioning from displaying the first view (e.g., 914 at FIG. 9D) to the second view (e.g., 916 at FIG. 9G) includes animating raising at least one of the one or more indications (e.g., 920A and 920B in FIGS. 9E-9G) of the one or more locations and the indication (e.g., 932 at FIGS.
  • the current location of the computer system e.g., raise a location indication 920A and/or the indication of the current location
  • a base plane e.g., 934
  • the one or more indication of the one or more locations and/or the indication of the current location are located on the base plane while in the first view.
  • the first view is a two-dimensional view and the second view is a three-dimensional view (e.g., a perspective view).
  • the indications of the various locations are displayed on a single plane and in the second view the indications of the various locations are displayed in different planes (e.g., the planes are based on the altitude of the respective locations).
  • the animation from the first view to the second view includes indications of various locations rising above the base plane to their respective planes (based on their altitude). Animating the indications rising to show respective elevations provides the user with visual feedback that the placement of the indications represent elevations, thereby providing improved visual feedback.
  • the base plane (e.g., 934) represents an elevation that is the lowest elevation of the one or more locations and the current location.
  • the base plane represents the elevation of the current location and the indication of the current location is represented on the base plane.
  • the base plane represents the elevation of the first location and the indication of the first location is represented on the base plane (and the location of the current location is represented to appear to be above the base plane).
  • the animation (e.g., at FIGS. 9D-9G) of raising a respective indication (e.g., 920A and/or 920B) (e.g., an indication of the one or more indications and/or the indication of the current location) includes raising the respective indication an amount that is based on a difference of the elevation of a location corresponding to the respective indication and the elevation represented by the base plane (e.g., 934). Raising the respective indications above the base plane provides the user with visual feedback about how much higher in elevation the respective corresponding locations are, thereby providing improved feedback.
  • a respective indication e.g., 920A and/or 920B
  • the respective indication includes raising the respective indication an amount that is based on a difference of the elevation of a location corresponding to the respective indication and the elevation represented by the base plane (e.g., 934). Raising the respective indications above the base plane provides the user with visual feedback about how much higher in elevation the respective corresponding locations are, thereby providing improved feedback.
  • the second view (e.g., 916 at FIG. 9G) includes, concurrently with the one or more indications (e.g., 920A-920B) of the one or more locations and the indication of the current location of the computer system, a plurality of other indications (e.g., 920C-920E) of a plurality of other locations.
  • the one or more indications e.g., 920A-920B
  • the indication of the current location of the computer system e.g., 920C-920E
  • the displayed relationships (e.g., distances between, relative positions of, and elevations) in the second view among the plurality of other indications (e.g., 920C-920E) of the plurality of other locations correspond to (e.g., are based on and/or are to scale with) distance relationships and relative position relationships without the displayed relationships in the second view corresponding to elevation relationships among the plurality of other indications.
  • the second view includes indications of a plurality of other locations that show the distance and relative positions of the other locations, but that does not show the relative elevations of the plurality of locations. Showing distance and direction relationship information for some points without showing the elevation relationship for those points helps to not clutter the user interface, thereby enabling the user to better recognize the elevation differences of the points that are of interest, thus providing improved visual feedback.
  • computer system detects (e.g., via a magnetometer) a rotation (e.g., 9501) of the computer system (e.g., detecting that the computer system has rotated with respect to North).
  • a rotation e.g., 9501
  • the computer system raises (by animating an update of the second view) a first respective indication (e.g., 920D at FIGS.
  • a direction indicator is displayed that overlaps a portion of the base plane, and indications that are within the direction indicator are raised to show their altitude while indications that are not within the direction indicator are displayed on the base plane (not showing their altitude).
  • the raising of indications coming into the direction indicator and the lowering of indications leaving the direction indictor happens concurrently. Rotating the device to show the elevation for some indications allows the user to specify for which points the elevations should be displayed, thereby providing the user with more control and improved feedback.
  • the computer system in response to detecting the rotation (e.g., 9501) of the computer system (e.g., 2000), the computer system displays, via the display generation component (e.g., adjacent to the second respective indication) for an amount (e.g., a predefined amount) of time (e.g., before ceasing to display without requiring additional user input), a textual representation (e.g., 938 at FIG. 91) of an altitude (e.g., an absolute amount, 300 feet, 350 feet, or 654 feet above sea level) of the first respective location.
  • the computer system temporarily shows textual elevations next to points that come within the direction indicator (e.g., that raise up). Temporarily showing textual elevation information next to indications provides the user with precise feedback about the elevation (e.g., above sea level) for the corresponding location, thereby providing improved visual feedback.
  • the computer system displays, via the display generation component (e.g., 2001) and concurrently with the first view (e.g., 912 at FIG. 9C), a textual representation (e.g., 930) of a current elevation (e.g., 65 feet, 102 feet, or 322 feet above sea level) of the computer system.
  • a current elevation e.g., 65 feet, 102 feet, or 322 feet above sea level
  • the elevations of the one or more locations is not displayed in the first view. Displaying text of the current elevation of the computer system provides the user with precise feedback about the device’s current elevation, thereby providing improved feedback.
  • the computer system while displaying the second view (e.g., 916 at FIG. 9G), the computer system (e.g., 2000) detects, via the one or more input devices, a second input (e.g., 950G) (e.g., a tap input on a textual representation of the current elevation of the computer system).
  • a second input e.g., 950G
  • the computer system transitions (e.g., including an animation) from the second view (e.g., 916 at FIG. 9G) to the first view (e.g., 914 at FIG. 9D). Displaying the first view that does not include elevation relationships provides the user with a simplified view about the distances and positions of the various locations, thereby providing improved visual feedback.
  • the computer system prior to displaying the first view (e.g., 914 at FIG. 9D), displays, via the display generation component, a third view (e.g., 912 at FIG. 9C) (e.g., a two-dimensional view) that concurrently includes the one or more indications of the one or more locations (e.g., indications of one or a plurality of historic locations that the computer system has been and/or indications of waypoints and/or a first indication for a first location and a second indication for a second location) and the indication of the current location of the computer system.
  • a third view e.g., 912 at FIG. 9C
  • the computer system displays, via the display generation component, a third view (e.g., 912 at FIG. 9C) (e.g., a two-dimensional view) that concurrently includes the one or more indications of the one or more locations (e.g., indications of one or a plurality of historic locations that the computer system has been and/or indication
  • the displayed relationships (e.g., distances between and/or relative positions of) in the third view among the one or more indications (e.g., 920A- 920E) of the one or more locations and the indication of the current location correspond to (e.g., are based on and/or are to scale with) relative position relationships (e.g., based on location data (e.g., geographic location data, either estimated (e.g., based on data from one sensor type (e.g., gyroscope or accelerometer sensors)) or actual (e.g., based a different sensor type (e.g., GPS sensor)))) among the one or more locations and the current location of the computer system without the displayed relationships in the first view corresponding to distance relationships and elevation relationships among the one or more locations and the current location of the computer system.
  • location data e.g., geographic location data, either estimated (e.g., based on data from one sensor type (e.g., gyroscope or accelerometer sensors)
  • the third view is a two-dimensional view that includes indications of various locations.
  • the indications are arranged to show the relative positions of the various positions of the locations with respect to each other.
  • the indications are not arranged in a manner to reflect/disclose distances and/or elevations (e.g., absolute elevations or elevations relative to each other) among the various locations.
  • the computer system receives a user input (e.g., a tap input on a textual representation of the current elevation of the computer system) and, in response transitions from the third view to the first view. Displaying the first view that does not include elevation relationships and distance relationships provides the user with a simplified view about the positions of the various locations, thereby providing improved visual feedback.
  • the computer system prior to displaying the third view (e.g., 912), displays, via the display generation component, a fourth view (e.g., 910) (e.g., a two-dimensional view) that includes a current bearing (e.g., 910A) of the computer system (e.g., 2000) and that does not include the one or more indications of the one or more locations (e.g., indications of one or a plurality of historic locations that the computer system has been and/or indications of waypoints and/or a first indication for a first location and a second indication for a second location).
  • a fourth view e.g., 910
  • a current bearing e.g., 910A
  • the computer system e.g., 2000
  • the one or more indications of the one or more locations e.g., indications of one or a plurality of historic locations that the computer system has been and/or indications of waypoints and/or a first indication for a first location and
  • the fourth view does not include direction/distance/elevation relationships among the various points/locations.
  • the computer system receives a user input (e.g., a tap input on a textual representation of the current elevation of the computer system and/or rotation of a rotatable input mechanism) and, in response transitions from the fourth view to the third view. Showing the current bearing without showing any relationships to the various locations provides the user with a simplified view about the bearing of the computer system, thereby providing improved visual feedback.
  • the computer system while displaying the second view (e.g., 916 at FIG. 9K), the computer system (e.g., 2000) detects, via the one or more input devices, a set of one or more inputs that includes an input (e.g., 950K, 950L, and/or 950M) directed to (e.g., a tap input on) a respective indication that corresponds to a respective location.
  • the computer system e.g., 2000
  • the computer system detects a tap input on the respective indication and, in response, displays a list that corresponds to the one or more indications. In response to detecting a tap input on a respective item in the list that corresponds to the respective location, the computer system displays the textual distance and textual elevation. Enabling the user to select a specific location to see additional details about the location provides the user with additional feedback about that location, thereby providing improved feedback.
  • the computer system receives user input (e.g., 9500, 950P, and/or 950Q) selecting a target elevation (e.g., as in FIG. 9P).
  • the computer system detects that the computer system has reached the target elevation (e.g., the user wearing the computer system has hiked down or hiked up to the target elevation).
  • the computer system e.g., 2000
  • outputs e.g., audio, visual, and/or tactile
  • an alert e.g., 960 at FIG. 9P
  • the computer system while displaying the second view (e.g., 916 at FIG. 9K), the computer system (e.g., 2000) detects, via a rotatable input device of the one or more input devices, a rotational input. In response to detecting the rotational input, the computer system changes a scale of distances among the one or more indications of the one or more locations and the indication of the current location (and, optionally showing an indication of scale (e.g., on the base plane)). Changing a scale of the second view provides the user with additional feedback about additional locations and/or provides the user with more granular feedback about fewer locations, thereby providing improved visual feedback.
  • the computer system detects that the computer system is no longer in communication range of a cellular service provider of the computer system.
  • the computer system adds an indication (e.g., 920D), as part of the first view and/or the second view, corresponding to a last location that the computer system was in communication range of the cellular service provider.
  • the first view and/or second view automatically show a point corresponding to a location of the last place a cellular connection was available (of the service provider, even though other service provides are available and in communication range of the computer system). Automatically show an indication corresponding to last cellular connection (e.g., of the device’s cellular service provider) when out of cellular connection range provides the user with feedback about where to go back to get cellular service (e.g., in case of an emergency).
  • the computer system detects that the computer system is no longer in communication range of any cellular service provider.
  • the computer system adds an indication (e.g., 920D), as part of the first view and/or the second view, corresponding to a last location that the computer system was in communication range of any cellular service provider.
  • the first view and/or second view automatically show a point corresponding to the location of the last place where a cellular connection (of any service provider) was available.
  • a mobile device e.g., a phone or a wearable device such as a watch
  • a mobile device e.g., a phone or a wearable device such as a watch
  • a target altitude either above or below the target.
  • frequent and unwanted notifications may occur when the device moves up and down while close to the target altitude or when a user incidentally raises or lowers the arm with the device.
  • the disclosed techniques add a programmable threshold amount of altitude around the monitored (or measured) altitude to reduce or prevent unwanted notifications by enabling and disabling notifications at appropriate times when the mobile device travels up and down while close to a target altitude.
  • the threshold amount around the monitored (or measured) altitude may be viewed as a band along the trajectory line of the monitored altitude.
  • FIGs. 11 and 12 below illustrate altitude alerts triggered by the vertical geofence whenever a target altitude is reached or crossed. Excessive and unwanted alerts are shown.
  • FIG. 12 shows additional vertical geofence signal changes.
  • FIG. 11 illustrates a vertical geofence at a target altitude and alerts when the target altitude is reached, according to some embodiments.
  • Line 1110 shows the altitude change over time.
  • an alert can be provided on the screen of the device.
  • a user of a mobile device moves up (or ascends in elevation) and down a hill (or descends in elevation)
  • its movement may be categorized as crossing a target altitude or attaining a target altitude.
  • Crossing a target altitude may include crossing-on-the- way-up 1126, and crossing-on-the- way-down 1120.
  • Attaining a target altitude may include reaching a hilltop 1140 or reaching a valley (not shown but similar to 1140 in the opposite direction).
  • the user When crossing a target altitude, the user usually would like an alert when the device reaches the target altitude.
  • the trajectory line may be above or below but close to the target altitude, excessive and unwanted alerts (e.g., 1122 and 1124) may occur.
  • FIG. 12 illustrates the vertical geofence notifications when a user travels above and below a target altitude, according to some embodiments.
  • a vertical geofence signal 1202 may change with the monitored current altitude and control notifications (described below). For the vertical geofence signal 1202 changes from true (or true/high state) to false (or false/low state when a mobile device drops below the target altitude (e.g., 1220 and 1224), and changes from false to true when the mobile device goes above the target altitude (e.g., 1222 and 1226).
  • FIGs. 13 and 14 illustrate the disclosed techniques for preventing unwanted or excessive notifications, such as during target altitude attainments (e.g., hilltop or valley).
  • target altitude attainments e.g., hilltop or valley.
  • FIG. 15 A framework utilizing the disclosed techniques is also shown in FIG. 15.
  • FIG. 13 illustrates a mechanism to prevent unwanted notifications, according to some embodiments.
  • FIG. 13 shows a shaded band around the trajectory line. This band indicates that after an alert is triggered, a new alert will not be provided until the mobile device has an altitude that is different from the target altitude by at least a threshold amount.
  • the threshold amount i.e., the band
  • the threshold amount may be a programmable height (e.g., a few feet) set by a user of the mobile device or the manufacturer of the mobile device,
  • a new alert (notification) will not be provided as the band does not leave the vertical geofence. That is, the altitude does not go significantly (sufficiently) above the target altitude for the notification mechanism to reset.
  • FIG. 14 illustrates a mechanism to prevent unwanted notifications using a vertical geofence signal, according to some embodiments.
  • the vertical geofence signal 1402 may change with the monitored current altitude and control notifications (e.g., neutral state disables notifications, and true or false state enables notifications).
  • the vertical geofence signal 1402 (e.g., acting as a control signal) may be reset (i.e., by disabling notifications) after each notification and does not start (i.e., enabling notifications) again until the current altitude differs from the target altitude by a threshold.
  • the signal 1402 changes from true (or true/high state) to false (or false/low state) when a mobile device drops below the target altitude (i.e., crossing on the way down) at time 1420 and triggers a notification 1460.
  • the signal 1402 is then reset (i.e., notification is disabled and goes to the “init” (or neutral) state) soon after.
  • the notification is enabled again, for example, at time 1421 by returning the signal 1402 to the false/low state.
  • the signal 1402 changes from false to true when the mobile device goes above the target altitude and triggers a notification 1462.
  • the signal 1402 is then reset (i.e., notification is disabled) again.
  • the trajectory around the hilltop 1440 is still within the threshold amount (e.g., the band). Therefore, excessive and unwanted alerts (e.g., 1424) can be avoided.
  • the notification is not enabled again until time 1425 when the mobile device moves below the target altitude by more than the threshold amount.
  • the mobile device goes above the target altitude (i.e., crossing on the way up), and the signal 1402 changes from false to true accordingly, followed by a notification 1466.
  • the signal 1402 may be reset (i.e., notification is disabled and goes to the “init” (or neutral) state) each time after a notification is triggered (e.g., 1420, 1422, and 1426).
  • the notification can be enabled again when the mobile goes above or below the target altitude by more than the threshold amount (i.e., outside the band), by changing the signal 1402 from the “init” state to the “true” state (not shown) if above the target altitude, or “false” state (e.g., 1421 and 1425) if below the target altitude, respectively.
  • FIG. 15 shows the operation of a framework to track altitude and provide notifications, according to some embodiments.
  • An always-on processor can use an altimeter for making measurements and comparing a current altitude to a target altitude/elevation, including any upper and lower thresholds (e.g., as shown in FIG. 14).
  • An altimeter can correct itself due to weather and provide compensation according to the weather drift.
  • FIG. 16 is a flowchart illustrating a method of triggering an alert at a target altitude, according to some embodiments.
  • one or more method blocks of FIG. 16 may be performed by a mobile device (e.g., architecture 1500, electronic device 1700).
  • one or more method blocks of FIG. 16 may be performed by another device or a group of devices separate from or including the mobile device.
  • one or more method blocks of FIG. 16 may be performed by one or more components of the mobile device, such as computer-readable medium 1702, Input/Output (I/O) subsystem 1706, wireless circuitry 1708, sensors 1716, application processor 1718, etc.
  • I/O Input/Output
  • a target altitude is received and stored.
  • the target altitude can be received from a user.
  • the user may enter the information into the watch via a user interface, such as voice command, a slider, typing, etc.
  • the target altitude may also be entered into a mobile phone that is paired with the watch, for example, via Bluetooth. The mobile phone can then send the entered information to the watch.
  • the current altitude of the device is monitored using an altimeter.
  • An altimeter in the mobile device can measure the current altitude of the device. For example, in FIG. 14, an altimeter in the mobile device measures the device’s current altitude at different points in time.
  • the current altitude (also referred to as measured altitude) is compared to the target altitude.
  • the two values can be determined to be equal or different but within a threshold or tolerance.
  • the current measured altitude of a mobile device is determined to be equal to the target altitude 1401 at time 1422.
  • the measured altitude and the target altitude 1401 are different but within a threshold (e.g., the shaded band).
  • a notification is provided when the current altitude matches the target altitude.
  • a notification is triggered or provided (i.e., signal 1402 changes from “false” to “true” state) when the current altitude of the mobile device matches the target altitude 1410 at time 1422.
  • notifications are disabled after the notification in 1640 is provided.
  • the notification signal 1402 is reset to the “inif ’ state after the notification is triggered at time 1422.
  • notifications are enabled when the current altitude differs from the target altitude by more than a threshold amount.
  • a threshold e.g., the shaded band
  • FIG.17 is a block diagram of an example device 1700, which may be a mobile device.
  • Devicel700 generally includes computer-readable mediuml702, a processing systeml704, an Input/Output (I/O) subsy stem 1706, wireless circuitry 1708, and audio circuitryl710 including speakerl750 and microphonel752. These components may be coupled by one or more communication buses or signal linesl703.
  • I/O Input/Output
  • Devicel700 can be any portable mobile device, including a handheld computer, a tablet computer, a mobile phone, laptop computer, tablet device, media player, personal digital assistant (PDA), a key fob, a car key, an access card, a multi-function device, a mobile phone, a portable gaming device, a car display unit, or the like, including a combination of two or more of these items.
  • PDA personal digital assistant
  • Wireless circuitry 1708 is used to send and receive information over a wireless link or network to one or more other devices' conventional circuitry such as an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, memory, etc. Wireless circuitry 1708 can use various protocols, e.g., as described herein.
  • Wireless circuitryl708 is coupled to processing systeml704 via peripherals interfacel716.
  • Interfacel716 can include conventional components for establishing and maintaining communication between peripherals and processing systeml704.
  • Voice and data information received by wireless circuitryl708 e.g., in speech recognition or voice command applications
  • processors 1718 are configurable to process various data formats for one or more application programsl734 stored on mediuml702.
  • Peripherals interfacel716 couple the input and output peripherals of the device to processorl718 and computer-readable mediuml702.
  • One or more processors 1718 communicate with computer-readable mediuml702 via a controller 1720.
  • Computer-readable mediuml702 can be any device or medium that can store code and/or data for use by one or more processorsl718.
  • Mediuml702 can include a memory hierarchy, including cache, main memory, and secondary memory.
  • Devicel700 also includes a power systeml742 for powering the various hardware components.
  • Power systeml742 can include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components typically associated with the generation, management, and distribution of power in mobile devices.
  • power sources e.g., battery, alternating current (AC)
  • AC alternating current
  • a recharging system e.g., a recharging system
  • a power failure detection circuit e.g., a power failure detection circuit
  • a power converter or inverter e.g., a power converter or inverter
  • a power status indicator e.g., a light emitting diode (LED)
  • devicel700 includes a cameral744.
  • devicel700 includes sensorsl746.
  • Sensorsl746 can include accelerometers, compasses, gyrometers, pressure sensors, audio sensors, light sensors, barometers, altimeter, and the like.
  • Sensors 1746 can be used to sense location aspects, such as auditory or light signatures of a location.
  • devicel700 can include a GPS receiver, sometimes referred to as a GPS unitl748.
  • a mobile device can use a satellite navigation system, such as the Global Positioning System (GPS), to obtain position information, timing information, altitude, or other navigation information. During operation, the GPS unit can receive signals from GPS satellites orbiting the Earth.
  • GPS Global Positioning System
  • the GPS unit analyzes the signals to make a transit time and distance estimation.
  • the GPS unit can determine the current position (current location) of the mobile device. Based on these estimations, the mobile device can determine a location fix, altitude, and/or current speed.
  • a location fix can be geographical coordinates such as latitudinal and longitudinal information.
  • devicel700 may be configured to identify GLONASS signals, or any other similar type of satellite navigational signal.
  • One or more processors 1718 run various software components stored in medium 1702 to perform various functions for devicel700.
  • the software components include an operating systeml722, a communication module (or set of instructions) 1724, a location module (or set of instructions) 1726, a network coverage modulel728, a predicted app manager modulel730, and other applications (or set of instructions) 1734, such as a car locator app and a navigation app.
  • Operating systeml722 can be any suitable operating system, including iOS, Mac OS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks.
  • the operating system can include various procedures, sets of instructions, software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
  • Communication modulel724 facilitates communication with other devices over one or more external portsl736 or via wireless circuitryl708 and includes various software components for handling data received from wireless circuitry 1708 and/or external portl736.
  • External portl736 e.g., USB, EireWire, Lightning connector, 60-pin connector, etc.
  • a network e.g., the Internet, wireless LAN, etc.
  • Location/motion modulel726 can assist in determining the current position (e.g., coordinates or other geographic location identifier) and motion of device 1700.
  • Modern positioning systems include satellite based positioning systems, such as Global Positioning System (GPS), cellular network positioning based on “cell IDs,” and Wi-Fi positioning technology based on a Wi-Fi networks. GPS also relies on the visibility of multiple satellites to determine a position estimate, which may not be visible (or have weak signals) indoors or in “urban canyons.”
  • location/motion modulel726 receives data from GPS unitl748 and analyzes the signals to determine the current position of the mobile device.
  • location/motion modulel726 can determine a current location using Wi-Fi or cellular location technology.
  • the location of the mobile device can be estimated using knowledge of nearby cell sites and/or Wi-Fi access points with knowledge also of their locations.
  • Information identifying the Wi-Fi or cellular transmitter is received at wireless circuitryl708 and is passed to location/motion modulel726.
  • the location module receives the one or more transmitter IDs.
  • a sequence of transmitter IDs can be compared with a reference database (e.g., Cell ID database, Wi-Fi reference database) that maps or correlates the transmitter IDs to position coordinates of corresponding transmitters, and computes estimated position coordinates for devicel700 based on the position coordinates of the corresponding transmitters.
  • location/motion modulel726 receives information from which a location fix can be derived, interprets that information, and returns location information, such as geographic coordinates, latitude/longitude, or other location fix data.
  • Network coverage modulel728 can include various sub-modules or systems, e.g., as described herein with respect to FIGS. 6 and 7.
  • an altitude module (not shown) can include various sub-modules or systems, e.g., as described herein with respect to FIGS. 11-16.
  • the one or more application programsl734 on the mobile device can include any applications installed on the devicel700, including without limitation, a browser, address book, contact list, email, instant messaging, word processing, keyboard emulation, widgets, JAVA- enabled applications, encryption, digital rights management, voice recognition, voice replication, a music player (which plays back recorded music stored in one or more files, such as MP3 or AAC files), etc.
  • a graphics module can include various conventional software components for rendering, animating, and displaying graphical objects (including without limitation text, web pages, icons, digital images, animations, and the like) on a display surface.
  • a timer module can be a software timer.
  • the timer module can also be implemented in hardware. The time module can maintain various timers for any number of events.
  • the I/O subsysteml706 can be coupled to a display system (not shown), which can be a touch-sensitive display.
  • the display system displays visual output to the user in a GUI.
  • the visual output can include text, graphics, video, and any combination thereof. Some or all of the visual output can correspond to user-interface objects.
  • a display can use LED (light emitting diode), LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies can be used in other embodiments.
  • I/O subsysteml706 can include a display and user input devices such as a keyboard, mouse, and/or track pad.
  • I/O subsysteml706 can include a touch-sensitive display.
  • a touch-sensitive display can also accept input from the user based on haptic and/or tactile contact.
  • a touch-sensitive display forms a touch-sensitive surface that accepts user input.
  • the touch-sensitive display/surface (along with any associated modules and/or sets of instructions in mediuml702) detects contact (and any movement or release of the contact) on the touch-sensitive display and converts the detected contact into interaction with user-interface objects, such as one or more soft keys, that are displayed on the touch screen when the contact occurs.
  • a point of contact between the touch-sensitive display and the user corresponds to one or more digits of the user.
  • the user can make contact with the touch-sensitive display using any suitable object or appendage, such as a stylus, pen, finger, and so forth.
  • a touch-sensitive display surface can detect contact and any movement or release thereof using any suitable touch sensitivity technologies, including capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch-sensitive display.
  • the I/O subsystem can be coupled to one or more other physical control devices (not shown), such as pushbuttons, keys, switches, rocker buttons, dials, slider switches, sticks, LEDs, etc., for controlling or performing various functions, such as power control, speaker volume control, ring tone loudness, keyboard input, scrolling, hold, menu, screen lock, clearing and ending communications and the like.
  • devicel700 in addition to the touch screen, devicel700 can include a touchpad (not shown) for activating or deactivating particular functions.
  • the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output.
  • the touchpad can be a touch- sensitive surface that is separate from the touch-sensitive display, or an extension of the touch- sensitive surface formed by the touch-sensitive display.
  • some or all of the operations described herein can be performed using an application executing on the user’s device.
  • Circuits, logic modules, processors, and/or other components may be configured to perform various operations described herein.
  • a programmable processor can be configured by providing suitable executable code;
  • a dedicated logic circuit can be configured by suitably connecting logic gates and other circuit elements; and so on.
  • Any of the software components or functions described in this application may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C, C++, C#, Objective-C, Swift, or scripting language such as Perl or Python using, for example, conventional or object-oriented techniques.
  • the software code may be stored as a series of instructions or commands on a computer readable medium for storage and/or transmission.
  • a suitable non-transitory computer readable medium can include random access memory (RAM), a read only memory (ROM), a magnetic medium such as a harddrive or a floppy disk, or an optical medium ⁇ such as a compact disk (CD) or DVD (digital versatile disk), flash memory, and the like.
  • the computer readable medium may be any combination of such storage or transmission devices.
  • Computer programs incorporating various features of the present disclosure may be encoded on various computer readable storage media; suitable media include magnetic disk or tape, optical storage media, such as compact disk (CD) or DVD (digital versatile disk), flash memory, and the like.
  • Computer readable storage media encoded with the program code may be packaged with a compatible device or provided separately from other devices.
  • program code may be encoded and transmitted via wired optical, and/or wireless networks conforming to a variety of protocols, including the Internet, thereby allowing distribution, e.g., via Internet download.
  • Any such computer readable medium may reside on or within a single computer product (e.g., a solid state drive, a hard drive, a CD, or an entire computer system), and may be present on or within different computer products within a system or network.
  • a computer system may include a monitor, printer, or other suitable display for providing any of the results mentioned herein to a user.
  • this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person.
  • personal information data can include demographic data, locationbased data, telephone numbers, email addresses, twitter ID's, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
  • the present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users.
  • the personal information data can be used to predict users that a user may want to communicate with at a certain time and place.
  • use of such personal information data included in contextual information enables people centric prediction of people a user may want to interact with at a certain time and place.
  • other uses for personal information data that benefit the user are also contemplated by the present disclosure.
  • health and fitness data may be used to provide insights into a user’s general wellness or may be used as positive feedback to individuals using technology to pursue wellness goals.
  • the present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices.
  • such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure.
  • Such policies should be easily accessible by users and should be updated as the collection and/or use of data changes.
  • Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users.
  • policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
  • HIPAA Health Insurance Portability and Accountability Act
  • the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data.
  • the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter.
  • users can select not to provide location information for recipient suggestion services.
  • users can select to not provide precise location information, but permit the transfer of location zone information.
  • the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
  • personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed.
  • data de-identifi cation can be used to protect a user’s privacy.
  • De-identifi cation may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
  • specific identifiers e.g., date of birth, etc.
  • controlling the amount or specificity of data stored e.g., collecting location data a city level rather than at an address level
  • controlling how data is stored e.g., aggregating data across users
  • the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, users that a user may want to communicate with at a certain time and place may be predicted based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information, or publicly available information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Navigation (AREA)

Abstract

Des points de cheminement peuvent être créés automatiquement par surveillance d'une intensité de signal sans fil de réseau afin d'aider un utilisateur d'un dispositif mobile dans un emplacement non urbain à trouver un emplacement précédent avec une connectivité de réseau connue et à effectuer des appels d'urgence. Dans certains modes de réalisation, un itinéraire de retour en arrière est affiché sur le dispositif mobile vers l'emplacement précédent le plus proche présentant une connectivité de réseau. Dans certains modes de réalisation, pour des raisons de confidentialité, l'accès à des informations de point de cheminement stockées dans une base de données/un stockage sécurisés est limité sur la base de la détermination de l'état d'emplacement, et des itinéraires de retour en arrière sont affichés par étapes.
PCT/US2024/032631 2023-06-05 2024-06-05 Points de cheminement pour une dernière connectivité de réseau connue Pending WO2024254196A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363506362P 2023-06-05 2023-06-05
US63/506,362 2023-06-05
US18/733,658 2024-06-04
US18/733,658 US20240405900A1 (en) 2023-06-05 2024-06-04 Waypoints for last known network connectivity

Publications (1)

Publication Number Publication Date
WO2024254196A1 true WO2024254196A1 (fr) 2024-12-12

Family

ID=91782229

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/032631 Pending WO2024254196A1 (fr) 2023-06-05 2024-06-05 Points de cheminement pour une dernière connectivité de réseau connue

Country Status (1)

Country Link
WO (1) WO2024254196A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041911A1 (fr) * 1997-03-20 1998-09-24 Hedrick Geoffrey S M Systeme d'alerte d'altitude pour aeronef evoluant dans un espace aerien minimum a separation verticale limitee et procede correspondant
US20110029229A1 (en) * 2009-07-30 2011-02-03 Sony Ericsson Mobile Communications Ab System and Method of Providing Directions to a User of a Wireless Communication Device
US20140155099A1 (en) * 2012-11-30 2014-06-05 Samsung Electronics Co., Ltd. Method and apparatus for displaying location information of call service area in mobile terminal
US20160050531A1 (en) * 2014-08-14 2016-02-18 Samsung Electronics Co., Ltd. Method and apparatus for device positioning
US20160212612A1 (en) * 2015-01-21 2016-07-21 Htc Corporation Mobile device, notification method, and computer-readable recording medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998041911A1 (fr) * 1997-03-20 1998-09-24 Hedrick Geoffrey S M Systeme d'alerte d'altitude pour aeronef evoluant dans un espace aerien minimum a separation verticale limitee et procede correspondant
US20110029229A1 (en) * 2009-07-30 2011-02-03 Sony Ericsson Mobile Communications Ab System and Method of Providing Directions to a User of a Wireless Communication Device
US20140155099A1 (en) * 2012-11-30 2014-06-05 Samsung Electronics Co., Ltd. Method and apparatus for displaying location information of call service area in mobile terminal
US20160050531A1 (en) * 2014-08-14 2016-02-18 Samsung Electronics Co., Ltd. Method and apparatus for device positioning
US20160212612A1 (en) * 2015-01-21 2016-07-21 Htc Corporation Mobile device, notification method, and computer-readable recording medium

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BOB FANSHIER: "Garmin G500 Pilot's Guide", GARMIN INTERNATIONAL, 1 August 2011 (2011-08-01), pages 1 - B-10, XP055090809, Retrieved from the Internet <URL:http://static.garmincdn.com/pumac/190-01102-02_0D_web.pdf> [retrieved on 20131128] *

Similar Documents

Publication Publication Date Title
US11553302B2 (en) Labeling a significant location based on contextual data
US12078501B2 (en) Mobile search based on predicted location
US20240405900A1 (en) Waypoints for last known network connectivity
CN111896940B (zh) 针对移动设备的空间感知用户界面的测距测量
US10070261B2 (en) Harvesting labels for significant locations and updating a location fingerprint database using harvested labels
US11788858B2 (en) Labeling a significant location based on contextual data
US9743234B2 (en) Monitoring a mobile device en route to destination
KR101429298B1 (ko) 이동 장치를 위한 위치 기반 캐싱
US8660790B2 (en) Dynamic alerts for calendar events
US8718672B2 (en) Identifying status based on heterogeneous sensors
ES2760556T3 (es) Preobtención de información basándose en gestos
US20190005055A1 (en) Offline geographic searches
WO2024254196A1 (fr) Points de cheminement pour une dernière connectivité de réseau connue
CN121241583A (zh) 用于最后已知网络连接性的路点
US20250274900A1 (en) Managing wi-fi scans using measurements from other user devices

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24738104

Country of ref document: EP

Kind code of ref document: A1