Apple Inc.

Gregory Dennis Bolsinga

Seejo K Pylappan

Marcel Van Os

Richard Williamson

Bradford Allen Moore

Christine B McGavran

Tim Omernick

Lukas Michael Marti

Christopher Blumenberg

Michael P Dal Santo

Aroon Pahwa

Timothy P Omernick

A mobile device with a route prediction engine is provided that can predict current/future destinations or routes to destinations for the user, and can relay prediction information to the user. The engine includes a machine-learning engine that facilitates the formulation of predicted future destinations and/or future routes to destinations based on user-specific data. The user-specific data includes data about (1) previous destinations traveled, (2) previous routes taken, (3) locations of calendared events, (4) locations of events for which the user has electronic tickets, and/or (5) addresses parsed from e-mails and/or messages. The prediction engine relies on one or more of user-specific data stored on the device and data stored outside of the device by external devices/servers.

Mobile device with predictive routing engine

Some embodiments of the invention provide a novel prediction engine that (1) can formulate predictions about current or future destinations and/or routes to such destinations for a user, and (2) can relay information to the user about these predictions. In some embodiments, this engine includes a machine-learning engine that facilitates the formulation of predicted future destinations and/or future routes to destinations based on stored, user-specific data. The user-specific data is different in different embodiments. In some embodiments, the stored, user-specific data includes data about any combination of the following: (1) previous destinations traveled to by the user, (2) previous routes taken by the user, (3) locations of calendared events in the user's calendar, (4) locations of events for which the user has electronic tickets, and (5) addresses parsed from recent e-mails and/or messages sent to the user. In some embodiments, the prediction engine only relies on user-specific data stored on the device on which this engine executes. Alternatively, in other embodiments, it relies only on user-specific data stored outside of the device by external devices/servers. In still other embodiments, the prediction engine relies on user-specific data stored both by the device and by other devices/servers.

Warning for frequently traveled trips based on traffic

Some embodiments of the invention provide a mobile device with a novel route prediction engine that (1) can formulate predictions about current or future destinations and/or routes to such destinations for the device's user, and (2) can relay information to the user about these predictions. In some embodiments, this engine includes a machine-learning engine that facilitates the formulation of predicted future destinations and/or future routes to destinations based on stored, user-specific data. The user-specific data is different in different embodiments. In some embodiments, the stored, user-specific data includes data about any combination of the following (1) previous destinations traveled to by the user, (2) previous routes taken by the user, (3) locations of calendared events in the user's calendar, (4) locations of events for which the user has electronic tickets, and (5) addresses parsed from recent e-mails and/or messages sent to the user. The device's prediction engine only relies on user-specific data stored on the device in some embodiments, relies only on user-specific data stored outside of the device by external devices/servers in other embodiments, and relies on user-specific data stored both by the device and by other devices/servers in other embodiments.

One or more touch input signals can be obtained from a touch sensitive device. A touch event model can be used to determine touch and/or gesture events based on the touch input signals. The touch and gesture events can be associated with touch input signals generated from different regions of a web page displayed on the touch sensitive device. Access can be provided to at least one touch or gesture event through a programming interface.

Touch event model for web pages

Embodiments disclosed herein pertain to power conservation for electronic devices. According to one embodiment, power conservation can be achieved through adaptive frame rate control for a display associated with an electronic device. The frame rate is able to be controlled so as to adapt to a frame rate that is adequate for the display task. Since the display often times displays content that is not very dynamic, the frame rate in such situations can be controlled to use a reduced frame rate, which thereby reduces power consumption. However, when the display displays content that is substantially dynamic, the frame rate in such situations can be controlled to use an enhanced (or not reduced) frame rate, which ensures reasonable display quality.

Adaptive frame rate control for power savings

An electronic device receives touch input signals associated with a respective region of a web page. The respective region of the web page is associated with a plurality of event handlers or event listeners including an event handler or listener for a touch event and an event handler or listener for a gesture event. In response to receiving the touch input signals, the device sends a gesture event to the web page. The gesture event corresponds to a combination of two or more touch events, and the two or more touch events correspond to the touch input signals. The device dynamically rotates an element associated with the respective region of the web page with the event handler or listener for the gesture event based on a rotation value associated with the gesture event, and sends the touch events to the web page for processing, distinct from the dynamically rotating.

Touch event model programming interface

Prediction engine

A method includes receiving a touch event, where the touch event includes a plurality of touch lists. The plurality of touch lists includes one or more of: a first touch list for one or more touches associated with a target of the touch event, a second touch list for one or more changed touches, and a third touch list for all touches detected on a touch-sensitive surface. The method includes processing the touch event.

One or more touch input signals can be obtained from a touch sensitive device. If the touch input signals are associated with one or more regions of a web page displayed on the touch sensitive device, a touch event associated with the regions of a web page is processed by the web page. Otherwise, the touch events can be processed by an application (e.g., a browser).

Growing community of inventors

San Francisco, CA, United States of America

Gregory Dennis Bolsinga