Huawei 5671d79a0462d

1 Library
Information
Purpose
The IMS Product Documentation Answer
House identifies common consulting
questions raised by users and offers an-
swers to the questions, helping users
quickly overcome difficulties by
themselves.
3/205
Overview
House covers questions about product
principles and operations, which may be
raised by users during product learning
and maintenance.
House provides answers to the preceding
questions to help users obtain key
information:
1. For questions about product prin-

ciples, the IMS Product Documenta-
tion Answer House explains and de-
scribes specific principles and
mechanisms.
2. For questions about product opera-
tions, the IMS Product Documenta-
tion Answer House provides opera-
tions methods and procedures re-
quired by certain tasks.
4/205
In addition, the IMS Product Document-

ation Answer House offers links to de-
tailed documents for users' reference.
Release History
Product Version D
IMS Product • IMS V200R009C00 F

Documentation or later o
Answer House r
• Convergent Confer-
ence Solution
V100R002C00 or
later
• RCS
V100R002C10LG0001
or later
• VoLTE V100R001C02
or later
5/205
2 Basic Signaling
Process of the
Huawei IMS
2.1 What Is the Architecture of the
Huawei IMS?
2.2 How Is the P-CSCF Discovered?
2.3 How Are S-CSCFs Assigned?
2.4 How Is the I-CSCF Discovered?
2.5 Why Is Registration Required?

6/205
2.6 Which Are Types of

Registration?
2.7 What Are Home and Visited

Domains?
2.8 What Is the IMS Session

Process?
2.9 What Are the Working Prin-

ciples of the DNS and ENUM?
2.10 What Are IMS-Relevant Inter-

faces and Protocols?
2.11 What Is a tel URI?
2.12 What Is a SIP URI?
2.13 Which Are types of tel

Number?
7/205
2.14 What Are the Relationships

Between an IMPI and an IMPU?
2.15 What Is PSI?
2.16 What Is the SIP Structure?
2.17 Which Are Types of SIP

Responses?
2.18 Is There Any Description

About Diameter?
2.19 Where Can I Find the Informa-

tion About the Differences Between
Two Versions?
8/205
2.1 What Is the

Architecture of the
Huawei IMS?
Question
What is the architecture of the Huawei
IMS?
Answer
NEs of the Huawei IMS are classified into
the following types: NEs in the Service
Layer, NEs in the Session Control & Me-
dia Resources Layer, NEs in the Access &
Bearer Control Layer, NEs in the Inter-
working Layer, NEs in the Interworking
Layer, NEs in the Operation Support
Layer.
• The service layer consists of all types

of ASs and resource servers. It
9/205
provides services such as the game,

conference and IM. It also provides
service capabilities such as Presence,
group and media resources.
• The session control layer performs
functions such as registration, authen-
tication, session route control, service
triggering, topology hiding inter-net-
work gateway (THIG), routing, re-
source control, and interworking.
• The access & bearer control layer con-
sists of functional NEs such as the
PDF, PCRF, SPDF, NACF, and CLF.
▪ It provides QoS resources control,
depending on service based local
policy (SBLP)/service based bearer
control (SBBC). It controls the re-
sources of the access network
through the PDF, PCRF, and SPDF.
10/205
▪ If fixed networks access the IMS,

the access & bearer control layer
can include the network attachment
subsystem (NASS). The NASS con-
sists of the CLF and NACF, and per-
forms the functions of location
management and network access
configuration to access fixed
networks.
▪ This layer also performs the NAT
control function to support NAT
traversal in enterprise networks.
• The interworking layer interworks

with the IMS, PSTN, PLMN, NGN and
H.323 network.
• The operation support layer includes
functional NEs such as the CCF,
Portal, service provisioning gateway
(SPG), element management system
(EMS), and DNS/ENUM server. This
11/205
layer helps to charge, address, manage

networks, store subscription data, and
operate Web Portal in a unified
manner.
Reference Link
For details, see Descriptions > IMS Solu-
tion Description > Description of the
Huawei IMS > Architecture of the Hua-
wei IMS in the IMS product
documentation.
Version
IMS V200R009C00 or later
12/205
2.2 How Is the P-CSCF

Discovered?
Question
How is the P-CSCF discovered?
Answer
The UE obtains the IP address of the P-

CSCF in the following ways:
• The cable modem obtains the P-CSCF

domain name and the DNS address
through Dynamic Host Configuration
Protocol (DHCP) and queries the DNS
for the IP address of the P-CSCF.
• The UE queries the DNS using the P-
CSCF domain name configured on the
cable modem to obtain the IP address
of the P-CSCF.
13/205
• The IP address of the P-CSCF can be

directly configured on the UE.
• For the UEs managed by the element
management system (EMS), the IP ad-
dress of the serving P-CSCF can be
configured through the web portal.
• If there is a session border controller
(SBC) between the UE and the P-
CSCF, the SBC is the entry to the IMS
network and therefore the IP address
of the SBC instead of the P-CSCF is
required.
Reference Link
For details, see Descriptions > Network-
ing Description > Access Network De-
scription User Manual > Cable Network
Access > End-to-End Service Procedure >
Detecting the P-CSCF in the IMS product
documentation.
14/205
Version
2.3 How Are S-CSCFs

Assigned?
Question
How are S-CSCFs assigned?
Answer
S-CSCFs are assigned as follows:
1. After receiving the REGISTER mes-

sage and determining that the visited
network is trusted, the I-CSCF sends
a User Authorization Request (UAR)
message to the HSS to obtain the S-
CSCF's IP address.
15/205
2. After receiving the UAR message, the

HSS determines that the subscriber is
defined based on data in the local
database. Then, the HSS sends a User
Authorization Answer (UAA) mes-
sage to the I-CSCF. The message con-
tains the S-CSCF's IP address or
capabilities.
3. The I-CSCF selects an appropriate S-
CSCF based on the returned result.
Reference Link
For details, see Description > Function
Description > Service Functions > Regis-
tration and Session> Registration in the
IMS product documentation.
Product Version
16/205
2.4 How Is the I-CSCF

Discovered?
Question
How is the I-CSCF discovered?
Answer
Based on the domain name in the IMPU
in the Request-URI header field, the P-
CSCF queries the DNS server, obtains the
I-CSCF's address, and forwards the
REGISTER message to the I-CSCF.
Reference Link
For details, see Description> Function
17/205
Product Version
2.5 Why Is Registration

Required?
Question
Why is registration required?
Answer
Registration is the process in which sub-

scribers request permissions to use ser-
vices provided by the subscription net-
work. After registering with the network,
subscribers can perform the following
operations:
• Bind their addresses and identities.

When a registered subscriber is called,
18/205
the subscription network connects the

call to the subscriber based on the
subscriber's registered address.
• Use services to which they have sub-
scribed, for example, the Basic Call
service and the Customized Ring Back
Tone Control and Trigger (CRBT)
service.
Reference Link
Product Version
19/205

Registration?
Question
Which are types of registration?
Answer
Based on the entity used to initiate regis-

tration, IMS registration can be classified
into two categories.
• Basic registration: It is initiated by

user equipment (UE). After registra-
tion, subscribers have basic service
rights to send or receive session and
subscription messages.
After a subscriber uses an IP multime-
dia public identity (IMPU) to register
with the IMS network, all IMPUs that
20/205
are in the same implicit registration

set (IRS) as the registered IMPU are
registered.
• Third-party registration: Based on ini-
tial filter criteria (iFC) that are sub-
scribed by subscribers, the serving-call
session control function (S-CSCF) ini-
tiates registration on behalf of the sub-
scribers to the application server (AS)
that provides those services. After re-
gistration, subscribers have the rights
of these services. The iFC have differ-
ent priorities and define the service
trigger points and ASs to be contacted.
When processing a registration mes-
sage, the S-CSCF matches the current
service with the iFC data. If they
match, the S-CSCF initiates a registra-
tion to the corresponding AS.
21/205
Reference Link
Product Version
2.7 What Are Home and

Visited Domains?
Question
What are home and visited domains?
Answer
In IMS, the home domain is the network
that has been subscribed by a subscriber
22/205
and visited domain is the network where

the subscriber is located.
Reference Link
None.
Version
2.8 What Is the IMS

Session Process?
Question
What is the IMS session process?
Answer
An IMS session process involves session
setup, media negotiation, resource
23/205
reservation, application service session,

and session release.
Reference Link
For details, see Description > Feature De-
scription > Basic and Regulatory Services
> Basic Call > Session in the IMS product
documentation.
Product Version
24/205
2.9 What Are the Working

Principles of the DNS and
ENUM?
Question
What are the working principles of the
domain name server (DNS) and E.164
number to URI mapping (ENUM)?
Answer
The DNS and ENUM are used for signal-
ing route on the IMS network.
• The DNS converts domain names to

corresponding IP addresses.
• The ENUM converts tel uniform re-
source identifiers (URIs) to SIP URIs.
25/205
Reference Link
For details, see User Manuals > Number
Analysis User Manual > Basic Concepts >
DNS/ENUM in the IMS product
documentation.
Product Version
2.10 What Are

IMS-Relevant Interfaces
and Protocols?
Question
What are IMS-relevant interfaces and
protocols?
26/205
Answer
IMS-relevant interfaces are mainly Cx,
Dx, and Mg interfaces and IMS-relevant
protocols are mainly SIP, Diameter, and
H.248.
Reference Link
For details, see Descriptions > IMS Solu-
tion Description in the IMS product
documentation.
Product Version
2.11 What Is a tel URI?

Question
What is a tel URI?
27/205
Answer
The telephone URI (tel URI) is used to
identify resources using a telephone
number. The tel URI starts with tel:, fol-
lowed by tel Number. It can be a global
number (tel:+861012345678) or a local
number (tel:12345678).
Reference Link
For details, see User Manual > Number
Number Structure > tel URI in the IMS
product documentation.
Product Version
28/205
2.12 What Is a SIP URI?

Question
What is a SIP URI?
Answer
The SIP URI is in User informa-
tion@Host port[parameter] format and
uniquely identifies a subscriber. The SIP
URI starts with sip: or sips:.
Reference Link
Number Structure > Support of the
IMPU in SIP URI Format in the IMS
29/205
Product Version
2.13 Which Are types of tel

Number?
Question
Which are types of tel number?
Answer
The tel number is a traditional number
that consists of numbers 0-9, characters
A-E, and a-e. It may contain character +
and separators such as en dash (-). The
character + is added before a tel number
to indicate that the number is a global
number. Numbers 12345678,
+86-10-12345678, and C0101119 are all
tel numbers.
30/205
The tel number can be a global number

or local number.
• Global number: It starts with character

+ and is in "Character (+) + National
code + Area code" format. The global
number is globally unique. For ex-
ample, the number +86-10-12345678
uniquely identifies a subscriber in
Beijing of China.
• Local number: It does not start with
character + and identifies a number
only in a certain area. If a number is
dialed in different areas, calls may be
addressed to different subscribers. For
example, dialing 12345678 in Shang-
hai calls a subscriber in Shanghai and
dialing 12345678 in Beijing calls a sub-
scriber in Beijing.
31/205
Reference Link
Number Structure > tel Number in the
Product Version
2.14 What Are the

Relationships Between an
IMPI and an IMPU?
Question
What are the relationships between an IP
multimedia private identity (IMPI) and
an IMS public user identity (IMPU)?
32/205
Answer
An IMS standard subscriber is assigned
one IMPI and two IMPUs in which IMPU
1 is SIP URI and IPMU 2 is tel URI. The
two IMPUs belong to the same implicit
registration set and the same alias group,
and share repository data.
• An IMPI is a subscriber identity

defined by the carrier of the home net-
work and is unique across the world.
An IMPI is used to for IMS network
registration, authentication, authoriza-
tion, and charging but is not used for
call addressing or routing.
• An IMPU is used to request commu-
nication with another subscriber and
can be made public. An IMPU is used
for routing of SIP messages.
33/205
Reference Link
For details, see Description > Service
Provisioning Description > Subscriber
Data > Standard IMS Subscribers > Data
Model in the IMS product
documentation.
Product Version
2.15 What Is PSI?

Question
What is PSI?
Answer
Public Service Identity (PSI) is an iden-
tity that identifies services, such as pres-
ence, messaging, conferencing, and
34/205
group, provided by the application server

(AS) in the IP Multimedia Subsystem
(IMS). PSI is in SIP URI or tel URI
format, for example,
sip:messaginglist_joe@ims.com. The AS
hosting a service sends a service request
to subscribers by using a PSI; PSI sub-
scribers can also send a service request to
the AS.
Reference Link
For details, see Descriptions > Function
Description > Service Functions > Public
Service Identity in the IMS product
documentation.
Product Version
IMS V200R009C00 or a later version
35/205
2.16 What Is the SIP

Structure?
Question
What is the SIP structure?
Answer
SIP is a text-based protocol and uses the
UTF-8 character set. A SIP message is
either a request from a client to a server,
or a response from a server to a client.
• The start line in a request is named

Request-Line, and that in a response is
named Status-Line.
• Any SIP message must contain header
fields, whereas a message body is op-
tional, depending on the message type
and service requirements.
36/205
• Header fields and message body are

separated by an empty line indicating
the end of the header fields.
• A message body can be a specific im-
plementation mode of the current ses-
sion, which is described by using SDP
or text.
Reference Link
For details, see References > Typical Sig-
naling Flows > IMS Protocol > SIP > SIP
Overview in the IMS product
documentation.
Product Version
37/205

SIP Responses?
Question
Which are types of SIP responses?
Answer
A SIP response is used to respond to a re-
quest, indicating the status (success or
failure) of a session.
SIP responses are categorized based on
the Status-Code. The Status-Code is a
3-digit integer result code. The first digit
of the Status-Code defines the class of re-
sponse. The last two digits provide fur-
ther description of the response.
SIP responses are categorized as follows:
38/205
• 1xx: Provisional; indicates that a re-

quest is received and the server con-
tinues to process the request.
• 2xx: Success; indicates that the action
was successfully received, understood,
and accepted.
• 3xx: Redirection; indicates that a fur-
ther action needs to be taken in order
to complete the request.
• 4xx: Client Error; indicates that the re-
quest contains bad syntax or cannot be
fulfilled at this server.
• 5xx: Server Error; indicates that the
server failed to fulfill an apparently
valid request.
• 6xx: Global Failure; indicates that the
request cannot be fulfilled at any
server.
39/205
Reference Link
For details, see References > Typical Sig-
naling Flows > IMS Protocol > SIP > SIP
Responses in the IMS product
documentation.
Product Version
2.18 Is There Any

Description About
Diameter?
Question
Is there any description about Diameter?
40/205
Answer
Description about Diameter is available
in the IMS product documentation.
Reference Link
For details, see References> Protocols>
Diameter in the IMS product
documentation.
Product Version
41/205
2.19 Where Can I Find the

Information About the
Differences Between Two
Versions?
Question
Where can I find the information about
the differences between two versions?
Answer
The Delta Description describes version

changes before and after an upgrade. It
describes the changes based on upgrade
paths and consists of NIRs and Delta
records.
• NIRs describe general impacts and

feature impacts.
42/205
• Delta records describe the version

changes before and after an upgrade,
including the MML command delta
description, timer delta description,
alarm delta description, CDR interface
delta description, software parameter
delta description, inter-NE interface
delta description, performance counter
delta description, license delta descrip-
tion, and communication matrix delta
description.
Reference Link
For details, see Descriptions > Delta De-
scription in the IMS product
documentation.
Product Version
43/205
3 IMS Hardware
Capabilities
3.1 What Are the Differences
Between a T8260 subrack and a
T8280 subrack?
3.2 What Are the Differences

Between Boards?
3.3 What Are the Power Consump-

tions of a Board and a Subrack?
3.1 What Are the

Differences Between a
44/205
T8260 subrack and a

T8280 subrack?
Question
What are the differences between a
T8260 subrack and a T8280 subrack?
Answer
The differences between a T8260 subrack
and a T8280 subrack mainly lie in the
switching, heat dissipation, and power
supply capabilities.
Reference Link
For details, see Descriptions > Hardware
Description > Subrack > Subrack Differ-
ences in the IMS product documentation.
45/205
Product Version
3.2 What Are the

Differences Between
Boards?
Question
What are the differences between
boards?
Answer
The differences between boards are as
follows:
• The differences among switch boards

mainly lie in the bandwidth of the bus,
that is, the transmission capability.
46/205
• The differences among switch inter-

face boards lie in the interfaces
provided externally.
• The differences among subrack man-
agement boards lie in the configura-
tion specifications, that is, the CPU
dominant frequency, memory capabil-
ity, and flash capability.
• The differences among processor
boards mainly lie in the configuration
specifications of their components,
such as the CPU core number, CPU
dominant frequency, memory capabil-
ity and hard disk capability.
• The differences among processor
boards. The differences among inter-
face boards of processor boards mainly
lie in different ports provided to con-
nect to the external network.
47/205
Reference Link
For details, see Descriptions > Hardware
Description > Board > Board Differences
Product Version
3.3 What Are the Power

Consumptions of a Board
and a Subrack?
Question
What are the power consumptions of a
board and a subrack?
48/205
Answer
The maximum power consumption of a
UPB board is from 125 W to 135 W. The
typical power consumption of a UPB
board is 110 W.
The typical power consumption of a
T8280 subrack is 92 W and the maxim-
um power consumption is 186 W.
Reference Link
For details on board power consump-
tions, see Descriptions > Hardware De-
scription > Board in the IMS product
documentation.
For details on subrack power consump-
tions, see Descriptions > Hardware De-
scription > Subrack > T8280 Subrack in
the IMS product documentation.
49/205
Product Version
4 IMS Software
Capabilities
4.1 What Is the Software Structure
of the OMU?
4.2 Which Are Types of ATS9900

Service Process?
4.3 What Are the IMS Software In-

stallation principles?
50/205
4.4 What Are the IMS Upgrade

Principles?
4.5 What Are Patch Installation

Principles?
4.6 Which Are Types of Announce-

ment Playback in the IMS Network?
4.7 What Is the Process of Loading

Tone Files of the AS?
4.1 What Is the Software

Structure of the OMU?
Question
What is the software structure of the
OMU?
51/205
Answer
The OMU server software is an applica-
tion software that is based on the ATCA
hardware platform, runs on the Linux op-
erating system (OS), and requires the
database. The OMU communicates with
the host through the IP buses in the
ATCA subracks. The OMU performs op-
erations and maintenance on external
equipment through the LMT and WebUI.
The LMT runs on the Microsoft Windows
OS and connects to the OMU through the
maintenance IP address of the OMU. You
can view performance measurement res-
ults and upgrade the system through the
WebUI.
Reference Link
For details, see Descriptions > Software
Description > OMU > OMU Software
52/205
Structure in the IMS product

documentation.
Product Version

ATS9900 Service Process?
Question
Which are types of ATS9900 service
process?
Answer
Table 4-1 describes the service processes

of the ATS9900.
Table 4-1 ATS9900 service processes
53/205
Service Function Working

Process Mode
IP forward The IFM re- 1+1 active/

module ceives IP standby
(IFM) messages
from external
systems and
forwards the
IP messages
to related
modules for
processing.
The IFM ap-
plies to fixed
network
scenarios,
that is, the
IFM pro-
cesses only
fixed network
services.
54/205

Process Mode
Dispatching The DPU re- 1+1 active/

unit (DPU) ceives IP standby
messages
from external
systems and
forwards the
IP messages
to related
modules for
processing.
The DPU ap-
plies to scen-
arios where
the fixed and
mobile net-
works are
convergent,
that is the
DPU pro-
cesses both
55/205

Process Mode
fixed and mo-

bile network
services.
Call control The CCU im- 1+1 active/

unit (CCU) plements the standby
call control
and protocol
processing
functions. It
also controls
and processes
service logic
for calls, re-
gistrations,
subscriptions,
and new
services.
The CCU ap-
plies to fixed
network
56/205

Process Mode
scenarios,
that is, the
CCU pro-
cesses only
fixed network
services.
Service con- The VCU im- 1+1 active/

trol unit plements the standby
(VCU) call control
and protocol
processing
functions. It
also controls
and processes
service logic
for calls, re-
gistrations,
subscriptions,
and new
services.
57/205

Process Mode
The VCU ap-

plies to scen-
arios where
the fixed and
mobile net-
works are
convergent,
that is the
VCU pro-
cesses both
fixed and mo-
bile network
services. Cur-
rently, the
VCU pro-
cesses certain
fixed network
services.
58/205

Process Mode
Central data- The CDB per- 1+1 active/

base board forms service standby
(CDB) allocation
and registra-
tion. It also
processes ser-
vices that oc-
cupy a large
number of re-
sources, such
as calling
number
analysis.
Multimedia The multime- Load-

signal gate- dia signal sharing
way (MSG) gateway
(MSG) pro-
cesses multi-
media proto-
cols for the
59/205

Process Mode
ATS9900,
such as SIP.
The MSG ap-
plies to fixed
network
scenarios.
Broadband The BSG pro- Load-

signal gate- cesses broad- sharing
way (BSG) band signal-
ing, such as
Diameter and
DNS.
Service pro- The SPU im- Load-

vision unit plements ser- sharing
(SPU) vice provi-
sioning in
such a way
that different
channels are
60/205

Process Mode
used for data

configuration
and call
processing.
Reference Link
For details, see Descriptions > Software
Description > ATS9900 Software Struc-
ture > Process Types of the ATS9900 in
Product Version
61/205
4.3 What Are the IMS

Software Installation
principles?
Question
What are the IMS software installation
principles?
Answer
Software installation refers to software

package installation after hardware in-
stallation in the deployment beginning
stage. Software installation consists of
the OMU, LMT, and service ME installa-
tion. For details about how to install soft-
ware, refer to Software Installation
Guide. The software installation principle
is shown in Figure 4-1.
62/205
Figure 4-1 Software installation principle
The details of software installation prin-

ciple are as follows:
1. Install the OMU board using the

INU4Win.exe, and connect the net-
work interface of the PC with the
back network interface of the SWI
board. During the installation, read
data from the PC after OMU reset
63/205
and start the operating system, then

install all software to the OMU, in-
cluding the operating system soft-
ware, auxiliary software, and OMU
application software.
2. Install the LMT through the OMU,
and connect the LMT through the
Java Web Start (JWS) for LMT
installation.
Java Web Start is an auxiliary applic-
ation program associated with the
Web browser. When a user clicks on a
link that points to a special launch
file (JNLP file), the browser launches
the Java Web Start, which then auto-
matically downloads, caches, and
runs a given Java technology-based
application program.
3. Install the service ME through the
LMT, and install software packages of
the service ME by running ADD ME
64/205
in the MML Command - CGP win-

dow of the client. Configure the ser-
vice board and basic data of service
application through the LMT and
OMU. After the service board starts,
it loads automatically the operating
system and service application soft-
ware to the OMU or Flash card.
Reference Link
Description > Software Management
Principles > Software Installation Prin-
ciple in the IMS product documentation.
Product Version
65/205
4.4 What Are the IMS

Upgrade Principles?
Question
What are the IMS upgrade principles?
Answer
Figure 4-2 shows the seamless upgrade

principle.
Figure 4-2 Seamless upgrade principle
66/205
The details of the seamless upgrade prin-

ciple are as follows:
1. The upgrade tool on the Web client

issues an upgrade start message.
2. When the OMU receives the message,
it divides all modules of MEs into the
active and standby planes first:
• The OMU divides standby pro-
cesses and some load-sharing pro-
cesses into plane 1. As the standby
plane, plane 1 is locked in the
standby status. The processes do
not switch to the active status if
the active processes are faulty.
• The OMU divides active processes
and some load-sharing processes
into plane 0. As the active plane,
plane 0 is locked in active status.
The processes do not switch to the
67/205
standby status if the standby pro-

cesses are faulty.
3. The OMU upgrades all the host pro-

cesses in plane 1 to a new version.
The OMU does not activate the links
of all the processes in plane 1. These
processes are in the idle state.
4. The OMU activates the links in plane
1, and keeps the links in the standby
status.
5. The OMU backs up the dynamic data
of the processes in plane 0 to the pro-
cesses in plane 1 across versions.
6. The OMU switches the processes in
plane 1 to the active status and
switches the processes in plane 0 to
the standby status.
The processes of the new version in
plane 1 take over the services. During
68/205
the takeover, the service interruption

duration is less than 10 seconds.
7. The OMU upgrades the processes in
plane 0 to a new version, then the
processes in plane 0 retain the
standby status and the processes in
plane 1 retain the active status.
8. The OMU consolidates plane 1 and 0,
then the active and standby status of
processes of MEs is unlocked and
process switchover is allowed.
9. The OMU returns the upgrade report
to the upgrade tool on the WebUI.
NOTE:
The type and version of service MEs determine
whether the hitless upgrade mechanism can be
used.
During an actual upgrade, check whether the up-
grade supports hitless upgrade based on the doc-
uments released with the software version.
69/205
Reference Link
Principles > Hitless Upgrade Principle in
Product Version
4.5 What Are Patch

Installation Principles?
Question
What are patch installation principles?
Answer
In some cases, software requires certain
modifications for removing known bugs
or adding new functions to meet service
70/205
requirements. In this case, you can install

software patches for the system. You are
advised to load patches when the traffic is
light. For example, load patches during
the period from 23:00 to 00:00.
The patches are classified into server

patches, hot patches, third-party software
patches, and OMU cold patches. Cur-
rently, patches are released in remote
patch package and installed using the
WebUI. In some cases, you still needs to
use the LMT or command lines in Linux
OS to maintain the patches. The methods
of using the patches are described as
follows:
• Server patch: You can run MML com-

mands on the LMT to install the cold
patches that require restarting boards.
• Hot patch: After hot patches are in-
stalled, you do not need to restart
71/205
OMU services or boards. You can run

MML commands on the LMT to install
hot patches.
• Third-party software patch: You can
run MML commands to install the
third-party software patches. The sys-
tem can automatically determine
whether to restart the boards based on
the properties of the third-party soft-
ware patches.
• OMU cold patch: You can run patch
scripts on the OMU board to install the
OMU patches that require restarting
OMU services.
NOTE:
The procedure for installing patches varies ac-
cording to the patches. You are advised to per-
form the patch installation using WebUI on a live
network. For details about the installation using
WebUI, see the Patch Notes and Patch Update
Guide released with versions.
72/205
Reference Link
Principles > Software Patch Principle in
Product Version

Announcement Playback
in the IMS Network?
Question
Which are types of announcement play-
back in the IMS network?
73/205
Answer
Announcement playback in the IMS net-

work is categorized as follows:
• By function implementation: Common

announcement playback and IVR an-
nouncement playback.
• By user experience: Basic ringback
tone, Failure tone, Common service
tone and IVR service tone.
• By announcement contents: Fixed an-
nouncement tone and Variable an-
nouncement tone.
Reference Link
For details, see Description > Function
Description > Service Functions > An-
nouncement playback > Basic Concepts
74/205
Product Version
4.7 What Is the Process of

Loading Tone Files of the
AS?
Question
What is the process of loading tone files
of the AS?
Answer
The AS provides tone files based on ser-
vices, and the MRFP loads files on
boards. The tone files on the MRFP are
classified into static tone files, dynamic
tone files, local media files.
75/205
Reference Link
Functions > Announcement Playing >
Implementation Principle > Media Pro-
cessing Principles in the IMS product
documentation.
Product Version
5 IMS Number
Analysis
76/205
5.1 How Can I Configure Number

Analysis for NP Services?
5.2 What Is the Route Analysis Flow

of the S-CSCF?
5.1 How Can I Configure

Number Analysis for NP
Services?
Question
How can I configure number analysis for
NP services?
Answer
NP service schemes are All Call Query
(ACQ), Onward Routing (OR), and Query
on Release (QoR). Different schemes are
used in different scenarios and different
number analysis data related to the
77/205
ATS9900, S-CSCF, I-CSCF, and MGCF

must be configured accordingly.
Reference Link
• For details on NP service schemes, see

Descriptions > Feature Description >
Basic and Regulatory Services > Num-
ber Portability Services > Number
Portability in the IMS product
documentation.
• For details on how to configure num-
ber analysis for NP services, see User
Manuals > Number Analysis User
Manual > Typical Number Analysis
Flows > Configuring Number Analysis
Data for the NP Service in the IMS
product documentation..
Product Version
78/205
5.2 What Is the Route

Analysis Flow of the
S-CSCF?
Question
What is the route analysis flow of the S-
CSCF?
Answer
Route analysis is a process in which NEs
analyze received call requests for call
routing purposes. The route analysis pro-
cess varies from NE to NE. NEs can be
configured to query different data tables
for flexible routing.
The serving-call session control function
(S-CSCF) obtains the address of the next
hop based on the called number, calling
number, calling party location, phone-
79/205
context, calling party category (CPC), ser-

vice tag, and media type in a received
message.
Reference Link
For details, see User Manuals> Number
Analysis Flows of IMS NEs > CSC3300
Number Analysis Flow > Number Analys-
is Flow of the S-CSCF > Route Analysis in
Product Version
80/205
6 IMS Service
Provisioning
6.1 What Are WSDL and XSD?
6.2 What Is Shared iFC?
6.3 What Is the iFC Structure?
6.4 What Are the Elements Used in

Regular Expressions?
81/205
6.1 What Are WSDL and

XSD?
Question
What are WSDL and XSD?
Answer
WSDL is an XML application used to de-
scribe web services. It defines the web
services as a group of service access
points. The client can access services con-
taining the file information or the pro-
cedure call by using these service access
points. This procedure is similar to the
remote procedure call.
XML Schemas Definition (XSD) is an ex-
tension of the XML SCHEMA files. XML,
XML SCHEMA, and document type
definition (DTD) all belong to SCHEMA.
82/205
XML is a collection of data. XSD specifies

the XML format and verifies the correc-
tion of the XML data. For example, when
you write an XML file, you must define
how many subelements or properties are
contained in an element, what type each
subelement or property is (such as digit
or character) using the DTD or SCHEMA.
The definition process is called data mod-
eling. The XSD is like a template, and the
XML files are valid only when they meet
the requirements of the XSD template.
Reference Link
For details, see Descriptions > Service
Provisioning Description > Northbound
Interfaces of Service Provisioning >
WSDL\XSD Files in the IMS product
documentation.
83/205
Product Version
6.2 What Is Shared iFC?

Question
What is shared iFC?
Answer
A group of iFCs shared by multiple ser-
vice profiles. The HSS and S-CSCF data-
bases store the same shared iFC data, in-
cluding shared iFC and associated iFC
template IDs. The S-CSCF obtains the
shared iFC template ID from the HSS and
obtains the associated shared iFC from
its local database.
84/205
Reference Link
Provisioning Description > Service Provi-
sioning Mechanism > Subscriber Data
Mechanisms > Shared iFC in the IMS
Product Version
6.3 What Is the iFC

Structure?
Question
What is the iFC structure?
Answer
An iFC is composed of zero or one Trig-
ger Point and one Application Server. A
85/205
Trigger Point is composed of one or mul-

tiple Service Point Triggers. The Applica-
tion Server is composed of the Service In-
formation and Include Register Request.
Reference Link
For details, see User Manuals > iFC User
Manual > iFC Structure and Composition
> iFC Structure in the IMS product
documentation.
Product Version
86/205
6.4 What Are the

Elements Used in Regular
Expressions?
Question
What are the elements used in regular
expressions?
Answer
A regular expression provides a concise
and flexible means for matching (specify-
ing and recognizing) strings of text, such
as particular characters, words, or pat-
terns of characters.
Reference Link
For details, see User Manuals > iFC User
Manual > iFC Structure and Composition
87/205
> References > Regular Expression in the

Product Version
7 IMS
Performance
Management
7.1 What Are the KPI Building
Principles?
88/205
7.2 What Is the IMS Network KPI

Model?
7.3 Which KPIs Do I Need to Pay At-

tention to Before and After an IMS
Upgrade?
7.4 How Can I Perform

Troubleshooting When IMS KPIs
Are Abnormal?
7.1 What Are the KPI

Building Principles?
Question
What are the IMS KPI building
principles?
89/205
Answer
The KPI system constitutes a hierarchical
view that reflects network performance
from the perspective of different users.
The hierarchical view consists of the
device layer, NE layer, network layer, and
user layer. KPI building principles are
worked out for each layer. For details, see
the following link. I
Reference Link
For details, see Descriptions > Perform-
ance Management Description > KPI Sys-
tem > KPI Building Principles in the IMS
Product Version
90/205
7.2 What Is the IMS

Network KPI Model?
Question
What is the IMS network KPI model?
Answer
Figure 7-1 shows the IMS network KPI

model.
NOTE:
• Engineers on a live network should focus on

the KPIs highlighted in red in Figure 7-1.
• Network KPIs vary from site to site. The KPIs
provided here are for reference only and do not
constitute a warranty on KPIs of IMS networks
provided by Huawei.
91/205
Figure 7-1 IMS network KPI model
Reference Link
ance Management Description > KPI Sys-
tem > Network KPI > Network KPI
92/205
Model in the IMS product

documentation.
Product Version
7.3 Which KPIs Do I Need

to Pay Attention to Before
and After an IMS
Upgrade?
Question
Which KPIs do I need to pay attention to
before and after an IMS upgrade?
93/205
Answer
Network performance is closely related to

the IMS version upgrade. The following
operations are required for an upgrade:
• Before an upgrade: Prepare a KPI

monitoring report of the recent week
for KPI comparison between the
source version and the target version.
Perform software mediation on the
M2000 based on the collected
information.
• After an upgrade: Modify customized
KPIs and add measurement objects as
required. Check whether KPIs are nor-
mal and there are customer com-
plaints about KPIs.
94/205
Reference Link
ance Management Description > Per-
formance Management Application >
KPI Monitoring Before and After an Up-
grade in the IMS product documentation.
Product Version
7.4 How Can I Perform

Troubleshooting When
IMS KPIs Are Abnormal?
Question
How can I perform troubleshooting when
IMS KPIs are abnormal?
95/205
Answer
This topic provides possible causes of

network, service, or interworking faults
from the abnormal KPI perspective, help-
ing users determine fault impacts and
locate the faults. When the impacts of
faults are not determined, you are ad-
vised to observe the changes in the values
of the KPIs of the serving-call session
control function (S-CSCF), proxy-call ses-
sion control function (P-CSCF), session
border controller (SBC), and access gate-
way control function (AGCF) to determ-
ine the impacts of faults. When the im-
pacts of faults are determined, comply
with the following rules to locate the
faults:
• If the entire network is faulty, first

check whether the KPIs of the S-CSCF
and P-CSCF are abnormal.
96/205
• If service faults occur only in a single

area or city, first check whether the
KPIs of the SBC, AGCF, and SIP
multiservice access node (MSAN) are
abnormal.
• If interworking faults occur, first check
whether the KPIs of the MGCF are
abnormal.
• If a certain type of service fault occurs,
first check whether the KPIs of the cor-
responding service AS are abnormal.
Reference Link
ance Management Description > Per-
formance Management Application >
Fault and Performance > Analyzing Ab-
normal KPIs in the IMS product
documentation.
97/205
Product Version
8 IMS Charging
Principles
8.1 What Is an ICID?
8.2 How Is Charging Correlation

Performed in the IMS network?
8.3 How Are CDRs Processed in the

IMS network?
98/205
8.1 What Is an ICID?

Question
What is an ICID?
Answer
Each IMS NE generates ACR messages
based on its own role and the received
session information. An ICID enables the
system to correct ACR messages gener-
ated by different IMS NEs for the same
session. This ensures that the BC obtains
complete and correct CDRs for this
session.
During offline charging, an ICID is gener-
ated by the first IMS NE in the Session
Initiation Protocol (SIP) signaling path
and then transferred to other IMS NEs.
The terminating P-CSCF deletes the
ICID.
99/205
Reference Link
For details, see Descriptions > Charging
Management Description > Offline Char-
ging > Basic Concepts in the IMS product
documentation.
Product Version
8.2 How Is Charging

Correlation Performed in
the IMS network?
Question
How is charging correlation performed in
the IMS network?
100/205
Answer
In the IMS network, charging correlation

is implemented in the following manner:
1. Charging messages are generated

separately. Each IMS NE generates
charging data record (ACR) messages
based on its function in a session and
sends the ACRmessages to the CCF
for preprocessing. The CCF prepro-
cesses the ACR messages into CDRs
and sends the CDRs to the billing
center (BC). The BC correlates the
CDRs and generates subscriber bills
and settlement bills. Exchange of
charging identifiers and deduction
are involved in the charging correla-
tion process.
2. Due to the separation of the bearer
plane and control plane, exchange of
charging messages must be
101/205
implemented by using the Policy De-

cision Function (PDF) and Policy En-
forcement Point (PEP). Charging cor-
relation between the IMS network
and the general packet radio service
(GPRS) network is implemented by
exchanging the IMS Charging Identi-
fier (ICID) and GPRS Charging Iden-
tifier (GCID).
NOTE:
In the Huawei IMS solution, charging data
record (CDR) correlation between the bearer
plane and control plane is implemented by
the Mediation.
3. Charging correlation between carriers

is implemented by using the inter op-
erator identifier (IOI) in the CDRs.
Reference Link
For details, see Description > Charging
Management Description > Offline
102/205
Charging > Implementation Principle >

Charging Correlation Principles in the
Product Version
8.3 How Are CDRs

Processed in the IMS
network?
Question
How are CDRs processed in the IMS
network?
Answer
IMS NEs send apply charging report
(ACR) messages to the CCF and the CCF
generates CDRs based on the ACR
103/205
messages. CDR processing includes du-

plicate ACR prevention, call detail record
(CDR) shielding, ACR consolidation, and
CDR sorting.
Reference Link
For details, see Description> Charging
Management Description > Offline Char-
ging > Implementation Principle > CDR
Processing in the IMS product
documentation.
Product Version
104/205
9 IMS
Redundancy
9.1 Which Redundancy Modes Are
Used by the IMS?
9.1 Which Redundancy

Modes Are Used by the
IMS?
Question
Which redundancy modes are used by the
IMS?
105/205
Answer
Common IMS redundancy modes are as
follows: 1+1 active/standby, 1+1 mutual
assistant, N+1 active/standby and Pool.
Reference Link
For details, see User Manuals > IMS Re-
dundancy User Manual > Introduction to
the Redundancy System in the IMS
Product Version
106/205
10 IMS
Troubleshooting
10.1 What Can I Do If the I-CSCF
Returns a 403 Response That Car-
ries "Invalid User"?
107/205
10.1 What Can I Do If the

I-CSCF Returns a 403
Response That Carries
"Invalid User"?
Question
What can I do if the I-CSCF returns a 403
response that carries "Invalid User"?
Answer
During the registration process of a sub-

scriber, the I-CSCF returns a 403 re-
sponse, in which the Warning header
field carries the message "Invalid User".
The registration of the subscriber fails.
• Check the IMPU and the IMPI of the

subscriber.
108/205
• Check whether the subscriber is

defined on the HSS.
• On the HSS, check whether the IMPU
and the IMPI carried by the
REGISTER request belong to the same
subscriber.
Reference Link
For details, see Fault Management >
Troubleshooting > Service Failures > Re-
gistration Failures > CSC3300 Registra-
tion Failures in the IMS product
documentation.
Product Version
109/205
11 General
IMS-Relevant
Operations
11.1 How Can I Replace an SMM
Board?
11.2 How Can I Obtain the BOM

Code of a Spare Part?
11.3 How Can I Load a License File?

110/205
11.1 How Can I Replace an

SMM Board?
Question
How can I replace an SMM board?
Answer
An SMM board can be replaced with an
SMM board of the same model or of a dif-
ferent model. In most cases, you can re-
place only the SMM boards that are
faulty or working in the standby state. Do
not directly replace an SMM board that is
working in the active state.
Reference Link
For details, see

111/205
• Fault Management > Parts Replace-

ment > Replacing a Board > Replacing
an SMM Board of Same Model in the
• Fault Management > Parts Replace-
ment > Replacing a Board > Replacing
an SMM Board of Different Models in
Product Version
11.2 How Can I Obtain the

BOM Code of a Spare Part?
Question
How can I obtain the BOM code of a
spare part?
112/205
Answer
Bill of material (BOM) codes of all spare
parts for the IMS can be obtained from
bar codes on labels that are attached on
spare parts.
Reference Link
For details, see References > Spare Parts
> How to Obtain BOM Codes of Spare
Parts in the IMS product documentation.
Product Version
11.3 How Can I Load a

License File?
Question
How can I load a license file?
113/205
Answer
An operator with the associated rights
obtains the license file, and then uploads
and activates it on the OMU client.
Reference Link
For details, see References > General
Operation > Loading a License in the
Product Version
114/205
12 Convergent
Conference Solution
12.1 What Is a Telepresence
Conference?
12.2 What Is a Web Conference?
12.3 What Is a Public Conference?
12.4 What Is a Group Call

Conference?
12.5 What Is a Private Conference?
12.6 What Is a Subconference?

115/205
12.7 What Is a Security Conference?
12.8 What Is a Video Broadcasting?
12.9 What Is Video Selection?
12.10 What Is Chairperson Video

Selection?
12.11 What Is Multipicture Control?
12.12 What Are Auxiliary Feeds?
12.1 What Is a
Telepresence Conference?
Question
What is a Telepresence conference?
116/205
Answer
The Telepresence Conference service is
provided by the convergent conference
system (CCS) to offer subscribers life-size
presentation and face-to-face communic-
ation experience as if they were person-
ally in the scene. In Telepresence confer-
ences, communication is not limited to
video and voice. Body movements, facial
expressions, and eye contacts of parti-
cipants are vividly delivered to each
other.
To ensure authentic face-to-face commu-
nication experience, the CCS has
incorporated cutting-edge technologies in
the following fields: intelligent IP net-
work, unified communication, ultra-high-
fidelity video conference, spatial audio,
interactive collaboration components, di-
gital movie, lighting, and ergonomics.
117/205
Figure 12-1 shows a Telepresence confer-

ence scene.
Figure 12-1 Telepresence conference scene
Location in Navigation Tree

For details, see Descriptions > Feature
Description > Telepresence Conference
in the Convergent Conference Solution
118/205
Product Version
Convergent Conference Solution
V100R002C00 or later
12.2 What Is a Web

Conference?
Question
What is a Web conference?
Answer
Web Conference is a service provided by

the convergent conference system which
integrates data and voice/video. If a car-
rier has subscribed to the Data Confer-
ence service, the site can use the Web
Conference service by combining a voice
or video conference with a data
119/205
conference. Web conferences are classi-

fied into the following types:
• Web conference (voice+data)

• SD Video Conference + Data
Conference
The following licenses are required for

this combination:
▪ Standard Definition Video Confer-
ence License (Per Port)
▪ Data Conference License (Per Port)
• HD Video Conference + Data

Conference

this combination:
▪ High Definition Video Conference
License (Per Port)
120/205
• Telepresence Conference + Data

Conference

this combination:
▪ Telepresence Conference License
(Per Port)

Description > Web Conference in the
Convergent Conference Solution product
documentation.
Product Version
121/205
12.3 What Is a Public

Conference?
Question
What is a Public conference?
Answer
The Public Conference service enables
the convergent conference system to
provide instant voice conferences.
Subscribers who have subscribed to the
Private Conference service do not need to
schedule a conference and can create a
conference anywhere anytime.
After a subscriber dials an access number
to initiate a public conference, the sub-
scriber is prompted to enter phone num-
bers of other participants. The conver-
gent conference system then
122/205
automatically invites other participants

to the public conference.
In a public conference, the conference
initiator has the chairperson rights and
other participants have the guest rights.
Figure 12-2 shows how to establish a

public conference.
123/205
Figure 12-2 Process for establishing a pub-

lic conference
124/205

Description > Scheduling-Free Confer-
ence Service > Public Conference in the
documentation.
Product Version
12.4 What Is a Group Call

Conference?
Question
What is a Group Call Conference?
125/205
Answer
The Predefined Group Call Conference
service is a reservationless conference
service provided by the convergent con-
ference system that allows subscribers to
hold a voice conference based on a pre-
defined group. This service provides the
following types of conference services:
• Alert Conference
When an emergency occurs, a sub-
scriber in a predefined alert confer-
ence group can dial the emergency ac-
cess number to hold an instant alert
conference. The convergent conference
system automatically calls all members
in the group. After answering the call,
these members attend the conference.
One alert conference group can simul-
taneously hold multiple alert confer-
ences. A predefined alert group is a
126/205
special group in which the group

members have subscribed to the One
Number service. That is, a number re-
gistered by a group member is bound
to multiple numbers. For example, a
group member's number (number a) is
bound to numbers a1, a2, a3, a4, and
a5. When an alert conference (confer-
ence A) starts, the system calls number
a. a1, a2, a3, a4, and a5 are alerted. If
a1 answers the call, a1 joins conference
A. At this time, another alert confer-
ence (conference B) starts and the sys-
tem calls number a. a2, a3, a4, and a5
are alerted. If a2 answers the call, a2
joins conference B. This example
shows that one alert conference group
can simultaneously hold multiple alert
conferences.
• Group Call Conference
127/205
One group can hold only one group

call conference at a time. An author-
ized subscriber in a predefined group
can hold an instant group call confer-
ence by dialing the group call access
number. The convergent conference
system automatically calls all members
in the group. After answering the call,
these members attend the conference.
The PTT service can be used in group
call conferences. After a conference
initiator presses the intercom button,
the convergent conference system
automatically creates a group call con-
ference and calls all members in the
group. The calls are automatically con-
nected, and the members are muted
after they attend the conference. The
members can press the intercom but-
ton on their terminals to cancel the
mute state.
128/205
• Group Announcement Broadcast

An authorized subscriber in a pre-
defined group can record or update
group announcements on the conver-
gent conference system or upload an-
nouncement files to the system. When
the announcement broadcast function
is enabled, the system calls all mem-
bers in the group. After answering the
call, these members hear the recorded
announcements from the start.
The recorded announcements can be
either a broadcast announcement or a
public announcement. Broadcast an-
nouncements are broadcast to all
group members, whereas public an-
nouncements are played for sub-
scribers who dial the access number
for group announcement playback.
The same announcement may be used
129/205
for either a broadcast or public

announcement.

Description > Scheduling-Free Confer-
ence Service > Predefined Group Call
Conference in the Convergent Conference
Solution product documentation.
Product Version
12.5 What Is a Private

Conference?
Question
What is a Private conference?
130/205
Answer
The Private Conference service enables
users to schedule and create a conference
using a fixed conference ID and chairper-
son password provided by the convergent
conference system (CCS).
If the system administrator specifies a
private conference ID when adding a
user, the user can use the Private Confer-
ence service. The user's phone account
password becomes the conference chair-
person password.
Users can schedule and create a private
conference through the User Portal, M-
Meeting or by dialing the private confer-
ence access number. Participants can be
invited to a private conference or join the
private conference through the User
Portal, M-Meeting, or by dialing the
private conference access number.
131/205
Figure 12-3 shows how to establish a

private conference.
Figure 12-3 Process for establishing a
private conference
1: A user schedules a private conference

through the User Portal or M-Meeting or
by dialing the access number, conference
ID, and chairperson password.
2: After the conference starts, the chair-
person invites participant A to the
conference.
132/205
3: Participants B and C joins the confer-

ence through the M-Meeting or by dialing
the access number, conference ID, and
guest password.
The Private Conference service supports

the following media:
• Voice
• Standard-definition (SD) video
• High-definition (HD) video
• Telepresence
• Voice+data
• SD video+data
• HD video+data
• Telepresence+data
133/205

Description > Private Conference in the
documentation.
Product Version
12.6 What Is a
Subconference?
Question
What is a Subconference?
Answer
The subconference service enables the
chairperson in a main conference to
134/205
initiate a voice conference (called

subconference).
The chairperson can add subscribers in-
side or outside a main conference to a
subconference.
Figure 12-4 shows the relationship

between the main conference and the
subconference.
135/205
Figure 12-4 Relationship between the main

conference and the subconference
As shown in Figure 12-4, the relationship

between the main conference and the
subconference is as follows:
136/205
• Subconferences can be created only for

voice conferences.
• The main conference and subconfer-
ence do not affect each other. Sub-
scribers in the main conference do not
know what is discussed in the subcon-
ference, and subscribers in the sub-
conference do not know what is dis-
cussed in the main conference.
• The subconference depends on the
main conference.
• Only one subconference can be initi-
ated from the main conference. If the
subconference ends before the main
conference, the chairperson can initi-
ate a new subconference.
• When the main conference ends, the
subconference automatically ends.
137/205

Description > Subconference in the Con-
vergent Conference Solution product
documentation.
Product Version
12.7 What Is a Security

Conference?
Question
What is a Security conference?
Answer
The Security Conference service is an ad-
vanced conference service that allows
138/205
subscribers to participate in a conference

only if their personal identification num-
bers (PINs) are authenticated by the con-
vergent conference system. This service
ensures conference security.
The convergent conference system au-

thenticates subscribers based on their
PINs or Caller Identity (CLI) to prevent
unauthorized subscribers from accessing
conference information and to ensure
that all conference participants are au-
thorized subscribers.
NOTE:
PIN: There are formal PINs and temporary PINs.
A formal PIN is unique within the convergent
conference system, whereas a temporary PIN is
unique only within a conference. Subscribers con-
figure their formal PINs when they are defined on
the Administrator Portal or maintain their formal
PINs on the User Portal. Temporary PINs are sent
to subscribers in the conference notification.
139/205
Subscribers can input their temporary PINs or

formal PINs (if they have configured a formal
PIN) to attend a conference.
CLI: CLI authentication refers to participant
number authentication. The convergent confer-
ence system determines whether to allow a sub-
scriber to attend a conference based on the au-
thentication of the calling number.

Description > Security Conference in the
documentation.
Product Version
140/205
12.8 What Is a Video

Broadcasting?
Question
What is a Video Broadcasting?
Answer
This service enables a chairperson to
broadcast the video of a participant to
other participants and the video viewed
by the participant will not be switched.
Moreover, the chairperson can choose a
video or appoint a participant whose
video is broadcast to watch a specific
video. The video broadcasting is one of
services in MediaX3600 convergent con-
ference system.
141/205

Description > Conference Service Func-
tions > Conference Control > Video
Broadcasting in the Convergent Confer-
ence Solution product documentation.
Product Version
12.9 What Is Video

Selection?
Question
What is Video selection?
142/205
Answer
Video selection service enables chairper-
sons to set a participant's video or shared
desktop as the video source of a specified
picture.

tions > Conference Control > Video
Selection in the Convergent Conference
Solution product documentation.
Product Version
143/205
12.10 What Is
Chairperson Video
Selection?
Question
What is Chairperson Video Selection?
Answer
The Chairperson Video Selection service
enables chairpersons to select a video
they want to view, without changing the
video being broadcast to other parti-
cipants. This service is used when only
one picture is specified as the broadcast
source on the User Portal.

Description > Conference Service
144/205
Functions > Conference Control > Chair-

person Video Selection in the Convergent
Conference Solution product
documentation.
Product Version
12.11 What Is Multipicture

Control?
Question
What is Multipicture Control?
Answer
The Multipicture Control service enables
the convergent conference system (CCS)
to simultaneously display multiple video
145/205
pictures on each video terminal in a con-

ference. One of these pictures is the
primary picture, while others are second-
ary pictures. The conference chairperson
can configure each picture from one or
more video sources, such as participant
videos or auxiliary streams.

tions > Conference Control > Multipic-
ture Control in the Convergent Confer-
ence Solution product documentation.
Product Version
146/205
12.12 What Are Auxiliary

Feeds?
Question
What are auxiliary feeds?
Answer
The Dual Streams service enables video

terminals to send or receive main and
auxiliary feeds at the same time and dis-
play them on different screens.
• Main feeds are video streams, for ex-

ample, participant images.
• Auxiliary feeds are feeds from PCs.

Description > Conference Service
147/205
Functions > Auxiliary Conference Func-

tions > Dual Streams in the Convergent
Conference Solution product
documentation.
Product Version
13 RCS Solution
13.1 What Is the MSRP?

148/205
13.2 What Are the Highlights of the

RCS9880?
13.3 How to Synchronize UUIDs

Among All Nodes in a Cluster?
13.4 What Are the Instant Mode

and Store-and-Forward Mode?
13.5 What Is RCS?
13.6 What NEs Do the I2000 and

M2000 Manage?
13.7 What Users Are Created by the

System During RCS9880
Installation?
13.8 How to Check the VCS

Version?
13.9 How to Check the UUID of

Nodes in a Cluster?
149/205
13.10 How to Configure the Physical

IP Address of the SMM Board?
13.1 What Is the MSRP?

Question
What is the MSRP?
Reply
According to the Message Session Relay
Protocol (MSRP), media streams in an
RCS session are transmitted over MSRP
connections. The MSRP is based on the
Transmission Control Protocol (TCP) and
is especially suitable for transmission of
instant messages. MSRP connections ini-
tiated by INVITE messages have a higher
transmission speed and security than
Session Initiation Protocol (SIP) connec-
tions over the User Datagram Protocol
(UDP)/Internet Protocol (IP).
150/205
Reference Link
scription > Basic Service > Instant Mes-
saging > Implementation Principle >
Basic Concepts in the RCS9880 product
documentation.
Product Version
RCS V100R002C10LG0001 or later
13.2 What Are the

Highlights of the
RCS9880?
Question
What are the highlights of the RCS9880?
151/205
Reply
The RCS9880 is the core NE for RCS ser-
vices and provides the following
functions:
• Stores, forwards, and schedules mes-

sages in one-to-one chats, stores files
for offline subscribers, resumes inter-
rupted file transfers.
• Saves created one-to-multiple chat
conferences to the server so that mem-
bers in the conferences can join the
conferences and chat with other mem-
bers at any time.
• Supports the terminal wakeup capabil-
ity provided by the Apple Push Notific-
ation service (APNs) so that sub-
scribers can be always online.
152/205
• Supports interworking with traditional

PLMN short message system to pro-
tect carriers' investments.
• Supports large-capacity cluster deploy-
ment and geographic redundancy.
• Supports co-deployment with the VoIP
and VoLTE solutions on the same
hardware platform.
Reference Link
For details, see Description > Product
Description > Highlights in the RCS9880
Product Version
153/205
13.3 How to Synchronize

UUIDs Among All Nodes
in a Cluster?
Question
How to synchronize UUIDs among all
nodes in a cluster?
Reply
If nodes of a cluster have different
UUIDs, you must select a reference node
and synchronize its UUID to all other
nodes in this cluster. Perform the follow-
ing steps to synchronize UUIDs:
1. As user root, log in to the reference

node you selected.
154/205
2. Run the following command to syn-

chronize the UUID of this node to an-
other node:
/opt/VRTSvcs/bin/uuidconfig.pl
-clus -copy -from_sys srv1 -
to_sys srv2
In the command, "srv1" indicates the
name of the local host and "srv2" in-
dicates the name of another host.
3. Repeat the preceding command to
synchronize the UUID to all other
nodes.
NOTE:
You can also synchronize UUIDs by copying the
clusuuid file in /etc/vx/.uuids from one node
to another.
Reference Link
For details, see Installation and Commis-
sioning > Appendix > Appendix B-VCS
155/205
FAQ > How to Synchronize UUIDs

Among Nodes in the RCS9880 product
documentation.
Product Version
13.4 What Are the Instant

Mode and
Store-and-Forward Mode?
Question
What are the instant mode and store-
and-forward mode?
Reply
The instant mode and store-and-forward
mode are the two delivery modes of in-
stant messages.
156/205
• In instant mode, when the RCS AS re-

ceives a message from the calling
party, it first forwards the message to
the called party and then returns a re-
sponse to the calling party.
• In store-and-forward mode, when the
RCS AS receives a message from the
calling party, it first returns a response
to the calling party and then forwards
the message to the called party.
Reference Link
scription > Basic Service > Instant Mes-
saging in the RCS9880 product
documentation.
Product Version
157/205
13.5 What Is RCS?

Question
What is RCS?
Reply
Rich Communication Suite (RCS) is a
suite of services that includes voice calls,
video calls, instant messaging (IM) ser-
vices (such as, instant messages, Pres-
ence service, address book synchroniza-
tion, and file transfer), and sharing ser-
vices (picture sharing and video sharing).
IMS-based RCS services enhance user ex-
perience such as a better QoS. Therefore,
the QoS of RCS services can be guaran-
teed by using dedicated bearers.
158/205
Reference Link
For details, see Glossary in the RCS9880
Product Version
13.6 What NEs Do the

I2000 and M2000
Manage?
Question
What NEs do the I2000 and M2000
manage?
Reply
In the Rich Communication Suite (RCS)
solution, the M2000 manages IMS NEs
159/205
and the I2000 manages the RCS AS. The

M2000 and I2000 provide northbound
interfaces (NBIs) to connect to the net-
work management system (NMS) and
southbound interfaces (SBIs) to connect
to their managed NEs.
Reference Link
For details, see Description > Product
Description > Operation and Mainten-
ance > Network Management in the
RCS9880 product documentation.
Product Version
13.7 What Users Are

Created by the System
160/205
During RCS9880
Installation?
Question
What users are created by the system
during RCS9880 installation?
Reply
The system automatically creates certain
users during RCS9880 installation. Table
13-1 lists details about the users.
Table 13-1 RCS9880 user planning
NE User User User U

Type Name ID G
RMC/ Operating see 550 sneg

Presence/ system
CAB users
161/205
NE User User User U

Type Name ID G
BMSuite Operating bmp 2100 sneg

system
users
bmpftp bmpftp 1050 sneg
mediation mediation 551 med

162/205
NE User User User U

Type Name ID G
163/205
NE User User User U

Type Name ID G
I2000 Operating devdata 600 neg

system
users
imapuser 550 ima
omc 1049 ima

164/205
NE User User User U

Type Name ID G
ftpuser 650 fileg
srcuser 700 term
nmsguest 750 nms

165/205
NE User User User U

Type Name ID G
166/205
NE User User User U

Type Name ID G
Common UOA uoa 560 sneg

users
ROOT root 0 root
oracle oracle 1048 oins

dba
sysomc sysomc 800 adm

sneg
oins
dba
167/205
NE User User User U

Type Name ID G
sshusr sshusr 1000 user
sms sms / sneg

168/205
NE User User User U

Type Name ID G
Reference Link
sioning > Software Installation > Prepar-
ations > Preparing Data > User Planning
in the RCS9880 product documentation.
Product Version
169/205
13.8 How to Check the

VCS Version?
Question
How to check the VCS version?
Reply
Perform the following steps to check the
VCS version:
1. Log in to any node of the cluster as

user root.
2. Run the following command: rpm -q
VRTSvcs
3. Check the VCS version in the output.
If the version is VCS 4.1, the output

should be as follows:
VRTSvcs-4.1.40.30-MP4RP3_SLES10
170/205
If the version is VCS 5.1, the output

should be as follows:
VRTSvcs-5.1.100.000-SP1GA_SLES10
Reference Link
FAQ > How to Check VCS Version in the
RCS9880 product documentation.
Product Version
171/205
13.9 How to Check the

UUID of Nodes in a
Cluster?
Question
How to check the UUID of nodes in a
cluster?
Reply
Perform the following steps to check the
UUID of nodes in a cluster. All nodes in a
cluster must have the same UUID.
1. Log in to a node of the cluster as user

root.
2. Run either of the following com-
mands to check the UUID:
• /opt/VRTSvcs/bin/uuidcon-
fig.pl -clus -display srv2
172/205
In the command, "srv2" indicates

the node name and depends on the
actual configuration.
• cat /etc/vx/.uuids/clusuuid
In the command, "/etc/vx/.uuids/
clusuuid" indicates the file that
stores the UUID.
Reference Link
FAQ > How to Synchronize UUIDs
Among Nodes in the RCS9880 product
documentation.
Product Version
173/205
13.10 How to Configure

the Physical IP Address of
the SMM Board?
Question
How to configure the physical IP address
of the SMM board?
Reply
After a planned IP address is configured
for the SMM board, users can use this IP
address to log in to the SMM board
through Internet Explorer (input the ad-
dress as http://physical IP address of the
SMM board) or PuTTY (use the SSH pro-
tocol). After the login, users can perform
maintenance operations.
174/205
Product Version
14 VoLTE
Solution
14.1 What Is the Difference
Between the VoLTE and CSFB
Solutions?
14.2 What Types of LTE Terminals

Are There?
175/205
14.3 How Does a UE Obtain the P-

CSCF Address?
14.4 How Many APNs Should Be

Created When VoLTE Subscribers
Attach to the Network?
14.5 For PS Voice Calls, How to Pre-

vent Repeated Charging by IMS and
EPC?
14.6 What Is Domain Selection?
14.7 What Is SRVCC/eSRVCC?
14.8 What Is the Difference

Between eSRVCC and SRVCC?
14.9 In What Scenarios Is the An-

choring Function Needed?
14.10 What Is the IP-SM-GW?

176/205
14.1 What Is the

Difference Between the
VoLTE and CSFB
Solutions?
Question
What is the difference between the
VoLTE and CSFB solutions?
Reply
The voice over long term evolution
(VoLTE) solution is an IMS-based voice
solution for LTE networks. In this solu-
tion, voice, video, SMS, and supplement-
ary services are processed in the IMS net-
work. Voice and video traffic of these ser-
vices is carried over IP networks and the
Policy Charging and Control (PCC)
177/205
mechanism is provided to achieve end-

to-end quality of service (QoS) of voice
traffic.
The circuit switched fallback (CSFB)
solution reuses CS networks to provide
voice services for LTE terminals and LTE
networks themselves provide only data
services. In this solution, when a terminal
tries to originate a voice service, the LTE
network instructs the terminal to fall
back to the CS domain.
Figure 14-1 shows the difference between
the VoLTE and CSFB solutions.
178/205
Figure 14-1 Difference between the VoLTE

and CSFB solutions
VoLTE is considered the ultimate voice

solution for LTE networks. CSFB is used
as a transitional solution because it re-
uses CS networks and does not require
deployment of IMS. Therefore, CSFB will
exist together with VoLTE in a long
period.
179/205
Reference Link
For more information, see Descriptions >
Solution Description > LTE Voice Solu-
tions in the VoLTE product
documentation.
Product Version
VoLTE V100R001C02 or later
14.2 What Types of LTE

Terminals Are There?
Question
What types of LTE terminals are there?
Reply
Long Term Evolution (LTE) terminals are

classified into voice over LTE (VoLTE)
and non-VoLTE terminals.
180/205
• VoLTE terminals are those that rely on

an IP multimedia subsystem (IMS) do-
main or an LTE network to use voice
services.
• Non-VoLTE terminals are those that
rely on a circuit switched (CS) domain
to use voice services while connecting
to the LTE network to use data
services.
Table 14-1 describes each type of VoLTE

terminal.
Table 14-1 VoLTE terminals
Terminal Type Description
Single Radio • A dual-mode ter-

minal with a
single subscriber
identity module
(SIM) card. Single
181/205
Radio terminals
can access an IMS
domain through
an LTE network
or access a CS do-
main through a
2G/3G network.
However, they
connect to either
an IMS or a CS
domain.
• Uses IMS voice
services while in
LTE networks;
uses CS voice ser-
vices while in 2G/
3G networks.
• Supports a single
radio voice call
continuity
(SRVCC) or
182/205
enhanced SRVCC
(eSRVCC) han-
dover after mov-
ing out of LTE
coverage.
LTE data card A software client on

PCs to use IMS voice
services.
Customer premises A terminal connec-

equipment (CPE) ted to a plain old
telephone service
(POTS) terminal to
use IMS voice
services.
Table 14-2 describes each type of non-

VoLTE terminal.
Table 14-2 Non-VoLTE terminals
183/205
Dual Radio • A dual-mode ter-

minal with a
single SIM card.
Dual Radio ter-
minals can be
connected to both
LTE and 2G/3G
networks at the
same time.
• Uses CS voice ser-
vices and LTE
data services.
• Does not support
an SRVCC or
eSRVCC
handover.
Circuit switched fall- • A dual-mode ter-

back (CSFB) minal with a
terminal single SIM card.
CSFB terminals
184/205
are preferentially
connected to an
LTE network.
They fall back to a
CS domain when
they need to use
voice services.
• Uses CS voice ser-
vices and LTE
data services.
• Does not support
an SRVCC or
eSRVCC
handover.
Product Version
185/205
14.3 How Does a UE

Obtain the P-CSCF
Address?
Question
How does a UE obtain the P-CSCF
address?
Reply
A UE includes 000CH (P-CSCF IPv4
Address Request) in the Protocol Con-
figuration Options information element
(IE) contained in an Attach request mes-
sage or a PDN Connectivity Request mes-
sage. The UE then sends the message to
the P-GW to request a P-CSCF address.
Based on the access point name (APN) or
subscriber identifier information (IMSI
or MSISDN), the P-GW searches the local
186/205
P-CSCF address data for a suitable P-

CSCF address and sends a session re-
sponse message to the UE. This message
contains the address of the P-CSCF that
is assigned to the UE.
Reference Link
Description > Registration in the VoLTE
Product Version
187/205
14.4 How Many APNs

Should Be Created When
VoLTE Subscribers Attach
to the Network?
Question
How many APNs should be created when
VoLTE subscribers attach to the
network?
Reply
When Long Term Evolution (LTE) sub-
scribers attach to the evolved packet core
(EPC) network, two separate access point
names (APNs) should be created. One is
used for data services and the other is
used for IMS services. The two APNs cor-
respond to different default bearers and
different IP addresses.
188/205
Reference Link
Description > QoS in the VoLTE product
documentation.
Product Version
14.5 For PS Voice Calls,

How to Prevent Repeated
Charging by IMS and EPC?
Question
For PS voice calls, how to prevent re-
peated charging by IMS and EPC?
189/205
Reply
When a subscriber accesses the IMS net-

work through the evolved packet core
(EPC) network, the EPC network charges
the subscribers for the used packet
switched (PS) bearer bandwidth. To
avoid repeated charging by IMS and EPC,
the billing center (BC) correlates IMS
CDRs and EPC CDRs in either of the fol-
lowing ways:
• (Recommended) If IMS services use a

separate access point name (APN), the
BC uses only IMS CDRs and does not
charge the subscriber for the PS traffic
used at this access point.
• If IMS services and data services use
the same APN, both IMS and EPC do-
mains generate CDRs. The BC correl-
ates IMS CDRs and EPC CDRs based
on the IMS charging identifiers
190/205
(ICIDs) and GPRS charging identifiers

(GCIDs) contained in CDRs.
Reference Link
For details, see Descriptions > Solution
Description > Charging in the VoLTE
Product Version
14.6 What Is Domain

Selection?
Question
What is domain selection?
191/205
Reply
UEs that support voice over long term
evolution (VoLTE) can access a 2G/3G
network, an LTE network, or both at the
same time, depending on the LTE signal
strength. Therefore, when a UE that sup-
ports VoLTE initiates or receives a call, a
network must be used to connect the call.
This process is called domain selection.
When a UE originates a call, the UE per-

forms domain selection based on data of
the network with which the UE has re-
gistered. When a UE receives a call, the
network side queries data of the network
with which the UE has registered and
performs domain selection. LTE sub-
scribers share the same number seg-
ments with 2G/3G subscribers. The net-
work side cannot connect a call to the
LTE or circuit switched (CS) network
simply based on the number segment of
192/205
the called party. Instead, it must query

the convergent HLR/HSS for the domain
selection information about the called
party and connect the call to the LTE or
CS network based on that information.
NOTE:
Domain selection by the network applies only to
Single Radio terminals. Other LTE terminals are
connected to only one network for voice services,
which does not involve domain selection.
As defined by 3GPP, domain selection by

the network is implemented by the T-
ADS, the function of which is integrated
with the SCC AS. The T-ADS queries the
subscriber database for the UE type and
access domain information and imple-
ments domain selection based on the car-
rier policies.
193/205
Reference Link
Description > Basic Call > Domain Selec-
tion Performed by the T-ADS in the
VoLTE product documentation.
Product Version
14.7 What Is SRVCC/

eSRVCC?
Question
What is SRVCC/eSRVCC?
Reply
Single radio voice call continuity
(SRVCC)/enhanced SRVCC (eSRVCC)
enables Long Term Evolution (LTE)
194/205
subscribers to continue their ongoing

calls when they move from an evolved
universal terrestrial radio access network
(E-UTRAN) to a UMTS terrestrial radio
access network (UTRAN) or GSM/EDGE
radio access network (GERAN).
An LTE network at the initial phase usu-
ally covers only hot spots and is limited
in continuous coverage. When a sub-
scriber in a call on an LTE network
moves out of the LTE coverage, the call
becomes disconnected. To address this
problem, SRVCC/eSRVCC is introduced.
SRVCC allows subscribers to continue an
ongoing call when roaming from an E-
UTRAN to a UTRAN or GERAN. SRVCC,
proposed by 3GPP, is aimed to resolve
the voice call continuity problem facing
subscribers at early LTE deployment
phase.
195/205
eSRVCC is introduced to shorten the

speech gap caused by SRVCC handovers.
In the eSRVCC network architecture, the
ATCF/ATGW is added between the
proxy-call session control function (P-
CSCF) and the I-CSCF/S-CSCF. If an
SRVCC handover is required, the media
session is anchored to the ATGW. Only
media information on the ATGW needs
to be updated when an SRVCC handover
occurs. Media information on the UE
does not need to be updated.
Reference Link
Description > SRVCC/eSRVCC in the
Product Version
196/205
14.8 What Is the

Difference Between
eSRVCC and SRVCC?
Question
What is the difference between eSRVCC
and SRVCC?
Reply
The difference between single radio voice
call continuity (SRVCC) and enhanced
SRVCC (eSRVCC) services is that the
eSRVCC service has decreased the han-
dover duration to 300 ms to reduce voice
interruption without changing the live
network architecture. A key challenge to
reducing handover duration is to control
the time that IMS spends establishing
new bearers. Figure 14-2 shows how the
197/205
eSRVCC service has shortened the new

bearer setup process by reducing the
message transmission path.
Figure 14-2 Comparison between eSRVCC
and SRVCC services
198/205
• SRVCC: The media handover point is a

peer device such as a peer UE. After
the local access network changes, the
local side must send the address of the
new bearer device to the peer device.
The peer device then updates bearer
addresses.
• eSRVCC: The media handover point is
an ATCF/ATGW (Huawei SBC) near
the local side. An ATCF/ATGW func-
tions as a media anchoring point and
forwards messages between the P-
CSCF and I-CSCF/S-CSCF regardless
of whether an eSRVCC handover oc-
curs. When an eSRVCC handover oc-
curs, only the bearer channel between
the UE and the ATGW needs to be es-
tablished. The original bearer channel
is reused to transmit media streams
between the peer device and the
ATGW.
199/205
Therefore, the message exchange path

for establishing a new bearer is shorter
than that in the SRVCC architecture,
cutting down the handover duration.
Reference Link
Description > SRVCC/eSRVCC in the
Product Version
200/205
14.9 In What Scenarios Is

the Anchoring Function
Needed?
Question
In what scenarios is the anchoring func-
tion needed?
Reply
In the voice over long term evolution
(VoLTE) solution, voice, video, and sup-
plementary services of VoLTE sub-
scribers are processed in the IMS net-
work. When a VoLTE subscriber roams
out of the LTE coverage or a 2G/3G sub-
scriber calls a VoLTE subscriber, the call
request must be routed to the IMS
network.
201/205
There are the following two scenarios of

routing:
• The VoLTE subscriber uses a number

in a new number segment.
For a new VoLTE subscriber whose
number is in a new number segment
planned by the carrier, the subscriber
number is distinguished from 2G/3G
numbers. Number analysis data can be
configured on the GMSC server or
MGCF so that calls of this subscriber
will be routed to the IMS network. In
this case, the anchoring function is not
needed.
• The VoLTE subscriber uses the origin-
al number upgraded from the 2G/3G
network.
As the VoLTE subscriber number is
not distinguished from 2G/3G num-
bers, the intelligent network (IN)
202/205
anchoring service must be provided for

this VoLTE subscriber. When this
subscriber's call request reaches the
GMSC server, IN anchoring is
triggered and the call request is sent to
the anchor AS. The anchor AS then as-
signs an IMS routing number (IMRN),
based on which the GMSC server or
MGCF routes the call to the IMS
network.
Reference Link
Description > Basic Call > Anchoring
Performed by the Anchor AS in the
Product Version
203/205
14.10 What Is the

IP-SM-GW?
Question
What is the IP-SM-GW?
Reply
The IP short message gateway (IP-SM-
GW) service enables short message deliv-
ery between IMS domains and circuit
switched (CS) domains.
The IP-SM-GW supports the following

types of short messages:
• Legacy CS short messages

• IP short messages in transport-level
interworking scenarios. The IP-SM-
GW includes a CS short message in a
MESSAGE message body as a relay
204/205
protocol data unit (RPDU) and trans-

mits it over an IP network.
Reference Link
Description > IP Short Message Gateway
in the VoLTE product documentation.
Product Version
@Created by PDF to ePub

Huawei 5671d79a0462d

Uploaded by

Copyright:

Available Formats

You might also like

Huawei 5671d79a0462d

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei 5671d79a0462d

Uploaded by

Copyright:

Available Formats

1 Library

1. For questions about product prin-

In addition, the IMS Product Document-

IMS Product • IMS V200R009C00 F

2.2 How Is the P-CSCF Discovered?

2.3 How Are S-CSCFs Assigned?

2.4 How Is the I-CSCF Discovered?

2.5 Why Is Registration Required?

2.6 Which Are Types of

2.7 What Are Home and Visited

2.8 What Is the IMS Session

2.9 What Are the Working Prin-

2.10 What Are IMS-Relevant Inter-

2.11 What Is a tel URI?

2.12 What Is a SIP URI?

2.13 Which Are types of tel

2.14 What Are the Relationships

2.15 What Is PSI?

2.16 What Is the SIP Structure?

2.17 Which Are Types of SIP

2.18 Is There Any Description

2.19 Where Can I Find the Informa-

2.1 What Is the

• The service layer consists of all types

provides services such as the game,

▪ If fixed networks access the IMS,

• The interworking layer interworks

layer helps to charge, address, manage

2.2 How Is the P-CSCF

The UE obtains the IP address of the P-

• The cable modem obtains the P-CSCF

• The IP address of the P-CSCF can be

2.3 How Are S-CSCFs

1. After receiving the REGISTER mes-

2. After receiving the UAR message, the

2.4 How Is the I-CSCF

2.5 Why Is Registration

Registration is the process in which sub-

• Bind their addresses and identities.

the subscription network connects the

2.6 Which Are Types of

Based on the entity used to initiate regis-

• Basic registration: It is initiated by

are in the same implicit registration

2.7 What Are Home and

and visited domain is the network where

2.8 What Is the IMS

reservation, application service session,

2.9 What Are the Working

• The DNS converts domain names to

2.10 What Are

2.11 What Is a tel URI?

2.12 What Is a SIP URI?

2.13 Which Are types of tel

The tel number can be a global number

• Global number: It starts with character

2.14 What Are the