Method and system of invoking MIDlets from a web browser on a local device

• US 8,271,611 B2
• Filed: 04/26/2006
• Issued: 09/18/2012
• Est. Priority Date: 09/28/2005
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Husa, Knut Eilif, Melby, Geir
• Primary Examiner(s): Avellino, Joseph
• Assistant Examiner(s): BARON, JAMES T
• Application Number:
  US11/380,355
• Publication Number:
  US 20070073835A1
• Time in Patent Office: 2,337 Days
• Field of Search: 709/219
• US Class Current: 709/219
• 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 a push registry mechanism provided by the application management software (AMS) of the local device;

triggering, by the AMS, the MIDlet,

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;

containing in an http response a web page with a redirect URL to local host; and

,

containing in the redirect URL all the needed parameters for the MIDlet.

2. The method of claim 1, further comprising:

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

decoding the http request.

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

4. The method of claim 3, wherein http request contains the result parameters from the MIDlet.

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

6. 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.

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

7. 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 a push registry mechanism provided by the application management software (AMS) of the local device;

triggering by the AMS, the MIDlet;

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 to the web server, a service that requires interaction with the MIDlet on the local device;

decoding the http request;

returning, upon completion of its tasks by the MlDlet, with an http response containing a redirect URL to the web server, the redirect URL containing all the needed parameters for the MIDlet, wherein the http response from the web server contains the result based on the MIDlet results;

connecting to a video server;

wherein the address to the video server are parts of the parameters passed to the MIDlet; and

,

commencing video streaming to the local device.

8. The method of claim 7, 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.

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

9. A system for invoking MlDlets 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, wherein the web browser for use on a local device includes;

a means for performing an http request to a MIDlet on the web server using a push registry mechanism provided by an application management software (AMS) of the local device and a means for triggering by the AMS, the MIDlet;

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

a means for containing in the http response a web page with a redirect URL to local device; and

a means for containing in the redirect URL all the needed parameters for the MIDlet.

10. The system of claim 9, 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.

11. The system of claim 9, for use in an authentication session.

12. The system of claim 9, further comprising a video server on the server platform.

13. The system of claim 9, 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.

14. A local device having a web browser adapted to invoke MIDlets, comprising:

a means for performing an http request to a MIDlet on a local host using a push registry mechanism provided by an application management software (AMS) of the local device;

a means for triggering, by the AMS, the MIDlet;

a means for registering the MIDlet socket invocations in a push registry;

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

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

a means for containing in the http response a web page with a redirect URL to the local host; and

a means for containing in the redirect URL all the needed parameters for the MIDlet.

15. The local device of claim 14, further comprising means for using, by the redirect URL, IP address 127.0.0.1.

16. The local device of claim 14, further comprising:

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

means for decoding the http request.

17. The local device of claim 16, further comprising means for returning with an http response containing a redirect URL to the web server upon completion of the MIDlet tasks.

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

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

20. The local device of claim 14, further comprising means for 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 local device having a web browser adapted to invoke a video session from a web page using a MIDlet without a result return to a web server, comprising:

means for performing an http request to a MIDlet on a local host using a push registry mechanism provided by an application management software (AMS) of the local device;

means for triggering, by the AMS, the MIDlet;

means for registering the MIDlet socket invocations in the push registry;

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

means for requesting, via the http request to the web server, a service that requires interaction with the MIDlet on the local device;

means for connecting to a video server;

means for commencing video streaming to the local device; and

means for containing in the redirect URL all the needed parameters for the MIDlet, wherein the address to the video server are parts of the parameters passed to the MIDlet.

22. The local device of claim 21, further comprising using, by the redirect URL, IP address 127.0.0.1.

23. The local device of claim 21, wherein the AMS triggers the MIDlet.

24. The local device of claim 23, further comprising means for reading, by the MIDlet, the contents buffered in the socket;

and decoding the http request.

25. The local device of claim 24, further comprising means for returning, upon completion of its tasks by the MIDlet, with an http response containing a redirect URL to the web server.

26. The local device of claim 25, wherein http request contains the result parameters from the MIDlet.

27. The local device of claim 26, wherein the http response from the web server contains the result based on the MIDlet results.

28. The local device of claim 21, further comprising means for determining, by the web server, based on a user agent profile whether the local device supports push registry socket or push registry SMS.