ESIF Subcommittee B March 21, 2006 Las Vegas, Nevada Agenda, Opening Comments, Previous Meeting Summ

1
ESIF Subcommittee BMarch 21, 2006Las Vegas,
NevadaAgenda, Opening Comments, Previous
Meeting Summary and References
ESIF-B-06-11-11-01

• Doug Rollender, Chair

2
ESIF-16-B AgendaJanuary 11, 2006

• Introductions Sign-In, Agenda Review and
  Approval, Opening Comments (BT slides on IMS),
  Assign Contributions to the Agenda
• Previous Meeting Highlights 01,
• Old Business
• a. Issue 45 Location Callback with New
  Access Technology
• Meet with PTSC
• Correspondence from IEEE
• closing statement from Jim or Tom
• b. Issue 20 International Roamers Making
  9-1-1 Calls
• statement of alternative solution sent from ESIF
  to NENA awaiting response
• Issue 14A (closed) WE9-1-1 Fraud need to
  propose new issue
• 4. New Business
• 5. Open Discussion, Review Action Items, Close

3
BT Vision
999 Multi-media Response Center
999 Centre
Community of mobile devices
Witnesses
Voice
Voice
SMS
SMS
MMS
MMS
Emergency Authority Multi-media Response centre
Investigation Workbench
Responding Services
4
Improving the Quality and Efficiency of Response

• In these scenarios the common benefits of using
  multi -media include
• Overcoming audible communications barriers
• Provide improved interactivity to callers at the
  scene
• Improved Response Planning
• Preservation of multimedia data for post incident
  analysis

5
Summary-999 Emergency Call Centres

• An emergency service centre could be designed so
  that-
• Emergency calls from advanced IP devices (e.g.
  video phones) are routed to devices in the call
  centre capable of multimedia communication.
• Receive incoming video calls from both fixed line
  and mobile phones so that the operator can see
  the caller and details of the scene.
• Engage in multimedia communication with the
  caller (e.g. video, audio, text, ..)
• Receive data from the caller (e.g. files
  transfer, live medical data, feeds from security
  system, )
• Record multi-media communication (e.g. record
  audio, video, text, ).
• Converse with a deaf person that has a fixed line
  video phone via a deaf relay service. (Note that
  today 3G mobile video quality is sufficient for
  accurate sign language)
• Compliment all existing voice plus location data
  functionality.

6
The evolving role (and training) of the 999
contact centers emergency services

• Media Interpretation
• Call takers would need to know how to interpret
  the significance of media and how it could assist
  the response.
• Media enabled collaboration
• The availability of media may guide the
  interaction between operators, dispatchers,
  callers, and responders.
• Media Selection
• What media should be seen by
• 999 Operator Services
• Emergency Services
• Responding officers
• Investigators

• The introduction of media into the emergency
  services 999 contact centers raises would
  several key areas
• Call Center Process Changes
• Indexing
• Security Privacy

7
Security Privacy

• Receiving media files from the public poses a
  variety of challenges that any solution will need
  to address regarding usage made of the files
• Filtering of silent calls ( A silent call with
  multimedia could help filtering)
• Filtering of hoax calls
• Fraud Detection Authentication
• Retention/Archiving

8
Key issues

• CLI is no longer permanently associated with a
  physical connection
• IP address allocation is even more temporary
• Software, Service, Access, IP Connection and Core
  Network can all be owned by different companies,
  potentially in different locations across the
  Globe

9
High Level Requirements -1

• Provide a voice link, maintained throughout the
  call
• Receive immediate priority treatment over other
  calls
• Must not be subject to restrictive network
  management practices
• Must be subject to normal call recording,
  charging and accounting (even tho' free)

10
High Level Requirements -2

• Must provide a unique ID to enable a callback
  (eg CLI) and Network ID
• Originating geographic location must be
  automatically provided to determine - correct
  operator centre (PSAP) to route the call to-
  appropriate local emergency service
  centre(responder)
• - location to accurately despatch assistance.
• Location information must be automatically
  available at the local emergency service centre
  (responders)

11
High Level Requirements -3

• Must be migrated to multi-party calls under the
  control of the emergency operator
• Shall be subject to "last party clear" or other
  method for handling false calls
• Shall be restored with priority over normal
  calls.
• Need IP Call Centre/switch solution

12
Key issues

• CLI is no longer permanently associated with a
  physical connection
• IP address allocation is even more temporary
• Software, Service, Access, IP Connection and Core
  Network can all be owned by different companies,
  potentially in different locations across the
  Globe

13
First Draft Prototype Architecture
Firewall
Gateway / proxy
1
Media Processing Environment, Recording Routing
2
2a (IP voice)
2b (video)
CTI Platform
2a (TDM voice)
Call Mgt
CD/RSI Server
6a
5a,c
3a
XML Video Commands
4a
6c
XML Video telephony Commands
3b
3c
4b
4c
4b
To control video specific functionality
Agent Terminal
Application Mgr
Video Streaming Server
Agent Headset
Video stream
14
ESIF-16-B AgendaJanuary 11, 2006

• Introductions Sign-In, Agenda Review and
  Approval, Opening Comments (BT slides on IMS),
  Assign Contributions to the Agenda
• Previous Meeting Highlights 01,
• Old Business
• a. Issue 45 Location Callback with New
  Access Technology
• Meet with PTSC
• Correspondence from IEEE
• closing statement from Jim or Tom
• b. Issue 20 International Roamers Making
  9-1-1 Calls
• statement of alternative solution sent from ESIF
  to NENA awaiting response
• Issue 14A (closed) WE9-1-1 Fraud need to
  propose new issue
• 4. New Business
• 5. Open Discussion, Review Action Items, Close

15
ESIF-16-B Report Summary

• Issue 45 Location and Callback for New Access
  Technologies
• Conference call conducted 2/10/06 on closure
  statement
• Open Contributions from Jim Propst and Tom Breen
• Issue 27 Wireless Callback Number
• Closed
• Closed Issues Referenced in NENA TID 05-304
• New issues required to do further work on fraud
  and 911 caller mobility in ESIF-B
• Issue 20 Internal Roamer Calling 911
• Alternative Solution offered for comments
• Correspondence to NENA on Issues 20 27

16
While ESIF and NENA cannot compel non-controlled
entities to establish and mandate specific 911
requirements, both organizations will continue to
grow and enhance cooperative relationships
through involvement in and effective liaison
appointments with relevant standards and
regulatory entities to support effective
positioning of 911 requirements. They will also
continue to encourage their members to be
involved champions for the need to provide
location identification and callback
capabilities, as well as other specific 911
requirements, in all emerging access and
communications technologies. These actions on
the part of ESIF and NENA will demonstrate a
strong partnership and commitment to the
inclusion of location identification and callback
capability, prior to general deployment, for any
new communications technology from which a user
can reasonably expect to be able to make a 911
call.
17
. . . ESIF Issue 20 on the need for a callback
number for international roamers who place a
9-1-1 call. We would appreciate your feedback on
the alternative approach described below to
address Issue 20. This alternative approach
seems applicable with NCAS, Hybrid CAS or CAS
(even though it may never be implemented).  The
alternative approach involves the use of the E2
interface or PAM to solve the problem. Standards
for the E2 interface currently support a CBN of
10 digits or more in the MPC/GMLC and a nature of
number indicator for an international CBN (see
J-STD-026-A, Chapter 7, Section 2). Between the
MPC/GMLC and the ALI server, the ALI server needs
to know where to find an international CBN in
messages from the MPC/GMLC and where to put it in
the database for the PSAP. For example, existing
fields in messages from the MPC/GMLC may be used
for a NANP CBN and an alternate field may be used
for an international CBN. At the PSAP display,
if there is a limitation of 10 digits to show the
CBN, an international CBN of more than 10 digits
may be displayed in another field. . .