IPv6 adoption for operators

Transcription

1 adoption for operators 29 th Feb 2012 Ramesh Chandra Head IP & Transport Engineering India & South East Asia

2 Coverage Drivers for New service opportunities Present IPv4 Eco system Design consideration Translation strategies options available Challenges in transition Airtel status and support to Industry Summary

3 IPs in '000' IPv4 Pool size (in 000) adoption Drivers Limited IPv4 address space depletion (0.03 IPv4 per person) Internet user growth 3 rd largest user base (India 112Mn, China 300Mn & US 207Mn) 89 times Mobile sector growth (10Mn in 2002 to 890Mn in 2011) Operator A Operator B Operator C Operator D Operator E Q110Q210Q310Q410Q111Q211Q311Q411Q112Q212Q312Q412Q113Q213 IP address Forecast for data services Demand for by Business customers National strategy New service opportunities

4 Exploding mobile broadband traffic 6 Million GB 1.5 Million Users 75 Million Messages Source: Tech Orange web site, March 2011

5 New services opportunities - across verticals Communicati on Service providers Data centers ASP/Web Host Energy Smart Grid Smart Meters Transportatio n Intelligent transportation Smart vehicles Healthcare Emergency rural healthcare Smart healthcare management systems Government Regulatory agencies Domain Registrar s Internet Exchange Government agencies Disaster Mgmt * Disaster surveillance system * Disaster response system Banking and finance Payment gateways for e- commerce Internet banking and e-broking services across verticals 5

6 Present IPv4 eco system GPRS BTS/BSC SGSN GGSN,DPI FW GR NLD Core Network IPv4 Inter net UMTS NB/RNC LTE enb MME SGW/PGW PE Inter net DSL DSLAM SDX BRAS DPI/FW GR LI Systems User Devices Network Infrastructure ISP Network Internet Contents Operator controlled domain

7 Business considerations customer No impact on user services. users visit IPv4 contents Enhance the user experience of cost Trade off among cost of upgrade, new products and time to introduce mobile services, dual stack terminal cost, single-stack terminal need large volume of NAT-PT. LI & traceability cost Considerations network Scalable infrastructure. Reduce complexity and simplify operations End to end services management services Enable new service opportunities Long term coexistence of IPv4 & Continue all present services Seem-less coexistence

8 Design considerations Parameters Addressing Plan Selection of Transition strategies Interconnection User Plane & Transport Plane choices OSS, BSS and Network Management LI & regulatory compliance Scalability and reliability SLA & KPIs POC and product validation Consideration requirement for 10+ years and assignment policy. Assignment for retail users, Business customers and infrastructure. Strategy for retail services Strategy for Business services Peering with upstream, NAP/NIXI, private peering. Start with user plane Different options for control plane Use of existing management where ever possible Select control plane option meeting service requirements. Monitor and manage IPv4 and traffic Solution for meeting regulatory requirement. Right technology choice to increase scalability of services. More than carrier grade reliability. Network Architecture and services design to ensure better customer experience. Invest in setting up POC infrastructure for validation of overall solution 8

9 allocation plan Master Pool Infrastruct ure 2404.a800::/32 or higher IP Core NW (ES, MO & WS) West- Southregions East-Kol North-Del South-Blr Mum Chn....r POPs City- A City-B City-C City-D City-E.... ISPs ISP1 ISP2.... ES ESCust 1 ESCust 2 customers.... SMBs SMB1 SMB2.... Retail static RStat 1 Rstat Retail Dynamic RDyn 1 Rdyn 2....

10 Transition strategies Dual-Stack Translators Tunnels IPv4 Header Data Header Data Application TCP/UDP IPv4 Link IPv4 IPv4 NW tunnel IPv4 host IPv4 & Network host IPv4 Host CGNAT Host IPv4 Header Header Data Header Data Header Data /IPv4 co-existence Best-suited for the Core Ideal inflection point in the network Flexible edge options Need DS capable CPEs Technologies for Core DS routing protocols 6PE 6VPE IPv4 translation Solves the problem at the edge Expected to co-exist with Dual-stack for some time Technologies NAT44/NAT444 NAT64 DS Lite DS Lite + A+ P Tunneled over IPv4 Ideal when Core is not v6 ready Requiresv6 capable CPEs Technologies 6 to 4 6rd ISATAP Teredo

11 Translation requirement 3G Handsets Makes: 22 Top 60 models(83.4%) All 754 models Handsets Models: 754 Nos % Nos % Supported 2,400, % 2,400, % Not Supported 1,753, % 1,753, % Unknown handsets - 0.0% 829, % Total 4,153, % 4,983, % None of the GPRS models support. PCs CPE Mobile Services PE GGSN DS core Core NW BNG NAT44 NAT64 IPv4 Internet / contents Internet / contents contents Enterprise Services PC DSL Residential Services

12 Operator Transition Solution - Dual Stack Customer Scenario DS CPEs Applications support DS IPv4 & roaming IPv4 & PDP context 3GPP introduced dual-stack in release 8 for DS PDP contexts. NAT44 IPv4 Internet / contents GGSN Access NW DS core Internet / contents Mobile Services PE BNG Network requirement PCs CPE Enterprise Services PCs DSL Residential Services Need DS UEs, Access NW, PC, CPEs & BNGs All applications MUST support & IPv4 CGN - NAT44

13 Operator Transition solution All Customer Scenario CPEs supported Applications No IPv4 roaming PDP context DS core NAT64 IPv4 Internet / contents Mobile Services GGSN Access NW DNS64 Internet / contents PE BNG Network requirement PCs CPE Enterprise Services PCs DSL Residential Services Need UEs, Access NW, PC, CPEs & BNGs All applications MUST support NAT64 and DNS64

14 IPv4 & Pools IP Transition plan X Mn IPv4 Pool Size Pvt IPv4 deployment Free IPv4 Pool Size 20-30% of X Deployment months!

15 Services Transition Priorities Priority Services Network Services Present IPs used Future IPs I Core Transport Network IPv4 DS - IPv4 & I Access / CEN IPv4 DS - IPv4 & I 2G, 3G Pub IPv4 & Pvt IPv4 I LTE Pub IPv4 & Pvt IPv4 II LTE enbs Pvt IPv4 III Mobile hosted services Pvt IPv4 Continue Pvt IPv4. after depletion. Wireline Broadband II services Pub IPv4 IPv4 & Preservation of IPv4 and transition to simultaneously. Start in phases in from major cities for higher user coverage.

16 Challenges of IP eco system GPRS UMTS LTE DSL User Devices BTS/BSC NB/RNC enb DSLAM SGSN MME SDX GGSN,DPI SGW/PGW BRAS FW GR DPI/FW GR PE NLD Core Network LI Systems IPv4 Inter net Inter net Present challenges No control on User device readiness. (0.9Mn/26Mn support ) <5% contents on. No regulation to drive at present. Any NAT solutions need review of regulatory compliance requirements. Translation shall potentially degrade customer QoE Low demand from business customers. Contents

17 Unavoidable Network complexity Present After Only Public & Pvt. IPv4 Mostly Native without translations All Applications supported LI compliance without transaction log storage Simplified service delivery and assurance. Co-existence of Pub. IPv4, Pvt. IPv4 and Native, Translation (NAT44, NAT64 & DNS64) and possibly tunneling (6RD) Few messaging, gamming, streaming may not work. (testing critical) Storage for traceability required Operations more Complex YR 2011 YR Note: Text in green shall be new in eco system

18 Airtel status and support to Industry All NLD and ILD core pops ready with dual stack. Aggressive business customer trials Dual stack peering with upstream carriers. Dual stack peering with NIXI and private operators. OSS/BSS in process of readiness for. Mobile user plane infrastructure upgrade on progress. Upgraded dual stack with CDN providers. CGNAT trials completed for all services. Conducted training and awareness programs at major cities. Supporting all major lead working groups for readiness. Supporting DoT initiatives for readiness of all stake holders

19 Summary Transition is inevitable. Need collective effort. Cost of transition increases with time to start. Develop your own priorities and transition mechanism. Service POC is must for impact on user applications is not Y2k but impact is much bigger.

20 thank you