Wi-Fi Calling: Supporting voice over Carrier Wi-Fi, Enterprise Wi-Fi and

Residential environments

Byju Pularikkal, Santosh Patil

Mobility Solutions

BRKSPM-2123

Agenda

• Introduction

• VoWiFi Solution Architecture (Untrusted Wi-Fi Access Model)

• VoWiFi Deployment in Trusted Wi-Fi Access

• Hybrid Architecture for VoWiFi

• QoS Deployment Considerations

• Handset Side Requirements

• Inter-RAT Handover Considerations

• International Roaming

• Ongoing work on VoWiFi

• Deployment References

Introduction

What is Voice over WiFi

Use of an IEEE 802.11 WLAN for

vocal conversation

Dedicated HW or “soft phone” on any

Wi-Fi device

Until Recently offered by OTT

(Skype) providers

Focus: MNO Wi-Fi Calling

VoWiFi

• VoWiFi leverage functionalities in SP

Networks

• 60% Plus – Houses have limited 2G, 3G

or 4G coverage

• Most offices have some limited coverage

areas

• VoWiFi solves many coverage issues

very efficiently and cost effectively

• Focus of this session is MNO Wi-Fi

calling

Voice over Wi-Fi Models and Value Creation

• Leverage 100s of MHz of free spectrum to enable all services to be delivered over Wi-Fi

• Address in-door coverage and capacity without additional licensed radio build out

• Become more relevant to subscribers by offering Wi-Fi calling on non-SIM devices

• Increase customer engagement/analytics even when they are “off” the cellular network

Save Money Make Money

• Wi-Fi Carries over 80% of Mobile Data

Growing faster than smartphone cellular data

• 802.11ac to address growth demands

• Capability to address coverage/capacity issues

• Availability of native ePDG client

Seamless support of conversional services

• Identity Ecosystem

For non-UICC and companion devices

• Wi-Fi could support greater than 80% of voice minutes

VoWiFi Elevator Pitch

0

1

2

3

4

5

6

7

8

9

2014 2015 2016 2017 2018 2019

VoWiFi VoLTE VoIP

71%

VoWiFi Minutes of Use Exceed VoLTE by 2018VoWiFi Accounts for 53% of Mobile IP Voice by 2019

53%

41%Minutes of

Use

(Trillions)

per Year

Source: ACG, Cisco VNI Global Mobile Data Traffic Forecast, 2014–2019

6%29%

VoWiFi Market Trends

VoWiFi – Apple iOS 8 Wi-Fi Calling

Voice/Text over Wi-Fi

Standard based:

ePDG/IPSec 3GPP

23.402

Same Phone dialer

for 3G/4G/Wi-Fi voice

Voice Handover

between Wi-Fi/VoLTE

VoWiFi traffic goes to

Mobile Core; Others

goes local

Use VoLTE IMS

VoWiFi to address coverage issues

• 60% Plus – Houses have limited 2G, 3G or 4G coverage

• Most offices have some limited coverage areas

• Challenges around Adoption of Small Cell & DAS deployments

• VoWiFi solves many coverage issues very efficiently and cost effectively

• Residential Good voice quality for people in their own homes

Non guaranteed QoS not expected to be a real challenge

• Restaurant / Coffee shop / … Open… does not mean immediately available... Need to connect first

Wi-Fi infrastructure may not be designed for voice. Coverage holes, Scalability, QoE likely to become an issue in some cases.

Backhaul capacity issues

• Enterprise 802.11n and now ac providing high capacity network

Security challenges (many enterprises block IPSec to external peers)

Require a Wi-Fi network designed with voice in mind to provide a good QoE

VoWiFi target segments

Wi-Fi Calling & the influence on identity ecosystem

• Wi-Fi Calling and HS2.0 clients driving next phase in Non-UICC device support

• Cisco ePDG supports EAP-TLS, EAP-TTLS and EAP-MSCHAPv2 for Non-UICC devices

• HS2.0 OSU support to start managing/provisioning identities of Non-UICC devices

Voice over Wi-Fi Status

• 2015 – The year of VoWiFi

• At least 15 tier-1 MNOs evaluating

• Biggest barriers are around IMS readiness

• Emergency Calling issues still being addressed

• Cisco deployments in key tier-1 operators in North America and Europe

• Wi-Fi Calling being integrated into 6th phase of Cisco’s SP Wi-Fi solutions

VoWiFi Solution Architecture (Untrusted Wi-Fi Access Model)

InternetVoWiFi Solution Architecture• VoWifi Architecture requires:

ePDG

3GPP AAA

PGW with s2b support

PCRF

IMS Core infrastructure

TAS

VoWiFi capable UEs

HSS

• VoWiFi capable UE pre-loaded with operator profile

• UE discovers the ePDG using DNS lookup for ePDG FQDN – Statically or dynamically configured in Operator File

• UE establishes IPSec tunnel to ePDG

• ePDG sets up a PDN session to PGW on behalf of UE

• PGW allocates IP address and manages P-CSCF discovery – provides P-CSCF details to UE

• UE SIP registers with SBC/P-CSCF

• UE makes/receives call via IMS/TAS• P-CSCF discovery over IKE or operator profile

PGWHSS/HLR

Wi-Fi

access

ePDG

SWu

Untrusted network

(e.g. home/ent)

S2b

PMIPv6

GTPv2

SWm

SWn

IPSec

eNodeB NodeB

MME/SG

W

3GPP access

S5/S8

MSC

Gi

RNC

IMS Core

SGSN

TAS

ePDG

PGW PCRF

AAA

IMS/VoLTE

Cisco product

Cisco partner product

Non Cisco

VoWiFi over Untrusted WLAN to EPC Integration using ePDG

AP

AP

WLC

AP

AP

WLC

L3 Infra

ASR5K

ePDG

ASR5K

PGW

A-SBC I-SBC

CSCF TAS

MGCF MGW

L3 vGiLAN

Internet

PSTN

Voic

e C

ore

HSS

AuC

3GPP

AAA Server

PCRF

S2b

IPSec Tunnel

between UE & ePDG

GiLAN

ePDG as defined in Standards

SGi

PCRF

Gx

HSS

S2b

SWn

Operator's IP Services

(e.g. IMS, PSS etc.)

SWm

SWx

Untrusted Non-3GPP IP

Access SWa

HPLMN

Non-3GPP Networks

S6b

Rx

PDN Gateway

ePDG 3GPP AAA Server

Gxb

S2a

Gxa

Trusted Non-3GPP IP

Access STa

Gxc

S5

S6a

3GPP Access

Serving Gateway

UE

SWu

• ePDG is part of the 3GPP LTE SAE defined in 3GPP TS 23.402

• Responsible for interworking between the EPC and un-trusted non-3GPP networks

• ePDG terminates IPSec tunnels established/initiated by UEs via un-trusted Wi-Fi network for secure access to the EPC.

Wi-Fi Un-trusted

Non-3GPP

ePDG Basics – Main Functions

• User Authentication and Authorization IKEv2 based on EAP-AKA

De-capsulation/Encapsulation of packets for IPSec

Tunnel authentication and authorization

APN authorization and PGW selection

Provide PGW identity for static address

• Tunnel and QoS mapping between S2b bearers and access network Mapping of S2b bearer(s) to SWu (IPSec) sessions

Mapping of dedicated bearers on S2b using TFT packet filters

DSCP marking and/or 802.1p tagging for QoS

• Routing of downlink packets towards the SWu instance associated to the PDN connection; Transport level packet marking in the uplink;

Enforcement of QoS policies based on information received over S2b control plane

PGW Function for VoWiFi service

• UE IP address allocation Sent to UE via ePDG

PCEF - Acts on instruction from IMS (via PCRF) to allocate dedicated bearer for Voice

• DNS and P-CSCF server address discovery (and P-CSCF restoration)

• Anchor point for session HO between LTE and Wi-Fi– S6b interface required

• Accounting - PGW CDRs – If required, typically IMS CDRs are used

• QoS implementation based on QCI

ePDG Selection Procedures

• UE obtains DNS server address from AP

• UE generates ePDG FQDN and queries DNS

• DNS returns IP address(es) of ePDG(s)

• UE initiates IPSec connection to selected ePDG

High Level ePDG Call Flow - Session Creation

UE ePDG PGW AAA

1. IKEv2 SA_INIT

2. IKEv2 SA_INIT_RSP

3. IKEv2 AUTH_REQ4. DER

5. DEA6. IKEv2 AUTH_RESP

7. IKEv2 AUTH_REQ8. DER

9. DEA10. IKEv2 AUTH_RESP

11. IKEv2 AUTH_REQ

14. IKEv2 AUTH_RESP

12. Create Session Request

13. Create Session Response

VoWiFi Call setup

UE PGW PCRF

9. RAA

ePDG

14. Create Bearer response

13. Create Bearer Request

8. AAA7. RAR

OCSOFCSP-

CSCF

6. AAR

11. CCR

12. CCA

TAS

1. SIP RE-INVITE

2. SIP RE-INVITE

3. Ro Call Control

5. 200 OK

4. Peer UE procedures

10. 200 OK

LVC (Voice/Video) call ongoing on LTE (Dedicated Bearer)

LVC (Voice) call ongoing on LTE (Dedicated Bearer)

Cisco ePDG solution

SAEGWPGW

H(e)NBGW

SAMOGePDG

Multiple

Hardware

Platforms

Cisco ASR

5k Series

Multimedia

Core Platforms

• Product line is optimized for maximum performance & capital efficiency

• Software functions work across multimedia core platforms

• N:1 internal redundancy (ASR5k) and 1:1 geographical redundancy (All Platforms)

Single Software

(StarOS)

Supporting

Multiple Functions

Cisco ASR 5xxx

Flexibility and

Elasticity

Performance and

Scalability

Cisco Virtualized

Packet Core (vPC)

Op

en

Sta

ck

Cisco Virtual ePDG

Networking

Hardware: x86 server

VMware ESXi(OS + Hypervisor)

ePDGCisco StarOS

Linux Kernel

Networking

Hardware: x86 server

Ubuntu / RedHat (OS)

ePDGCisco StarOS

Linux Kernel

KVM (Hypervisor)

vS

ph

ere

/ v

Clo

ud

• Integrated OS + Hypervisor

• Benefits of Hardware/Network Acceleration

• Single Vendor OS/Hypervisor (VMware)

• KVM as Hypervisor

• Full OS Implementation (Ubuntu / RedHat)

• Multi-Vendor “Open Source” Environment

VMware Ecosystem OpenStack Ecosystem

• Base on COTS x86 server hardware

• Highly scalable: Capacity can be added by adding CPU/memory resource

• Elasticity: Capacity-on-demand

• Field Proven: Same software as physical ePDG

Voice over trusted Wi-Fi Access

VoWiFi over Trusted WLAN to EPC Integration using SaMOG GW

AP

AP

WLC Core Infra

ASR5K

TWAP

TWAG

ASR5K

PGWL3

Internet

PSTN

HSS

AuC

3GPP

AAA Server

PCRF

S2a

CPNR

DHCP

DNS

Cisco

Prime

Infra.

Prime

Perf.

Manager

STa

CAPWAP

L3-GRE

L3-GRE

L2

-GR

E

SWx

S6b

SGi

CMAP +

MAG

CMAP +

EoGRE

Access Infra

A-SBC I-SBC

CSCF TAS

MGCF MGW

Voic

e C

ore

vGiLAN

SaMOG GW (LTE, UMTS)

P-GWAAA

TWAGTWAP

STa

(Diameter)

Radius

S2a

GTPv2

Local Breakout

Web Portal

DHCP

HSS

EAP-SIMNon EAP-SIM

internet

Packet Core

WiFi access

EoGRE PMIPv6 / EoGRE

SWx

Gi

Gi

GGSN

Gn

GTPv1

WLCWLC

AP AP

SaMOG GW

TWAP: Trusted WLAN AAA Proxy

• Subscriber authentication and authorization based on EPC credentials

EAP-AKA, EAP-AKA’ and EAP-SIM over Radius

3GPP Diameter STa interface support

Radius interface towards Trusted WLAN (WLC, AP)

• Subscriber session management (attach, detach and accounting triggers)

UE session establishment upon EAP success

UE session teardown based on Radius message from Trusted WLAN

Radius accounting message support

TWAG: Trusted WLAN Access Gateway

• Data path connectivity to EPC for Tunnel Switching and packet forwarding

S2a interface to the PGW (3GPP TR 23.852 )

GTPv2-C (control), GTP-U (for data)

Bearer management support

Cisco SaMOG GW – Key differentiators

• 3GPP Complaint SaMOG GW plus Flow based LBO

• Authentication

EAP-AKA’ using Radius / Diameter

Web Authentication

• Local Breakout - Direct connectivity to the Internet

Policy-based APN selection, CDR generation, Legal Intercept

• Web Authorization

For non EAP-SIM UE (tablet, laptop)

• IP Session continuity for Rel 11 UEs

PGW anchor point preserved over LTE WiFihandovers

• 3GPP Rel.11 trusted Wi-Fi model did not place any UE requirements for PDN connectivity

• Rel.11 trusted Wi-Fi model cannot support APN signaling and simultaneous PDNs

• Assumes managed Wi-Fi access with secured SSID ( by the carrier or partner)

• No client based secured tunnel between UE and packet core

Challenges around VoWiFi over Trusted Access

Hybrid Solution for Wi-Fi Calling

Optimized Wi-Fi Calling over EPC based Carrier Wi-Fi (Supported on Cisco ePDG)

NSWO + Wi-

Fi Calling

Client

Default APN

P-GW

S2a

IKEv2

allocated

2610:8dba:82

e1:ffff::/64

DHCP

allocated

173.38.0.1

Default APN

Configuration

UE Pool:

173.38.0.0/24

802.11

Host:

10.10.1.1

ePDG

Including

SWu NAT

traversal

functionality

IP

IPv4

Internet

173.38.2.1

DNS Resolves

ePDG to

173.38.2.1

SIPTO

Enabled

TWAG

NAT

Outside Pool:

173.38.1.0/24

SIPTO

Match IP

173.38.2.1

SWu

SWu

NSWO

QoS Deployment Considerations

LTE vs Wi-Fi Bearer Comparison

eNodeBUE

Default Bearer (SIP)

QCI 5

Voice / QCI 1

Default Bearer (SIP)

QCI 5Default Bearer (SIP)

QCI 5IMS IPv6

S1u S5

Voice / QCI 1 Voice / QCI 1

Video / QCI 2 Video / QCI 2 Video / QCI 2

Radio

UE

SIP, Voice, VideoDefault Bearer (SIP)

QCI 5IMS IPv6

SWn

(IPSec)

S2b

Video / QCI 2

802.11

(IPSec)

SGW PGW

PGWAP

Voice / QCI 1WiFi QoS

WMM (802.11e)

DSCP based

Video option

ePDG

VoWiFi over untrusted access - E2E QoS

LTE QCI

QCI to IP

DSCP mapping

DSCP

Downlink

802.11e WMM

802.11acLTE QCI DSCP

Uplink

DSCP

802.11e WMM

802.11ac

QoS and Dedicated Bearer Creation

UE ePDG PGW PCRF IMS

1. Rx AAR / AAA

11. Create Bearer Request

3. Create Bearer Response

IMS core gets SIP invite

and it requests QoS from

EPC2. Gx RAR / RAA

PCRF installs PCC rules

on PGW

AP

Voice traffic prioritized in

the SP network

AP

ePDG marks traffic on SWu

to allow AP to enable WMM

Fast re-auth improves

HO performance IMS core operates the

same for VoLTE on LTE

and on WiFi

Internet

Voice Quality and Requirement

PGWEPDGWi-Fi VoIP – Control plane

IPSec VoIP – User plane

3GPP

AAA

SWm

• Bandwidth Requirement

Typically VoWiFi uses AMR-WB: 56.65 kbps per call

• Jitters and Latency

Latency: Propagation, transport, packetization, jitter buffer

Jitter: The variable arrival interval between packets

NAT

IMS

Ideal Tolerable

One way

Latency/Delay

<75ms 75ms -100ms

Jitter <2ms 2ms-10ms

Handset side requirement for Wi-Fi Calling

Mobile handset Wi-Fi User trend

More than

90%

Native VoWiFi calling App

Wifi Calling Native OTT

Client Native/embedded

with Phone OS (iOS,

Samsung & Nokia)

Downloaded as an

app

Dial Pad Same dial pad for

2/3/4G and VoWiFi

Different dial pad

between cellular and

VoWiFi

Wi-

Fi/Cellular

mobility

VoWiFi/VoLTE

supported

Not supported. Voice

call will drop when Wi-

Fi is lost

Wifi calling

Native AppOTT App

VoWiFi Handset support

• Wi-Fi Calling support in iPhone 5s/5c and iPhone 6/6+

Apple

Android

• No native Android OS support yet

• Samsung S6/S6-Edge Wi-Fi calling in selected markets

• Microsoft's Lumia 640

Handset Dialer View• User will have a “preference” to

offload Voice to WLAN

• UE will offload Voice to WLAN

when available and LTE

coverage is below a threshold

• Currently no method to restrict

where VoWiFi is used

• Roaming user can choose to

utilize Wi-Fi when traveling

internationally

• Handovers of E911 calls to LTE

are not supported in 3GPP TS

23.402 , Custom solutions are

available though

• Hosts SWu and IMS Clients – Natively embedded within the OS

UE Connection manager performs traffic steering/routing

• Performs ePDG selection static or dynamic FQDN of ePDG

Static – e.g. epdg.cisco.com

Dynamic – epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org - Allows selection of ePDG in VPLMN

• Initiates IPSEC tunnel establishment towards ePDG using IKEv2 (Including DPD)

• Contains Identity for authentication

Idi in form of root NAI (IMSI@realm); Fast Reauth ID; X.509 certificate etc

• UE is pre-configured with operator profile/carrier bundle which defines a set of policies

Criteria for RAT selection – based on RSSI and packet loss

Whether Inter RAT HO is supported – HO Can be enabled/disabled …. Etc

VoWiFi considerations on UE

Example parameters from carrier bundle

• RAT Selection criteria Use Wi-Fi if RSSI threshold > -75dBM

Use Wi-Fi if packet loss < 2%

• Guard timer – 2 mins Used to avoid ping-pong between RAT Types

• IKE DPDEnabled – True

DPDInterval – 600s

DPDMaxRetries & Retry Interval – 4&10

• IMS Config EnableWiFiCallingWithoutEntitlement – True

P-CSCF - 192.168.1.1

defaultAuthAlgorithm - AKAv1-MD5

• Child SAs

ChildProtocol – ESP

DHGroup – 2

EncryptionAlgorithm – Array of protocols e.g. 3DES

IntegrityAlgorithm - Array of protocols e.g. SHA1-96

Lifetime – 8640s

• Remote Address

epdg.<domain>.com

• 3GPP Config

APN – IMS

SupportsVolteCapability – True

Non SIM Handset access

Companion Device

Compete with Skype/Facetime

One Number

Increase Service Stickiness

Calling from PC, tablets, iPads

Re-use existing

infrastructure and

systems

Service across the

internet – across

devices

Proven, reliable,

standard interfaces

How to

Authenticate these

Devices ???

• As non UICC devices do not haveIMSI, customized vIMSI in format similar to UICC IMSI uniquely identifying the non UICC device needs to be shared by the device

• ePDG supports the X.509 certificate based authenticationand also communicates with OCSP(Online Certificate Status Protocol) server for completing the authentication.

• Once the authentication is doneePDG communicates with AAA server for ensuring the authorization of the device.

• Operator need to establish Certificate management system for the handset devices

X.509 based authentication

EAP-TLS based authentication

• EAP method encapsulating TLS session

• Two phases

Handshake phase (server authentication & key generation)

Data Phase (client authentication)

• Handshake phase provides secure channel for data phase

• Use MSCHAPv2 for authenticating client/device

• Reference RFC 5281

• Single phase

• EAP method encapsulating TLS session

• Use certificates between UE & AAA server for mutual authentication

• Reference -RFC 5216

EAP-TTLS based authentication

Inter-RAT Handover Consideration

Moving to Standard based handover (WiFi-LTE)

LTE to Wi-Fi inter RAT Hand Over

• UE connects to LTE, selects PGW. MME updates HSS with PGW ID over S6a (Notify)

• UE moves to Wi-Fi and sets up IPSec with HO indication. ePDG gets PGW ID over SWm and HSS

• ePDG sets up PDN connection with APN/IMSI pair and the PGW finds the existing LTE session and assigns same IP address/services – PCRF updated if necessary

• PGW updates PGW FQDN over S6b to AAA and AAA updates HSS to ensure WiFi to LTE also selects the same PGW

ePDG

SGW

PGW

eUTRAN

WiFi

PCRF

Gx

S5

S2bMME

S6a S6b

SWmDNS

HSS 3GPP

AAA

• IMS Centralized Services entity – SCC (Service Centralization and Continuity) ASprovides Call Continuity Function between WiFi and 2G/3G

• 3GPP defined Dual Radio VCC (DR-VCC) specification is utilized at Client Sidefor the handover from WiFi to 2G/3G. TS 23.237 – Dynamic STN method

Handover from Wi-Fi to 2G/3G

NodeB

PGWAP ePDG

RNC

IMS Core and service

2G/3G Core and service

P/S-CSCF, SCC AS ,

MGCF etc …

HLR, SMSC

IN/SCP etc …

Handover of Active

call between Wi-Fi

and 2G/3G with Call

Continuity function

SCC ASMSC

WiFi to 2G/3G handover method

SCC ASP/S-CSCF MCGF

MGW

NodeBRNC MSC/VLR

WiFi AP

VoWiFi Control Signaling path

VoWiFi Call Bearer path

2G/3G Control Signaling path

2G/3G Call Bearer path

Handover Control Signaling path

APN and IP Address Logic in UE

ePDG

SGW

PGW

MMELTE

Modem

Non 3GPP

Modem

WiFi

Modem

Connection

Manager

APN1

APN2

APN Connection

Policy

IP-WIPSec

IP2

IPSec

IP1

Virtu

al IP

2V

irtual IP

1

IP1

IP2

• Policy selects

seamless, non

seamless or LTE

access for each APN

• Virtual IP

interfaces hides

interface changes

on inter RAT events

• Connection manager

connects to Wi-Fi AP

iRA

TLogic

Internet

• Connection threshold

management based on RSSI,

beacons, SNR, 802.11k and

802.11v, rate shifting

International Roaming with VoWiFi

International RoamingExisting

MSC/I

MSForeign

PLMN

Home PLMN

OTTMSC/I

MS

OTT

ClientForeign

IP/Wifi

VoWifi

MSC/

IMSForeign

Wifi

ePDG/

PGW

Home MSISDN

OTT MSISDN

Home MSISDN

Home PLMN

Home PLMN

Same home mobile number for MO/MT

No need to pay expensive roaming charge

Same phone dialer for mobile and wifi call

Capture revenue long lost to OTT

No need to pay roaming partners

International Roaming Savings - Example

VoWiFi- Ongoing work

• UE Support , IOS support is major driver - growing with Android and other OS.

• E911 calling – location and Handover

• Wi-Fi Infrastructure designed for voice in mind to ensure the QoE

• Wi-Fi calling location is becoming important

• Enterprise challenges (Enterprise blocking IPSec to external peers)

VoWiFi Challenges and work in progress

• Charging/Taxation: Non-bundled consumption requires location to be identified

Roaming typically not-bundled and hence countries need to apply tax rates according to roamed to country

• Analytics: Operators would like to establish where Wi-Fi calling is being consumed .Can be used to target infrastructure investment or other offers

• Emergency calling: Need to provide PSAP with location where emergency call is originated

• Regulatory: Location of Wi-Fi Calling target may be required to be presented to LEA

• Authorization: Operators may desire to only authorize Wi-Fi calling service in certain locations

A number of diverse drivers for location in Wi-Fi Calling

• IPSec connection from Handset to ePDG

• Security Concern for Enterprise

Opening up hole in network

Not able to Monitor the traffic – IPSEC L3 encryption

Opening up network towards multiple operators ePDG.

• Potential security threats with compromised handset in enterprise

Enterprise IPSec Blocking

Cisco VoWiFi References

• First deployed in Verizon USA for iWLAN in 2013

• Wi-Fi Calling operators at iPhone 6 launch EE UK (Cisco ePDG) and T-Mobile USA (Cisco PGW)

• Cisco won VoWiFi: 2 major Tier-1 Mobile SP in USA

Major Tier-1 Mobile SP in Europe

• Other VoWiFi engagements: 17+ on-going trials

VoWiFi : Wi-Fi Calling DeploymentsCisco References

VoWiFi – WiFi Calling Deployment

• EE announced WiFi Calling support at iPhone 6 launch

• Driver for WiFi Calling

Enhances indoor voice coverage

Same price for VoLTE, VoWiFi and cellular calls

EE: You can use WiFi Calling anywhere there's no reception but there is WiFi, like rural areas or the London Underground.

• Other Operation details

IMS APN traffic goes to ePDG and all other data local breakout wifi

IPSec tunnel always up when wifi connected. Capable for outgoing/incoming calls

Voice service only at launch SMS to follow

Also plan to support Non-SIM devices

Cisco VoWiFi Differentiations

Proven solution and Leader in VoWiFi

Multi-service software

Multi-platform: virtual, high scale

gateway

Hybrid trusted/untrusted solution

Enhanced VoWiFi Core

• Deployed in EE UK and Verizon USA

• ePDG contracts awarded by major tier-1 mobile SP in

US and Europe

• ePDG, SAMOG GW, PGW, HNBGW in a single box

• ePDG available in

• Dedicated HW: ASR5500, ASR5000

• Virtual NFV x86 platform: vPC

• Co-existence of ePDG and SAMOG with optimized

routing

• Cisco ePDG offers access network visibility: Roaming

access whitelist/blacklist and other features

• Security: DOS attack protection/mitigation mechanisms

End to End VoWiFi Solution• Cisco Universal Wi-Fi on Access side

• StarOs based Packet Core

• Cisco Policy Suite , 3GPP AAA

Thank You!