PROPAGATION OF APPLICATION CONTEXT BETWEEN A MOBILE DEVICE AND A VEHICLE INFORMATION SYSTEM

• US 20140280580A1
• Filed: 08/23/2013
• Published: 09/18/2014
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited, QNX Software Systems Limited (Canada) (Blackberry Limited)
• Inventors: LANGLOIS, Michael George, JOHNSON, Benjamin Allan
• Granted Patent: US 10,251,034 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: B60K 2360/119 Icons
• CPC Class Codes: B60K 2360/55 Remote control arrangements
• CPC Class Codes: B60K 2360/569 Vehicle controlling mobile device functions
• CPC Class Codes: B60K 2360/589 Wireless data transfers
• CPC Class Codes: B60K 2360/5911 Bluetooth
• CPC Class Codes: B60K 2370/119 Icons
• CPC Class Codes: B60K 2370/55 Remote controls
• CPC Class Codes: B60K 2370/569 Vehicle controlling mobile device functions
• CPC Class Codes: B60K 2370/589 Wireless
• CPC Class Codes: B60K 2370/5911 Bluetooth
• CPC Class Codes: B60K 35/10 Input arrangements, i.e. from user to vehicle, associated with vehicle functions or specially adapted therefor
• CPC Class Codes: B60K 35/80 Arrangements for controlling instruments
• CPC Class Codes: B60K 35/85 Arrangements for transferring vehicle- or driver-related data
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

A method, device, and a vehicle information system are provided for persisting application context from the mobile device to the vehicle information system. An operating context is determined for at least one application executing on the mobile device. A user interface view for display by the vehicle information system is generated and provided to the vehicle information system. The user interface view comprises at least one application user interface element associated with the at least one application, and the application user interface element comprises an application entry point defined by the operating context for the at least one application.

Claims

1. A method, comprising:

establishing, by a mobile device, a session with an in-vehicle information system;

determining an operating context for at least one application executing on a mobile device, the operating context comprising one or more of a current execution state, a current output state, an availability of persisted data, and a most recently displayed application user interface view; and

defining, using the operating context for the at least one application, a user interface view for display by the in-vehicle information system.

2. The method of claim 1, wherein the operating context comprises the current execution state and the current output state;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises an application user interface view for the first application.

3. The method of claim 2, wherein the active state comprises current playback of an audio file.

4. The method of claim 2, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a background execution state; and

the current output state is a static state,

the user interface view for display by the in-vehicle information system comprises the application user interface view for the first application.

5. The method of claim 1, wherein the operating context comprises the current execution state and the current output state;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a background execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises a homescreen view for the in-vehicle information system, the homescreen view comprising application user interface elements for accessing a plurality of applications including the first application.

6. The method of claim 5, wherein the application user interface element for accessing the first application comprises an indicator of the operating context of the first application.

7. The method of claim 6, wherein the application user interface element for accessing the first application comprises:

a first portion comprising the indicator of the operating context of the first application, the first portion being actuatable to access the first application at a first application entry point; and

a second portion actuatable to access the first application at a second application entry point, the second application entry point providing access to interact with current output of the first application.

8. The method of claim 6, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a foreground execution state; and

the current output state is a static state,

the homescreen view includes an application user interface element for accessing the second application, said application user interface element comprising an indicator of the operating context of the second application.

9. The method of claim 1, wherein the operating context comprises the current execution state, the current output state, and the availability of persisted data;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises an application user interface view for the first application.

10. The method of claim 1, wherein the operating context comprises the current execution state, the current output state, and the availability of persisted data;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is a static state; and

the user interface view for display by the in-vehicle information system comprises a homescreen view for the in-vehicle information system, the homescreen view comprising application user interface elements for accessing a plurality of applications including the first application, the application user interface element for the first application comprising an indication of the persisted data.

11. The method of claim 10, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a background execution state;

the current output state is a static state; and

persisted data is available,

the homescreen view includes an application user interface element for accessing the second application comprising an indication of the persisted data for the second application.

12. The method of claim 1, wherein the user interface view is defined by the at least one application executing at the mobile device.

13. A mobile device, including:

a communications subsystem adapted for communication with an in-vehicle information system;

a memory adapted to store operating context for at least one application executing on the mobile device; and

a processor configured to enable;

establishing, using the communications subsystem, a session with the in-vehicle information system;

determining an operating context for the at least one application executing on a mobile device, the operating context comprising one or more of a current execution state, a current output state, an availability of persisted data, and a most recently displayed application user interface view; and

defining, using the operating context for the at least one application, a user interface view for display by the in-vehicle information system.

14. The mobile device of claim 13, wherein the operating context comprises the current execution state and the current output state;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises an application user interface view for the first application.

15. The mobile device of claim 14, wherein the active state comprises current playback of an audio file.

16. The mobile device of claim 14, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a background execution state; and

the current output state is a static state,

the user interface view for display by the in-vehicle information system comprises the application user interface view for the first application.

17. The mobile device of claim 13, wherein the operating context comprises the current execution state and the current output state;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a background execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises a homescreen view for the in-vehicle information system, the homescreen view comprising application user interface elements for accessing a plurality of applications including the first application.

18. The mobile device of claim 17, wherein the application user interface element for accessing the first application comprises an indicator of the operating context of the first application.

19. The mobile device of claim 18, wherein the application user interface element for accessing the first application comprises:

a first portion comprising the indicator of the operating context of the first application, the first portion being actuatable to access the first application at a first application entry point; and

a second portion actuatable to access the first application at a second application entry point, the second application entry point providing access to interact with current output of the first application.

20. The mobile device of claim 18, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a foreground execution state; and

the current output state is a static state,

the homescreen view includes an application user interface element for accessing the second application, said application user interface element comprising an indicator of the operating context of the second application.

21. The mobile device of claim 13, wherein the operating context comprises the current execution state, the current output state, and the availability of persisted data;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is an active state; and

the user interface view for display by the in-vehicle information system comprises an application user interface view for the first application.

22. The mobile device of claim 13, wherein the operating context comprises the current execution state, the current output state, and the availability of persisted data;

and for a first application of the at least one application executing on the mobile device;

the current execution state is a foreground execution state;

the current output state is a static state; and

the user interface view for display by the in-vehicle information system comprises a homescreen view for the in-vehicle information system, the homescreen view comprising application user interface elements for accessing a plurality of applications including the first application, the application user interface element for the first application comprising an indication of the persisted data.

23. The mobile device of claim 22, wherein when for a second application of the at least one application executing on the mobile device:

the current execution state is a background execution state;

the current output state is a static state; and

persisted data is available,

the homescreen view includes an application user interface element for accessing the second application comprising an indication of the persisted data for the second application.

24. The mobile device of claim 13, wherein the user interface view is defined by the at least one application executing at the mobile device.