Jocelyn Cloutier Michael Kocheisen Jean Tessier Francois McNeil jocelyn@att 6/8/99

1. Jocelyn Cloutier Michael Kocheisen Jean Tessier Francois McNeil jocelyn@att.com 6/8/99

2. Wouldn’t it be nice? • Get alerted anywhere, anytime about any important event? • Incoming Phone call from an important client! • Important New email, voice mail or FAX! • Your flight is 3 hour late! • Control if, when and how you are alerted? • YOU select WHEN NOT to be alerted! • YOU select WHAT triggers an alert! • All this control with minimal intervention? • Intelligent agent checks your PIM • e.g. “No alert during your board meeting?”

3. WHAT IS UNIFIED ALERTING? It’s a service which… Receives alerts about any communication or information event (e.g. phone call, email, etc.)... Stores, filters, and forwards alerts to subscribers Allowssubscribers to control and receive alerts on any alert-ready device in near real-time Allowsinformation providers to send, update, and schedule alerts for an unlimited number of recipients.

4. ALERT USES Alerts can refer to communication or information events. Alerts can serve as primary eventswith original information.

5. HOW IT WORKS: AN EXAMPLE

6. MAJOR CUSTOMER BENEFITS • Timely alerts about important network events • Alerts are optimized to subscriber’sdevice. • Subscribers won’t need to check their voice mail, email or Fax. • Subscriber does not have to take action to receive an alert. • Subscribers won’t be interrupted by non-urgent alerts • User-made filters screen alerts according to their importance (sender, subject, delivery time, etc.)

7. 2 years of Alerting • V1 (11/97) • Mostly client-based • Smart alerts (self-update, expiration, …) • Customized email servers • V2 (8/98) scaleable, robust • Network-based • Support for Pagers, SMS, Phone, ICQ, ... • Web UI for Geeks • SMTP to Alert conversion (copy-forward of email) • V3 (6/99) scaleable, EXTENSIBLE, robust • Re-implementation of V2 • 3rd party service integration • Non-Geek Web UI (Generic, WorldNet specific)

8. User Experience • User Goes to Web Site • Register • Specify “receivers” (pagers, phone numbers, SMS) • Each has an activated time interval • Specify “rules” (if, when and how to be alerted) • When “this” is true, alert me on those devices! • List of rules: first “true” win all!

9. Overview Incoming Alert Alert Server Alerted Device

10. DISPATCHER ARCHITECTURE

11. Challenges in bringing Alerting to the Masses • FACTS • Alerting is only as interesting as its SOURCES. • Customers hate configuration! • You must let users tell the system what event is important to them. • Supporting “receivers” is easy.

12. Integration • PROBLEMS: • Get alerts from 3rd parties • Get alerts from any email server • Get Alert Format Standardized

13. Current State • Alerting System • 6/1/99: Version 3.0 release (scalable and robust) • WorldNet • Summer’99: Deployment • Other AT&T’s Business Unit • 4Q99: Deployment

14. Goals (jocelyn@att.com) • Short Term (< 6 months): • Focus on 3rd party’s system integration • SDK • Open API • Availability of Test Systems • Collaboration with Internet Portals • Longer Term (> 6 months): • Integration with PIM (e.g. MS Exchange) • TV as alert receiver • Presence Information (alert, filtering and delivery)