Cloudcar, Inc.

Carrier Iq, Inc.

Bruce Leak

Peter T Barrett

Konstantin Othmer

Zarko Draganic

Steve Roskowski

An embodiment includes a non-transitory computer-readable medium with programming code executable by a processor to perform operations including accessing a scheduled time and teleconference contact information associated with a teleconference calendar event. The operations include determining whether an operator is operating a vehicle based on synchronization between a mobile device and an abstraction and communication device (device) interfaced with the vehicle. When an actual time is within a threshold of the scheduled time and the operator is operating the vehicle, the operations include determining whether the operator is a participant of a teleconference. If so, the operations include extracting the teleconference contact information from the teleconference calendar event. The operations include communicating a prompt to join the teleconference and receiving a confirmation to join the teleconference. The operations include communicating a signal indicating the confirmation via the device and placing a call to join the teleconference.

Teleconference calls based on calendar events

Course-based place searching systems and methods are described. In an embodiment, a system for performing a course-based place search may include a navigation device, a processing device, and a display. The navigation device may be configured to track a location and a course of the vehicle. The processing device may be communicatively coupled to the navigation device and may be configured to request places from a resource based at least in part on the location of the vehicle and the search criterion and to return a first one or more places received from the resource to an occupant of the vehicle. The first one or more places may be based at least in part on the course of the vehicle. The display may be communicatively coupled to the processing device. The first one or more places may be displayed on the display.

Course-based place searching

An example embodiment includes an automatic pairing system. The automatic pairing system includes a vehicle initialization module, a vehicle pairing module, and a triggering mechanism. The vehicle initialization module is loaded onto a vehicle abstraction device configured to interface with a vehicle. The vehicle pairing module is loaded on the vehicle abstraction device. The vehicle pairing module is configured to be launched by the vehicle initialization module. After being launched, the vehicle pairing module is configured to automatically communicate vehicle pairing data stored on the vehicle pairing module to establish one or more communication channels between the vehicle and a mobile device. The triggering mechanism is configured to trigger the vehicle initialization module to launch the vehicle pairing module.

Automatic device initialization and pairing

An example embodiment disclosed herein includes a vehicle teleconferencing system. The vehicle teleconferencing system includes an abstraction and communication device (hereinafter 'device') and a mobile device. The device includes an adaptor configured to interface with a Controller Area Network bus of a vehicle and to abstract vehicle data from the vehicle. The mobile device includes an operation determination module, a clock, and a teleconferencing module. The operation determination module is configured to determine that an operator is operating the vehicle based on a subset of the data. The clock is configured to track actual time. The teleconferencing module is configured to access a teleconference calendar event that includes a scheduled time and teleconference contact information, and when the actual time is within a predetermined threshold of the scheduled time and the operator is operating the vehicle, to prompt the operator to join a teleconference.

An example embodiment disclosed herein includes a predictive vehicle navigation system. The predictive vehicle navigation system includes an abstraction and communication device (hereinafter 'device') and a mobile device. The device includes an adaptor configured to interface with a Controller Area Network (CAN) bus of a vehicle and to abstract vehicle data from the vehicle. The mobile device includes an operation determination module configured to determine that an operator is operating the vehicle based on a subset of the data, a clock configured to track actual time, and a navigation module configured to receive the actual time and the determination that the operator is operating the vehicle, to access a calendar event that includes an address and a scheduled time, and when the actual time is within a predetermined threshold of the scheduled time, to predict that the address is a destination of the operator.

Navigation based on calendar events

In an example, a method of enforcing regulatory guidelines related to functionality of an electronic device associated with a vehicle when the vehicle is in a drive mode includes interfacing an application of an electronic device associated with a vehicle with an Application Programming Interface (API). The method additionally includes determining that the vehicle is in the drive mode. In the method, the API may modify a functionality of the application of the electronic device in accordance with regulatory guidelines associated with operation of the electronic device when the vehicle is in the drive mode. The modification may be based on the determination that the vehicle is in the drive mode.

Enforcement of regulatory guidelines associated with a drive mode of a vehicle

Generating neighbor lists. A set of devices are provisioned to report on neighbor lists and visibility of sectors. Each device in the set of devices generates event data that includes the neighbor list from a sector, other sectors visible while using the neighbor list, and/or sectors visible to the device if the call was dropped or lost. The event data of each device is received at a management system. The management system can derive recommended neighbor lists for each sector in a wireless network based on the cumulative event data received from the set of devices operating in the network.

Neighbor list generation in wireless networks

Generating neighbor lists. A set of devices are provisioned to report on neighbor lists and visibility of sectors. Each device in the set of devices generates event data that includes the neighbor list from a sector, other sectors visible while using the neighbor list, and/or sectors visible to the device if the call was dropped or lost. The event data can be recorded or stored by the device or forwarded to a server immediately or at a later time. The event data of each device is received at and recorded by a management system. The management system can derive recommended neighbor lists for each sector in a wireless network based on the cumulative event data received from the set of devices operating in the network.

Growing community of inventors

Los Altos Hills, CA, United States of America

Bruce Leak