Emergency Services Workshop UK VoIP 999/112s John Medland – BT 999/112 Policy Manager

UK Emergency Service today BT or CW Public Ntwk (PSTN) Other Networks BT or CW Operator Centres PSTN Police 56% Ambulance 35% Fire 8% Coastguard <1% 999/112/ (222 Local Controls) BT – 28m calls, 50% mobile, every call voice + location

Handling VoIP 999/112 now 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………. Devices/CPE use PSTN/GSM for 999 if possible Key issues for VoIP 112/999 : - provision of 112/999 access - registered name and address data kept up to date (end-user->CP1->CP2 to PSTN and PSAP) - 24 hour VSP contact point for PSAP use (tracing, alternative contacts) - lack of information to PSAP for nomadic users (definition of nomadic) - end user education - how to Automate Location provision………

NICC Task Group The Network Interoperabilty Consultative Committee : NICC is a UK telecommunications industry committee which acts as an industry consensus group in which specifications and technical issues associated with network competition can be discussed. It also is a source of advice to the Director General of Telecommunications on the harmonisation of interconnection arrangements Location Task Group : Routing 999/112 for VoIP to correct local EA with VoIP caller location information Membership : ITSPA, ISPA, BT, C&W, Ericssons, Huawei, Andrew, ETSI, Gradwell, Magrathea, Thus, Truphone, IN UK, Virgin Media and Ofcom +…. Approach :- - VSP, ISP and Access Provider(s) all different - Start with DSL and than tackle Cable, WiFI and GSM scenarios - Standards still developing (use wherever possible, eg IETF, ETSI) - Start with UK only (but need to allow for International dimension) - Don’t rely on user - Don’t rely on device (at least for next 2/3 years)

VPC Access LIS VoIP call CLI + VSP1 id VSP 1 Soft-Switch Emergency Handling Authority(EHA) Authority[PSAP] Internet service & access infrastructure providers PIG CLI + VSP1 id Source IP, VSP 1 ID and CLI information IAIC (BGP) Request using CLI, VSP id. Response gives location x 1 c b y ISP LIS Log-on functions SBC2 d PSTN—IP Gateway VSP 2 soft switch (Aggregation + interconnect ) a SBC1 Functional Architecture – work in progress

BTW BB BTR 999 or C&W 999BTR ISP & Other ISPs Network Transit ProvidersVoice Service Provider Layers involved User Network Attachment Network Attachment VoIP Registration 112 Call 112 Call +CLI112 Call +CLI + II digits CLI + IP Address IP Adrs -> Locn Req CLI->IP Adrs Locn Req BTOR / LLU ANP EHA/PSAP ISP VSP DSLAM,BRAS, RADIUS,(LAC) LNS, RADIUS Copper loop

Implications Yes, automated routing and location provision is technically feasible (for ADSL case) but will imply :- New requirements on all organisations (systems development) Many more organisations involved to deliver 112 (not just traditional telcos but VSPs and ISPs) New operational components : LIS and VPC New interfaces for all organisations: based on international standards as far as possible (eg IETF HELD) Increased co-op between PSAP and VSP, ISP and Access networks Detailed document is now going through NICC review process …………………..

Challenges to adoption ISPs storing and updating association of IP/Line ID/ location at an ISP LIS LIS cascades to access providers and length of response times ANPs storing and updating association of (IP)Line IDs/ location at ANP LIS Challenging business cases (!) unless regulatory driven Current regulatory responsibility unclear when several CPs and an ISP involved

Further Challenges National solutions are being developed National solutions will need to evolve to cover international IP roamers Long transition periods with hybrid TDM/IP services Multimedia calls : all organisations need clear 112 requirements driven by users (112Net?)

Next Steps Next Steps :- - Finalise basic architecture and BB ADSL scenario detail - Continued work on other UK scenarios (Cable, LLU, Private networks) - International Scenarios - IP end-to-end (as NGN, PSAP +device capabilities become clear)

Openreach Backhaul & Aggregation Wholesaler ISP Emergency Services Centre Locn Req (IP adrs) Locn Resp (Postal Adrs) New Provide (Instn Adrs) Customer New Provide (Instn Adrs) New Provide (Instn Adrs) Confirm (SID OR ) Confirm (SID W ) PPP Login Login OK + IP Adrs Login OK + IP Adrs LIS SID W -Instn Adrs LIS IP->SID W New Provide IP- SID W

Openreach Backhaul & Aggregation Wholesaler ISP Emergency Services Centre Locn Req (IP adrs) Locn Req (IP adrs) Locn Resp (Postal Adrs) Locn Resp (Postal Adrs) New Provide (Instn Adrs) Customer New Provide (Instn Adrs) New Provide (Instn Adrs) Confirm (SiD OR ) Confirm (SID W ) LIS Relay PPP Login Login OK + IP Adrs Login OK + IP Adrs LIS SID OR ->Instn Adrs LIS IP Adrs->SID OR New Provide (case B)

Current UK industry structure WLR Broadband; Calls SMPF / MPF Broadband Telephone line & calls Services: CPS; broadband Infrastructure End User reseller Retail CP Network (Access) Provider Eg Openreach Wholesale CP Automated B2B systems & processes currently (just about) support this