Professional Documents
Culture Documents
(Basic Training) IMS Bearer Network ISSUE 5.0
(Basic Training) IMS Bearer Network ISSUE 5.0
(Basic Training) IMS Bearer Network ISSUE 5.0
www.huawei.com
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
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
OSS/BSS/Billing zone Media zone Session control/service zone User access zone
PLMN、PSTN IMS
user
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
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
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.
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.
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.
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.
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.
Access zone
FW
Session/media/service zone Border zone
FW
CE1 CE2 CE3 CE4
CEA CEB
Splitter
Local IMS CCF MRFC MRFP MGW MGCF HSS DNS/ENUM S/I-CSCF P-CSCF
user access NEs of core network
MTU
Eudemon1000E:
S5328:
Hardware
name type ports Net element
version
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
R3(T8280) USIA1 4GE Slot of GE port board, up to down:J2,J3 GE port:BACK5,BACK6,BACK7,BACK8 All ,hot plug
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
4FE/GE(el
NIU NIU0 Position is fixed GE port:BACK1,BACK2,BACK3,BACK4 MPF backboard
ectrical)
IMS Core
SIP SoftPhone
Bearing network
Local IP network
SE2600
SIP SoftPhone
Local IP network GE links
Bearing network GE links
IMS Core
SIP SoftPhone
Bearing network
Local IP network
SE2600
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).
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
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
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.
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.
Eth-trunk
Eth-trunk
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
Access Network
Eth-trunk
# 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
# 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
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
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.
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
Troubleshoot the
fault caused by data
configuration error
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.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 59
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.
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.
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.