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

Handset Side Requirements

VoWiFi Solution Architecture

Inter-RAT Handover
Considerations

International Roaming

Ongoing work on VoWiFi

Deployment References

(Untrusted Wi-Fi Access Model)

VoWiFi Deployment in Trusted

Wi-Fi Access

Hybrid Architecture for VoWiFi

QoS Deployment Considerations

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

VoWiFi

Until Recently
offered by OTT
(Skype) providers

Focus: MNO Wi-Fi

Calling

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

Make Money

Save Money

Leverage 100s of MHz of free

spectrum to enable all services
to be delivered over Wi-Fi

Become more relevant to

subscribers by offering Wi-Fi
calling on non-SIM devices

Address in-door coverage and

capacity without additional
licensed radio build out

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

VoWiFi Elevator Pitch

Wi-Fi Carries over 80% of

Mobile Data

Growing

Seamless

faster than
smartphone cellular data

802.11ac to address growth

demands

Capability to address
coverage/capacity issues

Availability of native ePDG

client
support of conversional

services

Identity Ecosystem
For

non-UICC and companion

devices

Wi-Fi could support greater

than 80% of voice minutes

VoWiFi Minutes of Use Exceed VoLTE by 2018

VoWiFi Accounts for 53% of Mobile IP Voice by 2019

Minutes of
Use
(Trillions)
per Year

9
8
7
6
5
4
3
2
1 71%
29%
0

2014

VoWiFi

VoLTE

VoIP

53%
41%

6%
2015

2016

2017

2018

2019

Source: ACG, Cisco VNI Global Mobile Data Traffic Forecast, 20142019

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

VoWiFi target segments

Residential

Restaurant / Coffee shop /

Good voice quality for people in their own homes

Non guaranteed QoS not expected to be a real challenge

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

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, EAPTTLS and EAP-MSCHAPv2 for NonUICC 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 Ciscos SP Wi-Fi

solutions

VoWiFi Solution Architecture

(Untrusted Wi-Fi Access Model)

VoWiFi Solution Architecture

Internet

VoWifi Architecture requires:

ePDG

3GPP AAA

PGW with s2b support

PCRF

IMS Core infrastructure

TAS

VoWiFi capable UEs

HSS

TAS

Cisco product

IMS Core

AAA
Non Cisco

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

PCRF

Cisco partner product

PGW
PGW

HSS/HLR

S5/S8
SWm

S2b
PMIPv6
GTPv2

ePDG
ePDG

Wi-Fi
access

MME/SG
W

Gi

MSC

SGSN

3GPP access

RNC

SWn

Untrusted network
(e.g. home/ent)

SWu

eNodeB
IMS/VoLTE
IPSec

NodeB

VoWiFi over Untrusted WLAN to EPC Integration using ePDG

PSTN

AuC
HSS
MGW

CSCF
3GPP
AAA Server

Voice Core

MGCF

TAS

AP
WLC

A-SBC

IPSec Tunnel
between UE & ePDG

ASR5K

AP

L3 Infra

ePDG

I-SBC

ASR5K
L3
PGW

vGiLAN
GiLAN

S2b
AP
WLC
PCRF
AP

Internet

ePDG as defined in Standards

ePDG is part of the 3GPP LTE

SAE defined in 3GPP TS 23.402

HSS
SWx
S6a

PCRF
Gxc

Responsible for interworking

between the EPC and un-trusted
non-3GPP networks

Rx
Gx
SGi

3GPP
Access

Serving
Gateway

PDN
Gateway
S5

S6b

S2b

Gxb

ePDG terminates IPSec tunnels HPLMN

established/initiated by UEs via Non-3GPP
Networks
un-trusted Wi-Fi network for
secure access to the EPC.

SWm
3GPP AAA
Server

ePDG

S2a

Operator's IP
Services
(e.g. IMS, PSS
etc.)

SWn
Gxa

Non-3GPP

Trusted
Non-3GPP IP
Access

SWu

Untrusted
Non-3GPP IP
Access
UE

Wi-Fi Un-trusted

SWa

STa

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

PGW

ePDG
1. IKEv2 SA_INIT
2. IKEv2 SA_INIT_RSP
3. IKEv2 AUTH_REQ
4. DER
6. IKEv2 AUTH_RESP
7. IKEv2 AUTH_REQ

10. IKEv2 AUTH_RESP

11. IKEv2 AUTH_REQ

5. DEA
8. DER
9. DEA

12. Create Session Request

13. Create Session Response

14. IKEv2 AUTH_RESP

AAA

VoWiFi Call setup

ePDG

UE

PGW

PCRF

OFCS

OCS

PCSCF

TAS

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

1. SIP RE-INVITE
2. SIP RE-INVITE
3. Ro Call Control

4. Peer UE
procedures
5. 200 OK
6. AAR
7. RAR
8. AAA
9. RAA
10. 200 OK

11. CCR
12. CCA
13. Create Bearer Request
14. Create Bearer response

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

Cisco ePDG solution

Single Software
(StarOS)
Supporting
Multiple Functions

H(e)NBGW

ePDG

SAMOG
PGW

SAEGW

Performance and
Scalability

Multiple
Hardware
Platforms
Cisco ASR
5k Series
Multimedia
Core Platforms

Cisco ASR 5xxx

Flexibility and
Elasticity

Cisco Virtualized
Packet Core (vPC)

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)

Cisco Virtual ePDG

VMware Ecosystem

OpenStack Ecosystem

ePDG

ePDG

Cisco StarOS
Linux Kernel

Cisco StarOS
Linux Kernel

Hardware: x86 server

Networking

Ubuntu / RedHat (OS)

Hardware: x86 server

OpenStack

(OS + Hypervisor)

KVM (Hypervisor)

vSphere / vCloud

VMware ESXi

Networking

Integrated OS + Hypervisor

KVM as Hypervisor

Benefits of Hardware/Network Acceleration

Full OS Implementation (Ubuntu / RedHat)

Single Vendor OS/Hypervisor (VMware)

Multi-Vendor Open Source Environment

Base on COTS x86 server

hardware
Highly scalable: Capacity
can be added by adding
CPU/memory resource
Elasticity: Capacity-ondemand
Field Proven: Same
software as physical ePDG

Voice over trusted Wi-Fi Access

VoWiFi over Trusted WLAN to EPC Integration using SaMOG GW

PSTN
CM

AuC
Access Infra

AP +
EoGRE

CPNR
DHCP

CM

DNS

Cisco
Prime
Infra.

HSS

Prime
Perf.
Manager

SWx

STa

CSCF

PCRF

3GPP
AAA Server

A-SBC

L2-GRE

S6b

AP
WLC

L3-GRE

Core Infra

TWAP

SGi

L3
PGW

TAS

I-SBC

ASR5K

ASR5K

S2a
L3-GRE

MGW

MGCF

Voice Core

AP +
MAG

vGiLAN

TWAG

AP
CAPWAP

Internet

SaMOG GW (LTE, UMTS)

internet

HSS
SWx

AAA

Gi

P-GW

GGSN

Gi

Gn
STa
GTPv1
(Diameter)
Radius
EAP-SIM
Non EAP-SIM

Web Portal
Packet Core
WiFi access

TWAP

S2a
GTPv2
Local Breakout

TWAG

DHCP

PMIPv6 / EoGRE

EoGRE

WLC

AP

WLC

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 WiFi
handovers

Challenges around VoWiFi over Trusted Access

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

Hybrid Solution for Wi-Fi Calling

Optimized Wi-Fi Calling over EPC based Carrier Wi-Fi

(Supported on Cisco ePDG)
NAT
Outside Pool:
173.38.1.0/24

IKEv2
allocated
2610:8dba:82
e1:ffff::/64

Host:
10.10.1.1

SWu

173.38.2.1
ePDG

SIPTO
Enabled
TWAG

NSWO + WiFi Calling

Client

Including
SWu NAT
traversal
functionality

Default APN
P-GW

SWu
DHCP
allocated
173.38.0.1

802.11

SIPTO
Match IP
173.38.2.1

S2a

Default APN
Configuration
UE Pool:
173.38.0.0/24

IP

NSWO
IPv4
Internet

DNS Resolves
ePDG to
173.38.2.1

QoS Deployment Considerations

LTE vs Wi-Fi Bearer Comparison

UE

UE

Radio

eNodeB

S1u

SGW

S5

Default Bearer (SIP)

QCI 5

Default Bearer (SIP)

QCI 5

Voice / QCI 1

Voice / QCI 1

Default Bearer (SIP)

QCI 5
Voice / QCI 1

Video / QCI 2

Video / QCI 2

Video / QCI 2

802.11
(IPSec)

AP

SIP, Voice, Video

WiFi QoS
WMM (802.11e)
DSCP based

SWn
(IPSec)

PGW

IMS IPv6

Video option

S2b
ePDG

PGW

Default Bearer (SIP)

QCI 5
Voice / QCI 1
Video / QCI 2

IMS IPv6

VoWiFi over untrusted access - E2E QoS

Uplink
802.11e WMM
802.11ac

DSCP

LTE QCI

DSCP

Downlink
802.11e WMM
802.11ac

LTE QCI

QCI to IP
DSCP mapping

DSCP

QoS and Dedicated Bearer Creation

UE

AP
AP

ePDG

PGW

PCRF
1. Rx AAR / AAA

IMS
IMS core gets SIP invite
and it requests QoS from
EPC

2. Gx RAR / RAA

3. Create Bearer Response

PCRF installs PCC rules

on PGW

11. Create Bearer Request

ePDG marks traffic on SWu

to allow AP to enable WMM
Fast re-auth improves
HO performance

Voice traffic prioritized in

the SP network

IMS core operates the

same for VoLTE on LTE
and on WiFi

Voice Quality and Requirement

3GPP
AAA

Internet

Wi-Fi

NAT

SWm

PGW

EPDG

IPSec

IMS

VoIP Control plane

VoIP User plane

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

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

WiFi/Cellular
mobility

VoWiFi/VoLTE
supported

Not supported. Voice

call will drop when WiFi is lost

Wifi calling

Native App

OTT App

VoWiFi Handset support

Apple

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

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

VoWiFi considerations on UE

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

Example parameters from carrier bundle

RAT Selection criteria

Child SAs

Use Wi-Fi if RSSI threshold > -75dBM

ChildProtocol ESP

Use Wi-Fi if packet loss < 2%

DHGroup 2

Guard timer 2 mins

Used to avoid ping-pong between RAT Types

EncryptionAlgorithm Array of protocols e.g. 3DES

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

Lifetime 8640s

IKE
DPDEnabled True
DPDInterval 600s
DPDMaxRetries & Retry Interval 4&10

IMS Config
EnableWiFiCallingWithoutEntitlement True

P-CSCF - 192.168.1.1
defaultAuthAlgorithm - AKAv1-MD5

Remote Address
epdg.<domain>.com

3GPP Config
APN IMS
SupportsVolteCapability True

Non SIM Handset access

Calling from PC, tablets, iPads

Service across the
internet across
devices

Companion Device
Compete with Skype/Facetime
One Number
Increase Service Stickiness

How to
Authenticate these
Devices ???

Proven, reliable,
standard interfaces

Re-use existing
infrastructure and
systems

X.509 based authentication

As non UICC devices do not have

IMSI, 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 authentication
and also communicates with OCSP
(Online Certificate Status Protocol)
server for completing the
authentication.

Once the authentication is done

ePDG communicates with AAA
server for ensuring the authorization
of the device.

Operator need to establish

Certificate management system for
the handset devices

EAP-TTLS based
authentication

EAP-TLS based
authentication

Single phase

EAP method encapsulating TLS

session

EAP method encapsulating TLS

session

Two phases

Use certificates between UE & AAA

server for mutual authentication
Reference -RFC 5216

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

Inter-RAT Handover
Consideration

Moving to Standard based handover (WiFi-LTE)

LTE to Wi-Fi inter RAT Hand Over

eUTRAN
SGW
S6a
MME
DNS

S5
S6b

HSS 3GPP
AAA

SWm

S2b

PGW
Gx

WiFi

PCRF

ePDG

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

Handover from Wi-Fi to 2G/3G

IMS Centralized Services entity SCC (Service Centralization and Continuity) AS

provides Call Continuity Function between WiFi and 2G/3G

3GPP defined Dual Radio VCC (DR-VCC) specification is utilized at Client Side
for the handover from WiFi to 2G/3G. TS 23.237 Dynamic STN method
IMS Core and service

P/S-CSCF, SCC AS ,
MGCF etc

AP

Handover of Active
call between Wi-Fi
and 2G/3G with Call
Continuity function
SCC AS

ePDG

PGW

HLR, SMSC
IN/SCP etc

NodeB

RNC

MSC

2G/3G Core and service

WiFi to 2G/3G handover method

WiFi AP

P/S-CSCF

SCC AS

MCGF

MGW

NodeB

VoWiFi Control Signaling path

VoWiFi Call Bearer path

MSC/VLR

RNC

2G/3G Control Signaling path

2G/3G Call Bearer path

Handover Control Signaling path

APN and IP Address Logic in UE

Connection threshold
management based on RSSI,
beacons, SNR, 802.11k and
802.11v, rate shifting

APN2

IP1
IP2

iRAT Logic

Connection manager
connects to Wi-Fi AP

APN1

Virtual IP2

Virtual IP
interfaces hides
interface changes
on inter RAT events

APN Connection
Policy

Virtual IP1

Policy selects
seamless, non
seamless or LTE
access for each APN

LTE
Modem

MME

Non 3GPP
Modem
SGW

IPSec
IP1
IPSec
IP2

IP-W

PGW

Connection
Manager
WiFi
Modem

ePDG

Internet

International Roaming with

VoWiFi

International Roaming
Existing

Home PLMN

Home MSISDN

MSC/I
MS

Foreign
PLMN
OTT MSISDN

OTT
Client

Foreign
IP/Wifi

OTT

MSC/I
MS
Home PLMN

VoWifi

Home PLMN
Home MSISDN

Foreign
Wifi

ePDG/
PGW

MSC/
IMS

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

VoWiFi Challenges and work in progress

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)

A number of diverse drivers for location in Wi-Fi

Calling

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

Enterprise IPSec Blocking

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

Cisco VoWiFi References

VoWiFi : Wi-Fi Calling Deployments

Cisco 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 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

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

Multi-platform: virtual, high scale

gateway

ePDG available in
Dedicated HW: ASR5500, ASR5000
Virtual NFV x86 platform: vPC

Hybrid trusted/untrusted solution

Co-existence of ePDG and SAMOG with optimized

routing

Enhanced VoWiFi Core

End to End VoWiFi Solution

Cisco ePDG offers access network visibility: Roaming

access whitelist/blacklist and other features
Security: DOS attack protection/mitigation mechanisms
Cisco Universal Wi-Fi on Access side
StarOs based Packet Core
Cisco Policy Suite , 3GPP AAA

Thank You!