(Basic Training) IMS Bearer Network ISSUE 5.0

Security Level:
IMS Bearer Network

ISSUE 5.0
www.huawei.com
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Objectives
 Upon completion of this course, you will be able to learn the
IMS bearer network in terms of:
 Overall architecture
 Networking modes
 Basic data configuration and network planning
 Typical networking applications
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Chapter 1 Networking of IMS Bearer Network
Chapter 2 Major Datacom Devices of IMS Bearer Network
Chapter 3 Interfaces and Protocols for Interconnection
Between IMS Devices and Bearer Network
Chapter 4 Data Configuration for Interconnection
Chapter 5 Interconnection Operation and Maintenance
Chapter 6 Troubleshooting of the Interconnection

Architecture of Huawei IMS solution
N2000 OMS2600 ENUM Server SPG2800 OCS9810 ICG9815

EMS OMC ENUM Server Web portal OCS CCF
UTRAN
EVDO
RM9000
PDF/PCRF
ATS9900
Telephony AS
CSC3300 HSS9820
WIMAX I-CSCF HSS
AIM6300 CSC3300
NACF P-CSCF
WIFI
CSE9600
AIM6300 CSC3300 VCC AS
CLF S-CSCF/MRFC
LAN/FTTX InfoX AAA

UAAF & PDBF
SoftX3000
AGCF
xDSL CSC3300 MRP6600 UGC3200

BGCF MRFP IM-SSF
SCP
RM9000 RM9000
RACF SPDF
CABLE
SE2300
A-BGF UGC3200 SG7000 UMG8900 CSC3300
MGCF SGW IM-MGW I-BCF 3nd party AS
TDM Access
AMG5000
AG
PSTN PLMN IP Network

Function Zones of Huawei IMS Solution
IMS solution network design
OSS/BSS/Billing zone Media zone Session control/service zone User access zone
Service Core Border Session (P-CSCF/A-BGF)

OM zone Billing zone Service zone Web Portal
provision zone media media control zone DHCP server
zone zone
Border Session access Portal access

CSCF
MRFP IM-MGW session zone
PLMN、PSTN IMS
user

Function Zones of Huawei IMS Solution
Session  It is the core signaling zone. The session control zone and media resource zone are deployed with the core NEs of the
Control Zone IMS network (including the CSCF, HSS, MRFC, MRFP, and ENUM). The NEs cannot be accessed by external users.
Media Zone  It is deployed with the MRFP media ports on the IMS network.
Service Zone  The service zone is deployed with the IMS service ASs, including the ATSs, SCPs, and other SIP ASs.
 The border zone includes the border session zone and border media zone.
Border Zone  The border zone is mainly deployed with the NEs (including the IBCF, MGCF, and IM-MGW) that are interconnected with
the networks of other telecom operators.
 The user access zone is oriented to the users. It is responsible for connecting the IMS network and other access networks.
Except the Web Portal, the CN devices that are visible for the users and the devices (such as the P-CSCF, CLF, NACF, A-
User Access
RACF, SPDF, PDF, and PCRF) that interact with the user access network are all deployed in the zone. In the user access
Zone
zone, you need to deploy independent switches to converge signaling interfaces in this zone, and deploy firewalls between
public network routers to ensure the IMS network security.
Service  The service provisioning zone is mainly deployed with service provisioning gateways. It is responsible for interconnecting
Provisioning the BOSS system and the NE database.
Zone
 The billing zone is mainly deployed with the CCF NEs. In this zone, original CDRs of each CN NEs are sorted then
Billing Zone submitted to the billing center.
Network  The network management zone is deployed with the OMS and EMS. It manages the physical devices and bearer
Management devices on the CN, and reports the information such as device states to the BOSS through the MDCN private network.
Zone

Overall Description of IMS Bearer
Network Construction
IMS devices
 The IMS bearer network consists of three parts:
IMS access network, backbone network, and
P-CSCF S/I-CSCF HSS MGCF UMG ENUM/DNS MMTEL
core network (CN). This presentation focuses
on the networking of the IMS CN. IMS CN
networking
 The networking of the IMS CN is mainly about
the external IP interface capability and IMS-CE1 IMS-CE2
networking design scheme of IMS devices. The
IMS
IMS service devices include session control backbone
network SBC
devices (such as the P/I/S-CSCF and IBCF),
bearer control devices (such as SPDF/PDF),
CMNET-CE1 CMNET-CE2 IMS backbone network
media gateway devices (such as the IM-
MGW/IBGF/A-BGF), and service application
devices (such as different types of ASs and
Portal Servers). The networking design FW1 FW2
IMS access IMS-CE1 IMS-CE2
includes the IP networking configuration of the network
IMS CN devices, and the VLAN, IP address,
VRRP, IGP routing protocols, security policies, Other IMS networks
and reliability configuration of the L2/L3 switch
related to the networking.

IMS CN Description
The objective of the IMS CN is to
connect and separate different function
zones in the IMS network. The general
Service Other operator
principles are as follows: network networks
Service
Border
Zone
Zone
1. Use LSWs or CEs to converge the IP
connections between all function zones in a Service Zone
Media Zone
local office, to enable the interworking of the
devices in the function zones.
2. Connect these LSWs or CEs to the IMS
User access
dedicated networks (public networks), to Zone
enable the interworking of offices. User access

network
3. Converge the user access traffic and forward
it to the access network.

Standard Networking of Commercial IMS
Offices
Portal access zone Media zone Border zone Service provision/billing/OM zone
C-Office BMS N2000
MRP660 UMG8900 UGC3200 Provisioning OMC
Web Portal 0 IM-MGW MGCF
MRFP iCG9815 MM-CBS
CCF OCS
CSC3300 Session cotrol zone

Session access zone Nominum I/S-CSCF,BGCF Service zone
DNS/ENUM HSS9820 ATS9900 Media-X
CSC3300 SoftX3000 HSS/SLF AS
P-CSCF AGCF
CSC3300
MRFC
L9 L10
L7 L8 L3 L4 L1 L2 L5 L6
User access zone Media acess zone Session control zone Service zone Border control zone
F7 F8 F3 F4 F1 F2 F5 F6
Control Flows
PE PE PE PE Access Flows
Access VPN Media VPN Control VPN Border Flows
Internet/ Public Other Packet Media Flows
PE
Network Network

Offices – Session Control Zone
 The session control zone and media zone contain the core NEs of the
IMS network (including the CSCF, HSS, MRFC, MRFP, and ENUM). The
two zones cannot be accessed by external users. Normally, the two
zones are configured with private network IP addresses.
 A pair of Layer-3 switches (L1/L2) to converge signaling messages in the

session control zone.

Offices – Media Zone
 For the media ports on the MRP6600 in the IMS network, it is recommended that you
use a group of Layer-3 switches (L3 and L4) to converge them, and then
interconnect them to the routers on the IMS backbone convergence layer through
GE ports. For the UMG8900 in the office, it is recommended that you connect its
media ports with routers on the IP bearer network through GE ports. If the UMG8900
provides an independent signaling port, the signaling port can be interconnected
directly with L1/L2 in the session control zone.
 Normally, you can use L3 switches (L1 and L2) to converge the media ports of the
MRP6600 and then interconnect the media ports with routes on the IMS backbone
convergence layer if the following conditions are met: (1) The telecom operator has
no special requirements, for example, the operator does not require media ports and
signaling ports to be separated. (2) The media zone is deployed with only one
MRP6600. (3) There is no NE that uses electrical ports to perform media
interconnection.

Office – User Access Zone
 The user access zone is oriented to the users. It is responsible for connecting the IMS network
and other access networks. Except the Web Portal, the CN devices that are visible for the users
and the devices (such as the P-CSCF, CLF, NACF, A-RACF, SPDF, PDF, and PCRF) that
interact with the user access network are all deployed in the zone. In the user access zone, you
need to deploy independent switches L7/L8 to converge signaling interfaces, and deploy firewalls
F3/F4 between L7/L8 and public network routers to ensure the IMS network security.
 If an office provides the Web Portal application, you need to set the user access zone and deploy
LSWs and firewalls to ensure the security of the AS and IMS core NEs. If the office is deployed
with access devices that are directly accessed by users (such as the P-CSCF, CLF, NACF, A-
RACF, SPDF, PDF, and PCRF) and Web Portal application, you can connect the Web Portal and
core NEs on the access network side through LSWs.
 In some cases, the IMS network is invisible to external users because full-proxy SBCs are
deployed on the user access side. The SBCs can isolate borders of networks, and therefore they
can prevent security risks brought about by the users. In an office, if all SBCs are in full-proxy
mode and the Web Portal is not configured, you can integrate the user access zone into the
session control zone.

Offices – Service Zone
 The service zone is mainly deployed with IMS service ASs, including the ASs,
SCPs, 3rd party applications, and other SIP ASs. The address domains of some
ASs, SCPs, and 3rd ASs may be different from the address domain of the IMS
Core. In addition, these ASs also need to provide Web Portal for user access. The
service ASs and NEs in the session control zone may be in different equipment
rooms. Normally, a pair of LSWs are used to converge signaling interfaces of the
service zone. The service zone and session control zone are interconnected
through the CEs.
 In special cases, if the service AS and session control zone are deployed in the
same equipment room, and the IP address domain on the CN side of the service
AS is the same as that of the session control zone, and the customer has no
special requirement on the service AS deployment, you can directly connect the
interface on the CN side of the service AS to the convergence switch of the
session control zone. In this way, the service zone is included in the session
control zone, and LSWs and firewalls are not required.

Offices – Border Zone
 The border zone includes border media zone and border session zone.
 The border zone is mainly deployed with the NEs (including the MGCF and IM-MGW) that are
interconnected with the networks of other telecom operators. For the interfaces of session control
devices in the border zone that are oriented to the peer IP bearer network, if the peer IP bearer
network is different from the address domain of the session control zone, you need to implement the
interconnection of the two address domains through border interconnection NEs.
 If the routers on the peer IP bearer network and the interconnection devices of border zone are
deployed in different equipment rooms (or the routers do not provide GE electrical ports), you need to
deploy the switches L9/L10 to converge the interconnection signaling messages and connecting the
routers on the peer IP bearer network in parallel mode.
 Based on the telecom operator requirements, you can deploy a firewall between the interconnection
NE and the peer IP bearer network to ensure the service security of live network. Normally, it is
recommended not to deploy a firewall between the interconnection NE and the peer IP bearer
network. If the firewall is deployed, you must also deploy L9/L10.
 If the routers of the peer IP bearer network are in the same equipment room as the border zone and
provides GE electrical ports, you can directly connect the interconnection NE to the peer IP bearer
network.
 If the IMS network is interconnected with the peer network through the TDM and the L9/L10 are not
deployed, the border zone is integrated in the session control zone.

Standard Networking of Commercial IMS Offices – Billing Zone,
Network Management Zone, and Service Provisioning Zone
 Service provisioning network
 The service provisioning interface is connected to the existing service
provisioning network through a pair of Layer-3 switches and then
connected to the BOSS over the MDCN private network.
 Billing network
 The billing interface is connected to the existing billing network through a
pair of Layer-3 switches and then connected to the BOSS over the MDCN
private network.
 NM networking
 The NM interface is connected to the existing network management
network through a pair of Layer-3 switches and then connected to the
BOSS over the MDCN private network.

Networking Example – IMS Network of
China Mobile
 Actual IP networking requirements of China Mobile:
 1. Use the CE to converge signaling and media.
 2. Use the SBC as the IMS signaling and media proxy.
 Based on the preceding requirements:

 1. The firewall must be configured before the CN.
 2. The CE must be configured with VLAN division to distinguish signaling
and media.
 In the standard networking of commercial IMS offices, how to route the

interconnection signaling and media streams of the IMS and CS?

IMS Network of China Mobile
IP core
CMNET network
AR AR
Access zone
FW
Session/media/service zone Border zone
FW
CE1 CE2 CE3 CE4
CEA CEB
OLT SBC SBC
Splitter
Local IMS CCF MRFC MRFP MGW MGCF HSS DNS/ENUM S/I-CSCF P-CSCF
user access NEs of core network
MTU

question
 In the Standard Networking of Commercial IMS Offices, what’s the
route of the signals and media of the traffic between IMS and CS
users?


IMS solution network devices － Datacom
Devices
Eudemon1000E:
S5328：

Function Allocation of Datacom Devices
Function Allocation of Datacom Devices on CN Side
Device Switch Firewall
Configuration
Model and Standalone Model and Standalone
Function Configuration Principle Configuration Principle
Number Configuration Number Configuration
Classification
L1/L2 : 2 x S5328.
If there are 23 x 100 M/1000 Optional when the telecom operator
Session insufficient ports, M electrical port, requires to use its own bearer devices as
Mandatory
Control Zone you can set an 1 x GE optical signaling interconnection devices;
additional pair of port Mandatory in other cases
ports.
By default, it is not required.
It is required if the following conditions are met:
1. The service AS and session control zone
are deployed in the same equipment room.
2. The IP address domain of the interface on
1 x 4 GE optical-
CN side of the service AS is the same as Mandatory when the telecom operator
Service 23 x 100 M/1000 F1/F2 : 2 x electrical exclusive
that of the session control zone. requires that the service AS be deployed
Application L5/L6 : 2 x S5328 M electrical port, Eudemon port, 1 x 2 GE
3. The telecom operator does not require the with firewall;
Zone 1 GE optical port 1000E optical-electrical
firewall for the service AS deployment. The Not required by default
exclusive port
service ASs include the ATS9900,
MediaX3600, and ETAS9960, and exclude
the third-party service AS and service
software AS (which require independent
switch and firewall).
By default, it is not required. It is required if the following conditions are
It is required if the following conditions are met: met :
1. The full-proxy SBCs are used to access the VoBB 1. The full-proxy SBCs are used to access the 1 x 4 GE optical-
users or only the SIP AG is interconnected. 23 x 100 M/1000 VoBB users or only the SIP AG is
electrical exclusive
User Access 2. There is no Web Portal application. M electrical F3/F4 : 2 interconnected.
L7/L8 : 2 x S5328 3. The IMS CN NEs are not configured with public
port, 1 x 2 GE
Zone port,1 GE optical Eudemon1000E 2. There is no Web Portal application.
network IP addresses. 3. The IMS CN NEs are not configured with optical-electrical
port
If the preceding conditions are not met, public network IP addresses. exclusive port
configure a pair of switches and a pair of If the preceding conditions are not met,
firewalls. configure a pair of switches and a pair of
firewalls.

Function Allocation of Data Communication
Devices (Continued)
Function Allocation of Data Communication Devices at CN Side
Device Switch Firewall
Configuration
Standalone Model and Standalone
Function Model and Number Configuration Principle Configuration Principle
Configuration Number Configuration
Classification
By default, it is not required. 1 x 4 GE
It is required if the following conditions are met : optical-electrical
23 100/1000 M By default, it is not required.
1. The CE router and interconnection NE in the border F5/F6:2 exclusive port,
Border Zone L9/L10: 2 x S5328 electrical port, 1 It is required when the
zone can be directly connected through electrical port Eudemon1000E 1 x 2 GE
GE optical port customer needs it.
(you need to consider the CE deployment position and optical-electrical
port capability). exclusive port
It is required if the following conditions are met :
1. The IMS central office is configured with only one
23 100/1000 M
Media Interface MRS6600. Except the MRS6600, no NE (excluding the
L3/L4: 2 x S5328 electrical port, 1
Zone UMG) provides a GE electrical media port.
GE optical port
2. The customer does not require that the media port and
signaling port be separately connected to the upper-
level router.
Active/Standby 1 x 8FE
23 100/1000 M
SE2300 electrical port, 2
L23/L24: 2 x S5328 Optional electrical port, 1 2 SE2300
Networking x 2GE optical/
GE optical port
(Access Side) electrical port
IMS Service By default, it is
Device OSS recommended not to
Interface Zone configure firewall for the
Billing Interface 23 100/1000 M maintenance network. If the
Zone L17/L18:2 x S5328 Mandatory electrical port, 1 firewall is required, it is
GE optical port recommended that the
BSS Interface customer provide the
Zone firewall. When necessary,
you can provide two E500s.
16 x FE
LMT Zone L19: S2016 Mandatory
electrical port

IMS solution network devices –IMS
backboards

IMS solution network devices –IMS
backboards
后插板类型定义
Hardware
name type ports Net element
version
R2(T8261) USI1 4GE Slot of GE port board, up to down:J2,J3 GE port：BACK5,BACK6,BACK7,BACK8 all
R2(T8261) USI2 4GE+2FC Slot of GE port board, up to down:J2,J3 GE port ：BACK5,BACK6,BACK7,BACK8 MediaX,CCF,OSG
R2(T8261) USI3 2GE+4FC Slot of GE port board, up to down:J3 GE port：BACK7,BACK8 USCDB array
Slot of GE port board, up to GE port：

R2(T8261) USI7 6GE OMS
down:J1,J2,J3 BACK3,BACK4,BACK5,BACK6,BACK7,BACK8
R3(T8280) USIA1 4GE Slot of GE port board, up to down:J2,J3 GE port：BACK5,BACK6,BACK7,BACK8 All ,hot plug
Slot of GE port board, up to GE port：

R3(T8280) USIA7 6GE OMS，hot plug
down:J1,J2,J3 BACK3,BACK4,BACK5,BACK6,BACK7,BACK8
GE port：
R2(T8261) SWI0 8GE Base：LAN0～LAN3 Connecting of the
Fabric：LAN0～LAN3 subracks
GE port：
R3(T8280) SWIA0 16GE Base：LAN0～LAN7 Connecting of the
Fabric：LAN0～LAN7 subracks
SDM 1FE port：LAN

SMU board for NM
4FE/GE(el
NIU NIU0 Position is fixed GE port：BACK1,BACK2,BACK3,BACK4 MPF backboard
ectrical)

Devices in IMS Solution – SBC
Session Border Controller (SBC):
1. SBCs are used to ensure VoIP security SBC: SE2600 layout:
and continual communication and to
provide multimedia services. They are
border routers installed at the edge access
layer.
2. HUAWEI SessionEngine2300 (SE2300)
and SessionEngine2600 (SE2600) are the
SBCs independently developed by Huawei.
3. The SE2300 features small capacity,
whereas the SE2600 features large
capacity.
SBC: SE2300 layout:

Devices in IMS Solution – SBC
The SBC supports multiple proxy modes, including:
 Full-proxy mode: The SBC serves as the proxy of the user signaling and media. For the P-CSCF, the
SBC on network side is a user terminal. For the terminal, the SBC is the P-CSCF. In this mode, you
can use the SBC to separate the address of access network from that of the IMS CN. The SBC plays
the function of a firewall. This mode is a commonly-used mode at present.
 Signaling proxy mode: The SBC serves as the proxy of signaling only. The media stream is not
transmitted through the SBC.
 Transparent proxy mode: The server address of the terminal is the P-CSCF. Through networking
configuration, the SIP packets of the terminal are transmitted through the SBC downlink port. For the
terminal, the SBC is “transparent” and “invisible”.
 The logical functions of the SE2300 and SE2600 are the same on the network. The SBC has
two networking modes: direct connection mode and side mounted mode.
 The SBC can be mounted to the side a LanSwitch or router. The major advantage of the
networking mode is as follows: The SBC processes only the IMS service. The other services
can be directly forwarded without the SBC. Therefore, the SBC will not become a bottleneck of
transmission.
 If you can ensure that only signaling and media traffics pass the the SBC, the SBC can be
configured in direct connection mode.
 In the China Mobile project, the full-proxy SBC uses the direct connection mode.

Devices in IMS Solution－SBC
 The logic functions of SE2300 and SE2600 are the same. there are two
modes of application of SBC: bypass mode and full agent mode.
 For the bypass mode , the SBC is located beside the LSW, the benefit of
this mode is that: only the IMS services go through the SBC.
IMS Core
SIP SoftPhone
Bearing network
Local IP network
SE2600
SIP SoftPhone
Local IP network GE links
Bearing network GE links

Devices in IMS Solution－SBC
 If it is comfirmed that only signals and media go through the SBC , the
SBC can be applied with full agent mode.
 In the china mobile project, the SBCs are applied with all agent mode.
IMS Core
SIP SoftPhone
Bearing network
Local IP network
SE2600
Local IP network GE links

SIP SoftPhone
Bearing network GE links


Networking Technology – VRRP
 VRRP is a protocol for error tolerance. It is designed for
the LAN supporting multicast and broadcast (such as the IMS Network
Ethernet). It ensures that when next hop router of the AR1 AR2
host in the LAN is faulty, another router can replace the
faulty one. By using the preceding method, continuity
R R
and reliability of the communication are ensured. To
enable the VRRP, you need to configure the virtual
router number and virtual IP address on the router. In
addition, a virtual MAC address is generated. Therefore,
a virtual router is added to the network. The hosts on the VRRP
IMS CE1 IMS CE2
network can communicate with the virtual router and do
not require any information pertaining to the physical router
on the network. A virtual router consists of an active
router and multiple standby routers. The active router
implements the actual forwarding function. When the
active router is faulty, a standby router takes over the
traffic and becomes the active router. S/I-CSCF MRFC MGCF HSS P-CSCF AS
 As shown in the figure on the right, the IMS CE1 and
Core Equipment Room
IMS CE2 form a virtual router. For the IMS devices, there
is only one router, and the peer router is the virtual
router.

Networking Technology – VLAN
 The traditional LAN uses a HUB, which has only one bus that represents a collision domain. Therefore, the traditional
LAN is a flat network. A LAN refers to a collision domain. The packets sent by any host can be received by other hosts
in the same collision domain. Later on, a bridge (Layer-2 switch) is used to replace the HUB in networking. Each port of
the bridge can be considered as a separate bus. The collision domain refers to each port. Therefore, the efficiency of
the networking for sending unicast packets is improved considerably, and the Layer-2 network performance is
enhanced substantially. All ports on the network, however, still belong to one broadcast domain. When forwarding
broadcast packets, the bridge still makes multiple copies of the broadcast packets, and then sends the packets to each
corner of the network. To improve the network efficiency and prevent broadcast storm, the network is usually divided
into several segments, that is, a large broadcast domain is divided into several small broadcast domains.
 Virtual Local Area Network (VLAN) logically divides
the network resources and users based on a certain
principle. In this way, a physical network is divided VRRP
into multiple small logical networks. These logical IMS CE1 IMS CE2
networks represent different broadcast domains, that
is, different VLANs. As shown in the figure on the right,
different domains use the same central switch, but
each domain belongs to a specific VLAN, that is, a
specific broadcast domain. The broadcast packets
cannot be transmitted between different broadcast
domains.
 VLAN logically classifies the users in different S/I-CSCF MRFC MGCF HSS P-CSCF AS
physical network segments into the same LAN. The Access
functions and operations of VLAN are basically the Core Signaling VLAN VLAN AS VLAN
same as those of traditional LAN. VLAN can
interconnect terminal systems within a certain range.

Networking Technology – VLAN (Continued)
VLAN division principles:
1. One VLAN is specified for the core signaling.
2. One VLAN is specified for the media.
3. One VLAN is specified for the interconnection on the access side.
4. It is recommended that you specify a VLAN for the AS signaling.
5. It is recommended that you specify separate VLANs for the billing, NM, interception, and service provisioning.
6. Separate VLANs are specified for the Layer-3 forwarding and bearer interconnection configuration on the LSW.
Based on the preceding principles, you can combine the VLANs according to on-site conditions to reduce the
networking complexity.
 If the signaling network of the customer is a network that can ensure the reliability of signaling networking and the
interconnection of different service zones, you can combine some or all of the core signaling VLAN, access
signaling VLAN, interconnection VLAN, and AS signaling VLAN to simplify the network structure.
 The billing, NM, interception, and service provisioning are usually in independent VPNs or VLANs at the
customer side. If the customer have special requirements, you can combine some or all of the billing VLAN, NM
VLAN, and service provisioning VLAN. The security for interception VLAN is relatively higher. It is recommended
that you configure the interception VLAN independently, except that the customer requires the interception VLAN
to be combined with other VLANs.
 After the VLANs are combined, you can combine the switches of the VLANs. The IP addresses are planed in the
same subnet. Some NEs need to provide two physical network ports for connecting two VLANs, but after the
VLANs are combined, these NEs can reduce the connections of physical network port and reduce the IP
addresses. The network bandwidth, however, must meet the requirements of services (PCSCF access and CN
signaling cannot be combined).

Networking Technology - OSPF
IMS network
AR1 AR2
 OSPF (Open Shortest Path First) is used
for the IP routing on IP network. R R
OSPF
VRRP
IMS CE1 IMS CE2
S/I-CSCF MRFC MGCF HSS P-CSCF AS
Core signal VLAN Access AS VLAN

VLAN

Networking Technology – Ports of Core Devices
IMS CE
 The Open Shortest Path First (OSPF) protocol
is used to identify and calculate routes on the
computer network. On the IP network, the
protocol can dynamically identify and
propagate routes by collecting and transmitting
the link state in the autonomous system. Core Device Subrack
 The IMS core devices support the ip1 ip1

active/standby mode of signaling service port,
that is, each IMS device is configured with
active and standby external interface boards.
The two interface boards use the same IP
Interface Interface
address. When the active interface is faulty, the board 1 board 2
traffic is switched over to the standby interface.
Therefore, the network reliability is improved.

Networking Technology – Ports on the Router
 A group of Layer-3 switches interconnected with the signaling IMS CE1 IMS CE2
service port can form a VRRP backup group. In addition, the
active VRRP device can be configured to trace and monitor
the uplink physical port. Once the active VRRP device is
faulty or the uplink port of the active VRRP device is faulty, VRRP
the standby VRRP device promptly becomes the active one.
 For each VRRP backup group, at least two links are

Core Device
configured between each pair of Layer-3 switches as the link
redundancy configuration. Therefore, if a link is faulty, the
traffic is not affected. Moreover, multiple links are bound ip1 ip1
together to prevent the problem of “link loopback”.
Note: If the Layer-3 switch is configured with two or more

interface boards, it is recommended that you allocate the
interconnection links on different interface boards. Thus, the
reliability of link backup is improved.
Interface Interface
board 1 board 1

General Principle of IMS Bearer
Network Construction
 1. Prepare an IMS device list of each office based on the office construction
requirements of the customer.
 2. Classify the IMS device lists based on the IMS network areas separation.
 3. Choose datacom devices based on the traffic of each port calculated through
the user call model.
 4. Set up physical connections between the IMS devices and datacom devices

Networking Technology – Traffic Calculation
Diagram of the signaling bandwidth
logical interface:
HSS
Sh
Cx SIP AS
ISC Signaling bandwidth design
S-CSCF
(1) Traffic on the ISC port (Mbit/s)
Mw
= Total number of users x Number of BHSA
I-CSCF per user / 3600 x (Number of ISC
interface messages per session + Number
of CxDx interface messages per session)
x Length of each SIP message x 8
User quantity and traffic model
(bit/byte) / 1024 / 1024
Parameter Value =5000000 x 2/3600 x (14 x 2 + 1) x 1.5K x
Number of users who use the service 5,000,000
8/1024/1024
=921.9 Mbit/s
Number of messages on the ISC port in 14 x 2
each call (triggering the AS twice)
Number of C x D x message in each call 1
Number of calls per user in busy hours 2
Average size of message 1.5 KByte

Networking Technology – Switch Model
Selection Principles
 The switches implement the convergence, interconnection, and separation of traffic,
and provide reliable IP access and convergence of traffics, which are the same in
all aspects (such as signaling, media, and OM). To select a switch model, you
need to consider the switch cost, port capacity of the switch, actual data traffic of
users on the network, and quantity of office devices. The general principles for
selecting the switch model are as follows:
 The access of signaling NEs to the IP bearer network uses the 5624P.
 The access of media NEs to the IP bearer network uses the 5328P if the device
provides the FE port, or uses the 5624P if the device provides the GE port.
 In principle, the access of OM NEs to the IP bearer network uses the 5328P
(because Huawei OMU provides the GE port). On most networks, however, the
OM data traffic is small. To save costs, the 5328P can be used in this scenario.
 The SBC downlink port uses the 5328P.

Interconnection Between IMS Device
and Bearer Network – Signaling Zone
BFD for VRRP
IMS CE1 IMS CE2
The port is set to Access VRRP

mode. The uplink packets
are configured with VLAN ARP
tags based on CN Detection
requirements.
S/I-CSCF MRFC MGCF HSS P-CSCF AS

Access AS service
Core signaling zone control zone zone
 Each of the related CN signaling gateways provides a pair of 1000 M electrical ports in
uplink to the CE1 and CE2. The active and standby ports share one IP address. Both the
active and standby ports are set to UP. The uplink packet does not contain a VLAN tag.
 The ARP detection is configured between the CE and all devices on the signaling plane to
prevent single-link fault.

Interconnection Between IMS Device
and Bearer Network – Media Zone
IMS CE1 IMS CE2
ARP BFD
detection detection
MRFP MGW
Media Zone
The MRFP access mode is the same as that of the The MGW uses load-sharing
IMS signaling NE, both of which use active/standby mode in the uplink to the CE1
mode in uplink. The CE is configured with the VRRP and CE2. The uplink packets
to provide the gateway. contain VLAN tags.

Interconnection Between IMS CE and
IP Private Network AR
Deliver the service address
segment in the MBGP, and
AR1 AR2
R R deliver the default route to the
CE through the OSPF.
Bind the IMS

media and
signaling VPN on The OSPF multiple
the sub-interface. instances exchange the
VPN routing information.
IMS CE1 IMS CE2

Use the static black hole route
on the CE to converge the
BFD for trunk service addresses. Introduce it
Signaling sub-interface to the OSPF multiple instances,
and control it through the
Media sub-interface routing policies.
Eth-trunk

Interconnection Between IMS CEs
Bind the IMS media
and signaling VPN on Deliver the
the Eth-trunk sub- interconnection address
interface. segment in the OSPF.
IMS CE1 IMS CE2

VRRP heartbeat packets
Eth-trunk

Firewall (Edumen1000E) Configuration
CMNET CE1 CMNET CE2
OSPF
The firewall adopts two-node
cluster hot backup. The backup
forwarding is enabled. The
downlink and uplink adopts L2
transparent transmission.
Link-group Link-group
HRP
Traffic load is shared in

the uplink.
Access Network
Eth-trunk


Data configuration-OSPF
 # configure RouterA。
 [RouterA] router id 1.1.1.1
 [RouterA] ospf
 [RouterA-ospf-1] area 0
 [RouterA-ospf-1-area-0.0.0.0] network 192.168.0.0 0.0.0.255
 [RouterA-ospf-1-area-0.0.0.0] quit
 [RouterA-ospf-1] area 1
 [RouterA-ospf-1-area-0.0.0.1] network 192.168.1.0 0.0.0.255
 [RouterA-ospf-1-area-0.0.0.1] quit

Data configuration-VLAN
 # create VLAN2。
 [Router] vlan 2
 # add VLAN2 to GE1/0/0 and GE2/0/0
 [Router-vlan2] port gigabitethernet 1/0/0 2/0/0
 [Router-vlan2] quit
 # configure the VLANIF
 [Router] interface vlanif 2
 [Router-Vlanif2] ip address 120.1.1.1 24
 [Router-Vlanif2] quit

Relevant Technology – VLAN Separation Suggestions
Rang LAN-
Zone VLAN VLAN Description LANswitch Description
e Switch
The 110# VLAN interconnects the signaling ports in the session
Session In a new project, the L1/L2 must be configured. In project expansion, if the
100#~ control zone (such as the CSCF, HSS, MRC, and DNS/ENUM; if
control L1/L2 110# L1/L2 is already configured and the port meet the requirements on expansion,
199# the AS is not configured with independent service LANswitch, it
zone you need not configure it again.
can also be connected to 110# VLAN.)
By default, it is not necessary to configure independent switch in the service
zone. The switch is configured when the following conditions are not met:
1. The service AS and session control zone are deployed in the same
equipment room.
The 210# VLAN is deployed with the service AS. If the customer 2. The IP address domain on CN side of the service AS is the same as that of
Service
200#~ has special requirements, you can deliver L5/L6. The 210# VLAN the session control zone.
application L5/L6 210#
299# is separated from other VLANs. Otherwise, it is combined into 3. The telecom operator has no requirement for deploying firewall for the
zone
110# VLAN. service AS.
The Service ASs include the ATS9900, MediaX3600, and ETAS9960, and
exclude the third-party service AS and service software AS. The third-party
service AS and service software AS must be configured with independent
switches and firewalls. It is not recommended that you connect the L5/L6.
The 310# VLAN provides the interface oriented to the access side By default, it is not necessary to configure independent switch in the user
310# of the NEs with core session control signaling and access side access zone. The switch is configured when the following conditions are not
User signaling, such as the P-CSCF and NACF. met:
300#~
access L7/L8 1. The full-proxy SBC are used to access the VoBB users or only the SIP AG
399#
zone The 320# VLAN provides the NE interfaces for accessing the is interconnected.
320# 2. There is no Web Portal application.
Internet.
3. The IMS CN NEs are not configured with public network IP addresses.
By default, it is not necessary to configure independent switch in the media
The 410# VLAN provides media interfaces oriented to the internal zone. The switch is configured when the following conditions are not met:
Media 400#~ NEs. The media stream for interception function copying is also 1. The IMS central office is configured with only a MRS6600. Except the
L3/L4 410#
zone 499# accessed to 410# VLAN. In an office, if the MRP provides only one MRS6600, no NE (excluding the UMG) provides the GE electrical media port.
media port, the VLAN must be deployed on the L1/L2. 2. The customer does not require that the media port and signaling port be
separately connected to the upper-level router.
The 510# VLAN provides the signaling IP ports for devices in the
border zone for connecting the networks of other telecom
operators. If the telecom operator has no requirement for By default, it is not necessary to configure independent switch in the border
510# separating its network from other VoIP networks, the zone (UGC3200 and I-BCF). The switch is configured when the following
Border 500#~ interconnection can be implemented through the bearer network. It conditions are not met:
L7/L8 is recommended that you directly use the 110# VLAN on the L1/L2
zone 599# 1. The CE router and interconnection NE of the border zone can be directly
to realize border interconnection. connected through electrical port. (You need to consider the CE deployment
It is the interception VLAN. It is recommended that you position and port capability.)
520# independently separate the VLAN. If the switch is not configured, it
is recommended that you use the OM switch (L17/L18).
The 740# VLAN provides the IMS service device OSS interfaces. It
740# In a new project, the L17/L18 must be configured. In project expansion, if the
is a VLAN dedicated for data backup, data restoration, and LMT.
700#~ L17/L18 is already configured, you need not configure it again.
OM/Billing L17/L18 750# Billing interface zone
799# If the OSS, billing system, and BSS are deployed in the same network
segment, it is recommended that you deploy them in the same VLAN.
760# BSS interface zone

Relevant Technology – IP Planning Principles
 Normally, it is recommended that you plan the IP addresses based on the
following four service types: global interconnection address, signaling IP address
(IMS device address and interconnection address of data communication device),
media IP address (IMS device address and interconnection address of data
communication device), NM IP address (IMS device NM address and NM address
of data communication device). The IP address segments of each service type are
continuous. This mode facilitates the MPLS-VPN deployment and IP address
convergence in the VPN.
 Based on the IP address configuration principles in the IMS office, the IP
addresses are generally classified into the following three types:
 1. Public network IP address: It is the IP address that can be accessed by terminal
users through the Internet.
 2. Large network IP address: It is the IP address on the internal IP bearer network
or OM billing network of the telecom operator.
 3. Private network IP address: It is the internal IP address that is configured on the
network devices and can be routed in the IMS CN.

Relevant Technology – IP Planning Principles (Continued)
IP Address Planning Requirements Table
Zone IP Address Quantity IP Address Type Remarks
It is planned based on the service requirements.
Media zone Large network
Generally, 2/3 IP addresses are reserved.
Service signaling It is planned based on the service requirements.
Large network
stream Generally, 2/3 IP addresses are reserved.
Signaling stream Large network
In full-proxy mode, the address of P is invisible and is usually a large network address. In
It is planned based on the service requirements. Public network / MediaCom mode, the address of P is visible to users and is usually a public network
Access
Generally, 2/3 IP addresses are reserved. Large network address. The interfaces of the NEs such as the AIM and RM9000 at the user side use
public network addresses.
The public network address may be used for interconnecting with the networks of other
It is planned based on the service requirements. Public network /
Interconnection telecom operators. The large network address is used for interconnecting with other
Generally, 2/3 IP addresses are reserved. Large network
internal networks of the same telecom operator.
It is the IMS entry address visible on the user terminal. In full-proxy mode, it is the
User SIP Public network interface on the user side of the SBC. In MediaCom mode, it is the interface on the user
side of the P-CSCF.
User HTTP It is planned based on the service requirements. The user access interface of the WebPortal usually uses public network address or large
Public network
(Internet) Generally, 2/3 IP addresses are reserved. network address. It is performed with NAT through the firewall.
OSS Large network (DCN)
Billing Large network (DCN)
Service It is planned based on the service requirements.
Large network (DCN)
provisioning Generally, 2/3 IP addresses are reserved.
It is planned based on the service requirements. The IP address of the interception interface must be interconnected with the peer LIG.
Interception Large network
Generally, 2/3 IP addresses are reserved. Generally, the IP address domain of the peer LIG is used.
Note:
1. Some areas can share the same pair of switches. Normally, the IP address planning is unchanged.
2. In special cases, if you confirm that the devices in the zones to be combined are of the same nature, you can consider the IP address planning for these devices together. For example, the ATS and Mediax signaling
can be consolidated into the signaling part and be planned together.
3. If the telecom operator has no special requirements on the separation of the maintenance, billing, and service provisioning, you can determine that the three flows are the same in all aspects, and the IP address
planning can be performed in the OSS service zone.

Interconnection Configuration Between
the IMS Device and Bearer Network
 1. To configure the active/standby mode of the signaling service port on the IMS core device, run the following
command lines:
 (Take the UGC3200 as an example to illustrate the command execution on the corresponding NE.)
 ADD MODULE: MID=1500, MT=IFM, SUBRN1=0, SN1=0, SUBRN2=0, SN2=1, MNAME="IFM";
 ADD IPADDR: IPNAME="IP", DPUMID=1500, PORTID=BACK7, IPVER=IPV4, IP4="10.10.10.10",
NETMASK="255.255.0.0", DEFAULTGW4="10.10.10.0", DETECT=ARP, RFC=OPEN, LFC=OPEN;
 2. One pair of Layer-3 switches on which the service ports of signaling and media devices converge enable the VRRP
backup group as the redundancy configuration as follows:
 Create the backup group 10. Set the priority level of Router A in backup group 10 to 160 and set the state of Router A
to Master.
 [RouterA] interface gigabitethernet 2/0/0
 [RouterA-GigabitEthernet2/0/0] vrrp vrid 10 virtual-ip 10.1.1.3
 [RouterA-GigabitEthernet2/0/0] vrrp vrid 10 priority 160
 [RouterA-GigabitEthernet2/0/0] quit
 # Create the backup group 10. Set the priority level of Router B in backup group 10 to 140 and set the state of Router B
to Backup.
 [RouterB] interface gigabitethernet2/0/0
 [RouterB-GigabitEthernet2/0/0] vrrp vrid 10 virtual-ip 10.1.1.3
 [RouterB-GigabitEthernet2/0/0] vrrp vrid 10 priority 140
 3. Enable the ARP detection on the VLAN configured on the switch.

 [Quidway-vlan1] arp detection enable


Interconnection OM Between the IMS
Device and Bearer Network
 The network consists of multiple devices that are distributed
across different places. To facilitate device maintenance, an
NM center is established on the network. The maintenance
personnel can maintain the devices through the NM center.
 To implement the preceding function, you need to configure the

Telnet login mode on the router. To ensure security, the local
user must be authenticated during the login.

Interconnection OM Between the IMS
Device and Bearer Network
 User management:
 By default, any person can configure the router through the Console port. In actual application, however,
not all users are allowed to modify the router settings. Therefore, the authorities are allocated as follows:
 Visiting level: The users only have the right to use network diagnosis commands (tracert and ping) and
terminal service commands (telnet and SSH).
 Monitoring level: Based on the visiting level, the system maintenance command (display) and fault
diagnosis command (debugging) are added.
 Configuration level: Based on the monitoring level, the service configuration commands are added.
 Management level: Based on the configuration level, the system management commands and file
management commands are added.
 To allocate the authorities according to the preceding principle, you need to create one or more users in
each level. The users are classified into four levels. Level 0 corresponds to the visiting level, level 1
corresponds to the monitoring level, level 2 corresponds to the configuration level, and level 3 corresponds
to the management level.
 When you need to configure the router, you can log in to the router as a corresponding user, and then
perform the corresponding configuration. For example, to set the VPN service on the router, you need to
log in as the user at the level not lower than 2.
 Configuration example:
 # Create the user user4 with password user4. The password is encrypted, and the user level is 3.
 [Quidway-aaa] local-user user4 password cipher user4
 [Quidway-aaa] local-user user4 level 3
 [Quidway-aaa] quit
 [Quidway] quit

NM System
 With the rapid development of data communication technologies, new services are
emerging endlessly. The network scale becomes greater, and the technologies
become more complex. The management, maintenance, and optimization of the
networks become increasingly difficult. For a network with dozens of routers and
hundreds of links, it is impractical to check the device states and link states through
the display command on the router, especially in the developed countries with high
labor costs. Therefore, it is necessary to deploy a centralized and unified NM system.
 The NM system can be used to quickly locate network faults, analyze network
performance, settle network bottlenecks, and improve response speed of service
requirements. The iManager N2000 DMS (Datacomm network Management System)
can uniformly manage the datacom devices such as Huawei routers, switches,
service gateways, security gateways, voice gateways, and WLANs.

Architecture of NM network
Carrier NMS /OSS Center
OSS/BSS/Billing Network for IMS Service
VPN Client
PE DDN Router
OAM VPN Control VPN DDN Carrier Billing/
外网 Media VPN Access VPN Provisioning Center
IMS Office at Center F10 OAM VPN layer 3 port

VPN Server
L19 NAT Edumon500 NM layer 3 port
billing/service provision layer 3 port
IMS converge service layer 3 port
本地客户端 OSPF Media-X layer 3
S3528G
L17 S
S S L18
F1 F2
OCS
F3 F4
iCG9815
OMU2600
SE2300
BMS
Layer 3 port I2000 N2000 UMG8900
iGWB BAM MRS6200
for NM /M2000


Troubleshooting Principle
Start
 If a fault occurs on the IP bearer
network, you need to collect the fault
Collect fault
information
information, and then perform
troubleshooting according to the
Troubleshoot cable
sequence of “cable fault  board fault fault
 data configuration error”.

Troubleshoot board
fault
Troubleshoot the
fault caused by data
configuration error

Troubleshooting – Emergency Method
 Use the Ping function in the IP tracing task of the LMT, and send the Ping packets to the destination. If the
connection to destination network is normal, after the destination host receives the Ping packets, it sends the
Ping response packets to the source host. The Ping command outputs the responses of each Ping packet as
follows:
 1) Before the timeout, if the response packet is received, the bytes number, packet sequence number, TTL,
and response time are displayed.
 2) Before the timeout, if the response packet is not received, the “Requested time out” information is
displayed.
 The final statistics information includes the number of sent packets, number of received response packets,
percentage of non-responded packets, and minimum, maximum, and average response time.
 Note: You need to confirm which addresses can be pinged. For example, public network address usually
cannot be pinged due to isolation function of the firewall.
 When running the Ping command, you need to pay attention to the following:
 If the network transmission speed is slow, you can timeout wait time for the response.
 In the Telnet mode, you can press CTRL+C to pause the Ping command.
 Each board supports five Ping operations simultaneously.
 The Ping operation means to send Ping packets to the destination through the network port of the board with
IP interface, and then analyze whether the connection to the destination network is normal.
 When you find out in the Ping test that the network connection is faulty, you can use TRACERT to locate the
fault. Run the TRACERT operation in the IP tracing task of the LMT, and then locate the IP address of the
faulty router on the bearer network.
 Use specific instruments or software to test the transmission delay, BER, packet loss ratio, and jitter
parameter of the transmission network. Check whether there is network congestion, network storm, or virus
attack on the network.
Troubleshooting – Information Collection
 To check whether the IP bearer network is normal, you need to collect the following information:
Whether the Browse Alarms window displays alarms related to bearer network faults, whether
the board running state is normal, whether the negotiated interconnection parameters are
consistent, whether the cables or function modules are loose, and whether the fault is caused
by data communication devices.
 1. Check the alarm information: Log in to the LMT and choose Alarm > Browse Alarms. Right-
click on the displayed alarm information window. Choose Save As... to export the alarm
information.
 2. Check the alarm log information: Log in to the LMT and choose Alarm > Query Alarm Log.
On the displayed Query Alarm Log dialog box, set Alarm Cleared Flag, Alarm Severity, and
Alarm Time to be queried. Click OK.
 3. Check the board running state: On the navigation tree on the left side of the client, click
Device Panel to display the device management view. Double-click different cabinet names,
and then you can see the current states of all boards in the cabinet. Check whether the running
states of all boards are normal. By default, the system first displays the view of front boards. If
you click the subrack edge, the view of back boards are displayed. The Legend window on the
right displays the board states in different colors.

Troubleshooting – Cable Faults
 The transmission faults may be caused by cable problems, such as cable
damages, loose connection, and connection errors.
 Check whether the Ethernet cables are in good condition. If any cable is damaged,
replace it.
 Check whether the Ethernet cable connectors are inserted firmly. If any connector
is loose or not connected, tighten the connector and ensure that the connector is
connected properly.
 If the external coating of a cable is not damaged and the connector is connected
properly, you can infer that the internal core of the cable may be damaged.
Replace the faulty cable with a normal one and observe whether the fault is
rectified.
 If the fault persists after the cable is replaced, you can infer that the fault is not
caused by the cable.

Troubleshooting – Board Faults
 1. In any of the following scenarios, the maintenance personnel
can determine that the board is faulty:
 (1) The RUN indicator on the board panel is off or blinking quickly.
 (2) The ALM indicator on the board panel is on or blinking quickly.
 2. Check the related alarms in the Browse Alarms window, and

then rectify the fault based on the alarm online help. If the alarm
persists, replace the faulty board.

Troubleshooting – Faults Caused by
Data Configuration
 If the device cables and boards are running properly, you can infer that
the transmission fault may be caused by inconsistent negotiation
parameters of the interconnected devices. The troubleshooting steps are
as follows:
 1. Contact the maintenance personnel of the interconnected devices to

query the data configuration of the peer end.
 2. Based on the data configuration of the local end and peer end, analyze
whether the interconnection parameters are consistent on both devices. If
the interconnection parameters are inconsistent, modify them to be
consistent.

Thank you
www.huawei.com

(Basic Training) IMS Bearer Network ISSUE 5.0

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

(Basic Training) IMS Bearer Network ISSUE 5.0

Transféré par

Droits d'auteur :

Formats disponibles

Security Level:

IMS Bearer Network

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 4

N2000 OMS2600 ENUM Server SPG2800 OCS9810 ICG9815

LAN/FTTX InfoX AAA

xDSL CSC3300 MRP6600 UGC3200

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

IMS solution network design

Service Core Border Session (P-CSCF/A-BGF)

Border Session access Portal access

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8

enable the interworking of offices. User access

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

CSC3300 Session cotrol zone

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 A pair of Layer-3 switches (L1/L2) to converge signaling messages in the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

 Based on the preceding requirements:

 In the standard networking of commercial IMS offices, how to route the

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

OLT SBC SBC

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

R2(T8261) USI1 4GE Slot of GE port board, up to down:J2,J3 GE port：BACK5,BACK6,BACK7,BACK8 all

Slot of GE port board, up to GE port：

Slot of GE port board, up to GE port：

SDM 1FE port：LAN

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Local IP network GE links

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 32

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 33

S/I-CSCF MRFC MGCF HSS P-CSCF AS

Core signal VLAN Access AS VLAN

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

 The IMS core devices support the ip1 ip1

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 35

 For each VRRP backup group, at least two links are

Note: If the Layer-3 switch is configured with two or more

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 36

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 37

Number of C x D x message in each call 1

Number of calls per user in busy hours 2

Average size of message 1.5 KByte