System and method for implementing communication middleware for mobile "Java" computing

• US 20030233465A1
• Filed: 03/14/2003
• Published: 12/18/2003
• Est. Priority Date: 06/12/2002
• Status: Abandoned Application

• Current Assignee: Vuico LLC
• Original Assignee: Vuico LLC
• Inventors: Nguyen, Man, Le, Vui, Vu, Tao
• Application Number:
  US10/389,512
• Publication Number:
  US 20030233465A1
• Time in Patent Office: Days
• US Class Current: 709/231
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method of implementing a client side remote method call from a Java-enabled mobile device includes executing an instruction at the mobile device to open a connection at a Host URL. The Host URL includes a server side object of the remote method call. An output stream is opened via the connection. Remote method call parameters are written to the server side remote method call object at the Host URL via the output stream. An input stream is opened via the connection for receiving return data from the Host URL. Lastly, the return data is queried for any occurrence of errors in the remote method call request in response the server side remote method call object and the remote method call parameters, wherein responsive to a detection of errors, remote method call error recovery process is executed for performing a restart of the remote method call in response to at least one recovery query prior to throwing a remote exception which terminates the remote method call.

Claims

1. A method of implementing a client side remote method call from a Java-enabled mobile device, comprising:

executing an instruction at the mobile device to open a connection at a Host URL, the Host URL including a server side object of the remote method call;

opening an output stream via the connection;

writing remote method call parameters to the server side remote method call object at the Host URL via the output stream;

opening an input stream via the connection for receiving return data from the Host URL; and

querying the return data for any occurrence of errors in the remote method call request in response the server side remote method call object and the remote method call parameters, wherein responsive to a detection of errors, executing a remote method call error recovery process for performing a restart of the remote method call in response to at least one recovery query prior to throwing a remote exception which terminates the remote method call.

2. The method of claim 1, wherein the connection is an HTTP connection.

3. The method of claim 1, wherein the remote method call parameters include an object id, method id, and method arguments of the server side remote method call object.

4. The method of claim 3, wherein writing includes serializing the method arguments.

5. The method of claim 1, wherein responsive to an affirmative recovery response of the at least one recovery query, the remote method call error process restarts the remote method call over at the step of executing the instruction at the mobile device to open a connection at the Host URL.

6. The method of claim 1, wherein the remote exception is a lightweight object request broker (IORB) remote exception.

7. The method of claim 1, wherein responsive to non-detection of errors, said method further comprising:

querying at least one selected from the group consisting of a connection status query, an input stream status query, and an input stream read version validity query, wherein responsive to a negative or invalid status of a corresponding query, executing the remote method call error recovery process for performing a restart of the remote method call in response to the at least one recovery query prior to throwing the remote exception which terminates the remote method call.

8. The method of claim 1, wherein the remote method call error recovery process includes recovery queries, the recovery queries including at least one selected from the group consisting of a task abort query, a retry enabled query, and a retry limit query.

9. The method of claim 8, wherein responsive to a result of the task abort query being abort, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

10. The method of claim 8, wherein responsive to a result of the task abort query being not to abort, the remote method call error recovery process further including the retry enabled query.

11. The method of claim 8, wherein responsive to a result of the retry enabled query being non-enabled, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

12. The method of claim 8, wherein responsive to a result of the retry enabled query being enabled, the remote method call error recovery process further includes incrementing a retry count in response to the retry being enabled.

13. The method of claim 12, further wherein the retry limit query occurs subsequent to the retry enabled query and the incrementing of the retry count, wherein responsive to the retry count not exceeding a maximum number of retry attempts, the remote method call error recovery process further including executing a sleep mode prior to restarting the remote method call.

14. The method of claim 13, wherein the sleep mode includes a pause on the order of 1000 ms.

15. The method of claim 13, still further wherein responsive to the retry count exceeding the maximum number of retry attempts, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

16. The method of claim 8, wherein the remote method call error recovery process further includes executing a sleep mode prior to restarting the remote method call.

17. A Java-enabled mobile apparatus for use in a wireless mobile messaging system, the mobile device configured to perform a method of implementing a client side remote method call, wherein the method comprising:

executing an instruction at the mobile device to open a connection at a Host URL, the Host URL including a server side object of the remote method call;

opening an output stream via the connection;

writing remote method call parameters to the server side remote method call object at the Host URL via the output stream;

opening an input stream via the connection for receiving return data from the Host URL; and

querying the return data for any occurrence of errors in the remote method call request in response the server side remote method call object and the remote method call parameters, wherein responsive to a detection of errors, executing a remote method call error recovery process for performing a restart of the remote method call in response to at least one recovery query prior to throwing a remote exception which terminates the remote method call.

18. The apparatus of claim 17, wherein the connection is an HTTP connection.

19. The apparatus of claim 17, wherein the remote method call parameters include an object id, method id, and method arguments of the server side remote method call object.

20. The apparatus of claim 19, wherein writing includes serializing the method arguments.

21. The apparatus of claim 17, wherein responsive to an affirmative recovery response of the at least one recovery query, the remote method call error process restarts the remote method call over at the step of executing the instruction at the mobile device to open a connection at the Host URL.

22. The apparatus of claim 17, wherein the remote exception is a lightweight object request broker (IORB) remote exception.

23. The apparatus of claim 17, wherein the method further comprising in response to non-detection of errors, querying at least one selected from the group consisting of a connection status query, an input stream status query, and an input stream read version validity query, wherein responsive to a negative or invalid status of a corresponding query, executing the remote method call error recovery process for performing a restart of the remote method call in response to the at least one recovery query prior to throwing the remote exception which terminates the remote method call.

24. The apparatus of claim 17, wherein the remote method call error recovery process includes recovery queries, the recovery queries including at least one selected from the group consisting of a task abort query, a retry enabled query, and a retry limit query.

25. The apparatus of claim 24, wherein responsive to a result of the task abort query being abort, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

26. The apparatus of claim 24, wherein responsive to a result of the task abort query being not to abort, the remote method call error recovery process further including the retry enabled query.

27. The apparatus of claim 24, wherein responsive to a result of the retry enabled query being non-enabled, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

28. The apparatus of claim 24, wherein responsive to a result of the retry enabled query being enabled, the remote method call error recovery process further includes incrementing a retry count in response to the retry being enabled.

29. The apparatus of claim 28, further wherein the retry limit query occurs subsequent to the retry enabled query and the incrementing of the retry count, wherein responsive to the retry count not exceeding a maximum number of retry attempts, the remote method call error recovery process further including executing a sleep mode prior to restarting the remote method call.

30. The apparatus of claim 29, still further wherein responsive to the retry count exceeding the maximum number of retry attempts, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

31. The apparatus of claim 24, wherein the remote method call error recovery process further includes executing a sleep mode prior to restarting the remote method call.

32. A computer program stored on a computer readable medium for implementing a client side remote method call from a Java-enabled device, the computer program processable by a processor of the Java-enabled device for causing the processor to:

execute an instruction at the mobile device to open a connection at a Host URL, the Host URL including a server side object of the remote method call;

open an output stream via the connection;

write remote method call parameters to the server side remote method call object at the Host URL via the output stream;

open an input stream via the connection for receiving return data from the Host URL; and

query the return data for any occurrence of errors in the remote method call request in response the server side remote method call object and the remote method call parameters, wherein responsive to a detection of errors, execute a remote method call error recovery process for performing a restart of the remote method call in response to at least one recovery query prior to throwing a remote exception which terminates the remote method call.

33. The computer program of claim 32, wherein the connection is an HTTP connection.

34. The computer program of claim 32, wherein the remote method call parameters include an object id, method id, and method arguments of the server side remote method call object.

35. The computer program of claim 34, wherein writing includes serializing the method arguments.

36. The computer program of claim 32, wherein responsive to an affirmative recovery response of the at least one recovery query, the remote method call error process restarts the remote method call over at the step of executing the instruction at the mobile device to open a connection at the Host URL.

37. The computer program of claim 32, wherein the remote exception is a lightweight object request broker (IORB) remote exception.

38. The computer program of claim 32, wherein responsive to non-detection of errors, said computer program further for causing the processor to:

perform at least one query selected from the group consisting of a connection status query, an input stream status query, and an input stream read version validity query, wherein responsive to a negative or invalid status of a corresponding query, executing the remote method call error recovery process for performing a restart of the remote method call in response to the at least one recovery query prior to throwing the remote exception which terminates the remote method call.

39. The computer program of claim 32, wherein the remote method call error recovery process includes recovery queries, the recovery queries including at least one selected from the group consisting of a task abort query, a retry enabled query, and a retry limit query.

40. The computer program of claim 39, wherein responsive to a result of the task abort query being abort, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call, and wherein responsive to a result of the task abort query being not to abort, the remote method call error recovery process further including the retry enabled query.

41. The computer program of claim 39, wherein responsive to a result of the retry enabled query being non-enabled, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call, and wherein responsive to a result of the retry enabled query being enabled, the remote method call error recovery process further includes incrementing a retry count in response to the retry being enabled.

42. The computer program of claim 41, further wherein the retry limit query occurs subsequent to the retry enabled query and the incrementing of the retry count, wherein responsive to the retry count not exceeding a maximum number of retry attempts, the remote method call error recovery process further including executing a sleep mode prior to restarting the remote method call, and still further wherein responsive to the retry count exceeding the maximum number of retry attempts, the remote method call error recovery process throws the remote exception, thereby terminating the remote method call.

43. The computer program of claim 39, wherein the remote method call error recovery process further includes executing a sleep mode prior to restarting the remote method call.