PROJECT REPORT

VOICE COMMUNICATION
FALL 13

Group members:
Deepanjali Jadhav
Debsuta Roy

Exploring VoLTE related changes to transmission of voice traffic

This project will aim to research into the modal world of VoLTE and its components and how voice
traffic will be treated with the implementation of VoLTE. The main emphasis of the project will be
understanding the exact functioning of VoLTE and studying whether or not there are differences
between the mechanisms in which SIP works in a VoIP based scenario and in a VoLTE scenario.

INTRODUCTION
The transition from VoIP to VoLTE has been a phenomenon change to the world of VoIP and voice
transmission with previously incompetent networks.
VoLTE has brought over a revolutionary change to the way voice is being transmitted and brings
about better voice quality and delivery, reduced power consumption, better resource
management over VOIP. This project will dwell into the exact changes or in other words
enhancements in SIP that contribute to the better VoLTE.
Though, VoIP and VoLTE are essentially supposed to be looked as just a predecessor and successor,
they are often termed as different. VoIP is an integral parts of both voice architecture. VoIP is used
by VoLTE as well but the enhanced version of transmitting voice over IP but in an 4G LTE network
and its requirement to correlate with an IMS, become vital extremes that often puts these two
technologies so apart. SIP is hence, used in both technologies and VoIP is a major part of VoLTE.
But the purpose of this project is to research into great detail and conclude whether or not there
are any differences between how SIP operates in both scenarios.
SIP in VoIP
SIP in this case is a signaling protocol that is used for session establishment between two
users/peers and or modifies a session, like change the allocated channel or change the kind of
service being used. Skype for example is software that uses SIP signaling. For secure purposes
sometimes SIPS is used which stands for Session Initiation Protocol Secure. SIP uses similar
signaling like in HTTP and follows a similar transaction/respond model.
Each of these is performed in a client request - response model. In this, the client first sends a
request to which the server responds with the services of the particular request by the client. This
service could be something like changing the status from voice to video. SIP works in context with
many other protocols that are used for communication, but the job of SIP restricted to only
signaling. If secure transmission is required that a special scheme called 'sips:' is used which was
defined earlier. The goal when SIP was developed initially was for it to be able to contain a superset

of call manipulating and messaging functions, but it evolved to be a more efficient signaling
protocol instead. The ultimate goal of SIP was in developing a PSTN based fundamental voice and
SMS system. These aspects then became the goal of the now and recent VoLTE.
Below is a scheme diagram showing the functioning of SIP in VoIP:

Figure

1:

SIP

Functioning,

http://www.windowsnetworking.com/articles-

tutorials/netgeneral/Session-Initiation-Protocol-Functions.html
SIP in VoLTE
VoIP is only a small subset function of the larger solution VoLTE. Next is a diagram of 4G-LTE
implementation and VoLTE subsections and the following is an explanation on how SIP functions
differently in VoLTE.
There have been certain misconceptions between VoIP and VoLTE that these need to be first
addressed before going ahead with addressing the premise of this project itself. VoLTE
fundamentally uses VoIP for signaling purposes with voice traffic. So, essentially VoIP is a part of
VoLTE as explained in the first section of this project. Only difference becomes that in VoLTE the
signaling process is a little more in detail when it comes to initial setup of a user on a network. In
just VoIP, the server just ensures signaling during and prior the session and manages the

connection, while in VoLTE the process a little lengthier with the client reporting two to three
different servers getting authenticated with multiple algorithms before let on the network.

Figure 2:
4G-LTE
implementation,http://static.rcrlocal.com/article/files/2012/09/interphaseLTEnetwork.jpg

Figure 3:
VoLTE Implementation architecture,
http://regmedia.co.uk/2012/09/27/voLTE_2.jpg
Carrying the argument forward we can say that SIP in VoIP and in VOLTE cannot be looked at
as separate entities and can be considered same. But for the purpose of the project we look at the
functioning and architecture of VoLTE and derive at certain extra capabilities that will be added
to the transmission of voice while compared to VoIP only.
Behaviour of Voice and Data traffic in
VoLTE
The mobile communication standard LTE is built for optimization in transferring data and
designed

VoLTE is a growing investment ground for those who believe in its capabilities and is also
balanced on the grounds that VoLTE (IMS) guarantees substantially more adaptable
administrations, yet at the expense of needing to overhaul the whole voice call foundation. VoLTE
can additionally require Single Radio Voice Call Continuity (SRVCC) with a specific end goal to
have the ability to perform to a lower standard when the higher LTE standard is not functional or
is at a lower quality rate. In either case 3g or 3.5G will be automatically handling the network
and will fully function as an underlying layer/standard on any LTE deployment till the year 2018.

REFERENCES
1. http://www.ericsson.com/res/thecompany/docs/corpinfo/volte_backgrounder.pdf
2. http://www.mavenir.com/assets/files/Resources/MavenirCSFB.pdf
3. http://www.awardsolutions.com/forms/trainingSolutions.aspx?viewCourse=212
4. http://www.ibasis.com/downloads/pdfs/VoLTE_Whitepaper.pdf
5. http://www.microwavejournal.com/ext/resources/whitepapers/July2012/IMS_ArchitectureJuly2012.pdf

6. http://www.etsi.org/WebSite/document/Technologies/RCS_VoLTE_WhitePaper_11_14_2012.p
df