Volte Architecture: Abdulsalam Maher Cellqual Company
Volte Architecture: Abdulsalam Maher Cellqual Company
Volte Architecture: Abdulsalam Maher Cellqual Company
Architecture
Abdulsalam Maher
Cellqual company
VoLTE Architecture
VOLTE: VOICE OVER LTE
VoIP call support over an LTE network requires IMS support.
When a UE with an active VoIP call leaves LTE coverage to an area
with only 1xRTT coverage, the call can be seamlessly handed over
from the LTE-IMS to the 1xRTT CS domain. Call continuity from
IMS to the CS domain is maintained with the help of Single Radio
Voice Call Continuity (SRVCC) anchoring.
VoLTE and IMS :
The EUTRAN consists of a single node, the eNodeB that interfaces with
the UE.
The eNodeB hosts the Physical (PHY), Medium Access Control (MAC),
Radio Link Control (RLC), and Packet Data Convergence Protocol
(PDCP) layers that include the functionality of user-plane header-
compression and encryption.
It also offers Radio Resource Control (RRC) functionality corresponding to
the control plane.
It performs many functions including radio resource management,
admission control, scheduling, enforcement of negotiated UL QoS, cell
information broadcast, ciphering/deciphering of user and control plane
data, and compression/decompression of DL/UL user plane packet headers.
MME (Mobility Management Entity)
The Mobility Management Entity (MME) is the key control-node for the LTE
access network.
It is responsible for idle mode UE tracking and paging procedures including
retransmissions.
It is involved in the bearer activation/deactivation process and is also
responsible for choosing the SGW for the UE at the initial attach and at the
time of intra-LTE handover involving Core Network node relocation.
It is responsible for authenticating the user (in conjunction with the HSS).
The NAS (Non-Access Stratum) signaling terminates at the MME which is
also responsible for the generation and allocation of temporary identities to
the UEs.
MME (Mobility Management Entity)
The SGW routes and forwards user data packets, while also
acting as the mobility anchor for the user plane during inter-
eNodeB handovers and as the anchor for mobility between LTE
and other 3GPP technologies (terminating the S4 interface and
relaying the traffic between 2G/3G systems and PGW).
For idle state UEs, the SGW terminates the DL data path and
triggers paging when the DL data arrives for the UE.
It manages and stores UE contexts and performs replication of
the user traffic in case of lawful interception.
The SGW and PGW functions could be realized as a single
network element.
PGW (Packet Data Network Gateway)
The BGCF is responsible for determining the next hop for routing of SIP
messages.
This determination is based on information received within the SIP/SDP and
routing configuration data (which can be internal configuration data or
ENUM/DNS lookup).
For CS Domain terminations, the BGCF determines the network in which
CS domain breakout is to occur and selects the appropriate MGCF.
For terminations in peer IMS networks, the BGCF selects the appropriate
IBCF to handle the interconnect to the peer IMS domain.
The BGCF may also provide directives to the MGCF/IBCF on which
Interconnect or next network to select.
Such directives may be given by the inclusion of a routeing header pointing
to the next network ingress node.
Difference between CSFB and VoLTE
UE call procedure