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
(Untrusted Wi-Fi Access Model)
Considerations
• VoWiFi Deployment in Trusted
• International Roaming
Wi-Fi Access
• Ongoing work on VoWiFi
• Hybrid Architecture for VoWiFi
• Deployment References
• QoS Deployment Considerations
Introduction
What is Voice over WiFi

• VoWiFi leverage functionalities in SP

Use of an IEEE Dedicated HW or
802.11 WLAN for “soft phone” on any Networks
vocal conversation Wi-Fi device • 60% Plus – Houses have limited 2G, 3G
or 4G coverage
• Most offices have some limited coverage
areas
VoWiFi • VoWiFi solves many coverage issues
very efficiently and cost effectively
• Focus of this session is MNO Wi-Fi
Until Recently calling
Focus: MNO Wi-Fi
offered by OTT
Calling
(Skype) providers
Voice over Wi-Fi Models and Value Creation

Save Money Make Money

• Leverage 100s of MHz of free • Become more relevant to

spectrum to enable all services
to be delivered over Wi-Fi
• Address in-door coverage and
capacity without additional
licensed radio build out
subscribers by offering Wi-Fi
calling on non-SIM devices
• Increase customer
engagement/analytics even
when they are “off” the cellular
network
VoWiFi Elevator Pitch

• Wi-Fi Carries over 80% of • Availability of native ePDG

Mobile Data client
 Growingfaster than  Seamless support of conversional
smartphone cellular data services
• 802.11ac to address growth • Identity Ecosystem
demands  Fornon-UICC and companion
devices
• Capability to address
coverage/capacity issues • 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

9
VoWiFi VoLTE VoIP 53%
8
7
Minutes of 6 41%
Use 5
(Trillions) 4
per Year 3
2
1 71% 6%
29%
0
2014 2015 2016 2017 2018 2019
Source: ACG, Cisco VNI Global Mobile Data Traffic Forecast, 2014–2019
VoWiFi Market Trends
VoWiFi – Apple iOS 8 Wi-Fi Calling
Standard based:
Same Phone dialer
Voice/Text over Wi-Fi ePDG/IPSec 3GPP
for 3G/4G/Wi-Fi voice
23.402

VoWiFi traffic goes to

Voice Handover
Mobile Core; Others Use VoLTE IMS
between Wi-Fi/VoLTE
goes local
 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
 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
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)
 VoWiFi Solution Architecture Internet

• VoWifi Architecture requires: TAS

 ePDG Cisco product
PGW
PGW PCRF
 3GPP AAA HSS/HLR IMS Core
 PGW with s2b support
Cisco partner product
 PCRF
 IMS Core infrastructure AAA
 TAS Non Cisco S5/S8 Gi

 VoWiFi capable UEs SWm S2b

PMIPv6
 HSS GTPv2
MME/SG
SGSN MSC
W
• VoWiFi capable UE pre-loaded with operator profile
• UE discovers the ePDG using DNS lookup for ePDG FQDN ePDG
ePDG Wi-Fi 3GPP access
– Statically or dynamically configured in Operator File access

SWn RNC
• UE establishes IPSec tunnel to ePDG
• ePDG sets up a PDN session to PGW on behalf of UE
Untrusted network
(e.g. home/ent)
• PGW allocates IP address and manages P-CSCF discovery
– provides P-CSCF details to UE
• UE SIP registers with SBC/P-CSCF
SWu

• UE makes/receives call via IMS/TAS

eNodeB NodeB
• P-CSCF discovery over IKE or operator profile IMS/VoLTE
IPSec
VoWiFi over Untrusted WLAN to EPC Integration using ePDG
PSTN

AuC

HSS

MGCF MGW

Voice Core
CSCF TAS
3GPP
AAA Server
AP
IPSec Tunnel A-SBC I-SBC
WLC between UE & ePDG

ASR5K ASR5K
AP

L3 Infra L3 GiLAN
vGiLAN
ePDG PGW
S2b

AP

WLC

PCRF Internet

AP
 ePDG as defined in Standards
• ePDG is part of the 3GPP LTE
SAE defined in 3GPP TS 23.402 HSS
SWx

S6a PCRF
Gxc Rx
• Responsible for interworking Gx
Operator's IP
SGi
between the EPC and un-trusted 3GPP Serving
Gateway
PDN
Services
(e.g. IMS, PSS
Access Gateway etc.)
non-3GPP networks S5
S6b
S2b
Gxb
SWm
S2a ePDG 3GPP AAA
Server
SWn
• ePDG terminates IPSec tunnels HPLMN
Gxa
established/initiated by UEs via Non-3GPP
Networks
Trusted
SWu Untrusted
un-trusted Wi-Fi network for Non-3GPP Non-3GPP IP
Access
Non-3GPP IP
Access SWa
STa
secure access to the EPC. UE

Wi-Fi Un-trusted
 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_REQ
4. DER

6. IKEv2 AUTH_RESP 5. DEA

7. IKEv2 AUTH_REQ
8. DER

9. DEA
10. IKEv2 AUTH_RESP

11. IKEv2 AUTH_REQ

12. Create Session Request

13. Create Session Response

14. IKEv2 AUTH_RESP
VoWiFi Call setup
P-
UE ePDG PGW PCRF OFCS OCS
CSCF
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 H(e)NBGW
(StarOS) ePDG SAMOG
Supporting PGW SAEGW
Multiple Functions
Performance and
Scalability
Multiple
Hardware Flexibility and
Cisco ASR 5xxx Elasticity Cisco Virtualized
Platforms Packet Core (vPC)

• Product line is optimized for maximum performance & capital efficiency

Cisco ASR
5k Series • Software functions work across multimedia core platforms
Multimedia • N:1 internal redundancy (ASR5k) and 1:1 geographical redundancy (All Platforms)
Core Platforms
Cisco Virtual ePDG
VMware Ecosystem OpenStack Ecosystem

ePDG ePDG • Base on COTS x86 server

Cisco StarOS Cisco StarOS
hardware
Linux Kernel Linux Kernel
• Highly scalable: Capacity
KVM (Hypervisor) can be added by adding

vSphere / vCloud
VMware ESXi
CPU/memory resource

OpenStack
(OS + Hypervisor)
Ubuntu / RedHat (OS)
• Elasticity: Capacity-on-
demand
Hardware: x86 server Hardware: x86 server
• Field Proven: Same
software as physical ePDG
Networking 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
Voice over trusted Wi-Fi Access
VoWiFi over Trusted WLAN to EPC Integration using SaMOG GW
PSTN
AP + CM
MAG AuC

CPNR
Access Infra HSS
Cisco Prime
AP + DHCP
CM Prime Perf.
EoGRE MGCF MGW
Infra. Manager
DNS

Voice Core
SWx

CSCF TAS
STa 3GPP PCRF
AAA Server

S6b
A-SBC I-SBC
L2-GRE

L3-GRE
AP ASR5K ASR5K

WLC Core Infra TWAP L3 SGi vGiLAN

S2a PGW
L3-GRE TWAG
AP
CAPWAP

Internet
SaMOG GW (LTE, UMTS)
internet
HSS Gi
SWx
AAA GGSN P-GW
Gi
Gn
Web Portal STa GTPv1 S2a
(Diameter) GTPv2
Packet Core Radius
EAP-SIM
WiFi access Non EAP-SIM Local Breakout
TWAP TWAG
DHCP

PMIPv6 / EoGRE EoGRE

WLC WLC

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  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
IKEv2 Outside Pool: Host:
allocated 10.10.1.1
173.38.1.0/24 SWu
2610:8dba:82 173.38.2.1
e1:ffff::/64
ePDG
SIPTO
NSWO + Wi- Enabled Including
Fi Calling Default APN SWu NAT
TWAG
Client P-GW traversal
SWu functionality
Default APN
DHCP SIPTO S2a Configuration IP
802.11
allocated Match IP UE Pool:
173.38.2.1 173.38.0.0/24
173.38.0.1
NSWO

DNS Resolves
IPv4 ePDG to
Internet 173.38.2.1
QoS Deployment Considerations
 LTE vs Wi-Fi Bearer Comparison
UE Radio eNodeB
S1u SGW
S5 PGW
Default Bearer (SIP) Default Bearer (SIP) Default Bearer (SIP) IMS IPv6
QCI 5 QCI 5 QCI 5
Voice / QCI 1 Voice / QCI 1 Voice / QCI 1
Video / QCI 2 Video / QCI 2 Video / QCI 2 Video option

802.11 SWn S2b

UE (IPSec) AP (IPSec) ePDG PGW
Default Bearer (SIP) IMS IPv6
SIP, Voice, Video
QCI 5
WiFi QoS Voice / QCI 1
WMM (802.11e) Video / QCI 2
DSCP based
VoWiFi over untrusted access - E2E QoS
Uplink

802.11e WMM DSCP LTE QCI DSCP

802.11ac

Downlink

802.11e WMM
LTE QCI DSCP
802.11ac

QCI to IP
DSCP mapping
 QoS and Dedicated Bearer Creation
UE AP ePDG PGW PCRF IMS
AP
IMS core gets SIP invite
1. Rx AAR / AAA
and it requests QoS from
EPC
2. Gx RAR / RAA

PCRF installs PCC rules

3. Create Bearer Response on PGW
11. Create Bearer Request

ePDG marks traffic on SWu Voice traffic prioritized in

to allow AP to enable WMM the SP network

Fast re-auth improves

HO performance
IMS core operates the
same for VoLTE on LTE
and on WiFi
Voice Quality and Requirement
3GPP
AAA
IMS
SWm
Wi-Fi Internet VoIP – Control plane
NAT EPDG PGW
IPSec VoIP – User plane

• Bandwidth Requirement
 Typically VoWiFi uses AMR-WB: 56.65 kbps per call

• Jitters and Latency

 Latency: Propagation, transport, packetization, jitter buffer Ideal Tolerable
 Jitter: The variable arrival interval between packets One way <75ms 75ms -100ms
Latency/Delay
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 Downloaded as an

with Phone OS (iOS, app
Samsung & Nokia)

Dial Pad Same dial pad for Different dial pad

2/3/4G and VoWiFi between cellular and
VoWiFi

Wifi calling
Wi- VoWiFi/VoLTE Not supported. Voice
Fi/Cellular supported call will drop when Wi-
mobility Fi is lost

OTT App
Native 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
 EncryptionAlgorithm – Array of protocols e.g. 3DES
• Guard timer – 2 mins  IntegrityAlgorithm - Array of protocols e.g. SHA1-96
 Used to avoid ping-pong between RAT Types
 Lifetime – 8640s
• IKE
 DPDEnabled – True • Remote Address
 DPDInterval – 600s
 epdg.<domain>.com
 DPDMaxRetries & Retry Interval – 4&10

• IMS Config • 3GPP Config

 EnableWiFiCallingWithoutEntitlement – True  APN – IMS
 P-CSCF - 192.168.1.1
 SupportsVolteCapability – True
 defaultAuthAlgorithm - AKAv1-MD5
Non SIM Handset access
 Calling from PC, tablets, iPads
Service across the  Companion Device

internet – across 
Compete with Skype/Facetime
One Number
devices  Increase Service Stickiness

How to
Authenticate these
Devices ???
Re-use existing
Proven, reliable, infrastructure and
standard interfaces 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-TLS based EAP-TTLS based
authentication authentication

• EAP method encapsulating TLS

• Single phase
session
• EAP method encapsulating TLS
• Two phases
session
 Handshake phase (server authentication &
• Use certificates between UE & AAA key generation)
server for mutual authentication  Data Phase (client authentication)

• Reference -RFC 5216 • 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 S5
S6a S6b
MME HSS 3GPP
AAA S2b
DNS SWm 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 ePDG PGW

Handover of Active
call between Wi-Fi HLR, SMSC
and 2G/3G with Call IN/SCP etc …
Continuity function
SCC AS NodeB
RNC MSC
2G/3G Core and service
WiFi to 2G/3G handover method

WiFi AP P/S-CSCF SCC AS MCGF

MGW

NodeB
RNC MSC/VLR

VoWiFi Control Signaling path

2G/3G Control Signaling path Handover Control Signaling path
VoWiFi Call Bearer path
2G/3G Call Bearer path
APN and IP Address Logic in UE
• Policy selects APN Connection
seamless, non Policy
seamless or LTE LTE MME

iRAT Logic
APN1 Modem
access for each APN

Virtual IP1
IP1

• Virtual IP APN2 IP2 Non 3GPP

interfaces hides Modem
interface changes SGW

Virtual IP2
IPSec
on inter RAT events IP1
IPSec
• Connection manager IP2
IP-W
PGW
connects to Wi-Fi AP Connection
Manager

• Connection threshold WiFi

ePDG
Modem
management based on RSSI,
beacons, SNR, 802.11k and
802.11v, rate shifting
Internet
International Roaming with
VoWiFi
International Roaming
Existing
Home PLMN
Home MSISDN

Foreign
MSC/I
PLMN MS
OTT MSISDN

OTT Foreign
MSC/I
OTT
Client IP/Wifi MS
Home PLMN
VoWifi

Home PLMN
Home MSISDN

Foreign
ePDG/ MSC/
Wifi PGW IMS
Same home mobile number for MO/MT
Capture revenue long lost to OTT
No need to pay expensive roaming charge
No need to pay roaming partners
Same phone dialer for mobile and wifi call
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
• Deployed in EE UK and Verizon USA
Proven solution and Leader in VoWiFi • ePDG contracts awarded by major tier-1 mobile SP in
US and Europe

Multi-service software • ePDG, SAMOG GW, PGW, HNBGW in a single box

Multi-platform: virtual, high scale • ePDG available in

• Dedicated HW: ASR5500, ASR5000
gateway • Virtual NFV x86 platform: vPC

Hybrid trusted/untrusted solution • Co-existence of ePDG and SAMOG with optimized

routing

• Cisco ePDG offers access network visibility: Roaming

Enhanced VoWiFi Core access whitelist/blacklist and other features
• Security: DOS attack protection/mitigation mechanisms

• Cisco Universal Wi-Fi on Access side

End to End VoWiFi Solution • StarOs based Packet Core
• Cisco Policy Suite , 3GPP AAA
Thank You!