Professional Documents
Culture Documents
I
n the time since Apples revelation
that iOS 8 would support a form of Wi-Fi calling, the industry has seen a
barrage of announcements, even TV commercials, around Wi-Fi calling. Come
to find out that many of them are actually existing products and technologies
simply re-spun. A deeper dive into Wi-Fi callings history and characteristics
reveals what is truly needed to properly support this exciting new Apple
capability, as well as other Vo-Fi services.
LTE (VoLTE) call works. Its also being developed to support the transparent
handoff of a call as the user moves between Wi-Fi and LTE coverage areas,
something OTT approaches simply cant do. Its more of an evolution of
about older UMA (unlicensed mobile access) based services, which were
some of the first to support cellular voice services over Wi-Fi. Other
implementations would include services from MVNOs such as republic
wireless and Scratch Wireless.
While these are all examples of Wi-Fi Calling, they have very different
characteristics, raising a number of important questions:
Does the service support call handoff to and/or from a cellular service?
If so, does handoff work with Circuit-Switched networks, VoLTE/IMS
networks, or both?
While there are obviously a lot of possibilities to enable Wi-Fi calling, its also
encouraging that there are so many ways to support voice over Wi-Fi
underscoring Wi-Fis flexibility to support a myriad of IP-based services.
Whats REALLY changing with Apples iOS integration and mobile operators
lining up to support it is that Wi-Fi Calling will no longer be just a so-called
OTT service, or only be offered by upstart MVNOs like republic wireless or
Scratch Wireless. Wi-Fi calling is going mainstream.
The question now becomes: How do Enterprises, Operators, and Venues
optimize their Wi-Fi networks to support this service?
Voice as an IP Service
Voice is a low bitrate, but very finicky, data service because real-time,
bidirectional voice demands a narrow set of operating parameters from the
network in to ensure a high quality calling experience.
As such, the requirements for latency, jitter, and packet loss are much tighter
for voice than for standard business or Internet applications.