Enterprise Mobile Notification Solution

• US 20150373048A1
• Filed: 06/24/2015
• Published: 12/24/2015
• Est. Priority Date: 06/24/2014
• Status: Abandoned Application

• Current Assignee: Kashif Ali Siddiqui
• Original Assignee: Kashif Ali Siddiqui
• Inventors: Siddiqui, Kashif Ali
• Application Number:
  US14/749,510
• Publication Number:
  US 20150373048A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning
• CPC Class Codes: H04W 12/37 Managing security policies for mobile devices or for controlling mobile applications

Abstract

The present invention provides mobile clients that can be easily distributed using any third party MDM (Mobile Device Management) solutions, or mobile app stores. Two operational modes provide only messaging functions, or give more functions to manage and control various processes in the system server. This gives an easy way for Enterprises to manage their license cost by providing advance functions to targeted technical users. The solution works on all the above mentioned platforms and enables an Enterprise to work with heterogeneous mobile devices and platforms. An admin panel on the server software through which an admin can control each and every mobile device, and its access to the information. The present invention provides an easy to define general policy through which rules can be defined for all devices. Similarly, specific rules for individual devices can also be defined, and applied instantaneously.

Claims

1. A method for providing an enterprise mobile notification solution recorded on computer-readable medium and capable of execution by a computer, said method comprising the steps of:

configuring a server;

configuring mobile users devices;

installing the client app. on one or more mobile user devices;

after installation, registering and activating client, the app is required to once get registered with the server;

sending an admin control panel from the server to a user device;

displaying an admin control panel on a mobile device using the client;

registering and activating the client;

requiring logging-in to the server is required after registering the app;

defining access privileges, and client settings. logging-in to the system server;

providing full end-to-end security using cryptographic algorithms;

using Transport Layer Security (TLS);

providing a single session handshake process wherein the TLS encryption key is constantly changing on each communication session between the system server and the mobile device; and

enabling all the messages saved on the devices to be managed with automatic deletion, message expiry, and remote administration.

2. The method of claim 1, further comprising the steps of providing client access to the server for remotely removing data;

and

define general policy by the server through which rules can be defined for all devices;

defining specific rules for individual devices; and

applying the rules instantaneously to individual client devices.

3. The method of claim 1, wherein

configuring the server, an admin is required to setup an HNP manager, one or more HNP carriers, and an HNP messenger;

and

after this step, a solution will be ready to get connections from mobile clients, and become able to send messages to these clients.

4. The method of claim 1, wherein

configuring mobile users, mobile users are defined in the server contacts database;

and

each mobile user can be associated with a server user to grant extra authorities for advance features.

5. The method of claim 1, wherein when installing the client mobile app on the mobile device;

smartphone, tablet, or any supported media device,

the installation can be over-the-air (OTA) using any MDM (Mobile Device Management) solution;

or

the installation can be a manual distribution process involving install the app binary by each mobile user.

6. The method of claim 1, wherein the login can be configured as automatic procedure made every time on app startup.

7. The method of claim 1, further comprising the steps of

configuring mobile clients;

and

providing a mobile user with various settings in their app from display configuration, to alerting configuration to security setup.

8. The method of claim 1, wherein

the present invention server can be configured to define mobile user permissions and/or app settings at the server side;

these permissions and/or settings if defined are enforced on the mobile app.; and

an admin can setup general policy for mobile access authorities and app settings for all the mobile users.

9. The method of claim 1, further comprising a five step configuration process comprising the steps of

a. configuring the present invention server;

b. configuring mobile users;

c. installing a client;

d. registering (Activating) the client; and

e. logging in to the server.

10. The method of claim 9, wherein

in step a, configuring the present invention server, an admin is required to setup the HNP manager, the HNP carriers and the HNP messengers;

and

a solution will be generated and ready to receive connections from mobile clients, and become able to send messages to these clients.

11. The method of claim 9, wherein

in step b, configuring mobile users, mobile users are defined in a server contacts database;

and

each mobile user can be associated with a server user to grant extra authorities for advance features.

12. The method of claim 9, wherein

in step c, installing client, the present invention mobile app on the mobile device;

smartphone, tablet, or any supported media device the installation can be over-the-air (OTA) using any MDM solution, or it can be a manual distribution process involving install the app binary by each mobile user.

13. The method of claim 9, wherein

in step d, after installation, registering (Activating) client, the app is required to once get registered with the server.

14. The method of claim 9, wherein

in step e, after registering the app, logging in to the server, the user will be require to log into server;

the login can be configured as automatic procedure made every time on app startup.

15. The method of claim 9, further comprising the steps of

configuring mobile clients, wherein a mobile user can make various settings in their app from display configuration, to alerting configuration to security setup.

16. The method of claim 9, further comprising the steps of

defining access privileges, and client settings, the server can be configured to define mobile user permissions and/or app settings at the server side;

these permissions and/or settings if defined are enforced on the mobile app.; and

an admin can setup general policy for mobile access authorities and app settings for all the mobile users.

17. A method for providing an enterprise mobile notification solution recorded on computer-readable medium and capable of execution by a computer, said method comprising the steps of:

creating an iOS app 107 with a provisioning profile enabled with APNS support'"'"'

the iOS app registers for APNS alerts with the APNS gateways by

submitting a client application, a

asking for a device token 1, and

receiving its device-token,

the iOS app sends its token to system server;

the system server must be configured with APNS SSL Certificate and its associated private key;

the system server, when a new message is moved into waiting Queue,

sends push notification to the APNS server,

connects to APNS gateway using SSL/TLS sockets, and

dispatches the alert to the APNS Server

the APNS server sends the alert to the iOS device;

system server opens up the service (HNP) server port, and the clients connects to that server port to establish the communication link;

this port is completely configurable, and can be set or changed from the HNP configuration panel;

the port is configured for a separate server port for file transfer, which is being used to send message attachments to the target recipient mobile app.

18. The method of claim 17, wherein

the communication link is protected and secured by TLS protocol;

the server 208 must be configured with a server certificate and its associated private key;

the TLS will create a secure tunnel between the server and the client device; and

all the communication regarding messaging, reporting, and other requests, and their responses are sent through this tunnel;

the server is further comprised of an HNP manager which provides user access to the accounts;

the server is further comprised of a manager that enables a messenger module to send messages through the tunnel securely to client devices;

when any client app receives a message with attachment(s) that requests to pull the files using out-of-band mechanism, then the server port is also provided;

the client app then initiates the connection to that port, and receives the files in encrypted form;

the he encryption keys are sent separately with a message in the main HNP communication.

19. The method of claim 18, wherein

HNP communication is the primary link between the system server and the client apps.;

the client app makes a permanent connection to the server using a main HNP communication connection through a port and tries to keep it alive for the life of the app'"'"'s process;

the TLS (Transport Layer Security) connection is made over TCP, and after successful connection, TLS is started immediately;

first the server sends its public key (in its server certificate) and client uses it to establish the initial secure connection;

the TLS protocol then does the handshake procedure in which cipher capabilities are negotiated, and a shared secret key is established, and

after that the newly created key is used to secure the following session;

the shared key has an expiration time, and when it expires, it enforces both sides to go through the key creation procedure again.

20. The method of claim 19, wherein

the HNP Authentication &

session communication starts after TLS is successfully initiated in response to the initial connection request from the device to the server;

the server responding with a certificate,

creating the secure tunnel, and

starting secure tunnel communications;

the first process is the user authentication,

the user ID, password, and activation key is sent to the server via the secure tunnel;

the server authenticates the user,

checks its activation, and

then responds with user permissions (access privileges) and settings;

the permissions further disables app functions (leaving others as enabled), whereas settings changes the usage behavior;

the HNP session gets started,

then client app on the device sends any requests to execute operation at the server;

if the server has a message for the device, then the same HNP connection is used, and the server pushes the message to the device;

besides receiving messages in this session 500, the client can send requests to;

query for contacts, send a message to other contacts, query a sent message status, confirm/reject a message, log out of the session, to which the server can send response;

the HNP Session Lifecycle remains active as long as

the device has some form of data network to stay connected,

the user does not logoff explicitly, and

the client app is kept running (either in background or foreground);

at any time the user can send a logoff request from the device to the server; and

the sever will then terminate the session and secure tunnel.