US20160330599A9 - Secure Visual Voicemail - Google Patents

Secure Visual Voicemail Download PDF

Info

Publication number
US20160330599A9
US20160330599A9 US14/450,971 US201414450971A US2016330599A9 US 20160330599 A9 US20160330599 A9 US 20160330599A9 US 201414450971 A US201414450971 A US 201414450971A US 2016330599 A9 US2016330599 A9 US 2016330599A9
Authority
US
United States
Prior art keywords
mobile device
voicemail
request
visual voicemail
data session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US14/450,971
Other versions
US20140342702A1 (en
Inventor
William Joseph Sigmund
Michael Robert Zubas
Brian Keith Rainer
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nuance Communications Inc
Original Assignee
AT&T Mobility II LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by AT&T Mobility II LLC filed Critical AT&T Mobility II LLC
Priority to US14/450,971 priority Critical patent/US20160330599A9/en
Assigned to AT&T MOBILITY II LLC reassignment AT&T MOBILITY II LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: RAINER, BRIAN KEITH, SIGMUND, WILLIAM JOSEPH, ZUBAS, MICHAEL ROBERT
Publication of US20140342702A1 publication Critical patent/US20140342702A1/en
Publication of US20160330599A9 publication Critical patent/US20160330599A9/en
Assigned to NUANCE COMMUNICATIONS, INC. reassignment NUANCE COMMUNICATIONS, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AT&T MOBILITY II LLC
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16Communication-related supplementary services, e.g. call-transfer or call-hold
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00Handling natural language data
    • G06F40/40Processing or translation of natural language
    • G06F40/58Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/02Calling substations, e.g. by ringing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42017Customized ring-back tones
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42034Calling party identification service
    • H04M3/42042Notifying the called party of information on the calling party
    • H04M3/42051Notifying the called party of information on the calling party where the notification is included in the ringing tone
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42136Administration or customisation of services
    • H04M3/42153Administration or customisation of services by subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533Voice mail systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533Voice mail systems
    • H04M3/53325Interconnection arrangements between voice mail systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533Voice mail systems
    • H04M3/53366Message disposing or creating aspects
    • H04M3/53383Message registering commands or announcements; Greetings
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/537Arrangements for indicating the presence of a recorded message, whereby the presence information might include a preview or summary of the message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/068Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08Access security
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2201/00Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/50Telephonic communication in combination with video communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/45Aspects of automatic or semi-automatic exchanges related to voicemail messaging
    • H04M2203/4518Attachments to voicemail
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/45Aspects of automatic or semi-automatic exchanges related to voicemail messaging
    • H04M2203/4545Message forwarding

Definitions

  • the present disclosure relates generally to voicemail service and, more particularly, to a secure visual voicemail service.
  • 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 often done through a telephone user interface (TUI) that facilitates interaction between the subscriber and the voicemail system.
  • TUI provides functions for the subscriber to listen to messages, skip messages, delete messages, and save messages.
  • the TUI can also provide functions for the subscriber to set a voicemail greeting, record a voicemail greeting, record a name, and set/change a password.
  • 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.
  • the aforementioned systems fail to allow a subscriber to select the exact voicemail message the subscriber would like to hear. Furthermore, the aforementioned systems require the use of a TUI to access the voicemail system to listen to voicemail messages and manage a voicemail account. 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). Thus, it is desirable to create new enhanced voicemail systems and novel methods for providing secure visual voicemail (VVM) services.
  • VVM secure visual voicemail
  • a method for managing incoming voicemail messages for a visual voicemail system can include establishing a secure data session between a voicemail system and a mobile device, receiving a new voicemail message at the voicemail system, wherein the new voicemail message is directed to a voicemail account associated with a voicemail subscriber, generating a notification message in response to the new voicemail message, sending the notification message to the mobile device associated with the voicemail account that received the new voicemail message, receiving a first request for voicemail message header information in response to the notification message, sending the requested voicemail message header information to the mobile device in response to the first request, receiving a second request for at least one voicemail message, and sending the at least one voicemail message to the mobile device in response to the second request.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • SSL secure sockets layer
  • TLS transport layer security
  • a method for setting or changing a voicemail greeting for visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a voicemail greeting, wherein the request can include a new voicemail greeting recorded on the mobile device, and saving the new voicemail greeting at the voicemail system.
  • the method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • SSL secure sockets layer
  • TLS transport layer security
  • a method for changing a password for accessing visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a voicemail password, wherein the request can include an old password and a new password entered on the mobile device, and saving the new password, thereby replacing the old password.
  • the method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • SSL secure sockets layer
  • TLS transport layer security
  • a method for setting or changing a recorded name for a visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a recorded name, wherein the request can include a new recorded name recorded on the mobile device, and saving the new recorded name, thereby replacing an old recorded name.
  • the method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • SSL secure sockets layer
  • TLS transport layer security
  • a method for managing voicemails from a mobile device can include establishing a secure data session between a mobile device and a voicemail system, receiving a notification message identifying that at least one new voicemail message has been deposited into a voicemail account associated with the mobile device, generating a first request for voicemail header information from the voicemail system, sending the first request to the voicemail system, receiving, in response to the first request, the requested voicemail message header information, generating a second request for at least one voicemail message identified in the requested voicemail message header information, sending the second request to the voicemail system, and receiving, in response to the second request, the requested at least one voicemail message.
  • the method can further include saving the at least one voicemail message at least temporarily in a memory of the mobile device.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • FIG. 1 illustrates a portion of an exemplary network in which aspects of the present disclosure can be practiced.
  • FIG. 2 is a message flow diagram illustrating a process for voicemail message deposit and subsequent secure retrieval of message content for local storage on a mobile device, according to an exemplary embodiment present disclosure.
  • FIG. 3 is a message flow diagram illustrating a secure process for setting or changing a voicemail greeting, according to an exemplary embodiment of the present disclosure.
  • FIG. 4 is a message flow diagram illustrating a secure process for setting or changing a voicemail password, according to an exemplary embodiment of the present disclosure.
  • FIG. 5 is a message flow diagram illustrating a secure process for setting or changing a recorded name, according to an exemplary embodiment of the present disclosure.
  • FIG. 6 schematically illustrates an exemplary mobile device and components thereof for use in accordance with an embodiment of the present disclosure.
  • FIG. 1 schematically illustrates a portion of an exemplary wireless communications network 100 in which some embodiments of the present disclosure can be implemented.
  • the wireless communications network 100 can be configured as a 2G GSM (Global System for Mobile communications) network and can provide data communications via GPRS (General Packet Radio Service), and EDGE (Enhanced Data rates for GSM Evolution).
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data rates for GSM Evolution
  • the wireless communications network 100 can be configured as a 3G UMTS (Universal Mobile Telecommunications System) network and provide data communications via the HSPA (High-Speed Packet Access) protocol family, such as, HSDPA (High-Speed Downlink Packet Access), EUL (Enhanced Uplink) or otherwise termed HSUPA (High-Speed Uplink Packet Access), and HSPA+(Evolved HSPA).
  • HSPA High-Speed Packet Access
  • HSDPA High-Speed Downlink Packet Access
  • EUL Enhanced Uplink
  • HSUPA High-Speed Uplink Packet Access
  • HSPA+(Evolved HSPA) High-Speed Packet Access
  • the wireless communications network 100 is also compatible with future mobile communications standards including, but not limited to, pre-4G and 4G, for example.
  • the wireless communications network 100 can be configured to provide messaging services via Short Message Service (SMS), Multimedia Message Service (MMS), instant messaging and unstructured supplementary service data (USSD), for example.
  • SMS Short Message
  • the illustrated wireless communications network 100 includes a voicemail system (VMS) 102 that is illustrated as being in communication with a content delivery server (CDS) 104 , a USSD server 106 , and a mobile switching center (MSC) and visiting location register (VLR) 107 , although this is not necessarily the case.
  • 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 a plurality of voicemail accounts.
  • TS telephony server
  • TTI telephone user interface
  • SS storage server
  • the USSD server 106 can be configured to receive, decode, and process new USSD messages, perform database queries to retrieve the VMS hostname serving a subscriber, perform database queries to resolve the VMS hostname to the corresponding IP address, obtain the subscriber's voicemail class of service (COS), and send the subscriber's voicemail COS to the subscriber's mobile device.
  • 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 to facilitate these functions.
  • HLR home location register
  • DNS domain name server
  • 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 a plurality of subscribers.
  • the DNS server 116 can be configured to maintain a database for resolving host names and IP addresses for various network nodes, such as the VMS 102 , for example.
  • the USSD server 106 can retrieve the VMS hostname serving a subscriber from the subscriber database 114 and query the DNS 116 by specifying the VMS hostname to resolve the corresponding IP address.
  • 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 107 .
  • the MSC/VLR 107 is in communication with a MD 118 and a short message service center (SMSC) 122 .
  • the MD 118 can be, but is not limited to, a user equipment, a mobile terminal, a cellular telephone, a personal digital assistant (PDA), a handheld computer, or combinations thereof, and the like.
  • the SMSC 122 can be configured to deliver SMS messages and message waiting indicator (MWI) messages.
  • MMI message waiting indicator
  • the VMS 102 can be configured to store a plurality of voicemail accounts.
  • Each voicemail account can include a voicemail box in which voicemail messages can be deposited for a subscriber.
  • the number of voicemail messages capable of being stored per account can be determined by the voicemail service provider or any third party provider, such as the system manufacturer, for example.
  • the maximum voicemail message length can also be set, if desired.
  • the number of voicemail messages and the maximum voicemail message length can be configured on the VMS 102 .
  • the voicemail box Prior to a subscriber being provisioned for visual voicemail service, the voicemail box is in a not provisioned state. After being provisioned for visual voicemail service, the subscriber's 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 boot message process that is described below. After completion of the boot message process, the VMS 102 state can be changed to provisioned—initialized to reflect that the subscriber is provisioned for voicemail service and has completed the first boot access process.
  • the VMS 102 is accessible 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 via VVM methods, are automatically updated in both the voicemail box and on the subscriber's MD 118 . This ensures automatic and full synchronization between the subscriber's MD 118 and the VMS 102 so that the latest voicemail information is stored on the subscriber's MD 118 .
  • the subscriber's VMS-hosted voicemail box recognizes and maintains message states for each message, such as, but not limited to, an unheard—new state, a skipped state, and a saved—read state.
  • Deleted messages can be deleted from the VMS 102 , via the TUI 109 or directly on the MD 118 .
  • the message is deleted on both the VMS 102 and the MD 118 .
  • a message can remain accessible on the MD 118 and/or on the VMS 102 for a specified period of time to allow the message to be recovered in the case of accidental or premature deletion.
  • the VMS 102 can discard all messages after the MD 118 has successfully received and stored the available message content.
  • the MD 118 voicemail box also can recognize and maintain message states.
  • the MD 118 voicemail box can have message states for each message including, but 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 a priority scheme.
  • the MD 118 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.
  • Messages used to establish and/or update a VVM account can be sent using a variety of protocols, such as, but not limited to, short message peer-to-peer (SMPP), domain name server (DNS) protocol, lightweight directory access protocol (LDAP), unstructured supplementary service data (USSD) protocol, Internet message access protocol version 4 (IMAP4), and hypertext transfer protocol (HTTP), HTTP over secure socket layer (HTTPS), for example.
  • protocols to provide or enhance the security of data transmission to and from the various nodes described above can be provided via cryptographic protocols, such as, but not limited to, transport layer security (TLS), secure sockets layer (SSL), improvements, versions, variations, or evolutions thereof, and the like.
  • TLS transport layer security
  • SSL secure sockets layer
  • a first boot process can enable a subscriber to receive confirmation that VVM service is enabled and is immediately accessible via a VVM application 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.
  • Conventional voicemail in contrast, can block receipt of new messages until the mailbox is set up, or can notify the subscriber of the first new voice messages thereby prompting the subscriber to place a call to retrieve them, but can bar access to those messages until the subscriber sets up the mailbox.
  • the visual prompt of the present disclosure advantageously can eliminate the need to access the voicemail system 102 via the TUI 109 to setup the voicemail box and can help to ensure that the subscriber sets up a voicemail box.
  • the notification message also can be used to reset a voicemail password after a voicemail account is enabled.
  • the VVM service uses several parameters to enable automatic synchronization between the MD 118 and the VMS 102 .
  • the MD 118 does not have the CDS ID, port number, mailbox ID, initial or reset password, and a token value, if applicable.
  • an initial or first boot SMPP message can include a basic set of parameters for future synchronization sessions including a default password. If a subscriber forgets the password or otherwise needs to have the voicemail password reset, the subscriber can initiate a password reset by selecting a password reset option on the MD 118 . In this example, a new boot message can be sent to the MD 118 including a new default password in response to a password reset request from the MD 118 .
  • FIG. 2 a flow diagram illustrating a process 200 for voicemail message deposit and subsequent secure retrieval of message content for local storage on a mobile device 118 is illustrated, according to an exemplary embodiment of the present disclosure.
  • the steps of the process 200 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated.
  • the steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims.
  • the illustrated process 200 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • the process 200 is illustrated as including the VMS 102 , the SMSC 122 , and the MD 118 .
  • various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, SMPP and HTTPS, although other protocols are contemplated as described above.
  • the process 200 can be modified to include other network elements, such as the CDS 104 .
  • CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102 .
  • the CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • the process 200 begins, at step 202 , when a message is deposited into a voicemail box established at the VMS 102 .
  • the VMS 102 can generate a notification short message (notification_sm) and send the notification_sm to the SMSC 122 , at step 206 .
  • the SMSC 122 can temporarily store and forward the notification_sm message to the MD 118 , at step 208 .
  • the MD 118 can attach to a data network, for example, by a GPRS attach process and can perform a PDP context activation to connect to the data network via an access point name (APN) provided to the MD 118 by the service provider.
  • the APN can be included in the notification_sm message, in a first boot message, or other communication between the MD 118 and the VMS 102 or other network elements, such as the CDS 104 , a serving GPRS support node (SGSN), or a gateway GPRS support node (GGSN), for example.
  • SGSN serving GPRS support node
  • GGSN gateway GPRS support node
  • the MD 118 can perform these functions as is known in the art at any time prior to activating a secure handshake process 212 .
  • the handshake process 212 can be a handshake process of a cryptographic protocol, such as, but not limited to, SSL or TLS.
  • the illustrated secure handshake process 212 establishes the MD 118 as the client and the VMS 102 as the server, although this is not necessarily the case.
  • references to client refer to the MD 118 and references to server refer to the VMS 102 in the illustrated embodiment and description thereof.
  • the secure handshake process 212 begins when the MD 118 generates and sends a client_hello command to the VMS 102 , at step 214 .
  • the client_hello command can include the version(s) of SSL or TLS that is supported by the MD 118 , the cipher(s) supported by the MD 118 sorted in order of preference, the data compression algorithm(s) that is supported by the MD 118 , and a session ID.
  • the client_hello command can also include random data that is generated by the MD 118 for use in a key generation process.
  • the VMS 102 receives the client_hello command and, in response, generates and sends a server_hello command to the MD 118 .
  • the server_hello command can include the SSL or TLS version that will be used for the secure session, the cipher that will be used for the secure session, the session ID, and, if applicable, the compression algorithm that will be used for the secure session.
  • the server_hello command can also include random data that is generated by the VMS 102 for use in a key generation process.
  • the VMS 102 can generate and send a certificate command to the MD 118 .
  • the certificate command can include a public key and an authentication signature.
  • the certificate command can include a chain of certificates beginning with the certificate of the certificate authority that assigned the server's certificate.
  • the VMS 102 can generate and send a server_done command to the MD 118 to indicate that the VMS 102 has completed this phase of the secure handshake process 212 . If the MD 102 will be authenticated to the VMS 102 , additional commands can flow between the MD 118 and the VMS 102 . For example, the MD 118 can provide a certificate to authenticate to the VMS 102 . This certificate can be sent, for example, in the first boot message, or other communication.
  • the MD 118 can verify the server's certificate and can generate and send a certificate_verify command to the VMS 102 to inform the VMS 102 that the MD 118 has verified the certificate.
  • the VMS 102 can verify a client certificate, should one be used, and can generate and send a similar certificate_verify command to the MD 118 to inform the MD 118 that the VMS 102 has verified the certificate.
  • the MD 118 can generate and send a change_cipher_spec command to convey to the VMS 102 that the contents of subsequent SSL transmissions sent by the MD 118 will be encrypted.
  • the MD 118 can generate and send a finished command to the VMS 102 .
  • the finished command can include a list of all secure handshake commands exchanged between the MD 118 and the VMS 102 to validate that none of the unencrypted commands sent to establish a secure session were changed.
  • the VMS 102 can generate and send a change_cipher_spec command to convey to the MD 118 that the contents of subsequent SSL transmissions sent by the VMS 102 will be encrypted.
  • the VMS 102 can then generate and send a finished command.
  • the finished command can include a list of all secure handshake commands exchanged between the VMS 102 and MD 118 to validate that none of the unencrypted commands sent to establish a secure session were changed.
  • a secure session 232 is now established. HTTPS is described as the protocol used to send the various commands between the VMS 102 and the MD 118 in the secure session 232 , although other secure protocols are contemplated, as described above.
  • the secure session 232 can begin when the MD 118 generates and sends a get_headers command to the VMS 102 , at step 234 .
  • the get_headers command can include parameters, such as, but not limited to, the date, time, and calling line identity (CLI).
  • the get_headers message can additionally include authentication information.
  • the VMS 102 retrieves the voicemail message headers for the voicemail account associated with the MD 118 and sends the headers to the MD 118 .
  • the MD 118 uses the headers to determine the status of each voicemail message stored on the MD 118 and to identify any new voicemail messages in the subscriber's voicemail account.
  • the MD 118 After the MD 118 determines which message(s) needs to be retrieved, if any, the MD 118 can generate and send a get_message command with the header information for at least one requested message, at step 238 .
  • the VMS 102 receives the get_message command and sends the requested message content to the MD 118 .
  • the secure session 232 can end at step 242 .
  • the MD 118 can receive the message content and store the content under the appropriate header in a memory and permit a 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • WAV waveform audio
  • AIFF audio interchange file format
  • RAW encoded in GSM CODEC
  • AAC advanced audio coding
  • MP3 MPEG-1 audio layer 3
  • WMA Windows® media audio
  • RA RealAudio
  • FLAC free loss
  • An if-modified-since command can be used to occasionally poll the VMS 102 for an inbox voicemail message list and update any voicemail message if the voicemail was modified since the last update, for example, if a message was deleted or added. This can help 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 available for sending only the modified voicemail message header.
  • More than one connection can be established to the VMS 102 or in some cases to multiple or redundant VMSs. This can allow for simultaneous requests in order to serve a subscriber's request to view or listen to a message faster. Load balancing techniques can also be implemented.
  • Message downloads that are interrupted, via cancellation or connection failure can be resumed starting at the last received byte, for example. This assumes the message is stored in full, at least temporarily, on the VMS 102 . In some instances, however, the VMS 102 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 .
  • Requests to the VMS 102 can be pipelined in accordance with HTTP 1.1 specifications. This can help reduce network latency for multiple requests.
  • FIG. 3 a flow diagram illustrating a secure process 300 for setting or changing a voicemail greeting is illustrated, according to an exemplary embodiment of the present disclosure.
  • the steps of the process 300 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated.
  • the steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims.
  • the illustrated process 300 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • the process 300 is illustrated as including the VMS 102 , the SMSC 122 , and the MD 118 .
  • various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above.
  • the process 300 can be modified to include other network elements, such as the CDS 104 .
  • the CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102 .
  • the CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • the illustrated process 300 begins at step 302 , wherein the MD 118 records a new voicemail greeting, such as, for example, a voicemail greeting dictated by a subscriber.
  • the subscriber can 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • WAV waveform audio
  • AIFF audio interchange file format
  • RAW encoded in GSM CODEC
  • AAC advanced audio coding
  • MP3 MPEG-1 audio layer 3
  • MP4 MPEG-4 Part 14
  • the MD 118 can establish a secure session using, for example, SSL or TLS, via a secure handshake process 212 , as described in FIG. 2 .
  • the MD 118 can generate and send a change_greeting_request to the VMS 102 via HTTPS, for example.
  • the change_greeting_request can include the recorded greeting in one or more formats.
  • the change_greeting_request can be sent to the VMS 102 .
  • the VMS 102 can save the recording as the active or primary voicemail greeting for the subscriber. If a custom voicemail greeting is not set, a default voicemail greeting (e.g., a network default greeting) can be replaced with the new voicemail greeting.
  • the success or failure of the save can be reported back to the MD 118 via a change_greeting_response. If the change_greeting_request fails, the VVM application can notify the subscriber to retry, offer customer support, and/or refer the subscriber to a telephone number or website address for further information and troubleshooting.
  • FIG. 4 a message flow diagram illustrating a secure process 400 for setting or changing a voicemail password is illustrated, according to an exemplary embodiment of the present disclosure.
  • the steps of the process 400 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated.
  • the steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims.
  • the illustrated process 400 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • the process 400 is illustrated as including the VMS 102 , the SMSC 122 , and the MD 118 .
  • various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above.
  • the process 400 can be modified to include other network elements, such as the CDS 104 .
  • the CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102 .
  • the CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • the default password provided in a notification_sm 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 VMS 102 can send the current password in a notification_sm message.
  • the current password can 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.
  • the password can be set with a minimum and maximum length.
  • the VVM application can be configured to verify that the password complies with this requirement prior to attempting to change the password on the VMS 102 .
  • the password can be set with a minimum or maximum amount of numbers and/or characters.
  • the VVM application can be configured to verify that the password complies with this requirement prior to attempting to change the password on the VMS 102 . Other requirements can be established. If the subscriber enters a password that fails to comply with any requirement, the VVM application can notify the user to retry with a password that satisfies the requirement(s), offer customer support, and/or refer the customer to a telephone number or website address for further information and troubleshooting.
  • the illustrated process 400 begins when the subscriber is prompted to enter both the old password and the new password.
  • the MD 118 can establish a secure session using, for example, SSL or TLS, via a secure handshake process 212 , as described above in FIG. 2 , so that any password sent between the MD 118 and the VMS 102 is encrypted.
  • the subscriber can enter the old password and new password on the MD 118 .
  • the VVM application can generate a change_password_request.
  • the change_password_request can be sent to the VMS 102 for storage, at step 404 .
  • the VMS 102 can perform a password validation and save the new password.
  • the VMS 102 can generate and send a change_password_response to report the success or failure of the change_password_request. Error codes can be set for the VMS 102 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.
  • FIG. 5 a message flow diagram illustrating a secure process for setting or changing a recorded name is illustrated, according to an exemplary embodiment of the present disclosure.
  • the steps of the process 500 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated.
  • the steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims.
  • the illustrated process 500 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • the process 500 is illustrated as including the VMS 102 , the SMSC 122 , and the MD 118 .
  • various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above.
  • the process 500 can be modified to include other network elements, such as the CDS 104 .
  • CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102 .
  • the CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • the process 500 can begin when a subscriber records a new name on the MD 118 , at step 502 .
  • the subscriber can then 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • WAV waveform audio
  • AIFF audio interchange file format
  • RAW encoded in GSM CODEC
  • AAC advanced audio coding
  • MP3 MPEG-1 audio layer 3
  • WMA Windows® media audio
  • RA RealAudio
  • the MD 118 can establish a secure session using, for example, SSL or TSL, via a secure handshake process 212 , as described above in FIG. 2 , so that any password sent between the MD 118 and the VMS 102 is encrypted.
  • the VVM application can generate a change_recorded_name_request containing the recorded name in the selected format, at step 504 .
  • the VMS 102 can receive the change_recorded_name_request and save the new recorded name.
  • the VMS 102 can generate a change_recorded_name_response to report the success or failure of the save and send the change_recorded_name_response to the MD 118 , at step 506 .
  • the VVM application can be configured to switch between the standard greeting without name, the standard greeting with name, and a custom greeting.
  • 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.
  • FIG. 6 is a schematic block diagram illustrating an exemplary mobile device 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. 6 , the components can interact with each other to carry out device functions.
  • the mobile device 118 can be a multimode handset.
  • FIG. 6 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.
  • 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.
  • the illustrated device 118 includes a display 600 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 600 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).
  • the device 118 can include a processor 602 for controlling, and/or processing data.
  • a memory 604 can interface with the processor 602 for the storage of data and/or applications 606 .
  • the memory 604 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 .
  • the memory 604 can be configured to store one or more applications 606 .
  • the applications 606 can include a user interface (UI) application 608 .
  • the UI application 608 can interface with a client 610 (e.g., an operating system) to facilitate user interaction with device functionality and data, for example, managing voicemails in a visual voicemail application, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multimode interaction, and the like.
  • the applications 606 can include other applications 612 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 606 can be stored in the memory 604 and/or in a firmware 614 , and can be executed by the processor 602 .
  • the firmware 614 can also store code for execution during initialization of the device 118 .
  • a communications component 616 can interface with the processor 602 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 616 can also include a multimode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver 618 can operate in one mode, for example, GSM, and an Nth transceiver 620 can operate in a different mode, for example WiFi. While only two transceivers 618 , 620 are illustrated, it should be appreciated that a plurality of transceivers can be included.
  • the communications component 616 can also include a transceiver 622 for unlicensed RF communications using technology such as, for example, WiFi, WiMAX, NFC, other RF and the like.
  • the transceiver 622 can also be configured for line-of-sight technologies, such as, for example, infrared and IRDA. Although a single transceiver 622 is illustrated multiple transceivers for unlicensed RF and line-of-sight technologies are contemplated.
  • the communications component 616 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 616 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.
  • An input/output (I/O) interface 624 can be provided for input/output of data and/or signals.
  • the I/O interface 624 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.
  • 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.
  • Audio capabilities can be provided by an audio I/O component 626 that can include a speaker (not shown) for the output of audio signals and a microphone (not shown) to collect audio signals.
  • the device 118 can include a slot interface 628 for accommodating a subscriber identity system 630 , such as, for example, a SIM or universal SIM (USIM).
  • a subscriber identity system 630 such as, for example, a SIM or universal SIM (USIM).
  • the subscriber identity system 630 instead can be manufactured into the device 118 , thereby obviating the need for a slot interface 628 .
  • the device 118 can include an image capture and processing system 632 . Photos and/or videos can be obtained via an associated image capture subsystem of the image system 632 , for example, a camera.
  • the device 118 can also include a video systems component 634 for processing, recording, and/or transmitting video content.
  • a location component 636 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.
  • the device 118 can include a power source 638 such as batteries and/or other power subsystem (AC or DC).
  • the power source 638 can be single-use, continuous, or rechargeable. In the case of the latter, the power source 638 can interface with an external power system or charging equipment via a power I/O component 640 .

Abstract

A method for managing voicemail messages for a visual voicemail system can include establishing a secure data session between a voicemail system and a mobile device. The voicemail system can receive a voicemail message that is directed to a voicemail account associated with a voicemail subscriber. The voicemail system can generate a notification message and can send the notification message to the mobile device that is associated with the voicemail account that received the voicemail message. In response to the notification message, the mobile device can generate and send a first request for voicemail message header information. The voicemail system can send the requested voicemail message header information to the mobile device and, in response, receive a second request for at least one voicemail message. The voicemail message can send at least a portion of the at least one voicemail message to the mobile device.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This application claims priority to U.S. patent application Ser. No. 12/160,946, filed Jul. 15, 2008, which is a 371 of International Patent Application No. 2008/065046, filed May 29, 2008, which claims priority to U.S. Provisional Patent Application No. 60/969,419, filed Aug. 31, 2007, the entirety of which are hereby incorporated by reference.
  • TECHNICAL FIELD
  • The present disclosure relates generally to voicemail service and, more particularly, to a secure visual voicemail service.
  • BACKGROUND
  • 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 often 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 can also provide functions for the subscriber to set a voicemail greeting, record a voicemail greeting, record a name, and set/change a password.
  • With some voicemail systems, 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.
  • 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 a telephone number of the caller to identify a priority for a message 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. Accordingly, the recipient is must listen to and/or skip through multiple voicemail messages to find an important message. However, an important message can be easily relegated to a position of low importance if the subscriber previously has not 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.
  • The aforementioned systems fail to allow a subscriber to select the exact voicemail message the subscriber would like to hear. Furthermore, the aforementioned systems require the use of a TUI to access the voicemail system to listen to voicemail messages and manage a voicemail account. 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). Thus, it is desirable to create new enhanced voicemail systems and novel methods for providing secure visual voicemail (VVM) services.
  • SUMMARY
  • A method for managing incoming voicemail messages for a visual voicemail system can include establishing a secure data session between a voicemail system and a mobile device, receiving a new voicemail message at the voicemail system, wherein the new voicemail message is directed to a voicemail account associated with a voicemail subscriber, generating a notification message in response to the new voicemail message, sending the notification message to the mobile device associated with the voicemail account that received the new voicemail message, receiving a first request for voicemail message header information in response to the notification message, sending the requested voicemail message header information to the mobile device in response to the first request, receiving a second request for at least one voicemail message, and sending the at least one voicemail message to the mobile device in response to the second request. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • A method for setting or changing a voicemail greeting for visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a voicemail greeting, wherein the request can include a new voicemail greeting recorded on the mobile device, and saving the new voicemail greeting at the voicemail system. The method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • A method for changing a password for accessing visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a voicemail password, wherein the request can include an old password and a new password entered on the mobile device, and saving the new password, thereby replacing the old password. The method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • A method for setting or changing a recorded name for a visual voicemail service can include establishing a secure data session between a voicemail system and a mobile device, receiving a request from the mobile device to change a recorded name, wherein the request can include a new recorded name recorded on the mobile device, and saving the new recorded name, thereby replacing an old recorded name. The method can further include generating a response indicating the success or failure of the request, and sending the response to the mobile device. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • A method for managing voicemails from a mobile device can include establishing a secure data session between a mobile device and a voicemail system, receiving a notification message identifying that at least one new voicemail message has been deposited into a voicemail account associated with the mobile device, generating a first request for voicemail header information from the voicemail system, sending the first request to the voicemail system, receiving, in response to the first request, the requested voicemail message header information, generating a second request for at least one voicemail message identified in the requested voicemail message header information, sending the second request to the voicemail system, and receiving, in response to the second request, the requested at least one voicemail message. The method can further include saving the at least one voicemail message at least temporarily in a memory of the mobile device. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example. Establishing the secure data session between the voicemail system and the mobile device can include establishing a secure sockets layer (SSL) data session or a transport layer security (TLS) data session, for example.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 illustrates a portion of an exemplary network in which aspects of the present disclosure can be practiced.
  • FIG. 2 is a message flow diagram illustrating a process for voicemail message deposit and subsequent secure retrieval of message content for local storage on a mobile device, according to an exemplary embodiment present disclosure.
  • FIG. 3 is a message flow diagram illustrating a secure process for setting or changing a voicemail greeting, according to an exemplary embodiment of the present disclosure.
  • FIG. 4 is a message flow diagram illustrating a secure process for setting or changing a voicemail password, according to an exemplary embodiment of the present disclosure.
  • FIG. 5 is a message flow diagram illustrating a secure process for setting or changing a recorded name, according to an exemplary embodiment of the present disclosure.
  • FIG. 6 schematically illustrates an exemplary mobile device and components thereof for use in accordance with an embodiment of the present disclosure.
  • DETAILED DESCRIPTION
  • 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.
  • Referring now to the drawings wherein like numerals represent like elements throughout the several views, FIG. 1 schematically illustrates a portion of an exemplary wireless communications network 100 in which some embodiments of the present disclosure can be implemented. By way of example, the wireless communications network 100 can be configured as a 2G GSM (Global System for Mobile communications) network and can provide data communications via GPRS (General Packet Radio Service), and EDGE (Enhanced Data rates for GSM Evolution). By way of further example, the wireless communications network 100 can be configured as a 3G UMTS (Universal Mobile Telecommunications System) network and provide data communications via the HSPA (High-Speed Packet Access) protocol family, such as, HSDPA (High-Speed Downlink Packet Access), EUL (Enhanced Uplink) or otherwise termed HSUPA (High-Speed Uplink Packet Access), and HSPA+(Evolved HSPA). The wireless communications network 100 is also compatible with future mobile communications standards including, but not limited to, pre-4G and 4G, for example. The wireless communications network 100 can be configured to provide messaging services via Short Message Service (SMS), Multimedia Message Service (MMS), instant messaging and unstructured supplementary service data (USSD), for example. The wireless communications network 100 can also be configured to provide advanced voicemail messaging features, such as visual voicemail.
  • The illustrated wireless communications network 100 includes a voicemail system (VMS) 102 that is illustrated as being in communication with a content delivery server (CDS) 104, a USSD server 106, and a mobile switching center (MSC) and visiting location register (VLR) 107, although this is not necessarily the case. 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 a plurality of voicemail accounts.
  • The USSD server 106 can be configured to receive, decode, and process new USSD messages, perform database queries to retrieve the VMS hostname serving a subscriber, perform database queries to resolve the VMS hostname to the corresponding IP address, obtain the subscriber's voicemail class of service (COS), and send the subscriber's voicemail COS to the subscriber's mobile device. 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 to facilitate these functions.
  • 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 a plurality of subscribers. The DNS server 116 can be configured to maintain a database for resolving host names and IP addresses for various network nodes, such as the VMS 102, for example. The USSD server 106 can retrieve the VMS hostname serving a subscriber from the subscriber database 114 and query the DNS 116 by specifying the VMS hostname to resolve the corresponding IP address.
  • 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 107. The MSC/VLR 107 is in communication with a MD 118 and a short message service center (SMSC) 122. The MD 118 can be, but is not limited to, a user equipment, a mobile terminal, a cellular telephone, a personal digital assistant (PDA), a handheld computer, or combinations thereof, and the like. The SMSC 122 can be configured to deliver SMS messages and message waiting indicator (MWI) messages.
  • The VMS 102 can be configured to store a plurality of voicemail accounts. Each voicemail account can include a voicemail box in which voicemail messages can be deposited for a subscriber. The number of voicemail messages capable of being stored per account can be determined by the voicemail service provider or any third party provider, such as the system manufacturer, for example. The maximum voicemail message length can also be set, if desired. The number of voicemail messages and the maximum voicemail message length can be configured on the VMS 102.
  • Prior to a subscriber being provisioned for visual voicemail service, the voicemail box is in a not provisioned state. After being provisioned for visual voicemail service, the subscriber's 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 boot message process that is described below. After completion of the boot message process, the VMS 102 state can be changed to provisioned—initialized to reflect that the subscriber is provisioned for voicemail service and has completed the first boot access process.
  • The VMS 102 is accessible 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 via VVM methods, are automatically updated in both the voicemail box and on the subscriber's MD 118. This ensures automatic and full synchronization between the subscriber's MD 118 and the VMS 102 so that the latest voicemail information is stored on the subscriber's MD 118. The subscriber's VMS-hosted voicemail box recognizes and maintains message states for each message, such as, but not limited to, an unheard—new state, a skipped state, and a saved—read state. Deleted messages can be deleted from the VMS 102, via the TUI 109 or directly on the MD 118. The message is deleted on both the VMS 102 and the MD 118. Alternatively, a message can remain accessible on the MD 118 and/or on the VMS 102 for a specified period of time to allow the message to be recovered in the case of accidental or premature deletion. The VMS 102 can discard all messages after the MD 118 has successfully received and stored the available message content.
  • The MD 118 voicemail box also can recognize and maintain message states. The MD 118 voicemail box can have message states for each message including, but 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 a priority scheme. As mentioned above, the MD 118 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.
  • Messages used to establish and/or update a VVM account can be sent using a variety of protocols, such as, but not limited to, short message peer-to-peer (SMPP), domain name server (DNS) protocol, lightweight directory access protocol (LDAP), unstructured supplementary service data (USSD) protocol, Internet message access protocol version 4 (IMAP4), and hypertext transfer protocol (HTTP), HTTP over secure socket layer (HTTPS), for example. Moreover, protocols to provide or enhance the security of data transmission to and from the various nodes described above can be provided via cryptographic protocols, such as, but not limited to, transport layer security (TLS), secure sockets layer (SSL), improvements, versions, variations, or evolutions thereof, and the like. 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 and the attached claims.
  • A first boot process can enable a subscriber to receive confirmation that VVM service is enabled and is immediately accessible via a VVM application 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. Conventional voicemail, in contrast, can block receipt of new messages until the mailbox is set up, or can notify the subscriber of the first new voice messages thereby prompting the subscriber to place a call to retrieve them, but can bar access to those messages until the subscriber sets up the mailbox. The visual prompt of the present disclosure advantageously can eliminate the need to access the voicemail system 102 via the TUI 109 to setup the voicemail box and can help to ensure that the subscriber sets up a voicemail box. The notification message also can be used to reset a voicemail password after a voicemail account is enabled.
  • The VVM service uses several parameters to enable automatic synchronization between the MD 118 and the VMS 102. For example, prior to first boot, the MD 118 does not have the CDS ID, port number, mailbox ID, initial or reset password, and a token value, if applicable. Accordingly, an initial or first boot SMPP message can include a basic set of parameters for future synchronization sessions including a default password. If a subscriber forgets the password or otherwise needs to have the voicemail password reset, the subscriber can initiate a password reset by selecting a password reset option on the MD 118. In this example, a new boot message can be sent to the MD 118 including a new default password in response to a password reset request from the MD 118.
  • Referring now to FIG. 2, a flow diagram illustrating a process 200 for voicemail message deposit and subsequent secure retrieval of message content for local storage on a mobile device 118 is illustrated, according to an exemplary embodiment of the present disclosure. It should be understood that the steps of the process 200 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated. The steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims. It should also be understood that the illustrated process 200 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • The process 200 is illustrated as including the VMS 102, the SMSC 122, and the MD 118. In the illustrated process 200, various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, SMPP and HTTPS, although other protocols are contemplated as described above. The process 200 can be modified to include other network elements, such as the CDS 104. In one embodiment, CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102. The CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • The process 200 begins, at step 202, when a message is deposited into a voicemail box established at the VMS 102. At step 204, the VMS 102 can generate a notification short message (notification_sm) and send the notification_sm to the SMSC 122, at step 206. The SMSC 122 can temporarily store and forward the notification_sm message to the MD 118, at step 208.
  • The MD 118 can attach to a data network, for example, by a GPRS attach process and can perform a PDP context activation to connect to the data network via an access point name (APN) provided to the MD 118 by the service provider. The APN can be included in the notification_sm message, in a first boot message, or other communication between the MD 118 and the VMS 102 or other network elements, such as the CDS 104, a serving GPRS support node (SGSN), or a gateway GPRS support node (GGSN), for example. Accordingly, a GPRS attach and PDP context activation process 210 is illustrated. The MD 118 can perform these functions as is known in the art at any time prior to activating a secure handshake process 212. The handshake process 212 can be a handshake process of a cryptographic protocol, such as, but not limited to, SSL or TLS.
  • The illustrated secure handshake process 212 establishes the MD 118 as the client and the VMS 102 as the server, although this is not necessarily the case. As such, references to client refer to the MD 118 and references to server refer to the VMS 102 in the illustrated embodiment and description thereof. The secure handshake process 212 begins when the MD 118 generates and sends a client_hello command to the VMS 102, at step 214. The client_hello command can include the version(s) of SSL or TLS that is supported by the MD 118, the cipher(s) supported by the MD 118 sorted in order of preference, the data compression algorithm(s) that is supported by the MD 118, and a session ID. The client_hello command can also include random data that is generated by the MD 118 for use in a key generation process.
  • At step 216, the VMS 102 receives the client_hello command and, in response, generates and sends a server_hello command to the MD 118. The server_hello command can include the SSL or TLS version that will be used for the secure session, the cipher that will be used for the secure session, the session ID, and, if applicable, the compression algorithm that will be used for the secure session. The server_hello command can also include random data that is generated by the VMS 102 for use in a key generation process.
  • At step 218, the VMS 102 can generate and send a certificate command to the MD 118. The certificate command can include a public key and an authentication signature. In addition, the certificate command can include a chain of certificates beginning with the certificate of the certificate authority that assigned the server's certificate.
  • At step 220, the VMS 102 can generate and send a server_done command to the MD 118 to indicate that the VMS 102 has completed this phase of the secure handshake process 212. If the MD 102 will be authenticated to the VMS 102, additional commands can flow between the MD 118 and the VMS 102. For example, the MD 118 can provide a certificate to authenticate to the VMS 102. This certificate can be sent, for example, in the first boot message, or other communication.
  • At step 222, the MD 118 can verify the server's certificate and can generate and send a certificate_verify command to the VMS 102 to inform the VMS 102 that the MD 118 has verified the certificate. Likewise, the VMS 102 can verify a client certificate, should one be used, and can generate and send a similar certificate_verify command to the MD 118 to inform the MD 118 that the VMS 102 has verified the certificate.
  • At step 224, the MD 118 can generate and send a change_cipher_spec command to convey to the VMS 102 that the contents of subsequent SSL transmissions sent by the MD 118 will be encrypted. At step 226, the MD 118 can generate and send a finished command to the VMS 102. The finished command can include a list of all secure handshake commands exchanged between the MD 118 and the VMS 102 to validate that none of the unencrypted commands sent to establish a secure session were changed.
  • At step 228, the VMS 102 can generate and send a change_cipher_spec command to convey to the MD 118 that the contents of subsequent SSL transmissions sent by the VMS 102 will be encrypted. At step 230, the VMS 102 can then generate and send a finished command. The finished command can include a list of all secure handshake commands exchanged between the VMS 102 and MD 118 to validate that none of the unencrypted commands sent to establish a secure session were changed. A secure session 232 is now established. HTTPS is described as the protocol used to send the various commands between the VMS 102 and the MD 118 in the secure session 232, although other secure protocols are contemplated, as described above.
  • The secure session 232 can begin when the MD 118 generates and sends a get_headers command to the VMS 102, at step 234. The get_headers command can include parameters, such as, but not limited to, the date, time, and calling line identity (CLI). The get_headers message can additionally include authentication information. At step 236, the VMS 102 retrieves the voicemail message headers for the voicemail account associated with the MD 118 and sends the headers to the MD 118. The MD 118 uses the headers to determine the status of each voicemail message stored on the MD 118 and to identify any new voicemail messages in the subscriber's voicemail account. After the MD 118 determines which message(s) needs to be retrieved, if any, the MD 118 can generate and send a get_message command with the header information for at least one requested message, at step 238. At step 240, the VMS 102 receives the get_message command and sends the requested message content to the MD 118. The secure session 232 can end at step 242.
  • The MD 118 can receive the message content and store the content under the appropriate header in a memory and permit a 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • An if-modified-since command can be used to occasionally poll the VMS 102 for an inbox voicemail message list and update any voicemail message if the voicemail was modified since the last update, for example, if a message was deleted or added. This can help 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 available for sending only the modified voicemail message header.
  • More than one connection can be established to the VMS 102 or in some cases to multiple or redundant VMSs. This can allow for simultaneous requests in order to serve a subscriber's request to view or listen to a message faster. Load balancing techniques can also be implemented.
  • Message downloads that are interrupted, via cancellation or connection failure, can be resumed starting at the last received byte, for example. This assumes the message is stored in full, at least temporarily, on the VMS 102. In some instances, however, the VMS 102 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.
  • Requests to the VMS 102 can be pipelined in accordance with HTTP 1.1 specifications. This can help reduce network latency for multiple requests.
  • Referring now to FIG. 3, a flow diagram illustrating a secure process 300 for setting or changing a voicemail greeting is illustrated, according to an exemplary embodiment of the present disclosure. It should be understood that the steps of the process 300 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated. The steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims. It should also be understood that the illustrated process 300 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • The process 300 is illustrated as including the VMS 102, the SMSC 122, and the MD 118. In the illustrated process 300, various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above. The process 300 can be modified to include other network elements, such as the CDS 104. In one embodiment, the CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102. The CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • The illustrated process 300 begins at step 302, wherein the MD 118 records a new voicemail greeting, such as, for example, a voicemail greeting dictated by a subscriber. The subscriber can 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • The MD 118 can establish a secure session using, for example, SSL or TLS, via a secure handshake process 212, as described in FIG. 2. At step 304, the MD 118 can generate and send a change_greeting_request to the VMS 102 via HTTPS, for example. The change_greeting_request can include the recorded greeting in one or more formats. The change_greeting_request can be sent to the VMS 102. The VMS 102 can save the recording as the active or primary voicemail greeting for the subscriber. If a custom voicemail greeting is not set, a default voicemail greeting (e.g., a network default greeting) can be replaced with the new voicemail greeting. At step 306, the success or failure of the save can be reported back to the MD 118 via a change_greeting_response. If the change_greeting_request fails, the VVM application can notify the subscriber to retry, offer customer support, and/or refer the subscriber to a telephone number or website address for further information and troubleshooting.
  • Referring now to FIG. 4, a message flow diagram illustrating a secure process 400 for setting or changing a voicemail password is illustrated, according to an exemplary embodiment of the present disclosure. It should be understood that the steps of the process 400 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated. The steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims. It should also be understood that the illustrated process 400 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • The process 400 is illustrated as including the VMS 102, the SMSC 122, and the MD 118. In the illustrated process 400, various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above. The process 400 can be modified to include other network elements, such as the CDS 104. In one embodiment, the CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102. The CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • If a password has not been set, the default password provided in a notification_sm 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 VMS 102 can send the current password in a notification_sm message. The current password can 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. The password can be set with a minimum and maximum length. The VVM application can be configured to verify that the password complies with this requirement prior to attempting to change the password on the VMS 102. The password can be set with a minimum or maximum amount of numbers and/or characters. The VVM application can be configured to verify that the password complies with this requirement prior to attempting to change the password on the VMS 102. Other requirements can be established. If the subscriber enters a password that fails to comply with any requirement, the VVM application can notify the user to retry with a password that satisfies the requirement(s), offer customer support, and/or refer the customer to a telephone number or website address for further information and troubleshooting.
  • The illustrated process 400 begins when the subscriber is prompted to enter both the old password and the new password. The MD 118 can establish a secure session using, for example, SSL or TLS, via a secure handshake process 212, as described above in FIG. 2, so that any password sent between the MD 118 and the VMS 102 is encrypted.
  • At step 402, the subscriber can enter the old password and new password on the MD 118. After the passwords have been entered, the VVM application can generate a change_password_request. The change_password_request can be sent to the VMS 102 for storage, at step 404. The VMS 102 can perform a password validation and save the new password. At step 406, the VMS 102 can generate and send a change_password_response to report the success or failure of the change_password_request. Error codes can be set for the VMS 102 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.
  • Referring now to FIG. 5, a message flow diagram illustrating a secure process for setting or changing a recorded name is illustrated, according to an exemplary embodiment of the present disclosure. It should be understood that the steps of the process 500 are not necessarily presented in any particular order and that performance of some or all the steps in an alternative order(s) is possible and is contemplated. The steps have been presented in the demonstrated order for ease of description and illustration. Steps can be added, omitted and/or performed simultaneously without departing from the scope of the appended claims. It should also be understood that the illustrated process 500 can be ended at any time. Some or all steps of this process, and/or substantially equivalent steps, can be performed by execution of computer-readable instructions included on a computer readable medium.
  • The process 500 is illustrated as including the VMS 102, the SMSC 122, and the MD 118. In the illustrated process 500, various messages and/or commands are exchanged among these network elements using various protocols, such as, for example, HTTPS, although other protocols are contemplated as described above. The process 500 can be modified to include other network elements, such as the CDS 104. In one embodiment, CDS 104 acts in an intermediary capacity, facilitating communication between the MD 118 and the VMS 102. The CDS 104 can communicate with the VMS 102 via the IMAP protocol, for example.
  • The process 500 can begin when a subscriber records a new name on the MD 118, at step 502. The subscriber can then 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, waveform audio (WAV), audio interchange file format (AIFF), RAW, encoded in GSM CODEC, advanced audio coding (AAC), MPEG-1 audio layer 3 (MP3), MPEG-4 Part 14 (MP4), Windows® media audio (WMA), RealAudio (RA), free lossless audio codec (FLAC), Apple® lossless encoder (ALE), i.e., Apple® lossless audio codec (ALAC), and other open and proprietary audio formats.
  • The MD 118 can establish a secure session using, for example, SSL or TSL, via a secure handshake process 212, as described above in FIG. 2, so that any password sent between the MD 118 and the VMS 102 is encrypted.
  • After a new name has been recorded, the VVM application can generate a change_recorded_name_request containing the recorded name in the selected format, at step 504. The VMS 102 can receive the change_recorded_name_request and save the new recorded name. The VMS 102 can generate a change_recorded_name_response to report the success or failure of the save and send the change_recorded_name_response to the MD 118, at step 506.
  • The VVM application can be configured to switch between the standard greeting without name, the standard greeting with name, and a custom greeting. 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.
  • FIG. 6 is a schematic block diagram illustrating an exemplary mobile device 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. 6, the components can interact with each other to carry out device functions.
  • As illustrated, the mobile device 118 can be a multimode handset. FIG. 6 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.
  • 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.
  • The illustrated device 118 includes a display 600 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 600 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).
  • The device 118 can include a processor 602 for controlling, and/or processing data. A memory 604 can interface with the processor 602 for the storage of data and/or applications 606. The memory 604 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.
  • The memory 604 can be configured to store one or more applications 606. The applications 606 can include a user interface (UI) application 608. The UI application 608 can interface with a client 610 (e.g., an operating system) to facilitate user interaction with device functionality and data, for example, managing voicemails in a visual voicemail application, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multimode interaction, and the like. The applications 606 can include other applications 612 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 606 can be stored in the memory 604 and/or in a firmware 614, and can be executed by the processor 602. The firmware 614 can also store code for execution during initialization of the device 118.
  • A communications component 616 can interface with the processor 602 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 616 can also include a multimode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver 618 can operate in one mode, for example, GSM, and an Nth transceiver 620 can operate in a different mode, for example WiFi. While only two transceivers 618, 620 are illustrated, it should be appreciated that a plurality of transceivers can be included. The communications component 616 can also include a transceiver 622 for unlicensed RF communications using technology such as, for example, WiFi, WiMAX, NFC, other RF and the like. The transceiver 622 can also be configured for line-of-sight technologies, such as, for example, infrared and IRDA. Although a single transceiver 622 is illustrated multiple transceivers for unlicensed RF and line-of-sight technologies are contemplated.
  • The communications component 616 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 616 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.
  • An input/output (I/O) interface 624 can be provided for input/output of data and/or signals. The I/O interface 624 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.
  • Audio capabilities can be provided by an audio I/O component 626 that can include a speaker (not shown) for the output of audio signals and a microphone (not shown) to collect audio signals.
  • The device 118 can include a slot interface 628 for accommodating a subscriber identity system 630, such as, for example, a SIM or universal SIM (USIM). The subscriber identity system 630 instead can be manufactured into the device 118, thereby obviating the need for a slot interface 628.
  • The device 118 can include an image capture and processing system 632. Photos and/or videos can be obtained via an associated image capture subsystem of the image system 632, for example, a camera. The device 118 can also include a video systems component 634 for processing, recording, and/or transmitting video content.
  • A location component 636 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.
  • The device 118 can include a power source 638 such as batteries and/or other power subsystem (AC or DC). The power source 638 can be single-use, continuous, or rechargeable. In the case of the latter, the power source 638 can interface with an external power system or charging equipment via a power I/O component 640.
  • 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.

Claims (20)

What is claimed is:
1. A method comprising:
completing, by a visual voicemail system, establishment of a secure data session with a mobile device, wherein establishment of the secure data session is initiated by the mobile device;
receiving, by the visual voicemail system, during the secure data session, a request from the mobile device to change visual voicemail account information associated with the mobile device; and
attempting, by the visual voicemail system, to change the visual voicemail account information associated with the mobile device in accordance with the request.
2. The method of claim 1, wherein the secure data session established between the visual voicemail system and the mobile device comprises a secure sockets layer data session.
3. The method of claim 1, wherein the secure data session established between the visual voicemail system and the mobile device comprises a transport layer security data session.
4. The method of claim 1 further comprising:
generating, by the visual voicemail system, a response to the request, the response indicating a success or failure of an attempt by the visual voicemail system to change the visual voicemail account information associated with the mobile device in accordance with the request; and
sending the response to the mobile device during the secure data session.
5. The method of claim 1, wherein the request comprises a change voicemail greeting request, and wherein the visual voicemail account information comprises a voicemail greeting spoken by a user of the mobile device and recorded by the mobile device.
6. The method of claim 1, wherein the request comprises a change voicemail password request, and wherein the visual voicemail account information comprises a voicemail password entered by a user of the mobile device and recorded by the mobile device.
7. The method of claim 1, wherein the request comprises a change recorded name request, and wherein the visual voicemail account information comprises a voicemail recorded name spoken by a user of the mobile device and recorded by the mobile device.
8. A visual voicemail system comprising:
a processor; and
a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising
completing establishment of a secure data session with a mobile device, wherein establishment of the secure data session is initiated by the mobile device,
receiving, during the secure data session, a request from the mobile device to change visual voicemail account information associated with the mobile device, and
attempting to change the visual voicemail account information associated with the mobile device in accordance with the request.
9. The visual voicemail system of claim 8, wherein the secure data session established between the visual voicemail system and the mobile device comprises a secure sockets layer data session.
10. The visual voicemail system of claim 8, wherein the secure data session established between the visual voicemail system and the mobile device comprises a transport layer security data session.
11. The visual voicemail system of claim 8, wherein the operations further comprise:
generating a response to the request, the response indicating a success or failure of an attempt by the visual voicemail system to change the visual voicemail account information associated with the mobile device in accordance with the request; and
sending the response to the mobile device during the secure data session.
12. The visual voicemail system of claim 8, wherein the request comprises a change voicemail greeting request, and wherein the visual voicemail account information comprises a voicemail greeting spoken by a user of the mobile device and recorded by the mobile device.
13. The visual voicemail system of claim 8, wherein the request comprises a change voicemail password request, and wherein the visual voicemail account information comprises a voicemail password entered by a user of the mobile device and recorded by the mobile device.
14. The visual voicemail system of claim 8, wherein the request comprises a change recorded name request, and wherein the visual voicemail account information comprises a voicemail recorded name spoken by a user of the mobile device and recorded by the mobile device.
15. A mobile device comprising:
a processor; and
a memory comprising computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising
initiating establishment of a secure data session with a visual voicemail system,
generating a request to change visual voicemail account information associated with the mobile device, and
providing, during the secure data session, the request to the visual voicemail system so that the visual voicemail system can attempt to change the visual voicemail.
16. The mobile device of claim 15, wherein the secure data session comprises a secure sockets layer data session.
17. The mobile device of claim 15, wherein the secure data session comprises a transport layer security data session.
18. The mobile device of claim 15, wherein the request comprises a change voicemail greeting request, and wherein the visual voicemail account information comprises a voicemail greeting spoken by a user of the mobile device and recorded by the mobile device.
19. The mobile device of claim 15, wherein the request comprises a change voicemail password request, and wherein the visual voicemail account information comprises a voicemail password entered by a user of the mobile device and recorded by the mobile device.
20. The mobile device of claim 15, wherein the request comprises a change recorded name request, and wherein the visual voicemail account information comprises a voicemail recorded name spoken by a user of the mobile device and recorded by the mobile device.
US14/450,971 2007-08-31 2014-08-04 Secure Visual Voicemail Abandoned US20160330599A9 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/450,971 US20160330599A9 (en) 2007-08-31 2014-08-04 Secure Visual Voicemail

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US96941907P 2007-08-31 2007-08-31
US12/160,940 US8401526B2 (en) 2007-08-31 2008-04-25 Systems and methods for providing a password reset feature
PCT/US2008/065046 WO2009029313A1 (en) 2007-08-31 2008-05-29 Secure visual voicemail
US14/450,971 US20160330599A9 (en) 2007-08-31 2014-08-04 Secure Visual Voicemail

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2008/065046 Continuation WO2009029313A1 (en) 2007-08-31 2008-05-29 Secure visual voicemail
US12/160,946 Continuation US8798241B2 (en) 2007-08-31 2008-05-29 Secure visual voicemail

Publications (2)

Publication Number Publication Date
US20140342702A1 US20140342702A1 (en) 2014-11-20
US20160330599A9 true US20160330599A9 (en) 2016-11-10

Family

ID=39629000

Family Applications (25)

Application Number Title Priority Date Filing Date
US12/161,076 Active US8306509B2 (en) 2007-08-31 2008-04-24 Enhanced messaging with language translation feature
US12/160,940 Expired - Fee Related US8401526B2 (en) 2007-08-31 2008-04-25 Systems and methods for providing a password reset feature
US12/161,033 Active US8340644B2 (en) 2007-08-31 2008-04-25 Voicemail forwarding functionality for communications networks
US12/160,946 Active 2029-01-06 US8798241B2 (en) 2007-08-31 2008-05-29 Secure visual voicemail
US12/161,027 Active US8406743B2 (en) 2007-08-31 2008-05-29 Systems and methods for consolidating wireline and wireless voicemail boxes
US12/161,035 Active US8509745B2 (en) 2007-08-31 2008-06-16 Voicemail archival and forwarding functionality for communications networks and devices
US12/161,021 Active US8351903B2 (en) 2007-08-31 2008-06-17 Updating voicemail with selective establishment of PDP contexts and data sessions
US12/160,931 Expired - Fee Related US8737580B2 (en) 2007-08-31 2008-06-20 Toggling voicemail class of service
US12/161,064 Active US8478239B2 (en) 2007-08-31 2008-06-20 Video greetings for voicemail systems
US12/201,945 Active 2030-05-01 US8032122B2 (en) 2007-08-31 2008-08-29 Systems and methods for providing enhanced voicemail services
US12/477,971 Active 2029-04-06 US8489074B2 (en) 2007-08-31 2009-06-04 Systems and methods for providing enhanced voicemail services
US12/485,484 Active 2031-09-06 US8548438B2 (en) 2007-08-31 2009-06-16 Systems and methods for providing enhanced voicemail services
US12/485,335 Active 2029-05-02 US8412162B2 (en) 2007-08-31 2009-06-16 Systems and methods for providing enhanced voicemail services
US12/485,961 Active 2031-05-12 US8515395B2 (en) 2007-08-31 2009-06-17 Systems and methods for providing enhanced voicemail services
US13/613,525 Active 2029-01-19 US9210558B2 (en) 2007-08-31 2012-09-13 Updating voicemail with selective establishment of PDP contexts and data sessions
US13/616,198 Active US8442496B2 (en) 2007-08-31 2012-09-14 Enhanced messaging with language translation feature
US13/654,480 Active US8977241B2 (en) 2007-08-31 2012-10-18 Voicemail forwarding functionality for communications networks
US13/751,505 Active US8503988B2 (en) 2007-08-31 2013-01-28 Systems and methods for providing a password reset feature
US13/785,710 Ceased US8688082B2 (en) 2007-08-31 2013-03-05 Systems and methods for consolidating wireline and wireless voicemail boxes
US13/892,882 Active US8923825B2 (en) 2007-08-31 2013-05-13 Enhanced messaging with language translation feature
US13/930,210 Active US8831573B2 (en) 2007-08-31 2013-06-28 Video greetings for voicemail systems
US13/964,650 Active US8843117B2 (en) 2007-08-31 2013-08-12 Voicemail archival and forwarding functionality for communications networks and devices
US14/450,971 Abandoned US20160330599A9 (en) 2007-08-31 2014-08-04 Secure Visual Voicemail
US14/492,908 Abandoned US20150011191A1 (en) 2007-08-31 2014-09-22 Voicemail Archival and Forwarding Functionality for Communications Networks and Devices
US14/534,762 Active USRE46952E1 (en) 2007-08-31 2014-11-06 Systems and methods for consolidating wireline and wireless voicemail boxes

Family Applications Before (22)

Application Number Title Priority Date Filing Date
US12/161,076 Active US8306509B2 (en) 2007-08-31 2008-04-24 Enhanced messaging with language translation feature
US12/160,940 Expired - Fee Related US8401526B2 (en) 2007-08-31 2008-04-25 Systems and methods for providing a password reset feature
US12/161,033 Active US8340644B2 (en) 2007-08-31 2008-04-25 Voicemail forwarding functionality for communications networks
US12/160,946 Active 2029-01-06 US8798241B2 (en) 2007-08-31 2008-05-29 Secure visual voicemail
US12/161,027 Active US8406743B2 (en) 2007-08-31 2008-05-29 Systems and methods for consolidating wireline and wireless voicemail boxes
US12/161,035 Active US8509745B2 (en) 2007-08-31 2008-06-16 Voicemail archival and forwarding functionality for communications networks and devices
US12/161,021 Active US8351903B2 (en) 2007-08-31 2008-06-17 Updating voicemail with selective establishment of PDP contexts and data sessions
US12/160,931 Expired - Fee Related US8737580B2 (en) 2007-08-31 2008-06-20 Toggling voicemail class of service
US12/161,064 Active US8478239B2 (en) 2007-08-31 2008-06-20 Video greetings for voicemail systems
US12/201,945 Active 2030-05-01 US8032122B2 (en) 2007-08-31 2008-08-29 Systems and methods for providing enhanced voicemail services
US12/477,971 Active 2029-04-06 US8489074B2 (en) 2007-08-31 2009-06-04 Systems and methods for providing enhanced voicemail services
US12/485,484 Active 2031-09-06 US8548438B2 (en) 2007-08-31 2009-06-16 Systems and methods for providing enhanced voicemail services
US12/485,335 Active 2029-05-02 US8412162B2 (en) 2007-08-31 2009-06-16 Systems and methods for providing enhanced voicemail services
US12/485,961 Active 2031-05-12 US8515395B2 (en) 2007-08-31 2009-06-17 Systems and methods for providing enhanced voicemail services
US13/613,525 Active 2029-01-19 US9210558B2 (en) 2007-08-31 2012-09-13 Updating voicemail with selective establishment of PDP contexts and data sessions
US13/616,198 Active US8442496B2 (en) 2007-08-31 2012-09-14 Enhanced messaging with language translation feature
US13/654,480 Active US8977241B2 (en) 2007-08-31 2012-10-18 Voicemail forwarding functionality for communications networks
US13/751,505 Active US8503988B2 (en) 2007-08-31 2013-01-28 Systems and methods for providing a password reset feature
US13/785,710 Ceased US8688082B2 (en) 2007-08-31 2013-03-05 Systems and methods for consolidating wireline and wireless voicemail boxes
US13/892,882 Active US8923825B2 (en) 2007-08-31 2013-05-13 Enhanced messaging with language translation feature
US13/930,210 Active US8831573B2 (en) 2007-08-31 2013-06-28 Video greetings for voicemail systems
US13/964,650 Active US8843117B2 (en) 2007-08-31 2013-08-12 Voicemail archival and forwarding functionality for communications networks and devices

Family Applications After (2)

Application Number Title Priority Date Filing Date
US14/492,908 Abandoned US20150011191A1 (en) 2007-08-31 2014-09-22 Voicemail Archival and Forwarding Functionality for Communications Networks and Devices
US14/534,762 Active USRE46952E1 (en) 2007-08-31 2014-11-06 Systems and methods for consolidating wireline and wireless voicemail boxes

Country Status (2)

Country Link
US (25) US8306509B2 (en)
WO (9) WO2009029296A1 (en)

Families Citing this family (198)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8090402B1 (en) * 2003-09-26 2012-01-03 Iwao Fujisaki Communication device
US20070005709A1 (en) * 2004-06-18 2007-01-04 2Speak, Inc. Method and system for providing a voice e-mail messaging service
US7624278B2 (en) * 2004-09-10 2009-11-24 At&T Intellectual Property I, L.P. Resetting access account passwords of a multitude of compartmentalized systems
EP1727024A1 (en) * 2005-05-27 2006-11-29 Sony Ericsson Mobile Communications AB Automatic language selection for text input in messaging context
US8225231B2 (en) 2005-08-30 2012-07-17 Microsoft Corporation Aggregation of PC settings
US7657006B2 (en) 2005-12-15 2010-02-02 At&T Intellectual Property I, L.P. Messaging translation services
US8175227B2 (en) * 2006-06-30 2012-05-08 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for providing message management services
US7860071B2 (en) 2006-08-31 2010-12-28 Skype Limited Dual-mode device for voice communication
US7912448B2 (en) * 2006-08-31 2011-03-22 Skype Limited Wireless device for voice communication
US8077837B1 (en) * 2007-07-03 2011-12-13 At&T Mobility Ii Llc Systems and methods for providing context-based voicemail
US8306509B2 (en) 2007-08-31 2012-11-06 At&T Mobility Ii Llc Enhanced messaging with language translation feature
US9276775B2 (en) * 2007-09-05 2016-03-01 Microsoft Patent Licensing, LLC Identity-based interactive response message
US9088660B2 (en) * 2007-09-14 2015-07-21 Bt Americas Inc. Messaging and application system integration
US8472589B1 (en) * 2007-09-28 2013-06-25 Sprint Communications Company L.P. Locally storing voicemails and communicating them to other wireless mobile devices
US8270577B2 (en) * 2007-12-13 2012-09-18 Verizon Patent And Licensing Inc. Multiple visual voicemail mailboxes
US8145196B2 (en) * 2007-12-18 2012-03-27 Apple Inc. Creation and management of voicemail greetings for mobile communication devices
US20090172103A1 (en) * 2007-12-26 2009-07-02 Nokia Corporation Event based instant messaging notification
US8706092B2 (en) * 2008-01-03 2014-04-22 Apple Inc. Outgoing voice mail recording and playback
US20090187398A1 (en) * 2008-01-18 2009-07-23 Avaya Technology Llc Script Selection Based On SIP Language Preference
JP5381975B2 (en) * 2008-03-04 2014-01-08 日本電気株式会社 Mobile terminal equipped with IC chip, application area control method, and application area control program
GB2459158A (en) * 2008-04-17 2009-10-21 Skype Ltd Initiating a call via an access network wherein access number availability is indicated based on information associated with a device.
US8589541B2 (en) 2009-01-28 2013-11-19 Headwater Partners I Llc Device-assisted services for protecting network capacity
US8832777B2 (en) 2009-03-02 2014-09-09 Headwater Partners I Llc Adapting network policies based on device service processor configuration
CN101610467A (en) * 2008-06-20 2009-12-23 深圳富泰宏精密工业有限公司 The system and method for repayment missed call and unread short messages
US8798238B2 (en) * 2008-06-30 2014-08-05 At&T Mobility Ii Llc Call handling treatment for voicemail systems
US8532637B2 (en) * 2008-07-02 2013-09-10 T-Mobile Usa, Inc. System and method for interactive messaging
US8422645B1 (en) * 2008-07-10 2013-04-16 Spring Communications Company L.P. Voicemail network capacity planning and management
US20100030821A1 (en) * 2008-07-31 2010-02-04 Research In Motion Limited Systems and methods for preserving auditable records of an electronic device
US8504001B2 (en) * 2008-08-12 2013-08-06 Apple Inc. Unified settings for multiple account types
US8934928B2 (en) * 2008-08-21 2015-01-13 Nokia Solutions And Networks Oy Match maker service
US8712384B1 (en) * 2008-08-26 2014-04-29 Sprint Spectrum L.P. Method and system for triggering message waiting indicator delivery
US8458220B2 (en) * 2008-10-02 2013-06-04 International Business Machines Corporation Method, system and computer-usable medium for early notification of a pending digital video recorder deletion event
US9282156B2 (en) * 2008-10-22 2016-03-08 International Business Machines Corporation Architecture and method of call routing based on session initiation protocol presence information
US20100105424A1 (en) * 2008-10-23 2010-04-29 Smuga Michael A Mobile Communications Device User Interface
US8411046B2 (en) 2008-10-23 2013-04-02 Microsoft Corporation Column organization of content
US8385952B2 (en) 2008-10-23 2013-02-26 Microsoft Corporation Mobile communications device user interface
US20100107100A1 (en) 2008-10-23 2010-04-29 Schneekloth Jason S Mobile Device Style Abstraction
US20100111270A1 (en) * 2008-10-31 2010-05-06 Vonage Holdings Corp. Method and apparatus for voicemail management
US9178842B2 (en) 2008-11-05 2015-11-03 Commvault Systems, Inc. Systems and methods for monitoring messaging applications for compliance with a policy
US20100151834A1 (en) * 2008-12-15 2010-06-17 Verizon Corporate Group Services Inc. Methods and systems for optimizing a visual voice mail system by reducing the use of communication resources
US8295814B2 (en) * 2008-12-15 2012-10-23 Microsoft Corporation Message forwarding and retrieval with a single messaging service
US8099134B2 (en) * 2008-12-19 2012-01-17 Verizon Patent And Licensing Inc. Visual manipulation of audio
US9980146B2 (en) 2009-01-28 2018-05-22 Headwater Research Llc Communications device with secure data path processing agents
US9572019B2 (en) 2009-01-28 2017-02-14 Headwater Partners LLC Service selection set published to device agent with on-device service selection
US9706061B2 (en) 2009-01-28 2017-07-11 Headwater Partners I Llc Service design center for device assisted services
US10237757B2 (en) 2009-01-28 2019-03-19 Headwater Research Llc System and method for wireless network offloading
US10798252B2 (en) * 2009-01-28 2020-10-06 Headwater Research Llc System and method for providing user notifications
US9565707B2 (en) 2009-01-28 2017-02-07 Headwater Partners I Llc Wireless end-user device with wireless data attribution to multiple personas
CN101483697A (en) * 2009-02-23 2009-07-15 惠州Tcl移动通信有限公司 Mobile communication terminal and message automatic cleaning method thereof
EP2409479B1 (en) * 2009-03-19 2017-07-12 Nxp B.V. Method for top-up information and computer device
US8355698B2 (en) 2009-03-30 2013-01-15 Microsoft Corporation Unlock screen
US8238876B2 (en) 2009-03-30 2012-08-07 Microsoft Corporation Notifications
US8175653B2 (en) * 2009-03-30 2012-05-08 Microsoft Corporation Chromeless user interface
US8269736B2 (en) 2009-05-22 2012-09-18 Microsoft Corporation Drop target gestures
US8836648B2 (en) 2009-05-27 2014-09-16 Microsoft Corporation Touch pull-in gesture
US9130779B2 (en) * 2009-06-02 2015-09-08 Qualcomm Incorporated Method and apparatus for providing enhanced SMS/EMS/MMS
US8379807B1 (en) * 2009-06-02 2013-02-19 Sprint Communications Company L.P. Providing a customized voicemail-retrieval announcement
US8761379B2 (en) * 2009-06-05 2014-06-24 Radish Systems, Llc System and method for establishing voice and data connection
US8260260B1 (en) * 2009-07-28 2012-09-04 Sprint Communications Company L.P. Visual voicemail client authentication
US8972355B1 (en) * 2009-08-31 2015-03-03 Symantec Corporation Systems and methods for archiving related items
US8443403B2 (en) 2009-09-04 2013-05-14 Time Warner Cable Inc. Methods and apparatus for providing voice mail services
US8433044B2 (en) 2009-09-15 2013-04-30 At&T Intellectual Property I, L.P. Apparatus and method for providing messaging services
US8781079B2 (en) * 2009-10-01 2014-07-15 Verizon Patent And Licensing Inc. Visual voicemail proxy server
US8326333B2 (en) * 2009-11-11 2012-12-04 Sony Ericsson Mobile Communications Ab Electronic device and method of controlling the electronic device
US9363380B2 (en) * 2009-12-10 2016-06-07 At&T Mobility Ii Llc Integrated visual voicemail communications
US8224296B2 (en) * 2009-12-15 2012-07-17 At&T Mobility Ii Llc Visual voicemail detection and management system
EP2520078A1 (en) * 2009-12-31 2012-11-07 Gemalto SA Method for management of a voice mailbox of a mobile phone
US8577341B2 (en) * 2010-01-15 2013-11-05 Qualcomm Connected Experiences, Inc. Methods and apparatus for providing messaging using voicemail
GB201002554D0 (en) * 2010-02-15 2010-03-31 Sony Europ Belgium Nv Customisation of notifications provided by a computer apparatus
US8885801B2 (en) * 2010-02-17 2014-11-11 Genband Us Llc Method and apparatus for providing virtual messaging
US9363633B2 (en) * 2010-02-22 2016-06-07 Nokia Technologies Oy Accurate GNSS time handling in dual/multi-SIM terminals
KR20110103626A (en) * 2010-03-15 2011-09-21 삼성전자주식회사 Apparatus and method for providing tag information of multimedia data in portable terminal
US8412163B2 (en) 2010-04-29 2013-04-02 Microsoft Corporation Local voicemail for mobile devices
CN102972001A (en) * 2010-07-02 2013-03-13 阿尔卡特朗讯公司 Control options during information recording sessions
US8612526B2 (en) * 2010-07-21 2013-12-17 At&T Intellectual Property I, L.P. System and method for prioritizing message transcriptions
US8543652B2 (en) 2010-07-22 2013-09-24 At&T Intellectual Property I, L.P. System and method for efficient unified messaging system support for speech-to-text service
EP2601787A1 (en) * 2010-08-05 2013-06-12 Nortel Networks Limited Web based access to video content associated with voicemail
US8879695B2 (en) 2010-08-06 2014-11-04 At&T Intellectual Property I, L.P. System and method for selective voicemail transcription
US8417224B1 (en) * 2010-09-01 2013-04-09 Cellco Partnership Systems and methods for providing live voicemail to a mobile handset
US9060059B2 (en) 2010-09-10 2015-06-16 Google Inc. Call status sharing
US20120284659A1 (en) * 2010-09-21 2012-11-08 Sony Ericsson Mobile Communications Ab System and method of enhancing messages
US9119041B2 (en) * 2010-11-15 2015-08-25 At&T Intellectual Property I, L.P. Personal media storage and retrieval for visual voice mail
US8738358B2 (en) * 2010-12-24 2014-05-27 Telefonaktiebolaget L M Ericsson (Publ) Messaging translation service application servers and methods for use in message translations
US8676908B2 (en) * 2010-11-25 2014-03-18 Infosys Limited Method and system for seamless interaction and content sharing across multiple networks
US8965982B1 (en) * 2010-11-29 2015-02-24 Cellco Partnership Backup and restoring instant messages
US20120148033A1 (en) * 2010-12-08 2012-06-14 Google Inc. Propagating user status information across computing resources
US20120159395A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Application-launching interface for multiple modes
US20120159383A1 (en) 2010-12-20 2012-06-21 Microsoft Corporation Customization of an immersive environment
US8689123B2 (en) 2010-12-23 2014-04-01 Microsoft Corporation Application reporting in an application-selectable user interface
US8612874B2 (en) 2010-12-23 2013-12-17 Microsoft Corporation Presenting an application change through a tile
US9423951B2 (en) 2010-12-31 2016-08-23 Microsoft Technology Licensing, Llc Content-based snap point
US9383917B2 (en) 2011-03-28 2016-07-05 Microsoft Technology Licensing, Llc Predictive tiling
US9379911B2 (en) * 2011-05-20 2016-06-28 StarLeaf Ltd. Message storage device and a moving image message processor
US8893033B2 (en) 2011-05-27 2014-11-18 Microsoft Corporation Application notifications
US9658766B2 (en) 2011-05-27 2017-05-23 Microsoft Technology Licensing, Llc Edge gesture
US9104307B2 (en) 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
US20120304132A1 (en) 2011-05-27 2012-11-29 Chaitanya Dev Sareen Switching back to a previously-interacted-with application
US9158445B2 (en) 2011-05-27 2015-10-13 Microsoft Technology Licensing, Llc Managing an immersive interface in a multi-application immersive environment
US9104440B2 (en) 2011-05-27 2015-08-11 Microsoft Technology Licensing, Llc Multi-application environment
GB2491889A (en) * 2011-06-17 2012-12-19 Sony Corp Trial period cellular network connection with identity modules of multiple devices loaded with multiple identities from a shared pool
US8687023B2 (en) 2011-08-02 2014-04-01 Microsoft Corporation Cross-slide gesture to select and rearrange
US8825762B2 (en) 2011-08-09 2014-09-02 At&T Intellectual Property I, L.P. Graphical interactive visual response system and method
US9832317B2 (en) * 2011-09-01 2017-11-28 Blackberry Limited Methods and apparatus to obtain voice messages
US20130057587A1 (en) 2011-09-01 2013-03-07 Microsoft Corporation Arranging tiles
US10353566B2 (en) 2011-09-09 2019-07-16 Microsoft Technology Licensing, Llc Semantic zoom animations
US8922575B2 (en) 2011-09-09 2014-12-30 Microsoft Corporation Tile cache
US9557909B2 (en) 2011-09-09 2017-01-31 Microsoft Technology Licensing, Llc Semantic zoom linguistic helpers
US8933952B2 (en) 2011-09-10 2015-01-13 Microsoft Corporation Pre-rendering new content for an application-selectable user interface
US9244802B2 (en) 2011-09-10 2016-01-26 Microsoft Technology Licensing, Llc Resource user interface
US9146670B2 (en) 2011-09-10 2015-09-29 Microsoft Technology Licensing, Llc Progressively indicating new content in an application-selectable user interface
US8924853B2 (en) * 2011-10-07 2014-12-30 Blackberry Limited Apparatus, and associated method, for cognitively translating media to facilitate understanding
US9280377B2 (en) 2013-03-29 2016-03-08 Citrix Systems, Inc. Application with multiple operation modes
US20140032733A1 (en) 2011-10-11 2014-01-30 Citrix Systems, Inc. Policy-Based Application Management
US9137262B2 (en) 2011-10-11 2015-09-15 Citrix Systems, Inc. Providing secure mobile device access to enterprise resources using application tunnels
US9015513B2 (en) * 2011-11-03 2015-04-21 Vocollect, Inc. Receiving application specific individual battery adjusted battery use profile data upon loading of work application for managing remaining power of a mobile device
KR20130071958A (en) * 2011-12-21 2013-07-01 엔에이치엔(주) System and method for providing interpretation or translation of user message by instant messaging application
US9223472B2 (en) 2011-12-22 2015-12-29 Microsoft Technology Licensing, Llc Closing applications
US9128605B2 (en) 2012-02-16 2015-09-08 Microsoft Technology Licensing, Llc Thumbnail-image selection of applications
US8509395B1 (en) 2012-04-17 2013-08-13 At&T Mobility Ii Llc Selecting a message greeting for an unavailable party based upon contextual data associated with a contacting party
FR2991125A1 (en) * 2012-05-24 2013-11-29 France Telecom METHOD FOR SAVING ANONYMAT DURING TELEPHONE COMMUNICATION AND TELECOMMUNICATION SYSTEM FOR IMPLEMENTING THE METHOD
CN104396284B (en) 2012-06-22 2016-09-07 谷歌公司 Present the information for current location or time
CN104641665B (en) * 2012-07-12 2018-09-18 诺基亚技术有限公司 Pass through the device and method of the transmission of the alarm of mobile communication system
US8611865B1 (en) * 2012-07-30 2013-12-17 Blackberry Limited Methods and apparatus to manage voice message system attributes
CN102883323B (en) * 2012-09-27 2018-07-27 中兴通讯股份有限公司 A kind of method and apparatus of protection mobile terminal user's private data
US9060275B2 (en) * 2012-10-09 2015-06-16 Cellco Partnership Interface for synchronizing automated replies between different messaging systems
US9774658B2 (en) 2012-10-12 2017-09-26 Citrix Systems, Inc. Orchestration framework for connected devices
US9053340B2 (en) 2012-10-12 2015-06-09 Citrix Systems, Inc. Enterprise application store for an orchestration framework for connected devices
US20140109176A1 (en) 2012-10-15 2014-04-17 Citrix Systems, Inc. Configuring and providing profiles that manage execution of mobile applications
US8910239B2 (en) 2012-10-15 2014-12-09 Citrix Systems, Inc. Providing virtualized private network tunnels
US9971585B2 (en) 2012-10-16 2018-05-15 Citrix Systems, Inc. Wrapping unmanaged applications on a mobile device
US20140108793A1 (en) 2012-10-16 2014-04-17 Citrix Systems, Inc. Controlling mobile device access to secure data
EP2909715B1 (en) 2012-10-16 2022-12-14 Citrix Systems, Inc. Application wrapping for application management framework
US9606774B2 (en) 2012-10-16 2017-03-28 Citrix Systems, Inc. Wrapping an application with field-programmable business logic
KR20150091406A (en) * 2012-12-06 2015-08-10 사로니코스 트레이딩 앤드 서비스즈, 유니페쏘알 엘디에이 Method and devices for language determination for voice to text transcription of phone calls
GB2511479A (en) * 2012-12-17 2014-09-10 Librae Ltd Interacting toys
ITUD20130035A1 (en) 2013-03-08 2014-09-09 Emmeti Spa METHOD FOR CHECKING THE FUNCTIONING OF A HEATING SYSTEM
US20140270110A1 (en) * 2013-03-15 2014-09-18 Appforest Llc Systems and Methods for Cloud VoiceMail and Two Way Communication
US9985850B2 (en) 2013-03-29 2018-05-29 Citrix Systems, Inc. Providing mobile device management functionalities
US9413736B2 (en) 2013-03-29 2016-08-09 Citrix Systems, Inc. Providing an enterprise application store
US9450952B2 (en) 2013-05-29 2016-09-20 Microsoft Technology Licensing, Llc Live tiles without application-code execution
US9355223B2 (en) 2013-03-29 2016-05-31 Citrix Systems, Inc. Providing a managed browser
US10284627B2 (en) 2013-03-29 2019-05-07 Citrix Systems, Inc. Data management for an application with multiple operation modes
US8849979B1 (en) 2013-03-29 2014-09-30 Citrix Systems, Inc. Providing mobile device management functionalities
US9351203B2 (en) 2013-09-13 2016-05-24 Microsoft Technology Licensing, Llc Voice call continuity in hybrid networks
US20150094041A1 (en) * 2013-09-30 2015-04-02 Elwha LLC, a limited liability company of the State of Delaware Mobile device sharing facilitation methods and systems conditionally provingin metadata in lieu of some user content
US10425365B2 (en) 2013-11-22 2019-09-24 At&T Intellectual Property I, L.P. System and method for relaying messages
US20150154206A1 (en) * 2013-12-03 2015-06-04 Cellco Partnership D/B/A Verizon Wireless Secure management of message archives
US9571994B2 (en) * 2013-12-17 2017-02-14 Matthew Stephen Yagey Alert systems and methodologies
US9510251B2 (en) 2013-12-31 2016-11-29 Microsoft Technology Licensing, Llc Call handoff initiation in hybrid networks
US9805320B2 (en) * 2014-02-27 2017-10-31 Genesys Telecommunications Laboratories, Inc. Tag-based performance framework for contact center
US9560185B2 (en) 2014-03-19 2017-01-31 Microsoft Technology Licensing, Llc Hybrid telecommunications network connection indicator
US10466882B2 (en) 2014-03-31 2019-11-05 Microsoft Technology Licensing, Llc Collaborative co-authoring via an electronic user interface
US10404637B2 (en) 2014-03-31 2019-09-03 Microsoft Technology Licensing, Llc Electronic communication-based storage of documents to support multiple workflows
US20150277724A1 (en) * 2014-03-31 2015-10-01 Microsoft Corporation Inline document collaboration workflow
WO2015153008A2 (en) * 2014-04-02 2015-10-08 Ridge Tool Company Electronic tool lock
EP3126969A4 (en) 2014-04-04 2017-04-12 Microsoft Technology Licensing, LLC Expandable application representation
US9363711B2 (en) 2014-04-07 2016-06-07 Microsoft Technology Licensing, Llc User experiences during call handovers on a hybrid telecommunications network
EP3129846A4 (en) 2014-04-10 2017-05-03 Microsoft Technology Licensing, LLC Collapsible shell cover for computing device
EP3129847A4 (en) 2014-04-10 2017-04-19 Microsoft Technology Licensing, LLC Slider cover for computing device
CN105025449B (en) * 2014-04-24 2018-09-07 中国移动通信集团湖南有限公司 A kind of short message reception state remapping method, apparatus and system
US9456333B2 (en) 2014-07-09 2016-09-27 Microsoft Technology Licensing, Llc Centralized routing in hybrid networks
US10592080B2 (en) 2014-07-31 2020-03-17 Microsoft Technology Licensing, Llc Assisted presentation of application windows
US10254942B2 (en) 2014-07-31 2019-04-09 Microsoft Technology Licensing, Llc Adaptive sizing and positioning of application windows
US10678412B2 (en) 2014-07-31 2020-06-09 Microsoft Technology Licensing, Llc Dynamic joint dividers for application windows
US9503516B2 (en) 2014-08-06 2016-11-22 Google Technology Holdings LLC Context-based contact notification
US10642365B2 (en) 2014-09-09 2020-05-05 Microsoft Technology Licensing, Llc Parametric inertia and APIs
CN106662891B (en) 2014-10-30 2019-10-11 微软技术许可有限责任公司 Multi-configuration input equipment
CN112152909B (en) * 2015-02-16 2022-11-01 钉钉控股(开曼)有限公司 User message reminding method
DE102015110560A1 (en) * 2015-07-01 2017-01-05 Form Orange Produktentwicklung Drawer with a base plate, two side walls, a rear wall and a panel
CN105610695B (en) 2015-12-21 2021-01-12 阿里巴巴集团控股有限公司 Object allocation method and device
CN105681056B (en) 2016-01-13 2019-03-19 阿里巴巴集团控股有限公司 Object distribution method and device
US9497326B1 (en) 2016-03-03 2016-11-15 Interactive Intelligence Group, Inc. System and method for voicemail acceleration
CN105812237B (en) 2016-03-07 2020-12-04 钉钉控股(开曼)有限公司 Method and device for quickly adding reminding object
US9648472B1 (en) * 2016-03-16 2017-05-09 International Business Machines Corporation Voicemail transmission utilizing signals associated with radio band frequencies
US20170302800A1 (en) * 2016-03-16 2017-10-19 Kirk Schultz Multiple voice mail accounts for telephones
KR20170110469A (en) * 2016-03-23 2017-10-11 삼성전자주식회사 A method for providing a video call and an electronic device therefor
CN107305459A (en) 2016-04-25 2017-10-31 阿里巴巴集团控股有限公司 The sending method and device of voice and Multimedia Message
CN107368995A (en) 2016-05-13 2017-11-21 阿里巴巴集团控股有限公司 Task processing method and device
CN107846345A (en) 2016-09-18 2018-03-27 阿里巴巴集团控股有限公司 The means of communication and device
US20180123986A1 (en) 2016-11-01 2018-05-03 Microsoft Technology Licensing, Llc Notification of a Communication Session in a Different User Experience
CN106921560B (en) * 2017-02-28 2020-06-02 北京小米移动软件有限公司 Voice communication method, device and system
USD795912S1 (en) 2017-03-29 2017-08-29 Sorenson Ip Holdings, Llc Display screen or a portion thereof with animated graphical user interface
USD803852S1 (en) 2017-03-29 2017-11-28 Sorenson Ip Holdings, Llc Display screen or a portion thereof with animated graphical user interface
US10089305B1 (en) 2017-07-12 2018-10-02 Global Tel*Link Corporation Bidirectional call translation in controlled environment
US10176366B1 (en) 2017-11-01 2019-01-08 Sorenson Ip Holdings Llc Video relay service, communication system, and related methods for performing artificial intelligence sign language translation services in a video relay service environment
US10225621B1 (en) 2017-12-20 2019-03-05 Dish Network L.L.C. Eyes free entertainment
US10162956B1 (en) 2018-07-23 2018-12-25 Capital One Services, Llc System and apparatus for secure password recovery and identity verification
US20200153965A1 (en) 2018-11-10 2020-05-14 Nuance Communications, Inc. Caller deflection and response system and method
EP3674935A1 (en) * 2018-12-27 2020-07-01 Atos International Germany GmbH System for providing it services support to end-users/customers
US10958790B2 (en) * 2019-05-11 2021-03-23 Alajuwon Omar Norman Video voicemail greeting system
EP3847564A1 (en) * 2019-07-23 2021-07-14 Peakup Teknoloji Anonim Sirketi A security system for a computer network
US11095775B1 (en) * 2019-08-06 2021-08-17 Noble Systems Corporation Handling an outbound call reaching a voicemail service
US11170784B2 (en) 2020-03-03 2021-11-09 Capital One Services, Llc Systems and methods for party authentication and information control in a video call with a server controlling the authentication and flow of information between parties whose identities are not revealed to each other
US11522993B2 (en) * 2020-04-17 2022-12-06 Marchex, Inc. Systems and methods for rapid analysis of call audio data using a stream-processing platform
EP4176372A1 (en) * 2020-07-02 2023-05-10 Cabo Applications LLC Multilingual conversation tool
US11350285B2 (en) 2020-09-15 2022-05-31 T-Mobile Usa, Inc. Visual voicemail as service for authentication or account recovery of wireless devices in a wireless network
US11546773B2 (en) 2020-09-15 2023-01-03 T-Mobile Usa, Inc. Visual voicemail centralized authentication system for wireless networks
US11539838B2 (en) 2021-04-28 2022-12-27 Zoom Video Communications, Inc. Video voicemail recording system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5915008A (en) * 1995-10-04 1999-06-22 Bell Atlantic Network Services, Inc. System and method for changing advanced intelligent network services from customer premises equipment
US20070192134A1 (en) * 2005-12-15 2007-08-16 Benjamin Littenberg Clinical decision support system
WO2008005924A2 (en) * 2006-06-30 2008-01-10 Benjamin Perlman Temporary voicemail greeting for cellular phones: instant away messaging
US8155627B2 (en) * 2007-12-13 2012-04-10 Verizon Patent And Licensing Inc. Visual voicemail provisioning and notification

Family Cites Families (145)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US522727A (en) * 1894-07-10 Electric lamplighter
US5224137A (en) * 1991-05-23 1993-06-29 Imatron, Inc. Tuning the scanning electron beam computed tomography scanner
US5737395A (en) * 1991-10-28 1998-04-07 Centigram Communications Corporation System and method for integrating voice, facsimile and electronic mail data through a personal computer
US5329579A (en) * 1992-07-27 1994-07-12 At&T Bell Laboratories Modular adjunct processor made of identical multi-function modules adaptable under direction of one of them to perform any of the adjunct-processor functions
FR2707069B1 (en) 1993-06-23 1995-09-15 Cofira Sa
US5524137A (en) * 1993-10-04 1996-06-04 At&T Corp. Multi-media messaging system
US6108559A (en) * 1993-10-26 2000-08-22 Telefonaktiebolaget Lm Ericsson System and method for routing messages in radiocommunication systems
WO1995015046A1 (en) * 1993-11-26 1995-06-01 Octel Communications Corporation Exchange of information between interconnected voicemail systems
CA2171041A1 (en) 1995-03-08 1996-09-09 Scott A. Jones System for archiving voice mail messages
US5737394A (en) * 1996-02-06 1998-04-07 Sony Corporation Portable telephone apparatus having a plurality of selectable functions activated by the use of dedicated and/or soft keys
US5809111A (en) * 1996-04-01 1998-09-15 Matthews Communications Management, Inc. Telephone control module and user site network and methods of operation
US5940478A (en) 1996-05-31 1999-08-17 Octel Communications Corporation Method and system for extended addressing plans
SE506976C2 (en) * 1996-07-12 1998-03-09 Europolitan Ab Allow a subscriber to edit personal settings regarding telecommunications services
US6005870A (en) * 1996-08-12 1999-12-21 At&T Corp. Method for called party control of telecommunications network services
US6006087A (en) * 1997-04-10 1999-12-21 At&T Wireless Services, Inc. Method and system for delivering a voice mail notification to a subscriber using cellular phone network
US6097791A (en) * 1997-07-15 2000-08-01 Octel Communications Corporation Voice-messaging system with non-user outcalling and auto-provisioning capabilities
US7088801B1 (en) * 1997-09-08 2006-08-08 Mci, Inc. Single telephone number access to multiple communications services
US6148212A (en) 1997-12-18 2000-11-14 Ericsson Inc. System and method for cellular control of automobile electrical systems
DE19803362A1 (en) * 1998-01-29 1999-08-05 Sartorius Gmbh Foamed porous membranes made of thermoplastic polymers and method and device for their production
US6335962B1 (en) * 1998-03-27 2002-01-01 Lucent Technologies Inc. Apparatus and method for grouping and prioritizing voice messages for convenient playback
US6092114A (en) * 1998-04-17 2000-07-18 Siemens Information And Communication Networks, Inc. Method and system for determining the location for performing file-format conversions of electronics message attachments
US6292799B1 (en) * 1998-06-05 2001-09-18 Netnumber.Com, Inc. Method and apparatus to automatically address a voice mail reply to a voice mail message
WO2000016209A1 (en) * 1998-09-15 2000-03-23 Local2Me.Com, Inc. Dynamic matchingtm of users for group communication
CN1339213A (en) * 1999-02-04 2002-03-06 爱培恩通信有限公司 Telecommunications gateway
US6981023B1 (en) * 1999-03-09 2005-12-27 Michael Hamilton Message routing
US6351523B1 (en) * 1999-03-22 2002-02-26 Sharp Laboratories Of America, Inc. Method and apparatus for management of EMail originated by thin client devices
US6360272B1 (en) * 1999-05-28 2002-03-19 Palm, Inc. Method and apparatus for maintaining a unified view of multiple mailboxes
WO2000073947A1 (en) * 1999-05-31 2000-12-07 Telefonaktiebolaget Lm Ericsson System and method for distributing information to subscribers and arrangement for reminder information distribution
KR100670006B1 (en) 1999-06-08 2007-01-18 더 트러스티스 오브 콜롬비아 유니버시티 인 더 시티 오브 뉴욕 Network telephony appliance and system for inter/intranet telephony
US6829334B1 (en) * 1999-09-13 2004-12-07 Microstrategy, Incorporated System and method for the creation and automatic deployment of personalized, dynamic and interactive voice services, with telephone-based service utilization and control
US6246871B1 (en) * 1999-09-24 2001-06-12 Nokia Networks Oy Method and apparatus for providing access of messages to multiple recipients in cellular networks
US20020112007A1 (en) * 1999-11-03 2002-08-15 Christopher (Noah) Wood Personal message management system
CA2326230C (en) 1999-12-30 2008-04-29 At&T Corp. Integrated multimedia messaging service
US6780885B1 (en) * 2000-01-14 2004-08-24 Idexx Laboratories, Inc. Formulations and methods for administration of pharmacologically or biologically active compounds
WO2001069564A2 (en) * 2000-03-13 2001-09-20 Pittway Corporation Integrated security and communications system with secure communications link
US6615036B1 (en) * 2000-04-04 2003-09-02 Motorola, Inc. Method and apparatus for storing data within a communication system
US20020012007A1 (en) * 2000-05-05 2002-01-31 Twigg John M. Internet based design/drafting system and method of use thereof
US7463619B1 (en) 2000-05-25 2008-12-09 Nortel Networks Limited Launching a web browser in response to a message relating to communications sessions
US6853715B2 (en) * 2000-07-05 2005-02-08 Texas Instruments Incorporated Provisioning of subscriber services
US7369648B1 (en) * 2000-07-06 2008-05-06 Purplecomm, Inc. Apparatus and method for PBX-integrated unified messaging services on a switched backbone
US7095828B1 (en) * 2000-08-11 2006-08-22 Unisys Corporation Distributed network applications platform architecture
DE10041005C1 (en) * 2000-08-22 2001-09-13 Draeger Medizintech Gmbh Method for altering concentration in an anesthesia equipment involves advancing the piston of the volume displacement unit in such a way that a predetermined, adjustable pressure is not exceeded
US6603837B1 (en) * 2000-09-11 2003-08-05 Kinera, Inc. Method and system to provide a global integrated messaging services distributed network with personalized international roaming
US20020077098A1 (en) * 2000-12-19 2002-06-20 Tiliks Dianna I. Method and system for dual ringing of a centrex line and a wireless extension of the centrex line
CA2368404C (en) * 2001-01-18 2005-08-09 Research In Motion Limited Unified messaging system and method
WO2002065745A1 (en) 2001-02-15 2002-08-22 Sivashunmugam Columbus Context association for multimedia using mark-up intelligence
US7136461B1 (en) * 2001-02-16 2006-11-14 Telesector Resources Group, Inc. Method and apparatus for implementing voice messaging using E-mail
US20020115429A1 (en) * 2001-02-16 2002-08-22 Deluca Michael J. Wireless voicemail forwarding of a truncated call
US6879847B1 (en) * 2001-04-09 2005-04-12 Mitsubishi Electric Corporation Systems and methods for displaying a message on a mobile communication device
US6751298B2 (en) * 2001-06-29 2004-06-15 International Business Machines Corporation Localized voice mail system
US6912275B1 (en) * 2001-07-05 2005-06-28 At&T Corp Secure remote access to voice mail
US20030091169A1 (en) * 2001-11-13 2003-05-15 Cain James B. System and method for providing telecommunications services
US20030099341A1 (en) * 2001-11-28 2003-05-29 Bell Canada Method and system for providing access to a voice mail system
US20030217096A1 (en) * 2001-12-14 2003-11-20 Mckelvie Samuel J. Agent based application using data synchronization
US6937868B2 (en) * 2002-01-16 2005-08-30 International Business Machines Corporation Apparatus and method for managing a mobile phone answering mode and outgoing message based on a location of the mobile phone
US20040252679A1 (en) * 2002-02-26 2004-12-16 Tim Williams Stored voice message control extensions
US6813489B1 (en) * 2002-03-01 2004-11-02 Yahoo! Inc. System and method for mobile electronic messaging
US7330538B2 (en) * 2002-03-28 2008-02-12 Gotvoice, Inc. Closed-loop command and response system for automatic communications between interacting computer systems over an audio communications channel
US7359491B2 (en) * 2002-03-29 2008-04-15 At&T Delaware Intellectual Property, Inc. Saving information from information retrieval systems
US20030220784A1 (en) 2002-05-24 2003-11-27 International Business Machines Corporation System and method for automated voice message transcription and delivery
CA2431387C (en) * 2002-06-10 2007-05-29 Research In Motion Limited Voicemail notification messaging for mobile communication devices
EP1599022B1 (en) 2002-06-10 2007-09-12 Research in Motion Voicemail user interface methods and apparatus for mobile communication devices
JP2004056563A (en) * 2002-07-22 2004-02-19 Matsushita Electric Ind Co Ltd Portable telephone set
US6868143B1 (en) * 2002-10-01 2005-03-15 Bellsouth Intellectual Property System and method for advanced unified messaging
US20040081088A1 (en) * 2002-10-25 2004-04-29 Schinner Charles Edward Data transfer time arbitration
US7796977B2 (en) * 2002-11-18 2010-09-14 Research In Motion Limited Voice mailbox configuration methods and apparatus for mobile communication devices
WO2004046895A2 (en) * 2002-11-20 2004-06-03 Corybant, Inc. Interactive voice enabled email notification and alert system and method
US7058392B1 (en) * 2002-12-03 2006-06-06 At&T Corp. Systems, methods and devices for reliable asynchronous message transmissions
GB0230197D0 (en) 2002-12-24 2003-02-05 Avaya Uk Messaging system
EP1582066A4 (en) * 2002-12-27 2006-09-20 Logicacmg Wireless Networks In Systems and methods for providing interactive video response to wireless terminals
US7085554B2 (en) * 2003-01-24 2006-08-01 Common Voices Llc Subscriber migration system
US8175622B2 (en) * 2003-02-14 2012-05-08 Roamware, Inc. Method and system for keeping all phone numbers active while roaming with diverse operator subscriber identity modules
JP4323827B2 (en) * 2003-02-14 2009-09-02 キヤノン株式会社 Solid-state imaging device and radiation imaging device
US7248857B1 (en) * 2004-02-27 2007-07-24 Cingular Wireless Ii, Llc System and method for enhanced message notification
US7277529B1 (en) * 2003-02-27 2007-10-02 Cingular Wireless Ii, Llc System and method for voice mail service in an environment having multiple voice mail technology platforms
JP4170808B2 (en) * 2003-03-31 2008-10-22 株式会社東芝 Information display device, information display method, and program
US7680491B2 (en) * 2003-05-15 2010-03-16 Redknee Inc. Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices (‘Multi-SIM’)
CN100519380C (en) * 2003-05-20 2009-07-29 尼司卡股份有限公司 Sheet stacking apparatus and image forming apparatus equipped with the same
US20040248594A1 (en) * 2003-06-09 2004-12-09 Wren Paul I. Combined multimedia cordless phone and messaging system
KR100565273B1 (en) 2003-06-27 2006-03-30 엘지전자 주식회사 Method for receiving e-mail of mobile communication terminal
US7263176B2 (en) * 2003-06-30 2007-08-28 Bellsouth Intellectual Property Corporation Diagnostic checking of an inter-messaging network
US8638910B2 (en) * 2003-07-14 2014-01-28 Cisco Technology, Inc. Integration of enterprise voicemail in mobile systems
US7142648B1 (en) * 2003-07-23 2006-11-28 Sprint Communications Company L.P. System for securing messages recorded in an IP telephony network
AU2003260819A1 (en) * 2003-09-12 2005-04-06 Nokia Corporation Method and device for handling missed calls in a mobile communications environment
US20050089149A1 (en) * 2003-10-27 2005-04-28 Comverse Ltd. Selectable voicemail greetings
US20050102368A1 (en) * 2003-11-12 2005-05-12 Forman George H. Email attribute system using external databases
US7092701B2 (en) * 2003-11-26 2006-08-15 Sony Ericsson Mobile Communications, Ab Methods, networks, and computer program products for selectively routing communications based on routing rules
US20050186944A1 (en) * 2004-02-25 2005-08-25 Lucent Technologies Inc. System and method for voicemail retrieval notification
US7881444B2 (en) 2004-05-26 2011-02-01 Qualcomm Incorporated Apparatus, system, and method for providing voicemail service using presence status in packet data messaging system
WO2006001593A1 (en) * 2004-06-29 2006-01-05 Ti Square Technology Ltd. Method and apparatus for sending voice message in mobile network
US7826831B2 (en) 2004-06-30 2010-11-02 Bettis Sonny R Video based interfaces for video message systems and services
US7738833B2 (en) 2004-06-30 2010-06-15 Glenayre Electronics, Inc. Provision of messaging services from a video messaging system for video compatible and non-video compatible equipment
US7631042B2 (en) * 2004-06-30 2009-12-08 International Business Machines Corporation Method to update status on multiple voice and text systems from a single device
US8060135B2 (en) * 2004-07-29 2011-11-15 Sprint Spectrum L.P. Method and system for selective application of cellular-PBX integration service
US7260384B2 (en) * 2004-07-29 2007-08-21 Sprint Spectrum L.P. Method and system for dynamic selection of voice mail system
US7702669B2 (en) * 2004-09-02 2010-04-20 Ringcentral, Inc. Synchronization in unified messaging systems
US7624278B2 (en) * 2004-09-10 2009-11-24 At&T Intellectual Property I, L.P. Resetting access account passwords of a multitude of compartmentalized systems
GB0421771D0 (en) * 2004-09-30 2004-11-03 Avaya Uk Messaging system
US7321655B2 (en) * 2005-02-07 2008-01-22 Adomo, Inc. Caching user information in an integrated communication system
WO2006101428A1 (en) * 2005-03-24 2006-09-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement in a communication system for delivering messages to a recipient
US20060239419A1 (en) * 2005-04-20 2006-10-26 Siemens Communications, Inc. Selective and dynamic voicemail
US7680260B2 (en) * 2005-05-03 2010-03-16 Avaya Inc. Detecting a voice mail system answering a call
US20060253584A1 (en) * 2005-05-03 2006-11-09 Dixon Christopher J Reputation of an entity associated with a content item
US20060281443A1 (en) * 2005-05-18 2006-12-14 Michael Chen Method and system for facilitating voice mailbox operations for a mobile phone that is capable of operating in both a CDMA and GSM environment
US8396456B2 (en) * 2005-06-28 2013-03-12 Avaya Integrated Cabinet Solutions Inc. Visual voicemail management
US7860805B2 (en) * 2005-08-15 2010-12-28 Personal Estate Manager, Inc. Computer-implemented personal information manager method and system
US20100166161A1 (en) * 2005-09-01 2010-07-01 Vishal Dhawan System and methods for providing voice messaging services
US8103253B2 (en) * 2005-09-22 2012-01-24 Cisco Technology, Inc. System and method for transmitting messages to a wireless communication device
US7894580B2 (en) * 2005-10-26 2011-02-22 Research In Motion Limited Methods and apparatus for reliable voicemail message deletion alerts at mobile communication devices
KR100810253B1 (en) * 2005-11-14 2008-03-06 삼성전자주식회사 Method and system for providing service menu in a communication system
US7657006B2 (en) * 2005-12-15 2010-02-02 At&T Intellectual Property I, L.P. Messaging translation services
US7226831B1 (en) * 2005-12-27 2007-06-05 Intel Corporation Device with scavenging spacer layer
CN101356796A (en) * 2006-01-06 2009-01-28 奥拉蒂夫公司 Integration of enterprise voicemail in mobile systems
US20070180032A1 (en) * 2006-01-27 2007-08-02 Sbc Knowledge Ventures Lp Method for email service in a visual voicemail system
ATE510396T1 (en) * 2006-02-01 2011-06-15 Research In Motion Ltd SYSTEM AND METHOD FOR VALIDATION OF A USER ACCOUNT USING A WIRELESS DEVICE
WO2007096866A2 (en) 2006-02-21 2007-08-30 Vimplicity Ltd. Conversion of a phone call into a smart pushed voice message
GB0604573D0 (en) * 2006-03-07 2006-04-19 Ghost Telecom Ltd Method and apparatus of interfacing and connecting a wireless devices(s) and a wireless network for in-and out-going SMS, voice-and data-call(s) routing
US20070223666A1 (en) * 2006-03-27 2007-09-27 Les Teague Electronic equipment and service providing personalized call features
US20070239833A1 (en) * 2006-04-06 2007-10-11 Qwest Communications International Inc. Device specific communication notifications
US8320535B2 (en) 2006-04-06 2012-11-27 Qwest Communications International Inc. Selectable greeting messages
CN101090361A (en) * 2006-06-12 2007-12-19 朗迅科技公司 Method for sending customizated multimedia greeting to calling party in communication network
US20080140767A1 (en) * 2006-06-14 2008-06-12 Prasad Rao Divitas description protocol and methods therefor
US8549089B2 (en) * 2006-06-28 2013-10-01 T-Jat Systems 2006 Ltd. Method for sending messages to a mobile telephone
EP1880594A1 (en) * 2006-07-21 2008-01-23 ITW Australia Pty Ltd. Hand Tools
US7961212B2 (en) * 2006-08-14 2011-06-14 Verizon Data Services Llc Video messaging system
US8402499B2 (en) * 2006-08-31 2013-03-19 Accenture Global Services Gmbh Voicemail interface system and method
WO2008034555A1 (en) 2006-09-22 2008-03-27 Koninklijke Kpn N.V. Voice mail platform and method of changing the voice mail settings of such a voice mail platform
US20080081609A1 (en) * 2006-09-29 2008-04-03 Motorola, Inc. Method and system for associating a user profile to a sim card
US20080167007A1 (en) * 2007-01-07 2008-07-10 Gregory Novick Voicemail Systems and Methods
US20080167010A1 (en) 2007-01-07 2008-07-10 Gregory Novick Voicemail Systems and Methods
US20080167014A1 (en) * 2007-01-07 2008-07-10 Gregory Novick Voicemail systems and methods
US8553856B2 (en) 2007-01-07 2013-10-08 Apple Inc. Voicemail systems and methods
US8644463B2 (en) * 2007-01-10 2014-02-04 Tvg, Llc System and method for delivery of voicemails to handheld devices
US20080188204A1 (en) * 2007-02-07 2008-08-07 Anders Gavner System and method for processing a voicemail message
US7995720B2 (en) * 2007-02-16 2011-08-09 At&T Intellectual Property I, L.P. Methods, systems, and products for notifications
US9294609B2 (en) 2007-02-27 2016-03-22 Sony Corporation Events on multiple phones
US8023931B2 (en) 2007-02-27 2011-09-20 Sony Ericsson Mobile Communications Ab Call rerouting
US8874445B2 (en) 2007-03-30 2014-10-28 Verizon Patent And Licensing Inc. Apparatus and method for controlling output format of information
US20080260118A1 (en) * 2007-04-20 2008-10-23 International Business Machines Corporation Product, method and system for enhanced voicemail management
US20080300873A1 (en) 2007-05-30 2008-12-04 James Siminoff Systems And Methods For Securely Transcribing Voicemail Messages
WO2008144930A1 (en) 2007-06-01 2008-12-04 Research In Motion Limited Interactive compression with multiple units of compression state information
DE102007028640A1 (en) * 2007-06-21 2008-12-24 Siemens Enterprise Communications Gmbh & Co. Kg Method, terminal and voice memory for storing voice messages in a communication network
US8306509B2 (en) 2007-08-31 2012-11-06 At&T Mobility Ii Llc Enhanced messaging with language translation feature
US8798238B2 (en) * 2008-06-30 2014-08-05 At&T Mobility Ii Llc Call handling treatment for voicemail systems
US7795977B2 (en) * 2008-07-01 2010-09-14 Teledyne Scientific & Imaging, Llc Bootstrapped class AB CMOS output stage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5915008A (en) * 1995-10-04 1999-06-22 Bell Atlantic Network Services, Inc. System and method for changing advanced intelligent network services from customer premises equipment
US20070192134A1 (en) * 2005-12-15 2007-08-16 Benjamin Littenberg Clinical decision support system
WO2008005924A2 (en) * 2006-06-30 2008-01-10 Benjamin Perlman Temporary voicemail greeting for cellular phones: instant away messaging
US8155627B2 (en) * 2007-12-13 2012-04-10 Verizon Patent And Licensing Inc. Visual voicemail provisioning and notification

Also Published As

Publication number Publication date
US8923825B2 (en) 2014-12-30
US20130137397A1 (en) 2013-05-30
US20100159886A1 (en) 2010-06-24
WO2009029328A8 (en) 2010-04-08
US9210558B2 (en) 2015-12-08
US8032122B2 (en) 2011-10-04
US20130012173A1 (en) 2013-01-10
US20090061828A1 (en) 2009-03-05
US20140342702A1 (en) 2014-11-20
US8503988B2 (en) 2013-08-06
US20090253407A1 (en) 2009-10-08
US8831573B2 (en) 2014-09-09
US8412162B2 (en) 2013-04-02
US8688082B2 (en) 2014-04-01
US8306509B2 (en) 2012-11-06
US8442496B2 (en) 2013-05-14
WO2009029313A1 (en) 2009-03-05
US8515395B2 (en) 2013-08-20
US20100189229A1 (en) 2010-07-29
US8406743B2 (en) 2013-03-26
US20100195807A1 (en) 2010-08-05
US20130252589A1 (en) 2013-09-26
WO2009029296A1 (en) 2009-03-05
US20100159889A1 (en) 2010-06-24
WO2009029298A1 (en) 2009-03-05
US8489074B2 (en) 2013-07-16
US20150011191A1 (en) 2015-01-08
WO2009029323A1 (en) 2009-03-05
US20100159890A1 (en) 2010-06-24
WO2009029324A1 (en) 2009-03-05
US8509745B2 (en) 2013-08-13
US20130010937A1 (en) 2013-01-10
US20100222024A1 (en) 2010-09-02
WO2009029314A1 (en) 2009-03-05
USRE46952E1 (en) 2018-07-10
US8798241B2 (en) 2014-08-05
US20130040614A1 (en) 2013-02-14
US20090239507A1 (en) 2009-09-24
WO2009029328A1 (en) 2009-03-05
WO2009029297A1 (en) 2009-03-05
US8737580B2 (en) 2014-05-27
WO2009029330A1 (en) 2009-03-05
US20130183941A1 (en) 2013-07-18
US20090253412A1 (en) 2009-10-08
US20100167699A1 (en) 2010-07-01
US20130331068A1 (en) 2013-12-12
US8843117B2 (en) 2014-09-23
US8340644B2 (en) 2012-12-25
US8977241B2 (en) 2015-03-10
US20100159891A1 (en) 2010-06-24
US8351903B2 (en) 2013-01-08
US20100159888A1 (en) 2010-06-24
US20130287184A1 (en) 2013-10-31
US8401526B2 (en) 2013-03-19
US8478239B2 (en) 2013-07-02
US20090253413A1 (en) 2009-10-08
US8548438B2 (en) 2013-10-01

Similar Documents

Publication Publication Date Title
US8798241B2 (en) Secure visual voicemail

Legal Events

Date Code Title Description
AS Assignment

Owner name: AT&T MOBILITY II LLC, GEORGIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SIGMUND, WILLIAM JOSEPH;ZUBAS, MICHAEL ROBERT;RAINER, BRIAN KEITH;REEL/FRAME:033458/0357

Effective date: 20080711

AS Assignment

Owner name: NUANCE COMMUNICATIONS, INC., MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T MOBILITY II LLC;REEL/FRAME:041494/0590

Effective date: 20161214

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE