1. 1 ESIF Task Force 34 Overview/Status* February, 2006 Mike Fargano, Co-Chair michael.fargano@qwest.com Christian Militeau, Co-Chair christian.militeau@intrado.com * Link to Latest Overview/Status: http://www.atis.org/esif/tf34status.asp www.atis.org

2. 2 Outline Task Force 34 (and Issue 34) Overview Reference Architecture Architectural Configurations Relationship to NENA i2 and i3 Issue 34 – Status Conclusion Task Force 34 Reference Links

3. 3 Task Force 34 – Focus on ESIF Issue 34 Task Force 34 is responsible for deliverables associated with ESIF Issue 34 – thus the name “Task Force 34” Initial ESIF Issue 34 acceptance at ESIF 10 (July 2004) Updated Issue 34 acceptance at ESIF 12 (Jan 2005)

4. 4 American National Standards Focus Issue 34 Deliverables ATIS/ESIF – ANSI Accredited for the production of American National Standards (ANS) Foundation: Openness, Transparency, Due Process – Per ATIS Operating Procedures – based on ANSI Essential Requirements; recognized for diligence; combined with rapid execution. Implementation of ANS are voluntary unless mandated Announcements/Liaison for Coordination: Wide announcement of work; utilizes ESIF/NENA leadership liaisons

5. 5 Task Force 34 Primary Participant List at&t Bellsouth Qwest Intrado Positron HBF Group Telcordia Technologies Verizon Wireless Cingular Sprint Nextel T-Mobile USA Tarrant County 911 District NENA

6. 6 Issue 34 – Overview Drivers Driver: next generation emergency services data messaging needs: –NENA Technical Information Document on Future 9-1-1 Models (Future: Based upon standard IP protocols, utilizing XML in a more robust protocol than envisioned by the ALI Bid/ Response model, including support of extensions for supplemental information delivery). –PSAP ALI Interface - Next Generation Needs (see TF34 contributions: ESMI-010, ESMI-011) –Need for Web Services based interface in support of emergency information services –APCO guidance regarding diversity of PSAP needs

7. 7 Issue 34 – Overview Initial Focus (July 2004) Initial Focus: Emergency Services Messaging Interface (ESMI) –Interface for Logical Entities/Agents: Response Gateway (RG) to Conforming Emergency Services Entity (CESE): ESNet (for messaging) to PSAP CPE Interface Provides for well defined TCP/IP persistent connection interface framework for PSAP CPE (next generation emergency services messaging) XML Schemas to be referenced

8. 8 Issue 34 – Overview Current Focus (Updated Jan 2005) Current Focus: ESMI; and Emergency Information Services Interface (EISI) –Interface for Logical Entities/Agents: Response Gateway (RG) to Entities Providing Emergency Services (EPES) for EISI: ESNet (for messaging) to EPES Provides for well defined Web Services based service interface framework for emergency information services (e.g., telematics providers) for next generation emergency services messaging XML Schemas to be referenced or discovered

9. 9 ESNet Emergency Information Service Emergency Information Services Interface; EISI (A2) PSAP CPE Emergency Services Messaging Interface; ESMI (A1) ESNet-to-ESNet Interface; ENEN (A3) Messaging Network Architecture Top Level Note: There is significant flexibility in configurations (e.g., a PSAP can contain ESNet and provide all three interfaces).

10. 10 ESNet instance (1:n) PSAP Entities Providing Emergency Services (EPES) A1 CESE (1:n) RG (1:n) RG (1:n) A3 A2 PSAP A1 A2 ESNet instance (1:n) A1 Conforming Emergency Services Entities (CESE) RG (1:n) CESE (1:n) CESE (1:n) Messaging Network Reference Model

11. 11 Functional Entities CESEConforming Emergency Services Entity RGResponse Gateway EPESEntities Providing Emergency Services Interfaces A1Emergency Services Messaging Interface (ESMI) A2Emergency Information Services Interface (EISI) A3ESNet to ESNet Interface (ENEN) Remarks - The (1:n) notation means “one or more” instances - A1,A2 and A3 interfaces have cardinality 1:1 Messaging Network Reference Architecture - Legend

12. 12 Architectural Configuration Note: CESE and RG are logical entities/agents; instantiations are shown ESNet RG 3 2 1 PSAP CESE Call Taker A Call Taker B Call Taker C PSAP Mgr PSAP call taker positions configured as CESEs connected to an ESNet ESMI

13. 13 Architectural Configuration PSAP CPE Proxy Server connection to an ESNet Note: CESE and RG are logical entities/agents; instantiations are shown ESNet RG 3 2 1 PSAP Call Taker A Call Taker B Call Taker C PSAP Mgr CESE Proxy Server ESMI

14. 14 Architectural Configuration PSAP CPE implementation of RG Functional Entity ESNet PSAP EISI ESMI

15. 15 ESMI and EISI Service Interaction CESE Response Gateway Service A (EPES) PSAP Service B (EPES) Service C (EPES) ESMI EISI ESNet ALI becomes a special case of a “Service”. Communication to the PSAP is generalized. Service Mgmt EISI

16. 16 Relationship to NENA i2 and i3 Relationship to NENA i2: –ESMI, EISI and ENEN can be used for basic ALI and/or advanced emergency information delivery –Use of various architectural configurations – driven by PSAP needs Relationship to NENA i3: –ESMI, EISI and ENEN can be used for advanced emergency information delivery –Use of various architectural configurations – driven by PSAP needs

17. 17 Issue 34 – Status* Feb 20, 2006 Emergency Services Messaging Interface (ESMI): –Trial Use Standard completed Sept 2005 –Pre-Publication version of ESMI Standard available: ATIS-PP-0500002-200X: Emergency Services Messaging Interface Emergency Information Services Interface (EISI): Stage 1 (Requirements) and Stage 2 (Analysis) are completed; Stage 3 (Detailed Interface Specification) started during ESIF 13. Standards Development is continuing. –EISI Plan: Targeted for completion in July 2006 (with initial Letter Ballot issuance in May 2006) ESNet to ESNet Interface (ENEN): Work not started; no target date set. Will probably be defined as an extension of EISI. See Task Force 34 posted meeting notes for more detail; TF34 Web Site: http://www.atis.org/esif/esmi.asphttp://www.atis.org/esif/esmi.asp * Link to Latest Overview/Status: http://www.atis.org/esif/tf34status.asp

18. 18 Conclusion Task Force 34 focus is on next generation emergency services data messaging Driven by common understanding of next generation emergency services messaging needs Three interfaces: ESMI, EISI, and ENEN targeted as American National Standards (ANS) Flexible configurations for interested parties – e.g., to meet the needs of various PSAPs Interfaces play well with foreseen future directions of next generation emergency services

19. 19 Task Force 34 Reference Links ATIS: –www.atis.org ESIF: –http://www.atis.org/esif/index.asp ESIF Issue 34: –http://www.atis.org/esif/docs/ESIF_Issues_Files/ESIF-034.doc ESIF Task Force 34: –http://www.atis.org/esif/esmi.asp Task Force 34 Terms of Reference: –http://www.atis.org/esif/docs/Public-Contributions/ESMI-002.pdf Task Force 34 Contributions (including Baseline Text): –http://www.atis.org/esif/esmicont.asp