Colloque IPv6 Colloque IPv6 Colloque IPv6 Colloque IPv6 Caen, 13 Juin 2013 Strat Strat Strat Straté égie de d é é gie de dé gie de d gie de d é é éploiement ploiement ploiement ploiement d’ d d d ’ ’ ’IPv6 dans les r IPv6 dans les r IPv6 dans les r IPv6 dans les ré éseaux é é seaux seaux seaux mobiles mobiles mobiles mobiles David BINET Orange
Agenda � Mobile services: Orange group in few figures Mobile services: Orange group in few figures Mobile services: Orange group in few figures Mobile services: Orange group in few figures � IPv6 introduction: the context IPv6 introduction: the context IPv6 introduction: the context IPv6 introduction: the context � IPv6 introduction strategy IPv6 introduction strategy IPv6 introduction strategy IPv6 introduction strategy � Hurdles and drivers Hurdles and drivers Hurdles and drivers Hurdles and drivers � Synthesis and next steps Synthesis and next steps Synthesis and next steps Synthesis and next steps David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 1
Orange Mobile footprint Tunisia Jordan Egypt U K Sénégal Mali Niger Poland Belgium Guinée-Bissau République Centrafricaine Guinea Cameroun Luxembourg Slovakia Austria Moldova Côte d’Ivoire Uganda Kenya France Guinée Romania Switzerland Equatoriale Armenia at end 2012 Madagascar Spain Botswana Dominican republic Mauritius Caribbean Islands mobile Vanuatu La Réunion 172 million customers Employees 170 000 employees Fixed broadband 15 million customers consolidated revenues € 43.5 billion David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 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 David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 3
…and common requirements User may access to services through Some applications may remain IPv4 IPv4-only devices visited network (roaming) will be the based majority (at least during first phase) BSC BSC BSC BSC IPv4 IPv4 IPv4 IPv4 GGSN GGSN GGSN GGSN SGSN SGSN SGSN SGSN Orange Services Orange Services Orange Services Orange Services IP backbone IP backbone IP backbone IP backbone RNC RNC RNC RNC INTERNET INTERNET INTERNET INTERNET IPv4 IPv4 IPv4 IPv4 Border Gateway Border Gateway Border Gateway Border Gateway IPv4 IPv4 IPv4 IPv4 Impacts on devices IPv6 IPv6 IPv6 IPv6 should be limited S S- S S - -GW - GW GW GW P P- P P - -GW - GW GW GW Orange Services Orange Services Orange Services Orange Services IP backbone IP backbone IP backbone IP backbone e INTERNET INTERNET INTERNET INTERNET LTE/EPC network will be deployed IPv6 IPv6 IPv6 IPv6 David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 4
IPv6 introduction strategy IPv6 only IPv4 only IPv4/IPv6 connectivity connectivity connectivity IPv4 Service continuity One IPv4v6 solutions PDP context /EPS bearer preferably Optimized solution for walled Garden services (M2M) Applications should be Address family Independent 2013: Poland Optional phase David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 5
IPv6 introduction strategy (2) � First (optional) step: Dual Stack (2 options) One PDP context for IPv4 and IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 IPv4 PDP context IPv6 Orange Services Orange Services Orange Services Orange Services GGSN/P- GGSN/P -GW GW GGSN/P GGSN/P - - GW GW GGSN GGSN GGSN GGSN Is the preferred option But IPv6 PDP context only Available or from Release 8 (LTE) and IPv4v6 PDP context Release 9 (GPRS) INTERNET INTERNET INTERNET INTERNET IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 � Second step: IPv6-only Internet Internet Internet Internet Orange applications Orange applications Orange applications Orange applications GGSN GGSN GGSN GGSN IPv6 IPv6 IPv6 IPv6 GGSN GGSN GGSN GGSN IPv6 PDP context NAT64/ GGSN/P GGSN/P- GGSN/P GGSN/P - - -GW GW GW GW DNS64 CLAT function IPv4 IPv4 IPv4 IPv4 Applications should be Address Family Applications should be Address Family Applications should be Address Family Applications should be Address Family Internet/ Orange Internet/ Orange Internet/ Orange Internet/ Orange Independent to reduce traffic in NAT64 function Independent to reduce traffic in NAT64 function Independent to reduce traffic in NAT64 function Independent to reduce traffic in NAT64 function applications applications applications applications David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 6
IPv6 introduction impacts on mobile architecture AAAA Information Customers (+DNS64 Management function) (PDP types) Terminals must DNS DNS DNS DNS support IPv6 HLR HLR HLR HLR (IPv6, IPv4v6 Functions update PDP contexts) (FW/DPI/LI) New function (NAT64) IPv4 IPv4 IPv4 IPv4 Applications Applications Applications Applications SGSN/ SGSN/ SGSN/ SGSN/ RAN GGSN/ GGSN/ GGSN/ GGSN/ Gi Interface Router IP backbone IP backbone IP backbone IP backbone Router S S S S- - -GW - GW GW GW P P P P- - -GW - GW GW GW No impacts IPv6 support IPv6 support IPv6 support (IPv4 transport) on user plane on user plane on applications APN management “No” impacts (6PE design ) David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 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 – … David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 8
Main hurdles - Devices draft draft draft draft- - - -ietf ietf- ietf ietf - - -v6ops v6ops v6ops v6ops- - - -mobile mobile mobile mobile- -device - - device device- device - -profile - profile profile- profile -03 - - 03 03 03 � This document is for: This document is for: This document is for: 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 Cross SDO (standards Developing Organization) document Cross SDO (standards Developing Organization) document Cross SDO (standards Developing Organization) document � Multi operators initiative Multi operators initiative Multi operators initiative Multi operators initiative � Document structure Document structure Document structure Document structure – basic Connectivity requirements – 3GPP interface – WLAN interface (IEEE 802.11) – Advanced requirements – Mobile Devices with LAN Capabilities – APIs & Applications David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 9
Hurdles: (s)Gi interface impacts IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 IPv4/IPv6 Applications Applications Applications Applications Mobile network GGSN/P- GGSN/P GGSN/P GGSN/P - -GW - GW GW GW Gi Interface - 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) David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 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) David BINET - Orange 13 juin 2013 Colloque IPv6 – Université de Caen 11
Recommend
More recommend
