Remote control inputs to Java applications

• US 20040031041A1
• Filed: 03/20/2003
• Published: 02/12/2004
• Est. Priority Date: 11/30/1998
• Status: Active Grant

• Current Assignee: Alok Prakash, Brian L. Windheim, Subha Pathial
• Original Assignee: Alok Prakash, Brian L. Windheim, Subha Pathial
• Inventors: Windheim, Brian L., Prakash, Alok, Pathial, Subha
• Granted Patent: US 7,302,693 B2
• Time in Patent Office: Days
• US Class Current: 719/321
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A method of delivering input from a device'"'"'s remote control to a Java™ application uses asynchronous method invocation in a processing device. The input from the remote control is captured in system-specific (native) code and delivered to a Java™ application asynchronously. This is achieved by calling an event method in the Java™ application in response to the received input signals. The event method is then executed to transfer the input signals from the remote control.

Claims

1. A method of delivering input signals from a remote control to a Java application in a processing device, said method comprising:

receiving the input signals of the remote control in a receiver of the processing device;

holding the received input signals in system-specific native code of the processing device;

calling-an event method in the Java application in response to the received input signals; and

executing the event method to transfer the input signals from the native code to the Java application.

2. A method according to claim 1, wherein the input signals are asynchronously delivered to the Java application.

3. A method according to claim 2, wherein the Java application is an applet in a hypertest mark-up language (HTML) page.

4. A method according to claim 3, wherein the event method calls on said applet using Java Native Interface/Java Remote Interface (JNI/JRI).

5. A method according to claim 4, comprising the further step of preventing the Java class object from being destroyed by the Java garbage collector.

6. A method according to claim 5, wherein the Java class object is prevented from being destroyed by storing a global reference in the native code.

7. A method according to claim 6, wherein the global reference is used to directly call event methods in said applet in response to the input signals.

8. A method according to claim 1, wherein the processing device is a set-top box, the remote control is an infrared remote control, and the receiver is an infrared receiver.

9. A tangible medium storing a program comprising instructions that, when executed, cause a processing device to carry out a method of delivering input signals from a remote control to a Java application in the processing device, said method comprising:

receiving the input signals of the remote control in a receiver of the processing device;

holding the received input signals in system-specific native code of the processing device;

calling an event method in the Java application in response to the received input signals; and

executing the event method to transfer the input signals from the native code to the Java application.

10. A tangible medium storing a program according to claim 9, wherein the input signals are asynchronously delivered to the Java application.

11. A tangible medium storing a program according to claim 10, wherein the Java application is an applet in a HTML page.

12. A tangible medium storing a program according to claim 11, wherein the event method calls on said applet using JNI/JRI.

13. A tangible medium storing a program according to claim 12, comprising the further step of preventing the Java class object from being destroyed by the Java garbage collector.

14. A tangible medium storing a program according to claim 13, wherein the Java class object is prevented from being destroyed by storing a global reference in the native code.

15. A tangible medium storing a program according to claim 14, wherein the global reference is used to directly call event methods in said applet in response to the input signals.

16. A tangible medium storing a program according to claim 9, wherein the processing device is a set-top box, the remote control is an infrared remote control, and the receiver is an infrared receiver.

17. A set-top box comprising:

a microprocessor;

a real-time operating system;

a plurality of input/output devices, including at least a transmitter and receiver for transferring input signals to and from a remote control; and

at least one Java application responsive to input signals received from said remote control via said receiver,

said real-time operating system having a dynamically linked library which traps the received input signals and calls a method in the Java application to transfer the input signals to the Java application.

18. A set-top box according to claim 17, wherein the dynamically linked library asynchronously delivers the input signals to the Java application.

19. A set-top box according to claim 18, wherein the Java application is an applet in a HTML page.

20. A set-top box according to claim 19, wherein the method calls on said applet using JNI/JRI.

21. A set-top box according to claim 20, comprising the further step of preventing the Java class object from being destroyed by the Java garbage collector.

22. A set-top box according to claim 21, wherein the Java class object is prevented from being destroyed by storing a global reference in the real-time operating system.

23. A set-top box according to claim 22, wherein the global reference is used to directly call the method in said applet in response to the input signals.

24. A set-top box according to claim 19, wherein the applet calls a script to execute application specific logic.