Transcript ESIF Task Force 34 Work Status/Overview Feb xx, 2005

www.atis.org
ESIF Task Force 34
Overview/Status*
February, 2006
Mike Fargano, Co-Chair
[email protected]
Christian Militeau, Co-Chair
[email protected]
* Link to Latest Overview/Status:
http://www.atis.org/esif/tf34status.asp
1
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
2
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)
3
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
4
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
5
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
6
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
7
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
8
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)
PSAP CPE
Note: There is
significant flexibility
in configurations
(e.g., a PSAP can
contain ESNet and
provide all three
interfaces).
9
Messaging
Network
Reference
Model
Entities Providing
Emergency Services
(EPES)
A2
ESNet instance (1:n)
RG
(1:n)
A3
ESNet instance (1:n)
RG
(1:n)
RG
(1:n)
A1
A1
CESE
(1:n)
CESE
(1:n)
PSAP
A2
A1
PSAP
A1
CESE
(1:n)
PSAP
Conforming Emergency
Services Entities (CESE)
10
Messaging Network Reference Architecture - Legend
Functional Entities
CESE Conforming Emergency
Services Entity
RG
Response Gateway
EPES Entities Providing Emergency
Services
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
11
Architectural Configuration
PSAP call taker positions configured as CESEs connected to an ESNet
PSAP
Call
Taker
A
CESE
ESNet
ESMI
RG
1
Call
Taker
B
CESE
Call
Taker
C
CESE
PSAP
Mgr
CESE
ESMI
ESMI
RG
2
RG
3
Note: CESE and RG are logical entities/agents; instantiations are shown
12
Architectural Configuration
PSAP CPE Proxy Server connection to an ESNet
PSAP
Call
Taker
A
Call
Taker
B
Call
Taker
C
ESNet
CESE
CESE
ESMI
RG
1
ESMI
RG
2
ESMI
RG
3
CESE
CESE
PSAP
Mgr
Proxy
Server
Note: CESE and RG are logical entities/agents; instantiations are shown
13
Architectural Configuration
PSAP CPE implementation of RG Functional Entity
PSAP
PSAP
Service A
EISI
EISI
ESNet
ESNet
CESE
ESMI
ESMI
EISI
EISI
RG
Service B
EISI
EISI
Service C
14
ESMI and EISI Service Interaction
ESNet
PSAP
Service
Mgmt
Service A
(EPES)
EISI
ESMI
CESE
EISI
Response
Gateway
Service B
(EPES)
EISI
Service C
(EPES)
ALI becomes a special case of a “Service”.
Communication to the PSAP is generalized.
15
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
16
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
17
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
18
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
19