You are on page 1of 26

Network Evolution Solution

The VoLTE architecture for a single PMN deployment


VoLTE Network Architecture
Registration (Convergent HLR/HSS)

Service Model
After a VoLTE UE is attached to an EPC network, the UE initiates a registration to an
IMS network.

IMS access point name (APN) and data APN are independent from each other. Data
APN is the default APN.

A convergent home location register (HLR)/home subscriber server (HSS) is


deployed. The convergent HLR/HSS integrates the functions of the HLR, system
architecture evolution-home subscriber server (SAE-HSS), and IP multimedia
subsystem-home subscriber server (IMS-HSS).

The SE2900 functions as both the session border controller (SBC) and proxy-call
session control function (P-CSCF).

The VoLTE registration process is divided into the following flows:


Attaching to an EPC network (Figure 1): A UE initiates an attach request. The EPC
network authenticates the UE. After the authentication is passed, the EPC network
obtains the UE's subscription data from the convergent HLR/HSS. Based on the default
APN and PDN context in the subscription data, the EPC network establishes a default
bearer. After the default bearer is established, the UE is attached to the EPC network.
Registering with an IMS network (Figure 2): The registration consists of basic registration
and third-party registration. During the basic registration, the UE and IMS network
authenticate each other. After the authentication is passed, the serving-call session control
function (S-CSCF) downloads the UE's subscription data from the convergent HLR/HSS.
During the third-party registration, the S-CSCF queries the UE's iFC and contacts the
advanced telephony server (ATS), and the ATS downloads the UE's data from the convergent
HLR/HSS.
VoLTE Registration
1) Key IEs carried in the Attach Request message
2) Network and UE authentication

3) After authentication, MME sends ULR to HSS


4) HLR/HSS sends a ULA message to the MME to insert subscription data to the MME. The
subscription data includes the default APN and one or more PDN contexts.
4) HLR/HSS sends a ULA message to the MME to insert subscription data to the MME. The
subscription data includes the default APN and one or more PDN contexts.
5) The MME selects a serving/PDN gateway (S/P-GW) based on the APN configuration and
network topology. The MME sends a Create Session Request message to the S/P-GW to
establish a default bearer for the data APN.

Create Session Request message


6) The S/P-GW sends a Create Session Response message to the MME. In the message, the
QCI value is 9, indicating that the default bearer for the data APN has been established and
an UE IP address is assigned
7) The MME sends an Attach Accept message to the UE.

8) The UE sends a PDN Connectivity Request message to the MME to establish a default
bearer for the IMS APN. The message carries the IMS APN name.
9) The MME sends a Create Session Request message to the S/P-GW to establish a default
bearer for the IMS APN.
10) When receiving the Create Session Request message, the P-GW initiates an IP-CAN
session establishment procedure. Specifically, the P-GW sends a CCR message to the PCRF
to obtain the UE's PCC rules.

11)The PCRF sends a CCA message carrying the PCC rules to the P-GW.
12) The S/P-GW sends a Create Session Response message to the MME. The QCI value is 5,
indicating that the default bearer for the IMS APN has been established. The C0DD430B in
the PCO indicates the P-CSCF address. The UE is attached to the EPC network.
Basic VoLTE Voice call
In the SRVCC solution, the
handover duration often
exceeds 300 ms because a
new bearer must be
established on the IMS
network. This results in long
call delay, affecting user
experience. eSRVCC is
introduced to shorten the
handover duration to smaller
than 300 ms, one that
subscribers can hardly
perceive. Huawei VoLTE
solution can realize both
SRVCC and eSRVCC. Figure 1
shows how SRVCC/eSRVCC is
implemented.
Handover message flow of an active call from an E-UTRAN to a UTRAN

You might also like