Alert%20Gateway%20Group%20(AGG)

1
Alert Gateway Group (AGG)

• Status Report to the Commercial Mobile Service
  Alert Advisory Committee
• March 12, 2007
• Anthony Melone, AGG Leader

2
AGG Mission Statement

• Draft requirements for interfacing to alerting
  systems recommended by the AIG.
• Recommend methods by which alerts received from
  target systems are processed and formatted for
  distribution over CMS systems. Processing of
  alerts will depend upon attributes such as
• User specific data (e.g. whether a user has
  chosen to opt out of an alerting class)
• Statutory requirements associated with user
  groups
• Methods by which alerts may be targeted to
  regional or local areas
• Procedures required for the maintenance of
  critical data on an ongoing basis and
• Handling of alert priorities as indicated by the
  AIG.
• Draft recommendations to address possible unique
  interfaces associated with different CMS
  technologies and service providers.
• Identify and make recommendations on any other
  requirements concerning communications or
  transactions between CMS alerting platforms and
  external alerting systems and agencies or
  specific data required for fulfillment of the
  groups primary mission.

3
AGG Participation

• AGG members include
• Verizon Wireless (Group Leader)
• CTIA (Deputy Group Leader)
• ATIS
• Cingular
• DHS
• Intrado
• Motorola
• Sprint Nextel
• Syniverse
• TIA
• VeriSign

4
AGG Status

• AGG held two meetings in Washington DC on Jan
  2007 and Feb 2007
• Adopted the working procedures for the informal
  working group
• Developed schedule for the monthly face-to-face
  meetings
• Defined project plan
• Current status On schedule
• Formed Technical Sub-group for in-depth technical
  matter discussion
• Scheduled bi-weekly technical meetings with
  goals/plans for each meeting
• Discussed the system requirement outline
• Assigned working items to AGG members and SMEs
• Discussed the network architecture
• Determined that a single alerting aggregator to
  distribute the alerts to the carriers networks
  is required
• In the process of analyzing CAP parameters to be
  mapped into the alert service profile being
  defined by CTG
• Defined the AGG Working Assumptions
• Support multiple protocols
• Support protocol mapping
• Support protocol evolution
• Identified the key deliverables
• GW System Requirements

5
AGG Working Assumptions

• The GW shall support multiple media profiles
  (text, audio, video, multimedia) from the
  Alerting Interfaces (input protocols to be
  identified by Alerting Interface Group).
• The GW shall support multiple media profiles
  (text, audio, video, multimedia) to the carriers
  networks (output protocols to be identified by
  Communication Technology Group).
• The GW shall support protocol mapping from the
  input to the output protocols.
• The GW shall format messages properly so that
  carriers should not be required to modify or edit
  the alert message content.
• The GW shall support sending geographical alerts
  to carriers network and let carriers
  disseminate the alert messages based on
  geo-information.
• The GW shall have an architecture to support GW
  deployment with redundancy and reliability.
• Multiple access points and delivery points
• Multiple platforms (mated-pair at the same site)
• Multiple sites (geo-redundancy)
• Multiple vendors (number of vendors to be further
  discussed)
• All GWs shall use the same format and same
  message identifier when sending the same message
  to carriers network. This should allow carrier
  to identify and ignore duplicated alerts.

6
Project Timeline