Device interoperability format rule set and method for assembling interoperability application package

• US 7,703,073 B2
• Filed: 06/08/2005
• Issued: 04/20/2010
• Est. Priority Date: 06/08/2004
• Status: Expired due to Fees

• 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
• Primary Examiner(s): Dam; Tuan Q
• Assistant Examiner(s): DAO, THUY CHAN
• Application Number:
  US11/148,981
• Publication Number:
  US 20050289527A1
• Time in Patent Office: 1,777 Days
• Field of Search: 717/101
• US Class Current: 717/121
• 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

Device interoperability format and method for assembling self-contained executable device interoperability software application package conforming to an interoperability format that is completely self-contained and sufficient to carry out an intended purpose of the application on a plurality of connected or intermittently connected devices, the executable device interoperability software application package when executed allowing the plurality of devices to interoperate with each other. Method of forming a linearly contiguous binary encoded part images, and packaging the formed part images together into an executable device interoperability software application package. Computer program product for execution on a computer, information appliance, or other device. Data structure for self-contained executable device interoperability software application package.

Claims

1. A device implemented method for forming an adaptive cross-device, self-distributing executable device interoperability application package for a software application, the method comprising:

forming at least one linearly contiguous binary encoded part image to conform to a single linear binary format of digitally encoded code, data and content, including at least one part image, the device interoperability application package being self-contained and sufficient and having all the executable code data and content elements needed to;

(i) execute and run as part of the interoperability application on all devices chosen by the interoperability application to be used to carry out the interoperability application'"'"'s purpose and including a main program code part of the interoperability application and a main program data or content part of the interoperability application;

(ii) dynamically choose which devices have the resources currently available as needed by the application to be formed into a device team to carry out the purpose of the application;

(iii) assemble the needed parts of the interoperability application package into a device specific custom adaptive cross-device executable software application package conforming to the same format package for each device chosen by the application to be part of the device team;

(iv) distribute the device specific custom adaptive packages to each needed device of the device team;

(v) adapt to displays and controls and run on each device in the device team; and

(vi) carry out services as part of the application on each device of the device team once it has been distributed and run on each device;

forming any additional necessary linearly contiguous part images comprised of combinations of binary encoded resources or program elements that are to be used to dynamically identify devices that may be needed based on a discovered device characteristics, dynamically form other interoperability relationships, load, select, execute or be processed as part of the executable device interoperability application package; and

packaging the formed at least one linearly contiguous binary encoded part image and the any additional necessary linearly contiguous part images together into the executable device interoperability software application package in a form where the part images can be deterministically located and independently executable part images identified, loaded, and executed on a connected or intermittently connected device, the executable device interoperability software application package conforming to an interoperability format of digitally encoded data, code and content, that is completely self-contained and sufficient to carry out an intended purpose of the application on a plurality of connected or intermittently connected devices; and

wherein the executable device interoperability software application package is self-contained and sufficient and when executed permits the plurality of teamed devices to interoperate with each other without additional executable software.

2. The method as in claim 1, wherein the formed at least one linearly continuous binary encoded part image consists of exactly one linearly continuous binary encoded part image that contains the program main code part of the application.

3. The method of claim 2, wherein:

the main code is comprised of executable instructions from an interoperability instruction set and content rendition instructions and content rendition data, and the main code instruction data address fields reference data assigned to one linear data address space in the main data part; and

the content rendition instructions are adapted to execute at different times on different devices sharing the exact same content rendition data and stored in location so that changes made in one rendition are the same as changes made in other renditions.

4. The method of claim 2, wherein the at least one linearly continuous binary encoded part image further contains a simple table of records for each of the independently executable images and a simple table of records for each of the parts belonging to a particular independently executable image;

and the table of independently executable images contains simple table records with the part identifier of a fixed field linear look-up table for finding executable image parts given its identifier.

5. The method of claim 4, wherein the records of the table of independently executable images contains one or more of the following fields in any combination:

(i) the smallest linear address range of the main code part that contains all the code needed for the independently executable image;

(ii) the smallest linear address range of the main data part that contains all the data needed for the independently executable image; and

(iii) the requested or required amount of memory or other resources that is to be reserved to be used during execution of the independently executable image.

6. The method as in claim 2, wherein the Dart format comprises a structure and rule for assembling the application package which encapsulates all the code, data, and content needed for execution of the interoperability application which can then be loaded and run on devices which have a running player engine.

7. The method as in claim 1, wherein the formed at least one linearly continuous binary encoded part image consists of exactly one linearly continuous binary encoded part image that contains the program main data part of the application.

8. The method as in claim 7, wherein the at least one linearly continuous binary encoded part image further includes a table of records for each of the independently executable images, and a table of records for each of the parts belonging to a particular independently executable image.

9. The method as in claim 8, wherein the formed additional necessary linearly contiguous part images include:

(a) a Dart or a plurality of Darts or a Dart procedure or a plurality of Dart procedures; and

(b) pictures, video, image, audio, sound or any other media capable of being rendered.

10. The method as in claim 8, wherein the method further includes forming untagged meta information and the packaging includes packaging the formed at least one linearly contiguous binary encoded part image and the any necessary linearly contiguous part images and the formed meta information together in a form where part images can be deterministically located and independently executable images identified, loaded, and executed;

and the formed meta information includes;

(a) a table for finding parts given its identifier;

(b) a first information used to find the table of parts;

(c) a second information needed to load and execute the linearly contiguous part images; and

(d) a third information used to find the list of independently executable images.

11. The method as in claim 7, wherein the interoperability formatted executable device interoperability software application package comprises a structure and rule for assembling the application package which encapsulates all the code, data, and content needed for execution of the interoperability application which can then be loaded and run on devices which have a running player engine.

12. The method as in claim 7, wherein the at least one linearly continuous binary encoded part image further includes at least one procedure part used by other devices to report their suitability for being member of a team of devices in accomplishing an application purpose.

13. The method as in claim 7, wherein the application package contains in a single linear binary package all code and data needed to distribute, run, adapt and carry out all aspects of the interoperability application.

14. The method as in claim 13, wherein the application code running on each device is repackaged and distributed directly from the parts of the initial single linear package using code to manage this repackaging and distribution from the same single linear binary package.

15. The method of claim 1, wherein the following linearly contiguous binary encoded part images are also formed and the content assembled and packaged into the executable device interoperability software application package:

a Dart or a plurality of Darts or a Dart procedure or a plurality of Dart procedures;

content including content selected from the set of content items consisting of pictures, audio, video, or other multimedia content or animations; and

virtual pointer data for use in maintaining a dynamically resized data structure in addressing multiple independent address spaces.

16. The method of claim 15, wherein one or more of the following meta information are also formed:

(i) signature information;

(ii) keywords or other information to be accessed to identify the names, types, content and or uses of the software application package;

(iii) parameters for list items or table items;

(iv) virtual pointer parameters;

(v) security checksums, and or signatures, and or certificates and or hashes; and

(vi) unique identifiers.

17. The method of claim 15, wherein the one or more linearly contiguous binary encoded part images that are formed include virtual pointer data for executable code, and the virtual pointer data includes any number of address ranges followed by the data instance values of the address range so as to efficiently represent a possibly sparse list of ranges of data values;

and wherein the virtual pointer data supporting multiple independent address spaces for use by each program, and allowing the number of real memory pages and the sizes of each real memory page to vary depending on the physical size of available real main memory in each device, the speed and performance characteristics of the main memory in each device, and the expected access patterns of specific programs to specific data sets.

18. The method of claim 15, wherein the virtual pointer data enables parts of a runtime for the application to be automatically sent to run on other devices as part of the inter-device interoperability executable application.

19. The method of claim 1, wherein the steps are performed to assemble a ready for execution inter-device interoperability application by a plurality of heterogeneous devices by tools embodied in an interoperability compiler, an interoperability linker and or an interoperability master player.

20. The method of claim 1, wherein any one, any combination, or all of the following are true:

(i) the format for the storing a software application package is a DartFormat;

(ii) the software application package is a Dart;

(iii) the parts are DartParts;

(iv) the table of independently executable images is a Dart RenditionsTable;

(v) the table of records for each of the parts is a Dart RenditionTable;

(vi) the table for finding parts given its identifier is a Dart PartTable; and

(vii) the Information used to find the table of parts is the DartTrailer and its known size, fields, and location in the DartFormat image.

21. The method of claim 1, wherein the main code is comprised of executable instructions from an interoperability Turing complete instruction set plus additional low-level instructions for carrying out discovery and sending of customized packages to run as part of the application on teamed devices.

22. The method of claim 21, wherein the main code instruction branching fields reference other code assigned to one linear address space in the main code part, wherein the linear address space is stored in a way intended to foster renditioning to allow the segmenting of the claimed interoperability application into a plurality of tightly integrated yet separately executable programs so that individual renditions may be chosen during a device recruitment process to be sent to run on other devices to provide coordinated access to the capabilities and content of individual devices.

23. The method as in claim 22, wherein the executable device interoperability software application package is adapted to provide renditioning on a plurality of different interconnected devices, and content to be renditioned on different unique heterogeneous devices may be adapted to the different unique heterogeneous devices without having to have executable images for every unique device or a package of separate executable images for every unique device.

24. The method of claim 1, wherein:

the interoperability instruction set is the Dart Interoperability Instruction set that provides for self-contained interoperability application packages and players that can intelligently and securely self-distribute and adapt themselves across a wide range of heterogeneous devices and protocols.

25. The method of claim 24, wherein the Dart interoperability instruction set comprises an interoperability instruction set that is designed and optimized to perform all necessary interoperability operations as instructions that are dispatched to functions which are compiled or assembled into the native code of the device processor.

26. The method of claim 25, wherein the interoperability instruction-set includes the following;

(i) device recruitment instructions, (ii) profile instructions, (iii) synchronizing instructions, (iv) user-interface and graphics instructions, (v) connection and session management instructions, (vi) content rendition instructions, (vii) application parts management instructions, (viii) text and symbol parsing instructions, (ix) virtual pointer management instructions.

27. The method of claim 26, wherein the interoperability instruction-set further includes the following (x) power management instructions, (xi) storage instructions, (xii) creationism instructions, (xiii) cryptographic large number math instructions, and (xiv) instructions that when executed expose unique capabilities of the device to Darts and thereby to any other Dart compatible devices.

28. The method as in claim 1, wherein the code data and content elements are formed as a linear database of all the necessary parts.

29. A computer program product embodied on a tangible computer readable medium 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 for forming an adaptive cross-device, self-distributing executable device interoperability application package for a software application, the program module including instructions for;

forming at least one linearly contiguous binary encoded part image to conform to a single linear binary format of digitally encoded code, data and content, including at least one part image, the device interoperability application package being self-contained and sufficient and having all the executable code data and content elements needed to;

(i) execute and run as part of the interoperability application on all devices chosen by the interoperability application to be used to carry out the interoperability application'"'"'s purpose and including a main program code part of the interoperability application and a main program data or content part of the interoperability application;

(ii) dynamically choose which devices have the resources currently available as needed by the application to be formed into a device team to carry out the purpose of the application;

(iii) assemble the needed parts of the interoperability application package into a device specific custom adaptive cross-device executable software application package conforming to the same format package for each device chosen by the application to be part of the device team;

(iv) distribute the device specific custom adaptive packages to each needed device of the device team;

(v) adapt to displays and controls and run on each device in the device team; and

(vi) carry out services as part of the application on each device of the device team once it has been distributed and run on each device;

forming any additional necessary linearly contiguous part images comprised of combinations of binary encoded resources or program elements that are to be used to dynamically identify devices that may be needed based on a discovered device characteristics, dynamically form other interoperability relationships, load, select, execute or be processed as part of the executable device interoperability application package; and

packaging the formed at least one linearly contiguous binary encoded part image and the any additional necessary linearly contiguous part images together into the executable device interoperability software application package in a form where the part images can be deterministically located and independently executable part images identified, loaded, and executed on a connected or intermittently connected device, the executable device interoperability software application package conforming to an interoperability format of digitally encoded data, code and content, that is completely self-contained and sufficient to carry out an intended purpose of the application on a plurality of connected or intermittently connected devices wherein the executable device interoperability software application package is self-contained and sufficient and when executed permits the plurality of teamed devices to interoperate with each other without additional executable software.

30. A data structure embodied on a tangible computer readable medium for storing an executable device interoperability software application package conforming to an interoperability format of digitally encoded data, code and content, that is completely self contained and sufficient to carry out an intended purpose of the application when executed on one or more connected or intermittently connected devices, the executable device interoperability software application package when executed allowing the plurality of devices to interoperate with each other, the data structure comprising:

at least one linearly contiguous binary encoded part image to conform to a single linear binary format of digitally encoded code, data and content, including at least one part image, the device interoperability application package being self-contained and sufficient and having all the executable code data and content elements needed to;

(i) execute and run as part of the interoperability application on all devices chosen by the interoperability application to be used to carry out the interoperability application'"'"'s purpose and including a main program code part of the interoperability application and a main program data or content part of the interoperability application;

(ii) dynamically choose which devices have the resources currently available as needed by the application to be formed into a device team to carry out the purpose of the application;

(iii) assemble the needed parts of the interoperability application package into a device specific custom adaptive cross-device executable software application package conforming to the same format package for each device chosen by the application to be part of the device team;

(iv) distribute the device specific custom adaptive packages to each needed device of the device team;

(v) adapt to displays and controls and run on each device in the device team; and

(vi) carry out services as part of the application on each device of the device team once it has been distributed and run on each device;

any additional necessary linearly contiguous part images comprised of combinations of binary encoded resources or program elements that are to be used to dynamically identify devices that may be needed based on a discovered device characteristics, dynamically form other interoperability relationships, load, select, execute or be processed as part of the executable device interoperability application package; and

the data structure packaging the parts together into an executable device interoperability software application package in a form where part images can be deterministically located and independently executable images identified, loaded, and executed on a connected device or intermittently connected device; and

the executable device interoperability software application package conforming to an interoperability format of digitally encoded data, code and content, that is completely self-contained and sufficient to carry out an intended purpose of the application on a plurality of connected or intermittently connected devices; and

wherein the executable device interoperability software application package is self-contained and sufficient and when executed permits the plurality of teamed devices to interoperate with each other without additional executable software.

31. The data structure as in claim 30, wherein the at least one linearly continuous binary encoded part image contains each of a main code part of the interoperability formatted executable device interoperability software application package, a main data part of the interoperability formatted executable device interoperability software application package, a table of records for each of the independently executable images, and a table of records for each of the parts belonging to a particular independently executable image.

32. The data structure as in claim 31, wherein the interoperability formatted executable device interoperability software application package comprises a structure and rule for assembling the application package which encapsulates all the code, data, and content needed for execution of the interoperability application which can then be loaded and run on devices which have a running player engine.

33. The data structure as in claim 32, wherein the data structure further includes meta information and the packaging the data structure packaging the parts and meta information together in a form where part images can be deterministically located and independently executable images identified, loaded, and executed;

and the formed meta information further includes;

(a) a table for finding parts given its identifier;

(b) a first information used to find the table of parts;

(c) a second information needed to load and execute the linearly contiguous part images; and

(d) a third information used to find the list of independently executable images.