Toggling Voicemail Class of Service

• US 20100189229A1
• Filed: 06/20/2008
• Published: 07/29/2010
• Est. Priority Date: 08/31/2007
• Status: Active Grant

• Current Assignee: Nuance Communications, Inc. (Microsoft Corporation)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Rainer, Brian Keith, Zubas, Michael Robert, Sigmund, William Joseph
• Granted Patent: US 8,737,580 B2
• Time in Patent Office: Days
• US Class Current: 379/88.220
• CPC Class Codes: G06F 40/58 Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation
• CPC Class Codes: H04M 2201/50 Telephonic communication in combination with video communication
• CPC Class Codes: H04M 2203/4518 Attachments to voicemail messages including annexed information, e.g. Attachments, in packet switching networks H04L51/08
• CPC Class Codes: H04M 2203/4545 Message forwarding selective message forwarding in packet switching networks H04L51/214
• CPC Class Codes: H04M 3/02 Calling substations, e.g. by ringing selective calling H04Q
• CPC Class Codes: H04M 3/42017 Customized ring-back tones
• CPC Class Codes: H04M 3/42051 where the notification is included in the ringing tone
• CPC Class Codes: H04M 3/42153 by subscriber
• CPC Class Codes: H04M 3/533 Voice mail systems
• CPC Class Codes: H04M 3/53325 Interconnection arrangements between voice mail systems
• CPC Class Codes: H04M 3/53383 Message registering commands or announcements; Greetings
• 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: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• 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 method (200, 400) for toggling voicemail class of service (CoS) including receiving a subscriber-initiated CoS change request (202, 402) at a billing system (109), wherein the CoS change request includes a request to change from a first CoS associated with a first voicemail system (VMS) (102, 104) to a second CoS associated with a second VMS (102, 104). The method (200, 400) further includes validating the CoS change request (204, 404) at the billing system (109), sending a CoS delete request (206, 406) to the first VMS (102, 104) to at least temporarily disable a first voicemail account, and sending a provisioning request (208, 408) to the second VMS (102, 104) to provision a second voicemail account. A system (100) for toggling voicemail CoS and a computer-readable medium (506) for toggling CoS from a mobile device (118).

Claims

1. A method (200, 400) for toggling voicemail class of service (CoS), the method (200, 400) comprising:

receiving a subscriber-initiated CoS change request (202, 402) at a billing system (109), the CoS change request comprising a request to change from a first CoS associated with a first voicemail system (VMS) (102, 104) to a second CoS associated with a second VMS (102, 104);

validating the CoS change request (204, 404) at the billing system (109);

sending a CoS delete request (206, 406) to the first VMS (102, 104) to at least temporarily disable a first voicemail account; and

sending a provisioning request (208, 408) to the second VMS (102, 104) to provision a second voicemail account.

2. The method (200, 400) of claim 1, wherein the first VMS is a plain old voicemail system (POVMS) (102).

3. The method (200, 400) of claim 2, wherein the second VMS is a visual voicemail system (VVMS) (104).

4. The method (200, 400) of claim 1, wherein the first VMS is a VVMS (104).

5. The method (200, 400) of claim 4, wherein the second VMS is a POVMS (102).

6. The method (200, 400) of claim 1, wherein receiving the subscriber-initiated CoS change request (202, 402) comprises receiving the subscriber-initiated CoS change request (202, 402) from a mobile device (118).

7. The method (200, 400) of claim 6 further comprising:

sending a first boot message (210) to the mobile device (118) if the second VMS (102, 104) is a VVMS (104) and the second voicemail account is a VVM account.

8. The method (200, 400) of claim 1, wherein validating the CoS change request (204, 404) at the billing system (109) comprises determining if a subscriber associated with the first voicemail account is authenticated for service provided by the second VMS (102, 104).

9. A computer-readable medium (506) on a mobile device (118) comprising computer-executable instructions that, when executed, perform the steps of:

receiving an input to toggle (602) between a first voicemail service and a second voicemail service;

generating and sending a voicemail class of service (CoS) change request message (202, 402) based upon the input, the CoS change request comprising a request to change from a first CoS associated with a first voicemail system (VMS) (102, 104) to a second CoS associated with a second VMS (102, 104); and

receiving a notification that a voicemail account is provisioned (308) on the second VMS (102, 104).

10. The computer-readable medium (506) of claim 9, wherein the first voicemail service is a plain old voicemail (POVM) service and the first VMS is a POVM system (POVMS).

11. The computer-readable medium (506) of claim 10, wherein the second voicemail service is a visual voicemail (VVM) service and the second VMS (102, 104) is a VVM system (VVMS) (104).

12. The computer-readable medium (506) of claim 9, wherein the first voicemail service is a VVM service and the first VMS (102, 104) is a VVMS (104).

13. The computer-readable medium (506) of claim 12, wherein the second voicemail service is a POVM service and the second VMS (102, 104) is a POVM system (102).

14. The computer readable medium (506) of claim 12 further comprising:

receiving a first boot message (210) if the second VMS (102, 104) is a VVMS (104) and the second voicemail account is a VVM account.

15. A system (100) for providing a voicemail class of service (CoS) toggle feature, the system (100) comprising:

a mobile device (118) configured to generate and send a subscriber-initiated CoS change request (202, 402), the CoS change request comprising a request to change from a first CoS associated with a first voicemail system (VMS) (102, 104) to a second CoS associated with a second VMS (102, 104); and

a billing system (109) configured to;

receive the subscriber-initiated CoS change request (202, 402);

validate the CoS change request (204, 404);

generate and send a CoS delete request (206, 406) to the first VMS (102, 104) to at least temporarily disable a first voicemail account; and

generate and send a provisioning request (208, 408) to the second VMS (102, 104) to provision a second voicemail account.

16. The system (100) of claim 15, wherein the first VMS (102, 104) is a POVM system (POVMS) (102).

17. The system (100) of claim 16, wherein the second VMS (102, 104) is a VVM system (VVMS) (104).

18. The system (100) of claim 15, wherein the first VMS (102, 104) is a VVMS (104).

19. The system (100) of claim 18, wherein the second VMS (102, 104) is a POVM system (102).

20. The system (100) of claim 15, wherein the billing system (109) is further configured to:

generate and send a first boot message (210) if the second VMS (102, 104) is a VVMS (104) and the second voicemail account is a VVM account.