HUAWEI ENS V900 Product Description

HUAWEI ENS Enhanced Name Server
V900
Product Description

Issue 1.0

HUAWEI TECHNOLOGIES CO., LTD.

Issue 1.0
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd.
i

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

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

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

Product Description Contents

Issue 1.0 Huawei Proprietary and Confidential
ii

Contents
1 Overview ......................................................................................................................................... 1
1.1 Positioning ....................................................................................................................................................... 1
1.2 Benefits ............................................................................................................................................................ 2
1.2.1 Flexible Deployment of the BE and the FE ............................................................................................ 2
1.2.2 Distributed Structure ............................................................................................................................... 3
1.2.3 Advanced Hardware Platform ................................................................................................................. 4
1.2.4 In-Memory Data Management ................................................................................................................ 4
1.2.5 Multi-Level Data Backup Mechanism .................................................................................................... 5
1.2.6 Large Capacity and High Integration ...................................................................................................... 6
1.2.7 Seamless Geographic Redundancy ......................................................................................................... 6
2 Architecture .................................................................................................................................... 7
2.1 Hardware Architecture ..................................................................................................................................... 7
2.1.1 Appearance .............................................................................................................................................. 7
2.1.2 Physical Structure ................................................................................................................................. 10
2.2 Software Architecture ..................................................................................................................................... 12
2.2.1 Signaling Processing Subsystem ........................................................................................................... 13
2.2.2 Subscriber Data Management Subsystem ............................................................................................. 14
2.2.3 Data Service Subsystem ........................................................................................................................ 14
2.2.4 Data Storage Subsystem ........................................................................................................................ 14
2.2.5 O&M Subsystem ................................................................................................................................... 14
3 Operation and Maintenance ..................................................................................................... 15
3.1 O&M Subsystem Architecture ....................................................................................................................... 15
3.2 O&M Functions ............................................................................................................................................. 17
3.2.1 Configuration Management .................................................................................................................. 17
3.2.2 Fault Management ................................................................................................................................ 17
3.2.3 Performance Measurement ................................................................................................................... 17
3.2.4 Security Management ........................................................................................................................... 18
3.2.5 Remote Maintenance............................................................................................................................. 18
4 Interfaces and Protocols ............................................................................................................. 19
4.1 Physical Interfaces ......................................................................................................................................... 19
4.1.1 Maintenance Interfaces ......................................................................................................................... 19
4.1.2 Service Ports ......................................................................................................................................... 21
Product Description Contents

iii

4.2 Protocol Interfaces ......................................................................................................................................... 23
4.2.1 USCDB Protocol Interfaces .................................................................................................................. 23
4.2.2 ENS Interfaces ...................................................................................................................................... 24
5 Reliability ..................................................................................................................................... 26
5.1 Hardware Reliability ...................................................................................................................................... 26
5.2 Software Reliability ....................................................................................................................................... 27
6 Technical Specifications ............................................................................................................ 29
6.1 Performance Specifications ............................................................................................................................ 29
6.2 Reliability Specifications ............................................................................................................................... 29
6.3 Power Consumption Specifications ................................................................................................................ 30
6.4 EMC Specifications ....................................................................................................................................... 31
7 Environmental Requirements................................................................................................... 32
7.1 Storage Requirements .................................................................................................................................... 32
7.2 Transportation Requirements ......................................................................................................................... 34
7.3 Operational Requirements .............................................................................................................................. 37
8 Acronyms and Abbreviations ................................................................................................. 40
Product Description 1 Overview

1

1 Overview
1.1 Positioning
Huawei enhanced name server (ENS) provides the functions of the domain name system
(DNS) and the E.164 number mapping (ENUM). The DNS translates human-friendly
hostnames into IP addresses for locating computers and devices worldwide. The ENUM
translates telephone numbers into uniform resource identifiers (URIs) or IP addresses for use
in Internet communications.
The ENS supports query for the following resources records:
Address (A): returns a 32bit IPv4 address
IPv6 address (AAAA): returns a 128bit IPv6 address
Naming authority pointer (NAPTR): allows regular expression based rewriting of
domain names which can then be used as URIs and domain names
Name server (NS): delegates a DNS zone to use the given authoritative name servers
Service (SRV): specifies the location of the server for a specific protocol and domain
Logically, the ENS consists of the front end (FE) and the back end (BE).
FE
The FE processes signaling messages and service logics and obtains data from the BE.
BE
The BE adds, deletes, updates, and queries data at the request of the FE.
The separation of the FE from the BE brings the following benefits:
More flexible networking
The BE and FE can be deployed in different places based on the population distribution
and geographical conditions.
Enhanced system compatibility
The BE provides standard and open interfaces for third-party devices. Carriers can
deploy network devices of different vendors.
Figure 1-1 shows the position of the ENS in the entire network.

2

Figure 1-1 Position of the ENS

CSCF: call session control function AS: application server
HSS: home subscriber server SLF: subscription locator function
NPDB: number portability database -

Normally, there is no way to avoid that some user data will be used when functions and
services are provided. You are obligated to take considerable measures, in compliance with
the laws of the countries concerned and the user privacy policies of your company, to ensure
that the personal data of users is fully protected.
1.2 Benefits
1.2.1 Flexible Deployment of the BE and the FE
Logically, the ENS consists of a back end (BE) and a front end (FE), which separates data
storage from service processing. The functions of the BE and FE are as follows:
BE
The BE stores subscriber data. It adds, deletes, updates, or queries data based on requests
from the FE.
FE

3

The FE processes signaling messages.
Separating data storage from service processing has the following advantages:
More flexible networking
The BE and FE can be deployed in different places based on the population distribution
and geographical conditions.
Enhanced system compatibility
The BE provides standard and open interfaces for third-party devices. Carriers can
deploy network devices of different vendors.
1.2.2 Distributed Structure
A distributed structure allows multiple identical functional entities to work in load-balancing
mode. Figure 1-2 shows the distributed structure of the ENS.
Figure 1-2 Distributed structure of the ENS

DRU: data routing unit DSU: data service unit
SPU: service processing unit -

The distributed structure has the following advantages:
High reliability
If a functional entity is faulty, the load is automatically distributed to other functional
entities, thereby ensuring uninterrupted service processing.
Smooth expansion

4

System capacity can be expanded by adding functional entities. After the system detects
that newly added entities are running stably, the system distributes the load among the
entities that provide identical functions to achieve load balancing.
1.2.3 Advanced Hardware Platform
The ENS uses the OSTA 2.0 hardware platform. This platform is compatible with the
Advanced Telecom Computing Architecture (ATCA). The ATCA standards are composed of a
series of peripheral component interconnect (PCI) Industrial Computer Manufacturers Group
(PICMG3.X) specifications and are widely accepted as the standard for the next-generation
standard telecommunication hardware platforms.
The OSTA 2.0 platform uses the Intel Architecture (IA), which allows for the use of
high-performance and high-efficiency processors, and Carrier Grade Linux (CGL) technology.
It is a highly competitive carrier-class platform.
In addition to complying with the ATCA standards, the OSTA 2.0 platform has the following
advantages:
The equipment and monitoring system comply with carrier-class application designs.
The service plane, control plane, and management plane are physically separate. The
lower-layer hardware planes are not adversely affected by abnormalities on other planes.
If the hardware needs to be upgraded, the existing software can be used without any
modification. This greatly improves system reliability.
The components used in the OSTA 2.0 platform are ETSI/NEBS compliant and can be
selected for carrier-class equipment.
The system enhances the monitoring on system operations, hardware components, and
external interfaces. It uses a fault diagnosis mechanism and provides pre-alerts when a
component is in a border line state between normal operation and a fault.
The OSTA 2.0 platform meets the sound and heat dissipation requirements for
telecommunications equipment.
The OSTA 2.0 platform uses fault detection and fault isolation technologies. Detected
faults are isolated so as not to adversely affect other parts of the system.
The OSTA 2.0 platform features an optimized fault location design, which allows
accurate identification of faulty components.
1.2.4 In-Memory Data Management
All subscriber data is managed in the board memory. The front end (FE) reads subscriber data
from the board memory when it processes service requests. The FE does not read subscriber
data from the external storage device. The external storage device, such as a disk array, is only
used to permanently store subscriber data.
In-memory data management has the following advantages:
Allows service processing to be independent of the external data storage device. If the
external data storage device fails, service processing is not adversely affected.
Features higher throughput and a shorter latency. It greatly enhances system performance,
especially for large-capacity systems.

5

1.2.5 Multi-Level Data Backup Mechanism
The ENS uses a multi-level data backup mechanism. This mechanism enables the system to
store subscriber data on different storage devices, thereby ensuring data security. Figure 1-3
shows the multi-level data backup mechanism.
Figure 1-3 Multi-level data backup mechanism

The multi-level data backup mechanism involves the following:
Level-1 backup
Backing up data in a master node to the slave node in the same cluster. Subscriber data is
stored in the memory of different boards. Each cluster is distributed on two boards and
comprised with master and slave nodes. The master node provides services; the slave
node serves as the backup for the master node. The master node synchronizes data to the
slave node in real time.
Level-2 backup
Backing up in-memory database data to board disks. Subscriber data stored in the board
memory is backed up to two local hard disks on the board, which work in RAID 1 mode.
Level-3 backup
Backing up in-memory database data to the physical database. Subscriber data stored in
the board memory is backed up to the local hard disk on a physical database board or to
the disk array.
If subscriber data is backed up to the local hard disk, the local hard disk is configured
with RAID 1.
If subscriber data is backed up to the disk array, the disk array is configured with
RAID 10 and hot spare disks.

6

1.2.6 Large Capacity and High Integration
One ENS cabinet can store data for 20 million subscribers. By storing such a large amount of
data in a centralized manner, the ENS helps carriers to minimize the operating expense
(OPEX) by:
Reducing the equipment maintenance and manpower costs
Simplifying the network by reducing the number of network elements
Reducing power consumption and rental space required
1.2.7 Seamless Geographic Redundancy
The ENSs can be deployed in different places. Data synchronization between the ENSs in
different places is implemented using real-time data duplication and periodic data consistency
checks.
Seamless geographic redundancy has the following advantages:
Isolates faults immediately, thereby improving network security.
Reduces infrastructure construction costs by using mature IT and IP technologies.
Simplifies network structure and equipment maintenance, thereby reducing the total cost
of operation (TCO).
Product Description 2 Architecture

7

2 Architecture
2.1 Hardware Architecture
2.1.1 Appearance
Cabinet
The ENS uses the Huawei N68E-22 cabinet. Figure 2-1 shows an N68E-22 cabinet.

8

Figure 2-1 N68E-22 cabinet

Table 2-1 lists the technical specifications of the N68E-22 cabinet.
Table 2-1 Technical specifications of the N68E-22 cabinet
Item Specifications
Model N68E-22 server cabinet
Power supply -48 V DC or -60 V DC (dual 3-input with 63
A input current configured for each circuit by
default)
Dimensions (height x width x depth) 2200 mm x 600 mm x 800 mm (86.61 in. x
23.62 in. x 31.50 in.)
Available height in the cabinet 46 U (1 U = 44.45 mm = 1.75 in.)
Weight (empty) 100 kg (220.5 lb)
Weight (fully-loaded integrated
configuration cabinet)
342 kg (754.11 lb)

9

Item Specifications
Weight (fully-loaded extension cabinet) 365 kg (804.825 lb)
Load-bearing capacity of the floor in the
equipment room
600 kg/m
2
(0.85 bf/in
2
)
Required floor space 0.48 m
2
(5.17 ft
2
)
Heat dissipation 20820.024 BTU
Cabling modes supported Overhead cabling and underfloor cabling

Subrack
The ENS uses OSTA 2.0 subracks, which are ATCA-compatible. Figure 2-2 shows an OSTA
2.0 subrack.
Figure 2-2 OSTA 2.0 subrack

The OSTA 2.0 subrack has the following features:
The OSTA 2.0 subrack is 14 U (1 U = 44.45 mm = 1.75 in.) high and 19 in. (1 in. = 25.4
mm) wide. It can be installed in a standard 19-inch wide cabinet.
The OSTA 2.0 subrack provides 14 vertical slots, which allow 14 front boards and 14
back boards to be installed.
The OSTA 2.0 subrack is configured with a dual-star high-speed backplane, which
provides dual-star buses such as the Intelligent Platform Management Bus (IPMB),
service data bus, power bus, and clock bus. The boards and modules are interconnected
by using the buses provided by the backplane, thereby reducing the number of cables
used between boards and modules.

10

The OSTA 2.0 subrack can be configured with a maximum of four power modules,
which provide power to the boards by using the backplane. The power modules can work
in 2+2 or 2+1 backup mode.
The active and standby fan boxes are located under the board slots and can be
maintained separately.
The OSTA 2.0 subrack provides cable troughs at the rear of the subrack to facilitate
maintenance.
Board
Boards can be classified into the following types based on their position:
Front board
The front boards, located in the front of a subrack, can be classified into the following
types:
UPB: processes data and services by using the service applications running on the
board.
SWU: implements layer-2 network switching and optical switching.
SMU: manages the components in a subrack.
Back board
The back boards, installed back-to-back with the front boards, provide interfaces for the
front boards. The back boards can be classified into the following types:
USI: interface board of the UPB
SWI: interface board of the SWU
SDM: interface board of the SMM
Backplane
The backplane, located between the front boards and the back boards, transmits signals
between boards.
Figure 2-3 shows the boards in an OSTA 2.0 subrack.
Figure 2-3 Boards in an OSTA 2.0 subrack

2.1.2 Physical Structure
Cabinets can be classified into integrated configuration cabinets and extension cabinets based
on the components installed in the cabinets. Figure 2-4 shows an integrated configuration
cabinet. Figure 2-5 shows an extension cabinet.

11

An integrated configuration cabinet houses the following components:
Power distribution box (PDB)
OSTA 2.0 subrack
LAN switch
Disk array
Figure 2-4 Integrated configuration cabinet

An extension cabinet houses the following components:
PDB

12

OSTA 2.0 subrack
Figure 2-5 Extension cabinet

2.2 Software Architecture
The ENS consists of the following subsystems:
Signaling processing subsystem
Data service subsystem

13

Data storage subsystem
Subscriber data management subsystem
Operation and maintenance subsystem
Figure 2-6 shows the ENS software architecture.
Figure 2-6 ENS software architecture

DRU: data routing unit DSU: data service unit
OMU: operation and maintenance unit PGW: provisioning gateway
SPU: service processing unit BSG: broadband signaling gateway
CCU: call control unit -

2.2.1 Signaling Processing Subsystem
The signaling processing subsystem is responsible for establishing connections to other
network devices and processing signaling messages. It contains the following functional
modules:
SPU
The SPU processes the query requests sent by the peer network elements (NEs) and
sends response messages to the peer NEs.
BSG
The BSG processes IP messages at the SCTP layer and M3UA layer and forwards the
processed messages to the CCU.
CCU
The CCU processes SCCP, TCAP, and MAP messages and forwards the processed
messages to the SPU.

14

2.2.2 Subscriber Data Management Subsystem
The subscriber data management subsystem performs the following functions:
Provides unified service provisioning for different FEs.
Provides high-speed MML and SOAP interfaces.
Allows access from PGW Web LMTs.
Supports authentication and authority verification on the users of the provisioning
system and the PGW Web LMTs.
Implements subscriber data management.
2.2.3 Data Service Subsystem
The data service subsystem consists of the following components:
Data routing unit (DRU)
Subscriber data is distributed among multiple data service unit (DSU) clusters. Based on
the subscriber identity, the DRU identifies the DSU cluster in which the required
subscriber data is stored. The DRU selects a master DSU node to add, delete, and modify
the data and selects a DSU node to query the data based on the load balancing strategy.
DSU
The DSU consists of multiple DSU clusters.
The DSU adds, deletes, updates, and queries data, processes data requests, and returns
processing results.
2.2.4 Data Storage Subsystem
The data storage subsystem consists of a database and a disk array. It provides permanent
storage of subscriber data and implements the level-3 data backup and restoration function.
The data storage subsystem is only for permanent data storage and is independent of service
processing.
2.2.5 O&M Subsystem
The O&M subsystem implements operation and maintenance of the ENS. For details on the
O&M subsystem functions, see 3 Operation and Maintenance.
Product Description 3 Operation and Maintenance

15

3 Operation and Maintenance
3.1 O&M Subsystem Architecture
The operation and maintenance (O&M) subsystem is based on the client/server architecture. It
provides the GUI-based Huawei Operation & Maintenance System and WebUI-based
performance measurement system.
The O&M subsystem supports the following three operation modes:
Maintenance on the local maintenance terminal (LMT)
Centralized maintenance by accessing the iManager M2000 client
Remote maintenance by accessing the internal network through a dial-up server
The O&M subsystem consists of the OMU and LMTs, as shown in Figure 3-1.

16

Figure 3-1 O&M subsystem

The O&M subsystem works in client/server mode.
The OMU functions as a server.
It is connected to service boards and external networks through the Ethernet.
LMTs function as clients.
LMTs can be configured as various functional workstations, such as maintenance
consoles, data management consoles, alarm consoles, and performance measurement
consoles.
As the core of the O&M subsystem, the OMU provides a channel for communication between
the LMTs and the network elements (NEs). It forwards the O&M commands received from
the LMTs to the Unified Subscriber Center Database (USCDB) and the front ends (FEs), and
returns the responses to the LMTs.
As the client defined by TCP/IP, the LMT communicates with the OMU by using Telnet, FTP,
MML commands, GUI, or WebUI. The LMT allows users to perform data configuration,
routine operations, and maintenance.
The LMT allows users to perform operation and maintenance activities by using remote
maintenance interfaces.
Huawei iManager M2000 (M2000) is an integrated management system for the mobile
network. It implements centralized management of the NEs on the network. The M2000
consists of a server and multiple clients. It communicates with the NEs over TCP/IP.

17

3.2 O&M Functions
3.2.1 Configuration Management
The ENS provides a MML-based configuration system. The MML is defined by ITU
Z.301-ITU Z.341 series recommendations to standardize the interfaces over which the ENS
manages network devices from a console. The ENS provides a set of MML commands for
users to monitor and manage the ENS.
The ENS uses a relational database to manage the configured data. It supports operations such
as adding, deleting, modifying, storing, backing up, and restoring data. It allows users to
effectively manage and maintain various types of data, such as hardware data, signaling data,
and module data. The ENS provides the following configuration management functions:
Online and offline data configuration
Local and remote data configuration
Online upgrade
Data verification
3.2.2 Fault Management
Alarm Management
The alarm management system provides the following functions:
Detects errors, instructs the alarm devices (such as the alarm box and alarm console) to
generate audible and visual alarms based on the alarm type and alarm severity, and sends
the alarms to the operations support system (OSS) through the OSS interface.
Stores alarms, queries historical alarms, sets alarm processing modes, and provides the
CPU threshold in the alarms when the CPU usage is extremely high.
Displays alarm handling suggestions on the alarm console to help users rapidly identify
and rectify faults.
Tracing Management
The ENS provides network-wide tracing and subscriber-based tracing.
Network-wide tracing
Network-wide tracing helps users quickly identify faults in an increasingly complex
communications network. Compliant with the GSM 12.08 protocol, the ENS can use
network-wide tracing to trace a fault in the circuit switched (CS) domain to a specific
network element.
Subscriber-based tracing
The ENS provides subscriber-based tracing to help users identify faults:
Traces messages over standard interfaces and saves the traced messages.
Interprets the traced messages.
3.2.3 Performance Measurement
The performance measurement system of the ENS provides the following functions:
Allows users to create, modify, delete, and query performance measurement tasks.

18

Displays graphically performance measurement results.
Re-analyzes the measurement results and displays the results in graphs.
3.2.4 Security Management
Multiple users can use the operation and maintenance system of the ENS at the same time. To
ensure secure concurrent use of the operation and maintenance system, the ENS provides
authority management and log management functions.
Authority management
The operators and maintenance consoles of the ENS are assigned authorities of different
levels. On the operation and maintenance system of the ENS, two factors determine the
execution of an MML command: the authority of an operator and the authority of a
maintenance console. The MML command can be executed only when both the operator
and the maintenance console are authorized to run the MML command.
Log management
The ENS supports the query of the MML commands that have been executed. With the
help of the operation logs, users can determine whether any operations that may
adversely affect the system have been performed.
3.2.5 Remote Maintenance
The ENS provides the following remote maintenance functions:
Effectively protects the system against viruses, hackers, and malicious attacks during
remote maintenance.
Allows users to query the versions and status of subsystems and modules, monitors and
handles system faults, queries alarm information, commissions functional interfaces, and
queries the system running status in real time.
Supports remote maintenance and patch installation.
Product Description 4 Interfaces and Protocols

19

4 Interfaces and Protocols
4.1 Physical Interfaces
Physical interfaces can be classified into maintenance interfaces and service interfaces.
4.1.1 Maintenance Interfaces
Table 4-1 lists the maintenance interfaces supported by the ENS.
Table 4-1 Maintenance interfaces supported by the ENS
Board Interfac
e
Function Description Num
ber
of
Interf
aces
UPB Compon
ent
object
model
(COM)
serial
port
Used for
local
debugging
.
The COM serial port on the UPB incorporates
the functions of the baseboard management
controller (BMC) serial port and the system
serial port. The type of serial port to be used
can be specified using the SMM board. The
baud rate of the BMC serial port is 115200
bit/s. The baud rate of the system serial port
can be adjusted based on the actual situation.
This port complies with RS232.
1
USB
port
Used to
connect to
USB
devices,
such as a
mouse or a
keyboard.
This port is a standard USB 1.1 port. 2
SWU BMC
COM
serial
port
Used to
load or
upgrade
the BMC
software.
This port complies with RS232 and provides a
baud rate of 115200 bit/s. It can be connected
to an RJ45 connector. This port does not have
an indicator.
1

20

Board Interfac
e
ber
of
Interf
aces
SYS
COM
serial
port
Used for
local
manageme
nt,
maintenan
ce, and
debugging
.
an indicator.
1
Network
port of
LAN 1
Used to
load the
Base plane
driver and
for local
debugging
.
This port supports 10/100 Mbit/s Base-T
auto-negotiation. It can be connected to an
FTP5 cable by using an RJ45 connector. This
port has two indicators.
1
Network
port of
LAN 2
Used for
local
maintenan
ce.
FTP5 cable by using an RJ45 connector. This
port has two indicators. This port is available
only after the Base plane starts successfully.
1
SMM COM
serial
port
Used for
local
debugging
,
maintenan
ce,
configurati
on, and
local or
remote
connection
manageme
nt.
an indicator.
1
ETH0
port
Used for
debugging
,
maintenan
ce, and
configurati
on.
FTP5 cable by using an RJ45 connector.
1
SDM COM
serial
port
Used for
local
debugging
,
maintenan
an indicator.
1

21

Board Interfac
e
ber
of
Interf
aces
ce,
configurati
on, and
local or
remote
connection
manageme
nt.
Ethernet
port
Used to
implement
user
operation
and
manageme
nt, such as
running
MML
commands
and
performin
g
operations
on the
provisioni
ng
gateway
(PGW)
Web local
maintenan
ce
terminal
(LMT).
FTP5 cable by using an RJ45 connector.
1

4.1.2 Service Ports
Table 4-2 describes the service ports provided by the ENS.
Table 4-2 Service ports provided by the ENS
Board Port Function Description Num
ber
of
Ports
USI2 FC port Connects
to the FC
Supports FC-AL, FC-SW, or FC-P2P 1 Gbit/s
or 2 Gbit/s auto-negotiation and provides a
2

22

ber
of
Ports
disk array dual-channel Fiber Channel Protocol (FCP)
controller to implement FC redundancy
GE port Connects
to the
Ethernet
RJ-45 port supporting 10 Mbit/s, 100 Mbit/s,
or 1000 Mbit/s Base-T auto-negotiation
4
VGA
port
Connects
to the
monitor
Supports 1024 x 768 or higher super video
graphics array (SVGA) resolution
1
USB
port
Connects
to an
external
device
Standard USB port 1
USIA1 GE port Connects
to the
Ethernet
RJ-45 port supporting 10/100/1000 Mbit/s
Base-T auto-negotiation
4
VGA
port
Connects
to the
monitor
Supports 1024 x 768 or higher SVGA
resolution
1
USB
port
Connects
to an
external
device
Standard USB port 1
USIA7 GE port Connects
to the
Ethernet
RJ-45 port supporting 10/100/1000 Mbit/s
Base-T auto-negotiation
6
VGA
port
Connects
to the
monitor
Supports 1024 x 768 or higher SVGA
resolution
1
USB
port
Connects
to an
external
device
Standard USB port 1
SWI Base
port
Connects
the boards
in
subracks
to provide
the Base
plane
10/100/1000 Mbit/s Base-T auto-negotiation
Ethernet port with two indicators
8
Fabric
GE port
Connects
the boards
in
10/100/1000 Mbit/s Base-T auto-negotiation
Ethernet port with two indicators
8

23

ber
of
Ports
subracks
to provide
the Fabric
plane
Fabric
FC port
Connects
the
subrack
where the
SWI is
located to
the FC
disk array
4 Gbit/s 1000Base-SX port with two indicators 4

4.2 Protocol Interfaces
4.2.1 USCDB Protocol Interfaces
Table 4-3 lists the protocol interfaces supported by the USCDB.
Table 4-3 Protocol interfaces supported by the USCDB
Type Interface Description
Data access
interface
LDAP Used by FEs to access the USCDB
DCI A Huawei proprietary interface used by FEs to access
the USCDB
Service
provisioning
interface
SOAP Used for communication between the USCDB and the
provisioning system
MML A Huawei proprietary interface used for
communication between the USCDB and the
provisioning system
Subscription
and notification
interface
SOAP Used for data subscription and notification between
the USCDB and the FE
MCI A Huawei proprietary interface used for data
subscription and notification between the USCDB and
the FE
OM interface SNMP Used by the OMU to report alarms to the OSS


24

4.2.2 ENS Interfaces
The ENS provides open and standard interfaces for communicating with various network
elements (NEs) using various protocols. Figure 4-1 shows the interfaces between the ENS and
other NEs.
Figure 4-1 Interfaces between the ENS and other NEs

AS: application server CSCF: call session control function
MRFC: multimedia resource function controller ENS: enhanced name server
DNS: domain name system ENUM: E.164 number mapping
NPDB: number portability database -

Table 4-4 describes the interfaces between the ENS and other NEs on a public land mobile
network (PLMN).
Table 4-4 Interfaces between the ENS and other NEs on a PLMN
Interface Interworking
NE
Signaling
Protocol
Bearer Type Physical
Interface
DNS/ENUM P/S/I-CSCF,
AS, MRFC
DNS IP GE

25

Interface Interworking
NE
Signaling
Protocol
Bearer Type Physical
Interface
MAP NPDB MAP IP GE
Product Description 5 Reliability

26

5 Reliability
5.1 Hardware Reliability
Redundancy and Backup Design
The ENS adopts a redundancy and backup design to ensure system reliability. When a
component is faulty, the redundancy component automatically takes over services from the
faulty component, thereby ensuring uninterrupted service processing.
Reliable Power Supply
The ENS uses the following technologies to ensure high reliability of the power supply
system:
The power modules use a distributed structure. When a power module is faulty, the load
is automatically distributed to other power modules, thereby ensuring uninterrupted
power supply.
The input voltage is monitored, and an alarm is generated if the input voltage is outside
the normal range.
The power supply system is protected against sharp voltage fluctuation and lightning.
The boards are protected against over-voltage, over-current, and reverse-polarity
connection.
Distributed Structure of Boards
The boards of the ENS work in active/standby mode or load-sharing mode. When a board is
faulty, the other board automatically takes over services from the faulty board, thereby
ensuring uninterrupted service processing.
IP-based Dual-Plane Communication
The ENS is configured with two SWUs. Each SWU is connected to service processing boards
in star mode. With the help of the dual-star structure, service processing will not be adversely
affected by single-point failures. The ENS uses two planes, one for service data exchange and
the other for signaling exchange. The two planes are independent of each other, improving the
system reliability.

27

5.2 Software Reliability
Distributed Structure of Software Modules
The software modules of the ENS use a distributed structure. Therefore, a single-point failure
does not adversely affect service processing. This improves the system reliability.
Flow Control
The ENS uses the flow control mechanism. When a congestion occurs, the ENS discards
low-priority messages, ensuring service processing for most subscribers.
The flow control mechanism involves the following:
Monitors and analyzes the processor load and resource utilization in real time to
implement adaptive flow control.
Enables high-speed processing of the commands sent from the provisioning system.
When the traffic exceeds the maximum processing capability of the system, flow control
is started to ensure system security.
Provides configurable flow control parameters to implement forced flow control.
Automatic Load Balancing
The ENS uses software technologies to implement automatic load balancing among the same
type of boards. This improves system stability and reliability.
Automatic Fault Detection and Self-Healing
The ENS takes the following real-time fault monitoring and self-healing measures:
Automatic detection of hardware and software faults
Automatic running of troubleshooting programs to rectify faults in key hardware or
software components
Automatic switchover of services to the standby component if a fault cannot be rectified
Rollback upon Upgrade Failure
The ENS provides the rollback function, which allows the subscriber data and system version
to be restored to the pre-upgrade state when an upgrade fails. This function minimizes the
adverse impact caused by upgrade failures.
In-Memory Data Management
The ENS stores all subscriber data in the memory. The hard disks provide only permanent
storage of the subscriber data. Therefore, service processing is independent of the external
storage device. The boards can process services normally even if the external storage device is
faulty.
Distributed Storage of Subscriber Data
The ENS distributes subscriber data in data service unit (DSU) clusters working in
load-sharing mode. All the DSU nodes in a DSU cluster store the same subscriber data and

28

work in load-sharing mode. If a DSU board is faulty, the subscriber data will not be lost and
the system can continue providing services.
Backup and Restoration of Subscriber Data
The ENS stores subscriber data in different physical devices, thereby ensuring the security of
subscriber data. The multi-level data backup involves the following:
The subscriber data is stored in the memory of different boards, which form clusters.
Each cluster has master and slave nodes. The master node synchronizes data to the slave
node on a real-time basis.
The subscriber data stored in the board memory is backed up to the local hard disks of
the board.
The subscriber data stored in the board memory is backed up to the disk array.
Accordingly, there are three ways to restore data:
Restoring data from the master node in the same cluster
Restoring data from the local hard disk
Restoring data from the disk array
Data Consistency Check
The ENS checks data consistency between:
Master and slave nodes of a ENS
In-memory database and physical database of a ENS
Active and redundancy ENSs (only with the geographic redundancy solution)
Product Description 6 Technical Specifications

29

6 Technical Specifications
6.1 Performance Specifications
Table 6-1 lists the performance specifications of the ENS.
Table 6-1 Performance specifications of the ENS
Item Specifications
Maximum number of subscribers supported 20,000,000
Bearer networking modes supported IP
Maximum processing capability for query
requests
At least 5000 pcs/second (the number is
subject to the actual situation and can be
enlarged)
Time taken to send a response < 10 ms
Time taken to synchronize data between the
master and slave nodes
30 seconds
Annual down time 180 second/year
The ENSs work in active and standby mode.
Maximum command processing speed of
the provisioning system (in full
configuration)
10,000 commands/second

6.2 Reliability Specifications
Table 6-2 lists the reliability specifications of the ENS.

The reliability specifications apply only if the ENS uses the redundancy solution.

30

Table 6-2 Reliability specifications of the ENS
Item Specifications
System repair rate 0.3%
Availability 99.9999%
Fault detection rate > 95%
Mean time to repair (MTTR) < 1 hour
Mean time between failures (MTBF) 1151027 hours
Service interruption time of each upgrade or
expansion
< 10 seconds
Average service interruption time in a year < 30 seconds
Duration from system power-on to service
ready
8 minutes
Success rate of switchovers to redundancy
components
> 95%
Board switchover duration 10 seconds

6.3 Power Consumption Specifications
Table 6-3 lists the power consumption specifications of the ENS.
Table 6-3 Power consumption specifications of the ENS
Component Maximum Power
Consumption
Typical Power Consumption
Integrated configuration
cabinet (in full
configuration)
4488 W 3598 W
Extension cabinet (in full
configuration)
6102 W 4848 W
OSTA 2.0 subrack
(including fan boxes and
SWU, SWI, SMM, and
SDM boards)
382 W 268 W
UPBA0 125 W 110 W
UPBA2 135 W 110 W
UPBA6 122 W 110 W
USIA1 8 W 7 W

31

Component Maximum Power
Consumption
Typical Power Consumption
USIA7 12 W 10 W
USI3 25 W 22 W
USI2 19 W 16 W
LAN switch 60 W 48 W
Disk array 300 W 270 W

6.4 EMC Specifications
The electromagnetic compatibility (EMC) of the ENS complies with the following standards:
EN 55022 class A
CISPR 22 class A
ETSI EN 300 386
VCCI V-3 class A
ICES-003
AS/NZS CISPR 22
CNS 13438
FCC PART 15 class A
GB9254 class A
ETSI ES 201468 level 2
Product Description 7 Environmental Requirements

32

7 Environmental Requirements
The environmental requirements for the ENS comply with the following standards:
GB 4798 application environment conditions of electrical products
ETS 300019 Equipment Engineering (EE); Environmental conditions and environmental
tests for telecommunications equipment
IEC 60721 Classification of environmental conditions
7.1 Storage Requirements
Climatic Requirements
Table 7-1 lists climatic requirements for equipment storage.
Table 7-1 Climatic requirements for equipment storage
Item Range
Temperature -40C to +70C (-40F to 158F)
Temperature change rate 1C/min (33.8F/min)
Relative humidity 10% to 100%
Altitude 5000 m (16,404 ft)
Atmospheric pressure 70 kPa to 106 kPa
Solar radiation 1120 W/m
2

Heat radiation 600 W/m
2

Wind speed 20 m/s (65.62 ft/s)

Waterproofing Requirements
Generally, the equipment must be stored inside the equipment room. If the equipment is
stored inside the equipment room, the following requirements must be met:

33

There is no water on the ground or any other place in the equipment room as
exposure to water may dampen the package.
The equipment is placed away from fire extinguishers and heating pipes.
If the equipment is stored outside the equipment room, the following requirements must
be met:
The package is kept intact.
Waterproofing measures are taken to protect the package against rainfall.
No water is found on the ground where the package is placed to prevent water from
seeping into the package.
The package is not exposed to sunlight.
Biological Requirements
The equipment room must be protected against epiphytes, mildew, and rodents.
Air Cleanliness Requirements
The equipment must be stored in an environment that is free from explosive, conductive,
magnetic conductive, and corrosive dust.
The density of mechanically active substances must meet the requirements listed in Table 7-2
Table 7-2 Density requirements for mechanically active substances in equipment storage
Mechanically Active Substance Density
Suspended dust 5.00 mg/m
3

Deposited dust 20.0 mg/m
2
h
Sand 300 mg/m
3

NOTE
Suspended dust: diameter 75 m
Deposited dust: 75 m diameter 150 m
Sand: 150 m diameter 1000 m

The density of chemically active substances must meet the requirements listed in Table 7-3.
Table 7-3 Density requirements for chemically active substances in equipment storage
Chemically Active Substance Density
SO
2
0.3 mg/m
3
to 1.0 mg/m
3

H
2
S 0.1 mg/m
3
to 0.5 mg/m
3

NO
2
0.5 mg/m
3
to 1.0 mg/m
3

NH
3
1.0 mg/m
3
to 3.0 mg/m
3

Cl
2
0.1 mg/m
3
to 0.3 mg/m
3


34

HCl 0.1 mg/m
3
to 0.5 mg/m
3

HF 0.01 mg/m
3
to 0.03 mg/m
3

O
3
0.05 mg/m
3
to 0.1 mg/m
3

Mechanical Stress Requirements
Table 7-4 lists the mechanical stress requirements for equipment storage.
Table 7-4 Mechanical stress requirements for equipment storage
Item Sub Item Vibration
Frequency for the
Fixed Shift
Vibration
Frequency for the
Fixed
Acceleration
Sinusoidal
oscillation
Shift 7.0 mm (0.28 in.) No requirements
Acceleration No requirements 20.0 m/s
2
(65.62
ft/s
2
)
Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz
Unsteady impulse Impulse response
spectrum II
250 m/s
2
(820.2 ft/s
2
)
Static payload 5 kPa
NOTE
Impulse response spectrum
Refers to the maximum response curve of the accelerated speed generated by the equipment under the
specified impulse motivation. Impulse response spectrum II means that the duration of half-sine impulse
response spectrum is 6 ms.
Static payload
Refers to the downward pressure that the packaged equipment can bear from above when piled in the
specified way.

7.2 Transportation Requirements
Table 7-5 lists climatic requirements for equipment transportation.

35

Table 7-5 Climatic requirements for equipment transportation
Item Range
Temperature -40C to +70C (-40F to 158F)
Relative humidity 10% to 100%
2

2


Waterproofing Requirements
During transportation, the following requirements must be met:
The package is kept intact.
Waterproofing measures are taken in the transportation vehicles to prevent water from
seeping into the package.
There is no water inside the transportation vehicles.
The transportation vehicles must be protected against epiphytes, mildew, and rodents.
The transportation vehicles must be free from explosive, conductive, magnetic conductive,
and corrosive dust.
The density of mechanically active substances must meet the requirements listed in Table 7-6.
Table 7-6 Density requirements for mechanically active substances in equipment transportation
Suspended dust No requirements
2
h
Sand 100 mg/m
3


36

NOTE

Table 7-7 Density requirements for chemically active substances in equipment transportation
SO
2
0.3 mg/m
3
to 1.0 mg/m
3

H
2
S 0.1 mg/m
3
to 0.5 mg/m
3

NO
2
0.5 mg/m
3
to 1.0 mg/m
3

NH
3
1.0 mg/m
3
to 3.0 mg/m
3

Cl
2
0.1 mg/m
3
to 0.3 mg/m
3

HCl 0.1 mg/m
3
to 0.5 mg/m
3

HF 0.01 mg/m
3
to 0.03 mg/m
3

O
3
0.05 mg/m
3
to 0.1 mg/m
3

Table 7-8 lists the mechanical stress requirements for equipment transportation.
Table 7-8 Mechanical stress requirements for equipment transportation
Frequency for
the Fixed
Shift
Vibration
Frequency for
the Fixed
Acceleration
Vibration
Frequency for
the Fixed
Acceleration
Sinusoidal
oscillation
Shift 7.5 mm (0.30
in.)
No
requirements
No
requirements
Acceleration No
requirements
20.0 m/s
2

(65.62 ft/s
2
)
40.0 m/s
2

(131.23 ft/s
2
)
Frequency
range
2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500
Hz
Random
oscillation
Acceleration
spectrum
density
10 m
2
/s
3
3 m
2
/s
3
1 m
2
/s
3


37

Frequency for
the Fixed
Shift
Vibration
Frequency for
the Fixed
Acceleration
Vibration
Frequency for
the Fixed
Acceleration
Frequency
range
2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500
Hz
Unsteady
impulse
Impulse
response
spectrum II
300 m/s
2
(984.24 ft/s
2
)
NOTE
Static payload
specified way.

7.3 Operational Requirements
Table 7-9 lists climatic requirements for short- or long-term use of the equipment.
Table 7-9 Climatic requirements for short- or long-term use of the equipment
Item Range
Temperature Long term: +5C to +40C (41F to 104F)
Short term: -5C to +50C (23F to 122F)
Relative humidity Long term: 5% to 85%
Short term: 5% to 95%
2

2



38

The equipment room must be protected against epiphytes, mildew, and rodents.
The equipment room must be free from explosive, conductive, magnetic conductive, and
corrosive dust.
The density of mechanically active substances must meet the requirements listed in Table
7-10.
Table 7-10 Density requirements for mechanically active substances during equipment operation
Suspended dust 0.24 mg/m
3

2
h
Sand 30 mg/m
3

NOTE

Table 7-11 Density requirements for chemically active substances during equipment operation
SO
2
0.3 mg/m
3
to 1.0 mg/m
3

H
2
S 0.1 mg/m
3
to 0.5 mg/m
3

NO
2
0.5 mg/m
3
to 1.0 mg/m
3

NH
3
1.0 mg/m
3
to 3.0 mg/m
3

Cl
2
0.1 mg/m
3
to 0.3 mg/m
3

HCl 0.1 mg/m
3
to 0.5 mg/m
3

HF 0.01 mg/m
3
to 0.03 mg/m
3

O
3
0.05 mg/m
3
to 0.1 mg/m
3

Table 7-12 lists the mechanical stress requirements for equipment operation.

39

Table 7-12 Mechanical stress requirements for equipment operation
Frequency for the
Fixed Shift
Vibration
Frequency for the
Fixed
Acceleration
Sinusoidal
oscillation
Shift 3.5 mm (0.14 in.) No requirements
Acceleration No requirements 10.0 m/s
2
(32.81
ft/s
2
)
Frequency range 5 Hz to 9 Hz 9 Hz to 200 Hz
Unsteady impulse Impulse response
spectrum II
100 m/s
2
(328.08 ft/s
2
)
NOTE
Static payload
specified way.

Anti-Shock Requirements
The ENS complies with the ETS 300 019-2-4-AMD standards and YDN5083 defined by the
Ministry of Information Industry (MII) in China.
Sound-Proof Requirements
The noise level must be lower than 7.2 bel. The reference standard is EST 300 753, and the
test standard is ISO7779.
Product Description 8 Acronyms and Abbreviations

40

8 Acronyms and Abbreviations
3
3GPP 3rd Generation Partnership Project

A
AS Application Server
ATCA Advanced Telecom Computing Architecture
ATS Advance Telephony Server

B
BE Back End
BMC Baseboard Management Controller

C
CGL Carrier Grade Linux
CPU Central Processing Unit
CS Circuit Switched Domain
CSCF Call Session Control Function

41

D
DCI DS Call Interface
DNS Domain Name Server
DSU Data Service Unit
DRU Data Routing Unit

E
EMC Electromagnetic Compatibility
ENS Enhanced Name Server
ENUM Telephone Number Mapping
ETS European Telecommunication Standards
ETSI European Telecommunications Standards Institute

F
FC Fiber Channel
FCC Federal Communications Commission
FCP Fiber Channel Protocol
FE Front End
FTP File Transfer Protocol

G
GE Gigabit Ethernet

42

GGSN Gateway GPRS Support Node
GMLC Gateway Mobile Location Center
GPRS General Packet Radio Service
GSM Global System for Mobile communications
GUI Graphic User Interface

H
HLR Home Location Register
HSS Home Subscriber Server

I
IA Intel Architecture
IEC International Electrotechnical Commission
IETF Internet Engineering Task Force;
IMS IP multimedia subsystem
IMSI International Mobile Subscriber Identity
IP Internet Protocol
IPMB Intelligent Platform Management Bus
IT Information Technology
ITU International Telecommunications Union
ITU-T International Telecommunication Union - Telecommunication
Standardization Sector

L

43

LAN Local Area Network
LDAP Lightweight Directory Access Protocol
LMT Local Maintenance Terminal

M
MCI Message Call Interface
MML Man-Machine Language
MRFC Multimedia Resource Function Controller
MRTIE Maximum Relative Time Interval Error
MSC Mobile Switching Center
MSISDN Mobile Station International ISDN Number
MTBF Mean Time Between Failure
MTTR Mean Time To Repair

N
NAPTR Naming Authority Pointer
NE Network Element
NEBS Network Equipment Building System
NTP Network Time Protocol

O
OM Operation and Maintenance
OMU Operation and Maintenance Unit

44

OPEX OPeration EXpenditure
OSTA Open Standards Telecom Architecture

P
PCI Peripheral Component Interconnect

Q
QoS Quality of Service

R
RAID Redundant Array of Independent Disks
RADIUS Remote Authentication Dial in User Service
RFC Remote Feature Control
PGW Provisioning Gateway

S
SDM Subrack Data Module
SMM Shelf Management Module
SNMP Simple Network Management Protocol
SOAP Simple Object Access Protocol
SPU Service Processing Unit
SVGA Super Video Graphics Array
SWI Switch Interface Unit

45

SWP Sliding Window Protocol
SWU Switching Unit

T
TCP Transmission Control Protocol

U
UDP User Datagram Protocol
UI Unit Interval
UMTS Universal Mobile Telecommunications System
UPB Universal Process Blade
USB Universal Serial Bus
USCDB Unified Subscriber Center DataBase
USI Universal Service Interface

V
VGA Variable Gain Amplifier
VLR Visitor Location Register

W
WiFi Wireless Fidelity
WiMAX Worldwide Interoperability for Microwave Access
WLAN Wireless Local Area Network

46

X
XML Extensible Markup Language

47

HUAWEI ENS V900 Product Description

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

HUAWEI ENS V900 Product Description

Încărcat de

Drepturi de autor:

Formate disponibile

HUAWEI ENS Enhanced Name Server

S-ar putea să vă placă și