Method, system and program product for using open mobile alliance (OMA) alerts to send client commands/requests to an OMA DM server

• US 7,523,155 B2
• Filed: 03/18/2004
• Issued: 04/21/2009
• Est. Priority Date: 03/18/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hayes, Kent F. Jr.
• Primary Examiner(s): JEAN GILLES, JUDE
• Application Number:
  US10/803,236
• Publication Number:
  US 20050228847A1
• Time in Patent Office: 1,860 Days
• Field of Search: 709/223, 709/200
• US Class Current: 709/200
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0843 based on generic templates
• 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/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Under the present invention, there is provided a method, system and program product for using Open Mobile Alliance (OMA) Device Management (DM) alerts to send client commands/requests to an OMA DM server to initiate management actions on the OMA server. The method comprises: sending an OMA DM alert from a client device to an OMA DM server to initiate a management action on the OMA DM server; and in response to the OMA DM alert, sending a reply from the OMA DM server to the client device.

Claims

1. A computer-implemented method, comprising:

sending an Open Mobile Alliance (OMA) device management (DM) alert from a client device running in an OSGi environment to an OMA DM server to initiate a client device management action on the OMA DM server, wherein the OMA DM alert is sent by the client device to the OMA DM server in response to a connection of a peripheral to the client device, and wherein the OMA DM alert comprises a query regarding an availability of an undated device driver for the peripheral; and

sending a reply from the OMA DM server to the client device in response to the OMA DM alert, wherein, if an undated device driver for the peripheral is available on the OMA DM server, the reply sent from the OMA DM server to the client device includes the undated device driver in an OSGi bundle, and wherein, if an undated device driver for the peripheral is not available on the OMA DM server, the reply sent from the OMA DM server to the client device informs the client device that an undated device driver is not available for the peripheral.

2. The method of claim 1, further comprising:

sending, by the client device, a second OMA DM alert to the OMA DM server, wherein;

the second OMA DM alert sent by the client device to the OMA DM server comprises a command/request for a list of software on the OMA DM server available for distribution to the client device, and wherein the reply sent from the OMA DM server to the client device comprises the list of available software.

3. The method of claim 2, further comprising:

sending a third OMA DM alert from the client device to the OMA DM server, wherein the third OMA DM alert comprises a command/request for selected software on the list of available software.

4. The method of claim 3, wherein:

in response to the third OMA DM alert, sending the selected software from the OMA DM server to the client device in an OSGi bundle.

5. The method of claim 1, further comprising:

sending, by the client device, a second OMA DM alert to the OMA DM server, wherein;

the second OMA DM alert sent by the client device to the OMA DM server comprises a command/request for software on the OMA DM server, and wherein the reply sent from the OMA DM server to the client device comprises the software in an OSGi bundle.