Emergency Location Working Group

Transcription

1 Emergency Location Working Group Ken Hatt, EE 2014 Open Forum

2 EmLoc TG Location Task Group : Routing 999/112 for VoIP to correct local Emergency Authority with VoIP caller s location Membership : Alcatel-Lucent, BSkyB, BT, CPNI, Ericsson, EE, Huawei, Magrathea, Nominet, Ofcom, O2, Unify, Virginmedia, Vodafone and Ofcom +.. Approach :- - VSP, ISP and Access Provider can all be different - Scope : excluded user and device inputs ; all parties UK based - International Standards still developing (use wherever possible) Output was ND1638 in 2010:- Increased co op between 999 CHA (PSAP) and VSP, ISP and Access networks New network entities : LIS (for ISP)and VPC(for 999 CHA) New interfaces for all : Http/Https and XML New requirements on all organisations => systems development not yet implemented Open Forum

3 Standards Groups monitored IETF : GeoPriv and ECRIT WGs NENA and NG911 : i3 standard and US Government programmes (DoT and FCC) 3GPP : IMS and NOVES IEEE 802 ESWG (using IETF approach) ETSI E2NA, formerly TISPAN EMTEL (working with 3GPP and EC), M 493 mandate from EC EENA NG112 requirements 2014 Open Forum

4 EmLoc TG current work IP PBX configuration : guidance for how Private Networks can be set up to provide best possible location (ND1432 draft) ND1638 being updated to allow for use of terminal location and to reflect recent IETF protocol changes ETSI M493 this is likely to supersede ND1638 so is being tracked : UK contributions led by BT with EmLoc input will be studied for UK implementation WiFi access use case for ND1638 : being driven by mobile networks as implement 4G and WiFi access for voice New Work Item (working with SIP TG) : emergency calls are protected/prioritised in TDM networks : principles to be documented to guide requirements for SIP networks 2014 Open Forum

5 Next Steps for VoIP 999 location More organisations involved to deliver 999 more diverse communication (not just traditional telcos providing physical access networks but VSPs, ISPs and terminal providers) New operational components will be : Location Information Server, LIS (ISP + Access Ntwk) and possibly a VPC (for 999 PSAP) for VoIP New interfaces for all organisations : based on international standards as far as possible (eg IETF HELD) New terminal capabilities : location aware mobile handsets, in vehicle units (ecall), routers Increased co op between PSAP/VSP, PSAP/ISP and VSP/ISP/Access networks Timescales to implement uncertain : technically feasible, end user technology changes probably will drive it, regulation also possible.. NICC EmLoc work to continue : need more organisations! [Eg : ITSPA, ISPA, Avaya, Cisco and Microsoft) 2014 Open Forum

6 Back Up Slides 2014 Open Forum

7 BT Public Network UK Emergency Service 999/112 Call Handling Product : Voice + Location Data Voice : Mobile, Fixed, VoIP - esms for hearing impaired ( also ITUv21 text over voice, real time text using special terminals) - Telematics in certain vehicles that includes a voice call + separate SMS data message PSTN IP Gateways VoIP CPs ~60% Mobile >80 Communication Providers (CPs) Fixed/Mobile Networks End user calls 999/112 Call Centres (BT) (7 sites) ~ 35m calls/year Public networks (BT and others) Rapid answer/assured voice connection to local EA (<10 secs) Automatic Location (<2 secs) Call filtering (~55% not connected or connected to Police IVR) CP data base or GMLC BT Location Hub (170 Local EA Controls) Police 51% Location VPN Ambulance 43% Fire 5% Coastguard <1%

8 Current VoIP Service Reach Call Centres through PSTN/IP Gateways Identified as VoIP Registered address accessed through tel number Name and address marked as needing confirmation Verbal routing. Key issues for VSPs using 999 : name and address data to 999 kept up to date 24 hour VSP contact point (tracing) information to 999 on nomadicity end user education 2014 Open Forum

9 Overview of ND1638 Architecture and Interfaces VoIP call VSP 2 soft switch (Aggregation + SS7 interconnect ) SBC2 SBC1/2 VSP 1 Soft Switch SBC1 1 CLI + VSP1 id 2 Source IP+Port, VSP 1 ID and CLI information (NENA v2) a Internet service & access infrastructure providers Access and IP Log on functions CLI + VSP1 id PSTN IP Gateway PIG 3 LIS URI IP IAIC b VPC 4 c ISP LIS Key Emergency Handling Authority Stage 1 PSAP Request using CLI, VSP id. Response gives location HELD third party request using Source IP (+ Port no.), in HELD ID extensions. Response gives PIDF LO Voice path Data path

10 Back Up Slides 2014 Open Forum