1 / 6

AGG Status Report to CMS Advisory Committee

This status report outlines the progress and goals of the Alert Gateway Group (AGG) in developing requirements and recommendations for interfacing with alerting systems. It includes updates on meetings, working assumptions, deliverables, and the project timeline.

chucke
Download Presentation

AGG Status Report to CMS Advisory Committee

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 group’s 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 • Interfaces to alerting authorities • Interfaces to the carriers’ networks • Protocols Mapping • System Reliability and Redundancy • Proof of Performance Requirements • Security Requirement

  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. 1Q’07 1Q-2Q’07 3Q’07 Oct 12,2007 • Define Key Deliverables • Define Project Plan • Define EAS Service Requirements • Schedule monthly WG meetings • Schedule bi-weekly technical meeting • Define GW System Requirements • Define GW Interfaces to alerting authorities • Define GW interfaces to carriers’ network • Define GW Protocols Mapping Requirements • System Reliability and Redundancy • Proof of Performance Testing • Security Requirements • Complete Deliverable • Submit Reports to the Advisory Committee • Emergency Alert Recommenations to FCC Project Timeline

More Related