Networking

SCTP is a reliable transport protocol operating on top of a connectionless packet
network such as IP. It offers the following services to its users: -- acknowledged
error-free non-duplicated transfer of user data, -- data fragmentation to conform to
discovered path MTU size,
6.1.3 Common Networking Solutions
 Eth-trunk Inface
 ARP Probe for Logical Links
 Route
 Concepts of OSPF Dynamic Routing
 BFD
 Typical Networking Solutions Between the UGW9811 and NEs
 Common combinations of networking solutions
This describes the commonly used interfaces, routing modes, and typical networking solutions
for the UGW9811 to interconnect with different network elements (NEs).
Eth-trunk Interface
If a physical interface fails, the communications between the UGW9811 and the peer device that
is connected to the UGW9811 through this physical interface also fail. This is a reliability defect
of single point interconnection between NEs. This defect can be rectified by Layer 2 reliability
networking. Multiple physical interfaces are bound to one Eth-trunk logical interface.
Physical interfaces in the Eth-trunk interface work in active/standby mode or load-sharing mode.
For details, see Table 1.
Table 1 Details about the Eth-trunk interface

Active/Standby Mode Load-sharing Mode
Only one link is active, whereas other links Multiple links are active and share the data
are standby. streams.
Multiple Ethernet physical interfaces are Multiple Ethernet physical interfaces are bound
bound to one Eth-trunk interface. These to one Eth-trunk logical interface. These
physical interfaces share one IP address, and physical interfaces share one IP address and
only one interface is active. If the active multiple links work in active mode to share
physical interface fails, the system data streams. When one physical interface
automatically switches to a standby physical fails, the links of other available physical
interface. interfaces automatically take over the traffic.
Networking Diagrams
Figure 1 Networking of physical interfaces in Figure 2 Networking of physical interfaces in
an Eth-trunk interface working in an Eth-trunk interface working in load-sharing
active/standby mode mode
Table 1 Details about the Eth-trunk interface
Active/Standby Mode Load-sharing Mode
Networking Description
On the UGW9811, two physical interfaces are On the UGW9811, two Eth-trunk logical
bound to one Eth-trunk interface and they interfaces work in load-sharing mode and each
work in active/standby mode. Eth-trunk interface is bound with three
physical interfaces. The three physical
 The two physical interfaces are located interfaces in each Eth-trunk interface are:
on different LPUs.
 Each of the two physical interfaces is  Located on the same LPU.
connected to one LAN Switch.  Connected to the same LAN Switch.
 The two physical interfaces have the  Sharing the same IP address, that is, the
same IP address, that is, the IP address IP address of the Eth-trunk interface.
of the Eth-trunk interface.
When the link between the Ethernet1/0/1
Ethernet1/0/1 and Ethernet2/0/1 are the active interface on the UGW9811 and LAN Switch-1
and standby interfaces of the UGW9811 fails, the links of the Ethernet1/0/2 and
respectively. If the link between Ethernet1/0/1 Ethernet1/0/3 interfaces automatically take
and LAN Switch 1 fails, the UGW9811 over the traffic.
enables Ethernet2/0/1 and then switches to the
link between Ethernet2/0/1 and LAN Switch
2.
Remarks
Once the active/standby mode is adopted on To further enhance reliability, two Eth-trunk
the Eth-trunk interfaces, you cannot disable interfaces in load-sharing mode can be backups
this mode unless the networking mode is for each other. See Figure 2. The UGW9811
changed; otherwise, the system fails. connects to LAN Switch 1 through Eth-trunk 1
and connects to LAN Switch 2 through Eth-
The Layer 2 networking requires routers or trunk 2. The two Eth-trunk interfaces in load-
switches supporting the Layer 2 exchange sharing mode are backups for each other. If the
function. On the peer router or LAN Switch, a link between Eth-trunk 1 and LAN Switch 1
pair of active and standby interfaces must fails, the UGW9811 switches to the link
belong to the same network segment or virtual between Eth-trunk 2 and LAN Switch 2. This
local area network (VLAN). scheme is implemented through route
redundancy.
ARP Probe for Logical Links
To improve the reliability of Layer 2 networking, the UGW9811 adopts the Address Resolution
Protocol (ARP) probe mechanism. For details, see GWFD-011000 Reliability.
Route
Table 2 lists the common static routing and OSPF dynamic routing modes from the UGW9811 to
interconnected NEs.
Table 2 Routing description

Static Routing Dynamic Routing
Static routing is applicable to the Dynamic routing is applicable to the network with a
small stable network with a simple complex topology and a certain number of Layer 3
topology. devices, which can automatically adapt to changes in the
network topology.
In a relatively simple network, you
need to configure only static routes The UGW9811 supports dynamic routing protocols such
to enable routers to work normally. as Routing Information Protocol (RIP), Open Shortest
Proper configuration and usage of Path First (OSPF), Intermediate System-to-Intermediate
static routes can improve network System (IS-IS), and Border Gateway Protocol (BGP).
performance and ensure the required The OSPF dynamic routing mode is taken as an
bandwidths for important example.
applications.
Attributes of Routes
 Reachable routes  Multi-process
Normal routes are of this Multiple OSPF processes can run on an NE.
type. That is, IP packets are These processes independently run and do not
sent to the next hop through affect each other. The routing interaction
the static route to the between different OSPF processes can be
destination. regarded as the routing interaction between
different routing protocols. An interface on the
 Black hole routes UGW9811 can belong to only one OSPF
process.
When a static route to a
destination has the  Packet authentication
BLACKHOLE attribute, all
IP packets to this destination OSPF supports packet authentication. Only the
are discarded, and the source authenticated OSPF packets can be received;
host is not informed of packet otherwise, the neighbor relationship cannot be
discarding. established normally.
The UGW9811 supports both area authentication

and interface authentication. When both
authentication modes are available, interface
authentication is used.
 Hot backup
The device in distributed structure supports
OSPF hot backup. In OSPF hot backup, essential
information on the active SRU/MPU is backed
up to the standby SRU/MPU. When the active
SRU/MPU is faulty, the standby SRU/MPU
becomes the active SRU/MPU. This ensures the
normal running of OSPF.
The UGW9811 supports two hot backup modes:
o Backing up all OSPF data: In this mode,

the OSPF function is immediately
restored to the normal state after the
active/standby switchover of
SRU/MPUs.
o Backing up only OSPF configurations:
When the active/standby switchover of
SRU/MPUs occurs, OSPF graceful
restart (GR) is performed. The
UGW9811 obtains the neighbor lists
from its neighboring routers and then
performs link state database (LSDB)
synchronization.
 OSPF GR
GR is used to gracefully restart a router. This

function prevents traffic forwarding interruption
and route flapping when the router is restarted in
a short period.
If OSPF is not restarted in GR mode on a router,

the information about this router is deleted from
the neighbor lists on its adjacent routers and a
notice is sent to other routers. As a result, the
shortest path first (SPF) re-calculation is
performed. If OSPF is restarted in a short period,
route flapping occurs.
 Multiple OSPF instances
OSPF supports multiple instances that can run

between the provider edge (PE) and customer
edge (CE) of a VPN. You can set area IDs on the
PE to differentiate the VPNs that different sites
belong to. The sites of the same VPN are
considered directly connected with each other.
Thus, the PEs can exchange OSPF route
information through a dedicated line. This
improves network management and OSPF
application efficiency.
Concepts of OSPF Dynamic Routing
Table 3 lists concepts of OSPF dynamic routing.
Table 3 Concepts of OSPF dynamic routing

Concept Description
OSPF process To start multiple OSPF processes on the UGW9811, you must specify
number different OSPF process numbers. The OSPF process number is a concept of
the local UGW9811 and it does not impact the packet exchange between the
UGW9811 and other routers. Therefore, routers can exchange packets
regardless of different process numbers.
ROUTER ID A router ID must exist for a router to run OSPF. A router ID is a 32-bit
unsigned integer. It uniquely identifies a router in an autonomous system
(AS).
You can manually set a router ID. Generally, the router ID is set as the IP
address of an interface on the router.
If you do not specify the router ID, the system automatically selects an IP
address of the existing interface as the router ID. The highest IP address of
loopback interfaces is selected as the router ID. If no loopback interface is
configured, the highest IP address of the interfaces is selected as the router
ID.
Area You must specify an area to which an interface running OSPF belongs.
OSPF processes can share an area. For example, area 0 can be used by both
OSPF 1 and OSPF 2.
Area OSPF supports packet authentication. Only the authenticated OSPF packets
authentication can be received; otherwise, the neighbor relation cannot be established
normally.
Table 3 Concepts of OSPF dynamic routing
Concept Description
All the routers in the area must agree on the same area authentication mode
and password.
OSPF network This network segment refers to the network segment of the IP addresses of
segment an interface that runs OSPF. A network segment can belong to only one area.
That is, you must specify an area for each interface running OSPF. OSPF can
be run on an interface only when the following conditions are satisfied::
 The length of the IP address subnet mask of an interface is not shorter

than that specified by using the network command.
 The primary IP address of an interface must be in the range of the
network segment specified by using network.
DR priority When configuring broadcast networks or non-broadcast multiple access

(NBMA) networks, you can specify the designated router (DR) priorities of
interfaces to determine the DR/backup designated router (BDR) election on
the network. A larger value indicates a higher priority. If the priority of a
router is 0, this router cannot be elected as the DR or BDR.
BFD
Deployed on the LPU, the Bidirectional Forwarding Detection (BFD) functions implemented on
the UGW9811 are as follows:
 Supporting single-hop and multi-hop detection.

 Supporting the asynchronous detection mode rather than the demand detection mode.
 Supporting static BFD sessions and static_auto BFD sessions rather than auto BFD
sessions.
 Port: A BFD session can be bound to a local Layer 3 interface. The interface can be an
Ethernet physical interface or a logical interface such as the Eth-trunk, VLAN If, or sub-
interface.
 Route: BFD sessions can be bound to static routes and OSPF routes.
 Interface: All service logical interfaces such as Ga and SGi interfaces on the UGW9811
support BFD.
For details, see GWFD-111004 BFD Function and GWFD-011000 Reliability.
Typical Networking Solutions Between the UGW9811 and NEs
Table 4 lists the typical networking solutions between the UGW9811 and interconnected NEs.
Table 4 Recommended UGW9811 networking solutions
Interconnected Single Group Recommended Backup
NE Logical Logical Networking Solution Networking
Interface Interface Solution
eNodeB S1-U Saif Networking of Eth- Networking of
trunk Interfaces in Eth-trunk Interface
MME S11
Static LACP in Active/Standby
RNC S12 Mode+OSPF Dynamic Mode+Static
Routing Routing
S4-SGSN S4
P-GW S5_p Paif
S-GW S5_s
Non-3GPP S2a
S2b
AAA Server S6a -
PDN SGi
CG Ga - Networking of Eth- -
trunk Interface in
OCS Gy
Active/Standby
PCRF Gx Mode+Static Routing
OM network OM
Report Server Grp
Common combinations of networking solutions
Networking of Eth-trunk Interface in Active/Standby Mode+Static Routing

This networking solution is recommended for the UGW9811 to interwork with the
operation and maintenance (O&M) network, charging gateway (CG), online charging
system (OCS) server, policy and charging rules function (PCRF), and report server.
Networking of Eth-trunk Interfaces in Static LACP Mode+OSPF Dynamic Routing
This networking solution is used for the UGW9811 to interwork with the serving GPRS
support node (SGSN), evolved NodeB (eNodeB), mobility management entity (MME),
serving gateway (S-GW), PDN gateway (P-GW), and packet data network (PDN).
Networking of Dual Active Interfaces+Static Routing+BFD
This networking solution is used for the UGW9811 to interwork with the evolved NodeB
(eNodeB), packet data network (PDN), online charging system (OCS) server, charging
gateway (CG), policy and charging rules function (PCRF), and operation and
maintenance (O&M) network.
VPN Networking
This networking solution is used for the UGW9811 to interwork with all network
elements (NEs).
Parent Topic: Networking Description
Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.
< Previous topic
6.1.3.1 Networking of Eth-trunk Interface in

Active/Standby Mode+Static Routing
 Networking Advantages
 Networking Solutions of the GE Interface
 Networking Solution of the 10GE Interface
This networking solution is recommended for the UGW9811 to interwork with the operation and
maintenance (O&M) network, charging gateway (CG), online charging system (OCS) server,
policy and charging rules function (PCRF), and report server.
Networking Advantages
 A default route is configured, which minimizes the route configuration. The number of
routes is small, which reduces the impact on performance.
 Eth-trunk interfaces work in active/standby mode. When a member link fails, the traffic
is automatically switched to another available link.
 Address Resolution Protocol (ARP) probe is used to enhance networking reliability. This
is to prevent interrupted communications caused by the member link faults that cannot be
detected, such as one way and probabilistic packet loss.
Networking Solutions of the GE Interface
Figure 1 shows the networking of the GE interface and static routing. Figure 2 shows the reliable
networking by using a Layer 3 device.
Figure 1 Networking of the GE interface and static routing

Figure 2 Reliable networking of the GE interface
Networking Solution of the 10GE Interface
Layer 3 networking is recommended for the 10GE interface on the UGW9811. See Figure 3.
Figure 3 Networking of the 10GE interface
Parent Topic: Common Networking Solutions

Next topic >
< Home
6.1.3.2 Networking of Eth-trunk Interfaces in

Static LACP Mode+OSPF Dynamic Routing
This networking solution is used for the UGW9811 to interwork with the serving GPRS support
node (SGSN), evolved NodeB (eNodeB), mobility management entity (MME), serving gateway
(S-GW), PDN gateway (P-GW), and packet data network (PDN).
 Open Shortest Path First (OSPF) dynamic routing is applicable in a network with the
complex topology and many devices and IP routes. For example, OSPF routes apply to
the situation in which there are a large number of eNodeBs, the Gp/S8 interface involves
inter-network roaming, and interworking with a packet data network (PDN) is required.
 A Not-So-Stubby Area (NSSA) is configured. In the NASSA, autonomous system (AS)
external routes (described by five types of LSAs) and inter-area routes (described by
three types of LSAs) are not allowed to be imported. This is to reduce routing table
entries on the UGW9811.
 Multiple GE/10GE physical interfaces are bound to an Eth-trunk interface and use the
same IP/MAC address. The physical interfaces that are bound to the Eth-trunk interface
work in load-sharing mode. In this situation, when the traffic volume increases, you
simply need to add physical interfaces to the Eth-trunk interface and do not need to add
IP addresses or change route configurations for the UGW9811 and the peer devices that
are directly connected to the UGW9811. Therefore, this networking has good
expansibility.
 Downlink routes to the UGW9811 do not need to be manually configured on provider
edges (PEs) or customer edges (CEs), because OSPF routes are automatically advertised
and learned. The UGW9811 dynamically generates downlink routes for a subscriber
address pool. Therefore, when the capacity of the address pool is expanded, the
UGW9811 advertises the routes using dynamic route configurations, thereby reducing the
heavy maintenance workload.
 In this networking solution, Layer 1/Layer 2/Layer 3 reliability can be guaranteed for the
UGW9811.
o At Layer 1, the auto-negotiation mode configured for GE optical ports and Local
Fault (LF)/Remote Fault (RF) defined by IEEE 802.3ae for 10GE ports are used
to detect physical layer faults (such as single-fiber faults).
o At Layer 2, Link Aggregation Control Protocol (LACP) detection is used to detect
link layer faults.
o At Layer 3, Bidirectional Forwarding Detection (BFD) is used to detect IP layer
faults.
Figure 1 shows the networking between the UGW9811 and a Layer 2 device. Figure 2 shows the
networking between the UGW9811 and a Layer 3 device.
Figure 1 Networking of the interconnection between the GE interface on the UGW9811 and a
Layer 2 device
Figure 2 Networking of the interconnection between the GE interface on the UGW9811 and a
Layer 3 device

< Previous topic Next topic >
< Home
6.1.3.3 Networking of Dual Active

Interfaces+Static Routing+BFD
This networking solution is used for the UGW9811 to interwork with the evolved NodeB
(eNodeB), packet data network (PDN), online charging system (OCS) server, charging gateway
(CG), policy and charging rules function (PCRF), and operation and maintenance (O&M)
network.
 Two static default equal-cost routes are manually configured, which minimizes the route
configuration. Different interfaces are isolated using a virtual private network (VPN), and
a default route is configured for each interface.
 Multiple GE/10GE physical interfaces are bound to an Eth-trunk interface and use the
same IP/MAC address. The physical interfaces that are bound to the Eth-trunk interface
work in load-sharing mode. In this situation, when the traffic volume increases, you
simply need to add physical interfaces to the Eth-trunk interface and do not need to add
IP addresses or change route configurations for the UGW9811 and the peer devices that
are directly connected to the UGW9811. Therefore, this networking has good
expansibility.
 The Bidirectional Forwarding Detection (BFD) function is deployed on the LPU.
Forwarding services are not affected when the active and standby SRUs/MPUs are
switched.
 In this networking solution, Layer 1/Layer 2/Layer 3 reliability can be guaranteed for the
UGW9811.
o At Layer 1, the auto-negotiation mode configured for GE optical ports and Local
Fault (LF)/Remote Fault (RF) defined by IEEE 802.3ae for 10GE ports are used
to detect physical layer faults (such as single-fiber faults).
o At Layer 2, Link Aggregation Control Protocol (LACP) detection is used to detect
link layer faults.
o At Layer 3, Bidirectional Forwarding Detection (BFD) is used to detect IP layer
faults.
Figure 1 shows the networking of the GE interface and static routing. Figure 2 shows the reliable
networking by using a Layer 3 device.
Figure 1 Networking of the GE interface and static routing
Figure 2 Reliable networking of the GE interface


< Home
6.1.3.4 VPN Networking

 Constructing a VPN by Creating VRF
 Constructing a VPN Through Tunnels
 Typical Application Scenarios
 Inband or Outband Networking with the AAA Server
 Implementation of IPv6 on the UGW9811
This networking solution is used for the UGW9811 to interwork with all network elements
(NEs).
 Address separation
The address space of a virtual private network (VPN) is separated from address spaces of
its public packet switched network (PPSN) and other VPNs. That is, the address of a host
inside the VPN is invisible to its PPSN and other VPNs. Address overlapping is allowed.
 Data security
No data exchange occurs between the VPNs or between a VPN and its PPSN.
 Reachability inside a VPN
Inside a VPN, when two hosts in different places communicate, the VPN edge device
selects a proper link on its PPSN. The data stream is therefore sent from a VPN edge
device to another VPN edge device.
Constructing a VPN by Creating VRF
Virtual routing forwarding (VRF) is used to logically divide a physical device and is a method of
constructing a VPN. Each VRF has an independent routing table and address space.
On the UGW9811, VRF is represented as VPN instances. With VPN instances, you can virtually
divide a router into multiple independent routers and then separate the routes on an IP network.
By creating VRF on the UGW9811, you can separate routes of a VPN from routes of a public
network and from those of another VPN.
The advantages of configuring a VPN by creating VRF are as follows:
 Each VRF has an independent routing table. Therefore, routing tables of different VPNs
do not affect each other.
 Each VRF has an independent address space. Address conflict does not occur on VPNs of
the same device.
 Each VRF can be bound with multiple interfaces. The interfaces can be physical
interfaces or logical interfaces (such as the tunnel interface).
On the UGW9811, you can configure the mappings between access point names (APNs) and
VPN instances. In this manner, you can separate the addresses and routes of users of different
APNs. See Figure 1. When a user accesses the UGW9811, the UGW9811 matches the VPN
instance of the APN according to the APN carried in the user activation message. Then, the
UGW9811 forwards uplink and downlink packets of the user according to the routing table of
the VPN.
Figure 1 Diagram of separating routes of different network segments through VPN instances
Constructing a VPN Through Tunnels
Apart from creating VRF, you can also construct a VPN through tunnel routes. The commonly
used tunnels include Generic Routing Encapsulation (GRE), IP Security Protocol (IPSec), and
Layer 2 Tunneling Protocol (L2TP) tunnels.
In this solution, you must create an enterprise dedicated tunnel between the UGW9811 and the
VPN gateway of the enterprise. This tunnel is not bound with any APN. The service procedure is
as follows:
1. On the UGW9811, configure routes to the intranet and configure the interface at the peer
end of the tunnel as the output interface.
2. The UGW9811 transmits the VPN data to the intranet according to the route. Otherwise,
the UGW9811 forwards the user data to the Internet.
NOTE:
Address space of different enterprise users may overlap because most of the network addresses
for enterprise users are private network addresses. Therefore, the tunnel technology is required
together with the VRF technology, so that route tables can be segregated and address space of
different VPNs can be reused. In this case, the interfaces bound to the VPN are tunnel interfaces.
Typical Application Scenarios
Table 1 lists the typical application scenarios for the VPN networking.
Table 1 Typical application scenarios for the VPN networking

Typical Interconnected NE Application Description
Application
Scenario
Common VPN All NEs In most cases, VRF is used for the VPN
access (VRF) networking of the interconnection between the
UGW9811 and an NE. On the UGW9811:
 Configure associated VRF for the VPN.

 Bind APNs to the VRF.
 Bind interfaces in a VPN to the VRF.
GRE tunnel AAA server and PDN GRE tunnels are the most commonly used tunnels
access and are mainly applied to:
NOTE:
 Intranet using private network addresses
The location of the AAA for communications.
server affects the  Terminals remotely accessing the intranet
network topology and over the public network.
route planning.
IPSec tunnel If enterprise users have high security requirements,
 If the AAA
access you can use the IPSec tunnels to construct the
server is located
VPN. IPSec tunnels are mainly applied to:
in an intranet,
you can
 Intranet using private network addresses
configure only
for communications.
one VPN on the
 Terminals remotely accessing the intranet
UGW9811.
over the public network.
 If the AAA
server is located
NOTE:
on the bearer
network, you
must configure To ensure the transmission security, the
an independent UGW9811 encrypts the packets transmitted over
VPN for the the public network by using IPSec.
AAA server on
the UGW9811.
Table 1 Typical application scenarios for the VPN networking
Typical Interconnected NE Application Description
Application
Scenario
For details, see Inband
or Outband Networking
with the AAA Server.
L2TP tunnel PDN The UGW9811 provides enterprise users with
access L2TP tunnels to access the VPN. On the
UGW9811:
 The UGW9811 serves as the L2TP access

concentrator (LAC) of an L2TP tunnel.
 Each intranet APN can be bound with an
L2TP group. Each L2TP group can be
configured with two primary/secondary IP
addresses for the LNS. The UGW9811
sends Hello packets to check the
availability of the tunnel. When the active
tunnel is faulty, the UGW9811 sets up an
L2TP tunnel to the standby LNS.
 The local IP address of the L2TP tunnel is
the IP address of the SGi interface bound
to the VRF of the intranet APN. Therefore,
if L2TP can be activated on multiple
instance
s of the UGW9811, multiple SGi interfaces

are required. Each interface requires a
public IP address as the LAC IP address of
the L2TP tunnel.
IPv6 over IPv4 When the UGW9811 needs to access a service
tunnel access server on an IPv6 network, IPv6 is required for the
interworking. The UGW9811 can currently
interwork with only IPv6 isolated islands through
tunnels rather than interwork with IPv6 networks
directly.
For details, see Implementation of IPv6 on the

UGW9811.
Inband or Outband Networking with the AAA Server

Two networking solutions between the UGW9811 and the AAA server are present, namely,
inband networking and outband networking. Figure 2 shows the networking solutions. Table 2
lists the application descriptions.
Figure 2 Inband or outband networking with the AAA server
Table 2 Application description of inband or outband networking with the AAA server
Inband Networking Outband Networking
For the RADIUS signaling packets from For the RADIUS signaling packets from an APN to
an APN to an AAA server and data an AAA server and data packets from an APN to a
packets from an APN to a PDN, the PDN, the UGW9811 uses different output
UGW9811 uses the same output interface interfaces for route forwarding.
for route forwarding.
Any interface of a physical interface, Eth-trunk interface, sub-interface, or tunnel interface,
which serves as the next hop from the UGW9811 to the AAA server and PDN, can be used as
the output interface.
VPN Binding Method
The same VPN routes are used from the Different VPN routes are used from the UGW9811
UGW9811 to the AAA server and PDN. to the AAA server and PDN. As shown by
As shown by Inband networking in Outband networking in Figure 2, VPN1 and
Figure 2, the VPN is used to bind with the VPN2 are used for data forwarding from the
following: UGW9811 to PDN1 and PDN2 and they are
respectively bound to:
 Eth-trunk0: Specifies the output
interface from the UGW9811 to  Eth-trunk0 and Eth-trunk1: Specify the
the AAA server and PDN. output interfaces from the UGW9811 to
 Giif3/0/0: Specifies the logical PDN1 and PDN2.
interface from the UGW9811 to  APN1 to APNn: Specify all APNs on the
the AAA server. UGW9811 bound to VPN1.
 AAA server: Specifies the  APNx1 to APNxn: Specify all APNs on the
RADIUS server used by APN1 to UGW9811 bound to VPN2.
APNn users.
 APN1 to APNn: Specify all APNs VPN_Radius is used for forwarding RADIUS
on the UGW9811 bound to the signaling packets from the UGW9811 to the AAA
VPN. server and is used to bind with:
 Eth-trunk2: Specifies the output interface

from the UGW9811 to the AAA server.
 Giif3/0/0: Specifies the logical interface
from the UGW9811 to the AAA server.
Table 2 Application description of inband or outband networking with the AAA server
Inband Networking Outband Networking
 AAA server: Specifies the RADIUS server
used by APN1 to APNn and APNx1 to
APNxn users.
Implementation of IPv6 on the UGW9811
There are four IPv6 tunneling technologies supported by the UGW9811.
IPv6 over IPv4 Manual or Automatic Tunnel
On an IPv4 network, all external interfaces on the UGW9811 use IPv4 addresses, as shown in
Figure 3. The UGW9811 uses IPv4 tunnels to access IPv6 networks.
Figure 3 IPv6 over IPv4 tunnel
1. IPv6 addresses are dynamically assigned to users and user data are encapsulated into
IPv6 packets inside the UGW9811.
2. A tunnel interconnecting the UGW9811 and the IPv6 gateway is established.
3. IPv6 packets are encapsulated into IPv4 packets.
4. IPv4 packets are transmitted to the border router on the IPv6 network through manual or
automatic tunnels.
5. IPv6 packets are obtained by decapsulating IPv4 packets on the border router.
6. The destination server is routed according to IPv6 headers.
IPv6 over IPv4 GRE Tunnel
Figure 4. The UGW9811 uses IPv4 GRE tunnels to access IPv6 networks.
Figure 4 IPv6 over IPv4 GRE tunnel
1. IPv6 addresses are dynamically assigned to users and user data are encapsulated into
IPv6 packets inside the UGW9811.
3. IPv6 packets are encapsulated into GRE packets and GRE packets are encapsulated into
IPv4 packets.
4. IPv4 packets are transmitted to the border router on the IPv6 network through tunnels.
5. IPv6 packets are obtained by decapsulating IPv4 packets and GRE packets on the border
router.
6to4 Tunnel
Figure 5. The UGW9811 uses IPv4 networks to access IPv6 networks.
Figure 5 6to4 tunnel
1. 6to4 addresses are dynamically assigned to users and user data is encapsulated into IPv6
packets inside the UGW9811.
3. IPv6 packets are encapsulated into IPv4 packets and the IPv4 address to the peer router is
obtained from the 6to4 address pool. The obtained IPv4 address is filled into the IPv4
header.
4. IPv4 packets are transmitted to the border router on the IPv6 network through tunnels.
5. IPv6 packets are obtained by decapsulating IPv4 packets on the border router.

< Previous topic
< Home
6.2 Product Description
6.2 Product Description
Introduction to product description:
Product Features
This describes the features of the UGW9811:Multiple service,Support of GGSN9811-based

smooth upgrade,Carrier-class platform,high reliability, security, large capacity, and customized
operation and maintenance (OM) system.
Architecture
This describes the hardware and software structure of the UGW9811.
Configurations
This describes the typical configurations of the UGW9811.
Interfaces and Protocols
The UGW9811 complies with R99/R4/R5/R6/R7/R8//R9/R10 3GPP standards which can be

applied in EPC or GPRS/UMTS systems.
Operation and Maintenance
This describes the operation and maintenance (OM) of the UGW9811 based on the client/server
architecture.
Technical Specifications
This lists the technical specifications of the UGW9811. The technical specifications consist of
performance specifications, entire-system specifications, reliability specifications, safety
standards, electromagnetic compatibility (EMC) specifications, and environment requirements.
Environment Specifications
This describes the environmental requirements for the UGW9811. The environment
specifications consist of the storage, transportation, and running specifications.
Parent Topic: Descriptions
< Home
6.2.1 Product Features

 Multiple Service Forms Meet Requirements in Different Scenarios
 Support of UGW9811-based Smooth Upgrade
 Carrier-Class Platform Enables More Flexible Services
 High Reliability Design Ensures the Normal Operation of Products
 Security Design Protects Customer Profits
 Large Capacity
 Customized Operation and Maintenance System
This describes the features of the UGW9811:Multiple service,Support of GGSN9811-based

smooth upgrade,Carrier-class platform,high reliability, security, large capacity, and customized
operation and maintenance (OM) system.
Multiple Service Forms Meet Requirements in Different Scenarios
The UGW9811 has many logical forms and supports various types of access. This product can
meet carriers' networking requirements at different phases and in different deployment scenarios.
 Multiple types of access: supports access in GPRS, UMTS, LTE, or CDMA2000HRPD mode.
 Multiple logical product forms: The UGW9811 supports any combination of the GGSN, S-GW,
and/or P-GW. In operation and maintenance, the UGW9811 supports logical combinations of
the GGSN, S-GW + P-GW, GGSN + S-GW + P-GW.
Support of UGW9811-based Smooth Upgrade
The UGW9811 hardware platform can implement the UGW9811 functions after software
upgrade. It can better adapt to the operators' various requirements for network evolution and
service expansion, ensuring the operators' operation investments.
Carrier-Class Platform Enables More Flexible Services
The UGW9811 presents an ideal and flexible solution for wireless data communication to
network carriers. In order to achieve this, it utilizes Huawei's Universal Switching Router (USR)
hardware platform which boasts high reliability and high-level data throughput and a software
platform that seamlessly integrates wireless telecommunication technologies and data
communication technologies.
The USR is a carrier-class network switching device that is compliant with industry standards.
Developed on the basis of Huawei Versatile Routing Platform (VRP), the software of the
UGW9811 inherits the integrated routing technology, IP Quality of Service (QoS), Virtual
Private Network (VPN), and security technology of the VRP and perfects the functions specific
to applications in wireless telecommunication.
High Reliability Design Ensures the Normal Operation of Products
 Hardware reliability
The UGW9811 supports hot plugging and hot backup of key boards, possesses a double-
channel power supply system, and is protected from over-voltage and over-current.
 Software reliability
The UGW9811 is capable of overload control, traffic control, resource check, system
software backup, configuration files check and automatic fault detection. This ensures
reliable running. The unique charging data record (CDR) cache function guarantees a
reliable billing system. The hot patch technology helps to ensure the normal software
running.
 Networking reliability
The route backup and router load sharing functions can prevent single point failure on
networks, helping to build highly reliable networks. The Eth-Trunk function can prevent
failure of a single port from affecting services.
 Operation and Maintenance Reliability
SSL: The UGW9811 ensure data confidentiality for operation and maintenance.
When the UGW9811 upgrade failed, it can rollback previous version automatically. In
this way, the remote update failed service restore time can be reduce.
The UGW9811 provides the patch rollback function to ensure the reliability of running
patch.
Security Design Protects Customer Profits
The same as reliability, security is concerned by operators and end users. The requirements for
security is fully considered for the design of the UGW9811 and the following measures are
taken:
 Strict verification of operator identity

 Point-to-Point Protocol (PPP) security verification by the Password Authentication Protocol
(PAP) and Challenge Handshake Authentication Protocol (CHAP) modes
 Packet filtering and access control list (ACL) mechanism to filter packets based on preset
conditions
 Gi/SGi interface redirection function, which can offer defense against attacks that are based on
protocol packets between mobile users in one UGW9811
 The SSL feature can be implemented on the UGW9811 when the UGW9811 communicates with
the U2000 or local maintenance terminal (LMT) to enhance security through encryption. With
this feature, the man-machine language (MML) channel, binary channel, and File Transfer
Protocol (FTP) file transfer channel between the UGW9811 and the U2000 or LMT are encrypted
 The UGW9811 provides the digital signature function. The UGW9811 checks the integrity of the
software or patch upgrade package by checking digital signature files.
Large Capacity
Huawei Universal Switching Router (USR), a fifth-generation core router, is the hardware
platform of the UGW9811. In Huawei USR, the signaling/control plane is separated from the
data plane. That is, the signaling/control plane consists of multiple high-performance universal
processors. The data plane consists of multiple high-performance and high-forwarding-capability
network processors (NPs).
Customized Operation and Maintenance System
 Various Management Methods

The OM system of the UGW9811 allows you to customize a network management
system based on the network structure, management requirements, and investment scale.
Based on a client/server distributed architecture, maintenance is available through the
graphic user interface (GUI) client, centralized network maintenance interfaces, and
command line interface (CLI). The UGW9811 supports simultaneous multi-user access at
local and remote ends.
 User-Friendly GUI
The GUI helps to provide a user-friendly and convenient OM interface. Operations are
simplified through the graphic network topology view and device panel view. Frequent
operations can be performed by selecting items from the menu.
 Configuration Management
The configuration management function is performed by the command line interface

(CLI) commands provided in the local maintenance terminal (LMT) of the UGW9811.
By running the CLI commands, you can configure, modify, and query data. The
UGW9811 receives, analyzes, and runs the CLI commands, and then returns the results to
the LMT.
 Message Tracing
The UGW9811 allows signaling message tracing, data packet tracing, interface message
tracing, user message tracing, and message explanation.
Operator can create interface and user tracing tasks to monitor the signaling of the
interfaces and users of the system in real time. The stored messages including the
information about previous versions can be viewed online or offline. If a fault occurs in
the UGW9811, you can quickly and accurately locate and clear the fault through the
interface signaling tracing function.
 Customizable Performance Measurement
The UGW9811 can display performance measurement data in the form of lists and
graphics. It also supports background performance data collection.The centralized
performance management system provides a comprehensive and direct operation
environment. Operator can manage the performance of devices in the entire network.
Operator can create, modify, and query performance measurement tasks and manage the
results to learn the running status of the network and devices. The measurement results
are for performance assessment and network optimization.
 Remote Management
The UGW9811 supports various remote management functions, including online

software patching, online commissioning, remote maintenance, and dynamic data setting.
 Real-Time Fault Management
The UGW9811 can receive and display network device fault reports in real time. It
provides real-time audible or visual alarms through the topology view, alarm panel, and
alarm box. The UGW9811 provides detailed fault reports, and the fault management
system with leveled filtering functions. This enables you to determine fault causes
quickly. After determining fault causes, you can clear faults by following the instructions
provided in the online help.
 Comprehensive Online Help
The online help provides help information on the OM system and alarm handling. Thus,
you can be familiar with the operation and maintenance of the UGW9811 quickly.
Parent Topic: Product Description
Next topic >
< Home
6.2.2 Architecture
This describes the hardware and software structure of the UGW9811.
Hardware Structure
The hardware components of UGW9811 include cabinets, subracks and boards.
Software Structure
This describes the software structure of the UGW9811.
< Home
6.2.2.1 Hardware Structure

The hardware components of UGW9811 include cabinets, subracks and boards.
Cabinet
The UGW9811 uses an N68E-22 cabinet.
Subrack (PGP-16)
Subrack (PGP-X8)
Subrack (PGP-X16)
Boards
The UGW9811 consists of SRUs/MPUs, SFUs, SPUs, PEUs, STEs, MSUs, and LPUs.
Parent Topic: Architecture
Next topic >
< Home
6.2.2.1.1 Cabinet
The UGW9811 uses an N68E-22 cabinet.
The design of the cabinet complies with the International Electro Commission 297 (IEC297) and Institute
of Electrical and Electronics Engineers (IEEE) standards. A modular structure is used, facilitating capacity
expansion and maintenance. In addition, electromagnetic compatibility was fully considered in the
design of the cabinet and electromagnetic shielding interfaces are used.The UGW9811 consists of a
UGW9811 subrack and a power distribution box. Figure 1 shows the exterior of the N68E-22 cabinet.
Figure 1 Exterior of the N68E-22 cabinet
Parent Topic: Hardware Structure
Next topic >
< Home
6.2.2.1.2 Subrack (PGP-16)

Figure 1 shows the layout of components when the cabinet is fully configured.The subrack
height is 36U(1U=44.45mm=1.75inch).
Figure 1 Hardware layout of the UGW9811(PGP-16)

Figure 2 shows a typical layout of boards in the UGW9811(PGP-16)subrack.
Figure 2 Layout of boards in the UGW9811(PGP-16)subrack
MPU: Main SFU: SPU: Service PEU: Packet STE: MSU: LPU: Line
Processing Switching Processing Enforcement Smart Multi- Processing
Unit Fabric Unit Unit Unit Traffic Service Unit
Explorer Unit
< Home
6.2.2.1.3 Subrack (PGP-X8)

Figure 1 Hardware layout of the UGW9811(PGP-X8)
Figure 2 shows a typical layout of boards in the UGW9811(PGP-X8)subrack.
Figure 2 Layout of boards in the UGW9811(PGP-X8)subrack
SRU: SFU: SPU: Service PEU: Packet STE: Smart MSU: LPU: Line
Switching Switching Processing Enforcement Traffic Multi- Processing
Route Unit Fabric Unit Unit Unit Explorer Service Unit
Unit
< Home
6.2.2.1.4 Subrack (PGP-X16)

Figure 1 Hardware layout of the UGW9811 (PGP-X16)
Figure 2 shows a typical layout of boards in the UGW9811(PGP-X16)subrack.
Figure 2 Layout of boards in the UGW9811(PGP-X16) subrack
MPU: Main SFU: SPU: Service PEU: Packet STE: MSU: LPU: Line
Processing Switching Processing Enforcement Smart Multi- Processing
Unit Fabric Unit Unit Unit Traffic Service Unit
Explorer Unit
< Home
6.2.2.1.5 Boards
 SRU/MPU(Switching Route Unit)/( Main Processing Unit)
 SFU(Switching Fabric Unit)
 SPU(Service Processing Unit)
 PEU(Packet Enforcement Unit)
 STE(Smart Traffic Explorer)
 MSU(Multi-Service Unit)
 LPU(Line Processing Unit)
The UGW9811 consists of SRUs/MPUs, SFUs, SPUs, PEUs, STEs, MSUs, and LPUs.
The SRU is the core circuit board for system management. The SFU performs the data exchange
function. The SPU performs the service processing function. The PEU provides the internet
protocol service quality management (IPSQM) function. The STE provides collecting metric
statistics for evaluating user experience. The MSU provides the traffic optimization function.
The LPU provides physical interfaces that connect the UGW9811 to NEs or external networks.
SRU/MPU(Switching Route Unit)/( Main Processing Unit)
The SRU/MPU, as the main control and switching unit of the UGW9811, is responsible for
centralized control and management and data exchange. The SRU/MPUs work in 1+1 backup
mode. The SRU/MPU is composed of the main control unit, switching unit, system clock unit,
synchronous switching clock unit, and system maintenance unit. The SRU applies to a PGP-X8
subrack, and the MPU applies to PGP-16 and PGP-X16 subracks. The SRUX applies to a PGP-
X8 subrack, and the MPUX applies to a PGP-X16 subrack. The SRU in a PGP-X8 subrack
integrates the function of an SFU.
SFU(Switching Fabric Unit)
The SFU supports expeditious data exchange.
SPU(Service Processing Unit)
The SPU performs service control, user packet forwarding, flow control, QoS, and content
resolution functions. The SPUs work in load-sharing or N+1 or 1+1 backup mode. The operating
mode is defined in the license file. In 1+1 backup mode, the SPUs guarantee service reliability.
An independent SPUf/SPUf1 can be deployed to provide the following functions:
TCP optimization: uses a number of techniques, including TCP transparent proxy, skipping
slow-start, fast retransmission and fast recovery, and TCP sender algorithm optimization, to
improve the TCP transmission efficiency.
Large-scale sponsored data: The UGW9811 performs service awareness (SA) and sends Layer
3/Layer 4 information and/or uniform resource locators (URLs) to the virtual service capability
exposure function (vSCEF). The vSCEF then performs service rule matching and sends the
charging identifier to the UGW9811 for charging so that subscribers can use free-of-charge or
preferential traffic packages.
SDN-based traffic classifier function: The UGW9811 performs SA to identify data services and
matches them with service chains based on subscriber information and policies. Then the
UGW9811 forwards data flows that match service chains to the vMSE, and the vMSE forwards
the data flows to corresponding Gi-LAN services for VAS processing based on service chain
information carried in the data flows.
PEU(Packet Enforcement Unit)
The PEU provides the internet protocol service quality management (IPSQM) function. With this
function, the PEU performs the traffic shaping function for the burst traffic destined to the
eNodeBs, improving the bandwidth usage of the S1-U bearer link.
STE(Smart Traffic Explorer)
The smart traffic explorer (STE) collects IP-, transmission-, and service-layer metric statistics for
evaluating user experience through the Gi/SGi interface and analyzes the statistics.
MSU(Multi-Service Unit)
The MSU provides functions, such as video optimization and content cache. The MSU must be
used together with the LPU and SPU to achieve network optimization and content acceleration
and improve user experience of online services.
LPU(Line Processing Unit)
The LPU provides the following physical interfaces that connect the UGW9811 to external
networks:
 FE (10/100 Mbit/s) interface

 GE (1000 Mbit/s) electrical interface
 GE (1000 Mbit/s) optical interface
 10GE (10 Gbit/s) optical interface
 100GE (100 Gbit/s) optical interface
The LPU is composed of three modules: LPU module, switching network fabric adapter (FAD)
module, and physical interface card (PIC) module.
These three modules work together to quickly process and forward service data. In addition, they
maintain and manage link protocols and forwarding information base (FIB) tables.
< Previous topic
< Home
6.2.2.2 Software Structure

This describes the software structure of the UGW9811.
The software structure of the UGW9811 consists of the access management (AM), charging
management (CM), service management (SM), platform service (PS), operation and maintenance
(OM) modules,and LMT(local maintenance terminal).
Figure 1 shows the logical structure of the UGW9811.
Figure 1 Software structure of the UGW9811
UGW9811 software structures are described in Table 1.

Table 1 UGW9811 Software structures
Structure Description
AM This module performs functions such as user
access control, user authentication and
authorization, address assignment, and
PDP/bearer context management. In addition,
the UGW9811 enables multiple user access
modes.
CM This module processes charging protocols and
manages charging data records (CDRs). In
addition, the CM system works with external
charging gateways (CGs) and external
charging systems to charge users.
SM This module obtains and controls policies of
user data flows.
PS This module distributes and processes
signaling packets and data packets of the
UGW9811; it works with the relevant modules
to implement charging and service control; it
performs functions such as system support and
routing.
OM This module performs OM functions such as
data configuration management, device
management, performance management, alarm
management, and security management.
LMT Provides graphical user interfaces (GUIs).
Parent Topic: Architecture
< Previous topic
< Home
6.2.3 Configurations
This describes the typical configurations of the UGW9811.
Configuring the UGW9811:
 The UGW9811 requires only one UGW9811 subrack. The cabinet that houses the UGW9811
subrack is called the UGW9811 service cabinet.
 Firewalls and Ethernet switches are optional devices in the UGW9811 service cabinet.
Typical Configuration (PGP-16)

The UGW9811(PGP-16) supports four typical configurations: minimum configuration, 1+1 mode
maximum configuration, load-sharing mode maximum configuration, and N+1 backup mode
maximum configuration.
Typical Configuration (PGP-X8)
The UGW9811(PGP-X8) supports four typical configurations: minimum configuration, 1+1 mode
maximum configuration, load-sharing mode maximum configuration, and N+1 backup mode
maximum configuration.
Typical Configuration (PGP-X16)
The UGW9811(PGP-X16) supports four typical configurations: minimum configuration, 1+1

mode maximum configuration, load-sharing mode maximum configuration, and N+1 backup
mode maximum configuration.
< Home
6.2.3.3 Typical Configuration (PGP-X16)

 Minimum Configuration
 1+1 Active/Standby Mode
 Load-sharing Mode
 N+1 Mode
The UGW9811(PGP-X16) supports four typical configurations: minimum configuration, 1+1

mode maximum configuration, load-sharing mode maximum configuration, and N+1 backup
mode maximum configuration.
NOTICE:
The performance specifications provided in this document are assessed based on specific traffic
models. The performance specifications vary obviously with increasing everlasting bandwidth
required by PS subscribers and Darwinian development of Internet services. For network
assessment of a specific site, contact Huawei local office.
Minimum Configuration
In minimum configuration, the UGW9811(PGP-X16) supports 4,000,000 bearer contexts and 60
Gbit/s throughput (with the packet length of 1024 bytes). Table 1 shows the board numbers.
Table 1 Typical configuration when the UGW9811(PGP-X16) is in Minimum Configuration
Board Number Remarks

MPU 2 This document lists only the
basic board configuration.
SFU 4
SPU 2
LPU 2
1+1 Active/Standby Mode
In 1+1 active/standby mode, the UGW9811(PGP-X16) supports 24,000,000 bearer contexts and
360 Gbit/s throughput (with the packet length of 1024 bytes). Table 2 shows the board numbers.
Table 2 Typical configuration when the UGW9811(PGP-X16) is in 1+1 Active/Standby Mode

SFU 4
SPU 12
LPU 4
Load-sharing Mode
In load-sharing mode, the UGW9811(PGP-X16) supports 40,000,000 bearer contexts and 600
Gbit/s throughput (with the packet length of 1024 bytes).Table 3 shows the board numbers.
NOTE:
Using the load-sharing mode is not recommended.
Table 3 Typical configuration when the UGW9811(PGP-X16) is in Load-sharing Mode

SFU 4
Table 3 Typical configuration when the UGW9811(PGP-X16) is in Load-sharing Mode

SPU 10
LPU 6
N+1 Mode
In N+1 mode, the UGW9811(PGP-X16) supports 36,000,000 bearer contexts and 540 Gbit/s
throughput (with the packet length of 1024 bytes).Table 4 shows the board numbers.
Table 4 Typical configuration when the UGW9811(PGP-X16) is in N+1 Mode

SFU 4
SPU 10
LPU 6
Parent Topic: Configurations
< Previous topic
< Home
6.2.4 Interfaces and Protocols

The UGW9811 complies with R99/R4/R5/R6/R7/R8//R9/R10 3GPP standards which can be
applied in EPC or GPRS/UMTS systems.
Protocol Interfaces
Physical Interfaces
< Home
6.2.4.1 Protocol Interfaces
The UGW9811 provides multiple interfaces that comply with standard protocols.
The interfaces provided by the UGW9811 on the GPRS/UMTS network are as follows:
Figure 1 Interfaces when the UGW9811 serves as the GGSN
 Gn/Gp Interface: Gn/Gp Interface is an interface between the GGSN and the SGSN.The Gn
interface is between the GPRS support nodes (GSNs) within the same public land mobile
network (PLMN). The Gp interface is between the GSNs in different PLMNs.
 Gi Interface: Gi interface is an interface between the GGSN and the PDN. It can also serve as the
interface connecting the GGSN and the AAA server, transmitting authentication and charging
control messages.
 Ga Interface: Ga is an interface between the GGSN and the Charging Gateway Functionality
(CGF). The Ga interface runs the GTP protocol. It runs the GTP protocol to send charging data
records (CDRs) that are generated by a network element or functional entity to the CGF.
 Gy Interface: Gy is an interface between the GGSN and the online charging system/credit control
function (OCS/CCF). It communicates based on the Diameter protocol and is used for online
charging control. The UGW9811 interacts with the OCS through the Gy interface to realize credit
control for content-based charging users and non-content-based charging users.
 Gx Interface: Gx is an interface between the GGSN and the policy charging rules function (PCRF).
It communicates based on the Diameter protocol. The GGSN interacts with the PCRF through
the Gx interface to realize policy and charging control (PCC) function.
 Grp Interface: Grp interface is a Huawei proprietary interface between the GGSN and report
server. The GGSN uses the Grp interface to interwork with the report server to implement the
mobile broadband (MBB) visibility function.
 Gcf Interface: Gcf interface is a Huawei proprietary interface between the GGSN and Internet
Content Adaptation Protocol (ICAP) server. The GGSN uses the Gcf interface to interwork with
the ICAP server to implement the uniform resource locator (URL) filtering function.
 Gnr Interface: Gnr interface is a Huawei proprietary interface between the GGSN and eLog
server. The GGSN uses the Gnr interface to interwork with the eLog server to implement the
NAT logs report function.
The interfaces provided by the UGW9811 on the EPC network are as follows:
Figure 2 Interfaces when the UGW9811 serves as the S-GW or P-GW
 S1-U Interface: S1-U interface is an interface in the user plane between the eNodeB and the S-
GW. It is used to transmit the uplink and downlink user plane data between the eNodeB and the
S-GW.
 S11 interface: The S11 interface is an interface in the control plane between the MME and S-
GW. It is mainly used to transmit messages for bearer establishment, update, and deletion
between the MME and S-GW. This interface is also used for the S-GW to instruct the MME to
page a UE in the ECM-IDLE state and to restore the S1 bearer.
 S12 Interface: S12 interface is an interface to the user plane between the RNC and the S-GW. It
is used to transmit the downlink and uplink user plane data flows between the RNC and the S-
GW when the direct tunnel solution is used on the UTRAN.
 S4 Interface: S4 interface is an interface in the signaling plane and the user plane between the
S4 SGSN and S-GW. The signaling plane connects the S4 SGSN to the EPS network, transmitting
messages for bearer establishment, update, and deletion. The user plane transmits the user
plane downlink and uplink data flows between the S4 SGSN and the S-GW.
 S5/S8 interface: The S5/S8 interface is an interface in the user plane and signaling plane
between the S-GW and P-GW. The S5 interface is used between the home S-GW and
home P-GW, and the S8 interface is used between the S-GW on a visited network and the
home P-GW.
NOTE:
S5 interface is used when the UGW9811 functions as the S-GW or as P-GW, not used
when the S-GW and P-GW are deployed on the same device.
 Ga Interface: Ga is an interface between the S-GW,or P-GW and the charging gateway
functionality (CGF). The Ga interface runs the GTP protocol. It runs the GTP protocol to send
charging data records (CDRs) that are generated by a network element or functional entity to
the CGF.
 Gxc Interface: Gxc is an interface between the S-GW and the policy charging rules function
(PCRF). It communicates based on the Diameter protocol. The S-GW interacts with the PCRF
through the Gxc interface to realize policy and charging control (PCC) function.
 Gx Interface: Gx is an interface between the P-GW and the policy charging rules function (PCRF).
It communicates based on the Diameter protocol.The P-GW interacts with the PCRF through the
Gx interface to realize policy and charging control (PCC) function.
 Gy Interface: Gy is an interface between the P-GW and the online charging system/credit control
function (OCS/CCF). It communicates based on the Diameter protocol and is used for online
charging control. The UGW9811 interacts with the OCS through the Gy interface to realize credit
control for content-based charging users and non-content-based charging users.
 Gn/Gp Interface: Gn/Gp Interface is an interface between the P-GW and the Gn/Gp SGSN.The
Gn interface is between the GPRS support nodes (GSNs) within the same public land mobile
network (PLMN). The Gp interface is between the GSNs in different PLMNs.
 S6b Interface: S6b interface is an interface between the P-GW and the 3GPP AAA server. It is
used to obtain authentication parameters related to mobility, transmit mobility parameters, and
provide static QoS information for the users switching from a non-3GPP network to the UE.
 SGi Interface: SGi interface is an interface between the P-GW and the PDN. It can also serve as
the interface connecting the P-GW and the AAA server, transmitting authentication and
charging control messages.
 S2a Interface: S2a interface is an interface between the P-GW and the trusted non-3GPP IP
network (HSGW/TWAN). The S2a interface enables the interworking between a trusted fixed
network and an EPC network.
 S2b Interface: S2b interface is an interface between the P-GW and the Untrusted non-3GPP
Access ePDG(evolved Packet Data Gateway).The S2b interface enables the interworking
between a WLAN network and an EPC network.
 SGmb Interface: SGmb is an interface between the S-GW+P-GW and the broadcast/multicast
service center (BM-SC). It communicates based on the Diameter protocol and is used to provide
the control plane function of the evolved multimedia broadcast multicast Service.
 Grp Interface: Grp interface is a Huawei proprietary interface between the P-GW and report
server. The P-GW uses the Grp interface to interwork with the report server to implement the
mobile broadband (MBB) visibility function.
 Gcf Interface: Gcf interface is a Huawei proprietary interface between the P-GW and Internet
Content Adaptation Protocol (ICAP) server. The P-GW uses the Gcf interface to interwork with
the ICAP server to implement the uniform resource locator (URL) filtering function.
 Gnr Interface: Gnr interface is a Huawei proprietary interface between the P-GW and eLog
server. The P-GW uses the Gnr interface to interwork with the eLog server to implement the
NAT logs report function.
Parent Topic: Interfaces and Protocols

Next topic >
< Home
6.2.4.2 Physical Interfaces

Table 1 lists types and numbers of external physical interfaces provided by the UGW9811.
Table 1 Types and numbers of external physical interfaces provided by the UGW9811
Interface Type Maximum Number of Maximum Number of

Interfaces (PGP-X16/PGP- Interfaces (PGP-X8
16 Subrack) Subrack)
GE (Gigabit Ethernet) 240 120
10GE (10 Gigabit Ethernet) 72 48
100GE (100 Gigabit Ethernet) 6 4
Table 2 lists protocols used on the UGW9811 interfaces.

Table 2 Protocols used on the UGW9811 interfaces
Interface Name Physical Characteristics Standard

Protocol Compliance
Gn/Gp GE GTP-C 3GPP TS 29.060
10GE GTP-U 3GPP TS 29.281

S2a GE PMIPv6 3GPP TS 23.402
10GE GTP-C 3GPP TS 29.275
GTP-U 3GPP TS 29.274

S2b GE GTP-C 3GPP TS 23.402

Gi/SGi GE RADIUS/DHCPv4/L2TP 3GPP TS 29.061
10GE
S6b GE Diameter 3GPP TS 23.402
10GE 3GPP TS 29.273

S4 GE GTP-C 3GPP TS 23.401
3GPP TS 29.281
S11 GE GTP-C 3GPP TS 23.401
10GE 3GPP TS 29.274

S12 GE GTP-U 3GPP TS 23.401
10GE 3GPP TS 29.281

S1–U GE GTP-U 3GPP TS 23.401
10GE 3GPP TS 29.281
3GPP TS 36.414
S5/S8 GE GTP-C 3GPP TS 23.401
10GE GTP-U
Table 2 Protocols used on the UGW9811 interfaces
Interface Name Physical Characteristics Standard

Protocol Compliance
3GPP TS 29.274
3GPP TS 29.281
Ga GE GTP' 3GPP TS 32.240
10GE 3GPP TS 32.251
3GPP TS 32.295
3GPP TS 32.298
Gy GE Diameter 3GPP TS 32.299
10GE
Gx/Gxc GE Diameter 3GPP TS 23.203
10GE 3GPP TS 29.212
3GPP TS 29.213
Parent Topic: Interfaces and Protocols
< Previous topic
< Home
6.2.5 Operation and Maintenance

 OM System
 OM Function
This describes the operation and maintenance (OM) of the UGW9811 based on the client/server
architecture.
OM System
Figure 1 shows the structure of the UGW9811 OM system.

Figure 1 Structure of the UGW9811 OM system
 BAM
The BAM is the server based on the Transmission Control Protocol/Internet Protocol
(TCP/IP). The BAM of the UGW9811 is integrated on the Switching Route Unit
(SRU)Main Processing Unit (MPU).
o Receiving connection requests from the client to establish connections, and analyzing
and processing commands from the client
o Receiving connection requests from the host through the local bus to establish
connections and realize the communication between the BAM and the host, and
processing data loading requests and alarms from the host
NOTE:
In spite of the loss or error of BAM files, the U2000 can interwork with the UGW9811
and restore the BAM.
 LMT
The LMT serves as the client and is connected to the back administration module (BAM)
based on the Transmission Control Protocol/Internet Protocol (TCP/IP).
The LMT supports the command line interface (CLI) mode and the graphic user interface
(GUI) mode. The LMT can be used to configure the device, trace messages, manage the
system performance, manage alarms, and manage logs. The LMT provides interfaces to
connect the alarm box to provide audible and visual alarms.
The LMT can be accessed by dialing through the public switched telephone network
(PSTN). Then, the LMT performs the operation and maintenance (OM) function.
The LMT can run on EMS clients to provide remote operation and maintenance.
 U2000
The U2000 is a mobile network management system (NMS) in Huawei iManager

network management solution. The U2000 communicates with the UGW9811 through
the Transmission Control Protocol/Internet Protocol (TCP/IP). The U2000 is composed
of the U2000 server and multiple U2000 clients.
The local maintenance terminal (LMT) can be integrated into the U2000. Thus, the LMT
can achieve uniform management and browsing of devices in the entire network through
the topology management function provided by the U2000. The LMT and the U2000 are
in the loose coupling relationship. The LMT is dedicated to management only on the
UGW9811, whereas the U2000 performs the public management such as topology
management and fault management for devices in the entire network.
OM Function
The UGW9811 provides the OM functions such as configuration management, message tracing,
performance management, alarm management, and log management.
 Configuration Management
The configuration management function is performed by the command line interface

(CLI) commands provided in the local maintenance terminal (LMT) of the UGW9811.
By running the CLI commands, you can configure, modify, and query data. The
UGW9811 receives, analyzes, and runs the CLI commands, and then returns the results to
the LMT.
 Message Tracing
The message tracing function of the UGW9811 is performed in the maintenance window
of the local maintenance terminal (LMT). Through the maintenance window of the LMT,
you can trace and view interfaces and users.
You can create interface and user tracing tasks to monitor the signaling of the interfaces
and users of the system in real time. The stored messages including the information about
previous versions can be viewed online or offline. If a fault occurs in the UGW9811, you
can quickly and accurately locate and clear the fault through the interface signaling
tracing function.
 Performance Management
The performance management function of the UGW9811 is realized through the

centralized performance management module of the U2000 and the Performance Browser
Tool of the local maintenance terminal (LMT).
The UGW9811 generates performance measurement files and provides File Transfer
Protocol (FTP) services. The U2000 acts as the FTP client to receive the performance
measurement files and then manage the performance of the UGW9811. The LMT obtains
the performance measurement files and provides them for viewing through the
Performance Browser Tool.
The centralized performance management system provides a comprehensive and direct

operation environment. You can manage the performance of devices in the entire
network. You can create, modify, and query performance measurement tasks and manage
the results to learn the running status of the network and devices. The measurement
results are for performance assessment and network optimization.
 Alarm Management
The alarm management function of the UGW9811 is realized through the alarm
management system of the local maintenance terminal (LMT) or the centralized fault
management system of the U2000.
The UGW9811 sends alarms to the LMT or the U2000 and simultaneously saves them in
alarm logs.
The UGW9811 collects alarms that are generated during fault occurrence and classifies
them based on type and severity level. Then, the UGW9811 sends the alarms to the alarm
management system of the LMT or the centralized fault management system of the
U2000. The LMT or U2000 displays the alarms in graphical user interfaces (GUIs) and
provides the location, cause, and troubleshooting suggestions.
 Log Management
Logs can be classified into operation logs, system logs, security logs, DDoS logs, alarm
logs, and diagnosis logs based on contents.
o The user operation logs record the information about user operation commands,
including the user name, executed commands, and execution time, to analyze faults.
o The system operation logs record certain state information in the system operation to
maintain the system and locate faults.
o The security logs record all security events, including user login events, user
authentication events, and management events.
o DDoS logs record DDoS attack events, including the IP address of a UE that initiates a
DDoS attack and the time a DDoS attack occurs.
o The alarm logs record all the generated alarms. You can learn fault information on the
device by querying the alarms.
o Diagnosis logs record normal key information and abnormal information about the
UGW9811.

< Home
6.2.6.1.3 Performance Specifications (PGP-

X16)
NOTICE:
The performance specifications provided in this document are assessed based on specific traffic
models. The performance specifications vary obviously with increasing everlasting bandwidth
required by PS subscribers and Darwinian development of Internet services. For network
assessment of a specific site, contact Huawei local office.
Table 1 Performance specifications of the UGW9811(PGP-X16) functioning as a GGSN/S-GW/P-GW
Item Specification
Maximum number of SPUs in active/standby mode 24,000,000
activated bearer contexts
SPUs in load-sharing mode 40,000,000
SPUs in N+1 backup mode 36,000,000
Maximum data throughput SPUs in active/standby mode 360G bit/s
SPUs in load-sharing mode 600G bit/s
SPUs in N+1 backup mode 540G bit/s
Maximum number of APNs 3,000
Maximum number of GRE 4,000
tunnels
Maximum number of L2TP 40,000
tunnels
Maximum number of 100,000
eNodeBs
6.2.6.2.3 Entire-system Specifications (PGP-

X16)
Table 1 Entire-system specifications of the UGW9811 (PGP-X16)
Item Specification
Cabinet N68E-22
Cabinet dimensions (height 2,200 mm × 600 mm × 800 mm (86.61 in. × 23.62 in. × 31.50
× width × depth) in.)
Cabinet weight (in full 475 kg (1047.4 lb)
configuration,include Power
Distribution Box)
Table 1 Entire-system specifications of the UGW9811 (PGP-X16)
Item Specification
Subrack dimensions (height 1420.00 mm× 442.00 mm × 650.00 mm (55.91 in. ×17.40 in. ×
× width × depth) 25.59 in.)
NOTE:
1 U = 44.45 mm. The height is 32 U
Subrack weight (in full 305 kg (672.5 lb)

configuration)
Load-bearing capacity ≥ 600 kg/m2
Power input(rated voltage) -48V DC or -60V DC
Power input(voltage range) -38.4V DC to -72V DC
Typical power consumption 8,000 W
of a subrack (in full
configuration)
Maximum power 14,000 W
consumption of a subrack
(in full configuration)
Noise (acoustic power) ≤ 83 dBA at 27°C (73.4°F)
6.2.7.3 Running Environment

 Climatic Requirements
 Biological Environment Requirements
 Air Purity Requirements
 Mechanical Stress Requirements
This section describes the requirements for the operating environment of the UGW9811. The
requirements for the operating environment consist of the climatic requirements, waterproofing
requirements, biological requirements, air purity requirements, and mechanical stress
requirements.
Climatic Requirements
Table 1 Requirements for temperature and humidity in the operating environment
Temperature Relative Humidity

Long term operation Short term Long term operation Short term operation
operation
0°C to 40°C (32°F to -5°C to +50°C 5% to 85% 5% to 90%
104°F) (23°F to 122°F)
NOTE:
 Before measuring temperature or humidity, make sure the device has no protection cards. The
values are measured at 1.5 m above the floor and 0.4 m in front of the equipment, without
protective panels in front of or behind the cabinet.
 Short term operation refers to continuous operation for no more than 48 hours or
accumulated operation of no more than 15 days in a year.
To improve product reliability, dedicated precision air conditioners must be installed in

equipment rooms to limit the temperature and humidity within the following ranges:
 Temperature: 15°C to 30°C (59°F to 86°F)

 Humidity: 40% to 75%
NOTE:
Air conditioners must not be installed above equipment and must not blow directly towards
equipment. Air conditioners should be installed away from windows to keep them from blowing
moisture to equipment.
Table 2lists requirements for other climatic factors in the operating environment.
Table 2 Requirements for other climatic factors in the operating environment
Item Specification
Altitude ≤ 4000 m (13123.2 ft) When the altitude ranges
from 1800 m to 4000 m (5905.44 ft to 13123.2
ft), the equipment operating temperature
decreases by 1°C (1.8°F) each time the altitude
increases by 220 m (721.78 ft).
Temperature change rate ≤ 0.5°C(32.9°F)/min
Wind speed ≤ 5 m (16.40 ft)/s
6.3.5 PGP-X16
 Functions
 Appearance
 Hardware Structure
 Logical Structure
 Technical Specifications
Functions
The PGP-X16 provides the following functions:
 Serves as an independent unit composed of various boards that are connected using the
backplane.
 Protects boards from external damage and supplies power to boards and fan modules.
 Provides heat dissipation channels.
The PGP-X16 has the following characteristics:
 Non-blocking switching network that can be upgraded, with a switching capacity at the
Tbit/s level
 Distributed and hardware-based forwarding capability and fast service deployment
 Compact structure to increase interface density
 Unified design of system components
 Separation of the control channel, service channel, and monitoring channel
 Carrier-class high reliability and manageability
 Shielding based on modules to meet Electro Magnetic Compatibility (EMC) requirements
 Hot swappable boards, power modules, and fan modules
 U-shaped air channels to improve system heat dissipation
 Independent power supply to enhance the power supply capability of a single subrack
 200 mm (7.87 in.) fan modules and compliance with the NEBS and ETSI
 Backup of key components such as power modules, fan modules, clocks, and
management buses
 Protection against incorrect insertion of boards
 Query of alarm prompts, alarm indications, running status, and alarm status of the voltage
and ambient temperature
Appearance
Figure 1 shows the appearance of the PGP-X16.
Figure 1 Appearance of the PGP-X16

NOTICE:
In the lower part of a PGP-X16 subrack, boards are installed using the same method but be
installed upside down compared with those in the upper part of the subrack. When connecting
cables to the LPUs in the lower part of a PGP-X16 subrack, ensure that the cables are connected
to the correct ports because the port numbers are also reversed.
Hardware Structure
Figure 2 shows the structure and main components of the PGP-X16 for the front view.
 Figure 2 Structure and main components of the PGP-X16 (front view)
1. Air intake vent 2. ESD jack 3. Cable trough

4. Handle 5. SFU boards area 6. Rack-mounting ear
 Figure 3 shows the structure and main components of the PGP-X16 for the rear view.
Figure 3 Structure and main components of the PGP-X16 (rear view)
1. Fan module 2. DC power module 3. AC power management interface
Figure 4 shows the slot layout on the PGP-X16.
Figure 4 Slot layout on the PGP-X16
Table 1 describes the slots on the PGP-X16.
Table 1 Slots of the boards.
Board Suggested Suggested Slot Width Description

Type Quantity Board
Slot
LPU 1 to 6 Slots 1 to 41 mm (1.60 Insert the LPUs into slots in an ascending
10 in.) order, from the lowest slot number to the
highest.

Type Quantity Board
Slot
SPU 1 to 12 Slots 3 to 41 mm (1.60 Insert the SPUs into a subrack according to
16 in.) the following rules if the subrack will not
be fully configured:
 When only one SPU group is

configured, insert the SPUs starting
from slots 7 to 14. If more SPUs need
to be inserted, insert them into slots 3
to 6 (which can also hold the LPUs) or
slots 15 and 16 (which can hold other
service boards).
 When two SPU groups are configured,
you are advised to insert the SPUs of
an SPU group starting from slots 7 to
14 and insert the SPUs of the other
SPU group starting from slots 14 to 7.
If more SPUs need to be inserted,
insert them into slots 3 to 6 (which can
also hold the LPUs) or slots 15 and 16
(which can hold other service boards).
 In other situations, insert the SPUs into
slots with consecutive slot numbers
and reserve slots for capacity
expansion.
PEU 2 Slots 11 to 41 mm (1.60 You are advised to insert the PEUs into
16 in.) slots 15 and 16. The PEUs can also be
inserted into slots 11 to 14.
STE 1 to 4 Slots 11 to 41 mm (1.60 You are advised to insert the STEf/STEf1s
16 in.) into slots 15 and 16. The STEf/STEf1s can
also be inserted into slots 11 to 14.
MSU 2 to 6 Slots 7 to 41 mm (1.60 Insert MSUf1s into these slots.
16 in.)
NOTE:
 You are advised to insert MSUf1s into

consecutive slots and reserve some
slots for future capacity expansion.

Type Quantity Board
Slot
 You are advised to insert MSUf1s into
slots 14 to 11 in descending order by
slot number. If more MSUf1s need to
be inserted, insert MSUf1s into slots 7
to 10 or slot 15 or 16.
 When there are more than two SPU
groups, if an MSUf1 group also needs
to be configured, you are advised to
preferentially insert MSUf1s into slots,
that is, insert MSUf1s into slots 14 to
11 in descending order by slot number.
If more MSUf1s need to be inserted,
insert MSUf1s into slots 7 to 10 or slot
15 or 16.
After MSUf1s are inserted into slots, you

are advised to insert SPUs in an SPU group
into slots starting from slot 7 in ascending
order by slot number and then install SPUs
in another SPU groups into slots in
ascending order by slot number.
MPU 2 Slots 17 41 mm (1.60 The MPUs work in 1+1 backup mode.
and 18 in.)
SFU 4 Slots 19 to 41 mm (1.60 The SFUs work in 3+1 backup mode.
22 in.)
NOTE:
SFUBs and SFU200Bs cannot be installed

in the same subrack.
For details about the basic configuration board list of the PGP-X16 subrack, see Boards.
For hardware mapping, see Hardware Equipment Matching Table.
PGP-X16 backplane is divided into six areas and power is supplied to the two areas
independently. For details, see Power Supply System.
For details about the heat dissipation system of the PGP-X16 subrack, see Heat Dissipation
System.
Logical Structure
The PGP-X16 uses a system architecture shown in Figure 5. In this architecture, the data plane,
management and control plane, and monitoring plane are separated. This design helps improve
system reliability and facilitates the upgrade of each plane separately.
Figure 5 Diagram of the system architecture
Table 2 lists the physical parameters of the PGP-X16.
Table 2 Physical parameters of the PGP-X16
Item Description
BOM 02300686
Dimensions (width x depth x height) The height of the PGP-X16 subrack is 32 U
(1422.4 mm or 56 in.).
Maximum exterior dimensions: 483 mm x 754

mm x 1420 mm (19.02 in. x 29.68 in. x 55.91
in.)
Basic exterior dimensions: 442 mm x 658 mm

x 1420 mm (17.40 in. x 25.91 in. x 55.91 in.)
NOTE:
The basic exterior dimensions do not include

the dimensions of mounting ears and cable
troughs, whereas the maximum exterior
dimensions include the dimensions.
Typical power consumption (full 7,400 W
configuration)
NOTE:
It is the power consumption when the ambient

temperature is 25°C (77°F) and the service
traffic is 50% of the capacity.
Table 2 Physical parameters of the PGP-X16
Item Description
Maximum power consumption (full 14,000 W
configuration)
NOTE:

Subrack configuration Full configuration in a PGP-X16 subrack:
twelve DC power supply modules, four fans,
four 24-Port 10GBase LAN/WAN-SFP+
Integrated Line Processing Unit (LPUF-
202A03)s, twelve SPUfs, two MPUXs, and
four SFU200Bs.
For the power consumption of each board, see

Power Consumption and Weight.
Weight Basic subrack 124.4 kg (274.3 lb; with 12 PEMs, four fans,
two MPUXs, and four SFU200Bs)
Full configuration 305 kg (672.52 lb)
DC input Rated voltage -48 V DC or -60 V DC
Allowed voltage -38.4 V DC to -72 V DC
DC input current There are six pairs of inputs. The two inputs in
a pair operate in active/standby mode. Each
input provides the current of 80 A.
NOTE:
It is the working current of the subrack with

the minimum working voltage and the
maximum power consumption. The electric
current of all lines will not reach the maximum
at the same time. To ensure the subrack power
supply reliability and facilitate subsequent
hardware capacity expansion, the rated current
of the air breaker on the PDF must be greater
than the maximum input current. For detailed
requirements, see Power Distribution Guide.
< Home
6.3.5.1 Power Supply System

 Functions
 Appearance
 Indicators
Functions
The power supply system of a PGP-X16 subrack provides 12 power entry modules (PEMs)
working in 6+6 backup mode.
Figure 1 Architecture of the power supply system
Figure 2 PEM slot distribution (rear side of the PGP-X16 subrack)
Figure 1 shows the architecture of the power supply system.
The power supply system includes two parts as followed:
 Power Input
The DC PDF and the upstream DC switchboard are external devices connected to the
PGP-X16, providing twelve (working in 6+6 backup mode) independent input power
supplies of stable voltages for the cabinet.
 Power Distribution
The PGP-X16 subrack is divided into six areas and two power inputs are provided for
each area.
The PGP-X16 power supply system works in 6+6 backup mode to provide power supply
for the subrack. PEM-A1 and PEM-B1 act as the backup for each other and provide
power supply for the first power supply area (slots in green). PEM-A2 and PEM-B2 act
as the backup for each other and provide power supply for the second power supply area
(slots in yellow). PEM-A3 and PEM-B3 act as the backup for each other and provide
power supply for the third power supply area (slots in blue). PEM-A4 and PEM-B4 act as
the backup for each other and provide power supply for the fourth power supply area
(slots in grey). PEM-A5 and PEM-B5 act as the backup for each other and provide power
supply for the fifth power supply area (slots in purple). PEM-A6 and PEM-B6 act as the
backup for each other and provide power supply for the sixth power supply area (slots in
orange).
NOTE:
If one area is not supplied by the active and standby power inputs, the area cannot be
powered on, and cannot be registered. The boards in this are faulty in the Device Panel
on the LMT.
The two power inputs working in active-standby mode supply power for each board in an
area.
After low-frequency filtering, the two power inputs for fan modules are joined inside the
fan modules, working in the 1:1 backup mode.
NOTE:
Each DC power input contains one NEG power input (-48 V or -60 V blue power cable) and one
RTN input (black power ground cable). RTN inputs are isolated before connecting to a board.
Two RTN inputs are combined into a board.
Figure 2 shows the PEM slot distribution. The functions of the PEM are as follows:
 The PEM provides power supply, filtering, surge protection, and overcurrent protection
for the subrack. It also monitors the status of the power supply, surge protection circuit,
and circuit breaker, and generates alarms on detecting exceptions.
 The PEM supports 2-input power supplies and uses the hydraulic electromagnetic breaker
(also called circuit breaker) as the overcurrent protection component. The PEM can be
maintained manually.
Appearance
Figure 3 shows the appearance of the PEM.
Figure 3 Appearance of the PEM
Indicators
Table 1 describes the LED indicators on the PEM.

Table 1 Indicators on the PEM
Indicator Color Description

RUN Green Indicates normal power output. If the indicator is steady on,
it implies the normal output.
ALM Red Power failure indicator. If the indicator is steady on, either of
the following situations occurs:
 The PEM has no voltage input.

 The circuit breaker of the PEM is not turned on.
 The lightning protection circuit of the PEM is
ineffective.
Table 2 lists the technical specifications of the PEM.
Table 2 Technical specifications of the PEM
Item Description
Dimensions (height x width x depth) 220 mm x 117 mm x 58 mm (8.66 in. x 4.61 in.
x 2.28 in.)
Weight About 1.1 kg (2.43 lb)
Input rated voltage -48 V DC or -60 V DC
Input voltage range -38.4 V DC to -72 V DC
Maximum input current 80 A
Maximum output current 80 A
Rated current of the air breaker on the 80 A
power module
To ensure the subrack power supply reliability and facilitate subsequent hardware capacity
expansion, the rated current of the air breaker on the PDF must be greater than or equal to 80 A.
NOTE:
There is one-to-one mapping between the air breakers on the PDF and the air breakers on the
subrack's power modules. That is, there are altogether six pairs of air breakers. The two air
breakers in a pair work in active/standby mode. For details about power distribution, see The
power distribution guide for PGP-X16 subrack.
Parent Topic: PGP-X16
Next topic >
< Home
6.3.5.2 Heat Dissipation System

 Functions
 Appearance
 Indicators
 Logical Structure
Functions
The heat dissipation system includes four FAN modules, ensures that the subrack operates in
normal temperature.
Appearance
Two fan modules each containing one fan are located side by side at the air exhaust vent. If a
single fan fails, the system can still work properly for a short period of time at the ambient
temperature of 40°C (104°F). Figure 1 shows the appearance of a fan module.
Figure 1 Appearance of a fan module
Indicators
Table 1 describes the indicators on a fan module.
Table 1 Description of the indicators on the fan module

STATUS Green If the indicator blinks every
two seconds (0.5 Hz), the fan
module is working properly.
Table 1 Description of the indicators on the fan module

If the indicator blinks four
times every second (4 Hz),
the fan module is not
working properly.
Red If the indicator blinks once
every two seconds (0.5 Hz), the
fan module has a hardware
fault.
 The fan module is

faulty.
 The 48 V power supply
is abnormal.
 The fan module is not
installed securely.
Logical Structure
 System air channel
The PGP-X16 is divided into an upper subrack and a lower subrack; it draws in air from
the front and exhausts air from the rear to dissipate heat. The air intake vent on the upper
subrack is located above the board area on the front subrack; the air exhaust vent is
located above the board area on the rear subrack. The lower subrack and the upper
subrack are opposites. The upper subrack and the lower subrack also have separate heat
dissipation systems.
The middle area of the PGP-X16 is for SFU slots. The air intake vent of this area is
located on the left of the subrack. Two upper SFU slots in the area draw in air from the
left. When flowing to the right, the air joins the air from the upper subrack. Two lower
SFU slots in the area also draw in air from the left. When flowing to the right, the air
joins the air from the lower subrack.
Figure 2 shows the air flow in the PGP-X16.
Figure 2 Air flow in the PGP-X16
 Air intake vent

PGP-X16 has three air channels.
The upper and lower subrack have separate air channels that draw air from the front and
exhausts air from the rear. The air filters are installed over the air intake vents. Each filter
has a curved face, large area, and small windage resistance. These features help to
improve heat dissipation efficiency. Air filters on the upper and lower subrack are
identical.
The air channel in the SFU slot area is located on the left of the subrack. The air filter
uses front access. The depth of the air filter is the same as that of an SFU and the height
of the air filter is four times the height of the an SFU.
 Air Filter
The PGP-X16 draws in air from the front and exhausts air from the rear. The two air
filters on the upper and lower subrack are identical. To maximize air intake, the filters are
fully perforated. Air filters are fixed to the subrack by fasteners to facilitate filter removal
and replacement. Figure 3 shows the appearance of an air filter.
Figure 3 An air filter
The air channel in the SFU slot area is located on the left of the subrack. The air filter
uses front access. The depth of the air filter is the same as that of an SFU and the height
of the air filter is four times the height of an SFU as shown in Figure 4.
Figure 4 An air filter in the SFU slot area
Placing a black sponge air filter at the air intake vent helps prevent dust from entering the
system. It is recommended that air filters be removed and cleaned at least once every
three months.
 Fan speed adjustment
When the system is fully configured, temperatures reported by the temperature sensors on
the LPUs, SFUs, and MPUs serve as the basis for fan speed adjustment. General
principles are listed below:
o When the ambient temperature is 27°C (80.6°F) or below, fans rotate at a fixed
low speed, which meets the NEBS noise requirement and the heat dissipation
requirement.
o When the ambient temperature is between 27°C (80.6°F) and 45°C (113°F), the
speed of fans is adjusted smoothly in linear mode, and there are slight changes in
noise levels.
Table 2 lists the technique specifications of a fan module.
Table 2 Technical specifications of a fan module
Item Technical Parameter

BOM 02120632
Dimensions (width x depth x height) 212.2 mm x 105 mm x 270.7 mm (8.35 in. x
4.13 in. x 10.66 in.)
Typical power consumption 90 W
NOTE:

Maximum power consumption 500 W
NOTE:

Weight 3.4 kg (7.50 lb)
Parent Topic: PGP-X16
< Home
6.3.8.1.1 MPUB
 Functions
 Appearance
 Interfaces
 Indicators
 Hardware and Software Compatibility
Functions
The Main Processing Unit (MPU) controls and manages the system, including route calculation,
and device management, maintenance, and monitoring.
 System control and management unit
As the system control and management unit, the MPUB provides the following functions
on the system control panel:
o Route calculation: all routing protocol packets are sent by the forwarding engine
to the MPUB for processing. In addition, the MPUB broadcasts and filters
packets, and downloads routing policies from the policy server.
o Outband communication between boards: the LAN switch modules integrated on
the MPUB provide outband communications between boards. In this manner,
messages can be controlled, maintained, and exchanged between boards.
o Device management and maintenance: the MPUB manages and maintains the
system through the management interfaces such as the Console interface or
network interface.
o Data configuration: the MPUB stores configuration data, startup files, charging
information, upgrade software, and system logs.
o Data storage: the MPUB provides one 8 GB hard disk for storing operation and
maintenance (OM) data and one hard disk of at least 80 GB for storing charging
data records (CDRs).
NOTE:
The capacity of the hard disk will be changed as the hardware is upgraded.
 ALM-0632 Insufficient hard disk space is generated when the OM hard disk
usage reaches 90%. This alarm is cleared when the OM hard disk usage falls
below 80%.
 ALM-0632 Insufficient hard disk space is generated when the CDR hard disk
usage reaches 35%. This alarm is cleared when the CDR hard disk usage falls
below 25%.
 System maintenance unit
As the system maintenance unit, the MPUB collects system monitoring information to
test system units locally or remotely, or implement in-service upgrade of system units.
The MPUB periodically collects information about the operation of system units by using
the Monitorbus. The MPUB then generates related control information based on the
collected information, for example, board installation detection and fan speed adjustment.
With the joint test action group (JTAG) bus, the MPUB remotely or locally tests system
units, or performs in-service upgrade of system units.
 Reliability
The main control modules, clock modules, and LAN switch modules on the MPUB work
in 1+1 hot backup mode, improving system reliability.
The two MPUs work in 1+1 backup mode. Each MPUB monitors the status of the other.
If the master MPUB is faulty, the slave MPUB automatically takes over as the master
MPUB.
Appearance
Figure 1 shows the appearance of the MPUB:
Figure 1 Appearance of the MPUB
Interfaces
Table 1 describes the interfaces on the MPUB.
Table 1 Interfaces on the MPUB
Interface Name Connector Type Description

USB interface USB It is used to hold a USB disk to store data
files as a massive storage device.
NOTE:
USB interfaces are reserved for later use.

CTL-ETH-SFP interface SFP It is reserved for the use after capacity
(1000MBase-X) expansion.
MGMT-ETH interface RJ45 It connects to the NMS workstation and has
(10M/100M/1000M Base- LINK and ACT indicators.
TX auto-sensing)
Console interface RJ45 It connects to the console for on-site
configuration of the system.
AUX interface RJ45 The AUX interface is unavailable.
NOTE:
The interfaces related CLK are not available on UGW9811.
Table 2 lists the USB interface attributes.
Table 2 USB interface attributes
Attribute Description
Connector type USB
Operation mode High-speed mode or full-speed mode
Standard compliance USB 2.0
Cable specification Standard USB cables
Table 3 lists the 1000MBase-X-SFP interface attributes.
Table 3 1000MBase-X-SFP interface attributes
Connector type SFP
Operation mode 1000M fiber
Standard compliance IEEE 802.3-2002
Cable specification Single-mode or multi-mode fibers
Table 4 describes the 10Base-T/100Base-TX/1000Base-T-RJ45 interfaces attributes.
Table 4 10Base-T/100Base-TX/1000Base-T-RJ45 interface attributes
Connector type RJ45
Operation mode 10M/100M/1000M auto-sensing interfaces, supporting half-duplex and full-
duplex modes
Standard IEEE 802.3-2002
compliance
Cable Category 5 unshielded twisted pair (UTP) cables recommended when the
specification interface rate is 10 Mbit/s or 100 Mbit/s; super category 5 Shielded Twisted
Pair (STP) cables recommended when the interface rate is 1000 Mbit/s
Table 5 describes the console interface attributes.

Table 5 Console interface attributes
Connector type RJ45
Operation mode Duplex Universal Asynchronous Receiver/Transmitter (UART)
Electrical attribute RS-232
Baud rate 9600 bit/s (default value), which can be changed as required
Data equipment Data Circuit-terminating Equipment (DCE)
type
Cable 8-core shielded cable
specification
Indicators
Table 6 describes the buttons and indicators on the MPUB panel.
Table 6 Buttons and indicators on the MPUB panel
Indicator/Button Description
OFL button To remove a board, press and hold the button for about six
seconds until the OFL indicator turns on.
NOTE:
This button takes effect only on the slave MPUB.

OFL indicator (red) If the indicator is on, you can remove the board.
RUN indicator (green) If the indicator blinks once every two seconds (0.5 Hz), the
system is in the normal state.
If the indicator blinks twice each second (2 Hz), the system is in

the alarm state.
ALM indicator (red) If the indicator is steady on, the system is in the alarm state.
If the indicator is steady off, the system is in the normal state.

ACT active/standby If the indicator is steady on, the MPUB is in the active state.
indicator (green)
If the indicator is off, the MPUB is in the standby state.
Table 6 Buttons and indicators on the MPUB panel
Reset button The button is used for resetting the MPUB. If you press the Reset
button, you can reset the MPUB.
SFP LINK/ACT indicator If the indicator is steady on, the link is normal.
(green)
If the indicator is blinking, data is being transmitted.
MGMT-ETH LINK If the indicator is steady on, the link is normal.
indicator (green) (on
Ethernet network If the indicator is off, the link is Down.
interfaces)
MGMT-ETH ACT If the indicator is blinking, data is being transmitted.
indicator (amber) (on
Ethernet interfaces) If the indicator is off, no data is being transmitted.
Hardware and Software Compatibility
The MPUB can be used only in the PGP-X16 subrack.
The MPU can be used only in the PGP-16 subrack.
Table 7 show the difference of specifications between the MPUB and MPU.
Table 7 Technical specifications of MPUB and MPU
MPU Type Dimensions (Width x Typical Maximum Heat Weight

Depth x Height) power power Dissipation
consumption consumption
MPUB 400 mm x 535 mm x 40 85 W 95 W 85 W 4 kg (8.82
mm (15.75 in. x 21.06 lb)
in. x 1.57 in.)
MPU 400 mm x 535 mm x 30 70 W 77 W 70 W 3.8 kg
mm (15.75 in. x 21.06 (8.38 lb)
in. x 1.18 in.)
Table 8 lists the technical specifications of the MPUB.

Table 8 Technical Specifications of the MPUB
Item Description
BOM 03053557
03030NAH (03030NAH is an earlier

BOM number and identifies the same
board as 03053557.)
Dimensions (Width x Depth x Height) 400 mm x 535 mm x 40 mm (15.75 in. x
21.06 in. x 1.57 in.)
NOTE:

temperature is 25°C (77°F) and the service traffic is
50% of the capacity.
NOTE:

temperature is 50°C (122°F) and the service traffic
is 100% of the capacity.
Heat Dissipation 85 W
Weight 4 kg (8.82 lb)
6.3.8.3 SFUs
SFUB
SFUC
SFUG
The switching fabric unit (SFU) provides the switching function of the service data throughout
the system.
SFU200B
SFU200C
Parent Topic: Boards
< Home
6.3.8.3.1 SFUB
 Functions
 Appearance
 Interfaces
 Indicators
Functions
The Switch Fabric Unit (SFU) on the PGP-X16 switches data for the entire system. This ensures
a non-blocked switching network.
The PGP-X16 has four SFUBs working in 3+1 load balancing mode.
The four SFUBs process services in load sharing mode. If an SFUB is faulty or replaced, the
other three SFUBs automatically take over the services on the SFUB, ensuring that the services
are not interrupted.
Appearance
Figure 1 shows the appearance of the SFUB.
Figure 1 Appearance of the SFUB
Interfaces
None
Indicators
Table 1 describes the buttons and indicators on the panel of the SFUB.
Table 1 Buttons and indicators on the panel of the SFUB
LED Description
RUN Before the registration of the SFUB: If the indicator blinks twice every second (2
Hz), the system is in the alarm state.
After the registration of the SFUB: If the indicator blinks once every two seconds
(0.5 Hz), the system is running normally.
ACT If the indicator is on, it indicates that the SFUB is working normally; if the green
indicator is off, it indicates that the SFUB is faulty.
OFFLINE When the SFUB is working normally, the OFL indicator is off. After the OFL
button is pressed to power off the SFUB, the OFL indicator is on.
NOTE:
To remove a board, press and hold the button for about six seconds until the OFL
indicator turns on.
SFUB is used on the PGP-X16.
Table 2 lists the technical specifications of the SFUB.
Table 2 Technical Specifications of the SFUB
Item Description
BOM 03053560
03030KSX (03030KSX is an earlier BOM

number and identifies the same board as
03053560.)
Dimensions (Width x Depth x Height) 411 mm x 535 mm x 40 mm (16.18 in. x 21.06
in. x 1.57 in.)
NOTE:
Table 2 Technical Specifications of the SFUB
Item Description

Maximum power consumption 55W
NOTE:

6.3.8.4 SPUe
 Functions
 Appearance
 Intefaces
 Indicators
Functions
The Service Processing Unit (SPU) performs functions such as service awareness and control, user packet
forwarding, flow control, and QoS functions.
 Flexible IP address assignment
The IP address assigned to a mobile user is the static IP address specified when the user
subscribes to packet services, or the dynamic IP address obtained when the PDP
context/EPS bearer is activated. The UGW9811 supports both static and dynamic address
assignment modes.
 Integrated firewall: The number of firewalls in networking is reduced and value-added

protection based on user information on the gateway is provided.
 Charging function: The content-based charging solution, prepaid charging solution, postpaid
charging solution, and user policy delivery solution are provided.
 Service awareness and control: Based on the protocol identification and content parsing
techniques and the user policy delivery solution, users' access permissions are determined
according to users' subscription information.
 Perfect security mechanism
o Protocol security authentication
o Packet filtering and access control list (ACL)
o Interface redirection
o IP address anti-spoofing
 QoS control: QoS policy delivery, user-traffic marking, user-specific traffic policing, queue
scheduling, and traffic shaping are provided.
Appearance
Figure 1 shows the appearance of the SPUe.
Figure 1 Appearance of the SPUe
Intefaces
None
Indicators
Table 1 describes the buttons and indicators on the panel of the SPUe.
Table 1 Buttons and indicators on the panel of the SPUe
OFL button To remove a board, press and hold the button
for about six seconds until the OFL indicator
turns on.
OFL indicator (red) If the indicator is on, you can remove the
board.
RUN indicator (green) If the indicator blinks every 2s (0.5 Hz), the
SPU is in the normal state.
If the indicator is steady on, the device is

starting and has not registered.

The SPUe is used on the PGP-16, PGP-X8 or PGP-X16 subracks.
Table 2 lists the technical specifications of the SPUe
Table 2 Technical Specifications of the SPUe.
Item Description
BOM 03053558
03030NAF (03030NAF is an earlier BOM

number and identifies the same board as
03053558.)
Dimensions (Width x Depth x Height) 400 mm x 533 mm x 41 mm (15.75 in. x 20.98
in. x 1.57 in.)
NOTE:

NOTE:

6.4.2 LMT
This describes the local maintenance terminal (LMT). HUAWEI LMT is the software that runs
over the operation and maintenance terminal. The LMT communicates with the back
administration module (BAM) on the SRU/MPU of the UGW9811 through the local area
network (LAN) or wide area network (WAN). Thus, the LMT enables the operation and
maintenance of the UGW9811.
LMT Software
This describes the local maintenance terminal (LMT) software. The LMT software contains the
LMT, File Transfer Protocol (FTP) client, FTP server, LMT service manager, trace viewer, monitor
viewer, performance browser tool, and convert management system.
Directory Structure of the LMT Software
This describes the directory structure of the local maintenance terminal (LMT) software on the
PC.
Parent Topic: Software Description
< Previous topic
< Home
6.4.2.1 LMT Software

This describes the local maintenance terminal (LMT) software. The LMT software contains the
LMT, File Transfer Protocol (FTP) client, FTP server, LMT service manager, trace viewer,
monitor viewer, performance browser tool, and convert management system.
Local Maintenance Terminal
This describes the local maintenance terminal (LMT). The LMT provides the authority
management, alarm management, device maintenance, and message tracing functions through
a graphic user interface (GUI). The LMT also provides abundant command line interface (CLI)
commands with which you can maintain the device and manage the performance.
FTP Client
The FTP client communicates with the FTP server through the FTP protocol. They exchange the
performance data, configuration data, and maintenance data. Thus, the quality of service (QoS)
is improved.
FTP Server
This describes the File Transfer Protocol (FTP) server. The local computer can be used as an FTP
server for access if the parameters of the FTP server are set.
LMT Service Manager

This describes the local maintenance terminal (LMT) service manager. The LMT service manager
enables the communication between the LMT software and the SRU/MPU. In addition, it can
manage the server processes. You need not start the LMT service manager manually.
Trace Viewer
This describes the trace viewer. The trace viewer is used to view offline the saved trace files
whose extension names are .tmf. In this way, the trace messages can be viewed.
Monitor Viewer
This describes the monitor viewer. The monitor viewer is used to review the data and display
the state by opening the monitor file with the extension name .mrf.
Performance Browser Tool
This describes the performance browser tool. The performance browser tool is used to manage
performance measurement tasks and check performance measurement results.
Convert Management System
This describes the convert management system. The convert management system is used to
transfer the alarm to the alarm box.
Parent Topic: LMT
Next topic >
< Home
6.4.2.1.1 Local Maintenance Terminal

 Start Mode
 Window
This describes the local maintenance terminal (LMT). The LMT provides the authority
management, alarm management, device maintenance, and message tracing functions through a
graphic user interface (GUI). The LMT also provides abundant command line interface (CLI)
commands with which you can maintain the device and manage the performance.
NOTE:
For details about how to run the CLI commands, refer to online help.
Start Mode
Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) > Local
Maintenance Terminal(Enhanced).
Window
The LMT window comprises the system menu, tool bar, navigation pane, output pane, client
pane, and status bar. The client pane provides the command line client, device panel, and tracing
pane.
Figure 1 shows the interface of the LMT when the CLI command line client is displayed in the
client window.
Figure 1 GUI of the LMT
1. Menu 2. Toolbar 3. Navigation tree pane

4. Output pane 5. Status bar 6. Command display pane
Parent Topic: LMT Software
Next topic >
< Home
6.4.2.1.2 FTP Client

 Starting the FTP Client
 Window
 Main Menu
 Toolbar
The FTP client communicates with the FTP server through the FTP protocol. They exchange the
performance data, configuration data, and maintenance data. Thus, the quality of service (QoS) is
improved.
Starting the FTP Client
Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) > FTP
Client(Enhanced).
NOTE:
FTP has security risks. You are advised to use secure protocols, such as SFTP and FTPS.
Use the SSL encryption mode for transmission to prevent data leakage. You can use the default
SSL certificate or a customized SSL certificate for encrypted transmission as required. If a
customized SSL certificate is used, you can choose to enter a private key. The SSL certificate is
stored in LMT installation directory\client\ftpclient\data. You can replace the certificate file in
this path with a customized certificate file.
The SRU/MPU serves as an FTP server when the FTP client backs up data. Run ftp server
enable to start the FTP server of the UGW9811 before using the FTP function.
Window
The window of the FTP client comprises the menu bar, toolbar, server input area, Local Folder
List, Local File List, Server File List, and Connection tips. See Figure 1.
Figure 1 FTP Client window
1. Menu 2. Toolbar 3. Local folder list

4. Local File List 5. FTP server input area 6. Server File List
7. Connection tips - -
If encryption-mode is set to encrypted in the ftps server-configuration command, SSL in the

FTP server input area of the FTP client must be selected.
The port number set in the FTP server input area of the FTP client must be the same as the port
number set in the ftp server port command.
Main Menu
Table 1 Functions of the main menu
Menu Item Function

System Connect It is used to set up connection with the server.
Disconnect It is used to disconnect from the server.
Reconnect It is used to re-establish the connection with the
server.
Delete Local Item You can manage local files and delete an
unnecessary file directly at the FTP Client when
the Client is connected with the Server.
Delete Server Item You can manage server files and delete an
unnecessary unlocked file directly at the FTP
Table 1 Functions of the main menu
Menu Item Function

Client when the Client is connected with the
Server.
Exit Exit from the FTP client.
Transfer Download From Multiple files can be simultaneously downloaded
Server to the FTP Client.
Upload To Server Multiple files can be simultaneously uploaded
from the FTP Client.
View Refresh Refresh view.
Toolbar It determines whether to display the toolbar.
Status Bar It determines whether to display the status bar.
Help Help Topics It is used to display the help of the monitor
viewer.
About It is used to display the version and copyright of
the monitor viewer.
Toolbar
Table 2 Functions of the icons in the toolbar
Icon Function
To set up connection with the server.
To disconnect from the server.
To re-establish the connection with the server.
To download files from the server.
To upload local files.
To refresh local view.
To delete local files.

Table 2 Functions of the icons in the toolbar
Icon Function
To delete files from the server.
To open the help of the FTP client.
< Home
6.4.2.1.3 FTP Server

 Start Mode
 Window
This describes the File Transfer Protocol (FTP) server. The local computer can be used as an
FTP server for access if the parameters of the FTP server are set.
Start Mode
Choose Start > Programs > HUAWEI Local Maintenance Terminal > FTPSServer.
For details about how to configure FTP server, refer to Configuring the FTP Service.
Window
After the FTP server is started, the system icon is displayed on the taskbar. You can set,
stop, or log out of the FTP server by right-clicking the icon.
Figure 1 shows the configurations of the FTP server. Table 1 lists the parameter settings.
Figure 1 Configurations of the FTP server

Table 1 Parameter settings of the FTP server
Parameter Description
User name When you use the FTP server for the first time, enter the default
password hwbs@com and then change the user name and password..
Password The default password is hwbs@com.
Working directory It is the path where the executed file is saved. By default, it is
D:\HWLMT_Enhanced\adaptor\serveradaptor\UGW9811\lib. All the
related log information is saved in this path.
Port number The default port number of the FTP server is 21.
Thread number It specifies the number of the processes that can be initiated. The
default value is 50.
Plain text Indicates that the traffic encryption mode is plain text.
Encrypted Indicates that the traffic encryption mode is encrypted.
Both Indicates that the FTP server will change the traffic encryption mode
to plain text or encrypted according to the configuration of the FTP
client.
SSL Settings Set SSL parameters.
If encryption-mode is set to encrypted in the ftps client-configuration command, Encrypted

or Both in the parameter configuration window of the FTP server must be selected.
The port number set in the parameter configuration window of the FTP server must be the same
as the port number set in the ftps destination-port command. ftps destination-port specifies
one port number for every FTP server. If the port number for the FTP server is not specified, the
port number is 21 by default.
< Home
6.4.2.1.4 LMT Service Manager

 Start Mode
 Window
This describes the local maintenance terminal (LMT) service manager. The LMT service
manager enables the communication between the LMT software and the SRU/MPU. In addition,
it can manage the server processes. You need not start the LMT service manager manually.
If the LMT service manager is not shut down properly or does not automatically start, you need
to start it manually. Otherwise, the LMT cannot be connected to the UGW9811.
Start Mode
You can start the LMT service manager by using either of the following modes:
 Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) > LMT Service
Manager(Enhanced).
 After the LMT software is installed, the LMT service manager automatically starts when the PC
with the LMT software starts.
Window
After the LMT service manager starts, the system icon is displayed on the taskbar. Right-
click on . Then, you can choose Open LMT service manager to start the LMT service
manager or choose Exit LMT service manager to shut down the LMT service manager. Figure
1 shows the LMT Service Manager window.
Figure 1 LMT Service Manager window
NOTE:
LMT Server is the process module of the LMT server. The client communicates with the
process module through the CORBA interface. In addition, the client is connected to the
SRU/MPU through this interface.
You can connect the LMT with the server or disconnect the LMT from the server through the
LMT service manager in either of the following ways:
 Right-click on LMT Server. You can choose Start from the shortcut menu to set the status to
Started. You can choose Stop to set the status to Stopped.
 You can choose Operation > Start to set the status to Started. You can choose Operation > Stop
to set the status to Stopped.
In the LMT service manager, when the status of the LMT server is Stopped, the following
problems may arise:
 You cannot log in to the LMT if you have not logged in to it.
 The LMT is disconnected from the LMT server if you have logged in to the LMT.

< Home
6.4.2.1.5 Trace Viewer

 Start Mode
 Window
This describes the trace viewer. The trace viewer is used to view offline the saved trace files
whose extension names are .tmf. In this way, the trace messages can be viewed.
For the method of saving tracing file, see Saving CPU Usage Monitoring Results.
NOTE:
A UGW9811 trace viewer can parse traced files generated by trace viewers of earlier versions.
However, trace viewers of V900R009C01 and later versions cannot parse traced files generated
by trace viewers of versions earlier than V900R009C01.
Start Mode
You can start the trace viewer in one of the following ways:
 Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) > Trace
Viewer(Enhanced).
 Choose in the toolbar in the LMT window.

 Choose View > Trace Viewer in the LMT window.
Window
The trace viewer window comprises the system menu, toolbar, and pane for browsing trace
messages, as shown in Figure 1.
Figure 1 Trace Viewer window

(1)System menu (2)Toolbar (3)Browsing trace messages
- - -
< Home
6.4.2.1.6 Monitor Viewer

 Start Mode
 Window
This describes the monitor viewer. The monitor viewer is used to review the data and display the
state by opening the monitor file with the extension name .mrf.
For the method of saving monitor file, see Saving CPU Usage Monitoring Results.
Start Mode
You can start the monitor viewer in one of the following ways:
 Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) > Monitor
Viewer(Enhanced).
 Choose in the toolbar in the LMT window.

 Choose View > Monitor Viewer in the LMT window.
Window
The monitor viewer window comprises the system menu, toolbar, and pane for browsing monitor
data, as shown in Figure 1.
Figure 1 Monitor Viewer window
(1)System menu (2)Toolbar (3)Pane for browsing monitor data

— — —
< Home
6.4.2.1.7 Performance Browser Tool

 Start Mode
 Window
This describes the performance browser tool. The performance browser tool is used to manage
performance measurement tasks and check performance measurement results.
For the method of using performance browser tool, see Operations of the Performance Browser
Tool.
Start Mode
Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) >
Performance Browser Tool(Enhanced).
Window
The window of the performance browser tool comprises the system menu, toolbar, performance
browsing window, and status bar, as shown in Figure 1.
Figure 1 Performance Browse Tool window
(1)System menu (2)Toolbar (3)Performance browser window

(4)Status bar - -
< Home
6.4.2.1.8 Convert Management System

 Start Mode
 Window
This describes the convert management system. The convert management system is used to
transfer the alarm to the alarm box.
Start Mode
Choose Start > All Programs > HUAWEI Local Maintenance Terminal(Enhanced) >
Convert Management System(Enhanced).
Window
After the LMT service manager starts, the system icon is displayed on the taskbar. Right-
click on . Then, you can choose Restore. Alternatively, you can click the system icon
to display the Convert Management System window. If you right-click the system icon ,
and then choose Exit, the convert management system shuts down.
When the serial port connected to the alarm box is faulty during communication, the system icon
is displayed on the taskbar.
The convert management system window comprises the title bar, system menu, toolbar, output
pane, and status bar, as shown in Figure 1.
Figure 1 Convert Management System window
(1)title bar (2)System menu (3)Toolbar

(4)Output pane (5)Status bar -
< Previous topic
< Home
6.4.2.2 Directory Structure of the LMT

Software
This describes the directory structure of the local maintenance terminal (LMT) software on the
PC.
Table 1 describes the directory structure of the LMT software on the PC.
NOTE:
$ indicates the installation path of the LMT software.
Table 1 Directory structure of the LMT software
Directory Secondary Tertiary Remarks

Subdirectory Subdirectory
$\server lmtserver \bin Directory of the system files of the
server and relevant *.DLL files
(Directory of
\etc Directory of the modules such as alarm
the platform
modules of the server
and
functional \var Directory of the files such as the logs of
modules of the server
the LMT
service
server)
$\adaptor \serveradaptor \common Directory of the adaptation information
about the universal functions of the
(Directory of (Directory of server platform
the adaptation the adaptation
\imap Directory of the information about the
modules) modules of the
iMap platform configured by the
server)
adaptation modules
\UGW9811 Directory of the information about the
UGW9811 configured by the adaptation
modules
\Public Directory of the information about
public adaptation or functions
\lib Directory of the information about
functions and library files provided by
the adaptation modules
\ProductVersion.xml Product version adaptation file
\clientadaptor \common Directory of the adaptation information
about the universal functions of the
client platform
Table 1 Directory structure of the LMT software
Directory Secondary Tertiary Remarks

Subdirectory Subdirectory
(Directory of \imap Directory of the information about the
the adaptation iMap platform configured by the
modules of the adaptation modules
client)
\ilmt Directory of the information about the
functional modules configured by the
adaptation modules
\UGW9811 Directory of the UGW9811
\convert Directory of the alarm forwarding files
\pfbTool Directory of the performance browser
files
$\client - - Directory of the platform and functional
modules of the LMT client
$\tray bin - Directory of the execution files of the
LMT service manager and relevant
(Directory of *.DLL files
the functional
data - Directory of the configuration files of
modules of
the LMT service manager
the LMT
service ico - Directory of the icon of the LMT
manager) service manager
log - Directory of the log files of the LMT
service manager
$\uninstall - - Directory of the uninstallation files of
the LMT
6.5 Function Description

Introduction to function description:
Access Functions
QoS Functions
Intelligent Policy Control Based on Service Awareness

System Overload Control
Parent Topic: Descriptions
< Home
6.5.1 Access Functions

Access System Overview
Subscriber Access
APN Selection
Access Control
Address Assignment
Session Management
Parent Topic: Function Description
Next topic >
< Home
6.5.1.1 Access System Overview

 Basic Concepts
The UGW9811 access system provides a number of functions for 3rd Generation Partnership
Project (3GPP) and trusted non-3GPP subscribers and untrusted non-3GPP subscribers. These
functions include access, access point name (APN) selection, access control, address assignment,
and session management. When a mobile station/user equipment (MS/UE) accesses an evolved
packet core (EPC) network through a General Packet Radio System/Universal Mobile
Telecommunications System (GPRS/UMTS), Long Term Evolution (LTE), Code Division
Multiple Access 2000 (CDMA2000) network or WiFi network, the UGW9811 access system
sets up a connection for transmitting subscriber data packets between the MS/UE and a packet
data network (PDN). Figure 1 shows the logical architecture of the UGW9811 access system.
Figure 1 Logical architecture of the UGW9811 access system

Basic Concepts
This section describes the basic concepts that enable you to better understand the UGW9811
access system.
GTP
The GTP is a communication protocol between GGSNs/P-GWs and Gn/GP SGSNs on a

GPRS/UMTS network. The GTP includes GTP-Control plane (GTP-C) and GTP-User plane
(GTP-U). GTP-C is used within the GPRS core network for signaling between GGSNs and
SGSNs. GTP-U is used for carrying user data within the GPRS core network and between the
radio access network (RAN) and the core network. For details, see 3GPP TS 29.060.
GTPv2 (enhanced GTP-C) is used for communication between S-GWs and MMEs/S4 SGSNs
and between P-GWs and S-GWs on an EPC network. For details, see 3GPP TS 29.274. GTP-U
of GTPv1 is used for communication between S-GWs and eNodeBs/RNCs and between P-GWs
and S-GWs.
When UEs access the EPC network through a trusted non-3GPP network, GTPv2 enables
communication between an Trusted WLAN Access Network (TWAN) and a P-GW.
PMIP
PMIPv6 is an IETF-defined (RFC5213) communication protocol between MAGs and local

mobility anchors (LMAs).
On an EPC network, PMIPv6 enables an S-GW and a P-GW to interwork, with the S-GW
functioning as an MAG and the P-GW functioning as an LMA.
When UEs access the EPC network through a trusted non-3GPP network, PMIPv6 enables
communication between an HRPD serving gateway (HSGW) and a P-GW, with the HSGW
functioning as an MAG and the P-GW functioning as an LMA.
Subscriber data packets are encapsulated using Generic Routing Encapsulation (GRE) and
transmitted through PMIPv6 tunnels.
Session
A session is a logical connection for data exchange between MSs/UEs and PDNs.
On a GPRS/UMTS network, primary Packet Data Protocol (PDP) contexts are used to
implement subscriber sessions. A session can include multiple secondary PDP contexts.
On an Evolved Packet System (EPS) network, subscriber sessions are PDN connections. A PDN
connection includes a default bearer that is set up during subscriber attach and multiple dedicated
bearers that are set up after subscriber attach.
When MSs/UEs access an EPC network through a GPRS/UMTS network, the MSs/UEs use PDP
context activation procedures to attach to the EPC network. PDP contexts are used between the
MSs/UEs and an S4 SGSN. The S4 SGSN maps PDP contexts to EPS bearers and then send
messages to an S-GW and a P-GW to initiate EPS bearer setup procedures. For details, see 3GPP
TS 23.060.
PDP context
On a GPRS/UMTS network, MSs/UEs initiate PDP context activation procedures to set up data
channels to PDNs.
Activated PDP contexts are stored on MSs/UEs, the SGSN, and the GGSN/P-GW to provide
subscribers with access to data services. After PDP context activation, MSs/UEs or the network
side can initiate secondary PDP context activation procedures. For details, see 3GPP TS 23.060.
EPS bearer
On an EPS network, a default EPS bearer is set up when a UE initiates an attach procedure or
requests a connection to a PDN. The default EPS bearer is not released until the UE is detached,
which ensures always-on IP connectivity between the UE and PDN. After default EPS bearer
setup, the network side can initiate a dedicated bearer setup procedure to the PDN. For details,
see 3GPP TS 23.401.
Parent Topic: Access Functions
Next topic >
< Home
6.5.1.2 Subscriber Access

 Access Type
 Path Management
 Blacklist/Whitelist
 Roaming Attribute
Access Type
The UGW9811 supports the following access types:
 3GPP network access

 Trusted non-3GPP network access
 PPP over GTP
 Untrusted non-3GPP network access
When the UGW9811 functions as a combined gateway, it supports both general packet radio
system (GPRS) and evolved packet system (EPS) data services. After the functions of the
gateway GPRS support node (GGSN), S-GW, and P-GW are deployed on the UGW9811, the
UGW9811 supports GSM/UMTS/LTE convergence access support.
After accessing a network, a subscriber can switch between different networks, including:
 Mobility management
 Inter-RAT mobility between LTE and GSM/UMTS
 Handover without optimizations between LTE and eHRPD
Path Management
The IP connection between the UGW9811 and the access side network element (NE) is called a
path.
3GPP subscribers can access the UGW9811 through the Gn/Gp-serving GPRS support node
(SGSN) with the path running GTPv0/GTPv1. 3GPP subscribers can also access the UGW9811
through the S4-SGSN/mobility management entity (MME) with the path running GTPv2. The
UGW9811 and the access side NE can periodically send echo messages to detect the path status,
implementing path management.
Trusted non-3GPP subscribers can access the UGW9811 through the HRPD serving gateway
(HSGW) with the path running Proxy Mobile IP (PMIP)v6. The UGW9811 and the access side
NE can periodically send echo messages to detect the path status, implementing PMIP
management.
Blacklist/Whitelist
The blacklist/whitelist is an IP address range configured on the UGW9811. When a subscriber

sends an activation or update request to the UGW9811 through the access side NE (SGSN,
MME, or S-GW), the UGW9811 uses the blacklist/whitelist to check whether the IP address of
the access side NE is valid to determine whether to allow the subscriber to activate or update.
Roaming Attribute
After a subscriber accesses the UGW9811, the UGW9811 extracts the subscriber's public land
mobile network (PLMN) ID, matches it with the locally configured home PLMN (HPLMN) to
identify the subscriber's roaming attribute (local subscriber, visitor, or roaming subscriber), and
performs charging and service policy control according to the roaming attribute.
< Home
6.5.1.3 APN Selection
 APN Introduction
 APN Mapping
APN Introduction
An access point name (APN) is a network identifier defined by general packet radio system
(GPRS)/evolved packet system (EPS) standards. The GPRS/EPS network uses APNs to identify
UGW9811s. An APN identifies an external packet data network (PDN) that is connected to a
UGW9811, or a service. The external PDN may be an Internet service provider (ISP) network or
an intranet. The service may be an Internet access service or a Wireless Application Protocol
(WAP) service.
As specified in 3GPP TS 23003, the APN is composed of the following two parts:
 APN network identifier: defines the external network to which the gateway GPRS support node
/PDN gateway (GGSN/P-GW) is connected and an optional service requested by the mobile
station/user equipment (MS/UE). This part of the APN is mandatory.
An APN is assigned to the ISP or an enterprise by a carrier and is the same as the Internet
domain name. For example, the APN network identifier can be planned as
"enterprise.com" for a mobile subscriber to access an intranet through the UGW9811.
 APN operator identifier: defines in which public land mobile network (PLMN) GPRS/EPS
backbone the GGSN/P-GW is located. This part of the APN is optional.
Each carrier has a default APN operator identifier in the format of

MNCxxxx.MCCyyyy.gprs in UMTS networks and
MNCxxxx.MCCyyyy.3gppnetwork.org in LTE networks, in which MNCxxxx and
MCCyyyy uniquely identify the home PLMN to which the UGW9811 belongs.
The UGW9811 controls which PDNs a mobile node (MN) is allowed to access through the
UGW9811. The access points for the external PDNs and APN information are configured on the
UGW9811. The domain name system (DNS) server on the GPRS/EPS network should associate
the APN with the UGW9811's IP address to ensure that the SGSN/MME can address this
UGW9811 based on the APN provided by the MS/UE. In this manner, the MS/UE can access the
corresponding PDN.
In addition, policies, such as accounting, quality of service (QoS), security, and service control
policies, can be configured on the UGW9811 based on APNs to implement flexible accounting
and service control.
The UGW9811 supports the following APNs:
 Actual APN: corresponds to a PDN and is used to enable access to a specified PDN.
 Virtual APN: must be mapped to an actual APN according to the mapping rule configured on the
UGW9811 to enable access to a specified PDN.
One virtual APN maps to multiple actual APNs.
 Alias APN: must be mapped to an actual APN according to the mapping rule configured on the
UGW9811 to enable access to a specified PDN.
Multiple alias APNs map to one actual APN.
NOTE:
Actual APNs can be configured on the UGW9811. For details, see apn. Configuring an actual
APN refers to configuring an APN network identifier (APN NI), which must have been
configured before a virtual APN and alias APN are configured on the UGW9811. An APN NI is
a string of 1 to 63 case-insensitive characters without any spaces or special characters such as _,
#, $, and &. An APN NI consists of letters, numbers, and hyphens but cannot start or end with a
hyphen.
APN Mapping
An actual APN, virtual APN, or alias APN is carried in an activation request during subscriber
access. Based on local configurations, the UGW9811 maps the virtual APN or alias APN carried
in the message to an actual APN to enable access to a specified PDN.
Virtual APN Mapping Mechanism
The UGW9811 maps a virtual APN to the actual APN according to the virtual APN mapping
rule configured locally by international mobile subscriber identity (IMSI), mobile station
international ISDN number (MSISDN), international mobile equipment identity (IMEI), or radio
access technology (RAT).
Besides obtaining the actual APN according to the virtual APN mapping rule, the UGW9811 can
use the APN returned using RADIUS as the actual APN. In this manner, the virtual APN carried
in the subscriber request must be authenticated on the AAA server. The UGW9811 accesses the
AAA server specified by the virtual APN after the subscriber accesses the UGW9811 and
obtains the actual APN after the authentication succeeds.
If the actual APN obtained must also be authenticated on an AAA server, the UGW9811 must
access the AAA server specified by the actual APN, which may be the same as or different from
that specified by the virtual APN. Then, secondary authentication occurs.
Alias APN Mapping Mechanism

An alias access point name (APN) allows many APNs on an existing network to be compatible
with each other. If a carrier intends to map services from different APNs to the same APN or
from one APN to another APN, the UGW9811 only needs to be mapped the alias APN carried
by a subscriber to an actual APN. This allows different APNs to share the same system resources
and facilitates allocation and combinations of system resources.
< Home
6.5.1.4 Access Control

The UGW9811 implements admission control based on the bandwidth, number of subscribers,
and admission control blacklist/whitelist so that online subscribers' services are not affected by
excess online subscribers or bandwidth usage.
Subscribers can access packet data networks (PDNs) in three access modes:
 Transparent access mode: Subscribers can access the UGW9811 without authentication.
 Non-transparent access mode: Subscribers must be authenticated before accessing the
UGW9811 but can subscribe to customized services.
The UGW9811 supports optional APN authentication modes, including authentication

based on the user name, mobile station international ISDN number (MSISDN), and
access point name (APN), simplifying configurations on the mobile station/user
equipment (MS/UE) and Authentication, Authorization and Accounting (AAA) server.
 Transparent authentication access mode: Public user names and passwords are used for
authentication so that subscribers can still access PDNs if their user names or passwords are
unavailable or incorrect.

< Home
6.5.1.5 Address Assignment

A mobile station/user equipment (MS/UE) can use data services after being assigned an IP
address. The IP address can be a public or private network address and can be dynamically or
statically assigned. The UGW9811 supports the following address assignment modes:
 Static address assignment: In this mode, assigned IP addresses are the static addresses that an
MS/UE subscribes to on the home location register/home subscriber server (HLR/HSS) and are
always used during the data service.
The UGW9811 does not assign static addresses. It only checks address conflicts and
distributes downlink routes.
 Local address pool assignment: In this mode, assigned IP addresses are the dynamic addresses
obtained from the address pool configured on the UGW9811.
The UGW9811 assigns and reclaims these addresses.
 Remote Authentication Dial-In User Service (RADIUS) address assignment: In this mode,
assigned IP addresses are those assigned by the Authentication, Authorization and Accounting
(AAA) server during RADIUS authentication.
The UGW9811 checks address conflicts and distributes address routes.
 Dynamic Host Configuration Protocol (DHCP) address assignment: In this mode, assigned IP
addresses are the dynamic addresses obtained from the address pool configured on a DHCP
server that is separately deployed by a carrier or on an intranet.
The UGW9811 checks address conflicts and distributes address routes.
Local address pool assignment, RADIUS address assignment, and DHCP address assignment are
dynamic address assignment modes. The address assignment mode to be used depends on the
address assignment mode and priority configured for an access point name (APN) on the
UGW9811.
IPv4 addresses, IPv6 addresses, or dual-stack addresses can be assigned to MSs/UEs.
< Home
6.5.1.6 Session Management

In session management, a connection is created between a mobile station/user equipment
(MS/UE) and a packet data network (PDN) and is processed, including the establishment,
update, and deletion of Packet Data Protocol (PDP) contexts/evolved packet system (EPS)
bearers.
PDP contexts/EPS bearers that are established using the same IP address and access point name
(APN) belong to the same session, as shown in Figure 1. On an EPS network, one UE can use
multiple IP addresses and APNs to create connections to multiple PDNs through one or more
PDN gateways (P-GWs). On a general packet radio system/Universal Mobile
Telecommunications System (GPRS/UMTS) network, you can configure the GWFD-110905
Multi-service APN feature to create connections to multiple PDNs.
Figure 1 Subscriber session logic
Primary PDP Context Activation/Default Bearer Creation
Create PDP Context Request and Create PDP Context Response messages are transmitted
between the serving GPRS support node (SGSN) and gateway GPRS support node (GGSN) to
activate the primary PDP context. Create Session Request and Create Session Response
messages are transmitted between the serving gateway (S-GW) and P-GW to create the default
bearer. The primary PDP context/default bearer is the first bearer of a session. Bearers created
subsequently are secondary PDP contexts/dedicated bearers.
Secondary PDP Context Activation/Dedicated Bearer Establishment
After a subscriber requests a service that requires a special quality of service (QoS) guarantee,
the UGW9811 can activate a secondary PDP context or create a dedicated bearer.
Secondary PDP contexts/dedicated bearers and the primary PDP context/default bearer use the
same IP address and APN but different QoS parameters. The traffic flow template (TFT) defines
the service represented by each secondary PDP context/dedicated bearer.
As specified in 3GPP TS 24.008, a TFT includes a group of packet filters, which can be in an
uplink direction, a downlink direction, or in both directions. Packet filters determine the
secondary PDP contexts/dedicated bearers corresponding to data services. The GGSN/P-GW
uses downlink packet filters and MS/UE uses uplink packet filters.
For secondary PDP context activation initiated by a subscriber, the MS/UE provides the TFT.
For secondary PDP context activation initiated by the network sidesecondary PDP context
activation initiated by the network side, the policy and charging rules function (PCRF) provides
the TFT. Only the network side can initiate the dedicated bearer establishment, and the PCRF/P-
GW provides the TFT.
PDP Context/Bearer Update

Update PDP Context Request and Update PDP Context Response messages are transmitted
between the SGSN and GGSN to change the parameter (such as the QoS, TFT, and GTP version)
values of an activated PDP context. This procedure can be initiated by the MS/UE, radio network
controller (RNC), SGSN, or GGSN. Modify/Update Bearer Request and Modify/Update Bearer
Response messages are transmitted between the S-GW and P-GW to change the parameter (such
as the QoS and TFT) values of an EPS bearer. This procedure can be initiated by the UE, home
subscriber server (HSS), or P-GW.
PDP Context Deactivation/Bearer Deletion
Delete PDP Context Request and Delete PDP Context Response messages are transmitted
between the SGSN and GGSN to release a PDP context. This procedure can be initiated by the
MS/UE, SGSN, or GGSN. Delete Bearer Request and Delete Bearer Response messages are
transmitted between the S-GW and P-GW to delete an EPS bearer. This procedure can be
initiated by the mobility management entity (MME) or P-GW.
The UGW9811 can reclaim PDP contexts/EPS bearers to reduce the memory used by unused
PDP contexts/EPS bearers. Reclaiming operations include deactivating idle PDP contexts/EPS
bearers, deactivating online PDP contexts/EPS bearers that have expired for a period of time, and
manually deactivating specified PDP contexts/EPS bearers.
During deactivation, the IP address of an MS/UE is released, and PDP contexts/EPS bearers are
deleted from the related network elements (NEs). After a PDP context/EPS bearer is deactivated,
the MS/UE cannot use the corresponding data service.
< Previous topic
< Home
6.5.2 QoS Functions

Concepts of the QoS
QoS Implementation on MBB Networks
Huawei Recommended Bandwidth Management Solution
Specialized QoS Guarantee Schemes
Parent Topic: Function Description

< Home
6.5.2.1 Concepts of the QoS

QoS Overview
QoS Specifications
Basic 3GPP QoS Principles
Key QoS Parameters in 3GPP Networks
Parent Topic: QoS Functions
Next topic >
< Home
6.5.2.1.1 QoS Overview

 Traditional Packets Transmission Application
 New Applications Requirements
This section describes the basic concepts of the Quality of Service (QoS), traditional packet
delivery services, new demands resulting from new services, and QoS features supported by the
product.
QoS is a term that describes the relations between demands and supplies. It is a measurement
reflecting the ability of a supplier to meet the demands of customers. Usually, the QoS
assessment does not provide the accurate score. Instead, it focuses on the quality of service under
certain conditions so that the quality of the service that is found defective can be improved
accordingly.
On the Internet, QoS is used to assess the ability of the network to transmit packets. The network
provides a wide variety of services. Therefore, QoS assesses the service from different aspects.
Generally, QoS is used to assess the ability to meet the core requirements for packet
transmission, including delay, jitter, and packet loss ratio.
Traditional Packets Transmission Application
It is difficult to ensure QoS in the traditional IP network. Because routers in the network handle
all the packets equally and adopt First In First Out (FIFO) method to transfer packets. Resources
used for forwarding packets are allocated based on the arrival sequence of the packets.
All packets share the bandwidth of networks and routers. Resources are allocated according to
the arrival time of the packets. This policy is called best effort (BE) . The device in this mode
tries its best to transmit packets to the destination. The BE mode, however, does not ensure any
improvement in delay time, jitter, packet loss ratio, and high reliability.
The traditional BE mode applies only to services such as World Wide Web (WWW), file
transfer, and email, which have no specific request for bandwidth and jitter.
New Applications Requirements
With the rapid development of the network, increasing number of networks are connected to the
Internet. The Internet expands greatly in size, scope, and users. The use of the Internet as a
platform for data transmission and implementation of various applications is on the rise. Further,
the service providers also want to develop new services for more profits.
Apart from traditional applications such as WWW, email, and File Transfer Protocol (FTP), the
Internet has expanded to accommodate other services such as E-learning, telemedicine,
videophone, videoconference, and video on demand. Enterprise users want to connect their
branches in different areas through VPN technologies to implement applications such as
accessing corporate databases or managing remote devices through Telnet.
These new applications put forward special requirements for bandwidth, delay, and jitter. For
example, videoconference and video on demand require high bandwidth, low delay, and low
jitter. Telnet stresses on low delay and priority handling in the event of congestion.
As new services spring up, the number of requests for the service capability of IP networks has
been on the rise. Users expect improved service transmission to the destination and also better
quality of services. For example, IP networks are expected to provide dedicated bandwidth,
reduce packet loss ratio, avoid network congestion, control network flow, and set the preference
of packets to provide different QoS for various services.
All these demand better service capability from the network, and QoS is just an answer to the
requirements.
Parent Topic: Concepts of the QoS
Next topic >
< Home
6.5.2.1.2 QoS Specifications

 Bandwidth/throughput
 Delay
 Jitter(Delay variations)
 Packet loss rate
QoS provides customized service guarantees based on the following specifications:
 Bandwidth/throughput
 Delay
 Jitter(Delay variations)
 Packet loss rate
Bandwidth/throughput
Bandwidth, also called throughput, refers to the maximum number of bits allowed to transmit
between two ends within a specified period (1 second) or the average rate at which specific data
flows are transmitted between two network nodes. Bandwidth is expressed in bit/s.
As services become increasingly diversified, Internet Citizens expect higher bandwidths so they
cannot only browse the Internet for news but also experience any number of popular
applications. The epoch-making information evolution continually delivers new and attractive
applications, such as new-generation multimedia, video transmission, database, and IPTV, all of
which demand extremely high bandwidths. Therefore, bandwidth is always the major focus of
network planning and provides an important basis for network analysis.
Delay
A delay refers to the period of time during which a packet is transmitted from a source to its
destination.
Use voice transmission as an example. A delay refers to the period during which words are
spoken and then heard. If a long delay occurs, voices become unclear or interrupted.
Most users are insensitive to a delay of less than 100 ms. If a delay ranging from 100 ms to 300
ms occurs, the speaker can sense slight pauses in the responder's reply, which can seem annoying
to both. If a delay greater than 300 ms occurs, both the speaker and responder obviously sense
the delay and have to wait for responses. If the speaker cannot wait but repeats what has been
said, voices overlap, and the quality of the conversation deteriorates severely.
Jitter(Delay variations)
Jitter refers to the difference in delays of packets in the same flow. If the period before a packet
that has reached a device is sent by the device differs from one packet to another in a flow, jitters
occur, and service quality is negatively affected.
Specific services, especially voice and video services, are zero-tolerant of jitters, which causes
interruptions in voice or video services.
Packet loss rate
Packet loss occurs when one or more packets traveling across a network fail to reach their
destination. Slight packet loss does not affect services. For example, users are unaware of the
loss of a bit or a packet in voice transmissions. If a bit or a packet is lost in video transmission,
the image on the screen becomes momentarily garbled but the image recovers very quickly. Even
if TCP is used to transmit data, slight packet loss is not a problem because TCP instantly
retransmits the packets that have been lost. If severe packet loss does occur, however, packet
transmission efficiency is affected. The packet loss rate indicates the severity of service
interruptions on networks and concerns users.
< Home
6.5.2.1.3 Basic 3GPP QoS Principles

Basic GPRS QoS Principles
Basic UMTS QoS Principles
Basic LTE QoS Principles
< Home
6.5.2.1.3.1 Basic GPRS QoS Principles

GPRS quality of service (QoS) parameters are transferred from a serving GPRS support node
(SGSN) to a gateway GPRS support node (GGSN). The GGSN then converts GPRS QoS
parameters into UMTS QoS parameters and applies the UMTS QoS parameters to services.
The mapping between GPRS QoS parameters and UMTS QoS parameters complies with 3GPP
specifications and is not configured using commands. Table 1 and Table 2 describe the mapping
between the two types of QoS parameters.
Table 1 Mapping from GPRS QoS parameters to UMTS QoS parameters
UMTS QoS Parameters GPRS QoS Parameters

Parameter Name Parameter Value Parameter Value Parameter Name
Traffic class Interactive 1, 2, 3 Delay class
Background 4
Traffic handling 1 1 Delay class
priority
2 2
3 3
SDU error ratio 10-6 2 Reliability class
10-4 3
10-3 4, 5
Residual bit error ratio 10-5 2, 3, 4 Reliability class
4 x 10-3 5
Delivery of erroneous no 2, 3, 4 Reliability class
SDUs
yes 5
Maximum bitrate 8 1 Peak throughput class
[kbps]
16 2
32 3
64 4
128 5
256 6
512 7
1024 8
2048 9
Allocation/retention 1 1 Precedence class
priority
2 2
3 3
Delivery order yes yes Reordering Required
(information in the
no no
SGSN and the GGSN
PDP contexts)

Maximum SDU size 1500 octets - -
Priority Level of 1 to H 1 Precedence class
Evolved
H+1 to M 2
Allocation/retention
priority M+1 to 15 3
Table 2 Mapping from UMTS QoS parameters to GPRS QoS parameters
GPRS QoS Parameters UMTS QoS Parameters

Delay class 1 conversational Traffic class
1 streaming Traffic class
1 Interactive Traffic class
1 Traffic handling
priority
2 Traffic handling
priority
3 Traffic handling
priority
4 Background Traffic class
Reliability class 2 ≤ 10-5 SDU error ratio
NOTE:
If the software parameter

BIT1346 is set to 1, the
value of Reliability class
is 3.
3 10-5 < x ≤ 5 x 10-4 SDU error ratio
4 > 5 x 10-4 SDU error ratio
≤ 2 x 10-4 Residual bit error ratio

5 > 5 x 10-4 SDU error ratio
> 2 x 10-4 Residual bit error ratio
Peak throughput 1 < 16 Maximum bitrate
class [kbps]
2 16 ≤ x < 32
3 32 ≤ x < 64
4 64 ≤ x < 128
5 128 ≤ x < 256
6 256 ≤ x < 512
7 512 ≤ x < 1024
8 1024 ≤ x < 2048
9 ≥ 2048
Precedence class 1 1 Allocation/retention
priority
2 2
3 3
Mean throughput Always set to 31 - -
class
Reordering Required yes yes Delivery order
(information in the
no no
SGSN and the GGSN
PDP contexts)
Precedence class 1 1 Priority Level of the
Evolved
2 H+1
Allocation/Retention
3 M+1 priority
Parent Topic: Basic 3GPP QoS Principles
Next topic >
< Home
6.5.2.1.3.2 Basic UMTS QoS Principles
In order to provide end-to-end (E2E) quality of service (QoS), the mobile packet switched (PS) network
sets up and uses bearer services with clearly defined attributes and functionality from the source to the
destination of a service. 3GPP TS 23.107 defines the E2E QoS architecture in the UMTS system, as shown
in Figure 1.
Figure 1 UMTS QoS architecture
As illustrated by the UMTS QoS architecture, the bearer service at each layer is provided by the
bearer service of its lower layer. This section uses a UMTS UE that accesses packet data services
as an example to describe the basic UMTS QoS principles.
Generally, data service traffic of a UMTS UE, either a terminal equipment (TE) or mobile terminal (MT),
passes through the UE, a radio access network (RAN), a serving GPRS support node (SGSN), and a
UGW9811 before finally reaching an Internet server. In the UMTS QoS architecture, the data service
quality is guaranteed by the following QoS systems:
 QoS of the radio access bearer (RAB) between the UE and SGSN
The RAB QoS is composed of the QoS of the GPRS Tunnel Protocol (GTP) tunnel
between the RNC and SGSN and the QoS of the radio bearer between the RNC and UE.
The QoS of the backbone network bearer and the QoS of the physical bearer at the
bottom layer are also used during data transmission.
 QoS of the GTP tunnel between the SGSN and UGW9811
3GPP UMTS QoS is classified into conversational class, streaming class, interactive class, and
background class based on how delay-sensitive the traffic is. Conversational class traffic is the
most delay-sensitive, whereas background class traffic is the least. Table 1 describes the QoS
classes.
 Conversational and streaming classes are mainly used to carry real-time data flows. The
major difference between them is how delay-sensitive the traffic is. Typical
conversational class services include voice calls and video conference. Typical streaming
class services include real-time video stream services.
 Interactive and background classes are mainly used by traditional Internet applications.
These two classes are less delay-sensitive compared with conversational and streaming
classes. The major difference between interactive and background classes is that the
interactive class is mainly used by interactive applications, such as interactive web
browsing, whereas the background class is used for background traffic, such as
background file download. Interactive applications have higher priorities than
background applications. Therefore, when bandwidth resources are insufficient,
background applications are allowed to use resources only when interactive applications
are not using them. This restriction is very important in wireless environment where
bandwidth resources are scarce.
Table 1 QoS classes
QoS Class Basic Characteristic Example Application

Conversational Preserved time relationships between information Voice services
entities of streams; conversational pattern
(stringent and low delay)
Streaming Preserved time relationships between information Video services
entities of streams.
Interactive Request/response pattern; payload content Web browsing
preserved
Background Destination not expecting data within a specified Background email
time period; payload content preserved download
The following uses a conversational service as an example to describe QoS principles in different
procedures of the service.
1. UE-initiated PDP context activation or modification procedure

o A UE sends a PDP context activation or modification request message to the
RNC. The message carries the requested QoS parameters, including the traffic
class, guaranteed bit rate (GBR), and maximum bit rate (MBR).
o The RNC sends a PDP context activation or modification request message, which
carries the requested QoS parameters, to the SGSN.
o The SGSN interworks with the HLR to obtain the UE's subscription information,
checks whether the requested QoS parameters are supported by the subscribed
QoS, and obtains QoS parameters for negotiation. Then the SGSN sends a PDP
context activation or modification request message to the UGW9811.
o The UGW9811 obtains QoS control policies that are locally configured or
delivered by the PCRF, accepts or adjusts the requested QoS parameters, and
sends a PDP context activation or modification response message to the SGSN to
accept or reject the request based on available bandwidths. If the UGW9811
accepts the request, the UGW9811 includes negotiated QoS parameters in the
response message.
o The SGSN/RNC obtains the negotiated QoS parameters from the PDP context
activation or modification response message, reserves bandwidth resources as
specified by the QoS parameters, and forwards the response message to the UE.
If the UE's traffic exceeds the negotiated MBR, excess traffic is discarded, traffic
between the GBR and MBR is forwarded with a low priority, and traffic within
the GBR is forwarded with a high priority. By default, the UGW9811 provides
priority queuing (PQ) for expedited forwarding (EF) traffic.
o The UGW9811 applies the negotiated QoS to the UE's subsequent traffic of this
PDP context.
2. Data forwarding procedure
During a data forwarding procedure, the UGW9811 performs differentiated services code
point (DSCP) or type of service (ToS) mapping for conversational service data flows,
matches these data flows against service rules based on their traffic class, traffic attributes
(direction and time period), and user properties (including the RAT type and roaming
attribute), and performs bandwidth management accordingly. In this way, the UGW9811
implements low-delay and high-priority data forwarding for conversational services.
NOTE:
The IETF defines three per-hop behaviors (PHBs): EF, assured forwarding (AF), and best
effort (BE).
In the mapping from 3GPP QoS to IP QoS, the QoS of conversational class traffic maps
to the DSCP value EF by default.
< Home
6.5.2.1.3.3 Basic LTE QoS Principles

In order to provide end-to-end (E2E) quality of service (QoS), the mobile packet switched (PS) network
sets up and uses bearer services with clearly defined attributes and functionality from the source to the
destination of a service. 3GPP TS 23.401 defines the E2E QoS architecture in the LTE system, as shown in
Figure 1.
Figure 1 LTE QoS architecture
As illustrated by the LTE QoS architecture, the bearer service at each layer is provided by the
bearer service of its lower layer. This section uses an LTE UE that accesses packet data services
as an example to describe the basic QoS principles.
Generally, data service traffic of an LTE UE, either a terminal equipment (TE) or mobile terminal (MT),
passes through the UE, an E-UTRAN NodeB (eNodeB), a serving gateway (S-GW), and a PDN gateway (P-
GW) before finally reaching a service server. In the LTE QoS architecture, the data service quality is
guaranteed by the following QoS systems:
 QoS of the radio bearer between the UE and eNodeB
 QoS of the S1 bearer between the eNodeB and S-GW
 QoS of the S5/S8 bearer between the S-GW and P-GW
3GPP LTE QoS is classified into nine classes identified by QoS class identifiers (QCIs) 1 to 9
based on how sensitive the traffic is to delay and packet loss. Conversational class traffic is the
most sensitive to delay and packet loss. Table 1 describes the QoS classes.
Table 1 QoS classes
QCI Resource Priority Packet Packet Application Example

Type Data Loss Rate
Delay
(ms)
1 Guaranteed 2 100 10-2 Conversational voice
bit rate
2 4 150 10-3 Conversational video (live
(GBR)
streaming)
3 3 50 10-3 Real-time gaming
4 5 300 10-6 Non-conversational video (buffered
streaming)
5 Non-GBR 1 100 10-6 IMS signaling
6 6 10-3 Voice, video (live streaming)
interactive gaming
7 7 300 10-6 Video (buffered streaming)
8 8
TCP-based (for example, WWW,
9 9 email, chat, FTP, P2P file sharing,
and progressive video)
The following uses a conversational service as an example to describe QoS principles in different
procedures of the service.
1. UE-initiated bearer creation or modification procedure

o A UE sends a bearer creation or modification request message to the eNodeB. The
message carries the requested QoS parameters, including the QCI, GBR, and
maximum bit rate (MBR).
o After receiving the request message, the eNodeB sends a bearer creation or
modification request message, which carries the UE-requested QoS parameters, to
the MME.
o After receiving the request message from the eNodeB, the MME interworks with
the HSS to obtain the UE's subscription information, checks whether the
requested QoS parameters are supported by the subscribed QoS, and obtains QoS
parameters for negotiation. Then the MME sends a bearer creation or
modification request message to the UGW9811.
o After receiving the request message from the MME, the UGW9811 obtains QoS
control policies that are locally configured or delivered by the PCRF, accepts or
adjusts the requested QoS parameters, and sends a bearer creation or modification
response message to the MME to accept or reject the request based on available
bandwidths. If the UGW9811 accepts the bearer creation or modification request,
the UGW9811 includes negotiated QoS parameters in the response message.
o The MME/eNodeB obtains the negotiated QoS parameters from the bearer
creation or modification response message, reserves bandwidth resources as
specified by the QoS parameters, and forwards the response message to the UE.
If the UE's traffic exceeds the negotiated MBR, excess traffic is discarded, traffic
between the GBR and MBR is forwarded with a low priority, and traffic within
the GBR is forwarded with a high priority. By default, the UGW9811 provides
priority queuing (PQ) for expedited forwarding (EF) traffic.
o The UGW9811 applies the preceding QoS guarantee to the UE's subsequent
traffic of this bearer.
2. Data forwarding procedure
During a data forwarding procedure, the UGW9811 performs differentiated services code
point (DSCP) or type of service (ToS) mapping for conversational service data flows,
matches these data flows against service rules based on their traffic class, traffic attributes
(direction and time period), and user properties (including the RAT type and roaming
attribute), and performs bandwidth management accordingly. In this way, the UGW9811
implements low-delay and high-priority data forwarding for conversational services.
NOTE:
The IETF defines three per-hop behaviors (PHBs): EF, assured forwarding (AF), and best
effort (BE).
In the mapping from 3GPP QoS to IP QoS, the QoS of conversational class traffic maps
to the DSCP value EF by default.
< Previous topic
< Home
6.5.2.1.4 Key QoS Parameters in 3GPP
Networks
Key QoS Parameters in GPRS Networks
Key QoS Parameters in UMTS Networks
Key QoS Parameters in LTE Networks
< Previous topic
< Home
6.5.2.1.4.1 Key QoS Parameters in GPRS

Networks
The following QoS parameters are defined for GPRS networks:
 Precedence class
 Delay class
 Reliability class
 Peak throughput class
 Mean throughput class
Table 1 describes the key QoS parameters in GPRS networks.
Table 1 Key QoS parameters in GPRS networks
Precedence class This parameter indicates the priority for
processing GPRS service packets. For
example, when an abnormality (such as a
network congestion) occurs, low-priority
packets are first discarded. Three precedence
classes are defined:
 High
 Normal
Table 1 Key QoS parameters in GPRS networks
 Low
Delay class The delay class indicates the level of end-to-

end delay in service data unit (SDU)
transmission on GPRS networks. It can be set
to 1, 2, 3, or 4. A larger value indicates a
longer delay.
Parent Topic: Key QoS Parameters in 3GPP Networks
Next topic >
< Home
6.5.2.1.4.2 Key QoS Parameters in UMTS

Networks
The UMTS network defines the following QoS parameters:
 Allocation/retention priority
 Traffic class
 Maximum bit rate for uplink
 Maximum bit rate for downlink
 Guaranteed bit rate for uplink
 Guaranteed bit rate for downlink
 Traffic handling priority
 Delivery order
 Maximum SDU size
 SDU bit error ratio
 Residual BER
 Delivery of erroneous SDUs
 Transfer delay
Table 1 describes the key QoS parameters in UMTS networks.

Table 1 Key QoS parameters in UMTS networks
Allocation/retention priority The allocation/retention priority (ARP)
parameter is used in session establishment and
update request messages to implement control
on access priority in session management.
ARP parameters of subscribers are registered
on the HLR and delivered by the HLR to the
SGSN.
The UMTS core network delivers ARP

parameters through a RAB assignment or
relocation request message to a radio network
controller (RNC). The RNC then maps the
ARP parameters to user priorities based on
configured mapping rules. Carriers can
configure the desired mapping rules.
Traffic class Service flows can be scheduled based on their
traffic classes. Four traffic classes are
available, which are listed in descending order
of priority:
 Conversational
 Streaming
 Interactive
 Background
Guaranteed bit rate for uplink These two parameters are used for bandwidth
management. The system uses multiple
Guaranteed bit rate for downlink methods, including resource reservation, to
ensure that all data flows can pass through
when the bit rate does not exceed the
guaranteed bit rate (GBR). When the bit rate
exceeds the GBR, the system handles excess
traffic as follows:
 Discards traffic that exceeds the GBR

if congestion occurs.
 Allows traffic between the GBR and
MBR to pass through if no congestion
occurs.
Table 1 Key QoS parameters in UMTS networks
Maximum bit rate for uplink These two parameters are used for bandwidth
management. The system prohibits excess data
Maximum bit rate for downlink flows to pass through to ensure that the bit rate
of data flows does not exceed the maximum
bit rate (MBR). The uplink MBR and
downlink MBR must be greater than or equal
to the uplink GBR and downlink GBR,
respectively.
Traffic handling priority This parameter specifies the priority with
which interactive class traffic is handled in
logical channels.
Parent Topic: Key QoS Parameters in 3GPP Networks
< Home
6.5.2.1.4.3 Key QoS Parameters in LTE

Networks
Table 1 Key QoS parameters in LTE networks
Bearer Bearers are classified into guaranteed bit rate
(GBR) bearers and non-GBR bearers. GBR
bearers are identified by QoS class identifiers
(QCIs) 1 to 4, and non-GBR bearers are
identified by QCIs 5 to 9.
All default bearers are non-GBR bearers. A

dedicated bearer can be either a GBR bearer or
a non-GBR bearer.
Bearer IDs range from 5 to 15, allowing a

maximum of 11 bearers for each subscriber.
The QCIs of the default bearer and dedicated
bearer for the APN used by a subscriber must
be different.
QCI A QCI is an identifier used by UEs and mobile
network elements (NEs) to indicate QoS
characteristics of services. Services with
different QCIs are carried on different bearers.
Each QCI corresponds to a group of QoS
parameters. QoS parameters corresponding to
standard QCIs are preconfigured on NEs.
3GPP specifications define only standard QCIs

1 to 9. Extended QCIs ranging from 10 to 255
are available for customization.
ARP The ARP parameter specifies the priority of a
bearer establishment or modification request.
It is used only for access control but not for
service scheduling.
The primary purpose of ARP is to decide

whether a bearer establishment or modification
request is acceptable or should be rejected due
to insufficient resources on the radio access
network (RAN) side for the GBR bearer. RAN
side resources (air interface resources) are
limited, and certain bearers may fail to be
established due to resource limitation.
Therefore, the ARP parameter is generally
delivered to the eNodeB, which then
determines whether a bearer can be
established. The ARP parameter contains the
following elements:
 Priority level: used to ensure that the

request of the bearer with a higher
priority level is prioritized when
resources are insufficient. A smaller
value indicates a higher ARP priority
level. For example, when resources are
insufficient, a bearer whose ARP value
1 is preferentially established
compared with a bearer whose ARP
value is 2.
 Pre-emption capability: indicates
whether a service can pre-empt the
resources of a lower-priority service
when resources are limited.
 Pre-emption vulnerability: indicates
whether the resources of a service can
be pre-empted by a higher-priority
service when resources are limited.
GBR The GBR is generally used for bandwidth

management. The system uses multiple
methods, including resource reservation, to
ensure that all data flows can pass through
when the bit rate does not exceed the GBR.
When the bit rate exceeds the GBR, the system
handles excess traffic as follows:
 Discards traffic that exceeds the GBR

if congestion occurs.
 Allows traffic between the GBR and
maximum bit rate (MBR) to pass
through if no congestion occurs.
A bearer with GBR resources is called a GBR

bearer. Other bearers are called non-GBR
bearers.
MBR The MBR is generally used for bandwidth
management. The system disallows excess
data flows to pass through to ensure that the
bit rate of data flows does not exceed the
MBR. The MBR must be greater than or equal
to the GBR.
APN-AMBR The per APN aggregate maximum bit rate
(APN-AMBR) limits the aggregate bit rate
that can be expected for all non-GBR bearers
of the same APN. It is the maximum
bandwidth of all bearers from a UE to the
same P-GW.
The P-GW enforces the APN-AMBR in the

downlink. Enforcement of the APN-AMBR in
the uplink is implemented by the UE and P-
GW.
UE-AMBR The per UE aggregate maximum bit rate (UE-
AMBR) limits the aggregate bit rate that can
be expected for all non-GBR bearers of a UE.
It is the maximum bandwidth of all bearers of
a UE. The eNodeB enforces the UE-AMBR in
both the uplink and downlink.

Networking

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Networking

Uploaded by

Copyright:

Available Formats

SCTP is a reliable transport protocol operating on top of a connectionless packet

Table 1 Details about the Eth-trunk interface

ARP Probe for Logical Links

Table 2 Routing description

The UGW9811 supports both area authentication

The UGW9811 supports two hot backup modes:

o Backing up all OSPF data: In this mode,

GR is used to gracefully restart a router. This

If OSPF is not restarted in GR mode on a router,

 Multiple OSPF instances

OSPF supports multiple instances that can run

Concepts of OSPF Dynamic Routing

Table 3 lists concepts of OSPF dynamic routing.

Table 3 Concepts of OSPF dynamic routing

 The length of the IP address subnet mask of an interface is not shorter

DR priority When configuring broadcast networks or non-broadcast multiple access

 Supporting single-hop and multi-hop detection.

For details, see GWFD-111004 BFD Function and GWFD-011000 Reliability.

Typical Networking Solutions Between the UGW9811 and NEs

Common combinations of networking solutions

Networking of Eth-trunk Interface in Active/Standby Mode+Static Routing

6.1.3.1 Networking of Eth-trunk Interface in

Networking Solutions of the GE Interface

Figure 1 Networking of the GE interface and static routing

Networking Solution of the 10GE Interface

Figure 3 Networking of the 10GE interface

Parent Topic: Common Networking Solutions

6.1.3.2 Networking of Eth-trunk Interfaces in

Networking Solutions of the GE Interface

Networking Solution of the 10GE Interface

Figure 3 Networking of the 10GE interface

Parent Topic: Common Networking Solutions

6.1.3.3 Networking of Dual Active

Networking Solutions of the GE Interface

Figure 1 Networking of the GE interface and static routing

Figure 2 Reliable networking of the GE interface

Networking Solution of the 10GE Interface

Figure 3 Networking of the 10GE interface

Parent Topic: Common Networking Solutions

6.1.3.4 VPN Networking

 Reachability inside a VPN

Constructing a VPN by Creating VRF

The advantages of configuring a VPN by creating VRF are as follows:

Constructing a VPN Through Tunnels

Table 1 Typical application scenarios for the VPN networking

 Configure associated VRF for the VPN.

 The UGW9811 serves as the L2TP access

s of the UGW9811, multiple SGi interfaces

For details, see Implementation of IPv6 on the

Inband or Outband Networking with the AAA Server

Figure 2 Inband or outband networking with the AAA server

 Eth-trunk2: Specifies the output interface

Implementation of IPv6 on the UGW9811

There are four IPv6 tunneling technologies supported by the UGW9811.

IPv6 over IPv4 Manual or Automatic Tunnel

Figure 3 IPv6 over IPv4 tunnel

IPv6 over IPv4 GRE Tunnel

Figure 4 IPv6 over IPv4 GRE tunnel

Figure 5 6to4 tunnel

Parent Topic: Common Networking Solutions

6.2 Product Description

6.2 Product Description

Introduction to product description: