emergency services workshop n.
Skip this Video
Loading SlideShow in 5 Seconds..
Emergency Services Workshop PowerPoint Presentation
Download Presentation
Emergency Services Workshop

Emergency Services Workshop

160 Views Download Presentation
Download Presentation

Emergency Services Workshop

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Emergency Services Workshop UK “i2” for VoIP 999/112s John Medland – BT 999/112 Policy Manager

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

  3. Handling VoIP 999 now • PSAPs still TDM based so VoIP goes through PSTN / IP Gateways • Small number of VoIP 999s at present, mostly fixed users • Regulation says if PSTN access, then must allow 999 • 999s identified as VoIP • Registered “default” address accessed through E164 tel number (CLI) for “fixed” users…. • ….but default address marked as needing confirmation Verbal routing • Device/CPE use PSTN/GSM for 999 if possible • Key issues for VoIP 999 : -- only default name+address data from large number of VoIP SPs- challenge of 24 hour VSP contact point for PSAP use (tracing, alternative contact numbers)- lack of information to PSAP for nomadic users • Need to Automate Location provision………

  4. 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 technical advice to the UK Regulator • Location Task Group : Routing 999/112 for VoIP to correct local EA supplying caller location information on all calls • Membership : BT, C&W, Ericssons, ALu, Huawei, Andrew, ETSI, Magrathea, Thus, IN UK, Virgin Media, Orange, and Ofcom +…. • Approach :-- VSP, ISP and Access Provider(s) all different organisations- PSAPs are still TDM based- Start with UK only (all parties UK-based) - Start with DSL, then tackle Cable, WiFI and GSM scenarios - Use developing standards wherever possible, eg IETF, ETSI- Don’t rely on user- Don’t rely on device

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

  6. Broadband and ADSL Access

  7. Interface (c) LIS HELD Server iM1 iB1 LIS OSS/ CRM Systems IP@ translation; Border Functions - NAPT/SBC/ALG iC1 iL2 Network elements Other LIS Basic UK LIS interfaces

  8. Implications Yes, automated routing and location provision is technically feasible (for DSL case) but will imply :- • New requirements on all organisations (systems development) • Many more organisations involved to deliver 999 (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 and trust relationships between PSAP and VSP, ISP and Access networks • Detailed document is now in final stage of NICC review process …………………..

  9. 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 • Challenging business cases (!) unless regulatory driven • Current regulatory responsibility unclear when several CPs and an ISP involved

  10. Next Steps - Continued work on other UK scenarios (Wireless, Private networks)- International Scenarios : national solns need to evolve to cover international IP roamers- Long transition periods with hybrid TDM/IP services- IP end-to-end (as NGN, PSAP +device capabilities become clear)  i3 / IETF Ecrit

  11. Back-ups

  12. xDSL Architecture for PPP BRAS Terminated Access User Local Loop Backhaul & Internet Service Emergency Internet Environment Provider Aggregation Provider Handling Telephony ProviderCentre Service Provider OSSLLP OSSBAP OSSISP iM2 iM1 Management iM3 Control BAP RADIUS Server VPC LIS iM4 iBB5 (RADIUS) ISP RADIUS Server iBB3 (RADIUS) iBB4 (RADIUS) SIP iBB1 (PPPoATM) BRAS iBB2 (PPPoE) Residential G/W DSLAM Voice Terminal IP N/W RTP/RTCP Media

  13. Network Attachment for PPP Terminated Access BAP RADIUS Server iBB3 (RADIUS) ISP RADIUS Server iBB5 (RADIUS) BRAS LIS iBB1 (PPPoATM) iBB4 (RADIUS) Residential G/W DSLAM iBB2 (PPPoE) PPP Challenge(Token) PPP Challenge(Token) PPP Resp (UID,#PW#) PPP Response (UID,#PW#, IA=SIDBAP) Access Req (UID,Token,#PW#,IA=SIDBAP) Access Acpt (BRAS Info) Acc Req (UID,Token,#PW#,IA=SIDBAP) Acc Acpt (IP Adrs) Accouting Req (IP Adrs,SIDBAP) PPP Success PPP Success Accouting Resp

  14. NICC Standard – end to end EISEC CLI EACR/PSAP ISP OSS Installation Adrs CLI Line ID -> Installation Adrs Installation Adrs Emergency Handling Centre CLI+ITSP IP Adrs Location Info Svr VPC Installation Adrs Installation Adrs CLI, ITSP CLI, ITSP -> IP Adrs PSTN IP Adrs-> Line Id TDM Gate- way ITSP Call Svr Public Internet IP Gate- way IPeXchange Home Hub BB Platform