CA2436067C - Availability and location predictor using call processing indications - Google Patents

Availability and location predictor using call processing indications Download PDF

Info

Publication number
CA2436067C
CA2436067C CA2436067A CA2436067A CA2436067C CA 2436067 C CA2436067 C CA 2436067C CA 2436067 A CA2436067 A CA 2436067A CA 2436067 A CA2436067 A CA 2436067A CA 2436067 C CA2436067 C CA 2436067C
Authority
CA
Canada
Prior art keywords
availability
call control
control events
user
running sum
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
CA2436067A
Other languages
French (fr)
Other versions
CA2436067A1 (en
Inventor
Thomas A. Gray
Ramiro Liscano
Rushabh Gudka
Christian Szpilfogel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitel Networks Corp
Original Assignee
Mitel Networks Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitel Networks Corp filed Critical Mitel Networks Corp
Publication of CA2436067A1 publication Critical patent/CA2436067A1/en
Application granted granted Critical
Publication of CA2436067C publication Critical patent/CA2436067C/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42229Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2242/00Special services or facilities
    • H04M2242/30Determination of the location of a subscriber
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42025Calling or Called party identification service
    • H04M3/42085Called party identification service
    • H04M3/42093Notifying the calling party of information on the called or connected party
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42365Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity

Abstract

A system for generating user availability information from call control events within a telephone system, comprising an Event Queue for receiving and storing call control events from the telephone system, and an Interpretation Engine for accessing the call control events in the Event Queue and in response updating a running sum for the user based on availability evidence ascribed to the call control events, and generating an indication of user availability based on the running sum.

Description

Availability and Location Predictor Using_Call Processing Indications Field of the Invention This invention relates generally to context-aware call handling in telephone systems, and more particularly to a method and apparatus for generating availability and location predictors using indications generated by call processing actions.
Background of the Invention To date, presence and availability capabilities have been confined generally to instant messaging systems such as Microsoft Messenger and ICQ. Users are presented with availability information in the form of buddy lists from which they are able to see which ones of their corespondents are available and attempt to send an instant message to them. The instant message system attempts delivery but there is no ability, such as is provided by call control in a telephony system, to forwaxd the call to another party, take a message, etc. Thus, no solution has been provided in the prior art to the problem of missed calls due to party unavailability.
2o To be truly useful, availability information must be as current and accurate as possible. In emerging IP telephony systems, where availability information is provided, the indicators of availability are primarily set by the user. The user can set his/her availability to 'At Lunch', 'Be Right Back' etc. This is obviously deficient in the sense that it relies on user action, which may be deferred when the user is concerned with other immediate pressing issues or more commonly when he/she is simply distracted.
This often leads to a situation wherein users do not use the such availability notification features since they are not updated often enough to be useful, and they are not updated often enough to be useful because people will not use them.
Summary of the Invention The present invention addresses the problem discussed above by making availability generation automatic, rather than based on a required action on the part of the user. In particular, a method of evidence gathering is provided that surmises (i.e. makes guesses) about user availability from his/her interactions with a PBX system.
The interactions are gathered as awareness information and processed by an algorithm into availability information. By using awareness information as evidence, the algorithm makes predictions about the users' availability or makes decisions in call processing. This information is fed back into a shared database (e.g. a tuple space) as assertions that indicate high level assessments about the user's state. These assessments are then used by call processing components to make decisions on call handling.
The present invention is an improvement to the invention described in Applicant's 1o copending UK Patent Application No. 0129250.7 entitled Proactive Features for Telephony. In that application, a system is described wherein availability information is presented and the user is provided with a mechanism to switch between multiple 'buddy lists' depending on either his/her express selection or by automatically taking into account his/her current actions. The system according to the present invention extends this concept 15 to provide a set of predictors for availability that use information from call processing actions. Thus, whereas Applicant's prior invention focuses on the receiver of presence information, the present invention focuses on the generation of presence information.
Applicant's copending Patent Application filed on the same date as this application 20 and entitled "Architecture and Implementation for Control of Context Aware Call Processing with Local Feature Definition ", discloses a generic call processing architecture in which operation of the system is divided into three main activities - context update, feature selection and feature execution. 'The system according to the present invention is implemented within the context update portion of Applicant's architecture.
25 Specifically, events from call processing are used to update information on the location and availability of users. This information may be sent to other users or sent to the feature selection component of Applicant's disclosed architecture to be used as part of the context evaluated when selecting a feature.
3o Brief Description of the Drawings A detailed description of the invention is set forth herein below, with reference to the following drawings, in which:

Figure 1 is a block diagram of an Internet telephony system according to the present invention for generating availability indicators from call control policies and awareness data;
Figure 2 is a schematic diagram showing how evidentiary and absolute indicators are composed according to the present invention;
Figure 3 shows the coordinates of a graph to indicate user availability based on call control events, where availability is predicted using the system according to the present 1o invention to be within areas bounded by predetermined levels;
Figure 4 is a graph of an example indication of user availability using the coordinates and regions of Figure 2, based on an example sequence of call control events;
and Figure 5 is a block diagram showing interpretation of incoming events from a PBX
in the system of Figure 1.
Detailed Description of the Preferred Embodiment Figure 1 is a block diagram of a system according to the present invention for combining call processing via call control 1 with a presence system 3. A PBX 5 provides conventional active call control functions as well as newly enabled applications that rely on presence information. More particularly, PBX S is enabled with an HCI
application by which external applications may be made aware of call control events which may occur in respect of any number of specific subscribers. For example, PBX 5 may be one either a Mitel 3200 or 3300 ICP with a MiTAI interface. Interpretation block 7 contains an application that subscribes to these call control events to provide an indication of user availability. Thus, the presence information used by call control 1 is generated both by its own actions and from information generated by presence system 3. Information from these two sources is combined for individual users in the Interpretation block 7. In IETF terms, this functions as a PUA 9 (Presence User Agent), which derives presence information from user activities to create an indication of availability for individual users that is stored in an internal database.

Thus, the Interpretation block 7 is integrated with real time call control. In terms of the call control architecture set forth in Applicant's copending Patent Application entitled "Architecture and Implementation for Control of Context Aware Call Processing with Local Feature Definition", this functionality falls within the category of context update activity by providing call control with context information for feature selection. This functionality also operates via the PUA 9 to generate presence and availability indications for the presence system 3.
1o The presence system 3 provides presence subscription and broadcast functionality to accept, authenticate and authorize subscription requests for presence information. In IETF terms, the PA 11 (Presence Agent) provides a service whereby external clients can subscribe to the availability information provided by the PUA 9. The PA 11 is responsible for the authorization of subscriptions from these external clients. In the example described is herein below, an implementation is set forth using the well-known IETF
protocol SIP.
An external client (Availability Client 13) is shown for subscribing to the availability information of personal correspondents of interest to a particular user. In the example of Figure 1, there is an indication that Aurora, Cathy, Feng and Gloria are 20 available for conversations while Brigitte, Debbie and Eliana are not. This is similar to the availability indications given in Applicant's copending Patent Application No.
0129250.7 entitled Proactive Features for Telephony.
It will be noted that there is effectively a feedback control loop for the user 2s between the presence application 3 and call control 1. The user is able to use hislher presence indications to direct the operation of call control features. Call processing indicators of availability are derived from the programming and operation of call control features for the user. As discussed below, the programming of certain features gives an absolute indication of a user's availability, whereas other features give no certain 3o indications when they are programmed but give 'evidence' directly when they are triggered.
Two examples of common call-processing features that give an absolute indication of a user's unavailability are Do-Not-Disturb (DND) and Call-Forward-Always-to-Voice-Mail (CFAVM). Both features prevent an incoming caller from synchronously connecting at any time with the user, thereby providing clear indications of unavailability.
Other examples of features that give indications of unavailability are:

~ Call-Forward-No-Answer (voice mail) ~ Directed Call Forward ~ Abandoned Incoming Call to Examples of features that give indications of availability are:
~ Off Hook ~ Answered Call Forward Always, No Answer or Busy (non voice mail) Table 1 is a list of the indicators used in the development of a working prototype of the invention. It will be appreciated that this list is exemplary only, and therefore non exhaustive.
Table 1-List of Indicators Used in Prototype Event Change in Evidence Availability DND on No Evidence Change Off DND off Evidence Up Evidentiary CF of any Evidence Up Evidentiary type Disable CFA No Evidence Change Off Voicemail Enable CFNA Evidence Up Evidentiary CFNA Voice Evidence Down Evidentiary CFNA Non Evidence Down (if not Evidentiary Voicemail answered) /LJp(answered) On Hook No Evidence Evidentiary Off Hook Evidence Up Off Abandoned Evidence Down Evidentiary Incoming Call Three absolute indictors are included in Table 1: DND On, CF always and Off 2o Hook. It will be noted that Off Hook is a hybrid indicator in that if a user is Off Hook, the user is obviously unavailable to take other calls. However the Off Hook event builds up evidence of availability since the user must be at his/her desk in order to go Off Hook.

Thus, when the user goes back On Hook the evidence gathered during the Off Hook period becomes relevant to the user's indicated availability. Of the absolute indicators shown in Table 1, only Off Hook is incremental. All others are discreet.
Contextual indicators are used in the system according to the invention to control the default value to which the running sum of evidentiary evidence decays in the absence of evidence. This default value can be set either high of low in order to bias the decision on availability to an expected state. For example, the default value can be set low during periods when the user is expected to be away (e.g. during the night, during meetings o (derived from the user's calendar), or higher during times in the user's business day when he/she has no meetings scheduled. One example of a list of indicators for controlling the default value is set forth in Table 2:
Table 2 Off Hours Low Lunch Time Neutral Business High Hours Vacation Low Meeting Low This default value can be set to high, low or neutral (0) in order to bias the decision on availability to an expected state.
Figure 2 is a schematic diagram showing how evidentiary and absolute indicators 2o are composed. The specific symbols used in Figure 2 are non-standard and are used only to give an illustration of how the composition is performed. The triangle is used as an indication that evidence from the occurrence of the evidentiary features is gathered and summed in a decision system as described in detail below. The output of the evidentiary system may be any one of available, unavailable or undetermined.
The absolute indicators may also have the availability values described above.
However, since they are definitive they are shown connected to a block that is used to indicate that they may be used to absolutely control the value of availability reported. It will be noted that Off Hook appears in both blocks because, even though it is an absolute indication of availability, it also provides incremental evidence?
The evidence gathered by the system according to the present invention relates to the occurrence of events in call processing. Some of this evidence is definitively gathered when the event occurs (referred to herein as 'discreet evidence'). Other evidence depends on the duration of occurrence of an event (referred to herein as 'incremental evidence' -one example being Off Hook).
The evidentiary system of the present invention implements a running sum whose value is determined by increments that are based on the occurrence of call control events.
The sum is compared against various levels as shown in Figure 3 (i.e. an upper maximum and a lower minimum which, for simplicity, are shown as being symmetrical around zero).
There are three regions for the sum, which determine the decision output of the system. If the sum is above the Upper Decision Level, it is in the Area of Availability and the user is considered to be available. If the sum is below the lower decision level, the sum is in the Area of Un-Availability and the user is considered to be unavailable. If the sum is 2o between these two values, it is considered to be in an Area of Indeterminate Availability and the availability of the user cannot be decided.
Figure 4 shows the operation of the evidentiary decision system fox exemplary values of input. It will be noted that the default value of the system has been set to below zero. This biases the system decision towards unavailability although, as shown in the diagram, without evidence the value at initiation creates an output of indeterminate availability.
From Figure 4, it can be seen that the system initially starts with no evidence. At some time later, a piece of incremental evidence is received (e.g. the user goes OFF
HOOK). This evidence points to availability such that the sum is incremented at a steady rate through time towards the upper maximum. Some time later a piece of discreet evidence is received (e.g. an answered Call Forward Always to a non-voice mail number).
This causes the sum to be increased immediately by a discreet amount. This increase takes the sum above the upper decision level such that the availability indicator report changes from indeterminate to available. If call control activity indicates that the user is available, the assumption of availability can be extended to an assumption that if the user is available now, he/she will be available for a further period of time. Thus, for the period following increase of the sum as a result of having received discreet evidence of availability, Figure 4 shows a gradual decay at a specific rate to the default value. This rate is chosen so that the availability state is maintained for a predetermined period of time.
Eventually, the sum decays below the upper decision value thereby causing the to prediction to change to indeterminate. The sum value continues to decay to the default value, where it where it remains in the absence of evidence, as indicted in Figure 4.
Some time later a piece of discreet evidence of unavailability is received (e.g. an unanswered incoming call). This results in the sum being further immediately decreased 1 s by a specific amount to below the lower decision level, causing the output to change to unavailable. In the absence of further evidence the sum increases incrementally (i.e.
reverse decay) towards the default value which, as discussed above, causes the availability status to change to indeterminate.
20 Returning briefly to Figure 1, in conjunction with Figure 5, within the PUA
9 there are two main processes, each with associated data components. The Event Queue operates asynchronously to gather call control events from the PBX 5. For each of the presentities that supply availability information ('presentity' is a term used in the art to describe an entity that supplies presence information to external clients), the Event Queue 25 creates the appropriate MiTAI subscriptions. The Event Queue 13 is thereby connected via a standard socket to the MiTAI application on the PBX 5 and thereafter asynchronously collects call control events from the PBX and stores them as strings.
The Interpretation Engine 7 works synchronously on a regular interval (e.g. 1 30 second) in accordance with a timer 15. It effectively runs once each such time interval and blocks on the expiration of the timer when it completes its operation, as discussed in greater detail below. The Interpretation Engine 7 contains multiple associated data structures with for each presentity. The data structure for each presentity contains:

~ Running Sum - an integer that contains the value of the current evidentiary sum, ranging from positive maximum to negative maximum ~ Default Value - an integer ranging from positive maximum to positive minimum to which Running Sum decays in the absence of evidence.
~ Availability - a string containing the current interpretation of the availability of the presentity. There are three values - Available, Unavailable, and Indeterminate ~ Absolute or Evidentiary - a boolean indicating which sort of indicator is currently controlling the availability state of the presentity. A value of 1 indicates control by an absolute indicator. A value of zero indicates control by evidentiary indicators ~ Absolute Indicator - a Boolean indicating the type of absolute indicator last seen. A
value of 1 is a positive indicator of availability and 0 is a negative indicator of availability.
~ Off Hook State - a Boolean indicating whether the presentity is off hook or not. A 1 indicates that the presentity is currently considered to be off hook.
1s 'The following pseudocode describes the reception and interpretation of events from the PBX 5.
Event Queue asynchronously receives events from the MiTAI application of the PBX
When timer on which the Interpretation Engine is blocked expires Interpretation Engine sets timer to its default period For all events in the Event Queue, Retrieve the event from the bottom of the queue If the queue is empty Block engine on its timer From information in the event string determine the presentity for which it is concerned and access the data structure for that presentity If the event indicates transition to an off hook state Set the Off Hook State Flag If the event indicates transition to an on hook state 5 Re-set the Off Hook state flag If the event indicates enabling of an absolute indicator Set the Absolute or Evidentiary indicator to indicate an absolute indicator Set the Absolute Indicator flag to indicate the type of absolute indicator, 1o either positive or negative If the event indicates the disabling of an absolute indicator Set the Absolute or Evidentiary indicator to indicate an evidentiary indicator If the event indicates a piece of discreet evidence of availability Increment the Running Sum towards the maximum value by the standard value used for discreet evidence.
Note that in the case of diverted calls (answered forwarded calls for 2o example) the evidence is indicative of the availability of the presentity from which the call was forwarded. In that case the Running Sum should be incremented for that presentity If the event indicates a piece of discreet evidence of unavailability Decrement the Running Sum towards the minimum value by the standard value used for discreet evidence Note that in the case of diverted calls (abandoned forwarded calls for example), the evidence is indicative of the unavailability of the presentity from which the call was forwarded. In that case, the 3o Running Sum should be decremented for that Presentity.
When the queue is exhausted For all presentities being monitored If the Off Hook State is set to 1, Increment the Running Sum towards the maximum value Else Decrement the Running sum towards the default value Check the state of the Absolute or Evidentiary Flag If the state of the Absolute or Evidentiary Flag indicates the observation of an absolute event to Set the value of the Availability string to the value indicated by the Availabilty_Indicator flag (i.e. set the Availability to available for positive absolute indicators and to Unavailable for negative indicators) Else, since there is no specific feature indicating an absolute indicator, check the value of the Off Hook State, ( an off hook line is considered to unavailable) if Off Hook State is not set Check value of the Running Sum If Running Sum is above the upper decision level Set Availability to Available 2o If Running Sum is equal to or less than the lower decision level Set Availability to Unavailable If Running Sum is greater than the lower decision level and less than the upper decision level Set Availability to Indeterminate If Off Hook State is set then set the value of the Availability string to Unavailable 3o When the foregoing has been accomplished for all presentities, the engine 7 will block on its timer 15.
The foregoing is a description of the process underlying the operation of the system. The pseudocode description is general, in order to provide a clear explanation of the process. In the particular implementation according to a working prototype of the invention, the Mitel Networks CTI protocol MiTAI was used to set monitors on the operations of specific line circuits connected to devices 17 within the ICP
(i.e. PBX 5).
The following additional elements of the data structure are used in the descriptions of the interpretations of the MiTAI event strings by the Interpretation Engine ? for the actual MiTAI implementation.
~ Voice Mail Number: a string containing the directory number of the voice mail to service for this presentity Diverted -a Boolean indicating that the call has been diverted to this directory number from another Diverted Number - a string containing the directory number of the device from which the call, has been diverted 1 s ~ Established - a Boolean indicating that a call has been established.
The events subscribed to and how these particular events were interpreted in the MiTAI implementation are as follows:
Zo For each of the monitored devices, subscriptions for seven events were set.
These were:
1. CallOriginatedEvent: a call attempt is being made on this device.
2. CallClearedEvent: an existing call on a device has ended
3. CallDivertedEvent: a call sent to this device has been diverted to another 25 device
4. CallReceivedEvent: a call attempt is being made to the device. It is in a state of nngmg
5. CallEstablishedEvent: a call attempt has been successful and the device has moved from the ringing state to the established state 30 6. ForwardFeatureEvent: a forwarding feature has been activated on the device 7. ActivateFeatureEvent: a feature has been activated on the device ' 13 These events are interpreted within the Interpretation Engine 7 to gather evidence of availability or unavailability which are then added to the Running Sum for each of the devices.
In operation MiTAI monitors in the ICP (PBX 5) forward notifications of these events to the Event Queue 13 in the form of strings of the form:
Event Strings from MiTAI
l0 The following are example of strings received from the MiTAI implementation for these various events. Explanations are provided for only the salient portions of each event:
CallReceivedEvent For the CallReceivedEvent there are two cases of interest. The first is for a call that was intended for the device that is being monitored. The second is for a call that was diverted to this device from another device. Examples are given below.
Call Intended for this Device:
A new call received by extension 4024 dialed from 4001:
CallReceivedEvent ReceivedState NewCall callid=69 hmonitor_obj=11147604 number=303 Wed Mar 13 16:46:07 caller: 4001 CallingDevice Msg:
dialed digits: 4024 origin:
ODD Msg:
3o Call Diverted to this Device Received a call on device 4023 dialed from 4001 and intended for 4024 CallReceivedEvent ReceivedState DivertedNoAnswerFrom callid=79 hmonitor_obj=11147604 number=371 Wed Mar 13 16:50:12 caller:4001 CallingDevice Msg:
dialed digits: 4024 origin: 4024 ODD Msg:

CallDivertedEvent Call diverted from 4024 to 4101 CallDivertedEvent IdleState DivertedNoAnswerAway callid=69 hmonitor_obj=11147604 number=313 Wed Mar 13 16:46:22 newdest: 41 O 1 The important aspects of this event string are:
newdest is the directory number of the device to which the call is sent CallEsta6lishedEvent Call was answered by extension 4023 CallEstablishedEvent EstablishedState AnswerInvoked callid=79 hmonitor_obj=11147604 number=380 Wed Mar 13 16:50:14 2o connect:4001 control:
control: 4023 Ca11C1earedEvent Note the identity of the device for which this event was received is not apparent in the event string. It can be derived from the parameters of the call back method that delivers the string.
3o CallClearedEvent IdleState ClearInvoked callid=3 hmonitor_obj=11147604 number=12 Mon Jul 08 09:30:55 Worktimer is Not Active CallOriginated Event Note the identity of the device for which this event was received is not apparent in the event string. It can be derived from the parameters of the call back method that delivers the string.
_____________________~__~________~_____~~_______________~_____r________________ ___~__ CallOriginatedEvent OriginatedState NewCallInvoked callid=5 hmonitor_obj=11147604 number=15 Mon Jul 08 09:32:30 Worktimer is Not Active ForwardFeatureEvent Call Forward Always feature to extension 4023 was enabled ForwardFeatureEvent FeatureEnabled CFAlways hmonitor_obj=11147604 number=394 Wed Mar 13 16:53:07 device: 4001 forwarding destination: 4023 5 ____________________________________________________________________ Forward No Answer feature to destination 4101 was disabled ForwardFeatureEvent FeatureDisabled CFNoAnswerInternal to hmonitor_obj=11147604 number=395 Wed Mar 13 16:53:41 device: 4001 forwarding destination: 4101 15 ActivateFeatureEvent Do No Disturb Feature on extension 4024 was enabled ActivateFeatureEvent FeatureEnabled DoNotDisturbFeature hmonitor_obj=11147604 number=397 Wed Mar 13 16:54:43 2o device:4024 The actions taken upon the reception of each MiTAI event string will now be described.
CallReceivedEvent:
When this event is received the Established Boolean is reset to indicate that a call has been received for this presentity but not yet established.
3o The Interpretation Engine 7 then checks to see if the call has been diverted or not by examining the string to see if it is a new or diverted call.
In the case of a new call, the Diverted Boolean in the data structure for the presentity is set to 0.
In the case of a diverted call, the Diverted Boolean is set to 1 and the Diverted Number string is set to the string found in the dialed digits field of the message.

CallDivertedEvent When this event is received, the only point of interest for this invention is whether the call has been diverted to the voice mail number for this presentity. The value of the string found in the Voice Mail field of the data structure is compared to the string found in the newdest filed of the message. If these are the same then the call has been diverted to voice mail. This is interpreted as discreet evidence that the user is unavailable and the discreet standard value is subtracted from the Running Sum for this presentity.
CallEstablishedEvent to The call has been answered. Several actions are taken:
The Established Boolean is set.
This event is interpreted as an indication that the device is off hook and the off hook flag is set.
The Diverted Boolean is examined, if it is set to one then this is taken as an indication that a forwarded call has been answered. This is evidence for the availability of the presentity that has forwarded the call. The Running Sum for the presentity that forwarded the call is incremented by the standard discreet amount. The identity of the presentity that forwarded the call is found in the Diverted Number string in the data structure, having been set to the correct value by the handling of the Call Received Event Ca110riginatedEvent This is interpreted as an off hook and the off hook flag for this presentity is set.
CaliClearedEvent The Established Boolean is checked. If it has been set, then this event is an indication that an established call has ended. This is interpreted as an on hook indication and the off hook flag for this presentity is reset If the Established Boolean has not been set, this will be taken as an indication that the incoming call has been abandoned (i.e. an indication of the unavailability of the presentity 3o for this device). The standard discreet amount is subtracted from the Running Sum of this presentity.
In addition, the Diverted Boolean is checked. If it is set then the call has been diverted and the abandonment is interpreted as unavailability for the forwarding presentity. The Diverted Number string in the data structure will contain the directory number of the forwarding presentity (as set by the CallReceivedEvent) and the Running Sum for this presentity is decremented by the standard discreet amount.
ForwardFeatureEvent This event indicates the enabling or disabling of a forwarding feature. For the purposes of the present invention the only events of interest are the enabling and disabling of Call Forward Always to the voice mail number for this presentity.
Initially the type of forwarding feature will be checked. If it is Call Forward Always (CFAlways in the string), the value of the field in the forwarding destination field is examined. If this is the same as the string in the Voice Mail field of the data structure for this presentity, the event string is checked to see if the feature is being enabled or disabled.
If the Call Forward Always feature is being enabled, this will be taken as an absolute indication of user unavailability. The Absolute or Evidentiary flag is then set to indicate an absolute indicator. The Absolute Indicator Boolean is set to 0 to indicate unavailability.
If the feature is being disabled, this will be taken as the disabling of an absolute indicator.
The Absolute or Evidentiary flag is therefore set to indicate an evidentiary indicator. It will also be taken as a discreet indication of user availability and the standard discreet amount is added to the Running Sum for this presentity.
ActivateFeatureEvent This event indicates the enabling or disabling of a feature. For the purposes of the present invention the only feature of interest is Do Not Disturb.
Initially, the type of feature is checked. If it is Do Not Disturb (DoNotDisturbFeature in the string), then whether it is being enabled or not is determined. If it is being enabled this will be taken as the enabling of an absolute indicator. It will be taken as an absolute indication of unavailability. The Absolute or Evidentiary flag is set to indicate an absolute indicator. The Absolute Indicator flag is set to 0 to indicate unavailability If the Do Not Disturb feature is being disabled, this is taken as an indication of the disabling of an absolute indicator and as a piece of discreet evidence that the user is available. The standard discreet amount is therefore added to the Running Sum for this presentity. The Absolute or Evidentiary flag is set to indicate an evidentiary indicator Ig Modifications and variations to the invention are possible. For example, it will be appreciated by a person skilled in the art that the activities discovered by the evidentiary indicators are also indications of location. Thus, indications of activity at the user's desk can be used to predict the user's presence at that location. Answered call forwards are also indicators of availability. If they are eliminated from consideration in the running sum, then the sum becomes an indication of location. Similarly, answered call forwards can be combined in another sum to indicate presence at that location.
1o Certain additional indicators may also be used to give a general but not conclusive indication of user availability. These indicators may be used to bias the evidentiary process into giving a prediction of availability that may be overcome by further evidence.
For example, time of day may be used an indicator of this type. Thus, for example, during business hours the evidentiary decision system may be biased to predict that the user is 15 available or perhaps more likely than not to be available. The opposite may be assumed outside of normal business hours.
Inherent in this disclosure is the assumption that parties other than the user will subscribe to the user's availability. However if the user either voluntarily or automatically 2o subscribes to his/her own availability as perceived by this system, the user will be encouraged to set the availability to the correct value (i.e. an absolute value of availability). This will encourage use of the system by making users aware of it and by also encouraging the provisioning of more accurate values.
25 The value of the running sum can also be used as an indicator of the confidence level that the system has in the decision that it has made. Decision levels relative to the default value can be supplied which can be used to indicate whether the system is confident, not confident, very confident, etc. in the decision. This, in turn, can be supplied as another value to the subscriber.
Instead of providing a subscriber with a decision on availability, it is contemplated that the subscriber be supplied with an indication of whether or not there is an absolute indicator what its value (available or unavailable) is. Alternatively, the value of the running sum can be provided to give an analog indication of the confidence that the system has in the user's availability.
All such modifications and variations are believed to be within the sphere and scope of the present invention as defined by the claims appended hereto.

Claims (15)

Claims:
1. A method of generating user availability information from call control events within a telephone system, comprising:

receiving call control events from said telephone system, wherein each of said call control events is ascribed one of either an absolute indicator of availability or evidence of availability;

updating a running sum for said user based on said evidence of availability;
and for each of said call control events to which said absolute indicator of availability has been ascribed generating an indication of said user availability based thereon, and otherwise generating said indication of user availability on said running sum.
2. A method as claimed in claim 1, wherein said running sum is updated by a discreet amount in response to call control events characterized by discreet evidence of availability and by incremental amounts in response to call control events characterized by incremental evidence of availability, whereby said indication of user availability is maintained for a predetermined period of time in the absence of further call control events.
3. A method as claimed in claim 2, wherein said running sum is prevented from being updated by said incremental amounts beyond a predetermined default value.
4. A method as claimed in claim 3, wherein said indication is 'available' in the event said running sum exceeds a predetermined upper decision level, 'unavailable' in the event said running sum is below a predetermined lower decision level, and 'indeterminate' in the event said running sum is intermediate said predetermined upper and lower decision levels.
5. A method as claimed in claim 4, wherein said default value is selected to bias said running sum toward said lower decision level.
6. A method as claimed in any one of claims 1 to 5, further including the step of generating an indication of said user location based on location information in said call control events.
7. A method as claimed in claim 3, wherein said absolute indictor of availability is one of either 'available' or 'unavailable'.
8. A system for generating user availability information from call control events within a telephone system, comprising:

an Event Queue for receiving and storing call control events from said telephone system, wherein each of said call control events is ascribed one of either an absolute indicator of availability or evidence of availability; and an Interpretation Engine for accessing said call control events in said Event Queue and for each of said call control events to which said absolute indicator of availability has been ascribed generating an indication of said user availability based thereon, and otherwise generating said indication of user availability on said running sum.
9. A system as claimed in claim 8, wherein said Interpretation Engine updates said value by a discreet amount in response to call control events characterized by discreet evidence of availability and by incremental amounts in response to call control events characterized by incremental evidence of availability, whereby said indication of user availability is maintained for a predetermined period of time in the absence of further call control events.
10. A system as claimed in claim 9, Interpretation Engine prevents said running sum from being updated by said incremental amounts beyond a predetermined default value.
11. A system as claimed in claim 10, wherein said Interpretation Engine generates an indication of 'available' in the event said running sum exceeds a predetermined upper decision level, 'unavailable' in the event said running sum is below a predetermined lower decision level, and 'indeterminate' in the event said running sum is intermediate said predetermined upper and lower decision levels.
12. A system as claimed in claim 11, wherein said default value is selected to bias said running sum toward said lower decision level.
13. A system as claimed in any one of claims 8 to 12, further including the step of generating an indication of said user location based on location information in said call control events.
14. A system as claimed in claim 8 and substantially as hereinbefore described with reference to or as illustrated in the accompanying Figures 1 to 5 inclusive.
15. A method as claimed in claim 1 and substantially as hereinbefore described with reference to or as illustrated in the accompanying Figures 1 to 5 inclusive.
CA2436067A 2002-08-12 2003-07-24 Availability and location predictor using call processing indications Expired - Lifetime CA2436067C (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GBGB0218708.6A GB0218708D0 (en) 2002-08-12 2002-08-12 Availability and location predictor using call processing indications
GB0218708.6 2002-08-12

Publications (2)

Publication Number Publication Date
CA2436067A1 CA2436067A1 (en) 2004-02-12
CA2436067C true CA2436067C (en) 2010-08-31

Family

ID=9942150

Family Applications (1)

Application Number Title Priority Date Filing Date
CA2436067A Expired - Lifetime CA2436067C (en) 2002-08-12 2003-07-24 Availability and location predictor using call processing indications

Country Status (5)

Country Link
US (2) US7308089B2 (en)
EP (1) EP1389866B1 (en)
CA (1) CA2436067C (en)
DE (1) DE60318786T2 (en)
GB (1) GB0218708D0 (en)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0218716D0 (en) * 2002-08-12 2002-09-18 Mitel Knowledge Corp Privacy and security mechanism fo presence systems with tuple spaces
US8060459B2 (en) 2003-08-01 2011-11-15 Mitel Networks Corporation Method for generating prospective availability data
US20050141687A1 (en) * 2003-12-31 2005-06-30 Timucin Ozugur Call treatment in a communications system based on instant messaging
US7804949B2 (en) * 2003-12-31 2010-09-28 Alcatel Lucent Client-based integration of PBX and messaging systems
US20050141479A1 (en) * 2003-12-31 2005-06-30 Timucin Ozugur Presence-based routing in a communications network environment
US7675903B2 (en) * 2004-02-06 2010-03-09 Alcatel Lucent Dynamic contact list management system and method
CA2609246A1 (en) * 2005-06-01 2006-12-07 Sanyo Electric Co., Ltd. Telephone and method of controlling telephone
EP1835707A1 (en) * 2006-03-14 2007-09-19 BRITISH TELECOMMUNICATIONS public limited company Communications networks
CN101035168B (en) * 2007-04-17 2010-08-25 华为技术有限公司 Call scheduling method, system and device
US20080285736A1 (en) * 2007-05-16 2008-11-20 Unison Technolgies Llc Systems and methods for providing unified collaboration systems with conditional communication handling
DE112007003365B4 (en) * 2007-11-12 2015-04-30 Avaya Communication Israel Ltd. Self-learning dynamic telephone feature activation profiles
JP5071158B2 (en) * 2008-02-29 2012-11-14 沖電気工業株式会社 Exchange system and server device
US9088882B2 (en) * 2009-06-16 2015-07-21 Intel Corporation Method and system for communication behavior
US8914850B1 (en) * 2011-10-14 2014-12-16 West Corporation Context aware transactions performed on integrated service platforms
CA2956413A1 (en) 2016-01-28 2017-07-28 Mitel Networks Corporation Method and system of providing context aware announcements

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH04160965A (en) 1990-10-25 1992-06-04 Nec Corp Method of updating presence information in switching network
US5341412A (en) * 1991-10-10 1994-08-23 Executone Information Systems, Inc. Apparatus and a method for predictive call dialing
US5946386A (en) * 1996-03-11 1999-08-31 Xantel Corporation Call management system with call control from user workstation computers
US5920621A (en) 1996-04-15 1999-07-06 Mci Communications Corporation System and method for distributing calls to customer service operators based on automatic determination of operator availability
US6330325B1 (en) * 1997-03-31 2001-12-11 Gn Netcom, Inc. Automatic log-off signaling for telephone systems
US6487290B1 (en) * 1999-04-28 2002-11-26 Periphonics Corporation Call routing based on local status evaluation
US6678366B1 (en) 1999-08-31 2004-01-13 Ulysses Esd, Inc. System and method for locating subscribers using a best guess location algorithm
DE60125637T2 (en) 2000-05-17 2007-10-04 International Business Machines Corp. System and method to detect the residence or availability of a telephone user and to publish the telephone number on the Internet
EP1161067B1 (en) 2000-05-17 2007-01-03 International Business Machines Corporation System and method for detecting the presence or availability of a telephone user and publishing the number in the internet
US20030121027A1 (en) * 2000-06-23 2003-06-26 Hines Kenneth J. Behavioral abstractions for debugging coordination-centric software designs
US20020085701A1 (en) * 2000-10-30 2002-07-04 Parsons Eric W. Method and system for providing unified communication management based on presence information
DE60040173D1 (en) 2000-12-29 2008-10-16 Nokia Corp PRESENCE AND MEETING TREATMENT INFORMATION

Also Published As

Publication number Publication date
EP1389866A1 (en) 2004-02-18
US20040028197A1 (en) 2004-02-12
CA2436067A1 (en) 2004-02-12
US7308089B2 (en) 2007-12-11
EP1389866B1 (en) 2008-01-23
GB0218708D0 (en) 2002-09-18
DE60318786T2 (en) 2009-02-12
DE60318786D1 (en) 2008-03-13
US20080095346A1 (en) 2008-04-24
US8102983B2 (en) 2012-01-24

Similar Documents

Publication Publication Date Title
US8102983B2 (en) Availability and location predictor using call processing indications
US7254221B2 (en) Methods, systems, and products for providing communications services
US6968052B2 (en) Method and apparatus for creating a presence monitoring contact list with dynamic membership
US6430289B1 (en) System and method for computerized status monitor and use in a telephone network
US7359496B2 (en) Communications system and method for providing customized messages based on presence and preference information
US6421439B1 (en) System and method for user affiliation in a telephone network
US6519335B1 (en) Apparatus, method and system for personal telecommunication incoming call screening and alerting for call waiting applications
US7020259B2 (en) Privacy screening service for telecommunications
US8848879B1 (en) Customizable notification based on recent communication history
US7330721B2 (en) Method and system for supporting non-intrusive and effective voice communication among mobile users
US8189759B2 (en) System and method for automatic call back using availability information
US7715538B2 (en) Privacy screening services
US7440562B2 (en) Phone line supervisory controls
US20070042792A1 (en) Determining message format according to status information
US20030005150A1 (en) Telecommunications interface
WO2007040787A2 (en) Telephony/conference activity presence state
US20050047562A1 (en) Managing incoming calls and/or messages in a communications system
US20060165058A1 (en) System and method for providing an eCamp feature in a session initiation protocol (SIP) environment
WO2007072323A2 (en) Communication terminal and server with presence database providing user acceptability levels for communication
Parsons et al. Guaranteed talk [telephony]

Legal Events

Date Code Title Description
EEER Examination request
MKEX Expiry

Effective date: 20230724