WO2009081319A1

WO2009081319A1 - Missed call interpretation service

Info

Publication number: WO2009081319A1
Application number: PCT/IB2008/055278
Authority: WO
Inventors: Adrish Bera; Ramesh B. Satagopan
Original assignee: Nokia Inc
Current assignee: Nokia Inc
Priority date: 2007-12-19
Filing date: 2008-12-12
Publication date: 2009-07-02
Anticipated expiration: 2010-06-19

Abstract

An apparatus for enabling missed call interpretation may include a processor. The processor may be configured to provide an association of a predefined missed call characteristic with corresponding message information and, in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, provide the corresponding message information.

Description

MISSED CALL INTERPRETATION SERVICE

TECHNOLOGICAL FIELD

Embodiments of the present invention relate generally to communication technology and, more particularly, relate to a method, apparatus and computer program product for providing a mechanism for interpreting missed calls.

BACKGROUND

The modern communications era has brought about a tremendous expansion of wireline and wireless networks. Computer networks, television networks, and telephony networks are experiencing an unprecedented technological expansion, fueled by consumer demand. Wireless and mobile networking technologies have addressed related consumer demands, while providing more flexibility and immediacy of information transfer.

Current and future networking technologies continue to facilitate ease of information transfer and convenience to users by expanding the capabilities of mobile electronic devices with respect to communicating with one another. Due to the ubiquitous nature of mobile communication devices, people all over the world and of all walks of life are now utilizing mobile terminals to communicate with other individuals, entities or contacts and/or to share or consume information, media and other content. Accordingly, mobile communication devices have been developed to enhance a user's ability to participate in emails, phone calls, text messaging, push-to-talk and other mechanisms for communication.

One mechanism for communication that has been developed recently involves the use of missed calls. Missed calls are typically indicated by alerts that show that an incoming call was received, but not answered (and also not transferred to voicemail). There is typically no charge for a missed call, since the call is not answered. Accordingly, some individuals, and indeed some cultures, have begun to utilize missed calls as a mechanism for communication of implicit messages or presence information. For example, a missed call could indicate an implicit desire to be called back, or that the caller is thinking of the called party. Additionally, missed calls may have pre-arranged meanings agreed to between the parties, such as where one person tells another that they will send a missed call when a particular destination is reached. However, since missed call communication currently requires pre-arranged communication or merely enables implicit communication, missed call communication may be considered to be a very limited mechanism for communication.

In order to provide for an improved communication capability with respect to missed call communication having the limitations described above, it may be desirable to provide an improved mechanism by which missed calls may be interpreted.

BRIEF SUMMARY A method, apparatus and computer program product are therefore provided to enable improved missed call communication capabilities. In particular, a method, apparatus and computer program product are provided that may enable a missed call interpretation service. In this regard, a missed call interpretation service may enable receipt of missed call information (e.g., a message to be associated with a particular missed call), which may be distributed to a receiver of the particular missed call. As a result, for example, mobile terminal users may enjoy an improved communication capability with respect to missed calls.

In one exemplary embodiment, a method of enabling missed call interpretation is provided. The method may include associating a predefined missed call characteristic with corresponding message information and, in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, providing the corresponding message information.

In another exemplary embodiment, a computer program product for enabling missed call interpretation is provided. The computer program product includes at least one computer-readable storage medium having computer-readable program code portions stored therein. The computer-readable program code portions include first and second executable portions. The first executable portion is for associating a predefined missed call characteristic with corresponding message information. The second executable portion is for, in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, providing the corresponding message information.

In another exemplary embodiment, an apparatus for enabling missed call interpretation is provided. The apparatus may include a processor configured to associate a predefined missed call characteristic with corresponding message information and, in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, provide the corresponding message information.

In another exemplary embodiment, an apparatus for enabling missed call interpretation is provided. The apparatus may include a processor configured to enable a calling party to define a service account, and provide an association of a predefined missed call characteristic with corresponding message information for communication to a network device managing the service account to enable provision of the corresponding message information to a receiver of a missed call in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic from the receiver.

In another exemplary embodiment, an apparatus for enabling missed call interpretation is provided. The apparatus may include a processor configured to enable a party receiving a missed call to access a network device storing an association of a predefined missed call characteristic with corresponding message information, provide missed call criteria to the network device, and receive the corresponding message information in response to a characteristic of the missed call criteria matching the predefined missed call characteristic.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S) Having thus described embodiments of the invention in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a schematic block diagram of a mobile terminal according to an exemplary embodiment of the present invention; FIG. 2 is a schematic block diagram of a wireless communications system according to an exemplary embodiment of the present invention;

FIG. 3 illustrates a block diagram of portions of a system for enabling missed call interpretation according to an exemplary embodiment of the present invention; FIG. 4 illustrates an exemplary architecture of a missed call interpretation server according to an exemplary embodiment of the present invention;

FIG. 5 illustrates an exemplary architecture of a missed call interpretation client according to an exemplary embodiment of the present invention; FIG. 6 illustrates a control flow diagram showing a message retrieval sequence according to an exemplary embodiment of the present invention;

FIG. 7 illustrates a control flow diagram showing a message upload sequence according to an exemplary embodiment of the present invention; and

FIG. 8 is a flow diagram according to an exemplary method for enabling missed call interpretation according to an exemplary embodiment of the present invention.

DETAILED DESCRIPTION

Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout.

FIG. 1, one aspect of the invention, illustrates a block diagram of a mobile terminal 10 that may benefit from embodiments of the present invention. It should be understood, however, that a mobile telephone as illustrated and hereinafter described is merely illustrative of one type of electronic device that may benefit from embodiments of the present invention and, therefore, should not be taken to limit the scope of embodiments of the present invention. While several embodiments of the mobile terminal 10 are illustrated and will be hereinafter described for purposes of example, other types of mobile terminals, such as portable digital assistants (PDAs), pagers, mobile televisions, gaming devices, laptop computers, cameras, video recorders, audio/video player, radio, GPS devices, tablets, internet capable devices, or any combination of the aforementioned, and other types of voice and text communications systems, can readily employ embodiments of the present invention.

In addition, while several embodiments of the method of the present invention are performed or used by a mobile terminal 10, the method may be employed by other than a mobile terminal. Moreover, the system and method of embodiments of the present invention will be primarily described in conjunction with mobile communications applications. It should be understood, however, that the system and method of embodiments of the present invention can be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries.

The mobile terminal 10 includes an antenna 12 (or multiple antennae) in operable communication with a transmitter 14 and a receiver 16. The mobile terminal 10 further includes an apparatus, such as a controller 20 or other processing element, that provides signals to and receives signals from the transmitter 14 and receiver 16, respectively. The signals include signaling information in accordance with the air interface standard of the applicable cellular system, and also user speech, received data and/or user generated data. In this regard, the mobile terminal 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the mobile terminal 10 may be capable of operating in accordance with any of a number of first, second, third and/or fourth-generation communication protocols or the like. For example, the mobile terminal 10 may be capable of operating in accordance with second-generation (2G) wireless communication protocols IS- 136 (time division multiple access (TDMA)), GSM (global system for mobile communication), and IS-95 (code division multiple access (CDMA)), or with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), with fourth-generation (4G) wireless communication protocols or the like.

It should be understood that the apparatus such as the controller 20 includes circuitry desirable for implementing audio and logic functions of the mobile terminal 10. For example, the controller 20 may be comprised of a digital signal processor device, a microprocessor device, and various analog to digital converters, digital to analog converters, and other support circuits. Control and signal processing functions of the mobile terminal 10 are allocated between these devices according to their respective capabilities. The controller 20 thus may also include the functionality to convolutionally encode and interleave message and data prior to modulation and transmission. The controller 20 may additionally include an internal voice coder, and may include an internal data modem. Further, the controller 20 may include functionality to operate one or more software programs, which may be stored in memory. For example, the controller 20 may be capable of operating a connectivity program, such as a conventional Web browser. The connectivity program may then allow the mobile terminal 10 to transmit and receive Web content, such as location-based content and/or other web page content, according to a Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP) and/or the like, for example.

The mobile terminal 10 may also comprise a user interface including an output device such as a conventional earphone or speaker 24, a ringer 22, a microphone 26, a display 28, and a user input interface, all of which are coupled to the controller 20. The user input interface, which allows the mobile terminal 10 to receive data, may include any of a number of devices allowing the mobile terminal 10 to receive data, such as a keypad 30, a touch display (not shown) or other input device. In embodiments including the keypad 30, the keypad 30 may include the conventional numeric (0-9) and related keys (#, *), and other hard and soft keys used for operating the mobile terminal 10. Alternatively, the keypad 30 may include a conventional QWERTY keypad arrangement. The keypad 30 may also include various soft keys with associated functions. In addition, or alternatively, the mobile terminal 10 may include an interface device such as a joystick, scrolling device or other user input interface. The mobile terminal 10 may further include a battery 34, such as a vibrating battery pack, for powering various circuits that are required to operate the mobile terminal 10, as well as optionally providing mechanical vibration as a detectable output.

The mobile terminal 10 may further include a user identity module (UIM) 38. The UIM 38 is typically a memory device having a processor built in. The UIM 38 may include, for example, a subscriber identity module (SIM), a universal integrated circuit card (UICC), a universal subscriber identity module (USIM), a removable user identity module (R-UIM), etc. The UIM 38 typically stores information elements related to a mobile subscriber. In addition to the UIM 38, the mobile terminal 10 may be equipped with memory. For example, the mobile terminal 10 may include volatile memory 40, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data. The mobile terminal 10 may also include other non- volatile memory 42, which can be embedded and/or may be removable. The non- volatile memory 42 may additionally or alternatively comprise an electrically erasable programmable read only memory (EEPROM), flash memory or the like, such as that available from the SanDisk Corporation of Sunnyvale, California, or Lexar Media Inc. of Fremont, California. The memories can store any of a number of pieces of information, and data, used by the mobile terminal 10 to implement the functions of the mobile terminal 10. For example, the memories can include an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying the mobile terminal 10. Furthermore, the memories may store instructions for determining cell id information. Specifically, the memories may store an application program for execution by the controller 20, which determines an identity of the current cell, i.e., cell id identity or cell id information, with which the mobile terminal 10 is in communication.

FIG. 2 is a schematic block diagram of a wireless communications system according to an exemplary embodiment of the present invention. Referring now to FIG. 2, an illustration of one type of system that may benefit from embodiments of the present invention is provided. The system includes a plurality of network devices. As shown, one or more mobile terminals 10 may each include an antenna 12 for transmitting signals to and for receiving signals from a base site or base station (BS) 44. The base station 44 may be a part of one or more cellular or mobile networks each of which includes elements required to operate the network, such as a mobile switching center (MSC) 46. As well known to those skilled in the art, the mobile network may also be referred to as a Base Station/MSC/Interworking function (BMI). In operation, the MSC 46 may be capable of routing calls to and from the mobile terminal 10 when the mobile terminal 10 is making and receiving calls. The MSC 46 may also provide a connection to landline trunks when the mobile terminal 10 is involved in a call. In addition, the MSC 46 may be capable of controlling the forwarding of messages to and from the mobile terminal 10, and may also control the forwarding of messages for the mobile terminal 10 to and from a messaging center. It should be noted that although the MSC 46 is shown in the system of FIG. 2, the MSC 46 is merely an exemplary network device and embodiments of the present invention are not limited to use in a network employing an MSC.

The MSC 46 may be coupled to a data network, such as a local area network (LAN), a metropolitan area network (MAN), and/or a wide area network (WAN). The MSC 46 may be directly coupled to the data network. In one typical embodiment, however, the MSC 46 is coupled to a gateway device (GTW) 48, and the GTW 48 is coupled to a WAN, such as the Internet 50. In turn, devices such as processing elements (e.g., personal computers, server computers or the like) may be coupled to the mobile terminal 10 via the Internet 50. For example, as explained below, the processing elements may include one or more processing elements associated with a computing system 52 (two shown in FIG. 2), origin server 54 (one shown in FIG. 2) or the like, as described below. The BS 44 may also be coupled to a serving GPRS (General Packet Radio Service) support node (SGSN) 56. As known to those skilled in the art, the SGSN 56 is typically capable of performing functions similar to the MSC 46 for packet switched services. The SGSN 56, like the MSC 46, may be coupled to a data network, such as the Internet 50. The SGSN 56 may be directly coupled to the data network. In a more typical embodiment, however, the SGSN 56 may be coupled to a packet-switched core network, such as a GPRS core network 58. The packet-switched core network may then be coupled to another GTW 48, such as a gateway GPRS support node (GGSN) 60, and the GGSN 60 may be coupled to the Internet 50. In addition to the GGSN 60, the packet-switched core network may also be coupled to a GTW 48. Also, the GGSN 60 may be coupled to a messaging center. In this regard, the GGSN 60 and the SGSN 56, like the MSC 46, may be capable of controlling the forwarding of messages, such as MMS messages. The GGSN 60 and SGSN 56 may also be capable of controlling the forwarding of messages for the mobile terminal 10 to and from the messaging center. In addition, by coupling the SGSN 56 to the GPRS core network 58 and the GGSN

60, devices such as a computing system 52 and/or origin server 54 may be coupled to the mobile terminal 10 via the Internet 50, SGSN 56 and GGSN 60. In this regard, devices such as the computing system 52 and/or origin server 54 may communicate with the mobile terminal 10 across the SGSN 56, GPRS core network 58 and the GGSN 60. By directly or indirectly connecting mobile terminals 10 and the other devices (e.g., computing system 52, origin server 54, etc.) to the Internet 50, the mobile terminals 10 may communicate with the other devices and with one another, such as according to the Hypertext Transfer Protocol (HTTP) and/or the like, to thereby carry out various functions of the mobile terminals 10. Although not every element of every possible mobile network is shown and described herein, it should be appreciated that the mobile terminal 10 may be coupled to one or more of any of a number of different networks through the BS 44. In this regard, the network(s) may be capable of supporting communication in accordance with any one or more of a number of first-generation (IG), second-generation (2G), 2.5G, third- generation (3G), 3.9G, fourth-generation (4G) mobile communication protocols or the like. For example, one or more of the network(s) may be capable of supporting communication in accordance with 2G wireless communication protocols IS-136 (TDMA), GSM, and IS-95 (CDMA). Also, for example, one or more of the network(s) may be capable of supporting communication in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), or the like. Further, for example, one or more of the network(s) may be capable of supporting communication in accordance with 3 G wireless communication protocols such as a UMTS network employing WCDMA radio access technology. Some narrow-band analog mobile phone service (NAMPS), as well as total access communication system (TACS), network(s) may also benefit from embodiments of the present invention, as should dual or higher mode mobile stations (e.g., digital/analog or TDMA/CDMA/analog phones).

The mobile terminal 10 may further be coupled to one or more wireless access points (APs) 62. The APs 62 may comprise access points configured to communicate with the mobile terminal 10 in accordance with techniques such as, for example, radio frequency (RF), infrared (IrDA) or any of a number of different wireless networking techniques, including wireless LAN (WLAN) techniques such as IEEE 802.11 (e.g., 802.1 Ia, 802.1 Ib, 802.1 Ig, 802.1 In, etc.), world interoperability for microwave access (WiMAX) techniques such as IEEE 802.16, and/or wireless Personal Area Network (WPAN) techniques such as IEEE 802.15, Bluetooth™ (BT) brand wireless technology developed by the Bluetooth™ Special Interest Group, Wibree™ radio standards, Wi-Fi, ultra wideband (UWB) and/or the like. The APs 62 may be coupled to the Internet 50. Like with the MSC 46, the APs 62 may be directly coupled to the Internet 50. In one embodiment, however, the APs 62 are indirectly coupled to the Internet 50 via a GTW 48. Furthermore, in one embodiment, the BS 44 may be considered as another AP 62. As will be appreciated, by directly or indirectly connecting the mobile terminals 10 and the computing system 52, the origin server 54, and/or any of a number of other devices, to the Internet 50, the mobile terminals 10 may communicate with one another, the computing system, etc., to thereby carry out various functions of the mobile terminals 10, such as to transmit data, content or the like to, and/or receive content, data or the like from, the computing system 52. As used herein, the terms "data," "content," "information" and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

Although not shown in FIG. 2, in addition to or in lieu of coupling the mobile terminal 10 to computing systems 52 across the Internet 50, the mobile terminal 10 and computing system 52 may be coupled to one another and communicate in accordance with, for example, RF, BT, IrDA or any of a number of different wireline or wireless communication techniques, including LAN, WLAN, WiMAX, UWB techniques and/or the like. One or more of the computing systems 52 may additionally, or alternatively, include a removable memory capable of storing content, which may thereafter be transferred to the mobile terminal 10. Further, the mobile terminal 10 may be coupled to one or more electronic devices, such as printers, digital projectors and/or other multimedia capturing, producing and/or storing devices (e.g., other terminals). Like with the computing systems 52, the mobile terminal 10 may be configured to communicate with the portable electronic devices in accordance with techniques such as, for example, RF, BT, IrDA or any of a number of different wireline or wireless communication techniques, including universal serial bus (USB), LAN, WLAN, WiMAX, UWB techniques and/or the like.

In an exemplary embodiment, content or data may be communicated over the system of FIG. 2 between a mobile terminal, which may be similar to the mobile terminal 10 of FIG. 1, and a network device of the system of FIG. 2 in order to, for example, execute applications or establish communication (for example, for purposes of establishing a phone call or to acquire or share content) between the mobile terminal 10 and other mobile terminals or network devices. As such, it should be understood that the system of FIG. 2 need not be employed for communication between mobile terminals or between a network device and the mobile terminal, but rather FIG. 2 is merely provided for purposes of example. Furthermore, it should be understood that embodiments of the present invention may be resident on a communication device such as the mobile terminal 10, and/or may be resident on a server or other device, absent any communication with the system of FIG. 2.

An exemplary embodiment of the invention will now be described with reference to FIG. 3, in which certain elements of a system for enabling missed call interpretation are displayed. The system of FIG. 3 may be employed, for example, on one or more mobile terminals like the mobile terminal 10 of FIG. 1 and/or a server or network device of FIG. 2. However, it should be noted that the system of FIG. 3, may also be employed on a variety of other devices, both mobile and fixed, and therefore, the present invention should not be limited to application on devices such as the mobile terminal 10 of FIG. 1 or a server or network device of FIG. 2. It should also be noted that while FIG. 3 illustrates one example of a configuration of a system for enabling missed call interpretation, for example, in a mobile environment, numerous other configurations may also be used to implement embodiments of the present invention. As such, it should be noted that the devices or elements described below may not be mandatory and thus some may be omitted in certain embodiments.

Referring now to FIG. 3, a system for enabling missed call interpretation is provided. The system may include a combination of entities or devices that may be embodied in hardware, software or a combination of hardware and software for use in connection with embodiments of the present invention. In the context of the description provided below, a missed call should be understood to be an incoming call that was received, but not answered. More particularly, the missed call is neither answered by a human or machine entity. Accordingly, a call for which the user does not answer and thus the call is directed to voice mail is not a missed call within the context used herein. FIG. 3 illustrates a block diagram of a system 68 for providing missed call interpretation according to an exemplary embodiment of the present invention. In this regard, the system 68 may include a calling station 70 and a receiving station 72. Each of the calling and receiving stations 70 and 72 may be examples of the mobile terminal 10 in FIG. 1. The calling and receiving stations 70 and 72 may communicate with each other (and/or with other stations) via a communication system 74 (of which the system of FIG. 2 may be an example). In an exemplary embodiment, the communication system 74 may include a missed call interpretation server (MCIS) 76. The communication system 74 may, for example, enable GPRS communication and, as such, the communication system 74 may include a GPRS - Ethernet gateway to enable communication between the either the sending station 70 or the receiving station 72 and the MCIS 76. At least the receiving station 72 (and in some embodiments also the calling station 70) may include a missed call interpretation client (MCIC) 78. The MCIS 76 and the MCIC 78 may be utilized for missed call interpretation in accordance with embodiments of the present invention as described in greater detail below. In this regard, it should be understood that the embodiment of FIG. 3 illustrates a simple configuration in which a client-server communication is described and other configurations of a system for providing missed call interpretation may also be used to implement embodiments of the present invention.

Referring still to FIG. 3, each of the calling and receiving stations 70 and 72 may be enabled to act as a client with respect to the MCIS 76. In general, the MCIC 78 and/or the MCIS 76 may be any device or means embodied in either hardware, software, or a combination of hardware and software that is configured for performing client and/or server functions, respectively, of the MCIC 78 and the MCIS 76 as described herein. In this regard, the MCIC 78 and the MCIS 76 could each be similar to known client and server devices except that they employ additional functionality as described herein to enable functioning responsive to missed call interpretation. It should be noted that the MCIC 78 and/or the MCIS 76 need not necessarily be an actual device. Instead, the MCIC 78 and/or the MCIS 76 may each be comprised of an application operating at a particular device. For example, the MCIC 78 could be embodied as an application executed by the receiving station 72 (or the sending station 70) and the MCIS 76 could be embodied as an application executed by a server or network device of FIG. 2. However, alternatively, the MCIC 78 and the MCIS 76 could each be a client device and a server device, respectively. Additionally, in one embodiment, communications with the MCIS 76 by the calling party (e.g., the calling station 70) may not need to be accomplished via an MCIC 78, but may be conducted via, for example, a web interface, SMS interface, voice recognition interface, etc.

In addition to other elements, the sending and/or receiving stations 70 and 72 may include a processor 80 (e.g., the controller 20) or other processing element, a user interface element 82, a memory element 84 and a communication element 88. The user interface element 82 may include, for example, a keyboard, keypad, function keys, mouse, scrolling device, touch screen, or any other mechanism by which a user may interface with the client 70, for example, to provide a user input and/or provide an output to the user. The memory element 84 may include, for example, volatile or non-volatile memory. The memory element 84 may be configured to store information, data, applications, instructions or the like for enabling the sending and/or receiving stations 70 and 72 to carry out various functions in accordance with exemplary embodiments of the present invention. In this regard, for example, the memory element 84 may store a mobile operating system and/or an HTTP stack to facilitate communications with the MCIS 76, which may itself include an HTTP stack and a corresponding operating system. In some embodiments, the MCIS 76 may further include a web server application and/or a web interface.

The communication element 88 may be any device or means embodied in either hardware, software, or a combination of hardware and software, such as a transceiver or other communications interface, that is capable of conducting communications with other stations or devices, for example, via the communication system 74. In an exemplary embodiment, the communication element 88 may be configured to provide missed call interpretation to the MCIS 76 or retrieve missed call interpretation information from the MCIS 76, for example, in response to the execution of an action responsive to receipt of a user interface event via the user interface element 82.

The MCIC 78 may be controlled by or otherwise embodied as the processor 80. As such, the MCIC 78 may be any device or means embodied in hardware, software or a combination of hardware and software that is configured to communicate with the MCIS 76 to obtain missed call interpretation information from the MCIS 76 responsive to indications of a missed call. Thus, for example, if a missed call from the calling station 70 is received at the receiving station 72, the MCIC 78 of the receiving station 72 may be utilized to initiate communication with the MCIS 76 to obtain missed call interpretation information (or simply missed call information) associated with the missed call.

The MCIS 78 may include a processing element 90, a MCIS interpreter 92 and a server side communication element 94. The processing element 90 may control or otherwise perform functions associated with the MCIS interpreter 92 and/or the server side communication element 94. Processing elements as described herein may be embodied in many ways. For example, the processing element 90 and/or the processor 80 may be embodied as a processor, a coprocessor, a controller or various other processing means or devices including integrated circuits such as, for example, an ASIC (application specific integrated circuit) or an FPGA (field programmable gate array).

The server side communication element 94 may be any device or means embodied in either hardware, software, or a combination of hardware and software, such as a transceiver or other communications interface, that is capable of conducting communications with the calling and/or receiving stations 70 and 72, for example, via the communication system 74. In an exemplary embodiment, the server side communication element 94 may be configured to receive either a request for missed call information or the provision of message information for association or inclusion with the missed call information.

The MCIS interpreter 92 may be any device or means embodied in either hardware, software, or a combination of hardware and software, such as, for example, the processing element 90, which is configured to store missed call information for distribution under appropriate circumstances. In other words, the MCIS interpreter 92 may receive message information from a calling party (e.g., the calling station 70), a notification of a current state or most recent action performed at the client 70 for inclusion in missed call information that may be shared with a receiving party (e.g., the receiving station 72) when the receiving party receives a missed call from the calling party. In an exemplary embodiment, the MCIS interpreter 92 may include memory that may further include, for example, a MCIS interpretation table 98. The MCIS interpretation table 98 may store missed call information 100 such as CaIlID indicating who called to the receiving party (e.g., the mobile identification number (MIN) of the calling party (e.g., the calling station 70)), the time the missed call was made, the duration of the call (e.g., the number of rings), and/or message information that may be associated with the missed call. FIG. 4 illustrates an example of a possible architecture for the MCIS interpretation table 98. As shown in FIG. 4, updates to the MCIS interpretation table 98 may be accomplished via, for example, a MCIS web interface 104. In this regard, the MCIS web interface 104 may be a web interface application that enables a user (e.g., via a browser on a client device such as the calling station 70) to establish or modify a subscriber account associated with the user. As an alternative to the MCIS web interface 104, an SMS interface, voice recognition interface and/or the like may be employed to enable modifications to the subscriber account associated with the user. In an exemplary embodiment, establishment and/or modification of the subscriber account may be a free or fee based service. Missed call information may be read out of the MCIS interpretation table 98 via, for example, a web server application 106 that may be accessed by a client (e.g., by the MCIC 78 of the receiving station 72) after a missed call is received. In this regard, the callID of the calling party may be communicated (along with publicly available directory data) and the callID may inform the MCIS 76 which account (e.g., the account associated with the callID) to access for determining what message information to include with the missed call information 100 to be communicated to the receiving station 72 (e.g., via the MCIC 76). Accordingly, the missed call information 100, or at least the message portion thereof, may be displayed, presented or otherwise rendered to the client. By using the MCIS web interface 104, the user (e.g., user of the calling station 70) may define message information comprising particular text or even audio (e.g., prerecorded voice messages) or video messages to be associated with missed call information. In this regard, the user may define a plurality of different message information segments that may be assigned to be associated with missed call information in pre-defined circumstances. Thus, for example, the user's profile may define particular message information to be associated with missed calls to one or more particular receiving stations (as identified by the telephone number of a particular receiving station), during particular times (or dates) or for calls of a particular duration. Thus, as a more specific example, a missed call having one ring may be associated with message information stating "call me back", while a missed call to a loved one's telephone number may be associated with message information stating a message of endearment. Similarly, messages may be tailored to the time of day or the date. As another example, the user may define that a given number of missed calls within a predefined period may also be associated with particular message information. As such, it should be noted, that there is no requirement for the missed call information to include message information or for the calling party to provide such information. In this regard, for example, standard missed call behavior may be correlated to particular messages. For example, a certain number of rings or missed calls in a given time may be associated with a particular meaning. In other words, a particular missed call characteristic (e.g., who the sender is, who the receiver is, the duration, the time and/or the like) may be associated with a corresponding predefined message.

In an exemplary embodiment, the MCIC 78 may be embodied as an application that is downloaded to a device such as the receiving station 72 (and/or the calling station 70), which may, for example, be integrated with a call log application of the device. In some embodiments, the MCIC 78 may be downloaded or otherwise enabled at a mobile terminal when the user of the mobile terminal subscribes to a missed call interpretation service (which may be a fee based service). The MCIC 78 may be configured to connect to the MCIS 76 to retrieve missed call information. In this regard, the MCIC 78 may be configured to retrieve missed call information at periodic or predefined intervals (e.g., based on the occurrence of specific events) which may be defined by a user (e.g., in a user profile). As an alternative, the MCIC 78 may automatically retrieve missed call information in response to receipt of a missed call. In another alternative, receipt of a missed call may cause the MCIC 78 to generate a prompt to alert the user of the receiving station 72 of the missed call. The user may then be enabled (e.g., via a menu option) to initiate a retrieval of the missed call information. After connection to the MCIS 76, the MCIC 78 may be provided with the missed call data (e.g., calllD, time of call, duration). Based on an identity of the receiving station 72 (e.g., a telephone number of the receiving station) and the missed call data (all of which may be considered missed call characteristics), the MCIS 76 may determine which message information to include with the missed call data for inclusion in the missed call information that may thereafter be presented to the user of the receiving station 72. In particular, the calllD may indicate which account should be checked by the MCIS 76 to determine what rules are to be applied (e.g., which association between predefined messages and missed call characteristics is to be applied) with respect to identifying message information for inclusion in the missed call information to be provided to the MCIC 78. As indicated above, the missed call information may include information from the missed call log along with other information such as, for example, message information designated by the calling party before placement of the missed call (e.g., based on rules defined in the calling parties account). Menu options may also be provided for use in defining associations between missed call characteristics and corresponding predefined messages.

In some embodiments, the MCIC 78 may have a local store for information (e.g., a portion of the memory element 84) related to missed calls to expedite access to missed call information. In this regard, portions of the MCIS interpretation table 98 may be stored in the local store (e.g., for frequently used numbers). As such, for example, the local store may be synchronized with the MCIS 76 with regard to the portions replicated in the local store at periodic or predefined intervals or in response to particular events or user selection. FIG. 5 illustrates an exemplary architecture of the MCIC 78 according to an exemplary embodiment. As indicated in FIG. 5, the MCIC 78 may include a user interface portion, a log interface portion (e.g., for receiving call log information from a call log application), and a server connection function. The server connection function may be configured to initiate connection to the MCIS 76 or the local store for use in retrieving missed call information. In response to receipt of a missed call, the log interface portion may read publicly available directory data (e.g., calllD, time of call and call duration) from the missed call log.

FIG. 6 illustrates a control flow diagram showing a message retrieval sequence according to an exemplary embodiment. In this regard, as indicated at operation 120 a call may be received at the receiving station. Via the messaging at operation 122, information related to the missed call (or calls) may be retrieved. The user may then select a particular missed call via the messaging at operation 124 in order to get missed call information related to the missed call. In this regard, information such as calllD, time of the missed call and call duration may be retrieved from the missed call log and such information may be provided via connection to the MCIS 76 to retrieve missed call information associated with the particular missed call for delivery to the receiving station.

FIG. 7 illustrates a control flow diagram showing a message upload sequence according to an exemplary embodiment. In this regard, the calling station 70 may utilize a browser to access the web interface. A web page may be provided with a format for uploading data corresponding to the message information and/or associations that apply to the message information (e.g., conditions for serving the message information). The data may be entered and submitted by the calling station 70 and the web interface may make corresponding changes to the MCIS interpretation table. An acknowledgement of a successful update may then be communicated to the calling station.

FIG. 8 is a flow diagram of a system, method and program product according to exemplary embodiments of the invention. It will be understood that each block or step of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, and/or software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device of the mobile terminal or server and executed by a built-in processor in the mobile terminal or server. As will be appreciated, any such computer program instructions may be loaded onto a computer or other programmable apparatus (i.e., hardware) to produce a machine, such that the instructions which execute on the computer or other programmable apparatus create means for implementing the functions specified in the flowcharts block(s) or step(s). These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowcharts block(s) or step(s). The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowcharts block(s) or step(s).

Accordingly, blocks or steps of the flowcharts support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that one or more blocks or steps of the flowcharts, and combinations of blocks or steps in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

In this regard, one embodiment of a method for enabling missed call interpretation as illustrated, for example, in FIG. 8 may include providing an association of a predefined missed call characteristic with corresponding message information at operation 200. In response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, the method may further include providing the corresponding message information at operation 210.

In various exemplary embodiments, the operations above may be preceded by optional other operations. For example, in some embodiments, the method may include an initial operation of enabling a calling party to define the predefined missed call characteristic and the corresponding message information or receiving message information via a web interface, a short message service interface, or a voice recognition interface. Another optional initial operation may include enabling a calling party to establish an account defining a plurality of predefined missed call characteristics with a corresponding plurality of messages.

In an exemplary embodiment, associating the predefined missed call characteristic with the corresponding message information may include defining a particular predefined message to be associated with one or more of a missed call sent to a specified call recipient, a missed call sent at a particular time, or a missed call of a particular duration. Furthermore, in some embodiments, the method may further include enabling the calling party to modify the account by associating a selected standard message with a particular predefined missed call characteristic or enabling a device of a party receiving the missed call to issue the request for missed call information as a periodic automatic request, in response to initiation by the party receiving the missed call, or in response to a predefined event.

Embodiments of the present invention may also include an apparatus comprising a processor configured to enable a calling party to define a service account and provide an association of a predefined missed call characteristic with corresponding message information for communication to a network device managing the service account in order to enable provision of the corresponding message information to a receiver of a missed call in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic from the receiver. Other embodiments of the present invention may provide an apparatus comprising a processor configured to enable a party receiving a missed call to access a network device storing an association of a predefined missed call characteristic with corresponding message information, provide missed call criteria to the network device, and receive the corresponding message information in response to a characteristic of the missed call criteria matching the predefined missed call characteristic.

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

WHAT IS CLAIMED IS:

1. A method comprising: generating message information based on missed call information.

2. A method according to Claim 1, wherein generating message information based on missed call information comprises: providing an association of a predefined missed call characteristic with corresponding message information; and in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, providing the corresponding message information.

3. A method according to Claim 2, further comprising an initial operation of enabling a calling party to define the predefined missed call characteristic and the corresponding message information.

4. A method according to Claim 2, further comprising an initial operation of receiving message information via a web interface, a short message service interface, or a voice recognition interface.

5. A method according to Claim 2, wherein providing the association of the predefined missed call characteristic with the corresponding message information comprises defining a particular predefined message to be associated with one or more of: a missed call sent to a specified call recipient, a missed call sent at a particular time, or a missed call of a particular duration.

6. A method according to Claim 2, further comprising an initial operation of enabling a calling party to establish an account defining a plurality of predefined missed call characteristics with a corresponding plurality of messages.

7. A method according to Claim 2, further comprising enabling the calling party to modify the account by associating a selected standard message with a particular predefined missed call characteristic.

8. A method according to Claim 2, further comprising enabling a device of a party receiving the missed call to issue the request for missed call information: as a periodic automatic request, in response to initiation by the party receiving the missed call, or in response to a predefined event.

9. A computer program product comprising at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising: executable code instructions for generating message information based on missed call information.

10. A computer program product according to Claim 9, wherein the executable code instructions include: a first executable portion for providing an association of a predefined missed call characteristic with corresponding message information; and a second executable portion for, in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, providing the corresponding message information.

11. A computer program product according to Claim 10, further comprising a third executable portion for an initial operation of enabling a calling party to define the predefined missed call characteristic and the corresponding message information.

12. A computer program product according to Claim 10, further comprising a third executable portion for an initial operation of receiving message information via a web interface, a short message service interface, or a voice recognition interface.

13. A computer program product according to Claim 10, wherein the first executable portion includes instructions for defining a particular predefined message to be associated with one or more of: a missed call sent to a specified call recipient, a missed call sent at a particular time, or a missed call of a particular duration.

14. A computer program product according to Claim 10, further comprising a third executable portion for an initial operation of enabling a calling party to establish an account defining a plurality of predefined missed call characteristics with a corresponding plurality of messages.

15. A computer program product according to Claim 10, further comprising a third executable portion for enabling the calling party to modify the account by associating a selected standard message with a particular predefined missed call characteristic.

16. A computer program product according to Claim 10, further comprising a third executable portion for enabling a device of a party receiving the missed call to issue the request for missed call information: as a periodic automatic request, in response to initiation by the party receiving the missed call, or in response to a predefined event.

17. An apparatus comprising a processor configured to: generate message information based on missed call information.

18. An apparatus according to Claim 17, wherein the processor is configured generate message information based on missed call information by: providing an association of a predefined missed call characteristic with corresponding message information; and in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic, providing the corresponding message information.

19. An apparatus according to Claim 18, wherein the processor is further configured to perform an initial operation of enabling a calling party to define the predefined missed call characteristic and the corresponding message information.

20. An apparatus according to Claim 18, wherein the processor is further configured to perform an initial operation of receiving message information via a web interface, a short message service interface, or a voice recognition interface.

21. An apparatus according to Claim 18, wherein the processor is configured to associate the predefined missed call characteristic with the corresponding message information by defining a particular predefined message to be associated with one or more of: a missed call sent to a specified call recipient, a missed call sent at a particular time, or a missed call of a particular duration.

22. An apparatus according to Claim 18, wherein the processor is further configured to perform an initial operation of enabling a calling party to establish an account defining a plurality of predefined missed call characteristics with a corresponding plurality of messages.

23. An apparatus according to Claim 18, wherein the processor is further configured to enable the calling party to modify the account by associating a selected standard message with a particular predefined missed call characteristic.

24. An apparatus according to Claim 18, wherein the processor is further configured to perform enable a device of a party receiving the missed call to issue the request for missed call information: as a periodic automatic request, in response to initiation by the party receiving the missed call, or in response to a predefined event.

25. An apparatus comprising a processor configured to: enable a calling party to define a service account; and provide an association of a predefined missed call characteristic with corresponding message information for communication to a network device managing the service account to enable provision of the corresponding message information to a receiver of a missed call in response to receipt of a request for missed call information associated with a particular missed call having the predefined missed call characteristic from the receiver.

26. An apparatus comprising a processor configured to: enable a party receiving a missed call to access a network device storing an association of a predefined missed call characteristic with corresponding message information; provide missed call criteria to the network device; and receive the corresponding message information in response to a characteristic of the missed call criteria matching the predefined missed call characteristic.