Method and apparatus of providing messaging service and callback feature to mobile stations

• US 9,325,772 B2
• Filed: 02/23/2015
• Issued: 04/26/2016
• Est. Priority Date: 09/09/2010
• Status: Active Grant

• Current Assignee: Datto LLC
• Original Assignee: Kaseya Limited
• Inventors: Miller, Allan
• Primary Examiner(s): Eng, George
• Assistant Examiner(s): DEAN, JR, JOSEPH E
• Application Number:
  US14/628,543
• Publication Number:
  US 20150312318A1
• Time in Patent Office: 428 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 40/205 Parsing
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• 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: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04M 1/72403 with means for local support of applications that increase the functionality
• CPC Class Codes: H04M 1/72406 by software upgrading or downloading
• CPC Class Codes: H04M 1/72436 for text messaging, e.g. short messaging services [SMS] or e-mails
• CPC Class Codes: H04M 1/72457 according to geographic location
• CPC Class Codes: H04M 3/42195 Arrangements for calling back a calling subscriber when the wanted subscriber ceases to be busy H04M3/48
• CPC Class Codes: H04M 3/42382 Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• CPC Class Codes: H04M 7/0012 Details of application programming interfaces [API] for telephone networks; Arrangements which combine a telephonic communication equipment and a computer, i.e. computer telephony integration [CPI] arrangements
• CPC Class Codes: H04M 7/0057 Services where the data services network provides a telephone service in addition or as an alternative, e.g. for backup purposes, to the telephone service provided by the telephone services network
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 24/00 : Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 : Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/60 : Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
• CPC Class Codes: H04W 60/005 : Multiple registrations, e.g. multihoming
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 8/22 : Processing or transfer of terminal data, e.g. status or physical capabilities

Abstract

Disclosed are an apparatus and method of performing automated administrative operations on a mobile device. One example method may include determining via a hosted server that an action needs to be performed by a mobile device under management. The method may further include generating a message via the hosted server, the message includes the action, and transmitting the message to the mobile device under management, and receiving a result message from the mobile device under management responsive to the transmitted message, the result message indicating that the action has been satisfied.

Claims

1. A method comprising:

automatically determining an application that needs to be executed on a mobile device;

generating a token responsive to the automatic application determination;

transmitting the token to the mobile device to establish a secure communication channel with a mobile agent router which authenticates and establishes a route for the mobile device to receive the application data based on the token;

creating an initial session between the mobile agent router and the mobile device and generating a device identifier (ID) during the initial session;

transmitting a system identifier (ID) to the mobile device during a provisioning cycle;

transmitting the device ID and the system ID to a hosted server and utilizing the device ID for subsequent identification and transmission communications;

transmitting a message to the mobile device using the secure communication channel; and

parsing the message to obtain an application that needs to be installed on the mobile device.

2. The method of claim 1, comprising monitoring operations performed by the mobile device by a remote administrative device that determines whether an action needs to be performed on the mobile device.

3. The method of claim 1, further comprising:

accessing a software database server to obtain the application that needs to be installed on the mobile device; and

forwarding the application to the mobile device.

4. The method of claim 3, further comprising customizing the application to have it report to a correct management console.

5. The method of claim 1, wherein the token is a semi-private token that is delivered to its intended destination to authenticate and route the mobile device to a correct administrative server.

6. The method of claim 5, further comprising:

performing a final authentication operation at the administrative server; and

communicating at least one additional token to the mobile device.

7. The method of claim 6, wherein the at least one additional token is a secret token.

8. An apparatus comprising:

a processor configured to

automatically determine an application that needs to be executed on a mobile device,

generate a token responsive to the automatic application determination,

create an initial session between a mobile agent router and the mobile device and generate a device identifier (ID) during the initial session;

a transmitter configured to

transmit the token to the mobile device to establish a secure communication channel with the mobile agent router which authenticates and establishes a route for the mobile device to receive the application data based on the token, and

transmit a system identifier (ID) to the mobile device during a provisioning cycle;

transmit the device ID and the system ID to a hosted server and utilize the device ID for subsequent identification and transmission communications;

transmit a message to the mobile device using the secure communication channel, and

wherein the processor is further configured to parse the message to obtain an application that needs to be installed on the mobile device.

9. The apparatus of claim 8, wherein the processor is further configured to monitor operations performed by the mobile device to determine whether an action needs to be performed on the mobile device.

10. The apparatus of claim 8, wherein the processor is further configured to access a software database server to obtain the application that needs to be installed on the mobile device, and forward the application to the mobile device.

11. The apparatus of claim 10, wherein the processor is further configured to customize the application to have it report to a correct management console.

12. The apparatus of claim 8, wherein the token is a semi-private token that is delivered to its intended destination to authenticate and route the mobile device to a correct administrative server.

13. The apparatus of claim 12, wherein the processor is further configured to perform a final authentication operation at the administrative server, and communicate at least one additional token to the mobile device.

14. The apparatus of claim 13, wherein the at least one additional token is a secret token.

15. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:

automatically determining an application that needs to be executed on a mobile device;

generating a token responsive to the automatic application determination;

transmitting the token to the mobile device to establish a secure communication channel with a mobile agent router which authenticates and establishes a route for the mobile device to receive the application data based on the token;

creating an initial session between the mobile agent router and the mobile device and generating a device identifier (ID) during the initial session;

transmitting a system identifier (ID) to the mobile device during a provisioning cycle;

transmitting the device ID and the system ID to a hosted server and utilizing the device ID for subsequent identification and transmission communications;

transmitting a message to the mobile device using the secure communication channel; and

parsing the message to obtain an application that needs to be installed on the mobile device.

16. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform monitoring operations performed by the mobile device by a remote administrative device that determines whether an action needs to be performed on the mobile device.

17. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform:

accessing a software database server to obtain the application that needs to be installed on the mobile device; and

forwarding the application to the mobile device.

18. The non-transitory computer readable storage medium of claim 17, wherein the processor is further configured to perform customizing the application to have it report to a correct management console.

19. The non-transitory computer readable storage medium of claim 15, wherein the token is a semi-private token that is delivered to its intended destination to authenticate and route the mobile device to a correct administrative server.

20. The non-transitory computer readable storage medium of claim 19, wherein the processor is further configured to perform:

processing a final authentication operation at the administrative server; and

communicating at least one additional token to the mobile device, the at least one additional token being a secret token.