VoLTE Solution Basic Signaling Procedure N-1

VoLTE Solution Basic Signaling Procedure N-2

VoLTE Solution Basic Signaling Procedure N-3
VoLTE Solution Basic Signaling Procedure N-4
VoLTE Solution Basic Signaling Procedure N-5
VoLTE Solution Basic Signaling Procedure N-6
VoLTE Solution Basic Signaling Procedure N-7
VoLTE Solution Basic Signaling Procedure N-8
VoLTE Solution Basic Signaling Procedure N-9
VoLTE Solution Basic Signaling Procedure N-10
VoLTE Solution Basic Signaling Procedure N-11
VoLTE Solution Basic Signaling Procedure N-12
VoLTE Solution Basic Signaling Procedure N-13
 VoLTE Solution Basic Signaling Procedure N-14

 1: A UE sends an Attach Request message to the MME. The message carries the
following VoLTE-related information elements (IEs):

 Attach Type: specifies the attach flow type: EPS attach, combined EPS/IMSI
attach, or emergency attach.

 MS Network Capability: carries the SRVCC to GERAN/UTRAN capability

IE, indicating that the UE supports the SRVCC capability.

 Voice domain preference and UE's usage setting: specifies whether the UE
supports circuit switched fallback (CSFB) and Short Message Service (SMS)
over signaling gateways (SGs).

 Protocol Configuration Options (PCO): contains the 0002H (IM CN

Subsystem Signaling Flag) parameter, indicating a request to establish a
default bearer for IMS signaling, and the 000CH (P-CSCF IPv4 Address
Request) parameter, indicating a request for the P-CSCF address.

 PDN Type: specifies the IP address type of the UE: IPv4, IPv6, or IPv4v6.

 2: The MME checks whether authentication sets are stored locally. If no

authentication set is stored locally, the MME sends an Authentication Information
Request (AIR) message containing the subscriber's IMSI to the convergent
HLR/HSS, requesting authentication data.
VoLTE Solution Basic Signaling Procedure N-16
VoLTE Solution Basic Signaling Procedure N-17
 VoLTE Solution Basic Signaling Procedure N-18

 The subscription data includes the default access point name (APN), one or more
PDN contexts, Session Transfer Number for SRVCC (STN-SR) and correlation
mobile station international ISDN number (C-MSISDN).
VoLTE Solution Basic Signaling Procedure N-19
 VoLTE Solution Basic Signaling Procedure N-20

 policy and charging rules function (PCRF).

 6: The MME selects the S/P-GW based on the APN configuration and network topology. The MME
then sends a Create Session Request message to the S/P-GW, requesting to establish a default
bearer.

 7: When the P-GW receives the Create Session Request message, it performs the following
operations: The P-GW checks whether the Create Session Request message carries the PCO and
PDN Type IEs and whether the QCI IE is set to 5.

 If the PCO IE contains 000CH (P-CSCF IPv4 Address Request), the P-GW queries the
local configuration for the P-CSCF address based on the APN, international mobile
subscriber identity (IMSI), or mobile station international ISDN number (MSISDN). If the
query is successful, the P-GW obtains the P-CSCF address list allocated to the UE. The P-
GW adds the list to the 000CH (P-CSCF IPv4 Address Request) of the PCO IE in the
Create Session Response message and sends the message to the UE. If the PCO IE does
not contain 000CH (P-CSCF IPv4 Address Request), the P-GW sends a failure response
to the UE.

 NOTE: P-CSCF groups are configured by running p-cscf-group and P-CSCF address
allocation mode is configured by running p-cscf-group-binding in the PCC view of the
UGW9811.

 If the PCO IE contains 0002H (IM CN Subsystem Signaling Flag), the P-GW queries the
local configuration based on the APN, IMSI, or MSISDN
VoLTE Solution Basic Signaling Procedure N-22
VoLTE Solution Basic Signaling Procedure N-23
VoLTE Solution Basic Signaling Procedure N-24
VoLTE Solution Basic Signaling Procedure N-25
VoLTE Solution Basic Signaling Procedure N-26
VoLTE Solution Basic Signaling Procedure N-27
VoLTE Solution Basic Signaling Procedure N-28

Confidential Information of Huawei. No Spreading Without Permission

VoLTE Solution Basic Signaling Procedure N-29
VoLTE Solution Basic Signaling Procedure N-30
VoLTE Solution Basic Signaling Procedure N-31
VoLTE Solution Basic Signaling Procedure N-32
 VoLTE Solution Basic Signaling Procedure N-33

After the P-CSCF registration is completed successfully, the following information is stored:
1. S-CSCF IP address. After being registered successfully, the user initiates a call to the P-
CSCF and the P-CSCF knows to which S-CSCF to route the call (instead of selecting any
S-CSCF as during registration). The S-CSCF sends its IP address in the Service-Route
header field in a registration 200 message to the P-CSCF.
2. UE information, including the IMPI and IMPU of the UE, access network information, and
UE IP address. When the user serves as the called party, the P-CSCF knows how to route
the call to the UE.
After the S-CSCF registration is completed successfully, the following information is stored:
1. P-CSCF IP address. When the user is the called party, the S-CSCF knows the P-CSCF
that serves the called party. The P-CSCF sends its IP address in the Path header field in a
calling message to the S-CSCF.
2. UE information, including authentication information (authentication information does not
need to be downloaded during user re-registration) and service triggering data (service
triggering during a call)
After the HSS registration is completed successfully, the following information is stored:
1. S-CSCF IP address. During user re-registration, the HSS directly returns a UAA message
carrying the S-CSCF IP address and the I-CSCF does not need to select any S-CSCF.
VoLTE Solution Basic Signaling Procedure N-34
VoLTE Solution Basic Signaling Procedure P-35

华为技术有限公司 版权所有 未经许可不得扩散

VoLTE Solution Basic Signaling Procedure P-36
VoLTE Solution Basic Signaling Procedure N-37
VoLTE Solution Basic Signaling Procedure N-38
VoLTE Solution Basic Signaling Procedure P-39
VoLTE Solution Basic Signaling Procedure N-40
 VoLTE Solution Basic Signaling Procedure N-41

 A UE sends its single radio voice call continuity (SRVCC) capability to the SAE-HSS
when attaching to the EPC network. During third-party registration with the IMS
network, the SCC AS queries the SAE-HSS for the UE's SRVCC capability.

 To configure whether the SCC AS checks UE's SRVCC capability, run MOD
TADSCFG in the MML Command - ATS9900 window of the OMU client. The SCC
AS does not check UE's SRVCC capability when Whether to determine that UE
supports SRVCC is set to NO(NO). You can set this parameter to NO(NO) only
when LTE coverage is available on the entire live network, where SRVCC/eSRVCC
handovers are not required.

 When a subscriber registers only with the ICS domain, the SCC AS downloads T-
ADS information based on the value of Subscribers only in ICS domain download
TADS information (configured using MOD TADSCFG in the MML Command -
ATS9900 window).
VoLTE Solution Basic Signaling Procedure N-42
VoLTE Solution Basic Signaling Procedure N-43
VoLTE Solution Basic Signaling Procedure N-44
VoLTE Solution Basic Signaling Procedure P-45
VoLTE Solution Basic Signaling Procedure P-46
VoLTE Solution Basic Signaling Procedure N-47
VoLTE Solution Basic Signaling Procedure N-48
 VoLTE Solution Basic Signaling Procedure N-49

 mobile originating (MO)

VoLTE Solution Basic Signaling Procedure N-50
VoLTE Solution Basic Signaling Procedure P-51
 VoLTE Solution Basic Signaling Procedure N-52

 The convergent HLR/HSS adds a prefix to UE_B's MSISDN to form an IMRN

based on the local data configuration
VoLTE Solution Basic Signaling Procedure N-53
 VoLTE Solution Basic Signaling Procedure N-54

 service centralization and continuity application server (SCC AS)

 CS routing number (CSRN) mode

 The service centralization and continuity application server (SCC AS) sends a User
Data Request (UDR) message to the convergent HLR/HSS, requesting the CSRN,
that is, the mobile station roaming number (MSRN). The MSRN instructs the S-
CSCF to route a call to the CS network.

 Carrier identification code (CIC) mode

 The SCC AS adds a CIC prefix to the calling number in the P-Asserted-Identity
header field and a CIC parameter to the called number in the Request-URI. The CIC
prefix is used to suppress repeated MT anchoring, and the CIC parameter is used to
instruct the S-CSCF to route the call to a CS network. After the call is routed to the
media gateway control function (MGCF), the MGCF configures a terminating CAMEL
subscription information (T-CSI) suppression information element (IE) based on the
CIC prefix and queries the convergent HLR/HSS for the MSRN.
 VoLTE Solution Basic Signaling Procedure N-55

 Send Routing Information (SRI)

 mobile station roaming number (MSRN).

VoLTE Solution Basic Signaling Procedure N-56
 VoLTE Solution Basic Signaling Procedure P-57

 To configure the prefix to be added to the MSISDN, run ADD ANCHORMGCF on the
HSS9860 Management page of the PGW Web LMT.
VoLTE Solution Basic Signaling Procedure N-58
VoLTE Solution Basic Signaling Procedure N-59
VoLTE Solution Basic Signaling Procedure N-60
VoLTE Solution Basic Signaling Procedure N-61
VoLTE Solution Basic Signaling Procedure N-62
VoLTE Solution Basic Signaling Procedure N-63
VoLTE Solution Basic Signaling Procedure N-64
VoLTE Solution Basic Signaling Procedure N-65
VoLTE Solution Basic Signaling Procedure N-66
VoLTE Solution Basic Signaling Procedure N-67
VoLTE Solution Basic Signaling Procedure N-68
VoLTE Solution Basic Signaling Procedure N-69
VoLTE Solution Basic Signaling Procedure P-70
VoLTE Solution Basic Signaling Procedure N-71
VoLTE Solution Basic Signaling Procedure N-72
 VoLTE Solution Basic Signaling Procedure N-73

 The format of the IMRN is determined by the value of P3403: When P3403 is set to
0, the IMRN is in "CC-MT anchoring prefix-NDC-SN" format. For example, if the
called number is 8613987650001 and the anchoring prefix is 123, the IMRN
allocated by the anchor AS is 8612313987650001.

 When P3403 is set to 1, the IMRN is in "MT anchoring prefix-NDC-SN" format. For
example, if the called number is 13987650001 and the anchoring prefix is 123, the
IMRN allocated by the anchor AS is 12313987650001.
VoLTE Solution Basic Signaling Procedure N-74
VoLTE Solution Basic Signaling Procedure P-75
VoLTE Solution Basic Signaling Procedure N-76
VoLTE Solution Basic Signaling Procedure N-77
VoLTE Solution Basic Signaling Procedure N-78
VoLTE Solution Basic Signaling Procedure N-79
VoLTE Solution Basic Signaling Procedure N-80
VoLTE Solution Basic Signaling Procedure N-81
VoLTE Solution Basic Signaling Procedure N-82
VoLTE Solution Basic Signaling Procedure N-83
VoLTE Solution Basic Signaling Procedure P-84
VoLTE Solution Basic Signaling Procedure N-85
VoLTE Solution Basic Signaling Procedure N-86
VoLTE Solution Basic Signaling Procedure N-87
VoLTE Solution Basic Signaling Procedure N-88
 VoLTE Solution Basic Signaling Procedure N-89

 8: The I-CSCF detects that the INVITE message does not carry the orig and sends an LIR
message containing the IMRN to the IMS-HSS.The IMS-HSS returns a LIA message containing
the anchor AS address to the I-CSCF. Figure 5 is an example of the LIA message.

 NOTE: To configure the IMS-HSS to query the anchor AS address based on the IMRN, run ADD
HPSI with PUSI set to tel:+routing prefix!.*!, and run SET HAS to configure the anchor AS
address in SIP format on the HSS9860 Management page of the SPG2800 web portal.

 10: The I-CSCF sends the INVITE message to the anchor AS. The anchor AS reverts the call
information and called number based on the IMRN and sends the INVITE message to the I-CSCF.

 11: The I-CSCF receives the INVITE message and sends an LIR message to the IMS-HSS to
select an appropriate S-CSCF for UE_B.The IMS-HSS returns an LIA message containing the S-
CSCF address to the I-CSCF.The I-CSCF sends the INVITE message to the S-CSCF.

 12: The S-CSCF contacts other ASs based on the subscribed iFC template stored locally. After the
other ASs trigger services, the S-CSCF routes the call to the SCC AS for T-ADS.

 If there is no locally stored iFC template, the S-CSCF sends an SAR message to the IMS-HSS to
request the iFC template. The IMS-HSS then returns an SAA message carrying the iFC template
to the S-CSCF.
VoLTE Solution Basic Signaling Procedure N-90
VoLTE Solution Basic Signaling Procedure N-91
 VoLTE Solution Basic Signaling Procedure N-92

 KeyPoints:

 Step1 - Caller UEA call Callee UE-B and Call route to Callee GMSC

 Step 2~10 – MT anchoring base on IMRN Segment

 Step 11 – T-ADS Domain Selection (B in CS)

 Step 12~15 Re-anchoring suppression by CSRN

 Step 16~19 MT Terminating flow to CS network and target callee UE

VoLTE Solution Basic Signaling Procedure N-93
 VoLTE Solution Basic Signaling Procedure N-94

 NOTE: To configure the SCC AS to route calls based on the MSRN, run MOD
CSRTCFG with CS route mode set to Use CSRN in the MML Command -
ATS9900 window of the OMU client.
VoLTE Solution Basic Signaling Procedure N-95
 VoLTE Solution Basic Signaling Procedure P-96

 Anchoring is special number routing flow

 Flow1 Caller UEA call Callee UE-B and MO signalling flow arrive at Callee GMSC

 Flow2 MT anchoring base on IMRN Prefix

 Flow3 T-ADS Domain Selection (B in CS)

 If Callee-B in CS, follow below flow

 Flow4 Re-anchoring suppression by CIC

 Flow5 MT Terminating flow to CS network and target callee UE

VoLTE Solution Basic Signaling Procedure N-97
VoLTE Solution Basic Signaling Procedure N-98
VoLTE Solution Basic Signaling Procedure N-99
VoLTE Solution Basic Signaling Procedure N-100
 VoLTE Solution Basic Signaling Procedure N-101

 CIC prefix to the called number: S-CSCF routes the call to the MGCF

 CIC prefix to the calling number：Anchor AS performs re-anchoring suppression

VoLTE Solution Basic Signaling Procedure N-102
VoLTE Solution Basic Signaling Procedure N-103
VoLTE Solution Basic Signaling Procedure N-104
VoLTE Solution Basic Signaling Procedure N-105
VoLTE Solution Basic Signaling Procedure N-106
VoLTE Solution Basic Signaling Procedure N-107
VoLTE Solution Basic Signaling Procedure N-108
VoLTE Solution Basic Signaling Procedure P-109
VoLTE Solution Basic Signaling Procedure N-110
VoLTE Solution Basic Signaling Procedure N-111
VoLTE Solution Basic Signaling Procedure N-112
VoLTE Solution Basic Signaling Procedure P-113
VoLTE Solution Basic Signaling Procedure N-114
VoLTE Solution Basic Signaling Procedure N-115
VoLTE Solution Basic Signaling Procedure N-116
VoLTE Solution Basic Signaling Procedure N-117
VoLTE Solution Basic Signaling Procedure N-118
VoLTE Solution Basic Signaling Procedure N-119
VoLTE Solution Basic Signaling Procedure N-120
VoLTE Solution Basic Signaling Procedure N-121
VoLTE Solution Basic Signaling Procedure N-122
VoLTE Solution Basic Signaling Procedure N-123
 VoLTE Solution Basic Signaling Procedure N-124

 Run ADD CIC to configure Carrier Identification Code. The SCC AS adds the
Carrier Identification Code to a calling number in the P-Asserted-Identity header
field to suppress repeated anchoring. It adds the Carrier Identification Code to the
Request-URI to notify the S-CSCF that the call needs to be routed to the MGCF.

 (Optional) Run MOD CSRETRYCFG to configure the CS Retry service data.

 If the SCC AS is required to route calls back to a CS domain based on the MSRNs
obtained from the HLR, set CS route mode to Use CSRN

 If the SCC AS is required to route calls back to a CS domain based on the CIC prefix
added to calling numbers or the CIC parameter added to called numbers, set CS
route mode to Use CIC
VoLTE Solution Basic Signaling Procedure N-125
VoLTE Solution Basic Signaling Procedure N-126
VoLTE Solution Basic Signaling Procedure N-127
VoLTE Solution Basic Signaling Procedure N-128
VoLTE Solution Basic Signaling Procedure N-129
VoLTE Solution Basic Signaling Procedure N-130
VoLTE Solution Basic Signaling Procedure N-131
VoLTE Solution Basic Signaling Procedure N-132
VoLTE Solution Basic Signaling Procedure N-133
VoLTE Solution Basic Signaling Procedure N-134