Method, apparatus and computer program product for providing confirmed over-the-air terminal configuration

• US 8,437,751 B2
• Filed: 04/25/2006
• Issued: 05/07/2013
• Est. Priority Date: 04/25/2006
• Status: Active Grant

• Current Assignee: Conversant Wireless Licensing S.à.r.l. (f/k/a Core Wireless Licensing S.a.r.l.) (MOSAID Technologies Inc. (f/k/a Conversant Intellectual Property Management))
• Original Assignee: Core Wiresless Licensing SARL (MOSAID Technologies Inc. (f/k/a Conversant Intellectual Property Management))
• Inventors: Szabo, Tamas.Zs
• Primary Examiner(s): Arevalo, Joseph
• Application Number:
  US11/410,810
• Publication Number:
  US 20070250614A1
• Time in Patent Office: 2,569 Days
• Field of Search: 455/574, 455/525, 455/436, 455/438, 455/510, 455/414, 455/567, 455/564, 455/417, 455/555, 455/3.01, 455/67.13, 455/226.2, 455/566, 455/466, 455/433, 455/502, 455/419, 370/352, 370/468, 370/503, 370/410, 370/254, 370/341, 370/39, 370/331, 370/465, 370/469, 370/412, 370/328, 370/338, 370/389, 370/349, 370/329, 370/252, 370/310, 370/393, 370/255, 370/401, 370/400, 709/208, 709/220, 709/224, 709/201, 709/217, 709/212, 709/221, 709/206, 709/245, 709/227
• US Class Current: 455/432.2
• CPC Class Codes: H04L 12/00 Data switching networks interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units G06F13/00
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0866 Checking the configuration
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• 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/125 involving control of end-device applications over a network
• 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: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 1/00 Substation equipment, e.g. for use by subscribers subscriber services or facilities provided at exchanges H04M3/00; prepayment telephone coin boxes H04M17/00; current supply arrangements H04M19/08
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/7243 with interactive means for internal management of messages
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 8/24 Transfer of terminal data
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 88/02 Terminal devices

Abstract

An apparatus for providing confirmed OTA terminal configuration includes a processing element configured to communicate configuration data to a mobile terminal. The processing element is also configured to initiate a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal, and to receive information indicating whether the configuration data was properly received at the mobile terminal.

Claims

1. A method comprising:

communicating, from a device, configuration data to a mobile terminal;

initiating, at the device, a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal by causing a server to establish a connection with the mobile terminal;

receiving information indicating whether the configuration data was properly received at the mobile terminal; and

re-communicating the configuration data to the mobile terminal in response to receipt of an indication that the configuration data was not properly received at the mobile terminal.

2. A method according to claim 1, wherein initiating the confirmation sequence comprises sending a request to the server, the server configured to establish the connection with the mobile terminal in response to the request.

3. A method according to claim 2, wherein receiving information comprises receiving a notification from the server that the mobile terminal properly received the configuration data.

4. A method according to claim 1, wherein initiating the confirmation sequence comprises establishing the connection with the mobile terminal and, thereafter, communicating a sample message from the server to the mobile terminal.

5. A method according to claim 4, wherein receiving information comprises receiving from the server a notification of receipt by the server of an acknowledgment of receipt of the sample message from the mobile terminal.

6. A method according to claim 1, wherein initiating the confirmation sequence comprises causing a multimedia message service (MMS) message to be sent from the server to the mobile terminal to request a connection with the mobile terminal and, thereafter, causing a sample message to be communicated from the server to the mobile terminal.

7. A method according to claim 1, further comprising re-communicating the configuration data to the mobile terminal in response to elapse of a predetermined time prior to receipt of an indication that the configuration data was properly received at the mobile terminal.

8. A method according to claim 1, further comprising sending an inquiry to the server requesting the information indicating whether the configuration data was properly received at the mobile terminal.

9. A method comprising:

a server receiving from a network device a request for establishing a server initiated session with a mobile terminal;

the server sending a connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session;

the server communicating a failure notification message to the network device in response to a failure to receive an indication of a connection with the mobile terminal within a first predetermined time or in response to a failure to receive an acknowledgement from the mobile terminal within a second predetermined time;

the server sending a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal; and

the server sending a notification to the network device in response to the acknowledgment from the mobile terminal, the notification including information indicating whether configuration data was properly received at the mobile terminal.

10. A method according to claim 9, wherein the server sending the notification is performed in response to the acknowledgment from the mobile terminal and receipt of an inquiry from the network device.

11. A computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for communicating, from a device, configuration data to a mobile terminal;

a second executable portion for initiating, at the device, a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal by causing a server to establish a connection with the mobile terminal;

a third executable portion for receiving information indicating whether the configuration data was properly received at the mobile terminal; and

a fourth executable portion for re-communicating the configuration data to the mobile terminal in response to receipt of an indication that the configuration data was not properly received at the mobile terminal.

12. A computer program product according to claim 11, wherein the second executable portion includes instructions for sending a request to the server, the server configured to establish the connection with the mobile terminal in response to the request.

13. A computer program product according to claim 12, wherein the third executable portion includes instructions for receiving a notification from the server that the mobile terminal properly received the configuration data.

14. A computer program product according to claim 11, wherein the second executable portion further includes instruction for establishing the connection with the mobile terminal and, thereafter, communicating a sample message from the server to the mobile terminal.

15. A computer program product according to claim 14, wherein the second executable portion includes instructions for receiving from the server a notification of receipt by the server of an acknowledgment of receipt of the sample message from the mobile terminal.

16. A computer program product according to claim 11, wherein the second executable portion includes instructions for causing a multimedia message service (MMS) message to be sent to the mobile terminal to request a connection with the mobile terminal and, thereafter, a sample message to be communicated from the server to the mobile terminal.

17. A computer program product according to claim 11, further comprising a fourth executable portion for re-communicating the configuration data to the mobile terminal in response to elapse of a predetermined time prior to receipt of an indication that the configuration data was properly received at the mobile terminal.

18. An apparatus comprising a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the apparatus at least to:

communicate, from a device, configuration data to a mobile terminal;

initiate, at the device, a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal by causing a server to establish a connection with the mobile terminal;

receive information indicating whether the configuration data was properly received at the mobile terminal; and

re-communicate the configuration data to the mobile terminal in response to receipt of an indication that the configuration data was not properly received at the mobile terminal.

19. An apparatus according to claim 18, wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to initiate the confirmation sequence by sending a request to the server configured to establish the connection with the mobile terminal in response to the request.

20. An apparatus according to claim 19, wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to receive a notification from the server that the mobile terminal properly received the configuration data.

21. An apparatus according to claim 18, wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to establish the connection with the mobile terminal and, thereafter, communicate a sample message from the server to the mobile terminal.

22. An apparatus according to claim 21, wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to receive from the server a notification of receipt by the server of an acknowledgment of receipt of the sample message from the mobile terminal.

23. An apparatus according to claim 18, wherein the memory and the computer program code are further configured to, with the processor, cause a multimedia message service (MMS) message to be sent from the server to the mobile terminal to request a connection with the mobile terminal and, thereafter, a sample message to be communicated from the server to the mobile terminal.

24. An apparatus according to claim 18, further comprising a timer and wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to re-communicate the configuration data to the mobile terminal in response to the timer sensing an elapse of a predetermined time prior to receipt of an indication that the configuration data was properly received at the mobile terminal.

25. An apparatus according to claim 18, wherein the memory and the computer program code are further configured to, with the processor, cause the apparatus to send an inquiry to a network device requesting the information indicating whether the configuration data was properly received at the mobile terminal.

26. An apparatus comprising:

a means for communicating, from a device, configuration data to a mobile terminal;

a means for initiating, at the device, a confirmation sequence to confirm proper receipt of the configuration data at the mobile terminal by causing a server to establish a connection with the mobile terminal;

a means for receiving information indicating whether the configuration data was properly received at the mobile terminal; and

a means for re-communicating the configuration data to the mobile terminal in response to receipt of an indication that the configuration data was not properly received at the mobile terminal.

27. A server comprising a timer, a processor and memory including computer program code, the memory and the computer program code configured to, with the processor, cause the server at least to:

receive a request for establishing a server initiated session with a mobile terminal from a network device;

send a connection request to the mobile terminal in response to receipt of the request for establishing the server initiated session;

communicate a failure notification message to the network device in response to a failure to receive an indication of a connection with the mobile terminal within a predetermined time sensed by the timer or in response to a failure to receive an acknowledgment from the mobile terminal within a predetermined time sensed by the timer;

communicate a sample message to the mobile terminal in response to an indication of a connection with the mobile terminal; and

communicate a notification to the network device in response to the acknowledgment from the mobile terminal, the notification including information indicating whether configuration data was properly received at the mobile terminal.

28. A server according to claim 27, wherein the memory and the computer program code are further configured to, with the processor, cause the server to communicate the notification in response to acknowledgment from the mobile terminal and receipt of an inquiry from the network device.