Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations

Presentation on theme: "Emergency Services Workshop UK i2 for VoIP 999/112s John Medland – BT 999/112 Policy Manager."— Presentation transcript:

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

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

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 s 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 - Dont rely on user - Dont rely on device

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

6 Broadband and ADSL Access



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

10 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 …………………..

11 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

12 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

13 Back-ups

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

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

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

Download ppt "Emergency Services Workshop UK i2 for VoIP 999/112s John Medland – BT 999/112 Policy Manager."

Similar presentations

Ads by Google