Provisioning to CDC devices

• US 7,580,703 B1
• Filed: 03/11/2004
• Issued: 08/25/2009
• Est. Priority Date: 03/11/2004
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Decristo, Dianna L., Veselov, Pavel S.
• Primary Examiner(s): Kincaid; Lester
• Assistant Examiner(s): MITCHELL, NATHAN A
• Application Number:
  US10/798,981
• Time in Patent Office: 1,993 Days
• Field of Search: 370/328, 455/414.1, 455/418, 717/147, 717/174
• US Class Current: 455/414.1
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: H04W 8/245 from a network towards a terminal

Abstract

A method for delivering a non-MIDlet application to a device associated with a connected device configuration (CDC) through an over the air (OTA) mobile information device profile (MIDP) protocol is provided. The method initiates with prefixing an identifier for the non-MIDlet application, wherein the identifier is configured to imply a MIDlet application. The method includes requesting the non-MIDlet application and determining a type of the non-MIDlet application. Then, the non-MIDlet application is managed with an interface application associated with the type of the application. A system and device configured to download a non-MIDlet application through a mobile information device profile (MIDP) are provided.

Claims

1. A method executed by a microprocessor for delivering a non-MIDlet application to a device associated with a connected device configuration (CDC) through an over the air (OTA) mobile information device profile (MIDP) protocol, comprising:

prefixing an identifier for the non-MIDlet application, wherein the identifier is configured to imply a MIDlet application and wherein the identifier is resident in memory of a computing device;

requesting the non-MIDlet application;

determining a type of the non-MIDlet application by parsing a descriptor of the non-Midlet application; and

managing the non-MIDlet application with an interface the non-MIDlet application follows.

2. The method of claim 1, further comprising:

downloading the non-MIDlet application.

3. The method of claim 1, wherein the non-MIDlet application is one of an Xlet and an applet.

4. The method of claim 1, wherein the method operation of prefixing an identifier for the non-MIDlet application includes,

applying an “

MID”

prefix to names of property keys associated with the non-MIDlet application.

5. The method of claim 4, wherein “

MID”

implies the MIDlet application.

6. A computer readable medium having program instructions for delivering non-MIDlet applications to a device associated with a connected device configuration (CDC) through an over the air (OTA) mobile information device profile (MIDP) protocol, comprising:

program instructions for prefixing an identifier for the non-MIDlet application, wherein the identifier is configured to imply a MIDlet application;

program instructions for requesting the application incompatible with the MIDlet API;

program instructions for determining a type of the non-MIDlet application through parsing a descriptor of the non-MIDlet application; and

program instructions for managing the non-MIDlet application with an interface application associated with the type of the application.

7. The computer readable medium of claim 6, further comprising:

program instructions for downloading the non-MIDlet application.

8. The computer readable medium of claim 6, wherein the non-MIDlet application is one of an Xlet and an applet.

9. The computer readable medium of claim 6, wherein the program instructions for prefixing an identifier for the non-MIDlet application includes,

program instructions for applying an “

MID”

prefix to names of property keys associated with the non-MIDlet application.

10. A system configured to deliver non-MIDlet applications through an over the air (OTA) mobile information device profile (MIDP) protocol, comprising:

a server enabling access to a non-MIDlet type application; and

a client in communication with the server through a mobile information device profile (MIDP), the client configured to download the non-MIDlet type application through the server, the client further configured to store a descriptor associated with the non-MIDlet type application, the descriptor configured to identify an address associated with the non-MIDlet application and describe executables associated with the non-MIDlet type application, the client including,

an application manager configured to manage the non-MIDlet type application, the application manager further configured to decipher whether the non-MIDlet type application is one of an Xlet and an applet through examination of a class data stored in an application file.

11. The system of claim 10, wherein the client communicates with the server through a distributed network through one of a wired connection and a wireless connection and wherein the client stores a repository of files that includes the descriptor, the application manager linked to the repository of files.

12. The system of claim 10, wherein the client supports a connected device configuration (CDC).

13. The system of claim 10 wherein the client is selected from the group consisting of a cellular phone, a pager, a household appliance, and a personal digital assistant.

14. A device configured to download a non-MIDlet application through a mobile information device profile (MIDP), wherein the device stores:

a repository of application files;

an application manager linked to the repository of application files, the application manager configured to decipher whether the non-MIDlet application is one of an Xlet and an applet through examination of a class data stored in the application file, a descriptor being stored in the repository of application files.

15. The device of claim 14, wherein the device is selected from the group consisting of a cellular phone, a pager, a household appliance, and a personal digital assistant.

16. The device of claim 14, wherein the non-MIDlet application is configured to appear as a MIDlet application to the MIDP through the incorporation of an “

MID”

prefix.

17. The device of claim 16, wherein the “

MID”

prefix is inserted prior to a name of a property key.

18. The device of claim 14, wherein the descriptor is a list of properties of the non-MIDlet application, the list of properties selected from the group consisting of a name, a version, a vendor, a source, and a size of the non-MIDlet application.