Methods and apparatus to send voice messages

CROSS REFERENCE TO RELATED APPLICATIONS

0001This application is a continuation-in-part of U.S. patent application Ser. No. 13/207,193, filed Aug. 10, 2011, the contents of which is expressly incorporated herein by reference.

FIELD OF THE DISCLOSURE

0002The present disclosure relates generally to communications and, more particularly, to methods and apparatus to send voice messages.

BACKGROUND

0003Voicemail messages are typically left for a call recipient when the recipient does not answer his or her telephone. In such situations, voicemail messages are left by a caller more or less in real time with placing a call to the call recipient. Sometime later, the call recipient may contact a voicemail server to retrieve voicemail messages.

BRIEF DESCRIPTION OF THE DRAWINGS

0004<figref idref="DRAWINGS">FIG. 1</figref> depicts an example system for sending voice messages between mobile devices.

0005<figref idref="DRAWINGS">FIG. 2</figref> depicts an example flow diagram representative of a process, which may be implemented using computer readable instructions on a mobile device that may be used to record and send voice messages in accordance with the system of <figref idref="DRAWINGS">FIG. 1</figref>.

0006<figref idref="DRAWINGS">FIGS. 2A and 2B</figref> depict example flow diagrams representative of example processes to specify service as shown in <figref idref="DRAWINGS">FIG. 2</figref>.

0007<figref idref="DRAWINGS">FIG. 3</figref> depicts an example flow diagram representative of a process, which may be implemented using computer readable instructions on a server that may be used to send voice messages in accordance with the system of <figref idref="DRAWINGS">FIG. 1</figref>.

0008<figref idref="DRAWINGS">FIG. 4</figref> depicts an example flow diagram representative of an alternate process, which may be implemented using computer readable instructions on a mobile device that may be used to record and send voice messages in accordance with the system of <figref idref="DRAWINGS">FIG. 1</figref>.

0009<figref idref="DRAWINGS">FIG. 5</figref> depicts an example flow diagram representative of an alternate process, which may be implemented using computer readable instructions on a server that may be used to send voice messages in accordance with the system of <figref idref="DRAWINGS">FIG. 1</figref>.

0010<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of a mobile device in accordance with the disclosure.

DETAILED DESCRIPTION

0011Although the following discloses example methods, apparatus, and articles of manufacture including, among other components, software executed on hardware, it should be noted that such methods, apparatus, and articles of manufacture are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be embodied exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Accordingly, while the following describes example methods, apparatus, and articles of manufacture, persons having ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such methods, apparatus, and articles of manufacture.

0012For simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of examples disclosed herein. However, it will be understood by those of ordinary skill in the art that examples disclosed herein may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure examples disclosed herein. Also, the description is not to be considered as limiting the scope of examples disclosed herein.

0013Example methods, apparatus, and articles of manufacture disclosed herein may be used in connection with telephony-capable mobile devices, which may be any mobile communication device, mobile computing device, or any other element, entity, device, or service capable of communicating wirelessly. Mobile devices, also referred to as terminals, wireless terminals, mobile stations, communication stations, user equipment (UE), or user devices, may include mobile smart phones (e.g., BlackBerry® smart phones), cellular telephones, wireless personal digital assistants (PDA), tablet/laptop/notebook/netbook computers with wireless adapters, etc.

0014Example methods, apparatus, and articles of manufacture disclosed herein facilitate operations in a mobile device and/or an associated server. Once example method includes receiving a selection of a service from a plurality of services; determining whether the selected service supports sending a voice message; recording the voice message using a mobile communication device; sending the voice message from the mobile communication device using the selected service if the selected service supports sending the voice message.

0015In one example, determining whether the selected service supports sending the voice message comprises obtaining supported functions of the selected service. The plurality of services may include a plurality of voicemail servers. In one example, determining whether the selected service supports sending the voice message comprises querying at least one of the plurality of voicemail servers. According to an example, when the selected service is a first service, the method may further include receiving a selection of a second service from the plurality of services when the first service does not support sending the voice message. The method may also include obtaining a list of the plurality of services, wherein each of the plurality of services supports sending the voice message. A default service may be presented to be used to send the voice message. In some examples, determining whether the selected service supports sending the voice message is carried out prior to receiving the selection of the service. The method may also include determining whether the selected service supports sending the voice message is carried out after receiving the selection of the service.

0016As described herein, a mobile device may include a housing; a display carried by the housing; a wireless receiver and transmitter carried by the housing; a processor carried by the housing, coupled to the wireless receiver and transmitter, and coupled to the display, the processor configured to receive a selection of a service from a plurality of services; determine whether the selected service supports sending a voice message; record the voice message using a mobile communication device; send the voice message from the mobile communication device using the selected service if the selected service supports sending the voice message.

0017In one example, determining whether the selected service supports sending the voice message comprises obtaining supported functions of the selected service. The plurality of services may include a plurality of voicemail servers. Determining whether the selected service supports sending the voice message may include querying at least one of the plurality of voicemail servers. In some cases, when the selected service is a first service, the processor may also receive a second service from the plurality of services when the first service does not support sending the voice message. The mobile device may also obtain a list of the plurality of services, wherein each of the plurality of services supports sending the voice message. In some examples the mobile device may present a default service to be used to send the voice message. Determining whether the selected service supports sending the voice message may be carried out prior to receiving the selection of the service. Determining whether the selected service supports sending the voice message may be carried out after receiving the selection of the service.

0018As shown in the example of <figref idref="DRAWINGS">FIG. 1</figref>, a first mobile device <b>102</b> desires to send a voice message to a second mobile device <b>104</b>. As described below, sending the voice message from the mobile device <b>102</b> to the mobile device <b>104</b> may be contingent on receipt of communication and/or the occurrence of one or more other events (e.g., calendar events). Sending the message may include the use of voicemail servers <b>106</b>, <b>107</b> and another server <b>108</b>, such as an enterprise server or an electronic mail server. The contingency may be evaluated by the mobile device <b>102</b>, the voicemail servers <b>106</b>, <b>107</b> or the server <b>108</b>. Accordingly, the voice message may be sent from the mobile device <b>102</b>, the voicemail servers <b>106</b>, <b>107</b>, and/or the server <b>108</b>.

0019In the example of <figref idref="DRAWINGS">FIG. 1</figref>, the mobile device <b>102</b> includes, among other things, voicemail clients <b>110</b>, <b>111</b> and applications <b>112</b>. In practice, the mobile device <b>102</b> may be implemented by a mobile telephone, a smart phone, a tablet computer, or any suitable device. The voicemail clients <b>110</b>, <b>111</b> and the applications <b>112</b> may be implemented using hardware, software, firmware, coding, or any other suitable logic to facilitate the functionality described herein. Although not pictured in <figref idref="DRAWINGS">FIG. 1</figref> for the sake of clarity, the mobile device <b>102</b> may include other functionality, such as wireless communication functionality, etc. The mobile device <b>102</b> is configured to communicate with the voicemail servers <b>106</b>, <b>107</b> and/or the server <b>108</b>, as well as suitable data networks (e.g., cellular networks, local area networks, etc.).

0020The voicemail clients <b>110</b>, <b>111</b> may be software executed by the mobile device <b>102</b> to allow the mobile device <b>102</b> to interface with the voicemail servers <b>106</b>, <b>107</b>. In this manner, the mobile device <b>102</b> may send voicemail to the voicemail servers <b>106</b>, <b>107</b> via the voicemail clients <b>110</b>, <b>111</b>. The voicemail client <b>110</b> is shown as voicemail client A in FIG. <b>1</b> and the voicemail clients <b>111</b> are referred to as other voicemail clients for purposes of explanation. The mobile device <b>102</b> may include multiple voicemail clients, each of which facilitates user interaction with voice messages associated with a voicemail server or voicemail servers. For example, with reference to <figref idref="DRAWINGS">FIG. 1</figref>, voicemail client A <b>110</b> of the mobile device <b>102</b> may be associated with the voicemail server <b>106</b>, which may be associated with a network carrier that provides network connectivity to mobile device <b>102</b>. Other voicemail servers <b>111</b> may be associated with one or more voicemail servers <b>107</b> of another entity (e.g., a voicemail server associated with an office or any other enterprise) or with any other voicemail server (e.g., a voicemail server associated with a subscription service).

0021Alternatively, rather than the mobile device <b>102</b> including multiple voicemail clients <b>110</b>, <b>111</b>, the voicemail client <b>110</b> may be an application that is configured to support multiple voicemail servers and to facilitate user interaction with numerous voicemail servers (e.g., the voicemail servers <b>106</b>, <b>107</b>). In such a case, the voicemail client <b>110</b> may include an account for each respective voicemail server to which the user has access. In either of these manners, the mobile device <b>102</b> may provide a user interface to visual voicemail (or any other voicemail) from numerous different sources.

0022As described below, the mobile device <b>102</b> may assess the function sets of associated voicemail servers (e.g., the voicemail servers <b>106</b>, <b>107</b>) to determine whether functionality is available. If the functionality is not available on a particular server, the mobile device may select a different voicemail server to perform a task involving that functionality. For example, the mobile device <b>102</b> may assess the function set of the voicemail servers <b>106</b>, <b>107</b> to determine if voice message sending is possible utilizing a particular voicemail server. If voicemail sending functionality is available through one server (e.g., the voicemail server <b>106</b>) but not another server (e.g., the voicemail server <b>107</b>), the mobile device <b>102</b> will utilize the voicemail server having the functionality facilitate sending a voice message.

0023The applications <b>112</b> may include smart phone applications, such as an electronic mail client, a calendar application, etc. In one example, the applications <b>112</b> may include an electronic mail client that interfaces to the server <b>108</b> via any suitable data network. The applications <b>112</b> may include rules that are carried out by the mobile device <b>102</b> to facilitate sending voice messages using either the voicemail client <b>110</b> and the voicemail servers <b>106</b>, <b>107</b> or the server <b>108</b>, or both.

0024The mobile device <b>104</b> includes, among other things, a voicemail client <b>120</b> and applications <b>122</b>. In practice, the mobile device <b>104</b> may be implemented by a mobile telephone, a smart phone, a tablet computer, or any suitable device. The voicemail client <b>120</b> and the applications <b>122</b> may be implemented using hardware, software, firmware, coding, or any other suitable logic to facilitate the functionality described herein. Although not pictured in <figref idref="DRAWINGS">FIG. 1</figref> for the sake of clarity, the mobile device <b>104</b> may include other functionality, such as wireless communication functionality, etc. The mobile device <b>104</b> is configured to communicate with the voicemail servers <b>106</b>, <b>107</b> as well as suitable data networks (e.g., cellular networks, local area networks, etc.).

0025The voicemail client <b>120</b> may be software executed by the mobile device <b>104</b> to allow the mobile device <b>104</b> to interface with the voicemail servers <b>106</b>, <b>107</b>. In this manner, the mobile device <b>104</b> may receive voicemail from the voicemail servers <b>106</b>, <b>107</b> via the voicemail client <b>120</b>. The voicemail client <b>120</b> is shown as voicemail client B in <figref idref="DRAWINGS">FIG. 1</figref> for purposes of explanation.

0026As described above in conjunction with the mobile device <b>102</b>, the applications <b>122</b> of the mobile device <b>104</b> may include smart phone applications, such as an electronic mail client, a calendar application, etc. For example, the applications <b>122</b> may include an electronic mail client that interfaces to an electronic mail server via any suitable data network.

0027The voicemail server <b>106</b> of the example of <figref idref="DRAWINGS">FIG. 1</figref> includes a voicemail manager <b>130</b>, a voicemail outbox for client A <b>132</b>, a voicemail inbox for client A <b>134</b>, a voicemail outbox for client B <b>136</b>, and a voicemail inbox for client B <b>138</b>. The voicemail manager <b>130</b>, in addition to carrying out standard voicemail operations, may include functionality to carry out evaluations based on rules or criteria or may include functionality to facilitate the reception of a trigger from the mobile device <b>102</b> or the server <b>108</b>. For example, the voicemail manager <b>130</b> may facilitate the storage of a voice message provided by the mobile device <b>102</b> in the voicemail outbox for client A <b>136</b>. Subsequently, the voicemail manager <b>130</b> may evaluate one or more rules to determine if the voice message is to be transferred to the voicemail inbox for client B <b>138</b>. The rules may have been previously provided to the voicemail manager <b>130</b> from the mobile device <b>102</b>. In another example, the mobile device <b>102</b> or the server <b>108</b> may store and carryout the rules and, when voicemail is to be sent, the mobile device <b>102</b> or the server <b>108</b> may provide a trigger to the voicemail manager <b>130</b>. In response to the trigger, the voicemail manager <b>130</b> may transfer the voice message to the voicemail inbox for client B <b>138</b>, which will deliver the voice message to the mobile device <b>104</b>.

0028The voicemail server <b>107</b> may include similar hardware and/or software, and/or functionality as described above in connection with the voicemail server <b>106</b>. However, the voicemail server <b>107</b> may include different function sets than the function sets included in the voicemail server <b>106</b>. For example, the voicemail server <b>106</b> may facilitate sending of voice messages as described herein, whereas the voicemail server <b>107</b> may, in some examples, not provide functionality to facilitate the sending of voice messages.

0029The server <b>108</b> may be implemented using any suitable combination of hardware and software. For example, the server <b>108</b> may be implemented as an enterprise server. In one example, the server <b>108</b> includes a rule store <b>140</b>, one or more messages <b>142</b> (e.g., electronic mail messages, voice messages, etc.), and a calendar <b>144</b> including one or more events (e.g., meetings, appointments, etc.) listed therein.

0030In one example, the rule store <b>140</b> includes rules or criteria that the server <b>108</b> evaluates to determine if one or more voice messages are to be sent. For example, the rules store <b>140</b> may be populated using the mobile device <b>102</b>.

0031The messages <b>142</b> may include electronic mail messages that are to be delivered to the mobile device <b>102</b> and may also include voice messages that are transferred to the server <b>108</b> from the mobile device <b>102</b>.

0032The calendar <b>144</b> may include events, such as appointments, meetings, or any other suitable events, that are provided by the mobile device <b>102</b>. In one example, the mobile device <b>102</b> may include a calendar application that includes similar information to the calendar <b>144</b> of the server <b>108</b>.

0033In general, during operation, a user of the mobile device <b>102</b> records a voice message designated for the mobile device <b>104</b> and designates one or more rules, the satisfaction of which results in the delivery of the voice message. The rules may include any suitable information. For example, one rule may specify that a voice message is to be delivered to the mobile device <b>104</b> when the mobile device <b>102</b> receives communication (e.g., an electronic mail, a short message service message, etc.) from the mobile device <b>104</b>. In another example, a voice message may be attached to an event after the event is created. For example, a voice message may be attached to a meeting event, wherein prior to the meeting a voice message is to be sent to each of the meeting participants reminding them of the meeting.

0034The voice message that is to be sent may be stored in any suitable location including within the mobile device <b>102</b>, within the server <b>108</b> (e.g., in the messages <b>142</b>), or within the voicemail servers <b>106</b>, <b>107</b>. The rules governing the sending of the message may be stored and evaluated by the mobile device <b>102</b>, the voicemail servers <b>106</b>, <b>107</b>, or the server <b>108</b>. For example, the voice message may be stored in the mobile device <b>102</b> and the mobile device <b>102</b> may evaluate one or more rules to control sending of the voice message. Alternatively, if the server <b>108</b> is capable of storing the voice message (e.g., in the messages <b>142</b>) and evaluating rules (e.g., from the rules store <b>140</b>), the server <b>108</b> may store the voice message and evaluate the rule(s). As a further alternative, the voicemail servers <b>106</b>, <b>107</b> may store the voice message and either of the mobile device <b>102</b> or the server <b>108</b> may send a trigger to the voicemail servers <b>106</b>, <b>107</b> to dispatch the voice message to the intended recipient.

0035<figref idref="DRAWINGS">FIGS. 2-5</figref> depict example flow diagrams representative of processes that may be implemented using, for example, computer-readable instructions stored on a computer-readable medium to send voice messages. The example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be performed using one or more processors, controllers, and/or any other suitable processing devices. For example, the example processes of <figref idref="DRAWINGS">FIGS. 2</figref>, <b>2</b>A, <b>2</b>B, and <b>4</b> may be implemented using coded instructions (e.g., computer readable instructions) stored on one or more tangible computer readable media such as flash memory, read-only memory (ROM), and/or random-access memory (RAM), such as may be found in the mobile device <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. As an additional example, the example processes of <figref idref="DRAWINGS">FIGS. 3 and 5</figref> may be implemented using coded instructions (e.g., computer readable instructions) stored on one or more tangible computer readable media such as flash memory, read-only memory (ROM), and/or random-access memory (RAM), such as may be found in the voicemail servers <b>106</b>, <b>107</b> or the server <b>108</b> of <figref idref="DRAWINGS">FIG. 1</figref>.

0036As used herein, the term tangible computer readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be implemented using coded instructions (e.g., computer-readable instructions or machine-accessible instructions) stored on one or more non-transitory computer readable media such as flash memory, read-only memory (ROM), random-access memory (RAM), cache, or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information).

0037As used herein, the term non-transitory computer-readable medium and non-transitory machine-accessible medium are expressly defined to include any type of computer-readable medium or machine-accessible medium.

0038Alternatively, some or all operations of the example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be implemented using any combination(s) of application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)), field programmable logic device(s) (FPLD(s)), discrete logic, hardware, firmware, etc. Also, some or all operations of the example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be implemented manually or as any combination(s) of any of the foregoing techniques, for example, any combination of firmware, software, discrete logic and/or hardware. Further, although the example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> are described with reference to the flow diagrams of <figref idref="DRAWINGS">FIGS. 2-5</figref>, other methods of implementing the processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be employed. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, sub-divided, or combined. Additionally, any or all operations of the example processes of <figref idref="DRAWINGS">FIGS. 2-5</figref> may be performed sequentially and/or in parallel by, for example, separate processing threads, processors, devices, discrete logic, circuits, etc.

0039In the illustrated example, the processes of <figref idref="DRAWINGS">FIGS. 2</figref>, <b>2</b>A, <b>2</b>B, and <b>4</b> are described below as performed by the mobile device <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. However, the example processes of <figref idref="DRAWINGS">FIGS. 2</figref>, <b>2</b>A, <b>2</b>B, and <b>4</b> may additionally or alternatively be implemented using any other suitable device or apparatus.

0040Now turning to <figref idref="DRAWINGS">FIG. 2</figref>, an example process to send voice messages is shown. The process of <figref idref="DRAWINGS">FIG. 2</figref> may be implemented using, for example, computer-readable instructions or any suitable combination of hardware and/or software and may be implemented on the mobile device <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The mobile device <b>102</b> specifies a service to be used (block <b>201</b>). Further detail regarding the service specification is provided below in conjunction with the examples of <figref idref="DRAWINGS">FIGS. 2A and 2B</figref>. The mobile device <b>102</b> records one or more voice messages, as well as an indication of the destination for the voice messages (block <b>202</b>). In one example, the destination may be specified by a telephone number, an electronic mail address, or any other suitable indicator of the intended recipient.

0041If the voice message is to be sent to the recipient based on receipt of communication from a particular entity, a specification of that communication is received by the mobile device (block <b>204</b>). For example, if the user of the mobile device <b>102</b> desires to specify that the voice message is to be sent upon receiving a communication from person X, an indicator of person X is provided as the communication specification. The indicator may be the identity of person X, the telephone of person X, an electronic mail address of person X, or any other suitable indicator.

0042The mobile device <b>102</b> evaluates server capabilities (block <b>206</b>) to determine if any servers are available to store the voice message and to evaluate the communication specification against incoming communications. For example, the mobile device <b>102</b> may query the server <b>108</b> or the voicemail servers <b>106</b>, <b>107</b> to determine if storage and evaluation resources are available.

0043If there is no server capable of the needed storage and evaluation functionality, the mobile device <b>102</b> handles the storage and evaluation itself. Thus, the mobile device <b>102</b> receives communication (block <b>210</b>) and determines if the communication meets the specification (block <b>212</b>). For example, the mobile device <b>102</b> determines whether communication (e.g., an electronic mail) has been received from person X at the mobile device <b>102</b> or at a server (e.g., the voicemail servers <b>106</b>, <b>107</b> or the server <b>108</b>) having an account associated with the mobile device <b>102</b>.

0044The evaluation (block <b>212</b>) will continue and, when the communication specification is met (e.g., an electronic mail is received from person X), the mobile device sends the voice message to the recipient (block <b>214</b>). According to this approach, the voice message may be stored in the mobile device <b>102</b> and sent to the recipient from the mobile device <b>102</b>. In another example, the voice message may be stored separately from the mobile device <b>102</b> and the mobile device <b>102</b> may provide a trigger for the voice message to be sent. For example, the voice message may be stored in the voicemail servers <b>106</b>, <b>107</b> and the mobile device <b>102</b> may trigger sending of the message from the voicemail servers <b>106</b>, <b>107</b>.

0045Alternatively, if a capable server is available (block <b>208</b>), the mobile device <b>102</b> sends the voice message and the communication specification to the server (block <b>216</b>). For example, if the mobile device <b>102</b> determines that the server <b>108</b> is available for the voice message storage and communication specification, the voice message and the communication specification may be provided to the server <b>108</b>, which stores the voice message and the communication specification (e.g., rules). While the determination of server capabilities is shown as occurring after the recording of the voice mail message, this is not necessarily the case. In accordance with the foregoing example, the server <b>108</b> may operate as shown in <figref idref="DRAWINGS">FIG. 3</figref> and as described below.

0046As shown in the example of <figref idref="DRAWINGS">FIG. 2A</figref>, in one example the specify service process <b>201</b> may include the mobile device receiving a service selection (block <b>220</b>), which may be provided through user input. In one example, a user may provide to the mobile device <b>102</b> an indication that the user desires to utilize, for example, voicemail server <b>106</b>.

0047The mobile device <b>102</b>, upon receiving the selection (block <b>220</b>), obtains the supported functions of the selected service (block <b>222</b>). In one example, the mobile device <b>102</b> may query the selected service (e.g., the voicemail server <b>106</b>) to obtain a list of functions supported by that service. In another example, the mobile device <b>102</b> may store a list of functions that are supported by the selected service. A stored list of functions may be pre-populated into the mobile device <b>102</b>, or the mobile device <b>102</b> may have previously obtained the list of functions based on a prior query to the selected service. If the list is based on a prior query, there may be a time associated with the list of functions, whereby after a pre-determined period of time, the list of functions associated with the service must be refreshed by querying the selected service.

0048When the list of supported functions has been obtained (block <b>222</b>), the mobile device <b>102</b> evaluates the list of functions to determine if the desired function is supported (block <b>224</b>). For example, if the mobile device <b>102</b> is being used to send a voice message and the selected service is to carry out the same, the mobile device <b>102</b> determines if voice message sending is supported by the functionality of the selected voicemail server. If the desired function is not supported by the selected service (block <b>224</b>), the mobile device <b>102</b> may receive another service selection (block <b>220</b>) by informing the user that the selected service does not support the desired function and prompting for a selection of another service.

0049If the desired function is supported by the selected service (block <b>224</b>), the mobile device <b>102</b> designates that service for use to carry out the desired function (block <b>226</b>). For example, if the voicemail server <b>106</b> supports sending voice messages, the voicemail server <b>106</b> is designated to send the voice message and is used as such.

0050An alternative example of the specify service process <b>201</b> is shown in the example of <figref idref="DRAWINGS">FIG. 2B</figref>. As shown in <figref idref="DRAWINGS">FIG. 2B</figref>, for a desired functionality, the mobile device <b>102</b> presents a default service (block <b>240</b>). For example, if the user manifests a desire to send a voice message, the mobile device may present voicemail server <b>106</b> as the default service for the function of sending the voice message. The mobile device <b>102</b> determines if the default service is to be utilized (block <b>242</b>). In one example, this determination may be made by evaluating user input to the mobile device <b>102</b>. If the default service is to be used (block <b>242</b>), the mobile device <b>102</b> designates that service for use to carry out the desired function (block <b>244</b>). For example, if the voicemail server <b>106</b> is the default service that is to be used to send a voice message, the voicemail server <b>106</b> is designated to send the voice message and is used as such.

0051If the default service is not to be utilized (block <b>242</b>), the mobile device <b>102</b> obtains a list of services that support the desired function (block <b>246</b>). In one example, the mobile device <b>102</b> may query services (e.g., the voicemail server <b>106</b> and/or the voicemail server <b>107</b>) to obtain a list of services that support the desired function (e.g., the sending of a voice message). In another example, the mobile device <b>102</b> may store a list of services that support the desired function. A stored list may be pre-populated into the mobile device <b>102</b>, or the mobile device <b>102</b> may have previously obtained or determined the list based on prior queries to services to determine their functionality. If the list is based on prior queries, there may be a time associated with the list, whereby after a pre-determined period of time, the list must be refreshed.

0052When the list of services is obtained (block <b>246</b>), the mobile device <b>102</b> receives a selection of a service that is to be used to carry out the desired function (block <b>248</b>) and that service is designated (block <b>244</b>), as described above.

0053In the example of <figref idref="DRAWINGS">FIG. 3</figref>, the server <b>108</b> receives the voice message and the communication specification from the mobile device <b>102</b> (block <b>302</b>). Additionally, the server <b>108</b> receives communication (block <b>304</b>) and evaluates the communication to determine whether the communication meets the specification (block <b>306</b>). When a communication meets the communication specification (block <b>306</b>), the voice message is sent to the recipient (block <b>308</b>). The voice message may be sent to the recipient directly from the server <b>108</b> or may be sent to the recipient via the voicemail servers <b>106</b>, <b>107</b>.

0054<figref idref="DRAWINGS">FIG. 4</figref> is an example process to send voice messages in response to occurrence of a predefined event. The process of <figref idref="DRAWINGS">FIG. 4</figref> may be implemented using, for example, computer-readable instructions or any suitable combination of hardware and/or software and may be implemented on the mobile device <b>102</b> of <figref idref="DRAWINGS">FIG. 1</figref>. The mobile device <b>102</b> receives an event, such as a calendar event (e.g., an appointment, a meeting, etc.) (block <b>402</b>) and records one or more voice messages, as well as an indication of the destination for the voice messages (block <b>404</b>) after the event is recorded. The voice message is to be sent to recipients in response to the occurrence of the event. For example, a voice message reminder may be sent in advance of a meeting calendar event. In one example, the destination for the voice message may be specified in the event information by a telephone number, an electronic mail address, or any other suitable indicator of the intended recipient.

0055The mobile device <b>102</b> evaluates server capabilities (block <b>406</b>) to determine if any servers are capable of storing the voice message and evaluating whether the specified event has occurred (block <b>408</b>). For example, the mobile device <b>102</b> may query the server <b>108</b> or the voicemail servers <b>106</b>, <b>107</b> to determine if storage and evaluation resources are available. In one particular example, the server <b>108</b>, as described above, may include the calendar <b>144</b> including the events and associated event information and the message storage <b>142</b>. As such, the server <b>108</b> may be particularly well suited to evaluate whether the specified even has occurred.

0056If there is no server capable of the needed storage and evaluation, the mobile device <b>102</b> determines if the event has occurred (block <b>410</b>). For example, the mobile device <b>102</b> determines whether a calendar event has occurred. The evaluation (block <b>410</b>) will continue and when the communication specification is met (e.g., a particular calendar event has occurred), the mobile device sends the voice message to the recipient (block <b>412</b>). According to this approach, the voice message may be stored in the mobile device <b>102</b> and sent to the recipient from the mobile device or the voice message may be stored separately from the mobile device <b>102</b> and the mobile device may provide a trigger for the voice message to be sent. For example, the voice message may be stored in the voicemail servers <b>106</b>, <b>107</b> and the mobile device <b>102</b> may trigger sending of the message from the voicemail servers <b>106</b>, <b>107</b>.

0057Alternatively, if a capable server is available (block <b>408</b>), the mobile device <b>102</b> sends the voice message and the event to the server (block <b>416</b>). For example, if the mobile device <b>102</b> determines that the server <b>108</b> is available for the voice message storage <b>142</b> and event storage <b>144</b>, the voice message and the event may be provided to the server <b>108</b>. While the determination of server capabilities is shown as occurring after the recording of the voice mail message, this is not necessarily the case. In accordance with the foregoing example, the server <b>108</b> may operate as shown in <figref idref="DRAWINGS">FIG. 5</figref>.

0058In the example of <figref idref="DRAWINGS">FIG. 5</figref>, the server <b>108</b> receives the voice message and the event from the mobile device <b>102</b> (block <b>502</b>). The server <b>108</b> determines whether the event has occurred (block <b>504</b>). When the event has occurred (block <b>504</b>), the voice message is sent to the recipient (block <b>506</b>). The voice message may be sent to the recipient directly from the server <b>108</b> or may be sent to the recipient via the voicemail servers <b>106</b>, <b>107</b>.

0059Further detail of certain aspects of the mobile devices <b>102</b>, <b>104</b> of <figref idref="DRAWINGS">FIG. 1</figref> are shown in <figref idref="DRAWINGS">FIG. 6</figref> with respect to a mobile, or portable electronic, device <b>600</b>. The mobile device <b>600</b> includes multiple components, such as a processor <b>602</b> that controls the overall operation of the mobile device <b>600</b>. Communication functions, including data and voice communications, are performed through a communication subsystem <b>604</b>. Data received by the mobile device <b>600</b> is decompressed and decrypted by a decoder <b>606</b>. The communication subsystem <b>604</b> receives messages from and sends messages to a wireless network <b>650</b>. The wireless network <b>650</b> may be any type of wireless network, including, but not limited to, data wireless networks, voice wireless networks, and networks that support both voice and data communications. A power source <b>642</b>, such as one or more rechargeable batteries or a port to an external power supply, powers the mobile device <b>600</b>.

0060The processor <b>602</b> interacts with other components, such as Random Access Memory (RAM) <b>608</b>, memory <b>610</b>, a display <b>612</b> with a touch-sensitive overlay <b>614</b> operably coupled to an electronic controller <b>616</b> that together comprise a touch-sensitive display <b>618</b>, one or more actuators <b>620</b>, one or more force sensors <b>622</b>, an auxiliary input/output (I/O) subsystem <b>624</b>, a data port <b>626</b>, a speaker <b>628</b>, a microphone <b>630</b>, short-range communications <b>632</b>, and other device subsystems <b>634</b>. In one example, the processor <b>602</b> and the memory <b>610</b> may cooperate to implement the functionality described in conjunction with the controllers <b>124</b> and <b>134</b> of <figref idref="DRAWINGS">FIG. 1</figref>. For example, tangible and/or non-transitory, and/or machine readable instructions may be stored by the processor <b>602</b> and/or the memory <b>610</b> to implement the functionality shown in <figref idref="DRAWINGS">FIGS. 2-4</figref>.

0061Input via a graphical user interface is provided via the touch-sensitive overlay <b>614</b>. The processor <b>602</b> interacts with the touch-sensitive overlay <b>614</b> via the electronic controller <b>616</b>. Information, such as text, characters, symbols, images, icons, and other items that may be displayed or rendered on a mobile device, is displayed on the touch-sensitive display <b>618</b> via the processor <b>602</b>. The processor <b>602</b> may interact with an accelerometer <b>636</b> that may be utilized to detect direction of gravitational forces or gravity-induced reaction forces.

0062To identify a subscriber for network access, the mobile device <b>600</b> may utilize a Subscriber Identity Module or a Removable User Identity Module (SIM/RUIM) card <b>638</b> for communication with a network, such as the wireless network <b>650</b>. Alternatively, user identification information may be programmed into memory <b>610</b>.

0063The mobile device <b>600</b> includes an operating system <b>646</b> and software programs, applications, or components <b>648</b> that are executed by the processor <b>602</b> and are typically stored in a persistent, updatable store such as the memory <b>610</b>. Additional applications or programs may be loaded onto the mobile device <b>600</b> through the wireless network <b>650</b>, the auxiliary I/O subsystem <b>624</b>, the data port <b>626</b>, the short-range communications subsystem <b>632</b>, or any other suitable subsystem <b>634</b>.

0064A received signal such as a text message, an e-mail message, or web page download is processed by the communication subsystem <b>604</b> and input to the processor <b>602</b>. The processor <b>602</b> processes the received signal for output to the display <b>612</b> and/or to the auxiliary I/O subsystem <b>624</b>. A subscriber may generate data items, for example e-mail messages, which may be transmitted over the wireless network <b>650</b> through the communication subsystem <b>604</b>. For voice communications, the overall operation of the mobile device <b>600</b> is similar. The speaker <b>628</b> outputs audible information converted from electrical signals, and the microphone <b>630</b> converts audible information into electrical signals for processing.

0065Although certain methods, apparatus, and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. To the contrary, this patent covers all methods, apparatus, and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.