Patent application number | Description | Published |
20090082951 | Intelligent Restriction of Device Operations - A navigation system includes a user interface for detecting touch input. The system uses touch input to determine if a driver or passenger is operating the navigation system. If the system determines that the driver is operating the system, then an action is initiated (e.g., the user interface is locked down, a warning is provided). The navigation system allows a passenger in the vehicle to operate the navigation system while the vehicle is in motion. In an aspect, additional or other sensors (e.g., seat sensor, seat belt sensor, infrared sensor) can be used to detect whether a driver or passenger is operating the navigation system while the vehicle is in motion. | 03-26-2009 |
20090096573 | Activation of Cryptographically Paired Device - An event is detected at a first device. Responsive to the detection, at least some functionality of the first device is deactivated. The presence of a second device, cryptographically paired with the first device, is detected by the first device. Responsive to the detection, at least some functionality of the first device is activated or reactivated. | 04-16-2009 |
20090157289 | Navigation Systems and Services - Navigation systems and services are described. The navigation services can include obtaining a route or route segment based on a location of a vehicle and a destination. Based on the route, a current fuel supply of the vehicle, and a number of factors related to fuel consumption, a refueling location can be estimated. A number of locations of fuel stations in proximity to the refueling location can be determined and presented to a user, for example, on a map showing the route. | 06-18-2009 |
20110179153 | METHOD AND APPARATUS FOR IDLING A NETWORK CONNECTION - The described embodiments provide a system that controls the operating state of a network interface. During operation, in response to receiving a request from an application to use the network interface for a route, the system creates a route structure for the route and increments a route reference counter in an interface data structure for the network interface. Upon subsequently determining that the application is no longer using the route, the system sets a route expiration timer in the route structure to a predetermined expiration time. When the route expiration timer expires, the system deletes the route structure and decrements the route reference counter in the interface data structure. When decrementing the route reference counter in the interface data structure causes the route reference counter to be equal to zero, the system sends a signal to a configuration application to inform the application that the network interface can be idled. | 07-21-2011 |
20110179163 | METHOD AND APPARATUS FOR IDLING A NETWORK CONNECTION - The described embodiments include a system that configures a network interface. During operation, the system receives a signal from an operating system indicating that the network interface can be idled. The signal is sent from the operating system as soon as the operating system determines that a final route structure that depended on the network interface has expired and been deleted. The system then determines if an application has established a route that uses the network interface since the signal was sent from the operating system. If not, the system causes the network interface to be idled. Otherwise, the system leaves the network interface in a current operating state. | 07-21-2011 |
20140171065 | SYSTEM AND METHOD FOR INTELLIGENTLY SELECTING A NETWORK INTERFACE - An method, apparatus and machine readable medium are described for intelligently selecting a network interface. An attempt may be made to connect over a first network interface having the highest priority (e.g., WiFi). At the same time, a fallback timer is started. If the attempt to connect over the first network interface does not succeed within a designated timer threshold, then a parallel attempt is made to connect over a second network interface having a lower priority (e.g., cellular). The first network interface over which a connection is successfully made is then used. These techniques may be employed on a per-connection basis. Thus, a first process may successfully connect over the first network interface while a second process may be unsuccessful over the first network interface but may fall back to the second network interface. | 06-19-2014 |
20140365642 | Smart Management of Background Network Connections Based on Historical Data - In some implementations, a network daemon can manage access to a mobile device's network interface. The network daemon (e.g., network connection managing process) can monitor the condition of the mobile device's network connection on one or more interfaces. The network daemon can monitor many conditions on the mobile device. The network daemon can receive background networking requests from network clients (e.g., processes, applications) that specify criteria for initiating a network connection. The network daemon can then smartly manage network connections taking into account network conditions, mobile device conditions and/or client criteria received in the client request. This can help reduce battery life impact, memory usage, likelihood of call drops, data usage cost, and load on network operators. | 12-11-2014 |
20140365673 | Smart Management of Background Network Connections - In some implementations, a network daemon can manage access to a mobile device's network interface. The network daemon (e.g., network connection managing process) can monitor the condition of the mobile device's network connection on one or more interfaces. The network daemon can monitor many conditions on the mobile device. The network daemon can receive background networking requests from network clients (e.g., processes, applications) that specify criteria for initiating a network connection. The network daemon can then smartly manage network connections taking into account network conditions, mobile device conditions and/or client criteria received in the client request. This can help reduce battery life impact, memory usage, likelihood of call drops, data usage cost, and load on network operators. | 12-11-2014 |
20140366042 | Initiating Background Updates Based on User Activity - In some implementations, a mobile device can be configured to monitor environmental, system and user events. The occurrence of one or more events can trigger adjustments to system settings. In some implementations, the mobile device can be configured to keep frequently invoked applications up to date based on a forecast of predicted invocations by the user. In some implementations, the mobile device can receive push notifications associated with applications that indicate that new content is available for the applications to download. The mobile device can launch the applications associated with the push notifications in the background and download the new content. In some implementations, before running an application or accessing a network interface, the mobile device can be configured to check energy and data budgets and environmental conditions of the mobile device to preserve a high quality user experience. | 12-11-2014 |