1

Chern Yuh Shyang

ychern@maxis.com.my

Maxis Berhad

Introducing IPv6 in Mobile Network

2

Agenda

• Mobile IPv6 Traffic/Devices Outlook

• The Need of IPv6 in Mobile Networks

• Implementation of IPv6 in Mobile Networks

• Mobile Devices Supports on IPv6

• Global IPv6 Deployment

• IPv6 Roaming Scenarios

• Charging & Billing in Mobile Networks with IPv6

• Summary

• Reference

3

11.5B

7.4B

Global Mobile Devices

Global IPv6 Capable

Mobile Devices

Mobile IPv6 Traffic/Devices Outlook

Source: Cisco VNI: Global Mobile Data Traffic Forecast Update 2014 - 2019

52% 54%

Mobile

Data

IPv6 Mobile

Data12%

4

The Need of IPv6 in Mobile NetworksDepletion of IPv4

Source: https://www.google.com/intl/en/ipv6/index.html

• There are more connected devices/internet users than the IPv4 addresses

• IANA assigned last IPv4 block in Feb 2011

• CG-NAT did provide additional address space but also introduced other

issues/limitations

5

The Need of IPv6 in Mobile NetworksSmartphone growth / Adoption of M2M (IoT)

• Smartphone Adoption Rate (GSMA

Intelligence)

- Global adoption rate (2015): 44%

- Malaysia adoption rate (end 2015): 60%

- Typical smartphone behavior (always-

on) further increases the demand of IP

addresses space

• M2M/IoT

- Mass deployment of M2M devices

- The need of globally routable IP

addresses for any devices

Source: GSMA Intelligence: The Mobile Economy 2015

6

The Need of IPv6 in Mobile Networks

3GPP

• PDP Type IPv6 included since 1997

• PDN Type IPv4v6 defined in the first release of LTE in 3GPP Release 8

• PDP Type IPv4v6 defined for GPRS in Release 9

• 3GPP TR23.975 – IPv6 Migration Guidelines

• VoLTE – at least 2 IP addresses required per device

GSMA

• IR.92 – IMS Profile for Voice and SMS

• IPv6 support is mandatory in this guideline

3GPP / GSMA

7

Implementation of IPv6 in Mobile Networks3GPP 3G/LTE Architecture

Internet

RAN

EUTRAN

HLR/HSS

SGSN

GGSN/PGW

SGW

MME

3G

LTE

PDP Type = IPv4, IPv6

and IPv4v6

GPRS/EPS Subscription:

pdpType/pdnType = IPv4, IPv6

and IPv4v6

APN Protocol: IPv4, IPv6

or IPv4/IPv6

FWBR

DNS

AAAA query supported

Provisioning / Policy /

Mediation / Charging

/ Billing / etc.

EPS Bearer, can be IPv4, IPv6 or

IPv4v6 (Since 3GPP Rel.8)

PDP Context, can be IPv4, IPv6 or

IPv4v6 (3GPP Rel.9)

APN Configuration:

IPv4 and/or IPv6

APN Protocol: IPv4, IPv6

or IPv4/IPv6

PDN Type = IPv4, IPv6

and IPv4v6

IPv6 capable

8

Implementation of IPv6 in Mobile Networks3GPP 3G/LTE Architecture – IPv6 requirement

Internet

RAN

EUTRAN

HLR/HSS

SGSN

GGSN/PGW

SGW

MME

3G

LTE FWBR

DNS IPv4

IPv6

IPv6 not requiredIPv6 optional

IPv6 support

required

IPv6 support

optional

Provisioning / Policy /

Mediation / Charging

/ Billing / etc.

Domain IPv6 support

Devices Required

RAN / Mobile

backhaulTransparent

EPC / PS Core Required

IP Core Optional

BR - IX Required

9

Implementation of IPv6 in Mobile NetworksGGSN/PGW – IP Core – IX

Internet

(IPv4 &

IPv6)

GGSN/PGW

Bearer/PDP:

IPv4 or IPv6

IPv4 (IPv6)

IPv6 (IPv4)

Tunneling:

- IPv6 over legacy IPv4 core OR

- IPv4 over new IPv6 core

- Different tunneling technologies

available (ISATAP, 6rd, GRE, etc.)

Internet

(IPv4 &

IPv6)

GGSN/PGW

Bearer/PDP:

IPv6 IPv6NAT

64 IPv6

IPv4

Translation:

- IPv6 translated to IPv4

- NAT64/DNS64 required

- IPv6 only bearer/PDP

Internet

(IPv4 &

IPv6)

GGSN/PGW

Bearer/PDP:

IPv4 and/or IPv6

IPv4

IPv6

Dual Stack:

- IPv4 and IPv6 co-exist

- All nodes to support dual-stack

- Bearer/PDP can be IPv4, IPv6 or

both

10

Implementation of IPv6 in Mobile NetworksBearer/PDP Context: Mobile devices - GGSN/PGW (APN)

IPv4 PDP

IPv6 PDP

GGSN/PGW

IPv4v6 PDP

GGSN/PGW

Internet Internet

(IPv4 &

IPv6)

Internet Internet

(IPv4 &

IPv6)

1a. Separate PDP context for IPv4 and IPv6:

- Accessible to both IPv4 and IPv6

contents

- Higher cost to maintain 2 PDP

- 3GPP Pre-Rel.9 compliant

1b. IPv4v6 PDP context:

- Accessible to both IPv4 and IPv6

contents

- 3GPP Rel.9 onwards only (for 2G/3G)

- Potential Roaming issue

IP assignment strategy #1: both IPv4 address and IPv6 prefix are assigned to devices

11

Implementation of IPv6 in Mobile NetworksBearer/PDP Context: Mobile devices - GGSN/PGW (APN)

IPv6 PDP

GGSN/PGW

NAT

64

DNS

64

IPv6 PDP

GGSN/PGW

NAT

64

DNS

64

CLAT

PLAT

Internet Internet

(IPv4 &

IPv6)

Internet Internet

(IPv4 &

IPv6)

IP assignment strategy #2: only IPv6 prefix assigned to devices

2a. IPv6 only PDP context with DNS64/NAT64:

- Non-IPv6 apps will not work

- Additional nodes (NAT64 and DNS64)

required

2b. IPv6 only PDP context with 464XLAT:

- Accessible to both IPv4 and IPv6 contents

- Additional features required in Devices

(CLAT) and NAT (PLAT)

- Additional nodes (NAT64/DNS64) required

- Not all devices support CLAT

12

Mobile Devices Support on IPv6Comparison of IPv6 support in mobile OS

OS Version Claimed IPv6 Ready Installed by Default DHCPv6 ND RDNSS Notes

Android 5.0 (Lollipop) Yes Yes No Yes

Supports ND-RDNSS in Android 5.0

and above. Does not support

DHCPv6. Suffers from intermittent

loss of its unicast address on some

phones.

iOS 4.1 Yes Yes Yes Yes

iOS supports stateless DHCPv6 since

version 4 and stateful DHCPv6 since

4.3.1.

MeeGo 1.2 No Yes No Yes

Symbian 7 Yes Yes No No

Windows Mobile 6.5 Yes Yes Lite No

If the OEM explicitly unsets the

SYSGEN_TCPIP6 pre-processor

symbol, the built image will not have

any IPv6 capabilities.

7.5 No No No No 8 might have some support

8.1 Yes Yes No NoPrivate lab research. No privacy

extensions (RFC4941)

Windows Phone

Source: https://en.wikipedia.org/wiki/Comparison_of_IPv6_support_in_operating_systems

13

Mobile Devices Supports on IPv6

• Not all mobile OS provide full IPv6 support

• Device manufacturers may enable/disable IPv6 support in certain models, e.g.

• Jelly Bean on manufacturer S does not support IPv6, same OS in manufacturer H does.

• Kit-kat on Model III does not support IPv6, same version on Model IV does

• Menu options (firmware / carrier bundle) to configure IPv6 depends on OS and network

IPv6 support – OS and Manufacturer dependent

14

Global IPv6 DeploymentISP, Equipment Vendors, Web/Content Providers

Percentage of users that access Google over IPv6

Source: http://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption&tab=ipv6-adoption

• World IPv6 Launch (6 June 2012) – Major Internet service providers (ISPs), home networking equipment manufacturers, and web companies around the world are permanently enabling IPv6 for their products and services. (source: http://www.worldipv6launch.org(source: http://www.worldipv6launch.org(source: http://www.worldipv6launch.org(source: http://www.worldipv6launch.org/)/)/)/)

IPv4

IPv6

IPv6

IPv4IPv4

IPv6

We are here today!

How does this impact Mobile IPv6

Deployment Strategy?

- Not all the websites/content

provider and equipment are

IPv6 capable

- IPv4 and IPv6 network will co-

exists for some time

Need to ensure both

networks are accessible!

15

IPv6 Roaming Scenarios

• Pre-Rel.9 SGSN

• IPv4v6 PDN type (LTE) was introduced in Rel.8 (when LTE was first introduced). However, IPv4v6 PDP type for 2G/3G was only introduced in Rel.9, user roaming in a PLMN with pre-Rel.9 SGSN may experience problem

• Potential Impact if PDP type in HLR subscription profile is IPv4v6:

• Case 1 (no service impact): Pre-Rel.9 SGSN ignores the unsupported Info-Element in MAP message

• Case 2 (data service rejected): Pre-Rel.9 SGSN discard the MAP message with unsupported Info-Element

• Roaming partner has not enabled IPv6

• Incorrect data CDR may be reported if roaming partner does not support IPv6 CDR format

IETF RFC 7445

16

IPv6 Roaming ScenariosPre-Release 9 SGSN (Case 1)

SGSN

HLR

GGSN Internet

GPRS Attach

Request

Authentication/

Update LocationInsert Subscriber Data (pdp-Type =

IPv4, ext-pdp-Type=IPv4v6)

Attach Accept

SGSN discards the unsupported ext-pdp-Type

IE, but continue to process the rest of the Insert

Subscriber Data messageVisited Network

Home Network

IPv4 OR IPv6 traffic

17

IPv6 Roaming ScenariosPre-Release 9 SGSN (Case 2)

SGSN

HLR

GGSN Internet

GPRS Attach

Request

Authentication/

Update LocationInsert Subscriber Data (pdp-Type =

IPv4, ext-pdp-Type=IPv4v6)

Attach Reject

SGSN discards the entire Insert Subscriber Data

message due to the presence of unsupported

IE, ext-pdp-Type

Data service failed!

Visited Network

Home Network

18

IPv6 Roaming Scenarios

• Request Roaming partner to get necessary patch on their SGSN to support the “ext-

pdp-Type” MAP Info-Element sent by HLR

• Separate profile in HLR for domestic and roaming (this feature may be vendor

dependent)

• Home Network: MAP-ISD message contains “pdp-Type” and “ext-pdp-Type”

• Visiting Network: MAP-ISD message contains only “pdp-Type”

Possible solution for IPv6 roaming issues

19

Charging & Billing in Mobile Networks with IPv6

SGSN-CDR

SGW-CDR and PGW-CDR

Changes in data CDR field (3GPP TS32.251):

CDR Field Description

Served PDP Address PDP address of the served IMSI, i.e. IPv4 when PDP Type is IPv4

or IPv6 when PDP Type is IPv6 or IPv4v6.

Served PDP/PDN

Address extension

This field holds IPv4 address of the served IMSI, if available,

when PDP type is IPv4v6.

CDR Field Description

Served PDP/PDN

Address

IP address allocated for the PDP context / PDN connection, if

available, i.e. IPv4 when PDN Type is IPv4 or IPv6 when PDN

Type is IPv6 or IPv4v6.

Served PDP/PDN

Address extension

This field holds IPv4 address of the served IMSI, if available,

when PDN type is IPv4v6.

Variable length

Value can be null

20

DD

P

I

Charging & Billing in Mobile Networks with IPv6Impact to the Charging and Billing Domains

IPv4 & IPv6

Internet

SGSN GGSN/DPI

OCS

Mediation

IPv6 Capable DPI

IPv6 Capable online

charging system

IPv6 Capable online

charging system

CDRs with IPv6 CDRs with IPv6

fields vPLMN /Roaming

Partner

Inbound roamer

Outbound roamer

21

Summary

• IPv6 in Mobile Networks is inevitable

• Upgrade/replacement of some core network elements and charging platforms will be

required to enable the IPv6 capability. However, communications between nodes that are

transparent to user traffic can be maintained at IPv4.

• There is no best transition method for IPv6, each organization will have own preference

based on own strategy on how to transition their existing network towards end-to-end IPv6

• IPv4 and IPv6 will co-exists for a period of time (years)

• Each Mobile OS and device manufacturers have their own roadmap in supporting IPv6;

even for the latest OS versions / device model, not all are fully IPv6 capable

• Both 3GPP and GSMA have included IPv6 as a standard requirement in the upcoming

technologies, e.g. VoLTE, non-3GPP access, etc.

• Content providers play a role in transitioning internet towards all IPv6

22

Q & A

23

Reference

• 3GPP 23.060 General Packet Radio Service (GPRS); Service description; Stage 2

• 3GPP 23.401 General Packet Radio Service (GPRS) enhancements for Evolved

Universal Terrestrial Radio Access Network (E-UTRAN) access

• 3GPP 23.975 IPv6 migration guidelines

• 3GPP 29.002 Mobile Application Part (MAP) Specification

• GSMA IR.92 IMS Profile for Voice and SMS

• IETF 7445 Analysis of Failure Cases in IPv6 Roaming Scenarios

• IETF 6877 464XLAT: Combination of Stateful and Stateless Translation

24

Thank you!