Method and system for specifying device interoperability source specifying renditions data and code for interoperable device team

• US 20050289509A1
• Filed: 06/08/2005
• Published: 12/29/2005
• Est. Priority Date: 06/08/2004
• Status: Active Grant

• Current Assignee: David E. Kahn
• Original Assignee: Covia Labs, Inc.
• Inventors: Bernstein, Bruce, Mirabella, Richard, Pieb, Wolfgang, Illowsky, Daniel, Wenocur, Michael, Tiberi, Richard, Sidney, Raymond
• Granted Patent: US 7,747,980 B2
• Time in Patent Office: Days
• US Class Current: 717/107
• CPC Class Codes: G06F 1/3203 Power management, i.e. event-based initiation of a power-saving mode
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2209/5015 Service provider selection
• CPC Class Codes: G06F 2221/2113 Multi-level security, e.g. mandatory access control
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/63 Image based installation; Cloning; Build to order
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5027 : the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/5044 : considering hardware capabilities
• CPC Class Codes: G06F 9/5072 : Grid computing
• CPC Class Codes: G06F 9/54 : Interprogram communication
• CPC Class Codes: G06F 9/541 : via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 : Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 65/1083 : In-session procedures
• CPC Class Codes: H04L 65/1094 : Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/80 : Responding to QoS
• 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/104 : Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1068 : Discovery involving direct consultation or announcement among potential requesting and potential source peers
• CPC Class Codes: H04L 67/1072 : Discovery involving ranked list compilation of candidate peers
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/24 : Negotiation of communication capabilities
• CPC Class Codes: H04L 69/328 : in the presentation layer [OSI layer 6]
• CPC Class Codes: H04N 21/41265 : having a remote control device for bidirectional communication between the remote control device and client device unidirectional remote control device H04N21/42204
• CPC Class Codes: Y02D 10/00 : Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/00 : Reducing energy consumption in communication networks

Abstract

System, device, method, and computer program and computer program products for providing communicating between devices having similar or dissimilar characteristics and facilitating seamless interoperability between them. Computer program software and methods of and systems and devices for sharing of content, applications, resources and control across similar and dissimilar permanently or intermittently connected electronic devices. Devices, systems, appliances, and the like communicating and/or interoperating within the framework provided. A interoperability source or DartSource method is provided for specifying program renditions and the code content and data needed for a packaged interoperability application. The interoperability source extends the languages constructs commonly used to specify single executable program targeted to a specific device, into a language which can also specify the procedures necessary for intelligent recruitment of teams of devices and the renditions needed so that there is a suitable rendition to send to run on each recruited device to carry out that device'"'"'s portion of the intended purpose of the application being specified.

Claims

1. A method for specifying a software application package of digitally encoded data, code and content, along with meta information in the form of data, code and content needed to carry out an intended purpose (intent) on one or more connected or intermittently connected devices;

the method comprising expressing in an interoperability software programming language one or more or any combination of the following;

(a) an object oriented framework and or library;

(b) source code for expressing the main code and data used to carry out the logic of the application, whether to be expressed as one executable image or an integrated set of executable images;

(c) digitally expressible resources; and

(d) system calls or instruction invocations necessary for connecting the logic of the application to the native underlying hardware and software of the device(s).

2. The method of claim 1, where the system calls or instructions are used to connect the logic of the application to one or more of the following native underlying hardware and software of the device:

(a) software engine;

(b) software operating system;

(c) communications subsystem;

(d) graphics subsystem;

(e) cryptographic subsystem;

(f) security subsystem;

(g) storage, audio rendering, and or input/output subsystems;

(h) native code expressed algorithms or procedures;

(i) media compression and or decompression subsystems;

(j) data processing or database processing;

(j) device specific unique functions and capabilities exposed through application program interfaces;

(k) device specific profile information for retrieving information about the resources, content and capabilities of the device;

(l) an event queue and associated event queue management subsystem to drive the synchronous and asynchronous operations of the application across devices;

(m) user interface, text, audio, video or other transcoding or rendering operations, and or general computation operations, and or general database operations;

(n) power management, suspend/resume, and or application level error recovery from intermittent connections through the use of events to drive the sharing and cooperative operations of software, data, content and state within and or between one or more cooperating devices;

(o) subsystems to dynamically save, configure, optimize and or send parts, packages of parts, procedures, executable images, or packages of executable images to or from physical storage, or to and from other connected devices; and

(p) any combination of these.

3. The method of claim 1, wherein the framework or library and/or source code includes class definitions and object implementations to carry out, encapsulate, order access to, and/or organize one or more of the native underlying software or hardware accessible which are listed in (a)-(p).

4. The method of claim 1, wherein the framework or library and/or source code includes class definitions and object implementations to provide a basis for conforming to specific runtime conventions used for event driven execution on or amongst one or more cooperating devices.

5. The method of claim 1, wherein the framework or library and/or source code includes class definitions and object implementations to ensure synchronous processing of events within an executable, and synchronized operation between devices by serializing the processing of events between parts of the software application distributed and then run on a set of cooperating devices.

6. The method of claim 1, wherein the framework comprises the DartFramework.

7. The method of claim 1, wherein source code is expressed at least in part in any one or more of:

a version or extension of the C programming language, a version or extension of the C++ programming language, a processor assembly language, an interoperability instruction set, the DartlnstructionSet, or any other suitable high-level, mid-level, low-level or machine language.

8. The method of claim 1, wherein the interoperability software programming language is an extension of an existing program language for expressing a single application executable image with one or more of the following extensions:

(i) semantics for specifying resources to be made into parts of the output package;

.

(ii) semantics for specifying independently executable procedures to be made into parts of the output package that is the result of processing the source;

(iii) semantics for referencing parts or ids of the parts;

(iv) semantics for specifying separately executable image starting points;

(v) semantics for referencing the separately executable images to be encapsulated into the output package or packages that is the result of processing of the source; and

(vi) any combination of these

9. The method of claim 8, wherein the existing application program language comprises the C or C++ programming language.

10. The method of claim 9, wherein one or more of the extensions are expressed as #pragma statements.

11. The method of claim 9, wherein one or more of the extensions are expressed as builtin functions with reserved names known to the software tools that parse and processes the source code expressed in the application program language.

12. The method of claim 9,wherein the extensions are parsed and processed by the DartTools.

13. The method of claim 11, wherein the extensions are parsed and processed by the DartTools.

14. The method of claim 1, wherein the digitally expressible resources are selected from the setoff resources consisting of one or more of:

(i) a JPEG, PNG, GIF, TIFF, MPEG, or any other picture, video, audio or other media formats resource;

(ii) a Darts or any other executable package format resource, whether intended to run on one or a plurality of devices;

(iii) a Content resource;

(iv) a Code resource;

(v) a Dataset resource;

(vi) a Database resource;

(vii) an Index resource;

(viii) any other digitally representable unit or package of information resource; and

(ix) any combination of theses resources.

15. The method of claim 1, wherein the interoperability software application is expressed as a Dart.

16. The method of claim 2, wherein the software engine is the DartEngine.

17. The method of claim 2, wherein the system calls or instructions used to connect the logic of the application are from an Interoperability Instruction Set.

18. The method of claim 17, wherein the Interoperability Instruction Set is the DartInstructionSet.

19. The method of claim 2, wherein the device specific unique functions and capabilities exposed through application program interfaces are implemented in the hardware abstraction layer of the DartEngine through the use of the OEM_BUILTIN_INSTRUCTION

20. The method of claim 2, wherein the device specific profile information for retrieving information about the resources, content and capabilities of the device are accessed from the hardware abstraction layer of the DartEngine through the use of the PROFILE_INSTRUCTION.

21. The method of claim 2, wherein the subsystems to dynamically save, configure, optimize and or send parts, packages of parts, procedures, executable images, or packages of executable images to or from physical storage, or to and from other connected devices carry out these operations according to a creationism procedure.

22. The method of claim 2, wherein the event queue management are carried out according to a Recruitment method.

23. The method of claim 2, wherein the power management, suspend/resume, and or application level error recovery are carried out using a LinearTasking method and/or a VerticalLayering method.

24. The method of claim 3, wherein the framework or library and or source code are the DartFramework.

25. The method of claim 4, wherein specific runtime conventions are the conventions of the DartRuntime method.

26. An apparatus for specifying a software application package of digitally encoded data, code and content, along with meta information in the form of data, code and content needed to carry out an intended purpose (intent) on one or more connected or intermittently connected devices;

the apparatus comprising;

a processor and a memory coupled with the processor; and

means accessible to the processor for expressing in an interoperability software programming language one or more or any combination of the following;

(a) an object oriented framework and or library;

(b) source code for expressing the main code and data used to carry out the logic of the application, whether to be expressed as one executable image or an integrated set of executable images;

(c) digitally expressible resources; and

(d) system calls or instruction invocations necessary for connecting the logic of the application to the native underlying hardware and software of the device(s).

27. A computer program product for use in conjunction with a computer system or information appliance, the computer program product comprising a computer readable storage medium and a computer program mechanism embedded therein, the computer program mechanism comprising:

a program module that directs the computer system or information appliance to function in a specified manner to specify an application package of digitally encoded data, code and/or content, optionally along with meta information in the form of data, code and/or content needed or desirable to carry out an intended purpose on one or more connected or intermittently connected devices, the program module including instructions for expressing in an interoperability software programming language one or more or any combination of the following;

(a) an object oriented framework and/or library;

(b) source code or executable code for expressing the main code and data used to carry out the logic of the application, whether to be expressed as one executable image or an integrated set of executable images;

(c) digitally expressible resources; and

(d) system calls or instruction invocations necessary for connecting the logic of the application to the native underlying hardware and software of the device(s).