MBB ATN+CX(HVPN) Solution

V600R002C01

Overview

Issue 02
Date 2013-5-31

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com

Issue 02 (2013-5-31) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview About This Document

About This Document

Intended Audience
This document describes service transmission, protocol control, data forwarding, protection,
QoS, clock synchronization, and operation and maintenance (O&M) for the ATN+CX solution,
with an intention to show how the ATN+CX solution helps tackle the issues regarding costs,
service quality, and O&M that will be encountered during the process of mobile network
evolution to broadband. The design of the ATN+CX solution aims at mobile broadband carrier
networks.
This document is intended for:
l Network planning engineers
l Technical support engineers
l Maintenance engineers
l Customer training engineers

Change History
Updates between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.

Issue 02 (2013-05-31)
This document is the second release of V600R002C01. Accurate description are made without
any solution update.

Issue 01 (2012-09-30)
This document is the first release of V600R002C01.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential ii

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview Contents

Contents

About This Document.....................................................................................................................ii

1 Current Status and Evolution Tendency of Mobile Carrier Networks...............................1
2 ATN+CX Solution Overview......................................................................................................5
2.1 Services Carried in the ATN+CX Solution....................................................................................................................6
2.2 Network Models in the ATN+CX Carrier Solution.......................................................................................................6
2.3 Overview of the ATN+CX Hierarchy VPN Carrier Solution........................................................................................7
2.4 Introduction to Products Used in the ATN+CX Carrier Solution................................................................................10

3 Implementation of the ATN+CX Hierarchy VPN Solution................................................13

3.1 Service Carrying...........................................................................................................................................................14
3.1.1 Carrying of Services from LTE Base Stations..........................................................................................................14
3.1.2 Carrying of Services from 2G/3G Base Stations.......................................................................................................15
3.2 Protocol Control...........................................................................................................................................................16
3.2.1 Protocol Control for Ethernet Services......................................................................................................................17
3.2.2 Protocol Control for TDM/ATM Services................................................................................................................21
3.3 Data Forwarding...........................................................................................................................................................22
3.3.1 Forwarding of Ethernet Services...............................................................................................................................22
3.3.2 Forwarding of TDM/ATM Services..........................................................................................................................25
3.4 Reliability.....................................................................................................................................................................26
3.4.1 Protection for Ethernet Services................................................................................................................................26
3.4.2 TDM/ATM Service Protection..................................................................................................................................29
3.5 QoS...............................................................................................................................................................................32
3.6 Clock Synchronization.................................................................................................................................................37
3.7 Operation and Maintenance..........................................................................................................................................40

A Acronyms and Abbreviations..................................................................................................47

Issue 02 (2013-5-31) Huawei Proprietary and Confidential iii

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution 1 Current Status and Evolution Tendency of Mobile Carrier
Overview Networks

1 Current Status and Evolution Tendency of

Mobile Carrier Networks

Network Evolution Tendency

As networks are evolving along the 2G->3G->LTE path, mobile services demand more and
more bandwidth, unveiling an era of mobile broadband. In the meanwhile, mobile services are
evolving towards all IP. Under such backgrounds, mobile carrier networks are also driven
towards IP.

Bottlenecks of Legacy Mobile Carrier Networks

Legacy mobile carrier networks are facing challenges regarding costs, availability, and
bandwidth resources, which, to a great extent, hinder advancement of mobile broadband. To
satisfy various mobile broadband requirements while improving availability of mobile
broadband, operators are expecting carrier-class mobile carrier networks that are easy to
maintain, support full scenarios, and have scale-up capabilities.

IPTime Mobile Carrier Solution

IP-based transmission on mobile base stations is essential for mobile broadband to advance. For
compatible transmission of both existing 2G/3G services and future LTE services, Huawei
proposes the IPTime mobile carrier solution to address various mobile broadband requirements
and align transmission expenditure with operators' development strategies, with an ultimate
intention to help operators establish profitable mobile broadband networks.
l Technical challenges for mobile broadband development
Evolution of any technical outlook cannot be completed easily. Mobile operators will have
to tackle challenges during rapid advance of mobile broadband. The following challenges
are typical.
– Maximizing return on investment (ROI)
Though mobile broadband services are prosperous, voice services are still major income
sources of mobile networks, even in a predictable future. That is, 2G, 3G, and LTE
networks will be running in parallel, raising high requirements for access, compatibility,
and scale-up capabilities of mobile carrier networks.
– Guaranteeing carrier-class quality for packet services
TDM/ATM networks are well recognized for its carrier-class features while packet
networks do not have these features. The packet technology for the new 3G/LTE era

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 1

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution 1 Current Status and Evolution Tendency of Mobile Carrier
Overview Networks

must possess new genes to address carrier-class quality requirements in aspects of

network security, service quality, and time synchronization.
– Facilitating network maintenance
The "cloud" feature of IP networks increases O&M expenditure while flexibly
extending network connections. When 3G or LTE services are provisioned based on
the IP architecture, simplifying O&M of legacy IP networks on mobile carrier networks
becomes critically important.
l Building mobile broadband with IPTime
IPTime enables mobile networks to evolve towards LTE while carrying 2G and 3G services.
Investment in IPTime helps operators tackle future challenges with ease. Against
counterpart solutions, the IPTime mobile carrier solution has the following advantages:
– Any media access
Transport resources are one of the factors that determine site acquisition. To provide
more site acquisition options for operators, Huawei IPTime solution enables service
access through copper wires, fibers, and microwave with an all-in-one box.
Any media access satisfies service access requirements even in complicated scenarios
and supports versatile service transportation when mobile network coverage goes deep.
Any media access helps operators reduce site acquisition costs and thereby reduce the
total OpEx, eliminating the transmission bottleneck in the last mile of mobile broadband.
– Any media synchronization
Mobile services refer to roaming and switching services, and mobile networks in
different radio modes require highly precise clock synchronization. For example, GSM/
WCDMA networks require frequency synchronization and CDMA/TD-SCDMA/TDD
LTE networks require phase synchronization.
IPTime uses various technologies like Synchronous Ethernet, IEEE 1588v2, and IEEE
1588 ACR to achieve clock synchronization in various scenarios and to address clock
synchronization requirements specific to different phases during mobile network
evolution. In other words, IPTime provides comprehensive clock synchronization
capabilities. For service access based on copper wires, fibers, and microwave, IPTime
enables packet clocks with GPS-like precision.
– Any media management
Synergized management most fits mobile backhaul networks where multiple service
access modes apply in various scenarios. IP-based rectification is intended to quickly
provision reliable mobile services while improving carrier efficiency and future-
oriented nature of mobile carrier networks, which are the essences of mobile packet
carrier.
Regarding reliability, IPTime offers end-to-end differentiated QoS and OAM
capabilities, which satisfy differentiated requirements of various services from base
stations to the core aggregation nodes. IPTime supports multiple complicated networks,
such as star, chain, ring, and mesh networks, and is capable of completing carrier-class
protection switching within the permitted time range (less than 50 ms for links and 200
ms for nodes).
Regarding unified network management, IPTime enables visual management of IP
services to resolve the "cloud" management issue and to shorten learning curve for the
O&M engineers to switch from SDH to IP. The joint use of network management
synergy, visual management, and one-click configuration enables O&M engineers to
understand the IP technology in an easier way. Visual network management simplifies
network O&M and consolidates the core competitiveness of operators.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 2

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution 1 Current Status and Evolution Tendency of Mobile Carrier
Overview Networks

– LTE ready
Considered as the ultimate goal for mobile network evolution, LTE is designed to
provide fixed-line-like broadband services on mobile networks. When evolving in the
LTE phase, mobile networks will experience extensive changes in aspects of mobile
broadband capabilities and network architecture. For example, LTE shapes an all-IP
flat architecture. Compared with the legacy 3G/HSPA network (with four levels), LTE
considerably reduces the delay in processing protocol packets and thereby improves the
performance of broadband services. LTE ensures low delay less than 20 ms for better
broadband service experience, increases the air interface bandwidth to the 100M level
to support provisioning of broadband services, and enables end-to-end QoS to guarantee
proper service quality. LTE also enables over 350 km/h mobility to support application
in new broadband scenarios such as high-speed railways and indoor coverage. LTE
provides new X2 logical interfaces to enable quick switchover between adjacent base
stations. To qualify themselves for LTE evolution, mobile networks must have flexible
capabilities, enable large-capacity access and aggregation, support time
synchronization, and centralize Layer 3 forwarding capabilities of nodes.
Regarding high bandwidth, IPTime uses an all-IP architecture to provide high
bandwidth, regardless of service access modes. In details, IPTime uses adaptive
modulation to increase bidirectional microwave transport bandwidth to 800 Mbit/s,
binds G.SHDSL line pairs to increase copper access bandwidth to 20 Mbit/s, uses fiber
access to increase the access bandwidth to the GE level, and uses the PON technology
to increase fiber usage while providing required transport bandwidth.
Regarding delay, IPTime ensures unidirectional delay of 5 ms or less, which meets the
delay requirement. Regarding clock synchronization, IPTime uses IEEE 1588v2 to
provide GPS-class packet clock, which meets the time synchronization requirement of
LTE. Regarding the X2 logical interface, IPTime uses L2/L3 stepless switching to
enable quick switchover between adjacent base stations.

Mobile Carrier Network Buildout Mode

Mobile operators choose proper modes to build their mobile carrier networks. Some mobile
carriers that lease networks prefer building their own mobile carrier networks to provide mobile
broadband on end-to-end networks. Some integrated operators that possess fixed-line broadband
metro networks prefer reusing their incumbent broadband metro networks to provide mobile
broadband. When building mobile carrier networks, mobile operators mainly use two modes:
independent end-to-end mode and gateway mode. In gateway mode, the incumbent broadband
metro networks are extended to provide mobile broadband.

l Independent end-to-end mode

Mobile operators mostly concern about reduction of lease costs and improvement of
transport efficiency. As mobile services are evolving towards IP, service granularities will
be larger and more network bandwidth will be required. During this process, more FE ports
will be used on the mobile base station side, which urgently calls for the packet technology
on the transport side. When building their own end-to-end packet transport networks
(PTNs) to carry mobile services, operators need to consider the requirements of introducing
and supporting highly-valuable services such as enterprise private line services. As the
packet technology is introduced, there are challenges regarding the features that are
essential to provisioning mobile services. For example, packet-based transport networks
must be capable of transmitting synchronization signals of higher precision and reliability.
Though GPS enables the required frequency and time synchronization, there are network
security threats. The packet technology veils network management and causes issues
regarding fault identification, performance management, and security management.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 3

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution 1 Current Status and Evolution Tendency of Mobile Carrier
Overview Networks

l Gateway mode
In this mode, mobile operators reuse the incumbent broadband metro networks to provide
mobile broadband. This reduces costs and relieves the pressure on the legacy SDH networks
to evolve. The legacy broadband metro networks hardly provide the essential features for
mobile services. To resolve this issue, new packet transport gateway devices must be
introduced to provide the essential features such as synchronization signal transmission
and offload. With help of new packet transport gateway devices, the incumbent broadband
metro networks can also transport mobile services while maximizing their wide coverage
and service provisioning capabilities. However, as mobile broadband applications are
evolving, the incumbent broadband metro networks will have to be reconstructed into FMC-
oriented carrier networks.
Huawei IPTime mobile carrier solution uses MPLS-based devices that fit the two network
buildout modes. Huawei devices integrate packet features like flexibility, scalability, and
statistics multiplexing, and transport features like end-to-end OAM, protection, connection-
orientation, QoS, and time synchronization. Thanks to feature integration, Huawei devices can
be used to build all-IP mobile packet carrier networks. As aforementioned, IPTime supports any
media access, provides precise packet clocks, and enables carrier-class 50 ms protection and 30s
hierarchical (five levels) fault detection. In addition, IPTime focuses on sustainable development
of mobile broadband and overall OpEx reduction, and helps mobile operators to build LTE-
oriented carrier networks and ultimately to achieve commercial success in the all-IP
transformation.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 4

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

2 ATN+CX Solution Overview

About This Chapter

This chapter describes the ATN+CX solution in aspects of service carrying, network models,
technical solutions, and related products.

2.1 Services Carried in the ATN+CX Solution

This section describes the services that can be transmitted over the network where the ATN+CX
solution is applied.
2.2 Network Models in the ATN+CX Carrier Solution
This section describes the network models in the ATN+CX carrier solution based on an end-to-
end network topology.
2.3 Overview of the ATN+CX Hierarchy VPN Carrier Solution
Hierarchy VPN (HVPN) refers to one of the carrier modes for the IPTime mobile broadband
(MBB) ATN+CX solution. The ATN+CX solution is the main solution for the IP Mobile
Backhaul (IP MBH) network constructed by Huawei.
2.4 Introduction to Products Used in the ATN+CX Carrier Solution
This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX carrier solution, and the network layers where the devices are used.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 5

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

2.1 Services Carried in the ATN+CX Solution

This section describes the services that can be transmitted over the network where the ATN+CX
solution is applied.

Long term evolution (LTE) marks the ultimate goal of 3G evolution, which enhances the air
interface performance in 3G. To be specific, under a 20 MHz frequency spectrum, peak rates of
downstream 326 Mbit/s and upstream 86 Mbit/s are available. This feature enhancement
improves service performance for cell edge users while increasing cell capacity and reducing
system delay. Among the total radio network investments during evolution from 2G/3G to LTE,
the investment on sites (telecommunications room and lease) accounts for 50%, that on radio
base stations accounts for 40%, and that on MBB service bearer networks accounts for only 10%
minus. Because of the extensive investment variations, operators rarely rectify their 2G/3G base
stations to fit the IP-based MBB service bearer networks, but require multiservice transport
capabilities of MBB service bearer networks.

The ATN+CX solution applicable to MBB service bearer networks is capable of transporting
the following services:
l LTE S1 services
The ATN+CX devices are used between eNBs and S-GWs/MMEs. Services are received
through Ethernet ports and are transported based on IP/MPLS using the IP technology.
l LTE X2 services
The ATN+CX devices are used between eNBs to establish logical connections. Services
are received through Ethernet ports and are transported based on IP/MPLS using the IP
technology.
l 2G/3G Ethernet services
The ATN+CX devices are used between BTSs/NodeBs and BSCs/RNCs. Services are
received through Ethernet ports and are transported based on IP/MPLS using the IP
technology.
l 3G ATM services
The ATN+CX devices are used between NodeBs and RNCs. Services are received through
multiple E1 ports and are transported based on PWE3/MPLS using the ATM inverse
multiplexing technology.
l 2G TDM services
The ATN+CX devices are used between BTSs and BSCs. Services are received through
E1 ports and are transported based on PWE3/MPLS using the TDM technology.

2.2 Network Models in the ATN+CX Carrier Solution

This section describes the network models in the ATN+CX carrier solution based on an end-to-
end network topology.

The ATN+CX solution is an IP/MPLS-based solution designed for the IP-based service
transmission on 2G, 3G, and LTE mobile networks.

In a typical network model, the networks between CSGs and RSGs carry services between base
stations and core nodes on mobile networks, as shown in Figure 2-1.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 6

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

Figure 2-1 Network models in the ATN+CX carrier solution

This carrier solution builds IP Mobile Backhaul (IP MBH) network using Huawei ATN and CX
devices. It supports simple flexible networks and has excellent fixed mobile convergence (FMC)
capabilities. In network topology, ATN devices are deployed as CSGs to build an access network
and CX600 devices are deployed as ASGs and RSGs to build an aggregation network. This
network can be flexibly adjusted to address 2G, 3G, and LTE service carrier requirements, also
VPN service.
The ATN+CX solution is flexible to deploy and applicable to large-, medium-, or small-scale
networks. This solution has the following characteristics:
l The ATN and CX devices can form ring or linear topologies.
l The ATN and CX devices can be single-homed or dual-homed to upstream nodes.
l The third-party network (using SDH, xDSL, or Layer 2/Layer 3 leased lines )can be used
to bear ATN+CX services.

2.3 Overview of the ATN+CX Hierarchy VPN Carrier

Solution
Hierarchy VPN (HVPN) refers to one of the carrier modes for the IPTime mobile broadband
(MBB) ATN+CX solution. The ATN+CX solution is the main solution for the IP Mobile
Backhaul (IP MBH) network constructed by Huawei.
With advance of the third generation (3G) services and long term evolution (LTE) services,
mobile operators are expanding their radio access networks (RANs). There are increasing

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 7

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

requirements for bandwidth, expansion, and configuration flexibility on the mobile carrier
network between base stations and base station controllers. For the second generation (2G) and
3G services, most operators use multi-service transmission platform (MSTP) to transmit data
between base stations and base station controllers. Based on the SDH platform, MSTP products
receive, process, and transmit TDM, ATM, and Ethernet services, and they can be managed by
a unified network management system (NMS). MSTP products, however, have their
weaknesses: high costs, low bandwidth usage, difficult expansion, and inflexible configurations.

As mainstream networks for data communication, IP data communication networks have

features like versatile access and large scale. IP RAN comes up to address operators' demands
for maximizing revenues generated from investments, reducing investments on new networks,
and evolving their networks towards LTE.

The Hierarchy VPN carrier solution builds IP RAN with Huawei ATN and CX devices, and it
has excellent fixed mobile convergence (FMC) capabilities and supports simple flexible
networks. This solution has a hierarchy design between cell site gateways (CSGs) and Radio
service gateway (RSGs), which fits large-sized carrier networks.

In network topology, ATN devices are deployed as CSGs to build an access network and CX600
devices are deployed as aggregation site gateways (ASGs) and RSGs to build an aggregation
network. The network topology can be flexibly adjusted to address 2G, 3G, and LTE service
carrier requirements. Figure 2-2 lists the details.

Figure 2-2 Hierarchy VPN carrier solution

Table 2-1 Radio service types

Mobile Communication Port Type (Base Station) Port Type (Core Node)
Service Type

2G TDM BTS:E1 BSC：Cpos STM-1

2G ETH BTS:Ethernet BSC：Ethernet

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 8

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

Mobile Communication Port Type (Base Station) Port Type (Core Node)
Service Type

3G ATM Node B:n*E1 RNC：ATM STM-1

3G ETH Node B:Ethernet RNC：Ethernet

LTE S1/X2 eNode B:Ethernet MME：Ethernet

The Hierarchy VPN carrier solution varies with 2G, 3G, and LTE services, and so does the
Hierarchy VPN solution that needs to be deployed.

Table 2-2 Hierarchy VPN to be deployed

Solution components HVPN MS-PW

Carried services l LTE S1/X2 l 3G ATM

l 3G Ethernet l 2G TDM

IGP Hierarchical interior gateway protocol (IGP) is deployed

between CSGs and RSGs for proper data forwarding. ASGs
use policy-based routing to aggregate and filter routes, freeing
up bandwidth used during route updates and maintenance.
The intermediate system to intermediate system (IS-IS)
protocol is recommended as an IGP.

MPLS tunnels MPLS tunnels between CSGs and ASGs, ASGs and RSGs
must be established to carry services.
The MPLS traffic engineering (TE) protocol is recommended
as an MPLS tunnel protocol.

VPN Hierarchical L3VPNs PW segments between CSGs

between CSGs and ASGs, and ASGs, ASGs and RSG
ASGs and RSGs must be smust be established to carry
built to carry services. services.

Protection switching Service protection switching between nodes or links is

required for higher network availability.

The recommended protection The recommended protection

or fault detection approaches or fault detection approaches
include MPLS TE hot- include MPLS TE hot-
standby, VPN FRR, VRRP, standby, PW redundancy,
BFD, and GR. VRRP, BFD, and GR.

QoS End-to-end QoS between CSGs and RSGs must be deployed

to guarantee required service quality.
The recommended QoS approaches include DiffServ and
HQoS.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 9

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

Solution components HVPN MS-PW

Clock synchronization End-to-end clock synchronization between CSGs and RSGs

must be deployed to ensure real-time service transmission.
The recommended clock synchronization solutions are
synchronous Ethernet and IEEE 1588v2.

2.4 Introduction to Products Used in the ATN+CX Carrier

Solution
This section describes the roles, functions, and product models of the devices that are used in
the ATN+CX carrier solution, and the network layers where the devices are used.

Network Layer Role Function Product Model

UNI side User equipment (UE) Refers to a terminal -

on a mobile network.

Base station Base transceiver Refers to a 2G base -

station (BTS) station. Mobile
communication
systems are
composed of mobile
stations, base station
subsystems (BSSs),
and network
subsystems (NSSs).
BSSs are composed
of BTSs and base
station controllers
(BSCs).
NOTE
A CDMA2000 (3G)
base station is also
BTS.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 10

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

Network Layer Role Function Product Model

NodeB (3G base Refers to a base -

station) station on a 3G
mobile network.
NodeBs are
interconnected with
radio network
controllers (RNCs)
through standard Iub
ports and
communicate with
UE nodes through
Uu ports, processing
Uu port physical-
layer protocols and
Iub port protocols.

eNodeB (E-UTRAN Refers to an evolved -

NodeB, LTE base form of NodeB or
station) LTE base station.

Access network Cell site gateway Receives and ATN910

(CSG) processes various Product version:
service signals from V200R001C02
base stations and
forwards them to Product version:
devices at the V200R002C00
aggregation layer. ATN950
Product version:
V200R001C02
ATN910I
Product
version:V200R002C
00
ATN950B
Product version:
V200R001C02
Product version:
V200R002C00

Aggregation Aggregation site Aggregates service Quidway CX600

network gateway (ASG) signals from CSGs Product version:
and forwards them. V600R005C00
Radio Service Connects to Product version:
Gateway (RSG) controllers. V600R006C00

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 11

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 2 ATN+CX Solution Overview

Network Layer Role Function Product Model

Core network (MBB BSC Manages radio -

core) network resources
and cell information,
controls power, and
locates and switches
users.

RNC Refers to a key node -

on a 3G network.
Manages mobility,
processes calls,
manages links, and
switches users on the
access network.

Mobility Refers to a critical -

management entity control node on a
(MME) 3GPP LTE access
network, and locates
UE nodes in idle
mode and processes
calls (including
regeneration).

Serving gateway (S- Provides the —

GW) functionality of a
proxy and a gateway
to implement
Wireless Application
Protocol (WAP)
service access, user
authentication,
service control, and
service scheduling.
In addition, the S-
GW can use the
WAP protocol to
perform content-
based or volume-
based accounting.

O&M system Network Operates, manages, iManager U2000

management system and maintains a Product version:
(NMS) network. V100R006C02
Product version:
V100R008C00

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 12

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

3 Implementation of the ATN+CX Hierarchy

VPN Solution

About This Chapter

This chapter describes the key technologies used in the Hierarchy VPN carrier solution in aspects
of service carrying, protocol control, data forwarding, QoS, clock synchronization, and O&M.

3.1 Service Carrying

This section describes how the solution carries 2G, 3G, and LTE services.
3.2 Protocol Control
A mobile network may carry LTE services only or carry LTE and 2G/3G services together.
Protocol control in the two application scenarios is different.
3.3 Data Forwarding
This section describes how the carrier solution forwards 2G, 3G, and LTE services.
3.4 Reliability
This section describes protection for 2G, 3G, and LTE services in the solution.
3.5 QoS
In the mobile carrier solution, QoS requirements vary with traffic typess. On the carrier network,
DiffServ and HQoS must be deployed to ensure proper service quality.
3.6 Clock Synchronization
Radio networks have high requirements for frequency and time synchronization, but GPS
deployment causes high costs. To solve the problem, Huawei provides multiple technologies
such as 1588v2, synchronous Ethernet, 1588 ACR, and IP clock to provide high-precision
frequency and time synchronization signals for radio base stations over the carrier network.
3.7 Operation and Maintenance
Future networks will be doubtlessly IP-based and more versatile mobile data services will be
available, which means increasingly complex network maintenance. A qualified operation and
maintenance (O&M) system must handle more flexible configurations and fault detection for
multiple types of services while the operational expenditure (OpEx) is maintained at a reasonable
level.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 13

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

3.1 Service Carrying

This section describes how the solution carries 2G, 3G, and LTE services.

3.1.1 Carrying of Services from LTE Base Stations

LTE base stations are referred to as eNodeBs (eNBs for short). This section describes how
Ethernet services, including LTE S1 and LTE X2 services, from LTE base stations are carried.

LTE S1 Service Carrying

LTE S1 services carry the message, voice, and video traffic of radio services and must be sent
to the MBB core to implement identity authentication, which is required for exchange of various
service data, as shown in Figure 3-1.

Figure 3-1 LTE S1 services carried by Hierarchy VPN

L3VPNs are deployed between CSGs and RSGs to carry LTE S1 service traffic.

NOTE

LTE S1 services are carried by eNBs in the same way as 3G Ethernet services are carried by NodeBs.

LTE X2 Service Carrying

LTE X2 services are sent by the source CSG to the destination CSG during switching between
mobile base stations, as shown in Figure 3-2.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 14

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-2 LTE X2 services carried by Hierarchy VPN

LTE X2 services are carried over L3VPNS between ASGs and CSGs.
message messages are exchanged between the source and destination eNBs, eNBs and MMEs,
while data traffic is forwarded from the source to the destination along the shortest path,
accounting 3% or less in the total service traffic.
NOTE
LTE X2 services carry only the traffic generated during switching of the source and destination eNBs.
After the eNB buffer is freed up, LTE S1 services will be established between the destination eNB and
MME.

3.1.2 Carrying of Services from 2G/3G Base Stations

The services carried on the carrier network vary with the types of base stations connected to
CSGs. This section describes how the carrier network carries TDM/ATM services from BTSs
or NodeBs.
On a 2G/2.5G network, RAN is also referred to as BSS and it mainly carries TDM services; on
a 3G/UMTS network, RAN is also referred to as UMTS terrestrial radio access network
(UTRAN) and it mainly carries ATM services.
Service access may be TDM access, ATM access, or Ethernet access, depending on the base
station access type. The IP technology has unified Layer 3 services and other packet technologies
will cease in advance. In addition, the Ethernet technology has been widely used, which makes
high bandwidth available based on low costs. Generally, the PWE3 technology is used on IP
Ethernet links to transparently transmit TDM/ATM services, protecting investment on live
networks.

NOTE

3G Ethernet services from NodeBs are carried in the same way as LTE S1 services are carried.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 15

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-3 Mobile carrier network diagram

As shown in Figure 3-3, the mobile carrier network is deployed as follows to carry TDM/ATM
services.

l PWE3 is deployed on the access ring.

l PWE3 is also deployed on the aggregation ring.
l PW switching is deployed on the ASGs.

The following describes end-to-end carrying of TDM/ATM services.

l TDM services
Multiple PW segments are established between the CSGs and RSGs. TDM PW segment 1
is established between the CSG and ASG and TDM PW segment 2 is established between
the ASG and RSG.
When receiving TDM services from the BTS over E1 links, the CSG encapsulates TDM
packets into PWE3 and transparently transmits PWE3 packets to the RSG. When receiving
the PWE3 services, the RSG strips the PWE3 packet header to recover TDM services and
then forwards the TDM services to the BSC.
l ATM service
Multiple PW segments are established between the CSGs and RSGs. ATM PW segment 1
is established between the CSG and ASG and ATM PW segment 2 is established between
the ASG and RSG.
When receiving ATM services from the NodeB over ATM/IMA links, the CSG
encapsulates ATM packets into PWE3 and transparently transmits PWE3 packets to the
RSG. When receiving the PWE3 services, the RSG strips the PWE3 packet header to
recover ATM services and then forwards the ATM services to the RNC.

3.2 Protocol Control

A mobile network may carry LTE services only or carry LTE and 2G/3G services together.
Protocol control in the two application scenarios is different.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 16

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

3.2.1 Protocol Control for Ethernet Services

VProtocol Control for Ethernet ServicesThis section describes how to establish hierarchical
VPN transmission and how to deploy IP/MPLS networks for VPNs.

IP/VLAN

Table 3-1 IP/VLAN deployment

NodeB/eNB Side MME/RNC Side

l Layer 3 sub-interfaces are created for l VRRP is deployed between the master and
different Ethernet services (LTE S1, LTE slave RSGs, which are dual-homed to the
X2, and OM). Then, VRFs receive RNCs. VRRP's virtual IP address is used
services from base stations through the as the default gateway IP address.
VLAN. l The VRF on the MME/RNC side is bound
l The same type of services from different to VLANIF.
base stations uses the same VID. l RSGs are connected to the MME/RNC
l Sub-interface IP addresses cannot be in through main interfaces.
the same network segment and the sub-
interfaces for the same type of services
from different base stations use
consecutive IP addresses for easy service
aggregation.
l The ports connecting base stations and
CSGs use 30-bit subnet masks to save the
address space.

IGP
Various routing protocols apply between the access network and aggregation network. Proper
CPU usage must be considered during service design assessment to prevent slow IGP
convergence. During IGP convergence, IGP has to maintain a large path database. In this
solution, the hierarchical design of the IGP protocol must be used. By-process IS-IS is
recommended, as shown in Figure 3-4.

Figure 3-4 By-process IS-IS deployment

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 17

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Table 3-2 IGP deployment

Deployment Point IS-IS

Access network IS-IS Level-2 routes are deployed.

Each access network belongs to a different
IS-IS process.

Aggregation network IS-IS Level-2 routes are deployed.

Route advertising and learning IGPs on different networks are isolated using
the routing process and the routes on the
access network are isolated from those on the
aggregation network.
LSR-IDs of ASGs are placed in the
aggregation ring's process. Therefore, the
route must be led into the access ring's
process through an ASG.

Multiple OSPF areas are deployed. Aggregation rings are deployed with OSPF area 0 (backbone
areas), and access rings are deployed with OSPF totally stub areas, as shown in Figure 3-5.

Figure 3-5 Multiple OSPF areas deployed on a network

Table 3-3 OSPF deployment

Deployment Point OSPF

Access ring Access rings are deployed with OSPF stub

areas.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 18

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Deployment Point OSPF

Aggregation ring Aggregation rings are deployed with OSPF

area 0.
The ASG uses the advertise mpls-lsr-id
command to advertise MPLS LSR IDs to
multiple areas as intra-area routes.
Configure one subinterface on the master
ASG and one on the slave ASG for each
access ring and add the subinterfaces to
access ring's OSPF area. Create a link
between the master ASG and the slave ASG,
and add the link to the OSPF area 0.
As the access ring is deployed with a totally
stub area and the ASGs are ABRs on the
access ring, issue the stub-no-summary
command to the ASGs to configure the access
ring OSPF area to be a totally stub area.

A proper IGP protocol must be chosen based on network assessment.

MPLS TE
In the Hierarchy VPN solution, to achieve hierarchical transmission and outer label assignment,
end-to-end tunnels between CSGs and RSGs must be deployed for 3G Ethernet and LTE
services, as shown in Figure 3-6.

Figure 3-6 MPLS TE network

l TE tunnels from CSGs to ASGs and ASGs to RSGs must be created segment by segment.
l Hot standby is applicable to TE tunnels.
l Dual-homing protection is deployed to establish backup tunnels leading to the slave device.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 19

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

MPLS LDP
MPLS LDP LSP can be used to carry services. LDP LSPs totally depend on IGP route
convergence, plan LDP LSPs using default IGP cost values and o not configure LDP FRR.
Enable synchronization between LDP and IGP on interfaces by running the isis ldp-sync or ospf
ldp-sync command.

L3VPN
In the Hierarchy VPN solution, hierarchical L3VPN must be established. VPN instances are
used to differentiate different Ethernet services and thereby to carry end-to-end services (LTE
S1 and 3G Ethernet) and local switching services (LTE X2), as shown in Figure 3-7 and Figure
3-8.

Figure 3-7 Carrying of end-to-end services

Figure 3-8 Carrying of local switching services

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 20

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Table 3-4 L3VPN deployment

L3VPN End-to-End Service Local Switching Service

MP-iBGP iBGP peers are established between the CSG and ASG, the
ASG and RSG.

Method 1: A route reflector is The ASG advertises a default

deployed in ASG's VPN. The route (0.0.0.0) to the CSG
GSG and RSG are clients of and the CSG sends packets to
the route reflector. The CSG the ASG along the default
receives all specific routes. route.
Method 2: A route reflector is l When adjacent CSGs are
deployed in ASG's VPN. The connected to the same
GSG is a client of the route ASG, the ASG searches
reflector. The CSG receives for VPN routes and
only default or aggregation forwards packets
routes. accordingly.
l When adjacent CSGs are
connected to different
ASGs, an ASG forwards
packets to the target ASG
through the RSG and then
the target ASG searches
for VPN routes and
forwards packets
accordingly.
l When adjacent CSGs are
connected to different
RSGs, the MME forwards
packets. In this case,
packets are carried in the
same way as LTE S1
services are carried.

3.2.2 Protocol Control for TDM/ATM Services

PWE3 services have to be deployed on the carrier network to transmit, control, and differentiate
various TDM/ATM services. This section describes how to establish MS PW transmission and
how to deploy IP/MPLS networks for VPNs.

IGP Selection
Protocol control (IGP) for TDM/ATM services is implemented in the same way as that for
Ethernet services.

MPLS and PWE3

Tunnels from CSGs to ASGs, from ASGs to RSGs, and between the master and slave RSGs
must be deployed so that TDM/ATM services can be carried. Multiple segments of PWs are
carried in the corresponding segments of the tunnel.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 21

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-9 Deployment of MPLS and VPN protocols for TDM/ATM services

As shown in Figure 3-9, PWE3 needs to be deployed after route deployment is completed.
Table 3-5 provides suggestions for the deployment.

Table 3-5 Suggestions for MPLS and VPN deployment

Deployment Point Tunnel MS PW

Access ring (from CSGs to MPLS TE is the best choice. Deploy PWE3 between
ASGs) ASGs and CSGs.
Bypass PWs are not required
between ASGs that connect
to the same access ring.

Aggregation ring (from Deploy PWE3 between

ASGs to RSGs) ASGs and RSGs.
Deploy bypass PW between
the master and slave RSGs.

ASG PW swapping is deployed.

3.3 Data Forwarding

This section describes how the carrier solution forwards 2G, 3G, and LTE services.

3.3.1 Forwarding of Ethernet Services

This section describes the process of Ethernet service forwarding, which helps users understand
how Ethernet services are carried in this solution.
When the NodeB/eNB sends LTE or 3G Ethernet packets to the MME/RNC, CSGs encapsulate
the packets in BGP/MPLS VPN and then forward them. The paths over which the packets are
forwarded vary with the service types as follows:

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 22

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l Carrying of end-to-end services (3G Ethernet and LTE S1)

l Carrying of local switching services (LTE X2).

Carrying of End-to-End Services

End-to-end services are carried between the CSG and RSG, as shown in Figure 3-10.

Figure 3-10 Carrying of LTE S1 services

NOTE
The outer TE label indicates the next BGP hop and the inner VPN label indicates the egress or VPN for
packets.

When receiving packets destined to the RSG, the ASG forwards them by the outer labels and
also swaps the inner labels. In other words, the ASG forwards packets based on the outer and
inner labels.

Carrying of Local Switching Services

Local switching services, that is, LTE X2 services, are forwarded between neighboring CSGs
along the shortest path as follows:
l If the neighboring CSGs are connected to the same ASG, the ASG forwards the LTE X2
services based on searched VPN routes.
l If the the neighboring CSGs are connected to different ASGs, the source ASG forwards
the LTE X2 services to the RSG which then forwards the LTE X2 services to the destination
ASG based on searched VPN routes.
l If the neighboring CSGs are connected to different RSGs, the LTE X2 services are
forwarded the same way LTE S1 services are forwarded.
l Figure 3-11 shows forwarding of LTE X2 services between CSGs that are connected to
the same ASG.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 23

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-11 Forwarding of LTE X2 services on the same ASG

l LTE X2 services on different ASGs are forwarded based on RSG deployment.

– When LTE X2 services are forwarded between CSGs that are connected to different
ASGs, the RSG does not swap the inner VPN label, as shown in Figure 3-12.

Figure 3-12 Forwarding of LTE X2 services on different ASGs (1)

– When LTE X2 services are forwarded between CSGs that are connected to different
ASGs, the RSG does not swap the inner VPN label, as shown in Figure 3-13.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 24

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-13 Forwarding of LTE X2 services on different ASGs (2)

l LTE X2 services on different RSGs are forwarded in the similar way as LTE S1 services
are forwarded.

3.3.2 Forwarding of TDM/ATM Services

This section describes the process of TDM/ATM service forwarding, which helps users
understand how TDM/ATM services are carried in this solution.

A multi-segment PWE3 (MS PW) consists of multiple PW segments between the CSG and RSG.
These PW segments must be connected by ASGs, which swap inner PW labels and outer tunnel
labels.

Figure 3-14 Forwarding of TDM/ATM services

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 25

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

NOTE
The figure below is based on an assumption that tunnels have been set up based on RSVP-TE.

The ATN device (CSG) on the access ring receives signals from base stations through ATM/
TDM ports and then encapsulates them into PWs and TEs. When the signals are forwarded, only
TE labels need to be swapped, but the inner PW labels remain unchanged. Figure 3-14 shows
the entire process.
As a conjunction, an ASG swaps the inner PW1 and PW2 labels, and the outer TE1 and TE2
labels.
When signals are forwarded between the ASG and RSG on the aggregation ring, only TE labels
need to be swapped and the inner PW labels remain unchanged. When terminating PWE3, the
NPE forwards ATM/TDM signals to the RNC or BSC.

3.4 Reliability
This section describes protection for 2G, 3G, and LTE services in the solution.

3.4.1 Protection for Ethernet Services

A reliable network requires that a backup path be available to data. This section describes how
Ethernet services are protected and restored in this solution.
Proper network restoration mechanisms must be chosen based on the general goal of network
availability. The network availability goal always depends on application requirements. If any
impact on users needs to be eliminated in case of any network component failures, the network
restoration mechanisms must function to reroute voice data to a backup path with QoS
guaranteed within milliseconds.
l End-to-end service protection
To ensure that services are switched in milliseconds in case of faults, multiple protection
mechanisms are used in this solution, as shown in Figure 3-15.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 26

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-15 End-to-end service protection

– Protection for ASG

The CSG is dual-homed to the master and slave ASGs. When BFD for TE on the CSG
detects a failure of the master ASG, VPN FRR switches over VPN services to slave
ASG.
The master RSG is dual-homed to the master and slave ASGs. When BFD for TE on
the master RSG detects a failure of the master ASG, VPN FRR switches over VPN
services to slave ASG.
When the VPN services are reverted and the CSG-to-ASG BGP is set up first, the ASG
sends a default route to the CSG, resulting in ASG inconsistency for the CSG and RSG,
and asynchronous reversion. Therefore, the CSG-to-ASG BGP setup time needs to be
extended.
– Protection for RSG
The master ASG is dual-homed to the master and slave RSGs. When dynamic BFD for
BGP detects a failure of the master RSG, quick BGP route convergence results and the
services are switched to the slave RSG.
– Protection for the access network (from CSG to ASG)
The CSG is dual-homed to the master and slave ASGs. When BFD for LSP detects a
failure of the working LSP between the CSG and ASG, services will be switched over
to the protection LSP. After the switching, TE tunnels remain unchanged and the peers
of the CSG and RSG neither change, except for the working LSP.
– Protection for the aggregation network (from ASG to RSG)
The ASG is dual-homed to the master and slave RSGs. When BFD for LSP detects a
failure of the working LSP between the ASG and RSG, services will be switched over
to the protection LSP. After the switching, the peers of the CSG and RSG do not change,
except for the working LSP.
– Protection for MBB core-side link
The MBB core is dual-homed to RSGs through VLANIFs. When the link between the
master RSG to the core is faulty, VRRP status remains unchanged and VLANIF updates

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 27

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

the egress ARP, switching communication over to the link between the slave RSG and
core. When the master RSG is malfunctioning, L3VPN switches to the slave RSG
through VPN FRR, resulting in VRRP status change. Then the slave RSG becomes
master and VRRP switches to the slave RSG and increases the priority the direct route.
NOTE
If the link between the master RSG and core is faulty, the logical relationships between the master
and slave RSGs remain unchanged. A VLANIF is bound as the egress for the L3VPN and
VLANIF status is always up. VRRP over VLANIF only changes the MAC address for the egress
in the VLANIF-to-core direction.
l Protection for local switching services
For local switching services and end-to-end services, link protection is the same, but node
protection is slightly different, as shown in Figure 3-16 and Figure 3-17.

Figure 3-16 Protection for ASG with local switching services

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 28

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-17 Protection for RSG with local switching services

– Protection for ASG

– The CSG is dual-homed to the master and slave ASGs. When BFD for TE on the
CSG detects a failure of the master ASG, VPN FRR switches over VPN services to
slave ASG.
When the VPN services are reverted and the CSG-to-ASG BGP is set up first, the
ASG sends a default route to the CSG, resulting in ASG inconsistency for the CSG
and RSG, and asynchronous reversion. Therefore, the CSG-to-ASG BGP setup time
needs to be extended.
– Local switching services on different ASGs
The CSG is dual-homed to the master and slave ASGs. When BFD for TE on the
CSG detects a failure of the master ASG, VPN FRR switches over VPN services to
slave ASG. This is consistent with end-to-end services.
The master RSG is dual-homed to the master and slave ASGs. When dynamic BFD
for BGP or BFD for TE detects a failure of the master ASG, route convergence or
VPN FRR switches services to the slave ASG.
When the VPN services are reverted and the CSG-to-ASG BGP is set up first, the
ASG sends a default route to the CSG, resulting in ASG inconsistency for the CSG
and RSG, and asynchronous reversion. Therefore, the CSG-to-ASG BGP setup time
needs to be extended.
– Protection for RSG
– Local switching services on the same ASG
Local services on the same ASG are carried on the same access network and an RSG
is not involved in the protection.
– Local switching services on different ASGs
The ASG is dual-homed to the master and slave RSGs. When BFD for TE on the
ASG detects a failure of the master RSG, VPN FRR switches over VPN services to
slave RSG. This is consistent with end-to-end services.

3.4.2 TDM/ATM Service Protection

This section describes how to use various network monitoring and protection mechanisms to
detect a TDM and ATM service fault within milliseconds and improve network reliability.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 29

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Protection Scheme Deployment

Protection is an important factor to be considered in the deployment of a mobile bearer solution.
Non-stop forwarding of services on the bearer network must be ensured, improving the reliability
of the mobile bearer network.

An example of ATM service protection is provided in this section. In this example, CSGs are
dual-homed to two ASGs and PWs are set up to bear ATM services. TDM service protection is
similar to ATM service protection and is not described in details.

Figure 3-18 is a schematic diagram showing how ATM services are protected.

Figure 3-18 Schematic diagram of ATM service protection

Table 3-6 Reliability scheme for CSGs' access to ASGs in dual-homing mode

Monitoring/Protection Monitoring Mechanism Recommended

Point Protection Scheme

Access ring and aggregation BFD for PW PW redundancy

ring TE HSB

RSG BFD for PW Combination of E-APS 1:1

and a single bypass PW
AC side of the RSG Physical link detection
or,
(RNC)
combination of E-APS 1+1
and two bypass PWs

Deploying the protection scheme shown in Table 3-6 is recommended, which can ensure carrier-
class reliability.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 30

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l BFD is associated with other protocol-based protection mechanisms, detecting faults within
milliseconds and triggering protection actions immediately.
l PW redundancy provides real-time protection for primary PWs. In addition, deployment
of bypass PWs between RSGs prevents traffic from being lost during PW switching.
l E-APS can be deployed on the AC side of the RSG to protect the base station controller.
l Deploying NSR(Non-Stopping Routing) on the entire network is recommended, which can
prevent traffic interruption during PW or APS switching.

Traffic Switching Mechanism to Protect Services on Faulty Points

l Combination of E-APS 1:1 and a single bypass PW

Figure 3-19 Schematic Diagram of Traffic Paths of E-APS 1:1

– Protection for ASG

Traffic is switched to the secondary PW on the network side.
On the AC side, the link between the master RSG and the RNC remains active.
Traffic flows over the bypass PW between the slave RSG and the master RSG, bypassing
the faulty primary PW.
– Protection for RSG
Traffic is switched to the secondary PW on the network side.
APS switching is performed on the AC side so that traffic will take the link between
the slave RSG and the RNC.
– Protection for the access network (from CSG to ASG)
The CSG is dual-homed to the master and slave ASGs. When BFD for LSP detects a
failure of the working LSP between the CSG and ASG, services will be switched over
to the protection LSP. After the switching, TE tunnels remain unchanged and the peers
of the CSG and RSG neither change, except for the working LSP.
– Protection for the aggregation network (from ASG to RSG)
The ASG is dual-homed to the master and slave RSGs. When BFD for LSP detects a
failure of the working LSP between the ASG and RSG, services will be switched over

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 31

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

to the protection LSP. After the switching, the peers of the CSG and RSG do not change,
except for the working LSP.
– If a fault occurs on the active AC, traffic is switched in the following manner:
APS switching is performed on the AC side so that traffic will take the link between
the slave RSG and the RNC.
– If the Independent mode is used for negotiation in PW redundancy:
Traffic is switched from the primary PW to the secondary PW on the network side.
– If the Master/Slave mode is used for negotiation in PW redundancy:
Traffic is not switched on the network side. On the AC side, traffic flows over the
bypass PW between the master RSG and the slave RSG.
l Combination of E-APS 1+1 and two bypass PWs

Figure 3-20 Schematic Diagram of Traffic Paths of E-APS 1:1

Traffic switching in this scenario is almost the same as that in the scenario mentioned above.
The difference is that in this scenario there are two bypass PWs deployed between the
master RSG and the slave RSG, traffic from the primary and secondary PWs are transmitted
through different bypass PWs.

3.5 QoS
In the mobile carrier solution, QoS requirements vary with traffic typess. On the carrier network,
DiffServ and HQoS must be deployed to ensure proper service quality.

A carrier network mainly carries the following types of traffic:

l Voice, video, and data traffic originating from end users

l Message and OM traffic originating from radio and core networks
l IP clock
l Protocol packets at the control layer

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 32

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l Pass-through traffic
As shown in Figure 3-21, if services are simple and quality needs to be ensured only for services,
common queue scheduling needs to be deployed; if services are complex and quality needs to
be ensured for services, base stations, and tunnels, HQoS must be deployed.

Figure 3-21 QoS solution

NOTE
It is recommended to deploy the same QoS mechanism on the working and protection links.

Table 3-7 lists QoS deployment recommendations specific to device roles on a carrier network.

Table 3-7 QoS deployment recommendations on a carrier network

Device Traffic Priority Single- HQoS Traffic
Role Classificati Mapping Level Shaping/
on Queue Policing
Scheduling

CSG Traffic Mappings Queues are - Traffic

classificatio between scheduled by shaping is
n is DSCP and service. implemented
implemented EXP. Table as required.
by IEEE 3-8 lists the
8021p, mapping
DSCP, IP recommenda
address, and tions.
VRF, as
required.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 33

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Device Traffic Priority Single- HQoS Traffic

Role Classificati Mapping Level Shaping/
on Queue Policing
Scheduling

ASG - Mappings Queues are Queues are Traffic

between scheduled by scheduled by shaping is
EXPs of service only service (FQ), implemented
different when base station as required.
tunnels. services are (SQ), or
simple. tunnel (GQ)
when
services are
complex.
If IP
forwarding is
used, HQoS
cannot be
deployed.

RSG Traffic Mappings Queues are Queues are Traffic

classificatio between scheduled by scheduled by shaping is
n is DSCP and service only service (FQ), implemented
implemented EXP. Table when base station as required.
by IEEE 3-8 lists the services are (SQ), or
8021p, mapping simple. tunnel (GQ)
DSCP, IP recommenda when
address, and tions. services are
VRF, as complex.
required. If IP
forwarding is
used, HQoS
cannot be
deployed.

NOTE

Generally, the message, protocol packets, and real-time voice and video traffic has a higher priority than
other traffic.

Table 3-8 DSCP-EXP priority mapping recommendations

Category Traffic Quality Class DSCP EXP

Feature Identifier
(QCI)a

Radio services Radio real-time 1 46 (EF) 5

services, mainly
real-time voice 2 26 (AF32) 3
and video 3 34 (AF41) 4
traffic. The

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 34

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Category Traffic Quality Class DSCP EXP

Feature Identifier
(QCI)a

traffic is heavy 4 26 (AF32) 3

and traffic may
burst. Such 5 46 (EF) 6
traffic has high
requirements
for bandwidth,
jitter, and delay,
and cannot
endure any
packet loss.

Radio non-real- 6 18 (AF21) 2

time services,
mainly non- 7 18 (AF21) 2
real-time user 8 10 (AF11) 1
Internet access
and message 9 00 (BE) 0
traffic. The
traffic is heavy
and may burst.
Such traffic has
common
requirements
for jitter and
delay. The
minimum
bandwidth must
be available to
such traffic.

Protocol control Mainly protocol - 46 (EF) 5

packets at the
control layer.
Generally, the
traffic is light.
As a key
performance
indicator (KPI),
it has a high
delay
requirement and
cannot endure
any packet loss.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 35

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Category Traffic Quality Class DSCP EXP

Feature Identifier
(QCI)a

OM The OM man- - 46 (EF) 5

machine
language
(MML) traffic is
light and has a
high delay
requirement.

Heavy file 10 (AF11) 1

transfer
protocol (FTP)
traffic may burst
and it has low
requirements
for jitter and
delay. The
minimum
bandwidth must
be available to
such traffic.

IP clock Control packets - 46 (EF) 5

and clock
packets that
provide IP
clocks for the
entire network.
The traffic is
light but has
high
requirements
for bandwidth,
jitter, and delay.

Pass-through Generally, pass- - - -

traffic through traffic
does not need to
be additionally
processed, and
is directly
scheduled by
DSCP (carried
in the traffic)
instead.

NOTE
a: QCIs are used to identify QoS policies on the wireless side.
QoS for TDM and ATM services are follows:

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 36

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l For PW-carried TDM services, the default priority is EF and priority queuing (PQ) is used.
l For different ATM services, including voice services and data services, cbr, nrt-vbr, or rt-
vbr is configured.
NOTE

l cbr: Constant Bit Rate.

l nrt-vbr: Non Real Time-Variable Bit Rate.
l rt-vbr: Real Time-Variable Bit Rate.

3.6 Clock Synchronization

Radio networks have high requirements for frequency and time synchronization, but GPS
deployment causes high costs. To solve the problem, Huawei provides multiple technologies
such as 1588v2, synchronous Ethernet, 1588 ACR, and IP clock to provide high-precision
frequency and time synchronization signals for radio base stations over the carrier network.

Radio networks have high requirements for frequency and time synchronization as shown in
Table 3-9.

Table 3-9 Clock requirements of radio networks

Radio Mode Requirements for Requirements for Time

Frequency Synchronization
Synchronization

GSM 0.05 ppm -

WCDMA 0.05 ppm -

TD-SCDMA 0.05 ppm +/-1.5 us

CDMA2000 0.05 ppm +/-3 us

WiMax FDD 0.05 ppm -

Wimax TDD 0.05 ppm +/-0.5 us

LTE FDD 0.05 ppm - (MBSFN requires +/-1 us.)

NOTE
MBSFN：Multimedia
Broadcast multicast service
Single Frequency Network.

LTE TDD 0.05 ppm +/-1.5us

This solution supports several clock synchronization technologies: 1588v2, synchronous

Ethernet, 1588ACR, and IP clock. Table 3-10 lists the suggestions for clock synchronization
deployment. Deploy clock synchronization based on the actual network situations.

NOTE

Deploying two BITSs for redundancy is recommended. If there are excessive hops on the carrier network,
other BITSs can be deployed in the downstream to improve precision.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 37

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Table 3-10 Suggestions for clock synchronization deployment

Technology Frequency Time Use Scenario Deployment
Synchronizati Synchronizati Suggestion
on on

1588v2 Supported Supported. Deploying During

1588v2 is deployment:
recommended if l CSGs,
the entire ASGs, and
network RSGs are
requires deployed as
frequency and boundary
time clocks
synchronization (BCs).
and supports the
same 1588v2. l No VPN
needs to be
deployed.
l Clock
services
have the
highest QoS
priority.

Synchronous Supported Not supported. Deploying During

Ethernet GPS needs to be synchronous deployment:
deployed Ethernet is l Synchronou
separately. recommended if s Ethernet is
the entire deployed on
network CSGs,
requires only ASGs, and
frequency RSGs.
synchronization
and supports the l No route,
same VPN, or QoS
synchronous needs to be
Ethernet. deployed.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 38

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Technology Frequency Time Use Scenario Deployment

Synchronizati Synchronizati Suggestion
on on

1588ACR Supported Not supported. If only During

GPS needs to be frequency deployment:
deployed synchronization l The public
separately. is required and network
the frequency routes
signals need to between the
traverse other 1588 ACR
devices that do server and
not support 1588 ACR
IEEE 1588v2 or client are
synchronous reachable.
Ethernet, 1588
ACR is l No VPN
recommended. needs to be
If 1588 ACR is deployed.
deployed, l Clock
proper services
intermediate have the
network quality highest QoS
must be also priority.
ensured. l Proper
intermediate
network
quality must
be also
ensured.

IP clock Supported Not supported. Deploying IP During

GPS needs to be clock is deployment:
deployed recommended if l 1588 packets
separately. the entire are carried in
network separate
requires only VRFs or
frequency PWs
synchronization between the
and if not all IP clock
devices (except server and IP
CSGs and clock client.
RSGs) are
manufactured l Clock
by the same services
manufacturer or have the
transit nodes do highest QoS
not support priority.
1588v2 or
synchronous
Ethernet.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 39

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

3.7 Operation and Maintenance

Future networks will be doubtlessly IP-based and more versatile mobile data services will be
available, which means increasingly complex network maintenance. A qualified operation and
maintenance (O&M) system must handle more flexible configurations and fault detection for
multiple types of services while the operational expenditure (OpEx) is maintained at a reasonable
level.

O&M Solution Overview

An IP-based mobile bearer network imposes the following challenges on O&M:
l The network management system must have a great management capacity and must be
stable and easy-to-use.
l New deployment commissioning for case-shaped devices must be simple, without the need
to perform on-site software commissioning.
l Service provisioning must be easy.
l Tight schedule of network construction requires highly efficient deployment and service
provisioning.
l Complex access technologies and various bearer channels require that the E2E service
provisioning system support E2E provisioning and management for services in all types of
bearer channels.
l Mobile bearer networks require high reliability, so the management system must provide
strong support for protection detection mechanisms, real-time network monitoring, and
fault diagnosis.
l Rapid development of mobile services involves frequent expansion at the access layer and
re-homing of base transceiver stations (BTSs). This requires a simple capacity expansion
and trail cutover to minimize impact on live-network services.

The MBB V600R002 provides a comprehensive O&M solution for mobile bearer networks, as
shown in the following figure.

Figure 3-22 procedure for O&M solution

U2000 IP plug-and -play
U2000 U2000
Network Network Routine Network expansion
design deployment maintenance and adjustment

U2000 U2000
Fault Service
management provisioning
U2000/DC U2000
Performance NE
management maintenance

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 40

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l To construct a new network, Huawei engineers provide a data plan according to which the
U2000 IP plug-and-play and U2000 work together to deploy the network.
l The U2000 is also recommended for routine maintenance, including fault management,
service provisioning, performance management, and NE maintenance.
l Mobile service providers whose services are increasing have to expand and adjust their
networks frequently.

NMS DCN
The NMS data communication network (DCN) is a network consisting of the NMS, NEs, and
lines and available routes between the NEs. The NMS can manage ATN and CX devices if there
are available routes between them. The major NMS DCN solutions include:
l DCN public network solution: applies to scenarios where DCN services do not need to be
isolated from other services.
l DCN local virtual routing and forwarding (VRF) solution: applies to scenarios with DCN
isolation requirements.
The DCN public network and DCN Automatically Available solutions are described below:
l DCN Public Network Solution

Figure 3-23 Network topology of the DCN public network solution

The NMS connects to the public network and remotely accesses the NEs on the public
network through available public network routes between the NEs.
l DCN Automatically Available Solution

Figure 3-24 Network topology of the DCN automatically available solution

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 41

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

In the DCN automatically available solution, the NMS communicates with gateway NEs
using DCN VPN instances and automatically discovers non-gateway NEs through DCN
packets transmitted from gateway NEs.
The following table describes MBB DCN solution.

Scenario Priority DCN Solution

Hierarchy VPN for all Recommended Public network solution

services
Recommended DCN Automatically
Available solution

Typical DCN networking includes self-established DCN, DCN traversing a Layer 2 network,
and DCN traversing a Layer 3 network.
l Self-established DCN

Figure 3-25 Network topology of a self-established DCN

A self-established DCN is a network or subnet that contains only ATN or CX devices

without any other devices or networks between them and their rendezvous points. A DCN
that traverses a physical layer network (such as a WDM network) is also a self-established
DCN. Both the DCN Automatically Available and DCN public network solutions support
the self-established DCN.
l DCN traversing a Layer 2 network

Figure 3-26 Network topology of a DCN traversing a Layer 2 network

As shown in the preceding figure, the DCN contains Huawei and non-Huawei devices and
traverses a third-party Layer 2 network. If the third-party Layer 2 network provides only a
public network VLAN for the DCN, the DCN public network solution is recommended. If
the third-party Layer 2 network provides an independent VLAN for the DCN and DCN
services need to be isolated from other services, the DCN Automatically Available solution
is recommended.
l DCN traversing a Layer 3 network

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 42

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Figure 3-27 Network topology of a DCN traversing a Layer 3 network

As shown in the preceding figure, the DCN contains Huawei and non-Huawei devices and
traverses a third-party Layer 3 network. Generic routing encapsulation (GRE) tunnels can
be configured to forward DCN services as Layer 3 virtual private network (L3VPN)
services to manage the NEs. Alternatively, the NMS can directly access the public network
interface on the Layer 3 network to manage the NEs.

Network Design
Network design includes two phases: high level design (HLD) and low level design (LLD).
l In the HLD phase, output HLD documents based on customer requirements.
– To understand customer requirements and set up the network correctly, perform the
following operations:
– Collect information about customer live networks and new sites to be added.
– Understand the development trend of customer services and analyze service
expansion capacity.
– Output the technical solution in slides and documents based on the collected
information.
– After the technical solution is approved, output the bill of quantity (BoQ).
l In the LLD phase, output LLD documents based on the customer requirements and HLD
documents. The LLD documents serve as a guide for generating dynamic drive (DD) scripts
and implementing rapid network deployment.

Network Deployment
The plug-and-play plan is used to deploy networks. With the plug-and-play plan, the NMS uses
the Dynamic Host Configuration Protocol (DHCP) to automatically configure new devices,
implementing remote and centralized device commissioning. The software commissioning frees
O&M engineers from on-site software commissioning, therefore reducing cost and improving
deployment efficiency.

The plug-and-play deployment plan is as follows:

l Huawei engineers or software commissioning personnel provide the data plan based on
which the U2000 IP plug-in-play generates basic device configuration scripts.
l Hardware installation personnel install devices according to slot layout and fiber/cable
connection diagrams provided by the U2000 IP LCT, and power on devices.
NOTE

l ATNs, which are plug-in-play, can be deployed using the DHCP of the U2000 IP plug-in-play, which
frees O&M engineers from on-site software commissioning.
l CXs must be commissioned on site. After the U2000 IP plug-in-play configures templates, and
generates and exports scripts, engineers issue the scripts to devices on site.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 43

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

l Hardware installation engineers install devices according to the rack panel diagram and
fiber connection diagram and power on the devices.
l The devices automatically request IP addresses from the U2000 plug-and-play. The U2000
plug-and-play assigns IP addresses according to the imported plug-and-play planning sheet.
Then the devices automatically configure interface IP addresses and enable remote Telnet
channels.
l After the remote Telnet channels are enabled, the IP LCT issues scripts to devices,
configures basic services for online devices, and enables management channels. The U2000
uses the IP addresses of management channels to discover NEs and links, and synchronizes
data to set up the network topology quickly for subsequent service provisioning.

Routine Maintenance
Users can perform routine maintenance on the U2000 for mobile bearer networks, including
fault management, service provisioning, performance management, and NE maintenance.

l Fault management: includes fault monitoring and fault handling.

– Fault monitoring: The U2000 provides two fault monitoring methods: monitoring NE
and link status in the topology view and monitoring alarms of network-wide NEs.
– Fault resolution: Huawei provides the U2000 for diagnosing faults and SmartKit for
collecting fault information.
– The U2000 can locate faults using alarms and the trail visualization function in the
topology view. Fault diagnosis methods vary with the manners in which the faults
are detected. For faults detected during alarm monitoring, locate the faults according
to troubleshooting suggestions. For faults reported by mobile subscribers or detected
during network quality monitoring, view the alarm status of trails displayed in the
topology view.
– For faults that fail to be located or resolved, use the SmartKit to collect fault
information about suspicious NEs in a one-click manner, compress the information,
and send it to Huawei R&D engineers for root cause analysis.
l Service Provisioning: a mobile bearer network generally carries a large number of services
and many new services are provisioned daily. Therefore, service provisioning operations
must be easy and efficient.
– Manually creating services in the U2000 GUI
The following table describes the service provisioning procedure.

Step Action

1 Create a working tunnel and a protection tunnel between the user-end

provider edge (UPE) and the network-provider edge (NPE).

2 Create a tunnel protection group.

3 Test the tunnel continuity.

4 Create a PWE3, VPLS, L3VPN, or L2+L3VPN service according to

networking conditions. Bind the service to a tunnel or specify a tunnel
policy.

5 Configure QoS.

6 (Optional) Configure BFD for PWs.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 44

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

Step Action

7 Check whether services are running properly and test the service continuity.

Manually creating services in the U2000 applies to the networks where fewer than 50
services are provisioned per person-day and GUI-based U2000 is mainly used in service
provisioning and management.
– Provisioning services using the OSS
After the U2000 is connected to the OSS, users can provision services on the OSS
without performing operations on the U2000. The XML northbound interface (NBI)
supports service provisioning by site. Carriers whose OSSs are fully developed can use
the OSSs to provision services.
l Performance management: helps discover and resolve network resource deterioration to
prevent network faults.
Devices and the U2000 provide different performance indicators for monitoring physical
and logical objects, as shown in the following figure. Focus on performance indicators for
the blue objects during routine performance monitoring.

Figure 3-28 Performance indicators

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 45

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview 3 Implementation of the ATN+CX Hierarchy VPN Solution

A mobile bearer network contains many logical objects to be managed. For example, one
RSG device may carry thousands of tunnels and PWE3 services. If they are all monitored
and service level agreement (SLA) indicators are collected every five minutes, the RSG
CPU will be overloaded and the U2000 performance will degrade. In addition, service fault
information is often reported by the wireless network rather than being detected during
routine performance deterioration analysis. Therefore, service-based performance
monitoring applies mainly to the network evaluation phase.
l NE maintenance: ensures that system configurations can be restored if a fault occurs. The
most frequent operation to prevent data loss is backing up the U2000 and NE databases.
O&M operations also include device software upgrade during network optimization or
reconstruction.

Network Expansion and Adjustment

l Network expansion: includes adding BTSs to a network and deleting BTSs from a network.
– After wireless BTSs are added to a network, ATN devices need to be added to rings or
links at the access layer.
– After wireless BTSs are deleted from a network due to resident complaints or other
reasons, related ATN devices need to be removed from rings or links at the access layer.
The following operations are required after some sites are added or deleted:
– Install hardware such as devices and fibers/cables.
– Reconnect fibers and change IP addresses of upstream and downstream interfaces for
involved sites. The U2000 allows users to add or delete fibers and change interface IP
addresses to expand network capacity.
– Adjust tunnels: If tunnels are statically configured, all tunnels that traverse the involved
fibers must be adjusted manually. If tunnels are maintained dynamically, tunnels are
automatically adjusted by the router control plane according to the automatically
calculated routes after interface IP addresses are configured. The U2000 allows users
to change interface IP addresses.
l Network adjustment
Network adjustment: includes network topology adjustment and BTS re-homing.
– Network topology adjustment: This adjustment is generally required at the access layer.
For example, at the initial engineering stage, the chain topology is used at the access
layer because fibers are not in position. After all fibers are deployed, the topology is
changed to a ring topology. Relevant tunnels need to be moved to newly deployed fibers.
In dynamic networking mode, route constraints for tunnels must be modified so that
routers can reroute traffic to the newly deployed fibers. The U2000 allows users to
modify route constraints for tunnels.
– BTS re-homing: If a wireless base station controller (BSC) is overloaded, BTSs need
to be re-homed to another BSC and bearer channels in bearer networks need to be re-
homed to the new BSC.

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 46

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview A Acronyms and Abbreviations

A Acronyms and Abbreviations

Number
1588v2 1588v2
3GPP 3rd Generation Partnership Project
A
ADSL Asymmetric Digital Subscriber Line
ASG Aggregation Site Gateway
B
BC Boundary Clock
BFD Bidirectional Forwarding Detection
BITS Building Integrated Timing Supply
BMC Best Master Clock
BTS Base Transceiver Station
BSC Base Station Controller
C
CDMA Code Division Multiple Access
CE Customer Edge
CES Circuit Emulation Service
CESoPSN Circuit Emulation Services over Packet Switch Network
CPRI Common Public Radio Interface
CSG Cell Site Gateway
CRAN Centralized RAN
D
DSLAM Digital Subscriber Line Access Multiplexer

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 47

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview A Acronyms and Abbreviations

DUT Device Under Test

E
E-APS Enhanced Automatic Protection Switching
E2E End to End
EEC Ethernet Equipment Clock
ESMC Ethernet Synchronization Messaging Channel
F
FDD Frequency Division Duplex
FE Fast Ethernet
G
G.SHDSL G.991.2. Single-line High-speed Digital Subscriber Line
GM Grandmaster
GPS Global Position System
GR Graceful Restart
GSM Global System for Mobile communications
H
HMSTP Hybrid Multi-Service Transmission Platform
HQoS Hierarchical Quality of Service
I
IP MBH IP Mobile Backhaul
IPRAN IP Radio Access Network
L
LAG Link Aggregation Group
LNC Local Node Clock
LPR Local Primary Reference
LTE Long Term Evolution
M
MBB Mobile Broadband
MME Mobility Management Entity
MPLS Multiprotocol Label Switching
MPLS-TP Multiprotocol Label Switching-Transport Profile
MS-PW Multiple Segment PWE3

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 48

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview A Acronyms and Abbreviations

MSTP Multi-Service Transmission Platform

MTIE Maximum Time Interval Error
N
NMS Network Management System
NTP Network Time Protocol
NTR Network Timing Reference
O
OC Ordinary Clock
OPEX Operating Expense
P
PDV Packet Delay Variation
PEC Packet-based Equipment Clock
PON Passive Optical Network
PPS Pulse Per Second
PRC Primary Reference Clock
PTP Precision Time Protocol
PWE3 Pseudo-Wire Emulation Edge to Edge
Q
QCI QoS Class Identifier
QL Quality Level
QoS Quality of Service
R
RAN Radio Access Network
RAN CE RAN Customer Edge
RNC Radio Network Controller
RSG Radio Service Gateway
S
SAToP Structure-Agnostic Time Division Multiplexing over Packet
SDH Synchronous Digital Hierarchy
SEC SDH Equipment Clock
SGW Service Gateway
SNTP Simple Network Time Protocol

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 49

Copyright © Huawei Technologies Co., Ltd.
MBB ATN+CX(HVPN) Solution
Overview A Acronyms and Abbreviations

SOOC Slave Only Ordinary Clock

SSM Synchronization Status Message
SSU Synchonization Supply Unit
STM Synchronous Transfer Mode
STM-1 SDH Transport Module -1
SyncE Synchronous Ethernet
T
TAI International Atomic Time
TDD Time Division Duplex
TDEV Time Deviation
TDM Time Division Multiplexing
TIE Time Interval Error
TNC Transit Node Clock
TOD Time of Day
U
UE User Equipment
UTC Universal Time Coordinated
V
VPN FRR VPN Fast Reroute
VRRP Virtual Router Redundancy Protocol
VLAN Virtual Local Area Network

Issue 02 (2013-5-31) Huawei Proprietary and Confidential 50

Copyright © Huawei Technologies Co., Ltd.