NENA i3 Standards Status

1
NENA i3 Standards Status

• Roger Marshall
• Vice-chair NENA VoIP/Packet Technical Committee

2
What is the NENA i3 Standard?

• Current Document Title
• Functional and Interface Standards for Next
  Generation 9-1-1 Version 1.0 (i3)
• Referred to as the i3 (Draft) Standard
• Considered a first version toward NG9-1-1

3
i3 Standard Development Status

• i3 Standard came to be, to address
• The need to support Next Generation 9-1-1 IP
  end-to-end emergency calls
• Development of an Emergency Services IP Network
  architecture, defined within i3 as the ESInet
• An architecture based on open Internet standards
  (e.g., IETF protocols)
• Remaining Goals
• Current work to serve as a basis for i3 (Stage 3)
  specification development
• Document v1.0 at final editing process
• Path Forward
• NENA standards are contribution driven
• Additional work efforts will lead by LTD-WG in
  NENA
• Anticipate possible other SDO development, based
  on NENA i3 requirements and architecture

4
Benefits to i3

• Provide guidance to SDO in implementing Stage 3
  standards
• Specify an architecture to aid equipment and
  service providers to implement solutions that are
  interoperable by conforming to these
  recommendations,
• Define new capabilities for persons seeking help
  and for the PSAPs and responders that can render
  assistance..
• Allow PSAPs to accept calls from a wider variety
  of devices and services
• Improve the quality and range of services
  provided to all callers
• React better than existing systems in major
  disasters
• React better to deliberate attack on the system

5
i3 Scope

• In Scope
• The architecture of the emergency calling system
• External Interfaces between PSAPs and
  public/private networks delivering 9-1-1 calls to
  the Emergency Service IP Network
• External Interfaces to systems and databases not
  in the PSAP that supply data and assistance in
  processing a call
• External Interfaces to systems that handle a call
  past the point where a call taker has exclusive
  control over it, such as the handoff to the
  Computer Aided Dispatch system
• External Interfaces to upper level management
  systems, such as disaster management systems, as
  well as peer PSAPs
• Functions such as location based routing, data
  creation and maintenance
• Gateway interworking from Wireline Wireless
  legacy origination networks

6
i3 Scope (2)

• Out of Scope
• Location determination
• Location acquisition
• Intra PSAP interfaces
• Responder systems (e.g. CAD systems, although the
  external interface to the CAD system is in scope)
• Transition from legacy networks to i3

7
i3 Scope (3)

• References to other work
• Location determination, acquisition, conveyance
  and updates to location
• Emergency call origination
• Actual Routing of emergency calls prior to entry
  to the Emergency Services IP Network (though the
  same functions to perform this action is IN
  scope, e.g., ECRF Location Validation Function)

8
Introduction to i3 Standard

• i3 Architecture
• NENA Recommended Standard for
• Devlepment of the concept of an ESInet
• ESInet Functions
• ESInet Interfaces between PSAPs and
  Public/Private networks
• Components within/without the ESInet
• Multimedia support
• Based on published NENA 08-751 TRD

9
i3 Overview (2)

• Characteristics of i3
• Baselines concept of IP end-to-end emergency
  calls
• Assumes any device, any media (though focuses on
  Voice)
• Promotes idea of multiple (new) IP-based PSAP
  services
• Supports variety of Access Networks technologies
• Recommends single signaling protocol (SIP)
• Defines the ESInet

10
i3 Overview (3)

• Components of i3
• ESInet the Emergency Services IP network
• Between originating networks and PSAP
• All calls delivered to the ESInet via IP
• Delivers all calls to the local PSAP network via
  IP
• Defined as a Network of Networks
• Listed Functions
• Listed Interfaces

11
Overview (4)

• Functions defined within the ESInet
• Emergency Services Routing Proxy (ESRP)
• Routing Function (ECRF)
• Location Validation Function
• Border Control Function (BCF)
• Multimedia
• Supplemental Data
• Interfaces defined in ESInet
• Legacy Gateway Interface
• TDM Gateway Interface
• Functions/Interfaces referenced but treated as
  out of scope
• Government
• Responder
• IP-PSAP (local PSAP LAN, Equipment, outbound
  interfaces)

12
(No Transcript)
13
Overview (5)

• ESInet defined
• ESInet (Emergency Services IP Network)
• Refers to a private IP network or IP Virtual
  Private Network (VPN) that is used for
  communications between PSAPs and among other
  entities that support or are supported by PSAPs
  in providing emergency call handling and
  response.
• ESInet implementations
• Generic SIP
• IMS

14
ESInet Architecture Generic SIP
15
ESInet Architecture IMS
16
Relationship to other Standards

• Some correspondence initiated via Liaison letters
• Ref. 3GPP interworking (TS 23.167) referenced by
  example
• IETF work in the area of Emergency Services call
  routing
• ECRIT working group http//www.ietf.org/html.char
  ters/ecrit-charter.html
• GeoPriv working group http//www.ietf.org/html.ch
  arters/geopriv-charter.html
• Call signaling via SIP http//www.ietf.org/rfc/rf
  c3261.txt?number3261
• Media flows via IETF protocols, e.g., RTP RTCP
• Acknowledgement of location acquisition
  protocols, including HELD, DHCP, LLDP-MED,
  SUPL/MLP
• Location conveyance via IETF SIP conveyance of
  location draft
• Inclusion of std. mechanism to distinguish an
  emergency call via IETF Service URN draft
• Emergency call routing protocols to the correct
  PSAP via LoST protocol
• The overall description of IETF approach to
  emergency calls
• Framework for Emergency Calling in Internet
  Multimedia (IETF draft)
• recommendations for telephones and proxy servers
  (carrier softswitches)
• Best Current Practice for Communications Services
  in support of Emergency Calling (IETF draft)

17
System Architecture

• Basic Assumptions
• Logical Domain Separation
• Originating network / ESInet / PSAP local network
• ESInet is a network of networks
• Location
• Civic or Coordinate (Geo)
• Pointers to IETF drafts
• Location-by-Value is represented
• Location-by-Reference is represented
• Location Information acquired by the endpoint
• Location-by-Reference identifier is dereferenced
  into a location
• Location Conveyance between element (e.g.,
  Proxies)

18
System Architecture (2)

• Additional Assumptions
• Origination Network Call Routing
• Generic SIP
• Edge Routed example
• Proxy Routed example
• IMS (3GPP TS 23.167)
• Gateway to Legacy Wireline and Wireless
• Wireless example, using ECRF
• Wireline w/ECRF

19
Call Routing Architecture Example Generic SIP
20
Call Routing Architecture Generic SIP
21
Legacy Gateway Architecture -Example of Wireline
Origination Network
22
Legacy Gateway Architecture -Example of Wireless
Origination Network
23
Call Architecture Example Generic SIP
24
Call Architecture

• Terminology - Calls Incidents
• Call a single communication that results in a
  defined action by a call taker.
• Call Identifier URI identifier assigned by the
  first ESInet element
• Agent a person employed by or contracted by an
  agency.
• Agency an organization that is a client of a
  database or service.
• Incident defined public safety event w/PSAP
  response
• Incident Identifier URI identifier assigned by
  the first PSAP

25
Call Architecture (2)

• Call Signaling
• SIP (RFC 3261) - Session Initiation Protocol
• Emergency Call identification
• Use of common dial string (e.g., 9-1-1)
• Service URN (e.g., urnservicesos)
• Call Routing
• ECRF - Emergency Call Routing Function
• Requires ubiquitous LoST Services
• For Origination networks
• For the ESInet

26
ECRF Emergency Call Routing Function

• LoST-based Call Routing
• Via LoST (Location to Service Translation)
  protocol
• Input Location Service Identifier
• Output PSAP URI
• Emergency Call identification
• Use of common dial string (e.g., 9-1-1)
• Service ID/URN (e.g., urnservicesos)
• http//tools.ietf.org/internet-drafts/draft-ietf-e
  crit-service-urn-06
• http//tools.ietf.org/internet-drafts/draft-ietf
  -ecrit-lost-05.txt
• Additional outputs from LoST
• Polygon data (geo boundary data)
• Civic Location Validation

27
Originating Network Routing w/LoST external
example
28
ESInet Routing w/LoST external example
29
Additional Topics in the NENA i3 Standard

• Basic Services
• Security
• Service Management
• Call Overload Management
• Roles Responsibilities
• Profiles and Minimal Profile Definitions
• Transition from legacy technology to i3
• Ref. NENA Transition Planning Committee Working
  Group, (contact Bob Sherry, Jim Goerke)
• List of references to other standards and draft
  standards

30
Thank you.

• Roger Marshall
• TeleCommunication Systems, Inc.
  rmarshall_at_telecomsys.com