Abstract:
A method for operating a mobile device to set a voicemail password directly from the mobile device includes providing the mobile device with a memory for storing a visual voicemail (VVM) application, an interface for receiving user input to the VVM application, and a transceiver for communication with a VVM system. The VVM application includes an option to create a voicemail password. The method further includes: receiving a selection of the option to create the voicemail password, creating the voicemail password based upon an input of a password string, generating a request that includes instructions to the VVM system to associate the voicemail password with a voicemail account, and transmitting the request to the VVM system.

Description:
RELATED APPLICATION 
       [0001]    This application is a continuation of U.S. application Ser. No. 12/201,945, filed Aug. 29, 2008, which claims priority to U.S. Application No. 60/969,419, filed Aug. 31, 2007, all of which are hereby incorporated by reference. 
     
    
     TECHNICAL FIELD 
       [0002]    The present disclosure relates generally to voicemail service and, more particularly, to providing enhanced voicemail services. 
       BACKGROUND 
       [0003]    Voicemail systems allow a caller to leave a voice message if the desired recipient is unavailable. Traditional voicemail systems (referred to herein as plain old voicemail or POVM) allow a subscriber to place a call to a voicemail system to access messages stored in his or her voicemail box. This is done through a telephone user interface (TUI) that facilitates interaction between the subscriber and the voicemail system. The TUI provides functions for the subscriber to listen to messages, skip messages, delete messages, and save messages. The TUI also provides functions for the subscriber to set a voicemail greeting, record a voicemail greeting, record a name, and set/change a password. 
         [0004]    A subscriber with multiple voicemail messages is required to listen to, skip, delete, or save each message while reviewing the voicemail box. This is time consuming and can be frustrating for the subscriber in situations where an important message has been deposited, requiring the subscriber to listen to, skip, delete or save each message in search of the important message. 
         [0005]    To help reduce the need to search through multiple messages, various improved voicemail systems have been developed that allow messages to be stored based on a priority scheme to increase the efficiency of listening to voicemail messages. Often, these systems use an identifier, such as a telephone number of the caller, to identify a priority and position the voicemail messages in order based on the assigned priorities. When the recipient accesses the voicemail system to acquire voicemail messages, the recipient is presented with each voicemail message in order of the priority or importance to the recipient. This reduces unwanted listening or skipping through multiple voicemail messages to find an important message. However, an important message can easily be relegated to a position of low importance if the subscriber has not previously set the priority for the caller. In this system, the priority for an incoming voicemail message is determined directly by the telephone number associated with the caller. 
         [0006]    The aforementioned systems fail to allow a subscriber to select the exact voicemail message the subscriber would like to hear. Further, the aforementioned systems require the use of a TUI to access the voicemail system. Still further, these systems merely notify a subscriber of a pending voicemail message with a message waiting indicator (MWI) and require that the subscriber access the voicemail system to retrieve the pending message(s). 
       SUMMARY 
       [0007]    According to one aspect of the present disclosure, a method for operating a mobile device to set a voicemail password directly from the mobile device includes providing the mobile device with a memory for storing a visual voicemail (VVM) application, an interface for receiving user input to the VVM application, and a transceiver for communication with a VVM system. The VVM application can include an option to create a voicemail password. The option can be selected via the interface. The method can further include receiving a selection of the option to create the voicemail password and, in response to receiving the selection, creating the voicemail password based upon an input of a password string received via the interface. In some embodiments, the password string can include a combination characters or numbers and, in other embodiments, the password string can include a combination of characters and numbers. The method can further include generating a request that includes instructions to the VVM system to associate the voicemail password with a voicemail account and transmitting the request to the VVM system. 
         [0008]    In some embodiments, the method can further include receiving a notification from the VVM system that a voicemail message has been received in association with the VVM account and communicating with the VVM system to obtain the voicemail message for storage in the memory. 
         [0009]    In some embodiments, the method can further include generating the request as a “ChangePassword” hypertext transfer protocol (HTTP) request. 
         [0010]    In some embodiments, the method can further include receiving a response to the transmitted request from the VVM system. The response can include an indication of the success or failure of the request. 
         [0011]    In some embodiments, the VVM application can further include an option to change a voicemail password. The method can further include receiving a selection of the change voicemail password option and, in response, prompting entry of the voicemail password, receiving entry of the voicemail password, prompting entry of a new voicemail password to replace the voicemail password, creating the new voicemail password, generating a new request to the VVM system to replaced the voicemail password with the new voicemail password for the voicemail account, and transmitting the new request to the VVM system. 
         [0012]    According to another aspect of the present disclosure, a computer-readable medium includes computer-executable instructions that, when executed by a processor, perform the steps of a method for operating a mobile device to set a voicemail password directly from the mobile device. The method performed when the computer-executable instructions are executed includes the steps set forth in the aforementioned method. 
         [0013]    According to another aspect of the present disclosure, a mobile device includes a processor and a transceiver, in communication with the processor, wherein the transceiver provides a communication interface between the mobile device and a VVM system remote to the mobile device. The mobile device further includes an interface, in communication with the processor, the interface providing a man-machine interface between a user of the mobile device and a VVM application. The mobile device further includes a memory, in communication with the processor, the memory including the VVM application for allowing user interaction via the interface to set a voicemail password directly from the mobile device. The VVM application: receives a selection of an option to create a voicemail password; in response to receiving the selection, creates the voicemail password based upon an input of a password string received via the interface; generates a request including instructions to the VVM system to associate the voicemail password with a voicemail account; and instructs the mobile device to transmit the request to the VVM system via the transceiver. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0014]      FIG. 1  illustrates an exemplary network in which the present disclosure can be implemented. 
           [0015]      FIG. 2  is an exemplary message flow diagram illustrating a process for provisioning a subscriber for visual voicemail service, according to the present disclosure. 
           [0016]      FIG. 3  is an exemplary message flow diagram illustrating a process for first boot access of a mobile device to a visual voicemail system, according to the present disclosure. 
           [0017]      FIG. 4  is an exemplary message flow diagram illustrating a process for setting or changing a voicemail greeting, according to the present disclosure. 
           [0018]      FIG. 5  is an exemplary message flow diagram illustrating a process for setting or changing a voicemail password, according to the present disclosure. 
           [0019]      FIG. 6  is an exemplary message flow diagram illustrating a process for setting or changing a voicemail recorded name, according to the present disclosure. 
           [0020]      FIG. 7  is an exemplary message flow diagram illustrating a process for voicemail message deposit and subsequent retrieval of message content for local storage on a mobile device, according to the present disclosure. 
           [0021]      FIG. 8  is an exemplary message flow diagram illustrating a process for telephone user interface access management, according to the present disclosure. 
           [0022]      FIG. 9  is an exemplary message flow diagram illustrating a process for password encryption, according to the present disclosure. 
           [0023]      FIG. 10  illustrates an exemplary mobile device and components thereof, according to the present disclosure. 
       
    
    
     DETAILED DESCRIPTION 
       [0024]    As required, detailed embodiments of the present disclosure are disclosed herein. It must be understood that the disclosed embodiments are merely exemplary examples of the disclosure that may be embodied in various and alternative forms, and combinations thereof. As used herein, the word “exemplary” is used expansively to refer to embodiments that serve as an illustration, specimen, model or pattern. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular components. In other instances, well-known components, systems, materials or methods have not been described in detail in order to avoid obscuring the present disclosure. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure. 
         [0025]    Referring now to the drawings, wherein like numerals represent like elements throughout the several views,  FIG. 1  illustrates a non-limiting example of a network  100  in which the present disclosure can be implemented. It should be understood that some elements have not been illustrated so as not to obscure the present disclosure. 
         [0026]    Although the present disclosure is applicable to any existing or yet to be developed wireless telecommunications network, aspects of the disclosed architecture are described with reference to the Global System for Mobile communications (GSM) air interface that uses general packet radio service (GPRS) as an enabling bearer. As indicated above, examples of other suitable wireless and radio frequency data transmission systems include networks utilizing time division multiple access (TDMA), frequency division multiple access (FDMA), wideband code division multiple access (WCDMA), orthogonal frequency division multiplexing (OFDM), and various other 2.5G, 3G (third generation), and above wireless communications systems. Examples of other suitable enabling bearers include universal mobile telecommunications system (UMTS), enhanced data rates for global evolution (EDGE), high speed downlink packet access (HSDPA), and similar communications protocols. 
         [0027]    The illustrated network  100  includes a voicemail system (VMS)  102  that is in communication with a content delivery server (CDS)  104  and an unstructured supplementary service data (USSD) server  106 . The VMS  102  can include a telephony server (TS)  108  for handling incoming voicemail inquiries via a telephone user interface (TUI)  109  and a storage server (SS)  110  for storing and managing voicemail messages for voicemail accounts. The USSD server  106  can be configured to receive, decode, and process new USSD messages. The USSD server  106  can be configured to query a database to retrieve a VMS hostname for the VMS (e.g., VMS  102 ) that is serving a mobile device (MD)  118 . The USSD server  106  can be configured to query a database to resolve the VMS hostname to a corresponding IP address. The USSD server  106  can be configured to obtain a subscriber&#39;s voicemail class of service (COS) and send the voicemail COS to the subscriber&#39;s MD  118 . To enable the execution of the aforementioned functions, the USSD server  106  is illustrated as being in communication with a home location register (HLR)  112 , a subscriber database  114 , and a domain name server (DNS)  116 . The USSD server  106  can also be in communication with a mobile switching center/visiting location register (MSC/VLR)  120  and a message waiting indicator (MWI)/short message service center (SMSC)  122 . The illustrated communication links are merely exemplary and are not intended to limit communications between the various network  100  elements via the links shown. 
         [0028]    The subscriber database  114  can be configured to store and manage subscriber data, such as, for example, account information, billing information, services information, and equipment information for subscribers. 
         [0029]    The DNS server  116  can maintain a database for resolving VMS hostnames and IP addresses for various network  100  elements, such as, the VMS  102 , for example. The USSD server  106  can retrieve a VMS hostname from the subscriber database  114  and query the DNS  116  to resolve the IP address for the VMS hostname. 
         [0030]    The HLR  112  can be configured to provide routing information for mobile-terminated calls and short message service (SMS) messages. The HLR  112  is illustrated as being in communication with the MSC/VLR  120 . The MSC/VLR  120  is illustrated as being in communication with the MD  118  and the MWI/SMSC  120  that can be configured for SMS and message waiting indicator (MWI) delivery. Multimedia message service (MMS) center functionality is also contemplated for the MWI/SMSC  120  or can be provided by another network  100  element. The MD  118  can be, but is not limited to, a wireless communications device, a cellular telephone, a WIFI telephone, a WIMAX telephone, a dual-mode telephone, and the like configured to operate on any wireless telecommunications network described herein above. An exemplary MD  118  and components thereof is described with reference to  FIG. 10 . 
         [0031]    The VMS  102  can be configured to store one or more voicemail accounts that can be associated with one or more voicemail boxes. A voicemail account can be assigned to a subscriber and can be associated with the MD  118 . A voicemail box can be a VMS-hosted voicemail box stored in a memory of a VMS. In addition or in the alternative, a voicemail box can be a MD-hosted voicemail box. A MD-hosted voicemail box can be stored in a memory of the MD  118 . The terms “voicemail account” and “voicemail box” as used herein may, at times, be used interchangeably to describe a mobile subscriber&#39;s voicemail access. Accordingly, the MD  118  can include functionality to retrieve and store, in memory, a voicemail message. The MD  118  can receive and store a portion of a newly deposited voicemail message, for example, a voicemail header and can retrieve the voicemail message body at a later time. 
         [0032]    The voicemail service provider or any third party provider can define the number of voicemail messages that can be stored in a voicemail box. The maximum voicemail message length can also be set. The number of voicemail messages and the maximum voicemail message length can be configured on the VMS  102 . 
         [0033]    Prior to a subscriber being provisioned for visual voicemail service, the voicemail box is in a not provisioned state. Upon being provisioned for visual voicemail service, the voicemail box state is changed to provisioned—not initialized to reflect that the subscriber is provisioned for service but has not yet initialized service via a first boot access process described herein below with reference to  FIG. 3 . Upon completion of the first boot access process, the voicemail box state changed to provisioned initialized to reflect that the subscriber is provisioned for voicemail service and has completed the first boot access process. 
         [0034]    The VMS  102  can be accessed via traditional or plain old voicemail (POVM) methods and visual voicemail (VVM) methods described herein. State changes to voicemail messages, whether requested through the TUI  109  via POVM methods or directly on the MD  118 , can be automatically updated in the VMS-hosted voicemail box and the MD-hosted voicemail box. Updates ensure automatic and full synchronization between the MD  118  and the VMS  102  so that up-to-date voicemail information is stored on the MD  118 . 
         [0035]    A VMS-hosted voicemail box can recognize and maintain message states for each voicemail message. A message state can be) but is not limited to, an unheard—new state, a skipped state, and a saved—read state, for example. Messages can be deleted from the VMS  102  via the TUI  109  or directly on the MD  118 . In either case, the message can be deleted on both the VMS  102  and the MD  118 . In an alternative embodiment, deleted messages remain accessible on the MD  118  and/or the VMS  102  for a specified period of time to allow the message to be recovered in the case of accidental or premature deletion. In other embodiments, the VMS  102  discards all messages after the MD  118  has successfully received and stored the available message content. 
         [0036]    A MD-hosted voicemail box can recognize and maintain message states. A message state can be, but is not limited to, an unheard—new state, a saved—read state, and a deleted state. The MD  118  does not require a skipped state because VVM provides an interface that allows a subscriber to access any message regardless of the order in which the message was received and is not subject to restraint of saved orders or priority schemes. As mentioned above, the MD-hosted voicemail box deleted state can be configured such that the message is available for recovery or merely as an indication that the message has been deleted. Either of these options can be set to be available for a time specified by either the subscriber via a device input or by the voicemail service provider. A recover option can be provided on the MD  108  so that a deleted message can be recovered for a designated period of time. 
         [0037]    It should be understood that the illustrated elements are merely exemplary of one network configuration that can be used to implement the various aspects of the present disclosure. In alternative embodiments, some elements can be combined. For example, the CDS  104  can be combined with the VMS  102  and the combined VMS/CDS can provide the functionality of both elements. Other exemplary combinations are contemplated. 
         [0038]    Referring now to  FIG. 2 , a process for provisioning a mobile device for visual voicemail (VVM) is illustrated, according to the present disclosure. In  FIGS. 2-9 , messages are sent using a variety of protocols, such as, for example, short message peer-to-peer (SMPP), DNS protocol, lightweight directory access protocol (LDAP), unstructured supplementary service data (USSD) protocol, Internet message access protocol version 4 (IMAP4), hypertext transfer protocol (HTTP), and HTTP over secure socket layer (HTTPS). The description provided below assumes an understanding of these protocols and as such further explanation is not provided. The use of alternative protocols or additional protocols to acquire similar results is deemed to be within the scope of the present disclosure. Accordingly, logical variations of the illustrated message flow are contemplated. 
         [0039]    In  FIGS. 2-9 , the VMS  102  and the CDS  104  are illustrated as separate elements, although this is not necessarily the case. The VMS  102  and the CDS  104  can be combined such that the functionality of each element is combined. Accordingly, in the illustrated embodiments, messages received by the VMS  102  or CDS  104  would be received by the combined VMS/CDS, and messages sent from the VMS  102  or CDS  104  would be sent from the combined VMS/CDS. Other network elements can be combined in a similar manner. 
         [0040]    The message flow begins at the MD  118  upon detection of a new integrated circuit card ID (ICCID) of a subscriber identity module (SIM) or universal SIM (USIM), at step  200 . If no SIM is present, the process fails and the MD  118  will not perform the remaining functions of this process. For example, if no SIM is inserted, the MD  118  may be configured to only allow emergency calls and prevent all other calls or communication. If a SIM is present, at step  202 , the MD  118  can generate a USSD message and send the message to the HLR  112 . The HLR  112  can receive the USSD message and append a mobile subscriber ISDN number (MSISDN) to the USSD message, at step  204 . At step  206 , the HLR  112  can send the USSD message with the MSISDN to the USSD server  106 . The USSD server  106  can receive the message and submit an LDAP_query to the subscriber database  114  to determine the hostname of the VMS  102  (VM_ID) serving the subscriber, at step  208 . The subscriber database  114  can respond with the proper VM_ID, at step  210 . At step  212 , the USSD server  106  can send a DNS_query to the DNS server  116  to obtain an IP address that corresponds to the VM_ID. The DNS server  116  can resolve the IP address from the VM_ID and submit a DNS_query response to the USSD server  106  that includes the IP address for the VMS  102 , at step  214 . In an alternative embodiment, the IP address for the VMS  102  can be obtained by a data table provisioned on another network element, such as the CDS  104 , for example. 
         [0041]    If no VM_ID is found, the subscriber is not provisioned for voicemail service. The USSD server  106  can generate a message indicating that the subscriber is not provisioned for voicemail service, and send the message to the SMSC  122 , at step  216 . The SMSC  122  can receive the message, generate a short message, and send the message to the MD  118 , at step  218 , to notify the subscriber that voicemail service is not provisioned. If a VM_ID is found, the USSD server  106  can send a query to the VMS  102  to retrieve the voicemail class of service (COS) for the subscriber, at step  220 . At step  222 , the VMS  102  can respond with the subscriber&#39;s COS. At step  224 , the USSD server  106  can send the subscriber&#39;s COS to the SMSC  122 . The SMSC  122  can receive the message, generate a short message that includes the subscriber&#39;s voicemail COS, and send the SM to the MD  118 , at step  226 . In some embodiments, the requesting subscriber will have a COS below the threshold needed for VVM service. In these embodiments, the subscriber may be denied VVM service and the present process may fail. The subscriber may upgrade their service and the present process can repeat. 
         [0042]    A COS can be assigned to each subscriber for the subscribed voicemail service. In networks that offer POVM and VVM, voicemail service subscriptions that include only POVM service can have a COS that provides only POVM service. Likewise, voicemail service subscription that include VVM service can have a COS that enables delivery of or access to VVM service as a stand-alone service or in addition to POVM. 
         [0043]    Upon completion of the provisioning process described above, the subscriber and the associated MD  118  are capable of being initialized via a first boot process that is described in detail immediately below with reference to  FIG. 3 . A VMS  102  voicemail box can be changed from a not provisioned state to a provisioned not initialized state after the provisioning process is complete. 
         [0044]    Referring now to  FIG. 3 , an exemplary process for first boot access of a MD to a VVM system is illustrated, according to the present disclosure. The first boot access process assumes that the subscriber has been provisioned and has the proper voicemail COS for VVM as determined in the process described immediately above in  FIG. 2 . When a subscriber is initially provisioned to the VMS  102  with the appropriate voicemail COS, the subscriber&#39;s account is enabled for voicemail notification via the CDS, for example. The VMS  102  can initiate a notification message to the CDS  104  intended for delivery to the MD  118  via an SMS message. The notification message confirms that VVM service is enabled and accessible via a VVM application stored on the MD  118 . A visual prompt can be presented to the subscriber as a cue or reminder to setup a voicemail box prior to receipt of incoming voice messages. Conversely, POVM blocks receipt of new messages until the mailbox is set up, or notifies the subscriber of the first new voice message thereby prompting the subscriber to place a call to retrieve the new voicemail message and bars access to the message until the subscriber sets up the POVM voicemail box. The visual prompt of the present disclosure advantageously eliminates the annoyance and need to access the voicemail system via the TUI  109  to setup the voicemail box and ensures the subscriber sets up a voicemail box. 
         [0045]    The VVM service can use several parameters to enable automatic synchronization between the MD  118  and the VMS  102 . Prior to first boot, the MD  118  does not have this information. Accordingly, the first boot process described below provides an initial SMS message that includes a set of parameters for future synchronization sessions. 
         [0046]    The message flow begins when the VMS  102  generates an SMPP notification message (notification_SM), at step  300 . For example, a notification_SM message can include, but is not limited to, the hostname and port number for the subscriber&#39;s CDS  104 , a token identifying the subscriber&#39;s VMS  102 , the subscriber&#39;s voicemail box ID (mailbox_ID) embedded with the token to uniquely identify the subscriber for the VMS  102 , and the current VMS password (if the password has not already been set). In an alternative embodiment, the notification_SM can include the IP address and port number for the subscriber&#39;s CDS  104  and the mailbox_ID. The password and token are added to increase security and preserve data integrity. If a password is used, the password may not be encrypted and instead the password can be obscured to hide the actual default password digits. Security aspects of the present disclosure are described in greater detail with reference to  FIG. 9 . 
         [0047]    After the notification_SM is generated, the VMS  102  can send the notification_SM to the CDS  104 , at step  302 . The CDS  104  can receive the notification_SM and generate an application directed notification and send the notification to the SMSC  122 , at step  304 . The SMSC  122  can receive and forward the message to the MD  118 , at step  306 . The application directed SM can be received by the MD  118  and sent to the VVM application stored on the MD  118 . A user may not be notified of the incoming SM. The VVM application can generate any prompts that are necessary to guide the user through setup and other processes identified in the application directed SM upon receipt of the SM or at a time thereafter. 
         [0048]    If the SIM card is removed from the MD  118  and replaced with a new SIM card, the MD  118  can be initially unaware as to whether the new subscriber is subscribed to VVM service. It is assumed that the new subscriber is subscribed to POVM service and can access voicemail via the TUI  109 , however, all VVM functionality is unavailable until the proper provisioning and initialization steps are taken for the new subscriber and SIM. In the meantime, the previous subscriber&#39;s VVM data, including all VVM messages, can be automatically removed or hidden to preserve subscriber privacy. As an exception to the synchronization protocol described above, if messages are removed due to removal of the SIM, those messages are not necessarily removed from the VMS  102 , but can be retained for retrieval when the SIM is reinserted or used with another MD. Upon insertion of the new SIM, the processes described above in  FIGS. 2-3  can substantially repeat for the new subscriber. If the new subscriber is provisioned for VVM service and has performed a first boot process previously on the MD  118  or another VVM compatible device, the new subscriber&#39;s VVM can be acquired and the subscriber can have normal access to VVM service. If the old subscriber chooses to reinsert the SIM, a notification_SM can be sent from the VMS  102  to the MD  118  and VVM service for the old subscriber can resume. The old subscriber&#39;s voicemail message can be retrieved again or un-hidden to recreate a VVM box as it was before the SIMs were swapped. 
         [0049]    For situations in which VVM is temporarily unavailable for network maintenance, device maintenance, or other unforeseen circumstances, the VVM subscriber can access voicemail via the TUI  109  as a default access method. 
         [0050]    Referring now to  FIG. 4 , an exemplary process for setting or changing a voicemail greeting is illustrated, according to the present disclosure. For this process, it is assumed that the VVM application has received the hostname and port number of the serving CDS  104  and the token identifying the VMS  102  in a prior exchange with the CDS  104  and has stored this data for use in setting up a data channel to the CDS  104 . The present process is described for a personal greeting for all calls, however, it should be understood that contact-specific greetings may also be set or changed using similar processes for VMSs that support such greetings. Other greeting types, for example, an extended absence greeting are also contemplated. 
         [0051]    The set/change greeting process can begin when the subscriber records a new voicemail greeting on the MD  118 , at step  400 . The subscriber can then select an upload function on the VVM application to upload the new greeting. The greeting can be formatted using any audio codec, such as, but not limited to, adaptive multi-rate (AMR), AMR wideband (AMR-WB), and any other standardized or independent audio codecs. 
         [0052]    After a new greeting has been recorded, the VVM application can generate a “ChangeGreeting” HTTP request that includes the recorded greeting in the selected format in a MIME message body. The “ChangeGreeting” request can be sent to the CDS  104  for storage, at step  402 . The CDS  104  can receive the “ChangeGreeting” request and send a message, at step  404 , to notify the VMS  102  to save the recording as the primary greeting for the user. If a custom voicemail greeting is not set, the default voicemail greeting (e.g., the network default greeting) can be replaced with the new voicemail greeting. The success or failure of the save can be reported back to the CDS  104 , at step  406 . The CDS  104  can report the success or failure of the “ChangeGreeting” request in a “ChangeGreeting” response, at step  408 . If the “ChangecGreeting” request fails, the VVM application can notify the user to retry, offer customer support, and/or refer the customer to a telephone number or website address for further information and troubleshooting. 
         [0053]    Referring now to  FIG. 5 , an exemplary process for setting or changing a voicemail password is illustrated, according to the present disclosure. For this process, it is assumed that the VVM application has received the hostname and port number of the serving CDS  104  and the token identifying the VMS  102  in a prior exchange with the CDS  104  and has stored this data for use in setting up a data channel to the CDS  104 . If a password has not been set, a default password provided in the notification_SM message can be required to be initialized prior to the subscriber accessing the voicemail box, setting the greeting, or setting a recorded name. If the password has not been initialized, the CDS  104  can send the current password in a notification_SM message. The current password can then be used to access the voicemail box to configure the new password. The password can be any combination of numbers and/or characters and can be any length. In an exemplary embodiment, the password can be set with a minimum and maximum length. The VVM application can be configured to verify that the password length complies with this requirement prior to attempting to change the password on the VMS. If the subscriber enters a password that fails to comply with the length requirement, the VVM application can notify the user to retry with a password that satisfies the minimum and maximum length requirement, offer customer support, and/or refer the customer to a telephone number or website address for further information and troubleshooting. 
         [0054]    The set/change password process can begin when a subscriber is prompted to enter both the old password and the new password. The subscriber can enter the old password and new password on the MD  118 , at step  500 . After the passwords have been entered, the VVM application can generate a “ChangePassword” HTTP request with no MIME message body. The “ChangePassword” request can be sent to the CDS  104  for storage, at step  502 . The CDS  104  can receive the “ChangePassword” request and send a message, at step  504 , to notify the VMS  102  to perform a password validation and to save the new password. The success or failure of the save can be reported back to the CDS  104 , at step  506 . The CDS  104  can report the success or failure of the “ChangePassword” request in a “ChangePassword” response, at step  508 . Error codes can be set for the VMS  102  and/or the CDS  104  to return to the MD  118  in case the password is found invalid for any reason or if the password has expired. The VVM application can be configured to receive an error code and provide corrective action to the subscriber to resolve the password issue. For example, the VVM application can notify the user to retry, offer customer support, and/or refer the customer to a telephone number or website address for further information and troubleshooting. 
         [0055]    After the first boot access process, the password can be encrypted to avoid unauthorized parties from identifying the password and potentially gaining access to the subscriber&#39;s private voicemail data. An exemplary password encryption process is described in detail with reference to  FIG. 9 . 
         [0056]    Referring now to  FIG. 6 , an exemplary process for setting or changing a voicemail recorded name is illustrated, according to the present disclosure. For this process, it is assumed that the VVM application has received the hostname and port number of the serving CDS  104  and the token identifying the VMS  102  in a prior exchange with the CDS  104  and has stored this data for use in setting up a data channel to the CDS  104 . This process can occur during mailbox initialization as directed from the VVM application or at anytime the subscriber desires to change the recorded name. 
         [0057]    The set/change recorded name process can begin when the subscriber records a new name on the MD  118 , at step  600 . The subscriber can select an upload function on the VVM application to upload the new name. The recorded name can be formatted using any audio codec, such as, but not limited to, adaptive multi-rate (AMR), AMR wideband (AMR-WB), or any other standardized or independent audio codec. 
         [0058]    After a new name has been recorded, the VVM application can generate a “ChangeRecordedName” HTTP request that includes the recorded name in the selected format in a MIME message body. The “ChangeRecordedName” request can be sent to the CDS  104  for storage, at step  602 . The CDS  104  can receive the “ChangeRecordedName” request and send a message, at step  604 , to notify the VMS  102  to save the recording as the recorded name for the subscriber. The success or failure of the save can be reported back to the CDS  104 , at step  606 . The CDS  104  can report the success or failure of the “ChangeGreeting” request in a “ChangeGreeting” response, at step  608 . 
         [0059]    The VVM application can be configured to switch between the standard greeting without name, the standard greeting with name, and a custom greeting, for example. The standard greeting can be, for example, a greeting provided by the VM service provider as a default with or without the recorded name. The VVM application can be further configured to retrieve the current voicemail greeting and recorded name using a HTTP request. 
         [0060]    Referring now to  FIG. 7 , an exemplary process for voicemail message deposit and subsequent retrieval of message content for local storage on the MD  118  is illustrated, according to the present disclosure. The process can begin when a message is deposited into the VMS  102 , at step  700 . The VMS can generate a notification_SM at a time after a message is deposited and can send the notification_SM to the CDS  104 , at step  702 . The CDS  104  can forward the message, at step  704 , to the SMSC  122  that, in turn, can forward the message, at step  706 , to the MD  118 . The MD  118  can receive the notification_SM message and can generate an HTTP message get_headers that can be sent to the CDS  104 , at step  708 . The get_headers message can include parameters such as the date, time, and calling line identity (CLI). The get_headers message can additionally include authentication information for IMAP sessions between the CDS and VMS. At step  710 , the CDS  104  can initiate an IMAP session with the VMS  102 . Accordingly, a TCP connection can be established and the get_headers message can be used to authenticate the session, after which the subscriber&#39;s voicemail box can be accessed on the VMS  102  to retrieve the header information for the voicemail messages. The VMS  102  can send the headers to the CDS  104 , at step  712 . The CDS  104  can forward the headers to the MD  118 , at step  714 . The MD  118  can use the headers to determine the status of each message stored on the MD  118  and identify any newly deposited messages. After the MD  118  determines which message(s) needs to be retrieved, the MD  118  can generate and send an HTTP message get_message with the header information for the requested message(s), at step  716 . At step  718 , the message can be received and the CDS  104  can generate and send an IMAP message_request to the VMS  102 . The IMAP message_request can include the requested voicemail message header information. The VMS  102  can process the request and return the requested message content in an IMAP message_response, at step  720 . The CDS  104  can deliver the message content, at step  722 . Upon receipt of the message content, the MD  118  can store the content under the appropriate header in a memory and permit the subscriber to access the content via a VVM application graphical user interface (GUI). The message content can be formatted using any audio codec, such as, but not limited to, adaptive multi-rate (AMR), AMR wideband (AMR-WB), or any other standardized or independent audio codec. 
         [0061]    In some embodiments, an “if-modified-since” HTTP message can be used to occasionally poll the VMS  102  for the inbox voicemail message list and update any voicemail message “if-modified-since” the last update, for example, if a message was deleted or added. This can reduce the amount of data traversing the network thereby reducing network congestion. In some instances, however, the header information is relatively small and as such no noticeable improvement may be achieved for sending only the modified voicemail message header. 
         [0062]    In some embodiments, more than one connection can be established to the VMS  102  or in some cases to multiple or redundant VMS&#39;s. This allows for simultaneous requests in order to serve a subscriber&#39;s request to view or listen to a message faster. Load balancing techniques can also be implemented. 
         [0063]    In some embodiments, message downloads that are interrupted, for example, via cancellation or connection failure, can be resumed starting at the last received byte. These embodiments assume the message is stored in full, at least temporarily, on the CDS  104 . In some instances, however, the CDS  104  can delete the message after the message content is sent to the MD  118 . A subsequent request for one or more previously sent messages can be facilitated by re-retrieving the message, re-transcoding the message, and sending the message to the MD  118 . 
         [0064]    In some embodiments, requests to the CDS  104  can be pipelined in accordance with HTTP standard specifications, thereby reducing network latency for multiple requests. 
         [0065]    Referring now to  FIG. 8 , an exemplary process for TUI management is illustrated, according to the present disclosure. The following process is for the scenario in which a subscriber accesses the TUI  109  via a landline, the MD  118 , or another MD. The process can begin at step  800 , wherein the subscriber places a call to the VMS  102  using the TUI  109 . After the subscriber is granted access to his or her mailbox, the user can listen to, skip, or delete any message. A voicemail box change can occur at step  802 . The subscriber can terminate the call, at step  804 . In response to the subscriber exiting the voicemail box, the VMS  102  can generate a notification_SM message that can be sent to the CDS  104 , at step  806 . The notification_SM message can include the content as described above. At step  808 , the notification_SM message can be forwarded to the SMSC  122 . The SMSC  122 , in turn, can forward the message to the MD  118 , at step  810 . At step  812 , the MD  118  can receive the notification_SM message and generate an HTTP get_headers message that can be sent to the CDS  104 . The MD  118  can use the get_headers message to determine what voicemail information has changed. At step  814 , the CDS  104  can initiate an IMAP session with the VMS  102 . A TCP connection can be established and the get_headers message can be used to authenticate the session. The subscriber&#39;s voicemail box can be accessed on the VMS  102  to retrieve the header information for the voicemail messages. The VMS  102  can send the headers to the CDS  104 , at step  816 . The CDS  104  can forward the headers to the MD  118 , at step  818 . The MD  118  can use the headers to determine if any voicemail box change(s) have occurred. After the MD  118  determines the message(s) that need to be retrieved, the MD  118  can generate and send an HTTP message get_message with the header information for the requested message(s), at step  820 . At step  822 , the get_message message can be received and the CDS  104  can generate and send an IMAP message_request to the VMS  102 . The IMAP message_request can include the requested voicemail message header information The VMS  102  can process the request and return the requested message content in an IMAP message_response, at step  824 . The CDS  104  can deliver the message content, at step  826 . Upon receipt of the message content, the MD  118  can store the content under the appropriate header in a memory (see  FIG. 10 ) and permit the subscriber to access the content via a VVM application GUI. 
         [0066]    In some embodiments, a subscriber can be provisioned to switch between a POVM system and a VVM system upon demand. For example, when traveling internationally, a subscriber may desire to switch to POVM to avoid higher data rate charges for use of VVM service. 
         [0067]    Referring now to  FIG. 9 , a process for password encryption is illustrated, according to the present disclosure. The process can begin at step  900  and the MD  118  can establish a connection with the CDS  104 . The CDS  104  can calculate an encryption key that is specific to the current session, at step  902 . At step  904 , the CDS  104  can send the session-specific encryption key to the MD  118 . The MD  118  can receive the encryption key and response with an HTTP request to the CDS  104  with encrypted password and a decryption key, at step  906 . If the session is intended for a password change process, the old and new passwords can be sent. At step  908 , the CDS  104  can receive and decrypt the password with the decryption key. The CDS  104  can generate an authentication_request to authenticate the password. The authentication_request can be sent to lie VMS  102 , at step  910 . At step  912 , the VMS  102  can respond with an authentication_response indicating the success or failure of the authentication. The CODS  104  can receive the authentication_response and generate a session_success/fail message. The session_success/fail message can be sent to the MD  118 , at step  914 . Assuming a successful authentication, the MD  118  and CDS  104  can conduct any of the aforementioned processes during CDS/MD actions  916 ,  918 ,  920 . The connection can be terminated at step  922  if, for example, the MD  118  closes the connection, there is a connection timeout between the MD  118  and the CDS  104 , or the initial authentication fails. After connection is terminated, the CDS  104  can delete the session-specific key, at step  924 . 
         [0068]      FIG. 10  is a schematic block diagram illustrating an exemplary MD  118  for use in accordance with an exemplary embodiment of the present disclosure. Although no connections are shown between the components illustrated and described in  FIG. 10 , the components can interact with each other to carry out device functions. 
         [0069]    As illustrated, the MD  118  can be a multimode handset.  FIG. 10  and the following discussion are intended to provide a brief, general description of a suitable environment in which the various aspects of an embodiment of the present disclosure can be implemented. While the description includes a general context of computer-executable instructions, the present disclosure can also be implemented in combination with other program modules and/or as a combination of hardware and software. 
         [0070]    Generally, applications can include routines, program modules, programs, components, data structures, and the like. Applications can be implemented on various system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like. 
         [0071]    The device  118  includes a display  1000  for displaying multimedia such as, for example, text, images, video, telephony functions, such as, visual voicemail data, caller line ID data, setup functions, menus, music metadata, messages, wallpaper, graphics, and the like. The display  1000  finds particular application in the present disclosure for displaying visual voicemail data in visual voicemail headers. The visual voicemail headers can include the date, time, CLI data, message length, and message status (i.e., new-unread, read, saved, or deleted). 
         [0072]    The device  118  can include a processor  1002  for controlling, and/or processing data. A memory  1004  can interface with the processor  1002  for the storage of data and/or applications  1006 . The memory  1004  can include a variety of computer readable media, including volatile media, non-volatile media, removable media, and non-removable media. Computer-readable media can include device storage media and communication media. Storage media can include volatile and/or non-volatile, removable and/or non-removable media such as, for example, RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM, DVD, or other optical disk storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information and that can be accessed by the device  118 . 
         [0073]    The memory  1004  can be configured to store one or more applications  1006 , such as, for example, video player software, user feedback component software, combinations thereof, and the like. The applications  1006  can also include a user interface (UI) application  1008 . The UI application  1008  can interface with a client  1010  (e.g., an operating system) to facilitate user interaction with device functionality and data, for example, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multimode interaction, and the like. The applications  1006  can include other applications  1012  such as, for example, visual voicemail software, add-ons, plug-ins, voice recognition software, call voice processing, voice recording, messaging, e-mail processing, video processing, image processing, music play, combinations thereof, and the like, as well as subsystems and/or components. The applications  1006  can be stored in the memory  1004  and/or in a firmware  1014 , and can be executed by the processor  1002 . The firmware  1014  can also store code for execution during initialization of the device  118 . 
         [0074]    A communications component  1016  can interface with the processor  1002  to facilitate wired/wireless communications with external systems including, for example, cellular networks, VoIP networks, LAN, WAN, MAN, PAN, that can be implemented using WiFi, WiMax, combinations and/or improvements thereof, and the like. The communications component  1016  can also include a multimode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver  1018  can operate in one mode, for example, GSM, and an Nth transceiver  1020  can operate in a different mode, for example WiFi. While only two transceivers  1018 ,  1020  are illustrated, it should be appreciated that a plurality of transceivers can be included. The communications component  1016  can also include a transceiver  1022  for unlicensed RF communications using technology such as, for example, WiFi, WiMAX, NFC, other RF and the like. The transceiver  1022  can also be configured for line-of-sight technologies, such as, for example, infrared and IRDA. Although a single transceiver  1022  is illustrated multiple transceivers for unlicensed RF and line-of-sight technologies are contemplated. 
         [0075]    The communications component  1016  can also facilitate communications reception from terrestrial radio networks, digital satellite radio networks, Internet-based radio services networks, combinations thereof, and the like. The communications component  1016  can process data from a network, such as, for example, the Internet, a corporate intranet, a home broadband network, and the like, via an ISP, DSL provider, or other broadband service provider. 
         [0076]    An input/output (I/O) interface  1024  can be provided for input/output of data and/or signals. The I/O interface  1024  can be a hardwire connection, such as, for example, a USB, PS2, IEEE 1394, serial, parallel, IEEE 802.3 (e.g., Ethernet RJ45, RJ48), traditional telephone jack (e.g., RJ11, RJ14, RJ25) and the like, and can accept other I/O devices, such as, for example, a keyboard, keypad, mouse, interface tether, stylus pen, printer, plotter, jump/thumb drive, touch screen, touch pad, trackball, joy stick, controller, monitor, display, LCD, combinations thereof, and the like. 
         [0077]    Audio capabilities can be provided by an audio I/O component  1026  that can include a speaker (not shown) for the output of audio signals and a microphone (not shown) to collect audio signals. 
         [0078]    The device  118  can include a slot interface  1028  for accommodating a subscriber identity system  1030 , such as, for example, a SIM or universal SIM (USIM). The subscriber identity system  1030  instead can be manufactured into the device  118 , thereby obviating the need for a slot interface  1028 . 
         [0079]    The device  118  can include an image capture and processing system  1032 . Photos and/or videos can be obtained via an associated image capture subsystem of the image system  1032 , for example, a camera. The device  118  can also include a video systems component  1034  for processing, recording, and/or transmitting video content. 
         [0080]    A location component  1036  can be included to send and/or receive signals, such as, for example, GPS data, assisted GPS data, triangulation data, combinations thereof, and the like. The device  118  can use the received data to identify its location or can transmit data used by other devices to determine the device  118  location. 
         [0081]    The device  118  can include a power source  1038  such as batteries and/or other power subsystem (AC or DC). The power source  1038  can be single-use, continuous, or rechargeable. In the case of the latter, the power source  1038  can interface with an external power system or charging equipment via a power I/O component  1040 . 
         [0082]    The law does not require and it is economically prohibitive to illustrate and teach every possible embodiment of the present claims. Hence, the above-described embodiments are merely exemplary illustrations of implementations set forth for a clear understanding of the principles of the disclosure. Variations, modifications, and combinations may be made to the above-described embodiments without departing from the scope of the claims. All such variations, modifications, and combinations are included herein by the scope of this disclosure and the following claims.