System and method of representing data entities of standard device applications as built-in components

• US 7,805,735 B2
• Filed: 02/09/2006
• Issued: 09/28/2010
• Est. Priority Date: 04/18/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Vitanov, Kamen, Qing, Richard, Bateman, Cameron, Wallis, Ken, Shenfield, Michael, Bibr, Viera
• Primary Examiner(s): Truong; Lechi
• Application Number:
  US11/350,098
• Publication Number:
  US 20060251047A1
• Time in Patent Office: 1,692 Days
• Field of Search: 719/328, 709/202, 717/100
• US Class Current: 719/328
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata

Abstract

A system and method for developing a standard data component for coupling with a plurality of components of a component-based application to access a stored data entity of a non-component-based native application, the applications for executing in a runtime environment of a device. The system and method comprises an application module configured for storing a model of the component-based application including features of data and message component definitions expressed in a structured definition language. Also included is a native module configured for storing properties of the data entity of the native application and a standard module for generating the standard data component definition based on the features of the component-based application and the properties of the data entity of the native application. The standard data component definition is expressed in the structured definition language.

Claims

1. A system for developing a standard data component for coupling with a plurality of components of a component-based application to access a stored data entity of a non-component-based native application, the applications having the plurality of components including metadata descriptors expressed in a structured definition language for defining execution of the application in a runtime environment of a device, the system comprising:

a computer readable memory for storing instructions; and

a processor for executing the instructions stored in the computer readable memory, the instructions, when executed by the processor, providing;

an application module configured for storing a model of the component-based application including features of data and message metadata descriptors expressed in the structured definition language;

a native module configured for storing properties of the data entity of the native application; and

a standard module for generating the standard data component definition as additional metadata descriptors based on the features of the component-based application and the properties of the data entity of the native application, the additional metadata descriptors of the standard data component definition being expressed in the structured definition language,

wherein the application module is configured for including a reference to the standard data component definition in the metadata descriptors of the plurality of components, such that the standard data component definition is external to the metadata descriptors of the plurality of components and therefore the standard data component definition is configured for remote access through the reference;

wherein the additional metadata descriptors of the standard data component include an ability to invoke APIs of the non-component-based native application for accessing the stored data entity.

2. The system of claim 1, wherein the properties of the data entity are selected from the group comprising:

a description of a data structure of the native application;

a description of a communication interface of a respective application program interface of the native application; and

a description of the data structure used by the device for storing the data entity in a device memory.

3. The system of claim 2, wherein the additional metadata descriptors of the standard data component include an ability to directly access the stored data entity through a data request to the device memory.

4. The system of claim 2, wherein the plurality of components are selected from the group comprising:

a data component, a message component, a workflow component, and a presentation component.

5. The system of claim 4, wherein the additional metadata descriptors are configurable to be operatively coupled to the plurality of components through the metadata descriptors of the plurality of components.

6. The system of claim 2 further comprising a runtime emulator module for emulating the runtime environment of the device during development of the standard data component, the standard data component configured for providing a plurality of the component-based applications access to the data entity of the native application.

7. The system of claim 6, wherein the application module is configured for including the additional metadata descriptors of the standard data component in the metadata descriptors of the component-based application model.

8. The system of claim 1 further comprising the standard module configured for

generating a runtime environment module for including the additional metadata descriptors of the standard data component.

9. A method for developing a standard data component for coupling with a plurality of components of a component-based application to access a stored data entity of a non-component-based native application, the applications having the plurality of components including metadata descriptors expressed in a structured definition language for defining execution of the application in a runtime environment of a device, the method comprising executing instructions stored in a computer readable memory, the instructions for:

accessing a model of the component-based application including features of data and message component metadata descriptors expressed in the structured definition language;

accessing properties of the data entity of the native application; and

generating the standard data component definition as additional metadata descriptors based on the features of the component-based application and the properties of the data entity of the native application, the additional metadata descriptors of the standard data component definition being expressed in the structured definition language; and

including a reference to the standard data component definition in the metadata descriptors of the plurality of components, such that the standard data component definition is external to the metadata descriptors of the plurality of components and therefore the standard data component definition is configured for remote access through the reference;

wherein the additional metadata descriptors of the standard data component include an ability to invoke APIs of the non-component-based native application for accessing the stored data entity.

10. The method of claim 9, wherein the properties of the data entity are selected from the group comprising:

a description of a data structure of the native application;

a description of a communication interface of a respective application program interface of the native application; and

a description of the data structure used by the device for storing the data entity in a device memory.

11. The method of claim 10 further comprising the step of emulating the runtime environment of the device during development of the standard data component, the standard data component configured for providing a plurality of the component-based applications access to the data entity of the native application.

12. The method of claim 11, wherein the application module is configured for including the additional metadata descriptors of the standard data component in the metadata descriptors of the component-based application model.

13. The method of claim 10, wherein the additional metadata descriptors of the standard data component include the ability to directly access the stored data entity through a data request to the device memory.

14. The method of claim 10, wherein the plurality of components are selected from the group comprising:

a data component, a message component, a workflow component, and a presentation component.

15. The method of claim 14, wherein the additional metadata descriptors are configurable to be operatively coupled to the plurality of components through the metadata descriptors of the plurality of components.

16. The method of claim 9 further comprising a step of generating a runtime environment module for including the additional metadata descriptors of the standard data component.

17. A computer program product for developing a standard data component for coupling with a plurality of components of a component-based application to access a stored data entity of a non-component-based native application, the applications having the plurality of components including metadata descriptors expressed in a structured definition language for defining execution of the application in a runtime environment of a device, the computer program product comprising:

a computer readable-memory;

an application module stored on the computer readable memory and configured for storing a model of the component-based application including features of data and message metadata descriptors expressed in the structured definition language;

a native module stored on the computer readable memory and configured for storing properties of the data entity of the native application; and

a standard module stored on the computer readable memory for generating the standard data component definition as additional metadata descriptors based on the features of the component-based application and the properties of the data entity of the native application, the additional metadata descriptors of the standard data component definition being expressed in the structured definition language;

wherein the application module is configured for including a reference to the standard data component definition in the metadata descriptors of the plurality of components, such that the standard data component definition is external to the metadata descriptors of the plurality of components and therefore the standard data component definition is configured for remote access through the reference;

wherein the additional metadata descriptors of the standard data component include the ability to invoke APIs of the non-component-based native application for accessing the stored data entity.