jocelyn cloutier michael kocheisen jean tessier francois mcneil [email protected] 6/8/99
TRANSCRIPT
Wouldn’t it be nice?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?”
WHAT IS UNIFIED ALERTING?WHAT IS UNIFIED ALERTING?
It’s a service which…
Stores, filters, and forwards alerts to subscribers
Allows subscribers to control and receive alerts on any alert-ready device in near real-time
Receives alerts about any communication or information event (e.g. phone call, email, etc.)...
Allows information providers to send, update, and schedule alerts for an unlimited number of recipients.
ALERT USESALERT USES
Alerts can serve as primary events with original information.
Alerts can refer to communicationor information events.
HOW IT WORKS: AN EXAMPLEHOW IT WORKS: AN EXAMPLE
MAJOR CUSTOMER BENEFITSMAJOR CUSTOMER BENEFITS
Timely alerts about important network events • Alerts are optimized to subscriber’s device.
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 alertsUser-made filters screen alerts according to their importance (sender, subject, delivery time, etc.)
2 years of Alerting2 years of AlertingV1 (11/97)
Mostly client-basedSmart alerts (self-update, expiration, …)Customized email servers
V2 (8/98) scaleable, robustNetwork-basedSupport for Pagers, SMS, Phone, ICQ, ...Web UI for GeeksSMTP to Alert conversion (copy-forward of email)
V3 (6/99) scaleable, EXTENSIBLE, robustRe-implementation of V23rd party service integrationNon-Geek Web UI (Generic, WorldNet specific)
User ExperienceUser 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!
OverviewOverview
Incoming Alert
Alert Server
Alerted Device
DISPATCHER ARCHITECTUREDISPATCHER ARCHITECTURE
Challenges in bringingChallenges in bringingAlerting to the MassesAlerting 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.
IntegrationIntegration
PROBLEMS:
• Get alerts from 3rd parties
• Get alerts from any email server
• Get Alert Format Standardized
Current StateCurrent State
Alerting System6/1/99: Version 3.0 release (scalable and robust)
WorldNetSummer’99: Deployment
Other AT&T’s Business Unit4Q99: Deployment
Goals Goals ([email protected])([email protected])
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)