Systems and methods for remote deletion of contact information

• US 9,178,972 B2
• Filed: 11/15/2011
• Issued: 11/03/2015
• Est. Priority Date: 03/23/2007
• Status: Expired due to Fees

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Swanburg, Scott, Okada, Andre, Hanson, Paul, Young, Chris
• Primary Examiner(s): Wu, Yicun
• Application Number:
  US13/296,374
• Publication Number:
  US 20120066177A1
• Time in Patent Office: 1,449 Days
• Field of Search: 707/610, 707/620, 707/621, 707/625, 709/206, 709/219, 709/224
• US Class Current: 1/1
• CPC Class Codes: G06F 16/3329 Natural language query formulation or dialogue systems
• CPC Class Codes: G06F 3/0489 using dedicated keyboard keys or combinations thereof
• CPC Class Codes: G06F 40/205 Parsing
• CPC Class Codes: G06F 40/221 Parsing markup language streams streaming G06F40/149
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 51/18 Commands or executable codes
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/4594 Address books, i.e. directories containing contact information about correspondents telephone directories in user terminals H04M1/27453
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04M 1/27453 Directories allowing storage of additional subscriber data, e.g. metadata
• CPC Class Codes: H04M 1/2757 by data transmission, e.g. downloading
• CPC Class Codes: H04M 1/72457 according to geographic location
• CPC Class Codes: H04M 1/72469 for operating the device by selecting functions from two or more displayed items, e.g. menus or icons
• CPC Class Codes: H04M 15/705 Account settings, e.g. limits or numbers or payment
• CPC Class Codes: H04M 2203/2011 : Service processing based on information specified by a party before or during a call, e.g. information, tone or routing selection
• CPC Class Codes: H04M 2203/2072 : Schedules, e.g. personal calendars
• CPC Class Codes: H04M 2250/10 : including a GPS signal receiver
• CPC Class Codes: H04M 3/42068 : where the identifier is used to access a profile
• CPC Class Codes: H04M 3/4211 : where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42357 : where the information is provided to a monitoring entity such as a potential calling party or a call processing server
• 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 3/493 : Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
• CPC Class Codes: H04M 3/5322 : for recording text messages
• CPC Class Codes: H04M 3/53333 : Message receiving aspects
• CPC Class Codes: H04M 3/537 : Arrangements for indicating the presence of a recorded message , whereby the presence information might include a preview or summary of the message
• CPC Class Codes: H04M 7/0033 : Notification or handling of incoming calls by a computer
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold

Abstract

An exemplary system for providing remote deletion of contact information includes a first device associated with a first user. The first device is configured to generate and send a delete request message to a second device. In some embodiments, the delete request message includes a request to delete contact information for the first user from the second device. The second device can be configured to receive the delete request message and delete the first user'"'"'s contact information. A method for providing remote deletion of contact information includes a delete request message being generated at a first device, associated with a first user. The delete request message can include a request to delete contact information for the first user. The first device can send the delete request message to a second device. The delete request message can instruct the second device to delete the first user'"'"'s contact information.

Claims

1. A method comprising:

receiving a delete request message, at a network contact database, from a first device associated with a first user, the delete request message comprising a text message generated by the first device, the text message comprising a destination number that identifies a second device from which contact information associated with the first user is to be deleted and a character string that instructs the network contact database to delete the contact information associated with the first user from the second device, and the second device being associated with a second user and comprising a local contact database of the second device;

causing, by a processor, contact information associated with the first user from the network contact database to be deleted in response to the delete request message; and

causing, by the processor, a synchronization process to be initiated between the local contact database of the second device and the network contact database to delete, from the local contact database of the second device, the contact information associated with the first user.

2. The method of claim 1, wherein the delete request message further comprises a network contact database number identifying the network contact database, and wherein the destination number also identifies an entry within the network contact database corresponding to the second device.

3. The method of claim 1, further comprising executing an action to ensure that the contact information deleted in connection with the synchronization process is not subsequently added to the local contact database of the second device.

4. The method of claim 3, wherein executing the action comprises causing a flag to be set at the second device, the flag acting to prevent the contact information from being transferred from the network contact database to the local contact database of the second device following deletion of the contact information at the second device during the synchronization process.

5. The method of claim 3, wherein executing the action comprises, as part of initiating the synchronization process, forwarding the delete request message to the second device.

6. The method of claim 1, wherein the second device is a handheld computer associated with the second user.

7. The method of claim 1, wherein the second device is a computer selected from a group of computers consisting of:

a desktop computer associated with the second user;

a laptop computer associated with the second user; and

a tablet computer associated with the second user.

8. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving a delete request message, at a network contact database, from a first device associated with a first user, the delete request message comprising a text message generated by the first device, the text message comprising a destination number that identifies a second device from which contact information associated with the first user is to be deleted and a character string that instructs the network contact database to delete the contact information associated with the first user from the second device, and the second device being associated with a second user and having a local contact database of the second device;

deleting the contact information corresponding to the first user from the network contact database in response to the delete request message; and

initiating a synchronization process between the local contact database of the second device and the network contact database to delete, from the local contact database of the second device, the contact information associated with the first user.

9. The non-transitory computer-readable storage medium of claim 8, wherein the delete request message further comprises a network contact database number identifying the network contact database, and the destination number also identifies an entry within the network contact database corresponding to the second device.

10. The non-transitory computer-readable storage medium of claim 8, wherein the operations further comprise executing an action to ensure that the contact information deleted is not subsequently added to the local contact database of the second device.

11. The non-transitory computer-readable storage medium of claim 10, wherein executing the action comprises causing a flag to be set at the second device, the flag acting to prevent the contact information from being transferred from the network contact database to the local contact database of the second device following deletion of the contact information at the second device during the synchronization process.

12. The non-transitory computer-readable storage medium of claim 10, wherein executing the action comprises, as part of initiating the synchronization process, forwarding the delete request message to the second device.

13. The non-transitory computer-readable storage medium of claim 8, wherein the second device is a handheld computer associated with the second user.

14. The non-transitory computer-readable storage medium of claim 8, wherein the second device is a computer selected from a group of computers consisting of:

a desktop computer associated with the second user;

a laptop computer associated with the second user; and

a tablet computer associated with the second user.

15. A method comprising:

generating a delete request message at a first device associated with a first user, the delete request message requesting deletion of contact information associated with the first user;

sending, from the first device, the delete request message for delivery to a second device associated with a second user;

after sending the delete request message, determining whether, at the first device, to allow the first user to provide an authorization to have the contact information associated with the first user deleted from the second device, wherein the contact information will not be deleted at the second device without the authorization having been provided at the first device;

receiving, at the first device, a request for the authorization to have the second device delete the contact information; and

receiving, at the first device, from the first user, and in response to receiving the request, the authorization from the first user to have the second device delete the contact information associated with the first user.

16. The method of claim 15, further comprising sending, in response to receiving the authorization, an authorization message for delivery to the second device for authorizing deletion of the contact information at the second device.

17. The method of claim 15, further comprising presenting to the first user, a prompt for authorizing the delete request message;

and wherein the authorization is received from the first user in response to the prompt.

18. The method of claim 15, wherein the second device is a handheld computer associated with the second user.