US20010055963A1 - Unified alerting method and apparatus - Google Patents
Unified alerting method and apparatus Download PDFInfo
- Publication number
- US20010055963A1 US20010055963A1 US09/303,517 US30351799A US2001055963A1 US 20010055963 A1 US20010055963 A1 US 20010055963A1 US 30351799 A US30351799 A US 30351799A US 2001055963 A1 US2001055963 A1 US 2001055963A1
- Authority
- US
- United States
- Prior art keywords
- subscriber
- alert
- devices
- conditions
- information type
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 230000009471 action Effects 0.000 claims abstract description 30
- 238000001914 filtration Methods 0.000 claims description 44
- 238000004891 communication Methods 0.000 claims description 34
- 230000014509 gene expression Effects 0.000 claims description 8
- 230000005236 sound signal Effects 0.000 claims description 3
- 238000011156 evaluation Methods 0.000 claims 2
- 230000008569 process Effects 0.000 abstract description 36
- 238000006243 chemical reaction Methods 0.000 abstract description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000005540 biological transmission Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 241001522296 Erithacus rubecula Species 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 229920000747 poly(lactic acid) Polymers 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/12—Inter-network notification
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
- H04W88/184—Messaging devices, e.g. message centre
Definitions
- This invention relates to a method and apparatus for unified alerting of subscribers.
- a person may subscribe to a large number of different services such as paging service, cellphone service, e-mail service and many others delivered over the telephone network or the Internet, for example.
- a subscriber to multiple services may receive messages in any one of the services during a period of time even when that particular service is not accessible to the subscriber.
- the subscriber may be unaware of messages and miss opportunities to take timely action. Accordingly, new technology is needed to improve techniques for alerting subscribers.
- This invention provides for a unified alerting system that alerts the subscriber via one or more subscriber identified devices.
- the unified alerting system includes a unified alerting device that receives alert events from services subscribed to by the subscriber such as e-mail, paging service, wireless mobile service (e.g., cellphone), Internet services, etc.
- the unified alerting device filters the alert event and, based on the filtering results, may generate an alert to one or more devices identified in a subscriber profile.
- the alert event is filtered by a set of logic specified by the subscriber in terms of if-then-else statements containing conditions and actions, for example.
- Conditions have Boolean values of TRUE and FALSE based on values of variables as specified by the subscriber. For example, one variable may be the time of day while other variables may have Boolean values that are defined by the subscriber.
- a Boolean variable A is TRUE if a title of an e-mail includes “project X”; otherwise, the Boolean variable A has a value of FALSE.
- the actions included in the subscriber logic may set various control variables such as urgency level or priority or may be further if-then-else statements. In this way, the subscriber may specify complex conditions that process each alert event to determine whether the subscriber should be alerted via one of the available devices.
- the subscriber profile includes entries corresponding to each of possible devices through which the subscriber may be alerted.
- a schedule may be entered by the subscriber that indicates times when each of the devices may be used to alert the subscriber.
- the profile also may include a priority level corresponding to each of the devices during time periods when multiple devices are available. Thus, the subscriber may specify during any time period which of the available devices is/are preferred for the alerting function.
- the unified alerting device may also perform various conversions such as voice-to-text and text-to-voice or information extracted for their summaries so that messages received via text may be converted to voice and voice communication may be converted to text and the subscriber may converse with another party regardless of the capabilities of the device used.
- FIG. 1 shows an exemplary diagram of a unified alerting system
- FIG. 2 shows an exemplary process for generating an alert signal
- FIG. 3 shows an exemplary block diagram for an alert filtering device shown in FIG. 2;
- FIG. 4 shows a table of variables
- FIG. 5 shows a table of conditions
- FIG. 6 shows a user device profile
- FIG. 7 shows an exemplary alert command
- FIG. 8 shows an exemplary block diagram for a unified alerting device
- FIG. 9 shows a flow chart of an exemplary process of the unified alerting device.
- FIG. 1 shows an exemplary block diagram of a unified alerting system 100 .
- the unified alerting system 100 includes a network 102 coupled to: an e-mail server 108 , service providers 132 , cellphones such as cellphone 114 via mobile base stations 110 and towers 112 , pagers such as pager 118 via paging towers 116 , terminals 124 - 130 (e.g., telephone stations, personal computers, etc.) via local access providers (LAP) 120 and 122 , and a unified alerting device 104 .
- LAP local access providers
- the network 102 may include a telephone network (e.g., local and/or long distance), a data network such as the Internet, or other wired or wireless networks either private or public.
- the LAPs 102 and 122 may be local exchange carriers or other network interfaces such as Internet Service Providers.
- a subscriber to the unified alerting system 100 may have subscribed to many other services.
- the subscriber may have subscribed to a cellphone service, a pager service, an Internet service that receives e-mails from the e-mail server 108 , and other types of services such as a system calendar with automated reminders and airline services that provide for flight change notification.
- the e-mail server 108 may send an alert event to the unified alerting device 104 to indicate that an e-mail has been received for the subscriber.
- the alert event may be a message that identifies the sender and may include a summary of a received communication.
- the alert event may include a title and a sender ID of the e-mail.
- the alert event may provide caller ID information such as available from Automatic Name Identification (ANI).
- ANI Automatic Name Identification
- the unified alerting device 104 filters the alert event based on conditions prespecified by the subscriber. If the alert event survives the filtering process, the unified alerting device 104 retrieves a subscriber profile from a database 106 and searches for a most likely device that may be used to alert the subscriber of the incoming e-mail. For example, if the subscriber profile indicates that the subscriber may be reached via the pager 118 , the unified alerting device 104 then sends an alert (a page) via the paging towers 116 to alert the subscriber via the pager 118 of the incoming e-mail.
- the subscriber may send an alert event to the unified alerting device 104 to indicate that the facsimile transmission has been received.
- the unified alerting device 104 may locate an alternate facsimile device that is accessible to the subscriber and transfer the facsimile to the alternate facsimile device. If a facsimile device is not available, the unified alerting device 104 may send an alert to the subscriber via the cellphone 114 using synthesized voice, for example, to indicate that a facsimile has been received. The subscriber may retrieve the facsimile directly or instruct the unified alerting device 104 to forward the facsimile to a facsimile device accessible to the subscriber by contacting the unified alerting device 104 directly or by modifying the subscriber profile.
- the LAP 120 may send an alert event to inform the unified alerting device 104 of the call.
- the unified alerting device 104 filters the alert event and, if required, determines via the subscriber profile whether the subscriber may receive the voice phone call via the cellphone 114 (or other voice terminals or devices), for example. If the subscriber may be reached via the cellphone 114 , the unified alerting device 104 routes the call to the cellphone 114 via the mobile base station 110 and the tower 112 .
- the unified alerting device 104 sends the alert to the logging device which in turn logs the communication.
- the LAP 120 may also generate an alert event when the communication ends (i.e., if the communication was re-routed and responded to) and this alert event may be directed to the logging device to log when the communication ended.
- the unified alerting device 104 may generate the alert to the logging device so that a record of the communication and its duration may be saved, for example.
- the unified alerting device 104 locates and alerts the subscriber or a subscriber device or service when communication for the subscriber is received by any one of the services subscribed to by the subscriber.
- alert events may be generated that indicates a new departure time, for example.
- the subscriber may also instruct the unified alerting device 104 to alert a party at the landing location to indicate arrival time changes to inform the party when to pick up the subscriber, for example.
- the unified alerting device 104 filters the alert events received from various services subscribed to by the subscriber to determine an urgency level of the associated communication. As shown in FIG. 2, the unified alerting device 104 proceeds along a process 200 which first performs an alert filtering process 202 for each of the alert events received and those alert events that are selected by the filtering process 202 result in an alert command. An alert device selection process 204 receives the alert command and generates an alert signal to a device specified in a subscriber profile.
- the alert filtering process 202 filters each alert event based on a set of conditions that is specified by the subscriber. For example, the subscriber may plan to take a business trip to attend two meetings regarding very important business transactions. However, due to unavoidable circumstances, critical information needed to complete the meetings is not available at the time the subscriber leaves for the meetings. Such information is being acquired by other members of the business team such as Jocelyn, the subscriber's boss, and Joe, the subscriber's coworker. Thus, in order to ensure that the information obtained by Jocelyn and Joe may be obtained as soon as the information is available, the subscriber may specify the conditions so that the subscriber is alerted as soon as messages from Jocelyn and Joe are received. At the same time, the subscriber may desire to filter out all other messages so that only alerts corresponding to messages from Jocelyn or Joe are permitted to alert the subscriber during a specified period of time.
- the subscriber may specify the conditions so that the subscriber is alerted as soon as messages from Jocelyn and Joe
- FIG. 3 shows an exemplary block diagram of a device that performs the alert filtering process 202 .
- An alert filtering engine 210 receives alert events from the network 102 and generates alert commands based on subscriber filtering data 212 .
- the alert filtering engine 210 may execute a program that essentially performs logical functions in the form of if-then-else statements such as if ⁇ condition> then ⁇ action list 1> else ⁇ action list 2>.
- An action list is a set of one or more actions. For the remainder of the discussion, only one action in the action list 1 (action 1) and one action in the action list 2 (action 2) are used for ease of discussion.
- the condition may be a regular expression which has a Boolean value of “TRUE” or “FALSE”.
- the condition may be A AND B where A has a Boolean value of TRUE if the title of a received e-mail includes “project X”; otherwise, A has a value of FALSE. B has a value of TRUE if the title of the e-mail includes “project Y”; otherwise, B has a value of FALSE.
- a AND B will have a value of TRUE if the e-mail message includes both project X and project Y.
- Actions may be a specific action taken by the alert filtering engine 210 such as setting an urgency level value or generating an alert command.
- action 1 may set the urgency level to 1
- action 2 may set the urgency level to 2, where the urgency level of 1 is of greater urgency than the urgency level of 2.
- the alert filtering engine 210 may filter incoming alert events based on logical values of Boolean variables combined using operators in regular expressions specified by the subscriber.
- Boolean operators such as AND, OR, NOT, XOR, etc.
- the action performed by the alert filtering engine 210 may either be a direct action, such as setting an urgency level, or another if-then-else statement.
- the subscriber may specify complex conditions so that a sophisticated filtering process may be achieved.
- the above embodiment of the filtering process uses the if-then-else construct, other techniques of filtering are also possible. For example, any program that selects certain alert events over other alert events based on specified circumstances may be applied.
- the subscriber filtering data 212 may include variable definitions as well as expressions as shown in FIGS. 4 and 5.
- a table 214 of variables A-E are shown as an example.
- the table 214 has a variable column 216 and a definition column 218 .
- Entries 220 - 228 define the meaning of each of the corresponding variables A-E.
- entries 220 and 222 specify the definition of Boolean variables A and B as discussed earlier.
- Entries 224 and 226 specify the definition of Boolean variables C and D.
- the Boolean variable C has the value of TRUE if the e-mail is from Sally and FALSE otherwise. Sally may be a rendezvous between Joe and the subscriber, for example.
- the Boolean variable D has the value of TRUE is the e-mail is from “Jocelyn” and FALSE otherwise.
- the variable E is not a Boolean variable but an algebraic variable that is set to the time of day. These variables are set to their respective values by the alert filtering engine 210 based upon the specifications as set forth in the description field 218 of the table 214 .
- the alert filtering engine 210 may also interact with the source of the alert event such as the e-mail server 108 to obtain the information required to set the variable values.
- FIG. 5 shows a table 230 of regular expressions.
- the table 230 has a regular expression identification field 232 and a regular expression field 234 .
- the entries 236 - 244 of the table 230 define all of the conditions as specified by the subscriber. For example, entry 236 specifies condition 1 being TRUE when the time of day E is less than 9:00 am on Jan. 26, 1999. Thus, if the time of day is after 9:00 am, condition 1 is FALSE. Similarly, condition 2 is TRUE when the time of day is between 9:00 am and 11:30 am on Jan. 26, 1999 and if Boolean variable A and D are TRUE. Thus, condition 2 is TRUE if an alert event is an e-mail received from Jocelyn having the title “project X” and the alert event is received between 9:00 am and 11:30 am on Jan. 26, 1999. Conditions 3-5 are similarly defined.
- the above program example first sets urgency levels based on the conditions 1-5 and then specifies the conditions under which alert commands are generated.
- Other types of programs and variables and/or condition specifications are also possible including other program type statements such as assign, case, etc.
- the alert filtering engine 210 executes filtering instructions based upon the subscriber filtering data 212 to determine when an alert command may be generated.
- the alert device selection process 204 determines which of the services specified by the subscriber in a subscriber profile 300 may be used to alert the subscriber.
- FIG. 6 shows the subscriber profile 300 which includes a device field 302 and an availability field 304 .
- the device field 302 identifies all the devices that may be used to alert the subscriber and the availability field 304 indicates the time when each of the devices identified in the device field 302 may be used to alert the subscriber and the priority in which the device should be used when more than one device are available.
- the subscriber profile 300 may be initially generated by the unified alerting device 104 based on records of the services subscribed to by the subscriber. As the need arises, the subscriber may modify the subscriber profile 300 by adding other devices that may be accessible (e.g., a facsimile machine near a meeting room) and the time periods that each of the devices may be used.
- the subscriber may be reached via a pager as indicated in entry 306 , a facsimile machine as indicated in entry 314 , a telephone station (telephone 1) as indicated in entry 316 and an Internet log-on ID as indicated in entry 322 .
- the subscriber has specified a priority order for each of the available devices as: the pager first, then telephone 1 second, then fax 2 third and then Internet 2 fourth.
- the alert device selection process 204 may select the pager of entry 306 and display the title of the text.
- the alert device selection process 204 may send an alert via telephone 1 of entry 316 by converting the title of the text into voice and outputting speech via speech synthesis to the telephone 1 when answered.
- the alert device selection process 204 may then convert the text into a facsimile transmission and transmit the converted text to fax 2 of the entry 314 . If fax 2 cannot be reached (i.e., no answer or busy, for example), then the alert device selection process 204 may send the text to the Internet ID at Internet 2 of entry 322 .
- the priority assigned by the subscriber indicates an order in which the alert device selection process 204 attempts to communicate the received communication. If two of the available devices have the same priority, or no priority is specified, then the alert device selection process 204 may attempt to alert the subscriber via all the available devices at the same priority concurrently. Alternatively, the unified alerting device 104 may use a round robin technique for selecting an alert device, for example. In this way, the alert device selection process 204 may achieve a best effort to reach the subscriber.
- the subscriber profile 300 may include other parameters set by the subscriber to elect other features such as to specify a number of times to retry before going on to lower priority devices, to delay the alert by a predetermined amount of time, to delay the alert until after a predetermined time period (e.g., if the subscriber will not be accessible or does not want to be accessible between 9:00 am and 10:00 am), to convert between communication types (e.g., between text, voice or video), or to extract or summarize the received communication for the alert or to be sent with the alert.
- a predetermined time period e.g., if the subscriber will not be accessible or does not want to be accessible between 9:00 am and 10:00 am
- convert between communication types e.g., between text, voice or video
- an incoming communication is transmitted in one type such as text (e.g., ASCII), and the device selected is an audio type device such as a telephone, for example, then the subscriber may elect to convert the text to voice to alert the subscriber via an audio signal such as a telephone call.
- subscriber has the option of directing the alert device selection process 204 to select an available device having a higher priority or to select the best available device with the highest priority that is capable of receiving the incoming communication without conversion (i.e., the selected device is capable of receiving communication of the same type as the incoming communication).
- the unified alerting device 104 may send the facsimile to fax 2 (entry 214 ) immediately, unless otherwise specified.
- the subscriber may also specify to always alert via the pager 118 , for example.
- the unified alerting device 104 also sends an alert via the pager 118 with a message such as “facsimile waiting at fax 2”, for example.
- the subscriber profile may be overridden by the subscriber explicitly specifying how various communications should be handled via the alert filtering process 202 so that the alert device selection process 204 may be directed to search for one or more devices based on the schedule portion of the subscription profile 300 .
- the unified alerting device 104 may select the facsimile device over the cellphone 114 because the incoming message is a facsimile message.
- the subscriber may have specified via the subscriber filtering data 212 that for this particular alert event (identified by title, sender name, etc.), the alert is to be transmitted via the cellphone 114 with text of title and sender ID speech synthesized and the full text is to be transmitted to the PDA (entry 308 in FIG. 6, for example) at the same time. If the above alert cannot be completed, then send the full text via a facsimile.
- the subscriber may also specify, via the alert filtering process 202 , to extract particular information to use for the alert. For example, the title and sender ID of an e-mail may be extracted for a pager alert. More advanced extraction techniques such as automatic summary or identification of keywords may also be performed.
- FIG. 7 shows an alert command 500 for the above filtering result.
- a field 502 indicates priority and fields 504 - 508 indicate the device type and message content of the alert.
- the alert command indicates alerting via the cellphone 114 with title and sender ID and sending the full text to a PDA as a first priority.
- the full message is sent to a facsimile machine as a second priority only if the first priority devices do not respond.
- the alert device selection process 204 may also be used.
- the device selection may be completely imbedded into the conditions as processed by the alert filtering engine 210 .
- the alert command may include specific parameters that directs the alert device selection process 204 to select a particular device and to perform any conversions such as text-to-voice or voice-to-text that may be necessary. In this way, the subscriber may have broad flexibility to control which communications are received, which device(s) to receive the communication and how the communication is received.
- FIG. 8 shows an exemplary block diagram of the unified alerting device 104 .
- the unified alerting device 104 includes a controller 402 , a memory 404 , the alert filtering engine 210 , a network interface 408 , and a database interface 410 .
- the above components may be coupled together via a signal bus 412 .
- FIG. 8 shows a bus architecture, other hardware configurations may also be possible as is well known in the art.
- FIG. 8 shows a bus architecture, other hardware configurations may also be possible as is well known in the art.
- FIG. 8 shows a bus architecture, other hardware configurations may also be possible as is well known in the art.
- FIG. 8 shows a bus architecture, other hardware configurations may also be possible as is well known in the art.
- controller 402 and the alert filtering engine 210 show the controller 402 and the alert filtering engine 210 as separate units, the functions performed by these units may be combined or may be further divided among specific processors such as digital signal processors and/or performed by dedicated hardware such as application specific integrated circuits (ASIC) or other hardware implementations such as PLD, PAL or PLAs, for example.
- ASIC application specific integrated circuits
- the controller 402 may retrieve the subscriber filtering data 212 via the database interface 410 , place the subscriber filtering data 212 in the memory 404 and instruct the alert filtering engine 210 to determine whether an alert command should be generated based on the subscriber filtering data 212 .
- the alert filtering engine 210 executes the logic specified by the subscriber conditions, etc. and issues an alert command to the controller 402 based on the subscriber logic.
- the controller 402 retrieves the subscriber profile from the database 106 via the database interface 410 and performs the alert device selection process 204 to determine which of the devices is available to reach the subscriber and what conversions might be necessary to be performed so that the communication may be placed in the correct format for the selected device.
- the controller 402 may perform text-to-speech and speech-to-text conversions and connect the calling party with the subscriber's Internet logon so that the subscriber may communicate with the caller via an Internet access terminal.
- the reverse situation may also be achieved if the subscriber is available via a telephone while the other communicating party is using a text terminal such as a personal digital assistant (PDA).
- PDA personal digital assistant
- the controller 402 may alert the subscriber via an appropriate device and may serve as a critical communication link between the subscriber and the other communicating party.
- FIG. 9 shows a flowchart for a process of the unified alerting device 104 .
- the controller 402 receives an alert event through the network interface 408 and goes to step 1002 .
- the controller 402 directs the alert filtering engine 210 to process the alert event and goes to step 1004 .
- the controller 402 determines whether the alert filtering engine 210 has generated an alert command. If an alert command is generated, the controller 402 goes to step 1006 ; otherwise, the controller 402 goes to step 1031 .
- step 1031 the controller 402 terminates the alert process by either instructing the device that generated the corresponding alert event to place a message in the voice mailbox (for a phone call, for example) or take no further action (for e-mail service, for example) and goes to step 1032 to end the process.
- step 1006 the controller 402 selects the alert device based on the alert command and the subscriber profile 300 retrieved via the database interface 410 and goes to step 1008 .
- step 1008 the controller 402 determines whether the subscriber is reachable.
- the alert command may include multiple devices, each identified with a priority field. If such is the case, the controller 402 attempts to alert the subscriber via the highest priority devices and, if unsuccessful, then the next highest priority device(s) is used to generate the alert.
- the controller 402 determines that the subscriber is not reachable only when all of the identified device and alert command has been exhausted. If reachable, the controller goes to step 1014 ; otherwise, the controller goes to step 1018 .
- step 1018 the controller 402 determines whether the subscriber has selected a retry option. If retry is selected, the controller 402 goes to step 1024 ; otherwise, the controller 402 goes to step 1032 and ends the process. In step 1024 , the controller 402 delays for a predetermined amount of time and goes to step 1026 . In step 1026 , the controller 402 increments a count and goes to step 1028 . In step 1028 , the controller 402 determines whether the count has exceeded the maximum. If exceeded, the controller 402 goes to step 1032 to end the process; otherwise the controller 402 returns to step 1006 to select the alert device. A new alert device must be selected because time has passed and different devices may be available since the last selection.
- step 1014 the controller 402 determines whether alert message conversion is required. If required, the controller 402 goes to step 1016 ; otherwise, the controller 402 goes to step 1030 .
- step 1016 the controller 402 determines whether the alert device is a voice device or a text device. If a voice device, the controller 402 goes to step 1020 ; otherwise, the controller 402 goes to step 1022 .
- step 1020 the controller 402 generates a voice message (with conversion if necessary) and goes to step 1030 .
- step 1022 the controller 402 generates a text message (with conversion if necessary) and goes to step 1030 .
- step 1030 the controller 402 sends the alert to the selected alert device and goes to step 1032 to end the process.
Abstract
This invention provides for a unified alerting system that alerts the subscriber via one or more devices. The unified alerting system receives alert events from services subscribed to by the subscriber, filters the alert events and alerts the subscriber via one or more devices identified in a subscriber profile. The alert event is filtered by if-then-else statements that contain conditions and actions. Conditions have Boolean values and the actions set various control variables or may be further if-then-else statements. In this way, the subscriber may specify complex conditions that process each alert event to determine whether the subscriber should be alerted via one of the available devices. The subscriber profile specifies possible devices through which the subscriber may be alerted via a schedule corresponding to each of the devices. The profile also includes a priority level for each of the devices when multiple devices are available. The unified alerting device may also perform various conversions such as voice-to-text and text-to-voice so that messages may be sent in an alert regardless of the capabilities of the devices used.
Description
- 1. Field of Invention
- This invention relates to a method and apparatus for unified alerting of subscribers.
- 2. Description of Related Art
- In this age of telecommunication explosion, a person may subscribe to a large number of different services such as paging service, cellphone service, e-mail service and many others delivered over the telephone network or the Internet, for example. A subscriber to multiple services may receive messages in any one of the services during a period of time even when that particular service is not accessible to the subscriber. Thus, the subscriber may be unaware of messages and miss opportunities to take timely action. Accordingly, new technology is needed to improve techniques for alerting subscribers.
- This invention provides for a unified alerting system that alerts the subscriber via one or more subscriber identified devices. The unified alerting system includes a unified alerting device that receives alert events from services subscribed to by the subscriber such as e-mail, paging service, wireless mobile service (e.g., cellphone), Internet services, etc. The unified alerting device filters the alert event and, based on the filtering results, may generate an alert to one or more devices identified in a subscriber profile.
- The alert event is filtered by a set of logic specified by the subscriber in terms of if-then-else statements containing conditions and actions, for example. Conditions have Boolean values of TRUE and FALSE based on values of variables as specified by the subscriber. For example, one variable may be the time of day while other variables may have Boolean values that are defined by the subscriber. For example, a Boolean variable A is TRUE if a title of an e-mail includes “project X”; otherwise, the Boolean variable A has a value of FALSE.
- The actions included in the subscriber logic may set various control variables such as urgency level or priority or may be further if-then-else statements. In this way, the subscriber may specify complex conditions that process each alert event to determine whether the subscriber should be alerted via one of the available devices.
- The subscriber profile includes entries corresponding to each of possible devices through which the subscriber may be alerted. A schedule may be entered by the subscriber that indicates times when each of the devices may be used to alert the subscriber. The profile also may include a priority level corresponding to each of the devices during time periods when multiple devices are available. Thus, the subscriber may specify during any time period which of the available devices is/are preferred for the alerting function.
- The unified alerting device may also perform various conversions such as voice-to-text and text-to-voice or information extracted for their summaries so that messages received via text may be converted to voice and voice communication may be converted to text and the subscriber may converse with another party regardless of the capabilities of the device used.
- The invention is described in detail with reference to the following figures, wherein like numerals reference like elements, and wherein:
- FIG. 1 shows an exemplary diagram of a unified alerting system;
- FIG. 2 shows an exemplary process for generating an alert signal;
- FIG. 3 shows an exemplary block diagram for an alert filtering device shown in FIG. 2;
- FIG. 4 shows a table of variables;
- FIG. 5 shows a table of conditions;
- FIG. 6 shows a user device profile;
- FIG. 7 shows an exemplary alert command;
- FIG. 8 shows an exemplary block diagram for a unified alerting device; and
- FIG. 9 shows a flow chart of an exemplary process of the unified alerting device.
- FIG. 1 shows an exemplary block diagram of a unified
alerting system 100. The unifiedalerting system 100 includes anetwork 102 coupled to: ane-mail server 108,service providers 132, cellphones such ascellphone 114 viamobile base stations 110 andtowers 112, pagers such aspager 118 viapaging towers 116, terminals 124-130 (e.g., telephone stations, personal computers, etc.) via local access providers (LAP) 120 and 122, and a unifiedalerting device 104. - The
network 102 may include a telephone network (e.g., local and/or long distance), a data network such as the Internet, or other wired or wireless networks either private or public. The LAPs 102 and 122 may be local exchange carriers or other network interfaces such as Internet Service Providers. - A subscriber to the unified
alerting system 100 may have subscribed to many other services. For example, the subscriber may have subscribed to a cellphone service, a pager service, an Internet service that receives e-mails from thee-mail server 108, and other types of services such as a system calendar with automated reminders and airline services that provide for flight change notification. - When the subscriber is on a trip without access to e-mail, for example, and e-mail is received for the subscriber, the
e-mail server 108 may send an alert event to the unifiedalerting device 104 to indicate that an e-mail has been received for the subscriber. The alert event may be a message that identifies the sender and may include a summary of a received communication. For example, for e-mail, the alert event may include a title and a sender ID of the e-mail. For voice communication such as a telephone call, the alert event may provide caller ID information such as available from Automatic Name Identification (ANI). - When the alert event is received, the unified
alerting device 104 filters the alert event based on conditions prespecified by the subscriber. If the alert event survives the filtering process, the unifiedalerting device 104 retrieves a subscriber profile from a database 106 and searches for a most likely device that may be used to alert the subscriber of the incoming e-mail. For example, if the subscriber profile indicates that the subscriber may be reached via thepager 118, the unifiedalerting device 104 then sends an alert (a page) via thepaging towers 116 to alert the subscriber via thepager 118 of the incoming e-mail. - Similar to the above, if the subscriber receives a facsimile transmission at the terminal124 (e.g., a subscriber's facsimile machine), either the
terminal 124 or theLAP 120 may send an alert event to the unifiedalerting device 104 to indicate that the facsimile transmission has been received. After the filtering process, the unifiedalerting device 104 may locate an alternate facsimile device that is accessible to the subscriber and transfer the facsimile to the alternate facsimile device. If a facsimile device is not available, the unifiedalerting device 104 may send an alert to the subscriber via thecellphone 114 using synthesized voice, for example, to indicate that a facsimile has been received. The subscriber may retrieve the facsimile directly or instruct the unifiedalerting device 104 to forward the facsimile to a facsimile device accessible to the subscriber by contacting the unifiedalerting device 104 directly or by modifying the subscriber profile. - If the subscriber receives a voice phone call at the terminal126 (the subscriber's telephone station) and the subscriber had specified that communications to the terminal 126 should be re-routed, then the
LAP 120 may send an alert event to inform the unifiedalerting device 104 of the call. The unifiedalerting device 104 filters the alert event and, if required, determines via the subscriber profile whether the subscriber may receive the voice phone call via the cellphone 114 (or other voice terminals or devices), for example. If the subscriber may be reached via thecellphone 114, the unifiedalerting device 104 routes the call to thecellphone 114 via themobile base station 110 and thetower 112. If the subscriber had specified that a logging device (not shown) be alerted, for example, then the unifiedalerting device 104 sends the alert to the logging device which in turn logs the communication. The LAP 120 may also generate an alert event when the communication ends (i.e., if the communication was re-routed and responded to) and this alert event may be directed to the logging device to log when the communication ended. The unifiedalerting device 104 may generate the alert to the logging device so that a record of the communication and its duration may be saved, for example. Thus, the unifiedalerting device 104 locates and alerts the subscriber or a subscriber device or service when communication for the subscriber is received by any one of the services subscribed to by the subscriber. - While the above description provides for specific examples of services that generate alert events, other sources of alert events may also be possible. For example, the subscriber may subscribe to a calendar service that generates alert events based on prespecified circumstances. The alert event may be a message that contains an appointment time and names of parties of the appointment. The subscriber may have made flight reservations with an airline that offers flight schedule change alerts. Thus, if a flight schedule has changed, an alert may be generated that indicates a new departure time, for example. The subscriber may also instruct the
unified alerting device 104 to alert a party at the landing location to indicate arrival time changes to inform the party when to pick up the subscriber, for example. Thus, there may be many sources for alert events and these events are processed by theunified alerting device 104 as described below. - The
unified alerting device 104 filters the alert events received from various services subscribed to by the subscriber to determine an urgency level of the associated communication. As shown in FIG. 2, theunified alerting device 104 proceeds along aprocess 200 which first performs analert filtering process 202 for each of the alert events received and those alert events that are selected by thefiltering process 202 result in an alert command. An alertdevice selection process 204 receives the alert command and generates an alert signal to a device specified in a subscriber profile. - The
alert filtering process 202 filters each alert event based on a set of conditions that is specified by the subscriber. For example, the subscriber may plan to take a business trip to attend two meetings regarding very important business transactions. However, due to unavoidable circumstances, critical information needed to complete the meetings is not available at the time the subscriber leaves for the meetings. Such information is being acquired by other members of the business team such as Jocelyn, the subscriber's boss, and Joe, the subscriber's coworker. Thus, in order to ensure that the information obtained by Jocelyn and Joe may be obtained as soon as the information is available, the subscriber may specify the conditions so that the subscriber is alerted as soon as messages from Jocelyn and Joe are received. At the same time, the subscriber may desire to filter out all other messages so that only alerts corresponding to messages from Jocelyn or Joe are permitted to alert the subscriber during a specified period of time. - FIG. 3 shows an exemplary block diagram of a device that performs the
alert filtering process 202. Analert filtering engine 210 receives alert events from thenetwork 102 and generates alert commands based onsubscriber filtering data 212. Thealert filtering engine 210 may execute a program that essentially performs logical functions in the form of if-then-else statements such as if <condition> then <action list 1> else <action list 2>. An action list is a set of one or more actions. For the remainder of the discussion, only one action in the action list 1 (action 1) and one action in the action list 2 (action 2) are used for ease of discussion. The condition may be a regular expression which has a Boolean value of “TRUE” or “FALSE”. For example, the condition may be A AND B where A has a Boolean value of TRUE if the title of a received e-mail includes “project X”; otherwise, A has a value of FALSE. B has a value of TRUE if the title of the e-mail includes “project Y”; otherwise, B has a value of FALSE. Thus, A AND B will have a value of TRUE if the e-mail message includes both project X and project Y. - Actions may be a specific action taken by the
alert filtering engine 210 such as setting an urgency level value or generating an alert command. For example,action 1 may set the urgency level to 1 andaction 2 may set the urgency level to 2, where the urgency level of 1 is of greater urgency than the urgency level of 2. Thus, thealert filtering engine 210 may filter incoming alert events based on logical values of Boolean variables combined using operators in regular expressions specified by the subscriber. The operators may include any mathematical operators (e.g., algebraic/set operators such as >, <, =, −, ÷, ×, ⊂, ⊂, ⊃, ⊃, , ∪, ∩, ∈, ∉, ∀, ∃, , etc., and Boolean operators such as AND, OR, NOT, XOR, etc.). - The action performed by the
alert filtering engine 210 may either be a direct action, such as setting an urgency level, or another if-then-else statement. Thus, the subscriber may specify complex conditions so that a sophisticated filtering process may be achieved. While the above embodiment of the filtering process uses the if-then-else construct, other techniques of filtering are also possible. For example, any program that selects certain alert events over other alert events based on specified circumstances may be applied. - The
subscriber filtering data 212 may include variable definitions as well as expressions as shown in FIGS. 4 and 5. In FIG. 4, a table 214 of variables A-E are shown as an example. The table 214 has avariable column 216 and adefinition column 218. Entries 220 -228 define the meaning of each of the corresponding variables A-E. For example,entries Entries entry 228, the variable E is not a Boolean variable but an algebraic variable that is set to the time of day. These variables are set to their respective values by thealert filtering engine 210 based upon the specifications as set forth in thedescription field 218 of the table 214. Thealert filtering engine 210 may also interact with the source of the alert event such as thee-mail server 108 to obtain the information required to set the variable values. - FIG. 5 shows a table230 of regular expressions. The table 230 has a regular
expression identification field 232 and aregular expression field 234. The entries 236-244 of the table 230 define all of the conditions as specified by the subscriber. For example,entry 236 specifiescondition 1 being TRUE when the time of day E is less than 9:00 am on Jan. 26, 1999. Thus, if the time of day is after 9:00 am,condition 1 is FALSE. Similarly,condition 2 is TRUE when the time of day is between 9:00 am and 11:30 am on Jan. 26, 1999 and if Boolean variable A and D are TRUE. Thus,condition 2 is TRUE if an alert event is an e-mail received from Jocelyn having the title “project X” and the alert event is received between 9:00 am and 11:30 am on Jan. 26, 1999. Conditions 3-5 are similarly defined. - Based on the subscriber filtering data as described in FIGS. 4 and 5 above, the subscriber may specify the alert filtering as follows:
. . . if condition 1 then urgency level = 5else if condition 2 then urgency level = 1else if condition 3 then urgency level = 1else if condition 4 then urgency = 2else if condition 5 then urgency level = 5end if; end if; end if; end if; end if; . . . if condition 1 AND urgency level >3 then generate alert command end if;if ( condition 2 OR condition 4) AND urgency level >2 then generate alertcommand end if; if condition 3 AND urgency level >4 then generate alert command end if;if condition 5 AND urgency level >8 then generate alert command end if;. . . - The above program example first sets urgency levels based on the conditions 1-5 and then specifies the conditions under which alert commands are generated. Other types of programs and variables and/or condition specifications are also possible including other program type statements such as assign, case, etc. Thus, the
alert filtering engine 210 executes filtering instructions based upon thesubscriber filtering data 212 to determine when an alert command may be generated. - The alert
device selection process 204 determines which of the services specified by the subscriber in asubscriber profile 300 may be used to alert the subscriber. FIG. 6 shows thesubscriber profile 300 which includes adevice field 302 and anavailability field 304. Thedevice field 302 identifies all the devices that may be used to alert the subscriber and theavailability field 304 indicates the time when each of the devices identified in thedevice field 302 may be used to alert the subscriber and the priority in which the device should be used when more than one device are available. Thesubscriber profile 300 may be initially generated by theunified alerting device 104 based on records of the services subscribed to by the subscriber. As the need arises, the subscriber may modify thesubscriber profile 300 by adding other devices that may be accessible (e.g., a facsimile machine near a meeting room) and the time periods that each of the devices may be used. - For example, between 8:30 am and 11:30 am on January 26, the subscriber may be reached via a pager as indicated in
entry 306, a facsimile machine as indicated inentry 314, a telephone station (telephone 1) as indicated inentry 316 and an Internet log-on ID as indicated inentry 322. As indicated by the numbers above each schedule line, the subscriber has specified a priority order for each of the available devices as: the pager first, then telephone 1 second, then fax 2 third and thenInternet 2 fourth. For example, if the incoming communication is text, the alertdevice selection process 204 may select the pager ofentry 306 and display the title of the text. However, if the pager does not acknowledge receipt (either transmission via a two-way pager signal or via a revertive call), then the alertdevice selection process 204 may send an alert viatelephone 1 ofentry 316 by converting the title of the text into voice and outputting speech via speech synthesis to thetelephone 1 when answered. - If
telephone 1 does not answer, the alertdevice selection process 204 may then convert the text into a facsimile transmission and transmit the converted text to fax 2 of theentry 314. Iffax 2 cannot be reached (i.e., no answer or busy, for example), then the alertdevice selection process 204 may send the text to the Internet ID atInternet 2 ofentry 322. Thus, the priority assigned by the subscriber indicates an order in which the alertdevice selection process 204 attempts to communicate the received communication. If two of the available devices have the same priority, or no priority is specified, then the alertdevice selection process 204 may attempt to alert the subscriber via all the available devices at the same priority concurrently. Alternatively, theunified alerting device 104 may use a round robin technique for selecting an alert device, for example. In this way, the alertdevice selection process 204 may achieve a best effort to reach the subscriber. - The
subscriber profile 300 may include other parameters set by the subscriber to elect other features such as to specify a number of times to retry before going on to lower priority devices, to delay the alert by a predetermined amount of time, to delay the alert until after a predetermined time period (e.g., if the subscriber will not be accessible or does not want to be accessible between 9:00 am and 10:00 am), to convert between communication types (e.g., between text, voice or video), or to extract or summarize the received communication for the alert or to be sent with the alert. If an incoming communication is transmitted in one type such as text (e.g., ASCII), and the device selected is an audio type device such as a telephone, for example, then the subscriber may elect to convert the text to voice to alert the subscriber via an audio signal such as a telephone call. Thus, subscriber has the option of directing the alertdevice selection process 204 to select an available device having a higher priority or to select the best available device with the highest priority that is capable of receiving the incoming communication without conversion (i.e., the selected device is capable of receiving communication of the same type as the incoming communication). - For example, if a facsimile is received at 9:00 am on January 26, the
unified alerting device 104 may send the facsimile to fax 2 (entry 214) immediately, unless otherwise specified. The subscriber may also specify to always alert via thepager 118, for example. In this case, theunified alerting device 104 also sends an alert via thepager 118 with a message such as “facsimile waiting atfax 2”, for example. The subscriber profile may be overridden by the subscriber explicitly specifying how various communications should be handled via thealert filtering process 202 so that the alertdevice selection process 204 may be directed to search for one or more devices based on the schedule portion of thesubscription profile 300. - For example, if a facsimile message is received and the subscriber's profile indicates that the
cellphone 114 is a first priority device and a facsimile machine is a second priority device, theunified alerting device 104 may select the facsimile device over thecellphone 114 because the incoming message is a facsimile message. However, the subscriber may have specified via thesubscriber filtering data 212 that for this particular alert event (identified by title, sender name, etc.), the alert is to be transmitted via thecellphone 114 with text of title and sender ID speech synthesized and the full text is to be transmitted to the PDA (entry 308 in FIG. 6, for example) at the same time. If the above alert cannot be completed, then send the full text via a facsimile. - The subscriber may also specify, via the
alert filtering process 202, to extract particular information to use for the alert. For example, the title and sender ID of an e-mail may be extracted for a pager alert. More advanced extraction techniques such as automatic summary or identification of keywords may also be performed. - FIG. 7 shows an
alert command 500 for the above filtering result. Afield 502 indicates priority and fields 504-508 indicate the device type and message content of the alert. Thus, the alert command indicates alerting via thecellphone 114 with title and sender ID and sending the full text to a PDA as a first priority. The full message is sent to a facsimile machine as a second priority only if the first priority devices do not respond. - While the above describes a particular embodiment for the alert
device selection process 204, other techniques may also be used. For example, the device selection may be completely imbedded into the conditions as processed by thealert filtering engine 210. Thus, the alert command may include specific parameters that directs the alertdevice selection process 204 to select a particular device and to perform any conversions such as text-to-voice or voice-to-text that may be necessary. In this way, the subscriber may have broad flexibility to control which communications are received, which device(s) to receive the communication and how the communication is received. - FIG. 8 shows an exemplary block diagram of the
unified alerting device 104. Theunified alerting device 104 includes acontroller 402, amemory 404, thealert filtering engine 210, anetwork interface 408, and a database interface 410. The above components may be coupled together via asignal bus 412. While FIG. 8 shows a bus architecture, other hardware configurations may also be possible as is well known in the art. In addition, while FIG. 8 shows thecontroller 402 and thealert filtering engine 210 as separate units, the functions performed by these units may be combined or may be further divided among specific processors such as digital signal processors and/or performed by dedicated hardware such as application specific integrated circuits (ASIC) or other hardware implementations such as PLD, PAL or PLAs, for example. - When an alert event is received via the
network interface 408, thecontroller 402 may retrieve thesubscriber filtering data 212 via the database interface 410, place thesubscriber filtering data 212 in thememory 404 and instruct thealert filtering engine 210 to determine whether an alert command should be generated based on thesubscriber filtering data 212. Thealert filtering engine 210 executes the logic specified by the subscriber conditions, etc. and issues an alert command to thecontroller 402 based on the subscriber logic. If an alert command is received, thecontroller 402 retrieves the subscriber profile from the database 106 via the database interface 410 and performs the alertdevice selection process 204 to determine which of the devices is available to reach the subscriber and what conversions might be necessary to be performed so that the communication may be placed in the correct format for the selected device. - For example, if a telephone call was received for the subscriber and the subscriber may only be reached via the Internet, the
controller 402 may perform text-to-speech and speech-to-text conversions and connect the calling party with the subscriber's Internet logon so that the subscriber may communicate with the caller via an Internet access terminal. The reverse situation may also be achieved if the subscriber is available via a telephone while the other communicating party is using a text terminal such as a personal digital assistant (PDA). Thus, thecontroller 402 may alert the subscriber via an appropriate device and may serve as a critical communication link between the subscriber and the other communicating party. - FIG. 9 shows a flowchart for a process of the
unified alerting device 104. Instep 1000, thecontroller 402 receives an alert event through thenetwork interface 408 and goes to step 1002. Instep 1002, thecontroller 402 directs thealert filtering engine 210 to process the alert event and goes to step 1004. In step 1004, thecontroller 402 determines whether thealert filtering engine 210 has generated an alert command. If an alert command is generated, thecontroller 402 goes to step 1006; otherwise, thecontroller 402 goes to step 1031. Instep 1031, thecontroller 402 terminates the alert process by either instructing the device that generated the corresponding alert event to place a message in the voice mailbox (for a phone call, for example) or take no further action (for e-mail service, for example) and goes to step 1032 to end the process. - In step1006, the
controller 402 selects the alert device based on the alert command and thesubscriber profile 300 retrieved via the database interface 410 and goes to step 1008. Instep 1008, thecontroller 402 determines whether the subscriber is reachable. The alert command may include multiple devices, each identified with a priority field. If such is the case, thecontroller 402 attempts to alert the subscriber via the highest priority devices and, if unsuccessful, then the next highest priority device(s) is used to generate the alert. Thecontroller 402 determines that the subscriber is not reachable only when all of the identified device and alert command has been exhausted. If reachable, the controller goes to step 1014; otherwise, the controller goes to step 1018. - In
step 1018, thecontroller 402 determines whether the subscriber has selected a retry option. If retry is selected, thecontroller 402 goes to step 1024; otherwise, thecontroller 402 goes to step 1032 and ends the process. Instep 1024, thecontroller 402 delays for a predetermined amount of time and goes to step 1026. In step 1026, thecontroller 402 increments a count and goes to step 1028. Instep 1028, thecontroller 402 determines whether the count has exceeded the maximum. If exceeded, thecontroller 402 goes to step 1032 to end the process; otherwise thecontroller 402 returns to step 1006 to select the alert device. A new alert device must be selected because time has passed and different devices may be available since the last selection. - In
step 1014, thecontroller 402 determines whether alert message conversion is required. If required, thecontroller 402 goes to step 1016; otherwise, thecontroller 402 goes to step 1030. Instep 1016, thecontroller 402 determines whether the alert device is a voice device or a text device. If a voice device, thecontroller 402 goes to step 1020; otherwise, thecontroller 402 goes to step 1022. Instep 1020, thecontroller 402 generates a voice message (with conversion if necessary) and goes to step 1030. Instep 1022, thecontroller 402 generates a text message (with conversion if necessary) and goes to step 1030. Instep 1030, thecontroller 402 sends the alert to the selected alert device and goes to step 1032 to end the process. - While the invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, preferred embodiments of the invention as set forth herein are intended to be illustrative, not limiting. Various changes may be made without departing from the spirit and scope of the invention.
Claims (24)
1. A method for alerting a subscriber in a communication network, comprising:
receiving an alert event from the network;
filtering the alert event; and
alerting the subscriber with an alert via a device based on a subscriber profile and a result of the filtering.
2. The method of , wherein the filtering step makes a decision whether to alert the subscriber, the decision being made by evaluating one or more if-then-else statements based on one or more conditions and one or more actions.
claim 1
3. The method of , further comprising:
claim 2
evaluating one or more conditions to obtain Boolean values, where each of the conditions evaluate to a Boolean value; and
taking one or more actions based on the Boolean values.
4. The method of , wherein a condition is a regular expression of one or more variables combined with operators, each of the variables having a quantity that may be evaluated.
claim 3
5. The method of , wherein an action includes setting a value of a variable or evaluating additional one or more conditions and taking additional one or more actions based on results of the evaluations of the additional one or more conditions.
claim 2
6. The method of , wherein the subscriber profile includes a schedule of availability for one or more devices, the schedule specifying a date and time for each of the devices that may be used to alert the subscriber.
claim 1
7. The method of , wherein the subscriber profile includes a priority specification, the priority specification indicating a priority of each of devices that are available for a common period of time.
claim 6
8. The method of , further comprising:
claim 7
selecting a device from the subscriber profile that has a highest priority among those devices that may receive an information type that matches an information type of a communication corresponding to the alert event; and
alerting the subscriber using the information type of the communication via the selected device.
9. The method of , wherein the information type includes text, voice and video.
claim 8
10. The method of , wherein the alert includes at least one of an audio signal, a text message or a video message.
claim 1
11. The method of , further comprising:
claim 10
extracting information from a communication corresponding to the alert event; and one of:
including extracted information with the alert, or
sending the extracted information as the alert.
12. The method of , further comprising one of:
claim 1
waiting for a predetermined amount of time before performing the alerting step; or
not performing the alerting step during a pre-specified period of time.
13. The method of , further comprising:
claim 1
receiving a portion of a communication corresponding to the alert event in one information type; and
generating the alert for the device in another information type, where information types include text, voice and video.
14. A unified alerting device that alerts a subscriber in a communication network, comprising:
a database;
a network interface; and
a controller coupled to the database and the network interface, the controller receiving an alert event from the network via the network interface, filtering the alert event, and alerting the subscriber via a device based on a subscriber profile retrieved from the database and a result of the filtering.
15. The device of , wherein the controller makes a decision whether to alert the subscriber, the decision being made by evaluating one or more if-then-else statements based on one or more conditions and one or more actions.
claim 14
16. The device of , wherein the controller evaluates one or more conditions to obtain Boolean values, where each of the conditions evaluate to a Boolean value, and takes one or more actions based on the Boolean values.
claim 15
17. The device of , wherein a condition is a regular expression of one or more variables combined with operators, each of the variables having a quantity that may be evaluated.
claim 16
18. The device of , wherein an action includes setting a value of a variable or evaluating additional one or more conditions and taking additional one or more actions based on results of the evaluations of the additional one or more conditions.
claim 15
19. The device of , wherein the subscriber profile includes a schedule of availability for one or more devices, the schedule specifies a date and time for each of the devices that may be used to alert the subscriber.
claim 14
20. The device of , wherein the subscriber profile includes a priority specification, the priority specification indicating a priority of each of devices that are available for a common period of time.
claim 19
21. The device of , wherein the controller selects a device from the subscriber profile that has a highest priority among those devices that may receive an information type that matches an information type of a communication corresponding to the alert event, and alerts the subscriber using the information type of the communication via the selected device.
claim 20
22. The device of , wherein the information type includes text, voice and video.
claim 21
23. The device of , wherein the alert include at least one of an audio signal, a text message or a video message.
claim 14
24. The device of , wherein the controller receives a portion of a communication corresponding to the alert event in one information type, and generates the alert for the device in another information type, where information types include text, voice and video.
claim 14
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/303,517 US6459913B2 (en) | 1999-05-03 | 1999-05-03 | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
CA002304355A CA2304355C (en) | 1999-05-03 | 2000-04-06 | Unified alerting method and apparatus |
EP00303419A EP1051019A2 (en) | 1999-05-03 | 2000-04-25 | Unified alerting method and apparatus |
BR0007098-0A BR0007098A (en) | 1999-05-03 | 2000-04-26 | Unified alert method and apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/303,517 US6459913B2 (en) | 1999-05-03 | 1999-05-03 | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010055963A1 true US20010055963A1 (en) | 2001-12-27 |
US6459913B2 US6459913B2 (en) | 2002-10-01 |
Family
ID=23172481
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/303,517 Expired - Lifetime US6459913B2 (en) | 1999-05-03 | 1999-05-03 | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
Country Status (4)
Country | Link |
---|---|
US (1) | US6459913B2 (en) |
EP (1) | EP1051019A2 (en) |
BR (1) | BR0007098A (en) |
CA (1) | CA2304355C (en) |
Cited By (103)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002031726A1 (en) * | 2000-10-12 | 2002-04-18 | Worldspan, L.P. | Method, computer program, and system for pushing flight information to passengers |
US20020059073A1 (en) * | 2000-06-07 | 2002-05-16 | Zondervan Quinton Y. | Voice applications and voice-based interface |
US6459913B2 (en) * | 1999-05-03 | 2002-10-01 | At&T Corp. | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
US20040003048A1 (en) * | 2002-03-20 | 2004-01-01 | Bellsouth Intellectual Property Corporation | Outbound notification using customer profile information |
US20040110488A1 (en) * | 2002-12-10 | 2004-06-10 | Nokia Corporation | System and method for performing security functions of a mobile station |
US20050038853A1 (en) * | 2001-10-05 | 2005-02-17 | Dominique Blanc | Communication of messages in a system |
US20060036702A1 (en) * | 2004-07-02 | 2006-02-16 | Theimer Gerhard K | Personal notification device |
US7139827B1 (en) * | 1999-10-20 | 2006-11-21 | Fujitsu Limited | Communication means notification method and notification system |
US20080075118A1 (en) * | 2006-09-25 | 2008-03-27 | David Knight | Methods and apparatuses for managing resources within a virtual room |
US20080318553A1 (en) * | 2006-04-26 | 2008-12-25 | Kamfu Wong | System and Method for Receiving Emails in Instantly Via a Mobile Phone |
US20090099992A1 (en) * | 2000-03-16 | 2009-04-16 | Microsoft Corporation | Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information |
US20090238088A1 (en) * | 2008-03-19 | 2009-09-24 | Oki Electric Industry Co., Ltd. | Network traffic analyzing device, network traffic analyzing method and network traffic analyzing system |
US20130028402A1 (en) * | 2004-02-06 | 2013-01-31 | At&T Intellectual Property I. L.P. | System and Method for Broadcasting Packetized Voice Messages |
US8560689B2 (en) | 2010-11-02 | 2013-10-15 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8621277B2 (en) | 2010-12-06 | 2013-12-31 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US8639980B2 (en) | 2011-05-26 | 2014-01-28 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8660995B2 (en) | 2011-06-22 | 2014-02-25 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8676883B2 (en) | 2011-05-27 | 2014-03-18 | International Business Machines Corporation | Event management in a distributed processing system |
US8682280B1 (en) * | 2006-10-17 | 2014-03-25 | At&T Mobility Ii Llc | Selectable processing of broadcast EAS messages |
US8688769B2 (en) | 2011-10-18 | 2014-04-01 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8689050B2 (en) | 2011-06-22 | 2014-04-01 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8713581B2 (en) | 2011-10-27 | 2014-04-29 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8730816B2 (en) | 2010-12-07 | 2014-05-20 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US8756462B2 (en) | 2011-05-24 | 2014-06-17 | International Business Machines Corporation | Configurable alert delivery for reducing the amount of alerts transmitted in a distributed processing system |
US20140200739A1 (en) * | 2013-01-15 | 2014-07-17 | Honda Motor Co., Ltd. | Enhancing vehicle connectivity |
US8805999B2 (en) | 2010-12-07 | 2014-08-12 | International Business Machines Corporation | Administering event reporting rules in a distributed processing system |
US8825852B2 (en) | 2010-11-02 | 2014-09-02 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system |
US20140282003A1 (en) * | 2013-03-15 | 2014-09-18 | Apple Inc. | Context-sensitive handling of interruptions |
US8868984B2 (en) | 2010-12-07 | 2014-10-21 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system with event listeners and alert listeners |
US8880943B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8887175B2 (en) | 2011-10-18 | 2014-11-11 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8943366B2 (en) | 2012-08-09 | 2015-01-27 | International Business Machines Corporation | Administering checkpoints for incident analysis |
US8954811B2 (en) | 2012-08-06 | 2015-02-10 | International Business Machines Corporation | Administering incident pools for incident analysis |
US9086968B2 (en) | 2013-09-11 | 2015-07-21 | International Business Machines Corporation | Checkpointing for delayed alert creation |
US9104995B1 (en) * | 2012-09-28 | 2015-08-11 | Emc Corporation | Subject and audience oriented instant collaborative development |
US9170860B2 (en) | 2013-07-26 | 2015-10-27 | International Business Machines Corporation | Parallel incident processing |
US9178937B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US9201756B2 (en) | 2011-05-27 | 2015-12-01 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US9246865B2 (en) | 2011-10-18 | 2016-01-26 | International Business Machines Corporation | Prioritized alert delivery in a distributed processing system |
US9256482B2 (en) | 2013-08-23 | 2016-02-09 | International Business Machines Corporation | Determining whether to send an alert in a distributed processing system |
US9286143B2 (en) | 2011-06-22 | 2016-03-15 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US20160110066A1 (en) * | 2011-10-04 | 2016-04-21 | Telogis, Inc. | Customizable vehicle fleet reporting system |
US9348687B2 (en) | 2014-01-07 | 2016-05-24 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US9361184B2 (en) | 2013-05-09 | 2016-06-07 | International Business Machines Corporation | Selecting during a system shutdown procedure, a restart incident checkpoint of an incident analyzer in a distributed processing system |
US9519931B2 (en) * | 2015-05-15 | 2016-12-13 | Ebay Inc. | System and method for personalized actionable notifications |
US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
US9602337B2 (en) | 2013-09-11 | 2017-03-21 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9620104B2 (en) | 2013-06-07 | 2017-04-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9626955B2 (en) | 2008-04-05 | 2017-04-18 | Apple Inc. | Intelligent text-to-speech conversion |
US9633660B2 (en) | 2010-02-25 | 2017-04-25 | Apple Inc. | User profiling for voice input processing |
US9646614B2 (en) | 2000-03-16 | 2017-05-09 | Apple Inc. | Fast, language-independent method for user authentication by voice |
US9658902B2 (en) | 2013-08-22 | 2017-05-23 | Globalfoundries Inc. | Adaptive clock throttling for event processing |
US9668024B2 (en) | 2014-06-30 | 2017-05-30 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US20170195442A1 (en) * | 2016-01-05 | 2017-07-06 | Samsung Electronics Co., Ltd. | Electronic device and method for controlling the electronic device |
US20170272505A1 (en) * | 2016-03-17 | 2017-09-21 | Disney Enterprises, Inc. | System and method for leveraging machine learning to deliver time-sensitive content over optimal devices and channels |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US9953088B2 (en) | 2012-05-14 | 2018-04-24 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US9966068B2 (en) | 2013-06-08 | 2018-05-08 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US9971774B2 (en) | 2012-09-19 | 2018-05-15 | Apple Inc. | Voice-based media searching |
US9986419B2 (en) | 2014-09-30 | 2018-05-29 | Apple Inc. | Social reminders |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
CN108476262A (en) * | 2016-01-05 | 2018-08-31 | 三星电子株式会社 | Electronic equipment and method for control electronics |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
US10079014B2 (en) | 2012-06-08 | 2018-09-18 | Apple Inc. | Name recognition system |
US10089072B2 (en) | 2016-06-11 | 2018-10-02 | Apple Inc. | Intelligent device arbitration and control |
US10102359B2 (en) | 2011-03-21 | 2018-10-16 | Apple Inc. | Device access using voice authentication |
US10169329B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Exemplar-based natural language processing |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
US10185542B2 (en) | 2013-06-09 | 2019-01-22 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US10269345B2 (en) | 2016-06-11 | 2019-04-23 | Apple Inc. | Intelligent task discovery |
US10283110B2 (en) | 2009-07-02 | 2019-05-07 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US10297253B2 (en) | 2016-06-11 | 2019-05-21 | Apple Inc. | Application integration with a digital assistant |
US10318871B2 (en) | 2005-09-08 | 2019-06-11 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US10354011B2 (en) | 2016-06-09 | 2019-07-16 | Apple Inc. | Intelligent automated assistant in a home environment |
US10356243B2 (en) | 2015-06-05 | 2019-07-16 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US10410637B2 (en) | 2017-05-12 | 2019-09-10 | Apple Inc. | User-specific acoustic models |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
US10482874B2 (en) | 2017-05-15 | 2019-11-19 | Apple Inc. | Hierarchical belief states for digital assistants |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10521466B2 (en) | 2016-06-11 | 2019-12-31 | Apple Inc. | Data driven natural language event detection and classification |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10706841B2 (en) | 2010-01-18 | 2020-07-07 | Apple Inc. | Task flow identification based on user intent |
US10733993B2 (en) | 2016-06-10 | 2020-08-04 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US10755703B2 (en) | 2017-05-11 | 2020-08-25 | Apple Inc. | Offline personal assistant |
US10791176B2 (en) | 2017-05-12 | 2020-09-29 | Apple Inc. | Synchronization and task delegation of a digital assistant |
US10795541B2 (en) | 2009-06-05 | 2020-10-06 | Apple Inc. | Intelligent organization of tasks items |
US10810274B2 (en) | 2017-05-15 | 2020-10-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US11080012B2 (en) | 2009-06-05 | 2021-08-03 | Apple Inc. | Interface for a virtual digital assistant |
US11217255B2 (en) | 2017-05-16 | 2022-01-04 | Apple Inc. | Far-field extension for digital assistant services |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
Families Citing this family (153)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9286294B2 (en) | 1992-12-09 | 2016-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content suggestion engine |
US7168084B1 (en) | 1992-12-09 | 2007-01-23 | Sedna Patent Services, Llc | Method and apparatus for targeting virtual objects |
US6633635B2 (en) | 1999-12-30 | 2003-10-14 | At&T Corp. | Multiple call waiting in a packetized communication system |
US6671262B1 (en) | 1999-12-30 | 2003-12-30 | At&T Corp. | Conference server for automatic x-way call port expansion feature |
US6826173B1 (en) | 1999-12-30 | 2004-11-30 | At&T Corp. | Enhanced subscriber IP alerting |
US6680935B1 (en) | 1999-12-30 | 2004-01-20 | At&T Corp. | Anonymous call rejection |
US6775273B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp. | Simplified IP service control |
US6690675B1 (en) | 1999-12-30 | 2004-02-10 | At&T Corp. | User programmable fail-proof IP hotline/warm-line |
US6728239B1 (en) | 1999-12-30 | 2004-04-27 | At&T Corp. | Scaleable network server for low cost PBX |
US6816469B1 (en) | 1999-12-30 | 2004-11-09 | At&T Corp. | IP conference call waiting |
US6678265B1 (en) | 1999-12-30 | 2004-01-13 | At&T Corp. | Local number portability database for on-net IP call |
US6775267B1 (en) | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US6671715B1 (en) | 2000-01-21 | 2003-12-30 | Microstrategy, Inc. | System and method for automatic, real-time delivery of personalized informational and transactional data to users via high throughput content delivery device |
US8024415B2 (en) | 2001-03-16 | 2011-09-20 | Microsoft Corporation | Priorities generation and management |
US7243130B2 (en) * | 2000-03-16 | 2007-07-10 | Microsoft Corporation | Notification platform architecture |
US7743340B2 (en) * | 2000-03-16 | 2010-06-22 | Microsoft Corporation | Positioning and rendering notification heralds based on user's focus of attention and activity |
US8701027B2 (en) * | 2000-03-16 | 2014-04-15 | Microsoft Corporation | Scope user interface for displaying the priorities and properties of multiple informational items |
US7634528B2 (en) | 2000-03-16 | 2009-12-15 | Microsoft Corporation | Harnessing information about the timing of a user's client-server interactions to enhance messaging and collaboration services |
US20020032020A1 (en) * | 2000-05-12 | 2002-03-14 | Brown Bonnie L. | Local and remote email alert apparatus and methods |
JP3489537B2 (en) * | 2000-05-16 | 2004-01-19 | 日本電気株式会社 | Function calling method and terminal device by keyword detection |
US8086672B2 (en) * | 2000-06-17 | 2011-12-27 | Microsoft Corporation | When-free messaging |
US7584033B2 (en) | 2000-08-31 | 2009-09-01 | Strategic Design Federation W. Inc. | Automobile monitoring for operation analysis |
US7181529B2 (en) * | 2000-09-22 | 2007-02-20 | Ericsson Inc. | Business to business engine and system for facilitating information interexchange using realtime data |
US7031437B1 (en) * | 2000-10-30 | 2006-04-18 | Nortel Networks Limited | Method and system for providing remote access to previously transmitted enterprise messages |
US20020052225A1 (en) * | 2000-11-01 | 2002-05-02 | Davis Derek L. | Feature timer functionality for a wireless communication unit |
US6928410B1 (en) * | 2000-11-06 | 2005-08-09 | Nokia Mobile Phones Ltd. | Method and apparatus for musical modification of speech signal |
DK200001706A (en) * | 2000-11-14 | 2002-05-15 | Bent Bjoern Dahl Christensen | Wireless monitoring device, monitoring system and method of using monitoring device and / or system. |
US7844666B2 (en) | 2000-12-12 | 2010-11-30 | Microsoft Corporation | Controls and displays for acquiring preferences, inspecting behavior, and guiding the learning and decision policies of an adaptive communications prioritization and routing system |
US8774380B2 (en) | 2001-02-27 | 2014-07-08 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
US8873730B2 (en) | 2001-02-27 | 2014-10-28 | Verizon Patent And Licensing Inc. | Method and apparatus for calendared communications flow control |
US8761363B2 (en) | 2001-02-27 | 2014-06-24 | Verizon Data Services Llc | Methods and systems for automatic forwarding of communications to a preferred device |
US20120106728A1 (en) * | 2001-02-27 | 2012-05-03 | Verizon Laboratories Inc. | Methods and systems for integrating communications services |
US8798251B2 (en) | 2001-02-27 | 2014-08-05 | Verizon Data Services Llc | Methods and systems for computer enhanced conference calling |
US8472428B2 (en) | 2001-02-27 | 2013-06-25 | Verizon Data Services Llc | Methods and systems for line management |
US8750482B2 (en) | 2001-02-27 | 2014-06-10 | Verizon Data Services Llc | Methods and systems for preemptive rejection of calls |
US8488761B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for a call log |
US7912193B2 (en) | 2001-02-27 | 2011-03-22 | Verizon Data Services Llc | Methods and systems for call management with user intervention |
US8503639B2 (en) * | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Method and apparatus for adaptive message and call notification |
US6976017B1 (en) * | 2001-02-27 | 2005-12-13 | Verizon Data Services Inc. | Method and apparatus for context based querying |
US8494135B2 (en) | 2001-02-27 | 2013-07-23 | Verizon Data Services Llc | Methods and systems for contact management |
US7912199B2 (en) | 2002-11-25 | 2011-03-22 | Telesector Resources Group, Inc. | Methods and systems for remote cell establishment |
US7903796B1 (en) | 2001-02-27 | 2011-03-08 | Verizon Data Services Llc | Method and apparatus for unified communication management via instant messaging |
US8503650B2 (en) | 2001-02-27 | 2013-08-06 | Verizon Data Services Llc | Methods and systems for configuring and providing conference calls |
US8488766B2 (en) | 2001-02-27 | 2013-07-16 | Verizon Data Services Llc | Methods and systems for multiuser selective notification |
US8751571B2 (en) | 2001-02-27 | 2014-06-10 | Verizon Data Services Llc | Methods and systems for CPN triggered collaboration |
US20060276179A1 (en) * | 2001-02-27 | 2006-12-07 | Reza Ghaffari | Methods and systems for integrating communications services |
US8467502B2 (en) | 2001-02-27 | 2013-06-18 | Verizon Data Services Llc | Interactive assistant for managing telephone communications |
US8472606B2 (en) | 2001-02-27 | 2013-06-25 | Verizon Data Services Llc | Methods and systems for directory information lookup |
US7024662B2 (en) | 2001-03-14 | 2006-04-04 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US7302634B2 (en) | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US7224774B1 (en) * | 2001-03-23 | 2007-05-29 | Aol Llc | Real-time call control system |
US6879838B2 (en) * | 2001-04-20 | 2005-04-12 | Koninklijke Philips Electronics N.V. | Distributed location based service system |
US8375411B2 (en) | 2001-06-27 | 2013-02-12 | Nokia Corporation | Cross-device sharing of reminders |
US6934367B1 (en) * | 2001-06-28 | 2005-08-23 | Bellsouth Intellectual Property Corporation | System and method for voicemail message certification and reply using a temporary voicemail service |
US7793326B2 (en) | 2001-08-03 | 2010-09-07 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator |
US7908628B2 (en) | 2001-08-03 | 2011-03-15 | Comcast Ip Holdings I, Llc | Video and digital multimedia aggregator content coding and formatting |
CN100471069C (en) * | 2001-10-03 | 2009-03-18 | Nxp股份有限公司 | Analogue to digital converter |
US20030119531A1 (en) * | 2001-12-21 | 2003-06-26 | Patton Charles M. | Dynamic selection of avatar policies based on physical device location and derived user control |
US9392120B2 (en) | 2002-02-27 | 2016-07-12 | Verizon Patent And Licensing Inc. | Methods and systems for call management with user intervention |
US7324638B2 (en) * | 2002-03-29 | 2008-01-29 | At&T Delaware Intellectual Property, Inc. | System and method for managing communications |
US7266190B1 (en) | 2002-03-29 | 2007-09-04 | At&T Intellectual Property, Inc. | System and method for managing communications |
US6825767B2 (en) | 2002-05-08 | 2004-11-30 | Charles Humbard | Subscription system for monitoring user well being |
US9886309B2 (en) * | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US20040076273A1 (en) * | 2002-10-18 | 2004-04-22 | Oman Paul W. | Text-to-voice system for communicating operational information from a protective device for a power system to a human user |
US7584114B2 (en) * | 2003-01-22 | 2009-09-01 | International Business Machines Corporation | System and method for integrating projects events with personal calendar and scheduling clients |
US7874983B2 (en) | 2003-01-27 | 2011-01-25 | Motorola Mobility, Inc. | Determination of emotional and physiological states of a recipient of a communication |
US7457879B2 (en) | 2003-04-01 | 2008-11-25 | Microsoft Corporation | Notification platform architecture |
US7515701B2 (en) * | 2003-06-02 | 2009-04-07 | Alcatel-Lucent Usa Inc. | Method and apparatus for screening calls from a telephony device |
US7334001B2 (en) * | 2003-06-13 | 2008-02-19 | Yahoo! Inc. | Method and system for data collection for alert delivery |
US7813488B2 (en) * | 2003-09-29 | 2010-10-12 | Siemens Enterprise Communications, Inc. | System and method for providing information regarding an identity's media availability |
US7373181B2 (en) * | 2003-10-24 | 2008-05-13 | Motorola, Inc. | Method and apparatus for sender controllable modalities |
US20050096095A1 (en) * | 2003-10-31 | 2005-05-05 | Benco David S. | Method and apparatus for network initiated event reminder alerting |
US7685265B1 (en) | 2003-11-20 | 2010-03-23 | Microsoft Corporation | Topic-based notification service |
US7877694B2 (en) * | 2003-12-05 | 2011-01-25 | Microsoft Corporation | Hosted notifications templates |
US20050129221A1 (en) * | 2003-12-11 | 2005-06-16 | Dickens James E. | Alerting of network-associated information associated with a telephone call |
US20050190744A1 (en) * | 2004-02-27 | 2005-09-01 | Xian-He Sun | Method of informing a callee of an attempted telephone call by means of internet protocol messaging |
US20050223074A1 (en) * | 2004-03-31 | 2005-10-06 | Morris Robert P | System and method for providing user selectable electronic message action choices and processing |
US20050227712A1 (en) * | 2004-04-13 | 2005-10-13 | Texas Instruments Incorporated | Handset meeting assistant |
US20050271186A1 (en) * | 2004-06-02 | 2005-12-08 | Audiopoint, Inc. | System, method and computer program product for interactive voice notification |
US7940746B2 (en) | 2004-08-24 | 2011-05-10 | Comcast Cable Holdings, Llc | Method and system for locating a voice over internet protocol (VoIP) device connected to a network |
US20060099945A1 (en) * | 2004-11-09 | 2006-05-11 | Sharp Laboratories Of America, Inc. | Using PIM calendar on a mobile device to configure the user profile |
US7925241B2 (en) | 2004-11-09 | 2011-04-12 | Sharp Laboratories Of America, Inc. | Using PIM calendar on a mobile device to configure a profile |
GB2421597A (en) * | 2004-12-17 | 2006-06-28 | Motorola Inc | Method and apparatus for alert management. |
GB2421333B (en) | 2004-12-17 | 2007-08-01 | Motorola Inc | An alert management apparatus and a method of alert management therefor |
US7873912B1 (en) * | 2005-02-25 | 2011-01-18 | Apple Inc. | Process and system for providing a reduced set of fields associated with a report layout |
US7353034B2 (en) | 2005-04-04 | 2008-04-01 | X One, Inc. | Location sharing and tracking using mobile phones or other wireless devices |
US7643620B1 (en) * | 2005-06-27 | 2010-01-05 | American Airlines, Inc. | System and method for notification of an event |
EP2086203A3 (en) | 2005-07-22 | 2009-10-28 | Huawei Technologies Co., Ltd. | Subscribing method and device |
US8365096B2 (en) * | 2007-12-31 | 2013-01-29 | Motorola Mobility Llc | Method and apparatus for transparently mapping personalized alert preferences onto thin client devices with differing capabilities |
CN102027721B (en) | 2008-04-02 | 2015-05-13 | 特维里奥公司 | System and method for processing telephony sessions |
US8837465B2 (en) | 2008-04-02 | 2014-09-16 | Twilio, Inc. | System and method for processing telephony sessions |
US8964726B2 (en) | 2008-10-01 | 2015-02-24 | Twilio, Inc. | Telephony web event system and method |
US8509415B2 (en) | 2009-03-02 | 2013-08-13 | Twilio, Inc. | Method and system for a multitenancy telephony network |
EP2404412B1 (en) | 2009-03-02 | 2019-05-01 | Twilio Inc. | Method and system for a multitenancy telephone network |
US20110083179A1 (en) * | 2009-10-07 | 2011-04-07 | Jeffrey Lawson | System and method for mitigating a denial of service attack using cloud computing |
US9210275B2 (en) | 2009-10-07 | 2015-12-08 | Twilio, Inc. | System and method for running a multi-module telephony application |
US8582737B2 (en) * | 2009-10-07 | 2013-11-12 | Twilio, Inc. | System and method for running a multi-module telephony application |
CN102804700B (en) | 2010-01-19 | 2015-04-15 | 特维里奥公司 | Method and system for preserving telephony session state |
WO2011149558A2 (en) | 2010-05-28 | 2011-12-01 | Abelow Daniel H | Reality alternate |
US9459926B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US20120208495A1 (en) | 2010-06-23 | 2012-08-16 | Twilio, Inc. | System and method for monitoring account usage on a platform |
US8416923B2 (en) | 2010-06-23 | 2013-04-09 | Twilio, Inc. | Method for providing clean endpoint addresses |
US9590849B2 (en) | 2010-06-23 | 2017-03-07 | Twilio, Inc. | System and method for managing a computing cluster |
US9338064B2 (en) | 2010-06-23 | 2016-05-10 | Twilio, Inc. | System and method for managing a computing cluster |
US9459925B2 (en) | 2010-06-23 | 2016-10-04 | Twilio, Inc. | System and method for managing a computing cluster |
US8838707B2 (en) | 2010-06-25 | 2014-09-16 | Twilio, Inc. | System and method for enabling real-time eventing |
US9749176B2 (en) * | 2010-06-29 | 2017-08-29 | Nokia Technologies Oy | Systems, methods, and apparatuses for providing adaptive user notifications |
US20120030586A1 (en) * | 2010-07-30 | 2012-02-02 | Neel Ketkar | Systems and methods for sharing media using social media guidance applications |
US20120030587A1 (en) * | 2010-07-30 | 2012-02-02 | Neel Ketkar | Systems and methods for sharing media using social media guidance applications |
US8649268B2 (en) | 2011-02-04 | 2014-02-11 | Twilio, Inc. | Method for processing telephony sessions of a network |
US20140044123A1 (en) | 2011-05-23 | 2014-02-13 | Twilio, Inc. | System and method for real time communicating with a client application |
US9648006B2 (en) | 2011-05-23 | 2017-05-09 | Twilio, Inc. | System and method for communicating with a client application |
US9398622B2 (en) | 2011-05-23 | 2016-07-19 | Twilio, Inc. | System and method for connecting a communication to a client |
US8915704B2 (en) | 2011-06-15 | 2014-12-23 | Honeywell International Inc. | Turbocharger variable-nozzle assembly with vane sealing ring |
US10182147B2 (en) | 2011-09-21 | 2019-01-15 | Twilio Inc. | System and method for determining and communicating presence information |
EP2759123B1 (en) | 2011-09-21 | 2018-08-15 | Twilio, Inc. | System and method for authorizing and connecting application developers and users |
US9495227B2 (en) | 2012-02-10 | 2016-11-15 | Twilio, Inc. | System and method for managing concurrent events |
US20130210394A1 (en) * | 2012-02-14 | 2013-08-15 | Keyona Juliano Stokes | 1800 number that connects to the internet and mobile devises |
US9602586B2 (en) | 2012-05-09 | 2017-03-21 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US20130304928A1 (en) | 2012-05-09 | 2013-11-14 | Twilio, Inc. | System and method for managing latency in a distributed telephony network |
US9240941B2 (en) | 2012-05-09 | 2016-01-19 | Twilio, Inc. | System and method for managing media in a distributed communication network |
US9247062B2 (en) | 2012-06-19 | 2016-01-26 | Twilio, Inc. | System and method for queuing a communication session |
US8737962B2 (en) | 2012-07-24 | 2014-05-27 | Twilio, Inc. | Method and system for preventing illicit use of a telephony platform |
US8738051B2 (en) | 2012-07-26 | 2014-05-27 | Twilio, Inc. | Method and system for controlling message routing |
US8938053B2 (en) | 2012-10-15 | 2015-01-20 | Twilio, Inc. | System and method for triggering on platform usage |
US8948356B2 (en) | 2012-10-15 | 2015-02-03 | Twilio, Inc. | System and method for routing communications |
US9253254B2 (en) | 2013-01-14 | 2016-02-02 | Twilio, Inc. | System and method for offering a multi-partner delegated platform |
US9282124B2 (en) | 2013-03-14 | 2016-03-08 | Twilio, Inc. | System and method for integrating session initiation protocol communication in a telecommunications platform |
US9001666B2 (en) | 2013-03-15 | 2015-04-07 | Twilio, Inc. | System and method for improving routing in a distributed communication platform |
US9338280B2 (en) | 2013-06-19 | 2016-05-10 | Twilio, Inc. | System and method for managing telephony endpoint inventory |
US9160696B2 (en) | 2013-06-19 | 2015-10-13 | Twilio, Inc. | System for transforming media resource into destination device compatible messaging format |
US9225840B2 (en) | 2013-06-19 | 2015-12-29 | Twilio, Inc. | System and method for providing a communication endpoint information service |
US9483328B2 (en) | 2013-07-19 | 2016-11-01 | Twilio, Inc. | System and method for delivering application content |
US9137127B2 (en) | 2013-09-17 | 2015-09-15 | Twilio, Inc. | System and method for providing communication platform metadata |
US9338018B2 (en) | 2013-09-17 | 2016-05-10 | Twilio, Inc. | System and method for pricing communication of a telecommunication platform |
US9274858B2 (en) | 2013-09-17 | 2016-03-01 | Twilio, Inc. | System and method for tagging and tracking events of an application platform |
US9325624B2 (en) | 2013-11-12 | 2016-04-26 | Twilio, Inc. | System and method for enabling dynamic multi-modal communication |
US9553799B2 (en) | 2013-11-12 | 2017-01-24 | Twilio, Inc. | System and method for client communication in a distributed telephony network |
EP2890087B1 (en) * | 2013-12-27 | 2016-08-03 | Telefonica S.A. | System for notifying subscriber devices in ISP networks |
US9344573B2 (en) | 2014-03-14 | 2016-05-17 | Twilio, Inc. | System and method for a work distribution service |
US9226217B2 (en) | 2014-04-17 | 2015-12-29 | Twilio, Inc. | System and method for enabling multi-modal communication |
US9516101B2 (en) | 2014-07-07 | 2016-12-06 | Twilio, Inc. | System and method for collecting feedback in a multi-tenant communication platform |
US9246694B1 (en) | 2014-07-07 | 2016-01-26 | Twilio, Inc. | System and method for managing conferencing in a distributed communication network |
US9251371B2 (en) | 2014-07-07 | 2016-02-02 | Twilio, Inc. | Method and system for applying data retention policies in a computing platform |
US9774687B2 (en) | 2014-07-07 | 2017-09-26 | Twilio, Inc. | System and method for managing media and signaling in a communication platform |
US9363301B2 (en) | 2014-10-21 | 2016-06-07 | Twilio, Inc. | System and method for providing a micro-services communication platform |
US9477975B2 (en) | 2015-02-03 | 2016-10-25 | Twilio, Inc. | System and method for a media intelligence platform |
US9948703B2 (en) | 2015-05-14 | 2018-04-17 | Twilio, Inc. | System and method for signaling through data storage |
US10419891B2 (en) | 2015-05-14 | 2019-09-17 | Twilio, Inc. | System and method for communicating through multiple endpoints |
US10659349B2 (en) | 2016-02-04 | 2020-05-19 | Twilio Inc. | Systems and methods for providing secure network exchanged for a multitenant virtual private cloud |
US10063713B2 (en) | 2016-05-23 | 2018-08-28 | Twilio Inc. | System and method for programmatic device connectivity |
US10686902B2 (en) | 2016-05-23 | 2020-06-16 | Twilio Inc. | System and method for a multi-channel notification service |
US20230342540A1 (en) * | 2022-04-21 | 2023-10-26 | Black Hills Ip Holdings, Llc | Method and apparatus for generating a document and data processing |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5375161A (en) * | 1984-09-14 | 1994-12-20 | Accessline Technologies, Inc. | Telephone control system with branch routing |
US4757529A (en) * | 1986-02-28 | 1988-07-12 | American Telephone And Telegraph Company, At&T Bell Laboratories | Call distribution arrangement |
US5029196A (en) * | 1988-07-11 | 1991-07-02 | Dytel Corporation | Automated call screening |
US5329578A (en) * | 1992-05-26 | 1994-07-12 | Northern Telecom Limited | Personal communication service with mobility manager |
US5742905A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Personal communications internetworking |
WO1997020423A1 (en) * | 1995-11-29 | 1997-06-05 | Bell Communications Research, Inc. | A system and method for automatically screening and directing incoming calls |
US5933778A (en) * | 1996-06-04 | 1999-08-03 | At&T Wireless Services Inc. | Method and apparatus for providing telecommunication services based on a subscriber profile updated by a personal information manager |
US5943607A (en) * | 1996-10-17 | 1999-08-24 | Lucent Technologies Inc. | Automatically notifying messaging device users of selected incoming calls to a telephone set |
US5930702A (en) * | 1996-10-22 | 1999-07-27 | At&T Corp. | Personal mobility communication system |
JP2894316B2 (en) * | 1997-03-24 | 1999-05-24 | 日本電気株式会社 | Communication terminal, subscriber calling method and mobility information updating method |
US6295447B1 (en) * | 1998-12-31 | 2001-09-25 | Ericsson Inc. | Method and system for enabling the control of execution of features in a telecommunications network |
US6459913B2 (en) * | 1999-05-03 | 2002-10-01 | At&T Corp. | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
-
1999
- 1999-05-03 US US09/303,517 patent/US6459913B2/en not_active Expired - Lifetime
-
2000
- 2000-04-06 CA CA002304355A patent/CA2304355C/en not_active Expired - Fee Related
- 2000-04-25 EP EP00303419A patent/EP1051019A2/en not_active Withdrawn
- 2000-04-26 BR BR0007098-0A patent/BR0007098A/en not_active Application Discontinuation
Cited By (145)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6459913B2 (en) * | 1999-05-03 | 2002-10-01 | At&T Corp. | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions |
US7139827B1 (en) * | 1999-10-20 | 2006-11-21 | Fujitsu Limited | Communication means notification method and notification system |
US20090099992A1 (en) * | 2000-03-16 | 2009-04-16 | Microsoft Corporation | Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information |
US8566413B2 (en) * | 2000-03-16 | 2013-10-22 | Microsoft Corporation | Bounded-deferral policies for guiding the timing of alerting, interaction and communications using local sensory information |
US9646614B2 (en) | 2000-03-16 | 2017-05-09 | Apple Inc. | Fast, language-independent method for user authentication by voice |
US20020059073A1 (en) * | 2000-06-07 | 2002-05-16 | Zondervan Quinton Y. | Voice applications and voice-based interface |
US7334050B2 (en) * | 2000-06-07 | 2008-02-19 | Nvidia International, Inc. | Voice applications and voice-based interface |
WO2002031726A1 (en) * | 2000-10-12 | 2002-04-18 | Worldspan, L.P. | Method, computer program, and system for pushing flight information to passengers |
US20050038853A1 (en) * | 2001-10-05 | 2005-02-17 | Dominique Blanc | Communication of messages in a system |
US7644152B2 (en) * | 2001-10-05 | 2010-01-05 | Abb Ab | Communication of messages in a system |
US20040003048A1 (en) * | 2002-03-20 | 2004-01-01 | Bellsouth Intellectual Property Corporation | Outbound notification using customer profile information |
US7996481B2 (en) * | 2002-03-20 | 2011-08-09 | At&T Intellectual Property I, L.P. | Outbound notification using customer profile information |
US7181252B2 (en) * | 2002-12-10 | 2007-02-20 | Nokia Corporation | System and method for performing security functions of a mobile station |
US20040110488A1 (en) * | 2002-12-10 | 2004-06-10 | Nokia Corporation | System and method for performing security functions of a mobile station |
US20130028402A1 (en) * | 2004-02-06 | 2013-01-31 | At&T Intellectual Property I. L.P. | System and Method for Broadcasting Packetized Voice Messages |
US8605866B2 (en) * | 2004-02-06 | 2013-12-10 | AT&T Intellectual Property I, L.L.P. | System and method for broadcasting packetized voice messages |
US20060036702A1 (en) * | 2004-07-02 | 2006-02-16 | Theimer Gerhard K | Personal notification device |
US10318871B2 (en) | 2005-09-08 | 2019-06-11 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US7869795B2 (en) * | 2006-03-20 | 2011-01-11 | Kamfu Wong | System and method for informing a user of the arrival of an email at an email server via mobile phone |
US20080318553A1 (en) * | 2006-04-26 | 2008-12-25 | Kamfu Wong | System and Method for Receiving Emails in Instantly Via a Mobile Phone |
US8645463B2 (en) * | 2006-09-25 | 2014-02-04 | Cisco Technology, Inc. | Methods and apparatuses for managing resources within a virtual room |
US20080075118A1 (en) * | 2006-09-25 | 2008-03-27 | David Knight | Methods and apparatuses for managing resources within a virtual room |
US8682280B1 (en) * | 2006-10-17 | 2014-03-25 | At&T Mobility Ii Llc | Selectable processing of broadcast EAS messages |
US20090238088A1 (en) * | 2008-03-19 | 2009-09-24 | Oki Electric Industry Co., Ltd. | Network traffic analyzing device, network traffic analyzing method and network traffic analyzing system |
US9865248B2 (en) | 2008-04-05 | 2018-01-09 | Apple Inc. | Intelligent text-to-speech conversion |
US9626955B2 (en) | 2008-04-05 | 2017-04-18 | Apple Inc. | Intelligent text-to-speech conversion |
US11080012B2 (en) | 2009-06-05 | 2021-08-03 | Apple Inc. | Interface for a virtual digital assistant |
US10795541B2 (en) | 2009-06-05 | 2020-10-06 | Apple Inc. | Intelligent organization of tasks items |
US10283110B2 (en) | 2009-07-02 | 2019-05-07 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US10706841B2 (en) | 2010-01-18 | 2020-07-07 | Apple Inc. | Task flow identification based on user intent |
US11423886B2 (en) | 2010-01-18 | 2022-08-23 | Apple Inc. | Task flow identification based on user intent |
US10049675B2 (en) | 2010-02-25 | 2018-08-14 | Apple Inc. | User profiling for voice input processing |
US9633660B2 (en) | 2010-02-25 | 2017-04-25 | Apple Inc. | User profiling for voice input processing |
US8560689B2 (en) | 2010-11-02 | 2013-10-15 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8898299B2 (en) | 2010-11-02 | 2014-11-25 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8825852B2 (en) | 2010-11-02 | 2014-09-02 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system |
US8627154B2 (en) | 2010-12-06 | 2014-01-07 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US8621277B2 (en) | 2010-12-06 | 2013-12-31 | International Business Machines Corporation | Dynamic administration of component event reporting in a distributed processing system |
US8805999B2 (en) | 2010-12-07 | 2014-08-12 | International Business Machines Corporation | Administering event reporting rules in a distributed processing system |
US8868984B2 (en) | 2010-12-07 | 2014-10-21 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system with event listeners and alert listeners |
US8868986B2 (en) | 2010-12-07 | 2014-10-21 | International Business Machines Corporation | Relevant alert delivery in a distributed processing system with event listeners and alert listeners |
US8737231B2 (en) | 2010-12-07 | 2014-05-27 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US8730816B2 (en) | 2010-12-07 | 2014-05-20 | International Business Machines Corporation | Dynamic administration of event pools for relevant event and alert analysis during event storms |
US10102359B2 (en) | 2011-03-21 | 2018-10-16 | Apple Inc. | Device access using voice authentication |
US8756462B2 (en) | 2011-05-24 | 2014-06-17 | International Business Machines Corporation | Configurable alert delivery for reducing the amount of alerts transmitted in a distributed processing system |
US8645757B2 (en) | 2011-05-26 | 2014-02-04 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8639980B2 (en) | 2011-05-26 | 2014-01-28 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US9201756B2 (en) | 2011-05-27 | 2015-12-01 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US8676883B2 (en) | 2011-05-27 | 2014-03-18 | International Business Machines Corporation | Event management in a distributed processing system |
US9344381B2 (en) | 2011-05-27 | 2016-05-17 | International Business Machines Corporation | Event management in a distributed processing system |
US9213621B2 (en) | 2011-05-27 | 2015-12-15 | International Business Machines Corporation | Administering event pools for relevant event analysis in a distributed processing system |
US8880943B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US9419650B2 (en) | 2011-06-22 | 2016-08-16 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8880944B2 (en) | 2011-06-22 | 2014-11-04 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8660995B2 (en) | 2011-06-22 | 2014-02-25 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US8713366B2 (en) | 2011-06-22 | 2014-04-29 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US8689050B2 (en) | 2011-06-22 | 2014-04-01 | International Business Machines Corporation | Restarting event and alert analysis after a shutdown in a distributed processing system |
US9286143B2 (en) | 2011-06-22 | 2016-03-15 | International Business Machines Corporation | Flexible event data content management for relevant event and alert analysis within a distributed processing system |
US10162495B2 (en) * | 2011-10-04 | 2018-12-25 | Verizon Patent And Licensing Inc. | Customizable vehicle fleet reporting system |
US20160110066A1 (en) * | 2011-10-04 | 2016-04-21 | Telogis, Inc. | Customizable vehicle fleet reporting system |
US9246865B2 (en) | 2011-10-18 | 2016-01-26 | International Business Machines Corporation | Prioritized alert delivery in a distributed processing system |
US8893157B2 (en) | 2011-10-18 | 2014-11-18 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US8688769B2 (en) | 2011-10-18 | 2014-04-01 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8887175B2 (en) | 2011-10-18 | 2014-11-11 | International Business Machines Corporation | Administering incident pools for event and alert analysis |
US9178937B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US9178936B2 (en) | 2011-10-18 | 2015-11-03 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US8713581B2 (en) | 2011-10-27 | 2014-04-29 | International Business Machines Corporation | Selected alert delivery in a distributed processing system |
US9953088B2 (en) | 2012-05-14 | 2018-04-24 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US10079014B2 (en) | 2012-06-08 | 2018-09-18 | Apple Inc. | Name recognition system |
US8954811B2 (en) | 2012-08-06 | 2015-02-10 | International Business Machines Corporation | Administering incident pools for incident analysis |
US8943366B2 (en) | 2012-08-09 | 2015-01-27 | International Business Machines Corporation | Administering checkpoints for incident analysis |
US9971774B2 (en) | 2012-09-19 | 2018-05-15 | Apple Inc. | Voice-based media searching |
US9104995B1 (en) * | 2012-09-28 | 2015-08-11 | Emc Corporation | Subject and audience oriented instant collaborative development |
US20140200739A1 (en) * | 2013-01-15 | 2014-07-17 | Honda Motor Co., Ltd. | Enhancing vehicle connectivity |
US10078487B2 (en) * | 2013-03-15 | 2018-09-18 | Apple Inc. | Context-sensitive handling of interruptions |
KR102057795B1 (en) * | 2013-03-15 | 2019-12-19 | 애플 인크. | Context-sensitive handling of interruptions |
KR101904293B1 (en) * | 2013-03-15 | 2018-10-05 | 애플 인크. | Context-sensitive handling of interruptions |
US20140282003A1 (en) * | 2013-03-15 | 2014-09-18 | Apple Inc. | Context-sensitive handling of interruptions |
US9361184B2 (en) | 2013-05-09 | 2016-06-07 | International Business Machines Corporation | Selecting during a system shutdown procedure, a restart incident checkpoint of an incident analyzer in a distributed processing system |
US9620104B2 (en) | 2013-06-07 | 2017-04-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
US9966060B2 (en) | 2013-06-07 | 2018-05-08 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9966068B2 (en) | 2013-06-08 | 2018-05-08 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
US10657961B2 (en) | 2013-06-08 | 2020-05-19 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
US10185542B2 (en) | 2013-06-09 | 2019-01-22 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US9170860B2 (en) | 2013-07-26 | 2015-10-27 | International Business Machines Corporation | Parallel incident processing |
US9658902B2 (en) | 2013-08-22 | 2017-05-23 | Globalfoundries Inc. | Adaptive clock throttling for event processing |
US9256482B2 (en) | 2013-08-23 | 2016-02-09 | International Business Machines Corporation | Determining whether to send an alert in a distributed processing system |
US10171289B2 (en) | 2013-09-11 | 2019-01-01 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9086968B2 (en) | 2013-09-11 | 2015-07-21 | International Business Machines Corporation | Checkpointing for delayed alert creation |
US9602337B2 (en) | 2013-09-11 | 2017-03-21 | International Business Machines Corporation | Event and alert analysis in a distributed processing system |
US9389943B2 (en) | 2014-01-07 | 2016-07-12 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US9348687B2 (en) | 2014-01-07 | 2016-05-24 | International Business Machines Corporation | Determining a number of unique incidents in a plurality of incidents for incident processing in a distributed processing system |
US10169329B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Exemplar-based natural language processing |
US9668024B2 (en) | 2014-06-30 | 2017-05-30 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US10904611B2 (en) | 2014-06-30 | 2021-01-26 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US9986419B2 (en) | 2014-09-30 | 2018-05-29 | Apple Inc. | Social reminders |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9519931B2 (en) * | 2015-05-15 | 2016-12-13 | Ebay Inc. | System and method for personalized actionable notifications |
US10356243B2 (en) | 2015-06-05 | 2019-07-16 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US11500672B2 (en) | 2015-09-08 | 2022-11-15 | Apple Inc. | Distributed personal assistant |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US11526368B2 (en) | 2015-11-06 | 2022-12-13 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US20170195442A1 (en) * | 2016-01-05 | 2017-07-06 | Samsung Electronics Co., Ltd. | Electronic device and method for controlling the electronic device |
US10306004B2 (en) | 2016-01-05 | 2019-05-28 | Samsung Electronics Co., Ltd. | Electronic device and method for controlling the electronic device |
CN108476262A (en) * | 2016-01-05 | 2018-08-31 | 三星电子株式会社 | Electronic equipment and method for control electronics |
US10148778B2 (en) * | 2016-01-05 | 2018-12-04 | Samsung Electronics Co., Ltd. | Electronic device and method for controlling the electronic device |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
US20170272505A1 (en) * | 2016-03-17 | 2017-09-21 | Disney Enterprises, Inc. | System and method for leveraging machine learning to deliver time-sensitive content over optimal devices and channels |
US11561671B2 (en) * | 2016-03-17 | 2023-01-24 | Disney Enterprises, Inc. | System and method for leveraging machine learning to deliver time-sensitive content over optimal devices and channels |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
US11069347B2 (en) | 2016-06-08 | 2021-07-20 | Apple Inc. | Intelligent automated assistant for media exploration |
US10354011B2 (en) | 2016-06-09 | 2019-07-16 | Apple Inc. | Intelligent automated assistant in a home environment |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10733993B2 (en) | 2016-06-10 | 2020-08-04 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
US11037565B2 (en) | 2016-06-10 | 2021-06-15 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10269345B2 (en) | 2016-06-11 | 2019-04-23 | Apple Inc. | Intelligent task discovery |
US11152002B2 (en) | 2016-06-11 | 2021-10-19 | Apple Inc. | Application integration with a digital assistant |
US10521466B2 (en) | 2016-06-11 | 2019-12-31 | Apple Inc. | Data driven natural language event detection and classification |
US10089072B2 (en) | 2016-06-11 | 2018-10-02 | Apple Inc. | Intelligent device arbitration and control |
US10297253B2 (en) | 2016-06-11 | 2019-05-21 | Apple Inc. | Application integration with a digital assistant |
US10553215B2 (en) | 2016-09-23 | 2020-02-04 | Apple Inc. | Intelligent automated assistant |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
US10755703B2 (en) | 2017-05-11 | 2020-08-25 | Apple Inc. | Offline personal assistant |
US11405466B2 (en) | 2017-05-12 | 2022-08-02 | Apple Inc. | Synchronization and task delegation of a digital assistant |
US10410637B2 (en) | 2017-05-12 | 2019-09-10 | Apple Inc. | User-specific acoustic models |
US10791176B2 (en) | 2017-05-12 | 2020-09-29 | Apple Inc. | Synchronization and task delegation of a digital assistant |
US10810274B2 (en) | 2017-05-15 | 2020-10-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
US10482874B2 (en) | 2017-05-15 | 2019-11-19 | Apple Inc. | Hierarchical belief states for digital assistants |
US11217255B2 (en) | 2017-05-16 | 2022-01-04 | Apple Inc. | Far-field extension for digital assistant services |
Also Published As
Publication number | Publication date |
---|---|
CA2304355C (en) | 2003-08-26 |
EP1051019A2 (en) | 2000-11-08 |
CA2304355A1 (en) | 2000-11-03 |
BR0007098A (en) | 2001-08-07 |
US6459913B2 (en) | 2002-10-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6459913B2 (en) | Unified alerting device and method for alerting a subscriber in a communication network based upon the result of logical functions | |
US5903845A (en) | Personal information manager for updating a telecommunication subscriber profile | |
JP3373214B2 (en) | Method and apparatus for providing telecommunications services | |
US8194833B2 (en) | System and method for dynamically routing communications | |
EP1255414B1 (en) | Automatic SMS handling | |
KR100310376B1 (en) | Personal communications internetworking | |
US6493431B1 (en) | Method and system for capturing telephone calls | |
US6359970B1 (en) | Communications control method and apparatus | |
US5930702A (en) | Personal mobility communication system | |
US6954781B2 (en) | Messaging system for directing a server to convert voice message into text and appending a converted text message to another converted text message | |
JP4944415B2 (en) | COMMUNICATION SYSTEM, PRESENCE SERVER, AND COMMUNICATION METHOD USED FOR THEM | |
US20060031326A1 (en) | Managing personal communications from a calendar scheduling application | |
US6622021B1 (en) | System and method for implementing an automated communication response service | |
MXPA98000830A (en) | Personal information administrator to update a telecommunication subscriber profile | |
CN1134775A (en) | System and method for prioritized routing of telephone calls to a subscriber | |
KR20090132613A (en) | Pre-programmed subscriber response | |
JPH07303146A (en) | Caller information notifying system | |
KR20100033565A (en) | Method and device for registration and application of spam phone number | |
JP3388893B2 (en) | Personal communication service device | |
EP1096807A2 (en) | Call routing based on alarm reports | |
US20030035515A1 (en) | Method and device for transmitting messages in an intelligent network | |
EP0996271A2 (en) | Active answering machine | |
JPH05136725A (en) | Mobile radio communication system | |
US20120163560A1 (en) | Emergency communications controller and protocol | |
KR20070059315A (en) | System and its method for providing caller's telephone number during callee's absence in wire telephone |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: AT&T CORP., NEW YORK Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CLOUTIER, JOCELYN;REEL/FRAME:009946/0057 Effective date: 19990416 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |