Telecommunication call support for mobile devices with presence features

Abstract

A system and method for achieving or assisting dynamic transfer of call support information across a network including at least a wireless portion coupled to a wireless communication device. The call support information providing the wireless communication device with updated caller identification and status or presence information by way of a service or server provisioned product and method.

Description

TECHNICAL FIELD

The present invention relates to telecommunication processing in general, and more particularly to call support for mobile communication devices having presence features.

BACKGROUND

It is commonly accepted today that users keep and rely on stored “phonebook” information in or on their mobile communication devices (e.g., cellular telephones). The phonebook is typically entered by the user of a mobile device using a user interface of the device such as a keypad. The user's contacts, such as friends, family, and frequently-called entities are associated in the phonebook with one or more phone numbers and other information that is then stored in a memory device, e.g. a flash memory, on the device. This enables easy and convenient dialing of the user's contacts from the user's device without the need to remember and re-enter the full phone number for each contact when the user wishes to call the contact.

In addition, it is common for mobile devices to include a display such that an incoming call identifies to the user of the device who the incoming call is from if the incoming call is from a contact of the user that is in the user's phonebook. The incoming call is simply matched to a phone number stored in the phonebook, and the incoming caller's name is shown to the user on the display of the mobile device rather than displaying the phone number of the caller. Alternately, even for unknown callers, the name and/or phone number of the caller can be displayed on the callee's mobile device through a “caller ID” feature.

More features for identifying the identity of callers are desired. And more features for determining the status of those in one's phonebook or contacts list are also desired. The present disclosure provides systems and methods for enhancing and creating such new features.

SUMMARY

The present disclosure includes numerous embodiments and preferred features of systems and methods for improving or facilitating dynamic presence functions on mobile communication devices such as cellular or wireless telephone devices. The present systems and methods include one or more where such mobile devices are coupled to a cellular or wireless network, or a portion of a wireless network being a cellular or wireless network. The cellular or wireless network including a server or other communication processor for provisioning calls, including by voice, data, packet, circuit, or combination of switching modalities between the mobile device and at least one other communication device. The at least one other communication device can include another wireless or cellular device, another communication processor device, computer, or similar apparatus that enables a user of the mobile device to communicate with another user of the other device.

In some embodiments, the user of the mobile device and another user of the other communication device communicate over a network including a wireless component and a wired component such as the Internet, and where a voice over IP portion of the communication between the users takes place. Packets of data or information relating to the call between the users represents voice data and other packets of data or information relating to the call between the users represents control or auxiliary, data such as for call set up and caller ID. In another embodiment, a service such as Skype® is employed to service a call between a computer coupled to one side of a network and a mobile device coupled to another side of the network.

Additional features and advantages of the invention will become apparent from the following drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention and to show how the same may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings in which like numerals designate corresponding elements or sections throughout. In the accompanying drawings:

FIG. 1 illustrates an exemplary communication network and associated communication devices according to one or more embodiments hereof;

FIG. 2 illustrates an exemplary method for delivery of contact information and caller ID data to a mobile phone user according to one or more embodiments hereof;

FIG. 3 illustrates another exemplary communication network and associated communication devices according to one or more embodiments hereof;

FIG. 4 illustrates another exemplary method for delivery of update and other contact presence data to a user of a mobile device;

FIG. 5 illustrates an exemplar process for tracking call failure according to one or more embodiments hereof; and

FIG. 6 illustrates another exemplary process for tracking and responding to call failure according to one or more embodiments hereof.

DETAILED DESCRIPTION

It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable sub-combination.

Unless otherwise defined, all technical and scientific terms used herein have the same meanings as are commonly understood by one of ordinary skill in the art to which this invention belongs. Although methods similar or equivalent to those described herein can be used in the practice or testing of the present invention, suitable methods are described herein.

The terms “include”, “comprise” and “have” and their conjugates as used herein mean “including but not necessarily limited to.”

Referring to FIG. 1, an exemplary block diagram for a communication system 100, and is provided in simplified form. The system is operative according to one or more of the preferred methods described herein. The system illustrated represents an embodiment according to the present discussion, but can be modified as would be appreciated by those skilled in the art. For example, equivalent corresponding components and elements could be substituted for those shown, sometimes under a different name. Also, other components could be added, including auxiliary components and elements beyond what is shown for the purpose of illustration. Specific examples of related embodiments are provided by the present applicants in earlier patent applications covering communications systems, some of which are referenced herein, and all of which are incorporated by reference.

The system 100 includes for example a communications server 110, which can be based on a server used in the telecommunications field or a server specifically assembled for the present purpose. The server 110 typically includes at least one processor capable of executing computer-readable instructions, the processor coupled to or having access to a memory or storage or database apparatus and an input/output apparatus as well as at least one communications port for communicating with other components over a communication channel.

In the shown illustrative embodiment, the server 110 has connections to a mobile circuit switched network 120. The network connection can be accomplished in one of the ways known to those skilled in the art, and can include at least a portion coupling server 110 to another server or switch within the mobile circuit switched network (not shown).

A mobile communications device such as a mobile or cellular phone 140 is designed to communicate through the mobile circuit switched network. Previous patent applications by the present inventors, incorporated herein by reference, describe ways to couple a mobile device to the network 120. However, those skilled in the art will appreciate several known ways to establish such coupling between mobile phone 140 and network 120.

Mobile phone 140 can be of a number of formats. In some embodiments, mobile phone 140 includes a user interface, perhaps even controlled by an operating system running on a processor of mobile phone 140. Also, mobile phone 140 can include a visual display unit, such as a LED or LCD or other electronic display, which shows the user of mobile phone 140 information relating to the function and operation of the mobile phone 140. Embodiments hereof will discuss some of the uses of the present system and methods and how the mobile phone 140 is used to display information to its user. Audible inputs and outputs of mobile phone 140 are also useful for voice communication with another party.

Server 110 is also connected to our coupled to a data network 130. Data network 130 can include one or many nodes therein, and in some embodiments, at least a portion of said network 130 includes the Internet or portions thereof. However, other networks can be used for the present purpose to carry data packets and information over the network. Packet switched networks ate suitable for some or all embodiments hereof.

A personal computer 150 is coupled to the data network 130. By the present exemplary illustration it is not meant to limit the present disclosure to traditional present-day personal computing devices, but some embodiments hereof do in fact utilize such computers (sometimes called “PCs”) as a communications apparatus. Other devices such as micro computers, workstations, desktop computers, notebook computers, and communication appliances are presently available and can be adapted for this purpose. The exemplary PC 150 typically includes a processor capable of executing computer-readable instructions, the processor coupled to or having access to a memory or storage or database apparatus and an input/output apparatus as well as at least one communications port for communicating with other components over a communication channel. In one or more embodiments, the PC 150 also includes a communications or telephony interface such as a microphone and a speaker system. The microphone and speaker system can permit audible (e.g., voice) interaction between a user of the PC 150 and the rest of the present system, usually by undertaking an analog to-digital process (connected to the microphone) and a digital-to-analog process (connected to the speaker system).

In operation, system 100 achieves at least a function of establishing a communications connection between mobile device 140 and PC 150. The communication in some embodiments or all embodiments can be initiated by either party. For most contexts, reference to communication between the communications devices (e.g., mobile phone 140, PC 150) corresponds to communication between users of the devices.

Communication over the networks (e.g., mobile circuit switched network 120, data network 130) can use one or more of the know communication protocols available to those skilled in the art. In addition, modified protocols or specialized protocols as necessary can be employed as well. More than one protocol can be used in the overall system to accomplish the present purpose. In some examples the communication protocol is influenced by the network over which the communication is to take place. In one or more embodiments, the Internet protocols (e.g., TCP/IP) are used to carry data communication. In other embodiments, the SS7 protocol is used to carry other information.

Turning to an exemplary method of operation of the system described above, FIG. 2 illustrates one embodiment of such a method. It is to be appreciated and understood that numerous other sub-steps than those shown and auxiliary steps and acts are often included in a specific implementation, but the present discussion is limited for the purpose of clarity and brevity, which is not intended to limit the present scope of the acts and steps and methods to be implemented in operational scenarios. Also, the sequence of steps described can be modified where appropriate or expedient, depending on the application at hand.

At the logical beginning of the communication process step 210 includes mobile phone 140 logging into a server that establishes a presence on a data network 130 with a push communication path. In some embodiments, the server can be server 110 shown in FIG. 1.

Next, at step 220 personal computer (PC) 150 originates a call to mobile phone 140 via server 110. It is notes once again, that such connections can in actual practice occur through a number of intermediate network nodes or servers or switches as appropriate.

In step 230 server 110 transmits data information, e.g., personal computer 150 or its user's code or identifier (e.g., a Skype® name) or other suitable user identification data to mobile phone 140. The act of transmission can include intermediate steps of signal processing, compression, encryption, conditioning, formatting, packaging, etc. Also, server 110 may send caller ID information to mobile phone 140 by way of a “push” communication path to mobile phone 140.

Mobile phone 140 receives the information sent from server 110 and stores some or all of said received information. For example, mobile phone 140 can store the received data in a memory unit such as a Flash memory device on mobile phone 14. The information can be associated with the caller ID information received by mobile phone 140.

Subsequently, or substantially concurrently, as called for, server 110 initiated a call (e.g., voice connection) from PC 150 to mobile phone 140. The call can comprise data transmitted over the mobile circuit switched network 120. It is understood in the present context that those skilled in the art could opt to use the same server 110 for both the push/data portion of the present steps and for the voice connectivity portion of the present steps. However, the present system and method are not so limited, and those skilled in the art can opt to employ two (or more) servers or communications processing machines for performing the push/data and the voice connectivity portions respectively.

Mobile phone 140 receives the call and the caller ID at step 260, not necessarily at the same time or in any particular sequence.

At step 270 the mobile phone 140 compares the received caller ID to previously-stored caller ID information. For example information stored in a memory unit such as a Flash memory unit on the mobile phone 140. The data information is then communicated to a user of the mobile phone 140.

In some embodiments the data information is communicated visually on the display unit mentioned above. In other embodiments other sensory interfaces, such as an audible interface, could be used for communicating the data information to the user.

To further illustrate the way in which the present systems and methods can improve mobile (and mixed) communications, consider illustrative exemplary FIG. 3 showing a communication system according to one or more embodiments hereof.

A server 310 or cluster of servers performing communications functions are coupled to at least one communications port, similar to the arrangement described earlier with respect to server 110. Through the communication network or networks, server 310 is in communication with a subscriber 320 of a mobile device (which can also be effectively interchangeably used with the subscriber 320 thereof where appropriate). In addition, server 310 is in communication with a contact 330 using another communications device, e.g., a personal computing device as previously described (which can be effectively interchangeably used with the contact 330 thereof where appropriate).

Server 310 is further coupled to, and in some embodiments can include, a tracking module or component, or tracker 340 to be described below. In addition, server 310 can include or be coupled to a watch module or component, or watcher 350 to be described below. Note that the watcher 350 can merely be a component or module of the tracker 340, but may be implemented as a separate component.

The tracker 340 and watcher 350 can be implemented as best fit for a particular application. In some embodiments, the tracker 340 and watcher 350 include hardware and/or software that enable computer-readable instructions and electronic logic operations to perform tracking and watching functions, as discussed herein. For example, separate tracking and watching software modules may be installed and run on server 310 or an associated machine to yield signals and results in a computing apparatus (e.g., a server) or processor to carry out the present steps and comprise the present system. As a further example, dedicated or substantially principally dedicated processor hardware can be included in or in association with server 310 to provide the tracking and watching features hereof.

Reference is now made to the mobile device 400 of FIG. 4, and to its operation described illustratively in FIG. 5. Once powered up, the subscriber device 320 presents a “Home Screen” on its visual display unit. The concept of a visible display unit has been discussed earlier and can be generalized as known to those skilled in the art. The Home Screen presents typically: a menu, a set of graphical user options or controls, some status information, and other operational and functional messages and icons.

Subscriber mobile device 400, which can be representative of mobile devices 140 and 320 above in certain embodiments, is illustrated in FIG. 4 to include a simplified user interface including a graphical visual display unit. The mobile device 400 provides a graphical visual output as discussed before and as known to those skilled in the art. The visual output can include for example the status of the subscriber's contacts 410. The subscriber's contact status portion 410 can in turn include useful information such as: 5 user contacts are presently online; 4 user contacts are offline; and 3 new contacts have joined or been added in the last five seconds. Furthermore, one or more of the user's contacts' presence status can be displayed in a presence display portion 412 of the Home Screen. The Home Screen can further include portions relating to the user's phonebook 420 and device options 430.

Some embodiments hereof provide active touch pads, touch-sensitive screens, or buttons, scroll wheels, and other user interaction apparatus, some or all of which can be adapted from presently-known technologies for human-device interaction and user interface design.

FIG. 5 illustrates an exemplary process for updating information on a subscriber's mobile device. There is little or no substantial difference in the present exemplary discussion between an owner, a user, and a subscriber unless the specific context so implies, in that they are generally human operators of the devices (e.g., mobile communication devices or personal computing devices). It should however be understood that an indirect use and operation of the devices is possible, and that a machine can be made to operate or use another machine or an output or result thereof, for example in automated systems. These are all generally included within the present scope.

In step 510 a subscriber (e.g., a person) powers-up or actuates his or her mobile device. The mobile device and its user can for this purpose be interchangeably referred to as 320 as seen in simplified FIG. 3. The activation or power-up can include a step of connecting the device so a source of power (e.g., a battery) and pressing an appropriate button (e.g., a power button), and may further comprise making appropriate start-up sequence operations to activate the subscriber's mobile device 320.

Upon startup, the Home Screen referenced above will appear to the user. The Home Screen will receive presence information from the network and/or server as discussed herein and in the references by the present inventors which are hereby incorporated. The presence information and contact status information are useful to the user of a mobile device to inform the user that certain of his or her friends or colleagues are in various states of availability for communication. Step 510 ensures that the presence information is dynamically up to date and refreshed as necessary by the server to indicate a current state of the contacts.

Tracker 340 on server 310 tracks or monitors call activity generated by mobile device 320 and notes such instances as: call failure to a contact, most dialed contacts, and contacts with highest call durations and totals. The tracker 340 can of course monitor the opposite or converse of these conditions and other conditions as required by the implementation and as needed to make a determination of which contacts are of certain significance. Tracker 340 itself or cooperatively can thus keep a log or an accounting to rank contacts of the user in some order if needed. In some embodiments, the user's most relevant or most called or most needed contacts are afforded special significance above those that the user rarely calls or speaks with very little.

In step 530, when an instance of call failure occurs, the tracker creates a “watch” 350 to watch for the status of the contact with which the call failure occurred. The watcher 350 can store parameters of the instance such as the callee's name and time of call or call failure, as well as a reason for the call failure. The watcher 350 registers itself with the tracker 340 and the watcher 350 and tracker 340 communicate by exchanging information, signals, and data as necessary. Again, the watcher 350 can be implemented as part of the tracker 340 in some embodiments. A separate watch by watcher 350 can be instantiated for each instance of a call failure. That is, if two calls had failed, two instances of a watch can be set up to monitor for future activity and status relevant to the two failed calls.

When and if update information is delivered to the mobile device 320 from server 310 the tracker 40 monitors the updated information as illustrated in step 540.

In step 550, when a contact with whom communication had failed due to offline presence then comes online, the watch created for that instance in referenced by the tracker 340.

In step 560 the tracker 340 notifies the server 310 that the newly-online (or restored) contact is important or significant to the subscriber 320. An alert is sent to subscriber mobile device 320 which displays this update on the Home Screen discussed earlier.

FIG. 6 illustrates an exemplary process 600 for updating contact information on a mobile subscriber's device. As before, the mobile communication device 320 can include a Home Screen on which the following indications take place.

In step 610, upon powering up the mobile device as discussed earlier, the subscriber is presented with a home screen interface indicative of information relevant to the subscriber, the mobile device, and the subscriber's contacts.

In step 620, the device indicates to the subscriber or user the number of contacts, type, status, and other information relating to the contacts. The contacts may correspond to entries in a subscriber's stored phonebook, or to entries in a database kept on or in the communication network.

In step 630, the device (e.g., in the home screen) indicates to the subscriber how many new or newly-available contacts have come online since a last refresh operation or update operation.

In step 640, a revolving or rotating or cycling “mood message” as discussed in earlier and related applications by the present inventors, is presented. In some embodiments, the messages can indicate a condition or status of the contacts. In some embodiments the messages indicate the status or condition of the subscriber's most relevant (or selected) contacts. These can be the contacts most often called or otherwise deemed of special significance as discussed earlier. The messages may revolve, rotate or cycle through a visible portion of the display, for example if there is insufficient space or resolution to conveniently display all mood or status information for the selected contacts concurrently.

In step 650, a special alert or tone or other audible or visual indication or message notifies the subscriber when a contact with whom communication had failed due to offline presence becomes available or online. A special contact can have a special or expedited or highlighted alert presented to indicate a special significance of the special contact's return to service. The subscriber can then re-establish connection with or redial the special contact.

It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather the scope of the present invention is defined by the appended claims and includes both combinations and sub-combinations of the various features described hereinabove as well as variations and modifications thereof, which would occur to persons skilled in the art upon reading the foregoing description.

Claims

1. A method for managing call failures on a mobile communication device, comprising: determining that a call between the mobile communication device and a contact over a wireless connection has failed;receiving, after the call failure determination on the mobile communication device, status information from a server that indicates that at least one triggering condition that caused the call failure has been resolved or eliminated, wherein the at least one triggering condition is associated with an identity parameter of the contact; andprompting, in response to the received status information, a user of the mobile communication device to re-attempt the call between the mobile communication device and the contact.

2. The method of claim 1, wherein the at least one triggering condition is associated with a time at which the call failed.

3. A method for tracking call failures of a mobile communication device on a server, comprising: monitoring, on the server, call activity of the mobile communication device;determining, based on the monitoring of the call activity, that a call between the mobile communication device and a contact over a wireless connection has failed;storing at least one triggering condition indicative of an expected causation for the call failure, wherein the at least one triggering condition is associated with an identity parameter of the contact;determining that the at least one triggering condition that caused the call failure has been resolved or eliminated; andtransmitting status information to the mobile communication device that indicates that the at least one triggering condition that caused the call failure has been resolved or eliminated.

4. The method of claim 3, wherein the storing further stores identification information of the contact and/or a time at which the call failure occurred.

5. The method of claim 3, wherein the at least one triggering condition corresponds to the contact transitioning from an online status to an offline status, andwherein the determination that the at least one triggering condition that caused the call failure has been resolved or eliminated corresponds to a detection that the contact has re-established the online status.

6. A mobile communication device configured to manage call failures, comprising: a memory storing computer-readable instructions; anda processor configured to execute the computer-readable instructions, the computer-readable instructions causing the processor to: determine that a call between the mobile communication device and a contact over a wireless connection has failed;receive, after the call failure determination, status information from a server that indicates that at least one triggering condition that caused the call failure has been resolved or eliminated, wherein the at least one triggering condition is associated with an identity parameter of the contact; andprompt, in response to the received status information, a user of the mobile communication device to re-attempt the call between the mobile communication device and the contact.

7. A server configured to track call failures of a mobile communication device, comprising: a memory storing computer-readable instructions; anda processor configured to execute the computer-readable instructions, the computer-readable instructions causing the processor to: monitor call activity of the mobile communication device;determine, based on the monitoring of the call activity, that a call between the mobile communication device and a contact over a wireless connection has failed;store at least one triggering condition indicative of an expected causation for the call failure, wherein the at least one triggering condition is associated with an identity parameter of the contact;determine that the at least one triggering condition that caused the call failure has been resolved or eliminated; andtransmit status information to the mobile communication device that indicates that the at least one triggering condition that caused the call failure has been resolved or eliminated.