Method and system for exchanging data between portable applications for mobile devices

• US 7,437,149 B1
• Filed: 03/23/2004
• Issued: 10/14/2008
• Est. Priority Date: 03/24/2003
• Status: Active Grant

• Current Assignee: Sprint Spectrum LP (Deutsche Telekom AG), Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sprint Spectrum LP (Deutsche Telekom AG)
• Inventors: Bostrom, Jon, Papineau, Scott, Myers, Dana
• Primary Examiner(s): Vo; Tim
• Assistant Examiner(s): Dwivedi; Mahesh H
• Application Number:
  US10/808,120
• Time in Patent Office: 1,666 Days
• Field of Search: 709/250, 709/217, 709/224, 707/200, 455/418
• US Class Current: 455/418
• CPC Class Codes: G06F 9/485 Task life-cycle, e.g. stopping, restarting, resuming execution G06F9/4881 takes precedence
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes

Abstract

A mobile information device may execute a Java MIDlet or a non-MIDlet application. The mobile information device may further include an application management system that allows one or more object-oriented object classes to allow input and output data to be communicated between Java MIDlets in different MIDlet Suites and between non-MIDlet applications.

Claims

1. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application;

prior to passing the appended second data and the URI that identifies the first MIDlet application to a second MIDlet application on the mobile information device;

(i) determining based on a scheme of the second URI that the second MIDlet application is registered to handle the second URI, and (ii) invoking the second MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to the second MIDlet application on the mobile information device.

2. The method of claim 1, wherein accepting the first data from the first MIDlet application includes receiving the first data via a setExitURI( ) object-oriented method,

and wherein accepting the second data from the first MIDlet application includes receiving the second data via an appendReferringURI( ) object-oriented method.

6. The method of claim 1, wherein the mobile information device is a mobile phone, a personal digital assistant or a two-way pager.

13. A computer-readable medium containing instructions for causing a processor to execute the steps of the method of claim 1.

18. The method of claim 1, wherein the scheme of the URI is tel:

.

19. The method of claim 1, wherein the scheme of the URI is midlet:

.

20. The method of claim 1, wherein the scheme of the URI is im:

.

21. The method of claim 1, wherein the scheme of the URI is http:

.

22. The method of claim 1, wherein the scheme of the URI is https:

.

28. The method of claim 1, wherein the URI passed to the second MIDlet application from the application management system allows execution control to be returned to a previous context used before the second MIDlet application was invoked.

3. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application;

prior to passing the appended second data and the URI that identifies the first MIDlet application to a second MIDlet application on the mobile information device;

(i) determining based on a scheme of the second URI and based on additional scheme specific information of the second URI that the second MIDlet application is registered to handle the second URI, and (ii) invoking the second MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to the second MIDlet application on the mobile information device.

4. The method of claim 3, wherein the scheme of the second URI is ams:

or midlet;

.

5. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to a second MIDlet application on the mobile information device,

wherein the appended second data passed to the second MIDlet application allows execution control to be returned to a previous context used before the second MIDlet application was invoked.

7. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a MIDlet application in a MIDlet suite on the mobile information device, wherein the MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the MIDlet application;

at the application management system, appending the second data to the URI that identifies the MIDlet application; and

passing the appended second data and the URI that identifies the MIDlet application from the application management system to a non-MIDlet application on the mobile information device.

8. The method of claim 7, further comprising:

prior to passing the appended second data and the URI that identifies the MIDlet application from the application management system to a non-MIDlet application on the mobile information device;

(i) determining based on a scheme of the second URI that the non-MIDlet application is registered to handle the second URI, and (ii) invoking the non-MIDlet application.

9. The method of claim 7, further comprising:

prior to passing the appended second data and the URI that identifies the MIDlet application from the application management system to a non-MIDlet application on the mobile information device;

(i) determining based on a scheme of the second URI and based on additional scheme specific information of the second URI that the non-MIDlet application is registered to handle the second URI, and (ii) invoking the non-MIDlet application.

10. The method of claim 9, wherein the scheme of the second URI is “

ams;

”

or “

midlet;

”

.

11. The method of claim 7, wherein accepting the first data from the MIDlet includes accepting the first data via a setExitURI( ) object-oriented method, and

wherein accepting the second data from the MIDlet includes accepting the second data via an appendReferringURI( ) object-oriented method.

14. A computer-readable medium containing instructions for causing a processor to execute the steps of the method of claim 7.

25. The method of claim 7, wherein passing the appended second data and the URI that identifies the MIDlet application from the application management system to the non-MIDlet application on the mobile information device is carried out in response to the non-MIDlet application sending a request to the application management system.

26. The method of claim 25, wherein the request sent to the application management system comprises a request selected from the group consisting of:

(i) a request for data via a getMediaType( ) object oriented method, (ii) a request for data via a getContentType( ) object-oriented method, (iii) a request for data via a getMuglet( ) object-oriented method, (iv) a request for data via a getReferringURI( ) object-oriented method, and (v) a request for data via a getURI( ) object-oriented method.

29. The method of claim 8, wherein the URI passed to the second non-MIDlet application from the application management system allows execution control to be returned to a previous context used before the non-MIDlet application was invoked.

12. A method for passing data between applications on a mobile information device, the method comprising:

maintaining an application management system on the mobile information device;

at the application management system, receiving first data from a non-MIDlet application on the mobile information device, wherein the non-MIDlet application is identified by a first URI, and wherein the first data comprises a second URI that identifies a MIDlet application on the mobile information device;

at the application management system, receiving second data from the non-MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the non-MIDlet application;

launching the MIDlet application on the mobile information device; and

passing the appended second data and the URI that identifies the non-MIDlet application from the application management system to the MIDlet application.

15. A computer-readable medium containing instructions for causing a processor to execute the steps of the method of claim 12.

27. The method of claim 12, wherein passing the appended second data and the URI that identifies the non-MIDlet application from the application management system to the MIDlet application is carried out in response to the MIDlet application sending a request to the application management system.

30. The method of claim 12, wherein the URI passed to the MIDlet application from the application management system allows execution control to be returned to a previous context used before the MIDlet application was launched.

16. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to a second MIDlet application on the mobile information device,

wherein the first MIDlet application and the second MIDlet application are in a MIDlet suite on the mobile information device.

17. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to a second MIDlet application on the mobile information device,

wherein the first MIDlet application is in a first MIDlet suite on the mobile information device and the second MIDlet application is in a second MIDlet suite on the mobile information device.

23. A method for an application management system on a mobile information device to pass data between applications on the mobile information device, the method comprising:

at the application management system, accepting first data from a first MIDlet application on the mobile information device, wherein the first MIDlet application is identified by a first URI, and wherein the first data comprises a second URI;

at the application management system, accepting second data from the first MIDlet application on the mobile information device;

at the application management system, appending the second data to the URI that identifies the first MIDlet application; and

passing the appended second data and the URI that identifies the first MIDlet application from the application management system to a second MIDlet application on the mobile information device,

wherein passing the appended second data and the URI that identifies the first MIDlet application from the application management system to the second MIDlet application is carried out in response to the second MIDlet application sending a request to the application management system.

24. The method of claim 23, wherein the request sent to the application management system comprises a request selected from the group consisting of:

(i) a request for data via a getMediaType( ) object oriented method, (ii) a request for data via a getContentType( ) object-oriented method, (iii) a request for data via a getMuglet( ) object-oriented method, (iv) a request for data via a getReferringURI( ) object-oriented method, and (v) a request for data via a getURI( ) object-oriented method.