Voicemail conversion

BACKGROUND

0001Voicemail servers have been implemented in communications systems to provide users with the ability to record messages directed to them when unavailable at a communications device. Generally speaking, when a caller sends a communication request to a communications line associated with a user, a communication network determines whether the user is available on the communications line. If the user is not available on the communications line, the communication request may be forwarded to a voicemail server that is coupled to the communications network. The voicemail server can then provide a predetermined recording to the caller and prompt the caller to leave a message.

0002While many users utilize the voicemail servers in Public Switched Telephone Networks (“PSTNs”), many users have migrated to Internet Protocol (“IP”) networks and are thus utilizing IP voicemail servers. This transgression has provided users with increased functionality and speed for their communication and voicemail services. While many users have changed from PSTN voicemail services to IP voicemail services, some users, although utilizing an IP communications network (such as Voice over IP networks), prefer to maintain their PSTN voicemail services. As such, integration among IP networks and wireless networks with PSTN voicemail servers have become problematic. Many users utilize PSTN voicemail servers that are unable to send Message Waiting Indicator (“MWI”) signals to IP based communications devices.

0003Thus, a heretofore unaddressed need exists in the industry to address the aforementioned deficiencies and inadequacies.

SUMMARY

0004Included are embodiments for providing voicemail conversion. At least one embodiment of a method includes receiving a message waiting indicator signal in a first protocol, the message waiting indicator signal being received from a Public Switched Telephone Network (PSTN) based voicemail server, the message waiting indicator signal being configured to indicate that a message for a called party has been received by the PSTN based voicemail server. Some embodiments of a method include receiving a PSTN based identifier for an Internet Protocol (IP) based communications device associated with the called party and converting the received message waiting indicator signal from the first protocol to a second protocol, the second protocol being configured for communication to the IP based communications device.

0005Also included are embodiments of a system for providing voicemail conversion. At least one embodiment of a system includes an indicator receiving component configured to receive a message waiting indicator signal in a first protocol, the message waiting indicator signal being received from a Public Switched Telephone Network (PSTN) based voicemail server, the message waiting indicator signal being configured to indicate that a message for a called party has been received by the PSTN based voicemail server. Some embodiments include an identifier receiving component configured to receive a PSTN based identifier for an Internet Protocol (IP) based communications device associated with the called party and a converting component configured to convert the received message waiting indicator signal from the first protocol to a second protocol, the second protocol being configured for communication to the IP based communications device.

0006Also included are embodiments of a computer readable medium for providing voicemail conversion. At least one embodiment of a computer readable medium includes indicator receiving logic configured to receive a message waiting indicator signal in a first protocol, the message waiting indicator signal being received from a Public Switched Telephone Network (PSTN) based voicemail server, the message waiting indicator signal being configured to indicate that a message for a called party has been received by the PSTN based voicemail server. Some embodiments include identifier receiving logic configured to receive a PSTN based identifier for an Internet Protocol (IP) based communications device associated with the called party and converting logic configured to convert the received message waiting indicator signal from the first protocol to a second protocol, the second protocol being configured for communication to the IP based communications device.

0007Other systems, methods, features, and advantages of this disclosure will be or become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, and be within the scope of the present disclosure.

BRIEF DESCRIPTION

0008Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.

0009<figref idref="DRAWINGS">FIG. 1</figref> is a functional diagram of an exemplary communications network environment.

0010<figref idref="DRAWINGS">FIG. 2</figref> is a functional diagram illustrating an embodiment of a communications network configuration, similar to the configuration from <figref idref="DRAWINGS">FIG. 1</figref>.

0011<figref idref="DRAWINGS">FIG. 3</figref> is a functional diagram illustrating a detailed view of a communications network configuration, similar to the configuration from <figref idref="DRAWINGS">FIG. 2</figref>.

0012<figref idref="DRAWINGS">FIG. 4</figref> is an exemplary embodiment of a communication network illustrating the facilitation of voicemail services between the PSTN network, an IP network, and a wireless network similar to the diagram from <figref idref="DRAWINGS">FIG. 2</figref>.

0013<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating an exemplary embodiment of a converter that may be configured to communicate via a communications network such as the network from <figref idref="DRAWINGS">FIG. 4</figref>.

0014<figref idref="DRAWINGS">FIG. 6</figref> is an exemplary embodiment of a sequence diagram illustrating a process for providing a message waiting indicator signal to a communications device such as the communications device in <figref idref="DRAWINGS">FIG. 4</figref>.

0015<figref idref="DRAWINGS">FIG. 7A</figref> is an exemplary embodiment of a sequence diagram for providing a message waiting indicator signal for an IP based voicemail server, similar to the sequence diagram from <figref idref="DRAWINGS">FIG. 6</figref>.

0016<figref idref="DRAWINGS">FIG. 7B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 7A</figref>.

0017<figref idref="DRAWINGS">FIG. 8A</figref> is an exemplary embodiment of sequence diagram for providing the message waiting indicator signal to a PSTN communications device via an IP based communications device via a PSTN voicemail server, similar to the sequence diagram from <figref idref="DRAWINGS">FIGS. 7A and 7B</figref>.

0018<figref idref="DRAWINGS">FIG. 8B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 8A</figref>.

0019<figref idref="DRAWINGS">FIG. 8C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 8B</figref>.

0020<figref idref="DRAWINGS">FIG. 9A</figref> is an exemplary embodiment of a sequence diagram for providing a message waiting indicator signal to a user of an IP based communications device via a wire and IP network, similar to the sequence diagrams from <figref idref="DRAWINGS">FIGS. 8A</figref>, <b>8</b>B, and <b>8</b>C.

0021<figref idref="DRAWINGS">FIG. 9B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 9A</figref>.

0022<figref idref="DRAWINGS">FIG. 9C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIGS. 9A and 9B</figref>.

0023<figref idref="DRAWINGS">FIG. 10A</figref> is an exemplary embodiment of a sequence diagram for providing a message waiting indicator signal to a dual mode handset via a wireless network, similar to the sequence diagram from <figref idref="DRAWINGS">FIGS. 9A</figref>, <b>9</b>B, and <b>9</b>C.

0024<figref idref="DRAWINGS">FIG. 10B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 10A</figref>.

0025<figref idref="DRAWINGS">FIG. 10C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIGS. 10A and 10B</figref>.

DETAILED DESCRIPTION

0026<figref idref="DRAWINGS">FIG. 1</figref> is a functional diagram of an exemplary communications network environment. As illustrated, a plurality of users may be connected via an external network such as a communications network <b>100</b>. The communications network <b>100</b> can include, for example, the Internet, a Wi-Fi® network (IEEE 802.11 compatible), a Wi-Max network (IEEE 802.16 compatible), a Public Switched Telephone Network (PSTN), a cellular communications network and/or other communications mediums. Users may access the communications network <b>100</b> via a communications device <b>102</b>, a communications device <b>104</b>, and/or a communications device <b>106</b> (via a wireless access point <b>108</b>).

0027It should be appreciated that while the network <b>100</b>, the communications devices <b>102</b>, <b>104</b>, <b>106</b> (via the wireless access point <b>108</b>), and connections illustrated in <figref idref="DRAWINGS">FIG. 1</figref> are shown by way of example, this disclosure is not limited to these examples. This disclosure may be applicable to any communications device, connection, and network that supports voice, data, and/or other types of communications.

0028One should note that depending on the type of communication desired, different functionality may be utilized. More specifically, while the communications devices <b>102</b> and <b>106</b> may be configured to facilitate voice communications over a cellular network and/or a PSTN, these devices may also be configured for data communications via the Internet. Similarly, the communications devices <b>102</b> and <b>106</b> may also be configured to facilitate communications via a Wi-Fi® network and/or a Wi-Max network. As a nonlimiting example, if a user operating the communications device <b>106</b> wishes to make a cellular communication, the user can input the address (e.g., telephone number) of the called party device. This address can be sent to the wireless access point <b>108</b> (which may include a cellular antenna and/or other component), configured to send the communication request to the network <b>100</b>. The network <b>100</b> may employ one or more cellular networks, PSTNs and/or other networks for facilitating the communication. Upon connecting communications device <b>104</b> with the called party device <b>102</b>, communication may begin.

0029Similarly, if a user operating the communications device <b>104</b> wishes to access a website (and/or other data associated with the Internet), the user can send a communication request, which may include an address, such as a Uniform Resource Locator (URL) or other Uniform Resource Identifier (URI). The request can be sent to the desired computing device (such as a server data storage) via the network <b>100</b>, which may include the Internet, a Wi-Max network a Wi-Fi® network, cellular network, and/or other network. The desired computing device can then respond by sending the requested data to the communications device <b>104</b> via the same (or similar) transmission mediums.

0030Also included in the nonlimiting example of <figref idref="DRAWINGS">FIG. 1</figref> is a voicemail server <b>110</b>. The voicemail server <b>110</b> may be configured to serve one or more user accounts. More specifically, in at least one embodiment, the voicemail server <b>110</b> may be configured to provide voicemail services for a telephone line coupled to the communications device <b>102</b>. The voicemail server <b>110</b> may be configured to receive a redirected call intended for a user associated with the communications device <b>102</b>. If the network <b>100</b> determines that a user is currently not available on the communications device <b>102</b>, the call may be redirected to the voicemail server <b>110</b>. The voicemail server <b>110</b> may be configured to provide the caller with options for leaving a message. Once a message is received (and/or stored), the voicemail server <b>110</b> can send a Message Waiting Indicator (MWI) signal to the communications device <b>102</b> (and/or one or more communications devices associated with the line to which the communications device <b>102</b> is connected). Upon receiving the message waiting indicator signal from the voicemail server <b>110</b>, the communications device <b>102</b> may display a light and/or other signifier of the message waiting indicator signal.

0031<figref idref="DRAWINGS">FIG. 2</figref> is a functional diagram illustrating an embodiment of a communications network configuration, similar to the configuration from <figref idref="DRAWINGS">FIG. 1</figref>. As illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, a communications network may include a plurality of networks, such as a Public Switched Telephone Network (PSTN) <b>202</b>, a wireless network <b>206</b>, which may include at least one wireless access point <b>108</b> (e.g., a communications tower, Wi-Fi® hot spot, etc.), and an Internet Protocol (IP) network <b>204</b> among others. The PSTN <b>202</b> may be coupled to at least one PSTN configured communications device <b>102</b>. The PSTN configured communications device <b>102</b> may be a conventional telephone, a wireless telephone, a personal computer, or other device.

0032Similarly, the IP network <b>204</b> may be coupled to at least one IP configured communications device <b>104</b>. The IP configured communications device <b>104</b> may include a personal computer, a telephone, and/or a wireless device (such as a pocket personal computer), or other device configured to communicate using an IP network. Further, a wireless configured communications device <b>106</b> may be coupled (wired or wirelessly) to the wireless access point <b>108</b>, which can facilitate communications with the wireless network <b>206</b>. One should note that while <figref idref="DRAWINGS">FIG. 2</figref> represents the wireless access point <b>108</b> as a structural tower, this is not intended as a limitation. The wireless access point <b>108</b> may take any of a number of forms such as a satellite, cellular tower, router, and/or other facilitator of communications with the wireless network <b>206</b>.

0033Additionally, while the wireless configured communications device <b>106</b> is illustrated as coupling wirelessly with the wireless access point <b>108</b>, this is not intended as a limitation. Further, the IP network configured communications device <b>104</b> and the PSTN configured communications device <b>102</b> may also communicate wirelessly or via a wired communications medium, depending on the particular configuration. The purpose of this disclosure is not to limit the subject matter in this or other manners.

0034Additionally included in the nonlimiting example of <figref idref="DRAWINGS">FIG. 2</figref> are a PSTN voicemail server <b>218</b> and an IP voicemail server <b>224</b>. In at least one embodiment, the PSTN voicemail server <b>218</b> may be configured for providing voicemail services according to a PSTN network, such as PSTN <b>202</b>. Similarly, the IP voicemail server <b>224</b> may be configured for providing voicemail services according to an IP network (such as a Voice over Internet Protocol (VoIP) network). Generally speaking, a user of the PSTN configured communications device <b>102</b> is associated with the PSTN voicemail server <b>218</b>. However, as users migrate from the PSTN configured communications devices <b>102</b> to the IP network configured communications devices <b>104</b>, some users may maintain an account with the PSTN based voicemail server <b>218</b>. Similarly, as some users change from the IP network configured communications device <b>104</b> to the PSTN configured communications device <b>102</b>, those users may maintain an account with the IP based voicemail server <b>224</b>. Since the PSTN based voicemail server <b>218</b> may not be configured to communicate with the IP network configured communications device <b>104</b> (and the IP based voicemail server <b>224</b> may not be configured to communicate with the PSTN configured communications device <b>102</b>), problems may arise. Similar problems may also arise with the presence of a wireless based voicemail server coupled to the wireless network <b>206</b> (not shown).

0035<figref idref="DRAWINGS">FIG. 3</figref> is a functional diagram illustrating a detailed view of a communications network configuration, similar to the configuration from <figref idref="DRAWINGS">FIG. 2</figref>. As illustrated, the PSTN <b>202</b> includes a plurality of PSTN configured communications devices <b>102</b><i>a</i>, <b>102</b><i>b</i>, <b>102</b><i>c</i>, coupled to a PSTN sub-network <b>1</b> (PSTN<b>1</b>) <b>302</b><i>a</i>, (PSTN<b>2</b>) <b>302</b><i>b</i>, (PSTN<b>3</b>) <b>302</b><i>c</i>, respectively. In at least one embodiment, the PSTN<b>1</b><b>302</b><i>a </i>is a PSTN of one communications protocol, while the PSTN<b>2</b><b>302</b><i>b </i>is a PSTN of another protocol. The PSTN<b>3</b><b>302</b><i>c </i>is a communications protocol different than both the PSTN<b>1</b><b>302</b><i>a </i>and the PSTN<b>2</b><b>302</b><i>b. </i>

0036Similarly, the IP configured communications devices <b>104</b><i>a</i>, <b>104</b><i>b</i>, <b>104</b><i>c </i>are coupled to an IP Sub-Network <b>1</b> (IPN<b>1</b>) <b>304</b><i>a</i>, IPN<b>2</b><b>304</b><i>b</i>, IPN<b>3</b><b>304</b><i>c</i>, respectively. In at least one embodiment, each of these sub-networks is configured to communicate in a protocol different than the other two. As a nonlimiting example, the IPN<b>1</b><b>304</b><i>a </i>can be a Digital Subscriber Line (DSL) communications network, while the IPN<b>2</b><b>304</b><i>b </i>can be a cable-based IP network. The IPN<b>3</b><b>304</b><i>c </i>may be a communications network that conforms to another protocol, which may be different than the IPN<b>1</b><b>304</b><i>a</i>, and/or the IPN<b>2</b><b>304</b><i>b. </i>

0037The wireless network <b>206</b> may be coupled to one or more of the wireless configured communications devices <b>106</b><i>a</i>, <b>106</b><i>b</i>, and/or <b>106</b><i>c </i>via the wireless access points <b>108</b><i>a</i>, <b>108</b><i>b</i>, and <b>108</b><i>c</i>. One or more of the wireless configured communications devices <b>106</b><i>a</i>, <b>106</b><i>b</i>, <b>106</b><i>c </i>may be coupled to a wireless subnet (WL<b>1</b>) <b>306</b><i>a</i>, WL<b>2</b><b>306</b><i>b</i>, WL<b>3</b><b>306</b><i>c</i>, respectively. One or more of the wireless sub-networks <b>306</b><i>a</i>, <b>306</b><i>b</i>, <b>306</b><i>c </i>may be configured to communicate data pursuant to a different communications protocol. As a nonlimiting example, the WL<b>1</b><b>306</b><i>a </i>may be configured to communicate via a Personal Communications Services (PCS), while the WL<b>2</b><b>306</b><i>b </i>may be configured to communicate via an analog cell phone protocol, while the WL<b>3</b><b>306</b><i>c </i>may be configured to communicate via a digital service protocol.

0038Although the PSTN configured communications device <b>102</b><i>a </i>may be a PSTN-based communications device, a user may establish a communications session with wireless configured communications device <b>106</b><i>c</i>, regardless of the fact that the two users are implementing devices that utilize different protocols. As with any of the devices illustrated in these nonlimiting examples, users of devices that operate via different protocols may generally establish a communications session.

0039Additionally included in the nonlimiting example of <figref idref="DRAWINGS">FIG. 3</figref> are a PSTN voicemail server <b>318</b>, an IP voicemail server <b>324</b><i>a</i>, and an IP voicemail server <b>324</b><i>b</i>. As discussed above, the PSTN voicemail server <b>318</b> may be configured to provide voicemail services in a PSTN, while the IP voicemail servers <b>324</b><i>a</i>, <b>324</b><i>b </i>may be configured to provide voicemail services in an IP network. Additionally, as discussed above, as PSTN the voicemail server <b>318</b> may have difficulty providing services to the IP network configured devices <b>104</b>, the IP voicemail server <b>324</b><i>a </i>may have difficulty providing services to communications devices on a different sub-network (e.g., the communications device <b>104</b><i>c </i>on the IPN<b>2</b><b>304</b><i>b</i>). Similar difficulties may arise with other sub-networks on the PSTN <b>202</b> and/or the wireless network <b>206</b>.

0040One should also note that while only one communications device is coupled to each sub-network in <figref idref="DRAWINGS">FIG. 3</figref>, this is for discussion purposes only. As one of ordinary skill in the art will understand, any number of communications devices may be coupled to a single sub-network.

0041<figref idref="DRAWINGS">FIG. 4</figref> is an exemplary embodiment of a communication network, illustrating the facilitation of voicemail services between the PSTN network <b>202</b>, an IP network <b>204</b>, and the wireless network <b>206</b> similar to the diagram from <figref idref="DRAWINGS">FIG. 2</figref>. More specifically, as illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 4</figref>, a user operating the communications device <b>102</b><i>a </i>may initiate a communication via the central office <b>412</b><i>a </i>via the PSTN <b>202</b> to the central office <b>412</b><i>b </i>for a communication directed toward a user at the communications device <b>102</b><i>b</i>. If a user at the communications device <b>102</b><i>b </i>is currently unavailable, a central office <b>412</b><i>b </i>may be configured to determine that the user is unavailable and forward the communication request via the central office <b>412</b><i>d </i>to a PSTN based voicemail server <b>418</b>. The PSTN based voicemail server <b>418</b> may be configured to provide the caller with an option to leave a message for the user of the communications device <b>102</b><i>b</i>. After receiving a message, the PSTN based voicemail server <b>418</b> may be configured to send a message waiting indicator signal (MWI) signal, via the PSTN <b>202</b>, to the communications device <b>102</b><i>b</i>, such that when a user returns to the communications device <b>102</b><i>b</i>, a message waiting indicator may be displayed. The message waiting indicator may include a light, light emitting diode (LED), liquid crystal display (LCD) screen output, a pulsating dial tone, and/or other indicators for conveying the received data.

0042As the communications device <b>102</b><i>b </i>is coupled to the PSTN <b>202</b> and the PSTN based voicemail server <b>418</b> is configured to operate in the PSTN <b>202</b>, the message waiting indicator signal sent to the communications device <b>102</b><i>b </i>may be received without modification. Similarly, if users of the communications devices <b>104</b><i>a </i>and/or <b>106</b> desire to send a communication request to a user of the user communications device <b>102</b><i>b </i>who is currently unavailable, the PSTN voicemail server <b>418</b> may be configured to provide a message waiting indicator signal to the communications device <b>102</b><i>b </i>without modification. Upon receiving the message waiting indicator signal, the communications device <b>102</b><i>b </i>can display the message waiting indicator.

0043Similarly, if a caller initiates communication requests to a user on the communications device <b>104</b><i>b </i>which is configured to operate on the IP network <b>204</b> and the user of communications device <b>104</b><i>b </i>is currently unavailable, an IP based voicemail server <b>424</b> may be configured to receive a forwarded call from the communications device <b>104</b><i>b </i>via the IP network <b>204</b> and then provide the message services as described above. Additionally, the IP based voicemail server <b>424</b> may be configured to send a message waiting indicator signal via session initiation protocol (SIP) such that the user of communications device <b>104</b><i>b </i>may be provided with an indication that a message is currently being stored at the IP based voicemail server <b>424</b>. As discussed above, the origination of the call is irrelevant to the communication of the message waiting indicator signal.

0044As an additional nonlimiting example, the user of the PSTN based communications device <b>102</b><i>b </i>utilizes the IP based voicemail server <b>424</b> and may receive a communication request from a user (via the PSTN based communications device <b>102</b><i>a</i>, via an IP based communications device <b>104</b>, a wireless based communications device <b>106</b>, and/or other communications devices). Upon receiving the voicemail from the caller, the IP based voicemail server <b>424</b> can send a SIP message waiting indicator signal to a terminal server <b>422</b>. The terminal server <b>422</b> can be configured to receive the SIP message from the IP based voicemail server <b>424</b> and convert the received message waiting indicator signal into a simplified message disk interface (SMDI) message and/or signaling system number 7 protocol (SS7). The converted message waiting indicator signal can then be sent to the central office <b>412</b><i>d </i>at the PSTN <b>202</b>, which may then be sent to the PSTN based communications device <b>102</b><i>b</i>, such that a user can identify that a message is waiting.

0045Additionally, in some configurations, a user of the IP based communications device <b>104</b><i>b </i>and/or Plain Old Telephone System (POTS) communications device <b>104</b><i>a</i>, <b>104</b><i>c </i>may utilize the PSTN based voicemail server <b>418</b>. As discussed above, a caller sending a communication request to a user on the communications device <b>104</b><i>a </i>may send the communications request from the PSTN based communications device <b>102</b><i>b </i>via the central office <b>412</b><i>b </i>via the PSTN <b>202</b>. The PSTN <b>202</b> may then facilitate communication of the communication request to the IP network <b>204</b>, which may then send the message to a Digital Subscriber Line Access Module (DSLAM) <b>426</b>. The DSLAM <b>426</b> may be configured to incorporate the PSTN based (e.g., POTS and/or other communications devices) into the IP network <b>204</b>. Upon a determination by the PSTN <b>202</b> and/or the IP network <b>204</b> that a user is currently unavailable at the communications device <b>104</b><i>a</i>, a communication request can be forwarded to the PSTN based voicemail server <b>418</b>, to which the user of <b>104</b><i>a </i>is currently subscribed. The PSTN based voicemail server <b>418</b> can be configured to receive the forwarded communication request and provide a user prompt for the caller to leave a message for the user of the communications device <b>104</b><i>a. </i>

0046The PSTN based voicemail server <b>418</b> can send a Simplified Message Desk Interface (SMDI) and/or other message waiting indicator signal to a converter <b>414</b>. The converter <b>414</b> may be configured to receive the message waiting indicator and an address of the recipient of the message waiting indicator signal (e.g., a telephone number of the user device <b>104</b><i>a</i>). The converter <b>414</b> may also be configured to send the received address to a SIP locator <b>416</b>. The SIP locator <b>416</b> may be configured to receive the address (which may include a telephone number, email address, Instant Messaging address, and/or other address) to determine a uniform resource identifier (URI) associated with the received address. The SIP locator <b>416</b> can then send the URI to the converter <b>414</b>. The converter <b>414</b> can send the message waiting indicator signal via SS7, SIP and/or other IP based protocols to the IP network <b>204</b>. The IP network <b>204</b> can send the message to the DSLAM <b>426</b>, which from the received URI can determine an IP address of the communications device <b>104</b><i>a</i>. The message waiting indicator may then be received by the communications device <b>104</b><i>a</i>, which can indicate to the user that a message is currently waiting on the PSTN based voicemail server <b>418</b>.

0047As an additional nonlimiting example, a user of the wireless network <b>206</b> such as a user of the communications device <b>106</b> may be configured to receive voicemails via the PSTN based voicemail server <b>418</b>. As such, if a user receives a message at the PSTN based voicemail server <b>418</b>, the PSTN voicemail server <b>418</b> may be configured to send an SMDI message waiting indicator signal (and/or other PSTN based message waiting indicator signal) to a wireless network converter <b>420</b>. The wireless network converter <b>420</b> may be configured to receive the PSTN based message waiting indicator signal and send the message waiting indicator signal to the wireless network <b>206</b>. The wireless network <b>206</b> may then send the converted message waiting indicator signal to the user device <b>106</b>, such that the user can receive an indication that a message is waiting on the PSTN based voicemail server <b>418</b>.

0048One should note that while the converter <b>414</b> (and/or the SIP locator <b>416</b>) are depicted as providing services to one PSTN voicemail server <b>418</b> in <figref idref="DRAWINGS">FIG. 4</figref>, this is a nonlimiting example. More specifically, in at least one exemplary embodiment, the converter <b>414</b> (and/or the SIP locator <b>416</b>) may be configured to provide services to a plurality of PSTN voicemail servers. While the plurality of PSTN voicemail servers may be associated with the same sub-network (see <figref idref="DRAWINGS">FIG. 3</figref>), this is not a requirement. More specifically, depending on the particular embodiment, the converter <b>414</b> (and/or the SIP locator <b>416</b>) may be configured to provide services to one or more different PSTN voicemail servers associated with a plurality sub-networks. As such, depending on the particular configuration, the converter <b>414</b> (and/or the SIP locator <b>416</b>) may be configured to communicate to the PSTN voicemail servers via one or more different protocols. Other exemplary embodiments may include an external database that could be used to look-up a mapping between the PSTN address of the called party to an IP based address. Such a configuration may include, for example, Telephone Number Mapping (ENUM) or Lightweight Directory Access Protocol (LDAP) type of database.

0049<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating an exemplary embodiment of a converter that may be configured to communicate via a communications network such as the network from <figref idref="DRAWINGS">FIG. 4</figref>. Although a wire-line communications device is illustrated, this discussion can be applied to wireless devices, as well. Generally, in terms of hardware architecture, as shown in <figref idref="DRAWINGS">FIG. 5</figref>, the converter <b>414</b> includes a processor <b>582</b>, volatile and nonvolatile memory <b>584</b>, a display interface <b>594</b>, data storage <b>595</b>, one or more input and/or output (I/O) device interface(s) <b>596</b>, and/or one or more network interfaces <b>598</b> that are communicatively coupled via a local interface <b>592</b>. The local interface <b>592</b> can include, for example but not limited to, one or more buses or other wired or wireless connections. The local interface <b>592</b> may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. The processor <b>582</b> may be a device for executing software, particularly software stored in volatile and nonvolatile memory <b>584</b>. The processor <b>582</b> can include any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the communications device <b>106</b>, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, and/or generally any device for executing software instructions.

0050The volatile and nonvolatile memory <b>584</b> can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and/or nonvolatile memory elements (e.g., ROM, hard drive, tape, CDROM, etc.). Moreover, the memory <b>584</b> may incorporate electronic, magnetic, optical, and/or other types of storage media. One should note that the volatile and nonvolatile memory <b>584</b> can have a distributed architecture (where various components are situated remote from one another), but can be accessed by the processor <b>582</b>.

0051The software in volatile and nonvolatile memory <b>584</b> may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example of <figref idref="DRAWINGS">FIG. 5</figref>, the software in the volatile and nonvolatile memory <b>584</b> may include conversion logic <b>599</b>, as well as operating system <b>586</b>. The operating system <b>586</b> may be configured to control the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services.

0052A system component and/or module embodied as software may also be construed as a source program, executable program (object code), script, or any other entity comprising a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the volatile and nonvolatile memory <b>584</b>, so as to operate properly in connection with the operating system <b>586</b>.

0053The Input/Output devices that may be coupled to system I/O Interface(s) <b>596</b> may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, etc. Further, the Input/Output devices may also include output devices, for example but not limited to, a printer, display, speaker, etc. Finally, the Input/Output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem; for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, etc.

0054Additionally included are one or more network interfaces <b>598</b> for facilitating communication with one or more other devices. More specifically, the network interface <b>598</b> may include any component configured to facilitate a connection with another device. While in some embodiments, among others, the converter <b>414</b> can include the network interface <b>598</b> that includes a Personal Computer Memory Card International Association (PCMCIA) card (also abbreviated as “PC card”) for receiving a wireless network card, however this is a nonlimiting example. Other configurations can include the communications hardware within the computing device, such that a wireless network card is unnecessary for communicating wirelessly. Similarly, other embodiments include the network interface <b>598</b> for communicating via a wired connection. Such interfaces may be configured with Universal Serial Bus (USB) interfaces, serial ports, and/or other interfaces.

0055If the converter <b>414</b> includes a personal computer, workstation, or the like, the software in the volatile and nonvolatile memory <b>584</b> may further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of software routines that initialize and test hardware at startup, start the operating system <b>586</b>, and support the transfer of data among the hardware devices. The BIOS is stored in ROM so that the BIOS can be executed when the communications device <b>106</b> is activated.

0056When the converter <b>414</b> is in operation, the processor <b>582</b> may be configured to execute software stored within the volatile and nonvolatile memory <b>584</b>, to communicate data to and from the volatile and nonvolatile memory <b>584</b>, and to generally control operations of the communications device <b>106</b> pursuant to the software. Software in memory, in whole or in part, may be read by the processor <b>582</b>, perhaps buffered within the processor <b>582</b>, and then executed.

0057One should note that while the description with respect to <figref idref="DRAWINGS">FIG. 5</figref> includes the converter <b>414</b> as a single component, this is a nonlimiting example. More specifically, in at least one embodiment, the converter <b>414</b> can include a plurality of servers, personal computers, and/or other devices. Similarly, while the description of <figref idref="DRAWINGS">FIG. 5</figref> describes the converter <b>414</b>, this is also a nonlimiting example, as other components may also be included in this description, such as SIP locator and/or other components.

0058Additionally, while the conversion logic <b>599</b> is illustrated in <figref idref="DRAWINGS">FIG. 5</figref> as a single software component, this is also a nonlimiting example. In at least one embodiment, the conversion logic <b>599</b> may include one or more components, embodied in software, hardware, and/or firmware. Additionally, while the conversion logic <b>599</b> is depicted as residing on a single computing device, as converter <b>414</b> may include one or more devices, the conversion logic <b>599</b> may include one or more components residing on one or more different devices.

0059The embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment disclosed herein is implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, as in an alternative embodiment, embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

0060<figref idref="DRAWINGS">FIG. 6</figref> is an exemplary embodiment of a sequence diagram illustrating a process for providing a message waiting indicator signal to a communications device such as a communications device in <figref idref="DRAWINGS">FIG. 4</figref>. As illustrated in this nonlimiting example, a caller can initiate a communication from caller communications device to a communications network such as the PSTN <b>202</b> (Arrow <b>632</b>). The communications network can then send the communications request to a called party communications device such as the communications device <b>102</b><i>a</i>. After a predetermined amount of time (e.g., a predetermined number of rings and/or predetermined time limit), the communications network may determine that a user is currently unavailable at the communications device <b>102</b><i>a </i>(Arrow <b>634</b>). The communications network can then send the communications request to a voicemail server, such as the PSTN based voicemail server <b>418</b> (Arrow <b>636</b>). The PSTN voicemail server <b>418</b> can then record a message from the caller (Arrow <b>638</b>). The voicemail server <b>418</b> can send a message waiting indicator signal to the communications device <b>102</b><i>a </i>(Arrow <b>640</b>). At this point, a message waiting indicator will be activated for display at the user's communications device <b>102</b><i>a. </i>

0061If the user of the communications device <b>102</b><i>a </i>decides to access the voicemail server <b>418</b> (via the communications device <b>102</b><i>a </i>and/or other communications devices), the user may input a predetermined address for accessing his or her account on the PSTN based voicemail server <b>418</b>. Upon accessing the user's account at the PSTN based voicemail server <b>418</b>, the user can retrieve messages stored by the PSTN based voicemail server (Arrow <b>642</b>). Upon retrieving his or her messages, the voicemail server <b>418</b> can send a message waiting indicator signal to the communications device <b>102</b><i>a </i>(Arrow <b>644</b>) to provide indication to the users that no messages are currently waiting.

0062One should note that although the embodiments of <figref idref="DRAWINGS">FIG. 6</figref> indicate that the message waiting indicator signal is sent only to a single communications device, this is a nonlimiting example. One should note that in at least one embodiment, a message waiting indicator signal can be sent to one or more communications devices at one or more addresses (e.g., the message waiting indicator signal can be sent to a plurality of different telephone numbers, IP addresses, etc.). Similarly, a message waiting indicator signal can be provided to other types of communications devices via e-mail accounts, instant messaging accounts, and/or other communications media.

0063<figref idref="DRAWINGS">FIG. 7A</figref> is an exemplary embodiment of a sequence diagram for providing a message waiting indicator signal for an IP based voicemail server, similar to the sequence diagram from <figref idref="DRAWINGS">FIG. 6</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 7A</figref>, a caller initiates communication from caller communications device <b>102</b><i>d </i>(Arrow <b>746</b>). The IP network <b>204</b> receives the communication request and sends the communication request to a called party communications device <b>104</b><i>a</i>. If the IP network <b>204</b> determines that the user is currently unavailable at the communications device <b>104</b><i>a</i>, the call is forwarded from the communications network <b>204</b> to the IP based voicemail server <b>424</b> (Arrow <b>750</b>). The IP voicemail server <b>424</b> can then record a voicemail message (Arrow <b>752</b>). The voicemail server <b>424</b> can then send a SIP message waiting indicator signal to a terminal server <b>422</b> (Arrow <b>754</b>). The terminal server <b>422</b> can then convert the SIP message waiting indicator signal to an SMDI message (and/or other PSTN based protocol) and can send the SMDI message to the PSTN based communications device <b>102</b><i>a </i>(Arrow <b>756</b>).

0064<figref idref="DRAWINGS">FIG. 7B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 7A</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 7B</figref>, a user may then retrieve his or her messages at the IP voicemail server <b>424</b> (via the communications device <b>104</b><i>d </i>and/or other communications devices) as illustrated with Arrow <b>658</b>. Upon providing messages to the user, the voicemail server <b>424</b> can send a SIP message waiting indicator signal to the terminal server <b>422</b> (Arrow <b>760</b>) for indicating that there are currently no messages awaiting retrieval. The terminal server <b>422</b> can convert the SIP message into a PSTN based protocol (e.g., SMDI, SS7, etc.) and can send the converted message waiting indicator signal to the communications device <b>102</b><i>d </i>(Arrow <b>762</b>).

0065<figref idref="DRAWINGS">FIG. 8A</figref> is an exemplary embodiment of sequence diagram for providing the message waiting indicator signal to an IP based communications device via a PSTN voicemail server, similar to the sequence diagram from <figref idref="DRAWINGS">FIGS. 7A and 7B</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 8A</figref>, a caller communications device initiates a communication request for an IP called party communications device via communications network such as the PSTN <b>202</b> (Arrow <b>832</b>). The PSTN <b>202</b> can receive the communications request and send the communications request to an IP communications device such as the communications device <b>104</b><i>b</i>. If the PSTN <b>202</b> determines that a user is not currently available at the user device <b>104</b><i>b </i>(Arrow <b>834</b>), the PSTN <b>202</b> can forward the communication request to the voicemail server <b>418</b> (Arrow <b>836</b>). The PSTN voicemail server <b>418</b> then can prompt the caller to leave a voice message (Arrow <b>838</b>). The PSTN based voicemail server <b>418</b> can then send a message waiting indicator signal (via SMDI and/or other protocols) to converter <b>414</b> (Arrow <b>840</b>). The converter <b>414</b> can send an address associated with the called party device <b>104</b><i>b </i>(e.g., a phone number) to the SIP locator <b>416</b> (Arrow <b>842</b>).

0066<figref idref="DRAWINGS">FIG. 8B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 8A</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 8B</figref>, the SIP locator <b>416</b> can return a URI and/or other address associated with called party device <b>104</b><i>b </i>for which the message was left (Arrow <b>844</b>). The SIP locator <b>416</b> can then send the address (e.g., URI, URL, IP address, and/or other identifier) to the converter <b>414</b> (Arrow <b>846</b>). The controller <b>414</b> can then convert the received PSTN based waiting indicator signal to SIP and/or other IP based protocol. The converter <b>414</b> can then send the converted message waiting indicator signal to the communications device <b>104</b><i>b </i>via the IP network <b>204</b> (Arrow <b>848</b>).

0067At this point, as indicated above, user of the communications device <b>104</b><i>b </i>may be alerted that a message is waiting via a message indicator on the communications device <b>104</b><i>b</i>. The user may access the awaiting messages at the PSTN based voicemail server <b>418</b> via the communications device <b>104</b><i>b </i>and/or other communications device (Arrow <b>850</b>). The PSTN based voicemail server <b>418</b> can then send a PSTN based message waiting indicator signal (e.g., SMDI and/or other protocol) to the converter <b>414</b> (Arrow <b>852</b>) to turn a message waiting indicator “off.”

0068<figref idref="DRAWINGS">FIG. 8C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 8B</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 8C</figref>, SIP locator <b>416</b> can determine an address (e.g., URI, URL, URN, IP address, etc.) as shown with Arrow <b>854</b>. In the present example, a URI is determined. The SIP locator <b>416</b> can then send the determined identifier to the converter <b>414</b> (Arrow <b>856</b>). The converter <b>414</b> may convert the received PSTN based (e.g., SMDI) message waiting indicator signal to a SIP and/or other protocol. The converter <b>416</b> can then send the converted message waiting indicator signal to communications device <b>104</b><i>b </i>(Arrow <b>858</b>).

0069<figref idref="DRAWINGS">FIG. 9A</figref> is an exemplary embodiment of a sequence diagram for providing a message waiting indicator signal to a user of an IP based communications device via a wireless and IP network, similar to the sequence diagrams from <figref idref="DRAWINGS">FIGS. 8A</figref>, <b>8</b>B, and <b>8</b>C. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 9A</figref>, a caller can initiate a communications request (Arrow <b>932</b>). The communications request can be received via the PSTN network <b>202</b>. The PSTN network <b>202</b> can send the communication request to a dual mode WIFI handset such as communications device <b>106</b> from <figref idref="DRAWINGS">FIG. 4</figref> (Arrow <b>934</b>). If a determination is made that a user is currently unavailable at communications device <b>106</b>, the PSTN network <b>202</b> can forward the communications request to the PSTN based voicemail server <b>418</b> (Arrow <b>936</b>). The PSTN based voicemail server <b>418</b> can prompt the user to provide a voice message and record the received voice message (Arrow <b>938</b>). The PSTN based voicemail server <b>418</b> can then send a message waiting indicator signal in a PSTN protocol such as SMDI to the converter <b>414</b> (Arrow <b>940</b>). The converter <b>414</b> can send a phone number and/or other address to SIP locator <b>416</b> to determine a URI and/or other IP based indicator signal associated with the caller communications device (Arrow <b>942</b>).

0070<figref idref="DRAWINGS">FIG. 9B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 9A</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 9B</figref>, SIP locator may determine a URI and/or other IP based identifier of the caller device <b>106</b> (Arrow <b>944</b>). The SIP locator <b>416</b> can then send the retrieved URI to the converter <b>414</b> (Arrow <b>946</b>). The converter <b>414</b> may convert the received SMDI message waiting indicator signal to an IP based protocol such as SIP. The converter <b>414</b> may then send the converted message to the communications device <b>106</b> (Arrow <b>948</b>). As previously indicated, a message waiting indicator signal may be provided to the communications device <b>106</b>.

0071If a user determines that messages might be waiting at the PSTN based voicemail server <b>418</b>, the user can check the voicemail from the communications device <b>106</b> and/or other communications devices (Arrow <b>950</b>). Upon retrieving the user's message, the PSTN based voicemail server <b>418</b> can send a message waiting indicator signal via a PSTN based protocol such as SMDI to converter <b>414</b> (Arrow <b>952</b>) to indicate that no messages are currently waiting.

0072<figref idref="DRAWINGS">FIG. 9C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIGS. 9A and 9B</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 9C</figref>, the converter <b>414</b> can send a phone number and/or other PSTN based identifier of the caller communications device to the SIP locator <b>416</b> (Arrow <b>954</b>). The SIP locator <b>416</b> can then determine the IP based indicator such as a URI associated with the caller communications device <b>106</b> (Arrow <b>956</b>). The SIP locator can then send the IP based identifier such as a URI to the converter <b>414</b> (Arrow <b>958</b>). The converter <b>414</b> may then convert the received SMDI message waiting indicator signal to an IP based protocol such as SIP. The converter <b>414</b> can then send the converted message waiting indicator signal to the communications device <b>106</b> via IP network <b>204</b> (Arrow <b>960</b>) to turn a message waiting indicator “off.”

0073<figref idref="DRAWINGS">FIG. 10A</figref> is an exemplary embodiment of a sequence diagram for providing a PSTN voicemail message waiting indicator signal to a dual mode handset that is Internet Protocol (IP) mode, similar to the sequence diagram from <figref idref="DRAWINGS">FIGS. 9A</figref>, <b>9</b>B, and <b>9</b>C. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 10A</figref>, a caller may initiate communications request for a called party on a dual mode handset such as the communications device <b>106</b> (Arrow <b>1030</b>). The communications request can be received by the IP communications network <b>204</b> which may then send the received communication request to the dual mode called party communications device <b>106</b> (Arrow <b>1032</b>). If a determination is made that the called party is currently unavailable at the communications device <b>106</b>, the IP communications network <b>204</b> can forward the communication request to the PSTN based voicemail server <b>418</b> (Arrow <b>1034</b>).

0074The PSTN based voicemail server <b>418</b> can receive and record a message from the caller (Arrow <b>1036</b>). The PSTN based voicemail server can send a message waiting indicator signal via an SS7 based protocol to the wireless network <b>206</b> (Arrow <b>1038</b>) to the Dual Mode Handset device <b>106</b> (called party device). The wireless network determines whether the Dual Mode handset is in IP mode, and if so, the wireless network sends a wireless MWI message to the converter (Arrow <b>1039</b>). The converter <b>414</b> can receive the message waiting indicator signal from the wireless network <b>206</b>. The converter <b>414</b> sends the received identifier to SIP locator <b>416</b> (Arrow <b>1040</b>). One should note that while the above description describes an exemplary embodiment where the wireless network <b>206</b> determines a dual handset mode, this is a nonlimiting example. More specifically, in at least one exemplary embodiment, the wireless network <b>206</b> may be configured to send a message waiting indicator to the wireless device <b>106</b> and converter <b>414</b>, simultaneously.

0075<figref idref="DRAWINGS">FIG. 10B</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIG. 10A</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 10B</figref>, the SIP locator <b>416</b> determines an IP based identifier associated with the called party communications device such as a URI (Arrow <b>1044</b>). The SIP locator <b>416</b> can then send the determined IP based identifier to the converter <b>414</b> (Arrow <b>1046</b>). The converter <b>414</b> can then convert the message waiting indicator signal to an IP based protocol such as SIP. The converter can then send the converted message waiting indicator signal to the communications device via the IP network <b>204</b> (Arrow <b>1048</b>). At this point, a message waiting indicator signal may be provided to a user of the communications device <b>106</b>. The user may then check for voice messages at the PSTN based voicemail server <b>418</b> via a communications device such as the communications device <b>106</b>, the communications device <b>104</b>, and/or the communications device <b>102</b> (Arrow <b>1050</b>).

0076<figref idref="DRAWINGS">FIG. 10C</figref> is a continuation of the sequence diagram from <figref idref="DRAWINGS">FIGS. 10A and 10B</figref>. As illustrated in the nonlimiting example of <figref idref="DRAWINGS">FIG. 10C</figref>, the PSTN based voicemail server <b>418</b> can then send a message waiting indicator to turn a message waiting indicator “off” (Arrow <b>1052</b>). The wireless network may be configured to determine that the Dual Mode Handset is in an IP mode, so the wireless network can send a wireless MWI OFF message to converter <b>414</b> (Arrow <b>1053</b>). The converter <b>414</b> can send the message waiting indicator signal and associated caller device identifiers (e.g., phone number) to the SIP locator <b>416</b> (Arrow <b>1054</b>). The SIP locator <b>416</b> can then determine an IP based identifier associated with the caller communications device <b>106</b> (Arrow <b>1056</b>). The SIP locator can then send and receive the determined identifier to the converter <b>414</b> (Arrow <b>1058</b>). The converter <b>414</b> can then convert the received message waiting indicator signal to a SIP and/or other IP based protocol. The converter <b>414</b> can then send the converted message waiting indicator signal to the communications device <b>106</b> via the IP network <b>204</b> (Arrow <b>1060</b>).

0077One should note that the flowcharts included herein show the architecture, functionality, and operation of a possible implementation of software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.

0078One should note that any of the programs listed herein, which can include an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.

0079One should also note that conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more particular embodiments or that one or more particular embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.

0080It should be emphasized that the above-described embodiments are merely possible examples of implementations, merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure.