METHOD AND SYSTEM OF INVOKING MIDLETS FROM A WEB BROWSER ON A LOCAL DEVICE

• US 20070073835A1
• Filed: 04/26/2006
• Published: 03/29/2007
• Est. Priority Date: 09/28/2005
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Melby, Geir, Husa, Knut
• Granted Patent: US 8,271,611 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• 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/55 Push-based network services
• CPC Class Codes: H04M 1/72445 for supporting Internet browser applications

Abstract

Method and system for invoking MIDlets from a mobile web browser using the push registry mechanism provided by the application management software (AMS) of a local device, such as the push registry socket or push registry SMS, the local device including a mobile terminal, mobile telephone, smart phone, personal digital assistant (PDA), handset and the like.

Claims

1. A method for invoking MIDlets from a web browser on a local device, comprising:

performing an http request to a MIDlet on a local host using the push registry mechanism provided by the AMS of the local device; and

triggering an application management software (AMS).

2. The method of claim 1, further comprising:

registering the MIDlet socket invocations in the push registry;

issuing by a web browser an http request to a web server;

requesting, via the http request, a service that requires interaction with the MIDlet on the local device; and

containing in the http response a web page with a redirect URL to localhost.

3. The method of claim 2, further comprising containing in the redirect URL all the needed parameters for the MIDlet.

4. The method of claim 3, further comprising using, by the redirect URL, IP address 127.0.0.1.

5. The method of claim 3, wherein the AMS triggers the MIDlet.

6. The method of claim 5, further comprising:

reading, by the MIDlet, the contents buffered in the socket; and

decoding the http request.

7. The method of claim 6, further comprising upon completing, by the MIDlet, it tasks, returning with an http response containing a redirect URL to the web server.

8. The method of claim 7, wherein http request contains the result parameters from the MIDlet.

9. The method of claim 8, wherein the http response from the web server contains the result based on the MIDlet results.

10. The method of claim 1, further comprising determining, by the web server based on a user agent profile, whether the local device supports push registry socket or push registry SMS.

11. A method for invoking a video session from a web page using a MIDlet from a web browser on a local device without a result return to a web server, comprising:

performing an http request to a MIDlet on a local host using the push registry mechanism provided by the AMS of the local device;

triggering an application management software (AMS);

registering the MIDlet socket invocations in the push registry;

issuing by a web browser an http request to a web server;

requesting, via the http request, a service that requires interaction with the MIDlet on the local device;

connecting to a video server; and

commencing video streaming to the local device.

12. The method of claim 11, wherein the address to the video server are parts of the parameters passed to the MIDlet.

13. The method of claim 12, further comprising containing in the redirect URL all the needed parameters for the MIDlet.

14. The method of claim 13, further comprising using by the redirect URL, IP address 127.0.0.1.

15. The method of claim 13, wherein the AMS triggers the MIDlet.

16. The method of claim 15, further comprising reading, by the MIDlet, the contents buffered in the socket;

and

decoding the http request.

17. The method of claim 16, further comprising returning, upon completion of its tasks by the MIDlet, with an http response containing a redirect URL to the web server.

18. The method of claim 17, wherein http request contains the result parameters from the MIDlet.

19. The method of claim 18, wherein the http response from the web server contains the result based on the MIDlet results.

20. The method of claim 11, further comprising determining, by the web server, based on a user agent profile whether the local device supports push registry socket or push registry SMS.

21. A method of invoking MIDlets from a web browser on a local device based on supported push registry mechanisms, comprising:

performing an http request to the web server requesting a service that needs interaction with a MIDlet on the local device;

issuing, by a web browser, an http request to a web server;

determining, by the web server, based on the user agent profile whether the local device supports push registry socket or push registry SMS;

submitting, by the web server only if push registry SMS is supported, a binary SMS containing parameters and thus invoking the MIDlet;

returning, upon completion of MIDlet of its tasks, an SMS or http request containing the results from the task performed by the MIDlet; and

returning, by the web server, the http response to the web browser.

22. A system for invoking MIDlets from a web browser on a local device, comprising:

a MIDlet client;

a web browser for use in a local device;

a web server located on a server platform;

a WAP gateway, the local device being coupled via a TCP/IP connection to the WAP gateway, the WAP gateway being coupled to the web server on the server platform via a TCP/IP connection.

23. The system of claim 22, wherein the local device is one selected from the group consisting of a mobile terminal, mobile telephone, a smart phone, a personal digital assistant (PDA) and a handset.

24. The system of claim 22, for use in an authentication session.

25. The system of claim 22, further comprising a video server on the server platform.

26. The system of claim 22, further comprising an SMS gateway, the local device being coupled to the SMS gateway via TCP/IP interface which is coupled to the server platform via the TCP/IP interface.