| 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 |
| Patent application number | Description | Published |
|---|
| 20080304486 | MULTIPLEXED DATA STREAM PROTOCOL - Multiplexed data stream protocols are described. In one embodiment, a method to provide a multiplexed data stream protocol includes packetizing a data stream to provide packets with headers and transmitting the packets through an interface which is not designed to use Internet Protocol (IP) addresses. The headers contain data for flow control and sequencing and are associated with a port for an application, and the headers allow multiple applications to maintain an arbitrary and changeable number of multiple concurrent sessions through the interface. The headers may be Transmission Control Protocol (TCP) like headers and may not include IP like headers. Systems, computer readable media, software architectures and other methods are also described. | 12-11-2008 |
| 20080307109 | FILE PROTOCOL FOR TRANSACTION BASED COMMUNICATION - File protocols for transaction based communication are described. In one embodiment, a method to provide a file transfer protocol includes receiving packets containing headers, the packets being received at a first network stack software through an interface, and extracting data from he packets and reconstructing a file from data in the packets. The extracting may be performed by a first network stack software, and the interface is not designed to use Internet Protocol (IP) addresses, and the headers contain data for flow control and sequencing and are associated with a port for a file transfer application, and the headers allow multiple applications to maintain multiple concurrent sessions through the interface, which may be a USB compliant or BLUETOOTH compliant interface. Systems, computer readable media, software architectures and other methods are also described. | 12-11-2008 |
