Colloque IPv6 Caen, 13 Juin 2013 Stratégie de déploiement d IPv6 dans les réseaux mobiles David BINET Orange
Agenda Mobile services: Orange group in few figures IPv6 introduction: the context IPv6 introduction strategy Hurdles and drivers Synthesis and next steps 1
Orange Mobile footprint Tunisia Jordan Egypt U K Belgium Luxembourg Poland Slovakia Sénégal Guinée-Bissau Guinea Mali Niger Cameroun République Centrafricaine France Austria Switzerland Moldova Romania Côte d Ivoire Guinée Equatoriale Uganda Kenya Armenia Spain at end 2012 Dominican republic Botswana Madagascar mobile 172 million customers Caribbean Islands Vanuatu Mauritius La Réunion Employees 170 000 employees Fixed broadband 15 million customers consolidated revenues 43.5 billion 2
Some diversity inside Orange Group Various situations regarding IPv4 mobile architectures in the group Most of the affiliates assign IPv4 private addresses to UEs (User Equipment) This pool is limited Known issues with NAT44 Performance, service availability, incoming communications, ALG, etc More complex design for accounting & regulatory functions Lawful Interception, UE traffic identification Some affiliates assign public IPv4 addresses But public IPv4 address exhaustion is happening Some affiliates assign both public and private IPv4 addresses 3
and common requirements IPv4-only devices will be the majority (at least during first phase) User may access to services through visited network (roaming) BSC SGSN IP backbone GGSN Some applications may remain IPv4 based IPv4 Orange Services RNC Border Gateway INTERNET IPv4 IPv4 Impacts on devices should be limited S-GW P-GW IPv6 Orange Services e IP backbone LTE/EPC network will be deployed INTERNET IPv6 4
IPv6 introduction strategy IPv4 only connectivity IPv4/IPv6 connectivity IPv6 only connectivity One IPv4v6 PDP context /EPS bearer preferably IPv4 Service continuity solutions Applications should be Address family Independent Optimized solution for walled Garden services (M2M) 2013: Poland Optional phase 5
IPv6 introduction strategy (2) First (optional) step: Dual Stack (2 options) IPv4 PDP context IPv6 PDP context or IPv4v6 PDP context GGSN/P-GW GW IPv4/IPv6 Orange GGSN Services INTERNET One PDP context for IPv4 and IPv6 Is the preferred option But only Available from Release 8 (LTE) and Release 9 (GPRS) IPv4/IPv6 Second step: IPv6-only IPv6 PDP context GGSN GGSN Internet Orange applications IPv6 CLAT function GGSN/P-GW GW NAT64/ DNS64 Applications should be Address Family Independent to reduce traffic in NAT64 function IPv4 Internet/ Orange applications 6
IPv6 introduction impacts on mobile architecture Terminals must support IPv6 (IPv6, IPv4v6 PDP contexts) Customers Management (PDP types) HLR AAAA Information (+DNS64 function) DNS Functions update (FW/DPI/LI) New function (NAT64) IPv4 RAN SGSN/ S-GW Router IP backbone Router GGSN/ P-GW Gi Interface Applications No impacts (IPv4 transport) IPv6 support on user plane No impacts (6PE design) IPv6 support on user plane APN management IPv6 support on applications 7
Main hurdles - Devices Some diversity in terminals portfolio With new chipsets integration more and more devices are IPv6 compliant considering basic features More functions are required CLAT function for IPv4 service continuity Prefix delegation capabilities /64 prefix sharing solution PCP function 8
Main hurdles - Devices draft-ietf ietf-v6ops v6ops-mobile mobile-device device-profile profile-03 This document is for: Providers to help in preparing documents detailing their device requirements Vendors to be aware of a minimal set of requirements to allow for IPv6 connectivity and IPv4 service continuity (using an IPv6-only connectivity) Cross SDO (standards Developing Organization) document Multi operators initiative Document structure basic Connectivity requirements 3GPP interface WLAN interface (IEEE 802.11) Advanced requirements Mobile Devices with LAN Capabilities APIs & Applications 9
Hurdles: (s)gi interface impacts IPv4/IPv6 Mobile network GGSN/P-GW GW Gi Interface Applications - Not exactly an interface but a network - Currently like some pearl necklace in our architectures - Various functions are provided: IP translation, Firewalling, DPI, billing, caching, routing. - These functions must be «IPv6 compliant» (at least to provide the same level of service than for IPv4 service) - New functions (new devices) to be added for IPv4 service continuity (NAT64 when IPv6-only connectivity is provided) 10
Hurdles: Roaming Roaming agreements to be updated for IPv4v6/IPv6 PDP contexts support IPv4 fallback must be ensured if IPv6 connectivity cannot be provided (visited network does not support IPv6) More crucial in IPv6-only scenario HLR/HSS must be updated to provide IPv4 / IPv6 / IPv4vv6 PDP contexts Identification of visited networks in connection request may be required to enable IPv6-only connectivity White paper for IPv6 transition edited by GSMA Roaming tests not easy to lead (hundreds of roaming situations!) Behavior of some «old» SGSN may not be compliant with new specifications (none connectivity for IPv6 PDP context) 11
In a nutshell IPv6 is here Core network devices are mature regarding IPv6 features Devices are more and more IPv6 friendly More time is required for advanced features Main applications (Google, Yahoo, Youtube ) are IPv6 compliant Some Orange affiliates have deployed it and some other operators also Whatever the strategy retained for IPv6 introduction (dual stack or IPv6-only), IPv4 and IPv6 protocols will have to be managed for some time Legacy IPv4 devices and applications will be here for some time 12
Still some efforts to lead.. To avoid any roaming issues To get all required features in devices To be sure middleboxes provide the same level of service than for IPv4 To consider IPv6 and IPv4 for new architectures FMC (Fixed Mobile Convergence), Wi-Fi offload.. But it is also the case for IPv4! 13
QUESTIONS?..THANK YOU 14