Secure Cloud-Based Phonebook

• US 20150195395A1
• Filed: 01/06/2014
• Published: 07/09/2015
• Est. Priority Date: 01/06/2014
• Status: Abandoned Application

• Current Assignee: Desiree Gina Mcdowell-White, Gilbert J. Arenas
• Original Assignee: Desiree Gina Mcdowell-White, Gilbert J. Arenas
• Inventors: McDowell-White, Desiree Gina, Arenas, Gilbert J.
• Application Number:
  US14/148,022
• Publication Number:
  US 20150195395A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04M 1/2757 by data transmission, e.g. downloading
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold

Abstract

A cloud-based system for securely maintaining phone numbers and contacts. A mobile application residing on a mobile computing device interfaces with a remotely positioned server to provide phonebook capabilities to a single user of the mobile application. Contact information is only maintained on the remote server and any local information is removed when the mobile application is exited or closed. The server only allows one registered user/device to access the remotely stored information at a time and will notify the authorized user of any attempts to access the remote server.

Claims

1. A secure phonebook system, comprising:

a mobile device having a mobile application installed thereon that is programmed to require a user to enter session credentials and to transmit those session credentials when said mobile application is opened;

a remotely positioned server interconnected to a database, wherein said server is programmed to store data representing said at least one contact and user credentials associated with said stored data, and is further programmed to transmit said data to said mobile device when said mobile application provides session credentials that match stored user credentials;

wherein said mobile application is programmed to display said data representing at least one contact only after said mobile application is opened and has received said data representing at least one contact from said server and to delete said data representing at least one contact each time said mobile application is closed.

2. The system of claim 1, wherein said server is programmed to accept session credentials that match user credentials from just one mobile application at a time.

3. The system of claim 2, wherein said server is programmed to notify said mobile application if the server receives a second transmission of matching session credentials.

4. The system of claim 1, wherein said mobile application is further programmed to connect to said remotely positioned server at least once and upload all contact information stored on said mobile device to said remotely positioned server.

5. The system of claim 4, wherein said mobile application is further programmed to delete said contact information from said mobile device after uploading to said remotely positioned server.

6. The system of claim 5, wherein said remotely positioned server is programmed to upload contact information from sources other than said mobile device.

7. A method of securing contact information used on a mobile device, comprising the steps of:

providing a mobile application for a mobile device that is programmed to require a user to enter session credentials and to transmit those session credentials when said mobile application is opened;

providing a remotely positioned server interconnected to a database, wherein said server is programmed to store data representing said at least one contact and user credentials associated with said stored data, and is further programmed to transmit said data to said mobile device when said mobile application provides session credentials that match stored user credentials;

using said mobile application to display said data representing at least one contact only after said mobile application is opened and has received said data representing at least one contact from said server; and

deleting said data representing at least one contact each time said mobile application is closed.

8. The method of claim 7, wherein said server is programmed to accept session credentials that match user credentials from just one mobile application at a time.

9. The method of claim 8, further comprising the step of providing a notification to said mobile device if the server receives a second transmission of matching session credentials.

10. The method of claim 7, further comprising the step of uploading all contact information stored on said mobile device to said remotely positioned server.

11. The method of claim 8, further comprising the step of deleting said contact information from said mobile device after uploading to said remotely positioned server.

12. The method of claim 7, further comprising the step of uploading contact information from sources other than said mobile device.

13. A method of securely providing contact information, comprising the steps of:

allowing a user to access a dedicated contact database stored on a remotely positioned server from a mobile device;

providing the user with contact information stored on said remotely positioned server in said dedicated contact database;

allowing said user to use said contact information to initiate a communication; and

automatically deleting all copies of said contact information stored on said mobile device.

14. The method of claim 13, wherein the step of allowing a user to access a dedicated user file stored on a remotely positioned server from a mobile device comprising the step of requiring said user to provide predetermined credentials unique to the user.

15. The method of claim 14, further comprising the step of notifying said user if another user provides said predetermined credentials after said user has provided said credentials and has accessed said dedicated contact database.

16. The method of claim 13, further comprising the steps of:

allowing a user to establish said dedicated contact database on said remotely positioned server;

allowing said user to establish said predetermined credentials unique to the user; and

associating said predetermined credentials unique to the user with said dedicated contact database.

17. The method of claim 16, further comprising the step of allowing said user to upload locally stored contact information from said mobile device to populate said dedicated contact database on said remotely positioned server.

18. The method of claim 17, further comprising the step of deleting said locally stored contact information on said mobile device after said dedicated contact database on said remotely positioned server has been populated with said contact information.