Huawei hss9860 v900 r008c20 production description

HUAWEI HSS9860 Home Subscriber Server V900R008C20

Product Description

Issue V1.1

Date 2013-12-19

HUAWEI TECHNOLOGIES CO., LTD.

Issue V1.1 (2013-12-19) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd. i

Copyright © Huawei Technologies Co., Ltd. 2013. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

HUAWEI HSS9860 Home Subscriber Server

Product Description Contents


Copyright © Huawei Technologies Co., Ltd.

ii

Contents

1 Overview ......................................................................................................................................... 1

1.1 Product Positioning ....................................................................................................................................................... 1

1.2 Benefits ......................................................................................................................................................................... 4

1.2.1 Flexible Deployment of the BE and the FE ............................................................................................................... 4

1.2.2 Distributed Structure .................................................................................................................................................. 5

1.2.3 Advanced Hardware Platform .................................................................................................................................... 6

1.2.4 In-Memory Data Management ................................................................................................................................... 6

1.2.5 Multi-Level Data Backup Mechanism ....................................................................................................................... 6

1.2.6 Virtual HSS Function ................................................................................................................................................. 7

1.2.7 Large Capacity and High Integration ......................................................................................................................... 8

1.2.8 Seamless Geographic Redundancy ............................................................................................................................ 8

1.2.9 Cloud Deployment ..................................................................................................................................................... 9

1.2.10 VoLTE Solution...................................................................................................................................................... 10

1.2.11 Auto Provision of LTE Service .............................................................................................................................. 13

1.2.12 Applicable to the Internet of Things ...................................................................................................................... 16

1.2.13 Standard and Open Data Access Interfaces ............................................................................................................ 17

1.2.14 Comprehensive Data Statistics and Analysis ......................................................................................................... 17

2 Architecture .................................................................................................................................. 18

2.1 Hardware Architecture ................................................................................................................................................ 18

2.1.1 Appearance .............................................................................................................................................................. 18

2.1.2 Physical Structure .................................................................................................................................................... 21

2.2 Software Structure ...................................................................................................................................................... 23

2.2.1 Signaling Processing Subsystem.............................................................................................................................. 24

2.2.2 Subscriber Data Management Subsystem ................................................................................................................ 25

2.2.3 Data Service Subsystem........................................................................................................................................... 25

2.2.4 Data Storage Subsystem .......................................................................................................................................... 25

2.2.5 O&M Subsystem ..................................................................................................................................................... 25

3 Operation and Maintenance ..................................................................................................... 26

3.1 O&M Subsystem Architecture .................................................................................................................................... 26

3.2 O&M Functions .......................................................................................................................................................... 28

3.2.1 Configuration Management ..................................................................................................................................... 28

3.2.2 Fault Management ................................................................................................................................................... 28


Product Description Contents



iii

3.2.3 Performance Measurement ...................................................................................................................................... 29

3.2.4 Security Management .............................................................................................................................................. 29

3.2.5 Remote Maintenance ............................................................................................................................................... 29

4 Interfaces and Protocols ............................................................................................................. 30

4.1 Physical Interfaces ...................................................................................................................................................... 30

4.1.1 Maintenance Interfaces ............................................................................................................................................ 30

4.1.2 Service Interfaces ..................................................................................................................................................... 32

4.2 Protocol Interfaces ...................................................................................................................................................... 36

4.2.1 USCDB Protocol Interfaces ..................................................................................................................................... 36

4.2.2 HSS9860 Interfaces ................................................................................................................................................. 37

5 Reliability ..................................................................................................................................... 45

5.1 Hardware Reliability ................................................................................................................................................... 45

5.2 Software Reliability .................................................................................................................................................... 46

6 Technical Specifications ............................................................................................................ 48

6.1 Performance Specifications ........................................................................................................................................ 48

6.2 Reliability Specifications ............................................................................................................................................ 49

6.3 Power Consumption Specifications ............................................................................................................................ 49

6.4 Clock Specifications ................................................................................................................................................... 50

6.5 EMC Specifications .................................................................................................................................................... 52

7 Environmental Requirements................................................................................................... 53

7.1 Storage Requirements ................................................................................................................................................. 53

7.2 Transportation Requirements ...................................................................................................................................... 55

7.3 Operational Requirements .......................................................................................................................................... 58


Product Description ‎1 Overview



1

1 Overview

1.1 Product Positioning

The HSS9860 stores and manages identities, authentication data, subscription information,

and location information about subscribers. In addition, the HSS9860 verifies mobile

terminals when mobile terminals attempt to connect to networks.

The HSS9860 implements the following functions:

Home location register (HLR) in Global System for Mobile Communications (GSM) and

Universal Mobile Telecommunications System (UMTS) networks

Equipment identity register (EIR) in GSM, UMTS, and EPS networks.

Home subscriber server (HSS) in evolved packet system (EPS) networks

HSS, subscription locator function (SLF), E.164 number to URI mapping (ENUM), or

domain name server(DNS) in IP multimedia subsystems (IMS).

GSM, UMTS, EPS, and IMS networks are 3GPP access networks while CDMA, WLAN,

WiMax, and ADSL are non-3GPP access networks.

‎Figure 1-1 shows the HSS9860's networking in GSM, UMTS, and EPS networks.





2

Figure 1-1 HSS9860's networking in GSM, UMTS, and EPS networks

GERAN: GSM/EDGE

radio access network

UTRAN: universal terrestrial


E-UTRAN: evolved universal

terrestrial radio access

network

MSC: mobile switching

center

SGSN: serving GPRS support

node

GGSN: gateway GPRS

support node

SCP: service control

point

HSS: home subscriber server GMLC: gateway mobile

location center

MME: mobility

management entity S-GW: serving gateway P-GW: PDN gateway

ePDG: evolved packet

data gateway

AAA: authentication,

authorization, and accounting

CDMA: Code Division

Multiple Access

WLAN: wireless local

area network

WiMAX: Worldwide

Interoperability for Microwave

Access

ADSL: Asymmetric Digital

Subscriber Line

PSTN: public switched

telephone network

CS: circuit switched PS: packet switched

EPC: evolved packet - -





3

core

‎Figure 1-2 shows the HSS9860's networking in IMS networks.

Figure 1-2 HSS9860's networking in IMS networks

MRFP: multimedia

resource function

processor

DNS: domain name system ENUM: E.164 number to URI

mapping

AS: application server I-CSCF: interrogating-call

session control function

S-CSCF: serving-call session

control function

BGCF: breakout

gateway control

function

MRFC: multimedia resource

function controller

MGCF: media gateway control

function

PCRF: policy and

charging rules function

SBC: session border

controller

P-CSCF: proxy-call session

control function

ATCF: access transfer

control function

ATGW: access transfer

gateway

IM-MGW: IP multimedia

media gateway

CDMA: Code Division

Multiple Access

EVDO: Evolution-Data

Optimized

WiMAX: Worldwide

Interoperability for Microwave

Access

Wi-Fi: Wireless Fidelity LAN: local area network FTTx: fiber to the x

xDSL: x digital TDM: time division PSTN: public switched





4

subscriber line multiplexing telephone network

PLMN: public land

mobile network

- -

The HSS9860 can be deployed to serve as any of the following:

HLR in GSM and UMTS networks

SAE-HSS in EPS networks

EIR in GSM, UMTS, and EPS networks

IMS-HSS in IMS networks

SLF in IMS networks

ENS in IMS networks

Both HLR and SAE-HSS in GSM, UMTS, and EPS networks.

HLR, SAE-HSS, and IMS-HSS in GSM, UMTS, EPS, and IMS networks

Flexible deployment of the HSS9860 brings the following advantages:

Simplified network structure

Convenient operation, maintenance, and service provisioning

Reduced operating expense (OPEX)

Faster rollout of diversified services for subscribers

Construction of a subscriber-centered business model

The HSS9860 must use some personal data of users during the provisioning of its functions

and services. You are obligated to take all necessary measures to comply 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 HSS9860 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

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





5

The BE and FE provide 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-3 shows the distributed structure of the HSS9860.

Figure 1-3 Distributed structure of the HSS9860

DRU: data routing unit DSU: data service unit

BSG: broadband signaling gateway CCU: call control unit

HSF: HSS signaling function 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

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





6

entities that provide identical functions to achieve load balancing. The capacity

expansion does not affect the service processing of the HSS9860.

1.2.3 Advanced Hardware Platform

The HSS9860 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.

1.2.5 Multi-Level Data Backup Mechanism

The HSS9860 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-4

shows the multi-level data backup mechanism.





7

Figure 1-4 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 the hard disk on an in-memory database board.

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 a disk array is not configured, subscriber data is backed up to the local hard disk on

a physical database board in RAID 1 mode.

− If a disk array is configured, subscriber data is backed up to the disk array in RAID

10 and hot spare disk modes.

1.2.6 Virtual HSS Function

The virtual HSS function allows a physical HSS to be divided into several logical HSSs. Each

logical HSS is equivalent to the HSS in the local network. ‎Figure 1-5 illustrates the virtual

HSS function.





8

Figure 1-5 Virtual HSS function

The virtual HSS function enables the local networks in different areas to share the same

physical HSS. It achieves centralized equipment maintenance, and distributed service

processing and subscriber data management. The virtual HSS function allows authority-based

and domain-based management and helps carriers to provide differentiated services. It

facilitates carriers to carry out network planning and equipment maintenance.

The virtual HSS function can greatly reduce the number of NEs used in the network, reduce

the equipment investment, and cut down the investment and expenses arising from system

upgrade and maintenance.

1.2.7 Large Capacity and High Integration

Using high-performance ATCA board servers, the HSS9860 has large capacity and high

integration. With fully populated, the GU HLR supports a maximum of 60 million dynamic

2G/3G subscribers and 100 million static 2G/3G subscribers.

The large-capacity HSS9860 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.8 Seamless Geographic Redundancy

The HSS9860s can be deployed in different places. Data synchronization between the

HSS9860s 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.





9

Simplifies network structure and equipment maintenance, thereby reducing the total cost

of operation (TCO).

1.2.9 Cloud Deployment

Geographically-dispersed back ends (BEs) serve as one BE logically. This logical BE

provides unified service provisioning. ‎Figure 1-6 shows how the HSS9860 is deployed in the

cloud.

Figure 1-6 Cloud deployment of the HSS9860

The HSS9860 uses service partitions and routing partitions to achieve cloud deployment.

Service partition





10

The BEs in a service partition store subscriber data by IMSI segment, and the FEs query

their local BEs.

Routing partition

The BEs in the routing partition store the mappings between subscriber identities and

service partitions. Generally, the routing partition is integrated with a service partition.

Cloud deployment has the following advantages:

Improves subscriber data storage and service processing capability.

Enables the routing partition to provide unified service provisioning and therefore

improves subscriber data management efficiency.

Increases network reliability by using seamless geographic redundancy networking for

each partition.

1.2.10 VoLTE Solution

Voice over Long Term Evolution (VoLTE) is an IP multimedia subsystem (IMS)-based voice

solution provided in the LTE network. Huawei VoLTE provides voice services, video services,

and data services with end-to-end quality of service (QoS) by overlaying the existing circuit

switched network with an IMS network and an LTE network. The VoLTE solution helps

carriers evolve from the existing 2G/3G networks to the LTE network to provide

comprehensive voice services instead of single voice services. ‎Figure 1-7 shows the network

architecture of VoLTE.





11

Figure 1-7 VoLTE network architecture

Anchor AS: anchor

application server

ATCF: access transfer

control function

ATGW: access transfer

gateway

BGCF: border gateway

control function

CSFB Proxy: circuit

switched fallback proxy

CCF: charging collection

function

CTAS: common telephony

application server

CPE: customer premises

equipment

DM Server: device

management server





12

DNS: domain name system E-UTRAN: evolved

universal terrestrial radio

access network

EMS: element management

system

EMSC: enhanced MSC

server

ENUM: E.164 number

mapping

GERAN: GSM/EDGE


HLR: home location register I-CSCF: interrogating-call


ICS: IMS centralized

services

IM-MGW: IP multimedia

media gateway

IM-SSF: IP multimedia

service switching function

IMS-HSS: IP multimedia

subsystem home subscriber

server

IP-SM-GW: IP short

message gateway

LTE CPE: long term

evolution customer premises

equipment

mAGCF: mobile access

gateway control function

MGCF: media gateway

control function

MGW: media gateway MME: mobility

management entity

MMTel AS: multimedia

telephony application server

MRFC: multimedia resource

function controller

MRFP: multimedia

resource function processor

MSC: mobile switching

center

P-CSCF: proxy-call session

control function

P-GW: PDN gateway

PCRF: policy control and

charging rules function

POTS: plain old telephone

service

RCS AS: rich

communication suite

application server

S-CSCF: serving-call


S-GW: serving gateway SBC: session border

controller

SCC AS: service

centralization and continuity

application server

SCP: service control point SPG: service provisioning

gateway

SRVCC IWF: single radio

voice call continuity

interworking function

USCDB: unified subscriber

center database

UTRAN: universal

terrestrial radio access

network

In the VoLTE solution, the HSS9860 stores data of voice services, short message services, and

intelligent services for VoLTE subscribers. It also manages the subscription data and location

data of VoLTE subscribers. The HSS9860 implements the following functions:

Supports the enhanced Single Radio Voice Call Continuity (eSRVCC) function.

The eSRVCC function enables subscribers to continue calls when they switch from the

LTE network to the 2G/3G network. To implement this function, the HSS9860 stores the

session transfer number for SRVCC (STN-SR) data and responds to queries for the data.

Optimizes anchoring procedures.

To redirect subscribers to the IMS network to use convergent multimedia services, calls

of these subscribers are routed to the IMS network by means of anchoring. The HSS9860

optimizes the anchoring procedures to shorten the call connection time. The optimization

varies according to the networks the subscribers currently connect to.

Supports IP short message service.





13

The IP short message service enables subscribers to send and receive short messages in

the IMS network after they connect to the IMS network using IP. To implement the IP

short message service, the HSS9860 uses the short message rerouting function to enable

short messages to be routed to the IP-SM-GW, which then sends the short messages to

user equipment (UEs) in the IMS network.

Supports service consistency between CS and VoLTE.

Service consistency between CS and VoLTE allows subscribers to have the same service

experience in CS and VoLTE networks.

In CS networks, subscribers' service data is stored in the HLR. In VoLTE networks,

subscribers' service data is stored in the IMS-HSS. Huawei HSS9860 can provide data

services in 2G, 3G, LTE, and IMS networks. ‎Figure 1-8 shows the networking to

implement service consistency between CS and VoLTE.

Figure 1-8 Networking to implement service consistency between CS and VoLTE

1.2.11 Auto Provision of LTE Service

Application Scenario

After deploying LTE networks, carriers have to address the following problems when they

develop LTE subscribers:

1. Subscribers have to register LTE services to the business hall. To provide LTE services

for subscribers, carriers require a large number of IT reconstructions, which increases

costs and takes long time to market.

2. After subscribers buy LTE terminals, the subscribers cannot differentiate 2G, 3G, and

LTE services and do not register LTE services. These subscribers use 2G and 3G

services using LTE terminals.

To address these problems, the HSS9860 provides the Auto Provision of LTE Service feature.

When an LTE terminal attempts to attach LTE networks, the HSS9860 generates an LTE

service profile for the subscriber based on the subscriber's 3G service profile if the subscriber

has not been provided with LTE services. ‎Figure 1-9 shows an application of the Auto

Provision of LTE Service feature.





14

Figure 1-9 Application of the Auto Provision of LTE Service feature

Provisioning Procedure

‎Figure 1-10 describes the procedure of the Auto Provision of LTE Service feature.





15

Figure 1-10 Procedure of the Auto Provision of LTE Service feature

1. When an LTE terminal attempts to attach the LTE network, the terminal sends a

registration request message to the SAE-HSS FE.

2. The SAE-HSS FE queries the USCDB to check that the subscriber has not been defined

in the LTE network.

3. The USCDB generates an LTE service profile to provide LTE services for the subscriber

based on the subscriber's 3G service profile.

4. The USCDB synchronizes the subscriber's LTE service profile to the service

provisioning system.

5. The service provisioning system synchronizes the subscriber's LTE service profile and

sends a short message to notify the subscriber of LTE service provisioning.

To implement this feature, the service provisioning system must be able to:





16

Process the requests to synchronize LTE service profile sent from the USCDB.

Send short messages to notify subscribers of LTE service provisioning.

Benefits

Carriers can develop LTE subscribers without IT reconstructions.

Subscribers using USIM cards can use LTE services without changing cards and numbers.

1.2.12 Applicable to the Internet of Things

The HSS9860 serves as a home location register in the Internet of Things. It stores the

subscription data of machine to machine (M2M) terminals and sends the data to the M2M

operation management platform in the Internet of Things. ‎Figure 1-11 shows the networking

of the HSS9860 in the Internet of Things.

Figure 1-11 HSS9860 networking in Internet of Things

GERAN: GSM/EDGE radio access

network

UTRAN: universal terrestrial radio access

network

MSC: mobile switching center SGSN: serving GPRS support node

GGSN: gateway GPRS support node -

The HSS9860 provides the following functions in the Internet of Things:

Binds IMEIs with IMSIs to ensure the security of SIM/USIM cards.

Reports a change in the status of M2M terminals to the M2M operation management

platform.

Queries the status and location information of M2M terminals.





17

1.2.13 Standard and Open Data Access Interfaces

Traditionally when deploying new services, carriers have to focus on service logic and

complex subscriber data management involving data structure design, data storage, data

backup, data redundancy, data security mechanism, and data-related operations. The diversity

of equipment provided by different vendors and different data management mechanisms

further slow down the rollout of new services. If carriers fail to promptly roll out new services,

986 -

1.2.14 Comprehensive Data Statistics and Analysis

The HSS9860 provides an efficient data analysis system, which helps carriers to collect the

complete information about subscribers in addition to the specific service data. Based on the

information, carriers can track the network operation and subscribers' call behavior, and

update market strategies in time.


Product Description ‎2 Architecture



18

2 Architecture

2.1 Hardware Architecture

2.1.1 Appearance

Cabinet

The HSS9860 uses the Huawei N68E-22 cabinet. ‎Figure 2-1 shows an N68E-22 cabinet.





19

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)





20

Item Specifications

Weight (fully-loaded extension cabinet) 365 kg (804.825 lb)

Load-bearing capacity of the floor in the

equipment room

≥ 6 / 2 (0.85 bf/in

2)

Required floor space 0.48 m2 (5.17 ft

2)

Heat dissipation 20820.024 BTU

Cabling modes supported Overhead cabling and underfloor cabling

Subrack

The HSS9860 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.





21

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.





22

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





23

OSTA 2.0 subrack

Figure 2-5 Extension cabinet

2.2 Software Structure

The HSS9860 consists of five functional subsystems, signaling processing, subscriber data

management, data service, data storage, and operation and maintenance (O&M). ‎Figure 2-6

shows the software structure of the HSS9860.





24

Figure 2-6 Software structure of the HSS9860

HSF: HSS signaling function BSG: broadband signaling

gateway

CCU: call control unit

DRU: data routing unit DSU: data service unit PGW: provisioning

gateway

OMU: operation and

maintenance unit

DBMS: database management

system

DSG: data service

gateway

DPU: dispatch unit NDF: network data function DTL: data tools

NSF: notification service

function

SPU: service processing unit

(DNS services)

-

2.2.1 Signaling Processing Subsystem

The signaling processing subsystem is responsible for establishing connections to other

network devices and processing signaling messages. The subsystem implements the following

functions:

Receives and processes Signaling System No. 7 (SS7), IP, and Diameter signaling

messages. When the HSS9860 serves as the ENS, the signaling processing subsystem

sends query messages to the number portability database (NPDB) and receives query

results from the NPDB.

Queries or updates subscriber data in the data service subsystem.

Processes subscription notifications sent from the subscriber data management

subsystem and forwards the notifications to peer network elements.





25

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 is implemented by a database platform that uses board hard disks

or a disk array as the storage medium. 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 HSS9860. For details on

the O&M subsystem functions, see ‎3 Operation and Maintenance.


Product Description ‎3 Operation and Maintenance



26

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.





27

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.





28

3.2 O&M Functions

3.2.1 Configuration Management

The HSS9860 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

HSS9860 manages network devices from a console. The HSS9860 provides a set of MML

commands for users to monitor and manage the HSS9860.

The HSS9860 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 HSS9860 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 methods on the alarm console to help users rapidly identify and

rectify faults.

Tracing Management

The HSS9860 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. The HSS9860 can trace a fault in the circuit switched (CS)

domain, packet switched (PS) domain, and evolved packet system (EPS) to a specific

network element.

Subscriber-based tracing

The HSS9860 provides subscriber-based tracing to help users identify faults:

− Traces messages over standard interfaces and saves the traced messages.

− Interprets the traced messages.

Management Panel

The HSS9860 provides a device panel to facilitate equipment management. The device panel

has the following capabilities:





29

Displays the logical module topology and automatically obtains the configuration

information about each logical node.

Displays graphically the physical location of each logical node and the relationships

between logical nodes.

Automatically collects the status of each logical node and displays different status

indicators in different colors.

Displays graphically the current and historical status of each logical node in response to

user queries.

3.2.3 Performance Measurement

The performance measurement system of the HSS9860 provides the following functions:

Allows users to create, modify, delete, and query performance measurement tasks.

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 HSS9860 at the same

time. To ensure secure concurrent use of the operation and maintenance system, the HSS9860

provides authority management and log management functions.

Authority management

The operators and maintenance consoles of the HSS9860 are assigned authorities of

different levels. On the operation and maintenance system of the HSS9860, 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 HSS9860 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 adversely

affect the system have been performed.

3.2.5 Remote Maintenance

The HSS9860 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



30

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 HSS9860.

Table 4-1 Maintenance interfaces supported by the HSS9860

Board Interface

Function Description Number of Interfaces

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





31

Board Interface


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





32

Board Interface


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 Interfaces

‎Table 4-2 describes the service interfaces provided by the HSS9860.





33

Table 4-2 Service interfaces provided by the HSS9860

Board Physical Interface

Function Description Number of Physical Interfaces

USI2 FC port This port

is used to

connect to

the disk

array.

This port can be an arbitrated loop (FC-AL),

switched fabric (FC-SW), or point-to-point

(FC-P2P) 1 Gbit/s or 2 Gbit/s auto-negotiation

FC port. It provides a built-in dual-channel

Fiber Channel Protocol (FCP) controller to

implement FC redundancy configuration.

2

GE port This port

is used to

connect to

the

Ethernet.

This port is an RJ-45 port that supports 10

Mbit/s, 100 Mbit/s, or 1000 Mbit/s Base-T

auto-negotiation.

4

VGA This port

is used to

connect to

the

monitor.

This port supports a monitor with 1024 x 768

or higher SVGA resolution.

1

USB

port

This port

is used to

connect to

an external

device.

This port is a standard universal serial bus

(USB) port.

1

USI3 FC port This port

is used to

connect to

the disk

array.

This port can be an FC-AL, FC-SW, or

FC-P2P 1 Gbit/s or 2 Gbit/s auto-negotiation

FC port. It provides a built-in dual-channel

FCP controller to implement FC redundancy

configuration.

4

GE port This port

is used to

connect to

the

Ethernet.



auto-negotiation.

2

VGA This port

is used to

connect to

the

monitor.



1

USB

port

This port

is used to

connect to

an external

This port is a standard USB port. 1





34



device.

USIA1 GE port This port

is used to

connect to

the

Ethernet.



auto-negotiation.

4

VGA This port

is used to

connect to

the

monitor.


or higher SVGA resolution. 1

USB

port

This port

is used to

connect to

an external

device.


USIA7 GE port This port

is used to

connect to

the

Ethernet.



auto-negotiation.

6

VGA This port

is used to

connect to

the

monitor.



USB

port

This port

is used to

connect to

an external

device.


ETIA0 E1 port This port

is used to

connect to

the mobile

switching

center

(MSC).

This port is a sub-miniature B (SMB) port that

supports 2.048 Mbit/s signaling transmission. 32

VGA This port

is used to

connect to



1





35



the

monitor.

USB

port

This port

is used to

connect to

an external

device.


ETIA2 GE port This port

is used to

connect to

the

Ethernet.



auto-negotiation.

2

E1 port This port

is used to

connect to

the MSC.

This port is an SMB port that supports 2.048

Mbit/s signaling transmission.

16

VGA This port

is used to

connect to

the

monitor.



USB

port

This port

is used to

connect to

an external

device.


SWI Base

port

This port

is used to

connect to

the Base

plane.

This port is a Gigabit Ethernet port that

supports 10Mbit/s, 100 Mbit/s, and 1000

Mbit/s Base-T auto-negotiation and has two

indicators.

8

Fabric

GE port

This port

is used to

connect to

the Fabric

plane.

This port is a Gigabit Ethernet port that

supports 10 Mbit/s, 100 Mbit/s, and 1000

Mbit/s Base-T auto-negotiation and has two

indicators.

8

Fabric

FC port

This port

is used to

connect

the Fabric

plane to

This port is an FC port that supports 4 Gbit/s

1000 Base-SX and has two indicators. 4





36



the disk

array.

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

FTP/SFTP Used to upload and download PGW-related files

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

A maintenance interface between the OMU and the

disk array

MML A maintenance interface between the OMU and the

OSS

SOAP A maintenance interface between the OMU and the

OSS

FTP/FTPS Used to back up data from the OMU database to a





37

Type Interface Description

third-party FTP or FTPS server

FTP/SFTP Used to back up data from the USCDB physical

database to a third-party FTP or SFTP server

FTP/SFTP Used to upload files exported from the USCDB

database to a third-party FTP or SFTP server

Different interfaces that support the same function will not apply to a single NE at the same time.

4.2.2 HSS9860 Interfaces

The HSS9860 provides open and standard interfaces for other network elements (NEs). ‎Figure

4-1 shows the interfaces between the HSS9860 and other NEs.

‎Figure 4-1 shows the interfaces between the HSS9860 and other NEs when the HSS9860

serves as the HLR and SAE-HSS in GSM, UMTS, and EPS networks.

Figure 4-1 Interfaces between the HSS9860 and other NEs when the HSS9860 serves as the

HLR and SAE-HSS in GSM, UMTS, and EPS networks

MSC: mobile switching center VLR: visitor location register

SMSC: short message service center USSD center: unstructured supplementary service





38

data center

SGSN: serving GPRS support node GGSN: gateway GPRS support node

SCP: service control point GMLC: gateway mobile location center

MME: mobility management entity S4-SGSN: serving GPRS support node

(supporting the S4 interface)

AAA: authentication, authorization,

and accounting

-


serves as the IMS-HSS in IMS networks.


IMS-HSS in IMS networks

CSCF: call session control function AS: application server

GGSN: gateway GPRS support node IM-SSF: IP multimedia service switching function


serves as the SLF in IMS networks.





39


SLF in IMS networks



serves as the ENS in IMS networks.


ENS in IMS networks


MRFC: multimedia resource function controller NPDB: number portability database

‎Figure 4-5shows the interfaces between the HSS9860 and other NEs when the HSS9860

serves as the EIR in GSM, UMTS, and EPS networks.





40


EIR in GSM, UMTS, and EPS networks.

SGSN: serving GPRS support node MSC: mobile switching center

VLR: visitor location register MME: mobility management

entity

S4-SGSN: serving GPRS support node (supporting the

S4 interface)

-

‎Table 4-4 describes the interfaces that the HSS9860 provides in mobile networks.

Table 4-4 Interfaces supported by the HSS9860

Interface

Interworking NE

Protocol Type

Function Compliance Standard

S6a MME Diameter Used by the HSS to

send subscription data

and authentication data

to the MME.

3GPP TS 29.272

S13 MME Diameter Used by the HSS to

send mobile terminals'

status at the MME's

request.

S6d S4-SGSN Diameter Used by the HSS to


and authentication data





41

Interface

Interworking NE

Protocol Type


to the S4-SGSN.

S13' S4-SGSN Diameter Used by the HSS to


status at the S4-SGSN's

request.

SWx AAA Diameter Used by the HSS to

send authentication

data, subscription data,

and location data to the

3GPP AAA server

when mobile stations

attempt to connect to

Non-3GPP networks.

3GPP TS 29.273

SLh GMLC Diameter Used by the HSS to

send routing data

related to location

services to the GMLC.

3GPP TS 29.173

C MSC/SM

C

MAP Used by the HLR to

send routing data to the

MSC or the SMC.

3GPP TS 29.002

F MSC MAP Used by the HLR to


status at the MSC's

request.

D VLR/US

SD

Center

MAP Used by the HLR to

send location data

and subscriber

management data to

the VLR.

Used by the HLR to

interwork with the

USSD center to

process USSD

services.

Gr SGSN MAP Used by the HLR to

send authentication data

and subscription data to

the SGSN.

Gf SGSN MAP Used by the HLR to


status at the SGSN's

request.

Gc GGSN MAP Used by the HLR to


and location data to the





42

Interface

Interworking NE

Protocol Type


GGSN.

J SCP MAP Used by the HLR to

send location data and

status information to the

SCP to implement

intelligent services.

Lh GMLC MAP Used by the HLR to

send routing data

related to location

services to the GMLC.

SOAP Service

provision

ing

system

SOAP Used by the HSS or the

HLR to interwork with

the service provisioning

system to achieve

service provisioning.

SOAP 1.2

MML Service

provision

ing

system

MML Used by the HSS or the

HLR to interwork with

the service provisioning

system to achieve

service provisioning.

Man-machine language

(complies with Huawei

proprietary standards)

Simple

Network

Manage

ment

Protocol

(SNMP)/

MML/S

OAP/NT

P/FTP/F

TPS

M2000 SNMP

MML

SOAP

NTP

FTP/FTP

S

SNMP

Used by the

HSS9860 to report

alarms to the

M2000.

MML

Used by the

HSS9860 to receive

MML commands

from the M2000.

SOAP

Used by the

HSS9860 to receive

SOAP commands

from the M2000.

NTP

Used by the

HSS9860 to

synchronize OMU

system time with the

M2000 system time.

FTP/FTPS

Used by the

HSS9860 to save

OMU data to an

SNMP v2c

SNMP v3

IETF

RFC 1305

SOAP 1.2

Network Time

Protocol (NTP)

FTP/FTPS





43

Interface

Interworking NE

Protocol Type


FTP/FTPS server.

Cx I-CSC

F

S-CS

CF

Diameter

/SCTP

Diameter

/TCP

Used by the HSS to

send S-CSCF's

capacity set at the

I-CSCF's request for

the I-CSCF to select

an S-CSCF to serve

the calling

subscriber.

Used by the HSS to

send backup data at

the S-CSCF's

request for the

S-CSCF to

implement

redundancy

networking.

3GPP TS 29.228

3GPP TS 29.229

Gi GGSN RADIUS/U

DP

Used by the HSS to

send Early IMS

authentication data at

the GGSN's request.

3GPP TS 33.978

Sh AS Diameter Used by the HSS to


at AS' request.

3GPP TS 29.328

3GPP TS 29.329

Si IM-SSF MAP/SIGT

RAN

Used by the HSS to

send subscribers'

CAMEL subscription

information (CSI) at

IM-SSF's request.

3GPP TS 23.278

Dx I-CSC

F

S-CS

CF

Diameter

/SCTP

Diameter

/TCP

Used by the SLF to

send the address of

the serving HSS at

the

I-CSCF/S-CSCF's

request if multiple

HSS devices are

deployed in the IMS

network.

Reserved if only one

HSS is deployed.

3GPP TS 29.228

3GPP TS 29.229

Dh AS Diameter Used by the SLF to

send the address of

the serving HSS at

the AS's request if

multiple HSS

devices are deployed

in the IMS network.

3GPP TS 29.228

3GPP TS 29.229





44

Interface

Interworking NE

Protocol Type


Reserved if only one

HSS is deployed.

DNS/EN

UM

P-CS

CF

I-CSC

F

S-CS

CF

AS

MRF

C

DNS Used by the ENS to

send DNS/ENUM

query results at a

DNS/ENUM client's

request.

RFC 1034

RFC 1035

RFC 1886

RFC 2181

RFC 2782

RFC 2915

RFC 2916


Product Description ‎5 Reliability



45

5 Reliability

5.1 Hardware Reliability

Redundancy and Backup Design

The HSS9860 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 HSS9860 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 HSS9860 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 HSS9860 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 HSS9860 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.





46

5.2 Software Reliability

Distributed Structure of Software Modules

The software modules of the HSS9860 use a distributed structure. Therefore, a single-point

failure does not adversely affect service processing. This improves the system reliability.

Flow Control

The HSS9860 uses the flow control mechanism. When a congestion occurs, the HSS9860

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 HSS9860 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 HSS9860 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 HSS9860 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 HSS9860 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 HSS9860 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





47

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 HSS9860 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 HSS9860 checks data consistency between:

Master and slave nodes of a HSS9860

In-memory database and physical database of a HSS9860

Active and redundancy HSS9860s (only with the geographic redundancy solution)


Product Description ‎6 Technical Specifications



48

6 Technical Specifications

6.1 Performance Specifications

‎Table 6-1 lists the performance specifications of the HSS9860.

Table 6-1 HSS9860 performance specifications

Item Specifications

Maximum number of subscribers supported GSM and UMTS networks: 60 million

dynamic subscribers or 100 million

static subscribers

EPS networks: 70 million subscribers

IMS networks: 20 million subscribers

GSM, UMTS, and EPS networks: 50

million dynamic subscribers or 70

million static subscribers

GSM, UMTS, EPS, and IMS networks:

20 million subscribers

Bearer networking modes supported IP networking

TDM networking

TDM/IP hybrid networking

Maximum number of 64 kbit/s TDM links

supported

11,776

Maximum number of 2 Mbit/s TDM links

supported

736

Maximum number of SCTP links supported 11,776

Maximum number of Diameter links

supported

512

Maximum processing speed for commands

from the provisioning system (in full

configuration)

10,000 commands/second





49

6.2 Reliability Specifications

‎Table 6-2 lists the reliability specifications of the HSS9860.

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

Table 6-2 Reliability specifications of the HSS9860

Item Specifications

System repair rate ≤ 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

Success rate of switchovers to redundancy

components

> 95%

Board switchover duration ≤ 1

6.3 Power Consumption Specifications

‎Table 6-3 lists the power consumption specifications of the HSS9860.

Table 6-3 Power consumption specifications of the HSS9860

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





50

Component Maximum Power Consumption

Typical Power Consumption

UPBA0 125 W 110 W

UPBA2 135 W 110 W

UPBA6 122 W 110 W

USIA1 8 W 7 W

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 Clock Specifications

‎Table 6-4 lists the technical specifications of the HSS9860 clock system.

Table 6-4 Technical specifications of the HSS9860 clock system

Item Specifications

Network

access

parameters

Lowest

accuracy

Stratum-2 clock: ±4 x 10-7

Stratum-3 clock: ±4.6 x 10-6

Pull-in range Synchronization accuracy of stratum-2 clock: ± 4 x 10-7

Synchronization accuracy of stratum-3 clock: ± 4.6 x

10-6

Maximum

frequency

offset

Stratum-2 clock: 5 x 10-10

/day

Stratum-3 clock: 2 x 10-8

/day

Maximum

initial

frequency

offset

Stratum-2 clock: < 5 x 10-10

/day

Stratum-3 clock: < 1 x 10-8

/day

Long-term

phase

variation

Ideal working

status

MR IE ≤ 1

Holdover status MR IE ( ) ≤ x + (1/2) x b x s2 + c

Here, s indicates the time in second, and MRTIE is in

nanosecond (ns).

Stratum-2 clock:

a = 0.5





51

Item Specifications

b = 1.16 x 10-5

c = 1000

Stratum-3 clock:

a = 10

b = 2.3 x 10-4

c = 1000

Clock

working

mode

Fast pull-in

Locked

Holdover

Free-run

Input jitter

tolerance

See ‎Figure 6-1.

Lowest accuracy: the maximum frequency offset in a long period (20 years) when the clock works in

free-run mode.

Maximum frequency offset: the maximum relative difference between clock frequencies in a unit

time during continuous running of the clock.

Pull-in range: the maximum frequency bandwidth of the input clock signals that the clock can lock.

Maximum relative time interval error (MRTIE): the variation of maximum peak-to-peak delay of a

tested clock relative to an actual reference clock during the test.

Figure 6-1 Maximum allowed input jitter and lower threshold of wander

If the system is working properly when the jitter frequency of an input signal is 1 kHz and the

signal amplitude is greater than 1.5 UI, then the input signal meets requirements.

UI stands for unit interval. The reciprocal of the digital signal frequency is 1 UI. For example, the UI of

a 2.048-Mbit/s signal is 488 ns.





52

6.5 EMC Specifications

The electromagnetic compatibility (EMC) of the HSS9860 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



53

7 Environmental Requirements

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 -40°C to +70°C (-40°F to 158°F)

Temperature change rate ≤ 1°C/ (33 8°F/ )

Relative humidity 10% to 100%

Altitude ≤ 5 (16,4 4 )

Atmospheric pressure 70 kPa to 106 kPa

Solar radiation ≤ 112 W/ 2

Heat radiation ≤ 6 W/ 2

Wind speed ≤ 2 / (65 62 / )

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:

− 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.





54

− 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 / 3

Deposited dust ≤ 2 / 2·h

Sand ≤ 3 / 3

NOTE

Suspended : ≤ 75 μ

D : 75 μ ≤ ≤ 15 μ

: 15 μ ≤ ≤ 1 μ

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

SO2 0.3 mg/m3 to 1.0 mg/m

3

H2S 0.1 mg/m3 to 0.5 mg/m

3

NO2 0.5 mg/m3 to 1.0 mg/m

3

NH3 1.0 mg/m3 to 3.0 mg/m

3

Cl2 0.1 mg/m3 to 0.3 mg/m

3

HCl 0.1 mg/m3 to 0.5 mg/m

3

HF 0.01 mg/m3 to 0.03 mg/m

3

O3 0.05 mg/m3 to 0.1 mg/m

3





55

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 ( 28 ) No requirements

Acceleration No requirements ≤ 2 / 2 (65.62

ft/s2)

Frequency range 2 Hz to 9 Hz 9 Hz to 200 Hz

Unsteady impulse Impulse response

spectrum II

≤ 25 / 2 (820.2 ft/s

2)

Static payload ≤ 5 P

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.

Table 7-5 Climatic requirements for equipment transportation

Item Range

Temperature -40°C to +70°C (-40°F to 158°F)


Relative humidity 10% to 100%

Altitude ≤ 5 (16,4 4 )







56

Item Range


Wind speed ≤ 2 / (65 62 / )

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

Deposited dust ≤ 3 / 2·h

Sand ≤ 1 / 3

NOTE

: ≤ 75 μ

D : 75 μ ≤ ≤ 15 μ

: 15 μ ≤ ≤ 1 μ


Table 7-7 Density requirements for chemically active substances in equipment transportation



3


3


3





57



3


3


3

HF 0.01 mg/m3 to 0.03 mg/m

3

O3 0.05 mg/m3 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




Sinusoidal

oscillation

Shift ≤ 7 5 ( 3

in.)

No

requirements

No

requirements

Acceleration No

requirements

≤ 2 / 2

(65.62 ft/s2)

≤ 4 / 2

(131.23 ft/s2)

Frequency

range

2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500

Hz

Random

oscillation

Acceleration

spectrum

density

10 m2/s

3 3 m

2/s

3 1 m

2/s

3

Frequency

range

2 Hz to 9 Hz 9 Hz to 200 Hz 200 Hz to 500

Hz

Unsteady

impulse

Impulse

response

spectrum II

≤ 3 / 2 (984.24 ft/s

2)


NOTE





Static payload


specified way.





58

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: +5°C to +40°C (41°F to 104°F)

Short term: -5°C to +55°C (23°F to 131°F)

Relative humidity Long term: 5% to 85%

Short term: 5% to 90%

Altitude ≤ 4 (13,123 2 )





Wind speed ≤ 1 / (3 28 / )


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 ≤ 24 / 3

Deposited dust ≤ 1 5 / 2·h

Sand ≤ 3 / 3





59


NOTE

: ≤ 75 μ

D : 75 μ ≤ ≤ 15 μ

: 15 μ ≤ ≤ 1 μ


Table 7-11 Density requirements for chemically active substances during equipment operation



3


3


3


3


3


3

HF 0.01 mg/m3 to 0.03 mg/m

3

O3 0.05 mg/m3 to 0.1 mg/m

3


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

Table 7-12 Mechanical stress requirements for equipment operation



Sinusoidal

oscillation

Shift ≤ 3 5 ( 14 ) No requirements

Acceleration No requirements ≤ 1 / 2 (32.81

ft/s2)

Frequency range 5 Hz to 9 Hz 9 Hz to 200 Hz

Unsteady impulse Impulse response

spectrum II

≤ 1 / 2 (328.08 ft/s

2)






60



NOTE





Static payload


specified way.

Anti-Shock Requirements

The HSS9860 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.

Huawei hss9860 v900 r008c20 production description

Technology

Transcript of Huawei hss9860 v900 r008c20 production description