1 / 19

ESIF Task Force 34 Overview/Status* February, 2006

www.atis.org. 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. Outline.

baka
Download Presentation

ESIF Task Force 34 Overview/Status* February, 2006

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. www.atis.org ESIF Task Force 34Overview/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

  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. 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. American National Standards FocusIssue 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. Task Force 34Primary 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. Issue 34 – OverviewDrivers 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. Issue 34 – OverviewInitial 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. Issue 34 – OverviewCurrent 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. Messaging Network Architecture Top Level Emergency Information Service Emergency Information Services Interface; EISI (A2) ESNet-to-ESNet Interface; ENEN (A3) ESNet Emergency Services Messaging Interface; ESMI (A1) Note: There is significant flexibility in configurations (e.g., a PSAP can contain ESNet and provide all three interfaces). PSAP CPE

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

  11. Messaging Network Reference Architecture - Legend • Interfaces • A1 Emergency Services Messaging Interface (ESMI) • A2 Emergency Information Services Interface (EISI) • A3 ESNet to ESNet Interface (ENEN) • Remarks • - The (1:n) notation means “one or more” instances • - A1,A2 and A3 interfaces have cardinality 1:1 Functional Entities CESE Conforming Emergency Services Entity RG Response Gateway EPES Entities Providing Emergency Services

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

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

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

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

  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. 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.asp * Link to Latest Overview/Status: http://www.atis.org/esif/tf34status.asp

  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. 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

More Related