System and method for manipulating HAVi specification virtual key data

• US 20030070002A1
• Filed: 08/31/2001
• Published: 04/10/2003
• Est. Priority Date: 08/31/2001
• Status: Abandoned Application

• Current Assignee: Sharp Laboratories of America Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Original Assignee: Sharp Laboratories of America Incorporated (Hon Hai Precision Industry Co., Ltd.)
• Inventors: Fang, Henry
• Application Number:
  US09/944,685
• Publication Number:
  US 20030070002A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: H04L 12/2805 Home Audio Video Interoperability [HAVI] networks
• CPC Class Codes: H04L 12/2807 Exchanging configuration information on appliance services in a home automation network arrangements for maintenance or administration involving network analysis for automatically determining the actual topology of a network H04L41/12; hardware or software tools for network management using graphical user interfaces H04L41/22; address allocation H04L61/50
• CPC Class Codes: H04L 12/2809 indicating that an appliance service is present in a home automation network monitoring functionality H04L43/0817; discovery or management thereof, e.g. service location protocol [SLP] or web services, H04L67/51
• CPC Class Codes: H04L 12/282 based on user interaction within the home receiver circuitry for displaying additional information being controlled by a remote control apparatus H04N21/42204

Abstract

Methods are provided for the maintaining HEventRepresentation virtual keys in a device using HAVi specification protocols. The first method comprising: from a HAVi level two (L2) graphical user interface (GUI), accessing a JAR file; and, in response to accessing the JAR file from read only memory (ROM), retrieving virtual key information as a static class or data array. The second method comprises: from a HAVi L2 GUI, accessing a Java input/output (I/O) ResourceBundle; and, in response to accessing the ResourceBundle, retrieving virtual key information stored in an I/O device such as a hard disk or Flash memory. The third method comprises: from a HAVi L2 GUI, calling a Java native interface (JNI); at the JNI, using Java byte codes to call a storage driver; from the storage driver, accessing a mapped memory stored in binary format in an electrically erasable programmable read only memory (EEPROM); and, in response to accessing the mapped memory, retrieving virtual key information.

Claims

1. In a device using HAVi specification protocols, a method for maintaining HEventRepresentation virtual keys, the method comprising:

from a HAVi level two (L2) graphical user interface (GUI), accessing a JAR file; and

,

in response to accessing the JAR file, retrieving virtual key information.

2. The method of claim 1 wherein accessing a JAR file includes accessing a JAR file stored in read only memory (ROM).

3. The method of claim 2 wherein retrieving virtual key information includes retrieving virtual key information from a JAR file model selected from the group including static classes and data arrays.

4. The method of claim 3 wherein retrieving virtual key information in response to accessing the JAR file includes retrieving a HEventRepresentation application bundled with the virtual key information.

5. The method of claim 4 in which a first microprocessor machine using a first operating system is included;

the method further comprising;

receiving virtual key information as Java source code;

using a Java compiler, compiling the Java source code into Java virtual machine (JVM) byte codes for the first operating system; and

,

using jar tools, archiving the JVM byte codes into a JAR file stored in ROM.

6. The method of claim 5 further comprising:

receiving the HEventRepresentation application as Java source code;

using a Java compiler, compiling the Java source code into Java virtual machine (JVM) byte codes for the first operating system; and

,

using jar tools, archiving the JVM byte codes into a JAR file stored in ROM.

7. In a device using HAVi specification protocols, a method for maintaining HEventRepresentation virtual keys, the method comprising:

from a HAVi level two (L2) graphical user interface (GUI) accessing a Java input/output (I/O) ResourceBundle; and

,

in response to accessing the ResourceBundle, retrieving virtual key information.

8. The method of claim 7 wherein accessing the ResourceBundle includes using a ResourceBundle application program interface (API) to specify a property file.

9. The method of claim 8 in which a first microprocessor machine using a first operating system is included;

the method further comprising;

maintaining a HEventRepresentation application in a protocol associated with the first operating system; and

,

wherein accessing the ResourceBundle includes using a ResourceBundle API to specify a property file stored in a file system associated with the first microprocessor machine.

10. The method of claim 9 wherein using a ResourceBundle API to specify a property file stored in the file system includes specifying a property file stored in an input/output (I/O) device selected from the group of storage devices including hard disks and Flash memory.

11. The method of claim 10 further comprising:

receiving virtual key information as text-based properties attributes in a ResourceBundle property file;

integrating the virtual key information into a table of virtual key characteristics; and

,

storing the virtual key characteristics table as the ResourceBundle property file.

12. In a device using HAVi specification protocols, a method for maintaining HEventRepresentation virtual keys, the method comprising:

from a HAVi level two (L2) graphical user interface (GUI) calling a Java native interface (JNI);

at the JNI, using Java byte codes to call a storage driver;

from the storage driver, accessing a mapped memory; and

,

in response to accessing the mapped memory, retrieving virtual key information.

13. The method of claim 12 wherein accessing a mapped memory includes accessing a mapped memory stored in an electrically erasable programmable read only memory (EEPROM).

14. The method of claim 13 wherein retrieving virtual key information includes retrieving virtual key information from mapped memory in a binary format.

15. The method of claim 14 wherein using Java byte codes to call a storage driver at the JNI includes converting the Java byte code to binary format addresses;

and,

wherein accessing a mapped memory from the storage driver includes using the binary format addresses to access ASCII codes stored in the EEPROM.

16. The method of claim 15 in which a first microprocessor using a first operating system is included;

the method further comprising;

receiving the storage driver as first operating system machine codes; and

,

storing the storage driver as machine code.

17. The method of claim 16 further comprising:

receiving virtual key information as binary format code;

using the storage driver, cross-referencing the virtual key information with EEPROM addresses; and

,

storing the virtual key information in the EEPROM as machine code.