Extendable software interface for a mobile device

• US 20020107991A1
• Filed: 07/02/2001
• Published: 08/08/2002
• Est. Priority Date: 06/30/2000
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Maguire, Michael, Pathiyal, Krishna K.
• Granted Patent: US 6,990,672 B2
• Time in Patent Office: Days
• US Class Current: 709/250
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality

Abstract

A system and method for an extendable software interface includes a software architecture for use in a mobile device having a processor and a memory device. The software architecture comprises a plurality of application programs stored in the memory device and executed by the processor, and at least one controller module for interfacing the plurality of application program with a one of a plurality of data objects stored in the memory device in the form of a data model. Each controller module utilizes one or more generic interfaces with the plurality of application programs, and also utilizes a specific interface with the data model.

Claims

1. A software architecture for use in a mobile device having a processor and a memory device, comprising:

one or more application programs stored in the memory device and executed by the processor; and

a plurality of controller modules, each controller module being configured to interface the application programs with one of a plurality of data objects stored in the memory device in the form of a data model, wherein each controller module utilizes one or more generic interfaces to communicate with the application programs.

2. The software architecture of claim 1, wherein each controller module utilizes a specific interface to communicate with the one data object.

3. The software architecture of claim 1, wherein more than one instance of the data model may be stored in the memory device at the same time.

4. The software architecture of claim 1, further comprising:

a virtual machine stored in the memory device and executed by the processor, wherein the virtual machine executes each controller module and corresponding data model.

5. The software architecture of claim 4, wherein the virtual machine is an object oriented run-time environment.

6. The software architecture of claim 5, wherein the object oriented run-time environment is JAVA®

.

7. The software architecture of claim 1, wherein each controller module and corresponding data model are constructed using a JAVA®

compiler.

8. The software architecture of claim 4, further comprising:

an operating system stored in the memory device and executed by the processor, wherein the virtual machine is executed by the operating system.

9. The software architecture of claim 1, wherein one of the plurality of controller modules is configured to interface the application programs with an e-mail message data model.

10. The software architecture of claim 1, wherein one of the plurality of controller modules is configured to interface the application programs with an address book card data model.

11. The software architecture of claim 1, wherein one of the plurality of controller modules is configured to interface the application programs with a calendar entry data model.

12. The software architecture of claim 1, wherein one of the plurality of controller modules is configured to interface the application programs with a task list data model.

13. The software architecture of claim 1, wherein one of the plurality of controller modules is configured to interface the application programs with a memo data model.

14. The software architecture of claim 1, wherein the one or more generic interfaces enable the plurality of controllers to interface with an application program installed on the mobile device that supports the one or more generic interfaces.

15. The software architecture of claim 1, wherein each generic interface is configured to perform an operation with any arbitrary data model.

16. The software architecture of claim 1, wherein each application program is configured to query each of the plurality of controller modules to determine whether the controller module supports a particular type of generic interface.

17. The software architecture of claim 1, wherein additional controller modules may be added to the software architecture that support one or more additional generic interfaces.

18. The software architecture of claim 1, wherein the one or more generic interfaces include a paint provider interface for painting the data objects into the one or more application programs.

19. The software architecture of claim 1, wherein the one or more generic interfaces include a field provider interface for providing one or more of the application programs with one or more fields from the data models.

20. The software architecture of claim 1, wherein the one or more generic interfaces include a verb provider interface for providing one or more of the application programs with one or more functions specific to the data model.

21. The software architecture of claim 1, wherein the data objects are logged in a persisted list when stored in the memory device, and the persisted list identifies the data model corresponding to each data object.

22. The software architecture of claim 1, wherein only one instance of each controller module is executing at one time.

23. The software architecture of claim 22, wherein the controller module associated with a particular type of data model is identified to one of the plurality of application programs by the data model when the application program attempts to interact with the data model.

25. The software architecture of claim 24, wherein:

a plurality of application programs are stored in the memory device and executed by the processor;

the first-order controller module is configured to utilize the generic interface to communicate with each of the application programs; and

the second-order controller module is configured to interface the second-order data object with each of the application programs.

26. The software architecture of claim 24, wherein:

a plurality of first-order data objects of different types are stored in the memory device in the form of first-order data models, wherein each first-order data model corresponds to one type of data object; and

the software architecture further comprising a plurality of first-order controller modules, each first-order controller module being configured to interface the application program with one type of first-order data model, wherein each first-order controller module utilizes the generic interface to communicate with the application program.

27. The software architecture of claim 24, wherein:

the first-order data object includes a plurality of second-order data objects of different types; and

the software architecture further comprising a plurality of second-order controller modules, each configured to interface the application program with one type of second-order data object.

28. The software architecture of claim 24, wherein the first-order controller module utilizes a plurality of generic interfaces to communicate with the application program.

29. The software architecture of claim 24, wherein the second-order controller module is executed from within the first-order controller module.

30. The software architecture of claim 24, wherein:

the first-order data model is also configured to interact with the second-order data object; and

the second-order controller module is configured to interface the application program with the first-order data model.

31. The software architecture of claim 30, wherein the second-order controller module utilizes a generic interface to communicate with the application program.

32. The software architecture of claim 30, wherein the second-order controller module utilizes a generic interface to communicate with the first-order controller module.

33. The software architecture of claim 24, wherein (1) the second-order data object is stored in the form of a second-order data model, and (2) the second-order controller module is configured to interface the application program with the second-order data model.

34. The software architecture of claim 33, wherein the second-order controller module utilizes a generic interface to communicate with the application program.

35. The software architecture of claim 33, wherein the second-order controller module utilizes a generic interface to communicate with the first-order controller module.

37. The method of claim 36, comprising the additional step of:

providing a virtual machine executing on the mobile device, wherein the virtual machine controls the plurality of controller modules and the data models.

38. The method of claim 36, comprising the additional steps of:

defining a second-order object within one or more data model;

providing a second-order controller module configured to (1) interface with the data models associated with the second-order object, and (2) utilize the one or more generic interfaces to communicate with the plurality of application programs;

wherein, the second-order controller enables the application programs to interact with the second-order object.

40. The method of claim 39, wherein the controller module utilizes one or more generic interfaces to communicate with the application program.

42. The method of claim 39, comprising the additional steps of:

selecting a function from the list of functions; and

executing the function.

43. The method of claim 39, wherein:

the controller module also interfaces the data model with one or more other application programs on the mobile device; and

the list of functions includes one or more functions that are associated with one of the other application programs.

44. The method of claim 43, comprising the additional steps of:

selecting a function from the list of functions;

determining whether the selected function is associated with the application program or one of the other application programs;

if the selected function is associated with the application program, then executing the function using the application program; and

if the selected function is associated with one of the other application programs, then (1) launching the other application program and (2) executing the function using the other application program.

45. The method of claim 44, wherein the controller module performs the step of determining whether the selected function is associated with the application program or one of the other application programs.

46. The method of claim 44, wherein the controller module launches the other application program.

47. The method of claim 39, comprising the additional steps of:

storing the one or more second-order objects in the form a second-order data models; and

providing a second-order controller module that interfaces the application program with the second-order data models.

48. The method of claim 47, wherein the second-order controller module utilizes one or more generic interfaces to communicate with the application program.

49. The method of claim 47, wherein the second-order controller module is implemented by the controller module when one of the second-order objects is selected from the displayed data object.

50. The method of claim 47, wherein the second-order controller module interfaces with the application program to display the list of functions.

51. The method of claim 39, comprising the additional step of:

storing the one or more second-order data objects in the form of second-order data models; and

providing a second-order controller module that interfaces the controller module with the second-order data models.

52. The method of claim 51, wherein the second-order controller module utilizes one or more generic interfaces to communicate with the controller module.

53. The method of claim 51, wherein the second-order controller module is implemented by the controller module when one of the second-order objects is selected from the displayed data object.

54. The method of claim 39, comprising the additional step of:

providing a second-order controller module that interfaces the application program with the one or more second-order objects using the data model.

55. The method of claim 54, wherein the second-order controller module utilizes one or more generic interfaces to communicate with the application program.

56. The method of claim 54, wherein the second-order controller module is implemented by the controller module when one of the second-order objects is selected from the displayed data object.

57. The method of claim 54, wherein the second-order controller module interfaces with the application program to display the list of functions.

58. The method of claim 39, comprising the additional step of:

providing a second-order controller module that interfaces the controller module with the one or more second-order objects using the data model.

59. The method of claim 58, wherein the second-order controller module utilizes one or more generic interface to communicate with the controller module.

60. The method of claim 58, wherein the second-order controller module is implemented by the controller module when one of the second-order objects is selected from the displayed data object.

24. A software architecture for use in a mobile device having a processor and a memory device, comprising:

an application program stored in the memory device and executed by the processor;

a first-order data object stored in the memory device in the form of a first-order data model, wherein the first-order data object includes a second-order data object;

a first-order controller module configured to interface the application program with the first-order data model, wherein the first-order controller module utilizes a generic interface to communicate with the application program; and

a second-order controller module configured to interface the application program with the second-order data object.

36. A method of extending a software interface in a mobile device having a plurality of application programs, comprising the steps of:

providing one or more generic interfaces;

providing a plurality of controller modules, each of which utilizes the one or more generic interfaces to communicate with the plurality of application programs; and

providing at least one data model associated with each application program, each data model configured to interface with one of the controller modules;

wherein the controller modules enable each application program to interface with each data model.

39. A method of adding functionality to an application program on a mobile device, comprising the steps of:

storing a data object associated with the application program on the mobile device in the form of a data model;

defining one or more second-order objects within the data model;

providing a controller module that interfaces the application program with the data model;

interfacing the application program with the controller module to display the data object;

selecting one of the second-order objects from the displayed data object; and

displaying a list of functions associated with the application program that may be performed on the selected second-order object.

41. The method of 39, wherein the controller module interfaces with the application program to display the list of functions.

61. A method of adding functionality to an e-mail messaging application, comprising the steps of:

storing an e-mail message data object in the form of an e-mail data model;

defining one or more second-order objects within the e-mail message data object;

providing a first-order controller module that interfaces the e-mail messaging application with the e-mail message data object through the e-mail data model;

providing a second-order controller module that interfaces the e-mail messaging application with the second-order objects through the e-mail data model;

interfacing the e-mail message data object with the first-order controller module to display the e-mail message;

selecting one of the second-order objects from within the displayed e-mail message data object;

interfacing the second-order controller module with the e-mail messaging application to display a list of functions associated with the e-mail messaging application that may be performed on the selected second-order object;

selecting a function from the displayed list of functions; and

executing the function.

62. The method of claim 61, wherein:

the first and second order controller modules also interface with one or more application programs other than the e-mail messaging application; and

the displayed list of functions includes one or more functions that are associated with one of the application programs other than the e-mail messaging application.

63. The method of claim 62, comprising the additional steps of:

determining whether the selected function is associated with the e-mail messaging application or one of the other application programs;

if the selected function is associated with the e-mail messaging application, then executing the function using the e-mail messaging application; and

if the selected function is associated with one of the other application programs, then (1) launching the other application program and (2) executing the function using the other application program.

64. The method of claim 61, wherein the one or more second-order objects are addresses within e-mail message data object.

65. The method of claim 61, wherein:

the one or more second-order objects are defined by a third-party; and

the second-order controller is designed by the third-party and installed by a user to upgrade the e-mail messaging application.