ubro solution description(v200r001_02,03).pdf

uBro Solution V200R001,03

Description Issue 02

Date 2009-08-14

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

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]

Copyright © Huawei Technologies Co., Ltd. 2009. 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 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 the warranty of any kind, express or implied.

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

http://www.huawei.com/

mailto:[email protected]

uBro Solution Description Contents

Issue 02 (2009-08-14) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

Contents

About This Document.....................................................................................................................1

1 Description of the uBro Solution............................................................................................1-1 1.1 Background ...................................................................................................................................................1-2 1.2 Huawei uBro Solution...................................................................................................................................1-2 1.3 Benefits .........................................................................................................................................................1-3

2 Solution Architecture ................................................................................................................2-1 2.1 Networking Architecture ...............................................................................................................................2-2 2.2 Hardware Configurations ..............................................................................................................................2-3

2.2.1 Hardware Configurations for Huawei uBro Solution (Triple-cabinet).................................................2-3 2.2.2 Hardware Configurations for Huawei uBro Solution (Single-cabinet) ................................................2-7

2.3 Major NEs .....................................................................................................................................................2-8 2.3.1 AP ........................................................................................................................................................2-8 2.3.2 AG........................................................................................................................................................2-8 2.3.3 Clock Server.........................................................................................................................................2-8 2.3.4 AHR .....................................................................................................................................................2-8 2.3.5 AP manager ..........................................................................................................................................2-9 2.3.6 SeGW...................................................................................................................................................2-9 2.3.7 M2000..................................................................................................................................................2-9 2.3.8 AAA.....................................................................................................................................................2-9

2.4 Technical Features.........................................................................................................................................2-9 2.4.1 Automatic Network Planning And Optimizing ....................................................................................2-9 2.4.2 Interference Detection........................................................................................................................2-10 2.4.3 Location Detection (Optional) ...........................................................................................................2-10 2.4.4 Location Indication ............................................................................................................................2-11 2.4.5 Clock Synchronization.......................................................................................................................2-11 2.4.6 Access Control ...................................................................................................................................2-11 2.4.7 Cell Reselection .................................................................................................................................2-12 2.4.8 Cell Handover ....................................................................................................................................2-12 2.4.9 HSPA..................................................................................................................................................2-12 2.4.10 Security Authentication....................................................................................................................2-13 2.4.11 Differential Charging (Optional)......................................................................................................2-13

Contents uBro Solution

Description

ii Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 02 (2009-08-14)

2.4.12 Performance Management of the AP (Optional) ..............................................................................2-13 2.4.13 Double-IPSec (Optional)..................................................................................................................2-14 2.4.14 Emergency Call Service...................................................................................................................2-14 2.4.15 Selection of the Optimal Core Network...........................................................................................2-14 2.4.16 AG Supporting Iu-Flex.....................................................................................................................2-14 2.4.17 End-to-End Security Solution Between the AP and the AP Manager (Optional).............................2-15 2.4.18 Flow Control of the IMSI Query Requests ......................................................................................2-15 2.4.19 Dynamic Jitter Prevention................................................................................................................2-15 2.4.20 Compensation for Packet Loss in Voice Services ............................................................................2-15 2.4.21 Alarm for the Disconnection of AP (Optional).................................................................................2-16 2.4.22 Daylight Saving Time ......................................................................................................................2-16 2.4.23 Allocation of Cell IDs ......................................................................................................................2-16 2.4.24 AP Type............................................................................................................................................2-16 2.4.25 AP Name ..........................................................................................................................................2-16 2.4.26 Separation of OM and Service (Optional)........................................................................................2-16

2.5 System Interface..........................................................................................................................................2-17 2.5.1 Overview of Interfaces.......................................................................................................................2-17 2.5.2 eIu Interface .......................................................................................................................................2-17 2.5.3 Ab Interface........................................................................................................................................2-19 2.5.4 Ae Interface........................................................................................................................................2-19 2.5.5 Hb Interface .......................................................................................................................................2-20 2.5.6 Hg Interface .......................................................................................................................................2-20 2.5.7 Ho Interface .......................................................................................................................................2-21 2.5.8 Ac Interface........................................................................................................................................2-21 2.5.9 RADIUS Interface .............................................................................................................................2-22 2.5.10 D' Interface.......................................................................................................................................2-22 2.5.11 Diameter Interface............................................................................................................................2-22 2.5.12 Uu Interface .....................................................................................................................................2-22 2.5.13 Iu Interface .......................................................................................................................................2-22

3 Networking Solution.................................................................................................................3-1 3.1 Service Networking.......................................................................................................................................3-2 3.2 Access Networking........................................................................................................................................3-3

3.2.1 xDSL Access Networking ....................................................................................................................3-3 3.2.2 Ethernet Access Networking................................................................................................................3-4

3.3 Clock Server Deployment Scheme................................................................................................................3-5 3.3.1 Networking with the Clock Server Deployed in the uBro Core Network............................................3-5 3.3.2 Networking with the Clock Server Deployed in the Backbone Network.............................................3-5 3.3.3 Networking with the Clock Server Deployed in the Access Network .................................................3-6

4 Security Solution........................................................................................................................4-1 4.1 Overview of the Security Solution ................................................................................................................4-2 4.2 Network Equipment Security ........................................................................................................................4-2

uBro Solution Description Contents


iii

4.3 Network Security ..........................................................................................................................................4-3 4.3.1 Security Domain Partition....................................................................................................................4-3 4.3.2 Border Protection .................................................................................................................................4-3 4.3.3 Network Anti-Attack............................................................................................................................4-3 4.3.4 Network Access Authentication ...........................................................................................................4-3 4.3.5 Transmission Security ..........................................................................................................................4-4

4.4 O&M Security...............................................................................................................................................4-4

5 QoS Policies ................................................................................................................................5-1 5.1 General QoS Policies ....................................................................................................................................5-2 5.2 QoS Policies of the AP Air Interface .............................................................................................................5-2

5.2.1 QoS Assurance Algorithm at Resources Congestion ...........................................................................5-2 5.2.2 QoS Assurance Algorithm of Traffic Volume and Link Quality ..........................................................5-3

5.3 Transmission QoS Scheme............................................................................................................................5-4 5.3.1 Congestion Detection Algorithm..........................................................................................................5-4 5.3.2 Transmission Packet Multiplexing and Header Compression..............................................................5-4 5.3.3 Transmission Resources Based Access Algorithm...............................................................................5-5 5.3.4 Blind Handover....................................................................................................................................5-5

5.4 AG QoS Scheme ...........................................................................................................................................5-5 5.4.1 AG Access Control...............................................................................................................................5-5 5.4.2 QoS Queue Management .....................................................................................................................5-5 5.4.3 DiffServ Function ................................................................................................................................5-6 5.4.4 QoS Mapping Function........................................................................................................................5-6 5.4.5 Traffic Regulating ................................................................................................................................5-6 5.4.6 Prevention of Time Delay and Jittering ...............................................................................................5-6

6 Operation and Maintenance ....................................................................................................6-1 6.1 O&M System ................................................................................................................................................6-2

6.1.1 Solution to Terminal Equipment Management ....................................................................................6-2 6.1.2 Solution to Central Office Equipment Management............................................................................6-2

6.2 O&M System of the AP ................................................................................................................................6-3 6.2.1 AP Manager..........................................................................................................................................6-3 6.2.2 AP WebUI ............................................................................................................................................6-4

6.3 O&M System of Central Office Equipment ..................................................................................................6-5 6.3.1 AG Maintenance System......................................................................................................................6-5 6.3.2 AHR O&M System..............................................................................................................................6-7 6.3.3 Clock Server O&M System .................................................................................................................6-8 6.3.4 SeGW Maintenance System.................................................................................................................6-9

7 Service Operation.......................................................................................................................7-1 7.1 Service Provisioning .....................................................................................................................................7-2

7.1.1 AP User Identifying Scheme................................................................................................................7-2 7.1.2 Service Provisioning Mode..................................................................................................................7-2 7.1.3 AP Registration ....................................................................................................................................7-3

Contents uBro Solution

Description

iv Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 02 (2009-08-14)

7.1.4 AP Deregistration .................................................................................................................................7-3 7.1.5 AP Migration........................................................................................................................................7-4 7.1.6 Maintenance of the Access Control List of the AP ..............................................................................7-4

7.2 AP Installation ...............................................................................................................................................7-5 7.3 Interference Processing .................................................................................................................................7-5 7.4 Upgrading of the AP......................................................................................................................................7-6 7.5 Maintenance of the AP ..................................................................................................................................7-6

8 Reference Information ..............................................................................................................8-1 8.1 System Performance......................................................................................................................................8-2

8.1.1 AP ........................................................................................................................................................8-2 8.1.2 AG........................................................................................................................................................8-2 8.1.3 AP Manager..........................................................................................................................................8-2 8.1.4 AHR .....................................................................................................................................................8-3 8.1.5 Clock Server.........................................................................................................................................8-4 8.1.6 SeGW...................................................................................................................................................8-4 8.1.7 M2000..................................................................................................................................................8-5 8.1.8 AAA.....................................................................................................................................................8-5

8.2 Reference Standards and Protocols ...............................................................................................................8-5

A Glossary .................................................................................................................................... A-1

B Acronyms and Abbreviations ................................................................................................B-1

uBro Solution Description Figures


v

Figures

Figure 1-1 Networking of Huawei uBro solution...............................................................................................1-2

Figure 2-1 Networking architecture of Huawei uBro solution ...........................................................................2-2

Figure 2-2 Components in the provision server .................................................................................................2-4

Figure 2-3 Components in the security gateway server......................................................................................2-5

Figure 2-4 Components in the service gateway server .......................................................................................2-6

Figure 2-5 Components in the uBro single-cabinet ............................................................................................2-7

Figure 2-6 Interfaces in the uBro solution........................................................................................................2-17

Figure 2-7 Protocol stack of the eIu interface ..................................................................................................2-17

Figure 2-8 Protocol stack at the Ab interface ...................................................................................................2-19

Figure 2-9 Protocol stack at the Ae interface....................................................................................................2-19

Figure 2-10 Protocol stack at the Hb interface .................................................................................................2-20

Figure 2-11 Protocol stack at the Hg interface .................................................................................................2-20

Figure 2-12 Protocol stack at the Ho interface .................................................................................................2-21

Figure 2-13 Protocol stack at the Ac interface..................................................................................................2-21

Figure 3-1 AG networking architecture..............................................................................................................3-2

Figure 3-2 xDSL access networking architecture...............................................................................................3-3

Figure 3-3 Ethernet access networking architecture...........................................................................................3-4

Figure 3-4 Networking architecture with the clock server deployed in the uBro core network .........................3-5

Figure 3-5 Networking architecture with the clock server deployed in the backbone network..........................3-6

Figure 3-6 Networking architecture with the clock server deployed in the access network...............................3-6

Figure 6-1 Architecture of the O&M system......................................................................................................6-2

uBro Solution Description Tables


vii

Tables

Table 8-1 System performance parameters of the AP.........................................................................................8-2

Table 8-2 System performance parameters of the AG ........................................................................................8-2

Table 8-3 System performance parameters of the AP manager ..........................................................................8-2

Table 8-4 Performance specifications of the AHR (Basic configuration)...........................................................8-3

Table 8-5 Performance specifications of the AHR (Medium configuration) ......................................................8-3

Table 8-6 System performance parameters of the clock server ..........................................................................8-4

Table 8-7 System performance parameters of the SeGW ...................................................................................8-5

Table 8-8 System performance parameters of M2000 ........................................................................................8-5

Table 8-9 System performance parameters of AAA ...........................................................................................8-5

uBro Solution Description About This Document

About This Document

Purpose This document describes the Huawei uBro solution V200R001 in terms of architecture, security, QoS, O&M, service operation, and reference information.

Related Versions The following table lists the product versions related to this document.

Product Name Version

uBro solution V200R001,03

Intended Audience This document is intended for:

System engineer Maintenance engineer

Organization This document consists of ten chapters and is organized as follows.

Chapter Content

1. Description of the uBro Solution

This chapter describes the background, networking applications, and benefits of the Huawei uBro solution.

2. Solution Architecture This chapter describes the networking architecture, hardware configurations, major NEs and interfaces, and technical features of the Huawei uBro solution.

3. Networking Solution This chapter describes the service networking solution, access networking solution, and clock server deployment solution.

About This Document uBro Solution

Description

Chapter Content

4. Security Solution This chapter describes the security strategies of the Huawei uBro solution in terms of equipment security, network security, and OM security.

5. QoS Policies This chapter describes the general QoS policy of the Huawei uBro solution, as well as the AP air interface QoS solution, transmission QoS solution, and AG QoS solution.

6. Operation and Maintenance

This chapter describes the structure and functions of the OMS of the Huawei uBro solution.

7. Service Operation This chapter describes the service provisioning, installation, interference elimination, software upgrade, and routine maintenance of the AP.

8. Reference Information This chapter describes the specifications of the major NEs in the Huawei uBro solution and the standards and protocols that the solution complies with.

Appendix A Glossary This appendix explains the terms used in this document.

Appendix B Acronyms and Abbreviations

This appendix lists the acronyms and abbreviations used in this document.

Conventions

Symbol Conventions The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results.

Indicates a tip that may help you solve a problem or save time.

Provides additional information to emphasize or supplement important points of the main text.

uBro Solution Description About This Document

General Conventions

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Terminal display is in Courier New.

Command Conventions


Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in square brackets [ ] are optional.

{ x | y | ... } Alternative items are grouped in braces and separated by vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

GUI Conventions


Boldface Buttons, menus, parameters, tabs, windows, and dialog titles are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operation

Format Description

Key Press the key. For example, press Enter and press Tab.

About This Document uBro Solution

Description

Format Description

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operation

Action Description

Click Select and release the primary mouse button without moving the pointer.

Double-click Press the primary mouse button twice continuously and quickly without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain position.

Update History Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.

Updates in Issue 02 (2009-08-14) The second release.

Updates in Issue 01 (2009-05-31) Initial release.

uBro Solution Description 1 Description of the uBro Solution


1-1

1 Description of the uBro Solution

About Thi

T le lists the cont

s Chapter

he following tab ents of this chapter.

Section Describes

1.1 Background Application background of the uBro solution.

1.2 Huawei uBro Solution The networking of Huawei uBro solution.

1.3 Benefits The benefits that carriers and users can obtain from Huawei uBro solution.

1 Description of the uBro Solution uBro

Solution Description

1-2 Copyright © Huawei Technologies Co., Ltd.

2009-08-14)

1.1 Background The indoor coverage of universal mobile telecommunications system (UMTS) signals has always been a problem that troubles users and carriers. The reasons are as follows:

UMTS signals are in high frequency band, so buildings may block signals. This causes the low quality of the signals at home, in the small office and home office (SOHO), and the small and medium enterprise (SME).

The coverage of indoor signals has different features from the coverage of outdoor signals. Outdoor signals cover a large area. This is called pane coverage. The indoor UMTS are of small capacity and micro areas. Therefore, the wireless coverage of indoor signals requires point coverage. This means that the macro cell network cannot solve the coverage problem of indoor signals and a better scheme is required.

With the wide use of the UMTS, indoor users want to enjoy high-speed wireless data services conveniently at low cost. The number of pieces of user equipment (UEs) in the macro cell network is large, and the broadband resources provided through the High Speed Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access (HSUPA) are shared by many UEs. Therefore, the actual bandwidth allocated to each UE is low and cannot meet the requirements of UEs for high-speed services.

To solve the coverage problem of indoor signals, carriers need to consider not only the cost of purchasing equipment, but also the cost of installing and maintaining the equipment. Thus, carriers need a solution with low cost and high profits.

Therefore, Huawei Technologies Co., Ltd. (hereafter referred to as Huawei) provides the uBro solution that solves the coverage problem of the indoor signals of the UMTS effectively.

1.2 Huawei uBro Solution Figure 1-1 shows the networking of Huawei uBro solution.

Figure 1-1 Networking of Huawei uBro solution

Huawei Proprietary and Confidential Issue 02 (

AG

Home Zone&SOHO Zone

AP HGW

NodeB RNC

Macro Network

SME Zone

ePico

ePico

UMTS Core Network

uBro Solution Description 1 Description of the uBro Solution


1-3

AP access point AG access gateway UE user equipment HGW home gateway RNC radio network controller

Huawei uBro solution solves the problem of the indoor signal coverage at home, in SOHOs, and in SMEs for carriers.

Huawei uBro solution introduces the access point (AP) and access gateway (AG) into the current UMTS. The AP is an access device in the UMTS and provides users with standard UMTS services. The AP accesses the Internet through the home gateway (HGW), and the ePico accesses the Internet through the enterprise Ethernet, and then accesses the AG. The AG manages the AP/ePico and routes data to the UMTS core network.

UMTS enhance indoor coverage pico base station (ePico), used for macro network indoor blind spot coverage and traffic offloading. The AP is a general term for all the APs used at home, in SOHOs and the ePicos in SMEs, unless there are special specifications.

1.3 Benefits

For Carriers Carriers can obtain the following benefits from Huawei uBro solution:

The coverage problem of the signals at home, in SOHOs, and in SMEs is solved and the capacity of the UMTS is increased.

The solution provides sufficient high speed packet access (HSPA) capacity to meet the requirements for high-speed services for the users at home, in SOHOs, and in SMEs. By relying on better UMTS service experience, the solution improves the customer retention rate (CRR).Users can cultivate the habit of using data services.

Carriers do not have to set up equipment rooms because the AP is small and portable and can be located at home, in SOHOs, and in SMEs. The AP is easy to transport and users can install and provide power supply for the AP by themselves. This helps to decrease the cost of creating a site.

The AP supports automatic network design, software upgrade, and data configuration. This helps to decrease the operation cost because carriers do not have to spend much energy on maintaining the AP.

Carriers can use the existing network to set up the uBro network without many changes, thus facilitating the quick setup of the uBro network.

For Users Users can obtain the following benefits from Huawei uBro solution:

User investment is protected by preventing the AP from being used by unauthorized UEs, because the AP supports the management and admission control of authorized UEs.

1 Description of the uBro Solution uBro


1-4 Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 02 (2009-08-14)

Compared with the users in the outdoor macro cell network, the users in the uBro network covered by the signals of the AP obtain better UMTS service experience and enjoy the data services with higher speed and quality.

Compared with the users in the outdoor macro cell network, the users in the uBro network covered by the signals of the AP pay lower fees.

The AP can be placed on a desk or wall and support plug and play.

uBro Solution Description 2 Solution Architecture


2-1

2 Solution Architecture

About Thi

T nten

s Chapter

he following table lists the co ts of this chapter.

Section Describes

2.1 Networking Architecture of Huawei uBro solution. The networking architecture

2.2 Hardware Configurationsne solution with single-cabinet and the other

The hardware configurations of two Huawei uBro solutions, osolution with triple-cabinet.

2.3 Major NEs The major NEs of Huawei uBro solution and their functions.

2.4 Technical Features The technical features of Huawei uBro solution.

2.5 System Interface The interfaces and protocols supported by the uBro solution.

2 Solution Architecture uBro



Issue 02 (2009-08-14)

2.1 Networking Architecture Figure 2-1 shows the networking architecture of Huawei uBro solution.

Figure 2-1 Networking architecture of Huawei uBro solution

User Access Network

Home Zone&SOHO Zone

AP HGW UE

SME Zone

ePico ePico

UE UE

uBro Core NetworkPublic Network UMTS Core Network

SeGW AG

AHRAP Manager

M2000 Clock Server

IP Network

AAA

IP Network

Office LAN

CS

PS

AP access point AG access gateway UE user equipment HGW home gateway SeGW security gateway AHR AP home register AAA authorization, authentication and accounting server CS circuit switched domain PS packet switched domain

The uBro network is divided into three parts:

User access network This part performs the service access function. The AP is installed at home, in SOHOs, or in SMEs and accesses the public network through the enterprise Ethernet or a home gateway, for example, the asymmetrical digital subscriber line modem (ADSL modem).

Public network This part is also called the uBro service bearer network. It implements the convergence, distribution, and remote transmission of uBro services.

uBro core network This part implements the routing, forwarding, and management of uBro services. It consists of the AG, AP manager, AP home register (AHR), clock server, security gateway (SeGW), Huawei iManager M2000 Integrated Network Management System (M2000), authorization, authentication, and accounting server (AAA server).



2-3

2.2 Hardware Configurations The hardware configurations of the uBro core network vary according to the network scale. The uBro core network can be deployed with single-cabinet or triple-cabinet.

The standard hardware configurations of the uBro network are implemented through single-cabinet or triple-cabinet. Customized hardware configurations used in certain scenarios are not described in this section.

2.2.1 Hardware Configurations for Huawei uBro Solution (Triple-cabinet)

In Huawei uBro solution (triple-cabinet), the three cabinets are provided for the provision server, security gateway server, and service gateway server respectively.




Issue 02 (2009-08-14)

Figure 2-2 shows the components in the provision server.

Figure 2-2 Components in the provision server

Provision Server (46U)

Filter panel(3U)

Filter panel(2U)

S5328C-EI-0(1U)

PC Server-1(AAA FEP, optional)(2U)

KVM(1U)

Disk array(3U)

Cable shelf(1U)

S5328C-EI-1(1U)Cable shelf(1U)

Filter panel(1U)

PDF(3U)

M2000-0

AP Manager-0

M2000-1(optional)

AP M

anager-1(optional)SW

USW

UAH

R-0

AHR

-1(optional)AAA

-0

AAA-1

ATAE shelf(14U)

SMM SMM

Filter panel(1U)

Filter panel(3U)

Filter panel(1U)

Outstanding filter panel(1U)

Outstanding filter panel(1U)PC Server-1(AAA FEP, optional)(2U)

Outstanding filter panel(1U)PC Server(USM)(2U)

Outstanding filter panel(1U)

46U45U44U43U42U41U40U39U38U37U36U35U34U33U32U31U30U29U28U27U

06U05U04U03U02U01U



06U05U04U03U02U01U


01 02 03 04 05 06 07 08 09 10 11 12 13 14



2-5

Figure 2-3 shows the components in the security gateway server.

Figure 2-3 Components in the security gateway server

Security Gateway Server (46U)

Filter panel(1U)

S9303-0(4U)

S9303-1(4U)

Large-capacity fiber rack(1U)

PDF(3U)

Cabling shelf(1U)


06U05U04U03U02U01U



06U05U04U03U02U01U


Cabling shelf(1U)Filter panel(1U)

Large-capacity fiber rack(1U)

Cabling shelf(1U)IPCLK1000-1(1U)Cabling shelf(1U)IPCLK1000-0(1U)Cabling shelf(1U)

Large-capacity fiber rack(1U)Filter panel(1U)

Cabling shelf(1U)

LPU

ES

PU

SR

U

SFU

SR

U

ES

PU

01 02 03 04 09 11 10 05 06 07 08

12

SFU

Eudemon 8080E(20U)

LPU

Filter panel(1U)




Issue 02 (2009-08-14)

Figure 2-4 shows the components in the service gateway server.

Figure 2-4 Components in the service gateway server

Service Gateway Server (46U)

PDF(2U)

Filter Panel(2U)


06U05U04U03U02U01U



06U05U04U03U02U01U


Air Defence Subrack(2U)



CPCI (9U)

UA

FUU

AFU

UA

FUU

AFU

UFC

UU

FCU

UR

CU

UR

CU

UO

MU

UO

MU

UG

TPU

GTP

UP

WR

UP

WR

CPCI (9U)

UP

IUU

PIU

UP

IUU

PIU

UP

IUU

PIU

UB

IUU

AC

UU

BIU

UA

CU

UFSU

UFSU

ULA

NU

CK

I

UC

KI

UP

WR

UP

WR

UA

LU

CPCI (9U)

UA

FUU

AFU

UAS

UU

ASU

UAS

UU

ASU

UR

CU

UR

CU

UAS

UU

ASU

UAS

UU

ASU

UAS

UU

ASU

UP

WR

UP

WR

CPCI (9U)

UPIU

UPIU

UBIU

UAC

UU

BIUU

ACU

UP

WR

UP

WR

UA

LU

CPCI (9U)

UA

FUU

AFU

UA

SU

UA

SU

UA

SU

UA

SU

UR

CU

UR

CU

UA

SU

UA

SU

UA

SU

UA

SU

UA

SU

UA

SU

UPW

R

UPW

R

CPCI (9U)

UP

IUU

PIU

UB

IUU

AC

UU

BIU

UA

CU

UP

WR

UP

WR

UA

LUCPCI (9U)

UA

FUU

AFU

UA

SU

UA

SU

UA

SU

UA

SU

UR

CU

UR

CU

UA

SU

UA

SU

UA

SU

UA

SU

UA

SU

UA

SU

UP

WR

UP

WR

CPCI (9U)

UPIU

UPIU

UBIU

UAC

UU

BIUU

ACU

UP

WR

UP

WR

UA

LU

01020304050607080910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

0102030405060708 0910 111213141516 1819 201700

01020304050607080910 111213141516 1819 201700

PSM 0

PSM 1(optional)

PSM 2(optional)

PSM 3(optional)



2-7

2.2.2 Hardware Configurations for Huawei uBro Solution (Single-cabinet)

Figure 2-5 shows the components in the uBro single-cabinet.

Figure 2-5 Components in the uBro single-cabinet

uBro single-cabinet (46U)

Air Deflector(2U)

Disk array(3U)

PDF (3U)

PC server (USM) (2U)


06U05U04U03U02U01U



06U05U04U03U02U01U


Cable shelf(1U)IPCLK1000-0 (1U)

Cable shelf(1U)IPCLK1000-1 (1U)

Cable shelf(1U)Eudemon 1000E-0 (1U)

Cable shelf(1U)Eudemon 1000E-1 (1U)

Cable shelf(1U)S5352C-EI-0 (1U)Cable shelf(1U)

S5352C-EI-1 (1U)

KVM (1U)

M2000-0

AP M

anager-0

M2000-1(optional)

AP M

anager-1(optional)S

WU

SW

UA

HR

-0

AHR

-1(optional)A

AA-0

AA

A-1

ATAE shelf(14U)

SMM SMM

01 02 03 04 05 06 07 08 09 10 11 12 13 14

CPCI (9U)

UA

FUU

AFU

UA

FUU

AFU

UFC

UU

FCU

UR

CU

UR

CU

UO

MU

UO

MU

UA

SU

UA

SU

UG

TPU

GTP

UPW

R

UPW

R

CPCI (9U)

UP

IUU

PIU

UP

IUU

PIU

UP

IUU

PIU

UB

IUU

AC

UU

BIU

UA

CU

UFS

UU

FSU

ULA

NU

CK

I

UC

KI

UP

WR

UP

WR

UA

LU

01 02 03 04 05 06 07 08 0910 111213 14 15 16 18 19 201700

01 02 03 04 05 06 07 08 0910 111213 14 15 16 1819 201700

AG (9U)




Issue 02 (2009-08-14)

2.3 Major NEs 2.3.1 AP

The AP is the network access device in Huawei uBro solution. The AP is installed at home, in SOHOs, or in SMEs and provides UMTS access services for users.

The AP integrates the NodeB and certain functions of the radio network controller (RNC) and performs the functions of wireless modulation, wireless resources management, and power control.

To meet the requirements in different scenarios, Huawei uBro solution provides two types of AP, the UMTS Access Point 2150 (UAP2150) and ePico3801.The UAP2150 is installed at home and in SOHOs, whereas the ePico3801 is installed in SMEs.

2.3.2 AG The AG is a device on the core network of Huawei uBro solution. Huawei Serving GPRS Support Node 9810 (SGSN9810) serves as the AG in the uBro solution and performs the following functions:

Forwarding the signaling of the control plane and data packets in the user plane in the Iu interface The AG is connected to the SGSN and MSC of the UMTS through a standard Iu interface, and forwards signaling of the control plane and data packets of the user plane between the AP and the UMTS core network.

Link control and link management of the AP The AG is connected to the AP through the Enhanced Iu Interface (eIu) interface, and controls/manages the links of the AP.

2.3.3 Clock Server The clock server is in the core network of the uBro solution and provides precise clock source for the AP. Huawei IPCLK1000 serves as the clock server in the uBro solution.

The IPCLK1000 adopts the following clock over IP technologies:

The Clock over IP technology is divided into two parts, namely, Server and Client. The IPCLK1000 acts as the Server and the AP acts as the Client.

The Server obtains the clock source from the clock equipment, and then provides the synchronous reference clock to the Client (AP) through the IP network in the form of IP packets after local phase-lock and hold-in.

2.3.4 AHR The AP home register (AHR) is in the uBro core network managed by the carrier.

Huawei AHR performs the following functions:

Registering/Deregistering an AP user, and managing the subscription data Centralized management of the AP access control list AP area management. AHR system management AHR log management



2-9

2.3.5 AP manager The AP manager is located in the uBro core network. It is Huawei-developed AP management platform and manages all the APs in the network in a unified manner.

The AP manager performs the following functions:

AP configuration management AP fault management AP software management Task management Security management Log management

2.3.6 SeGW The Security Gateway (SeGW) is located in the ingress of the uBro core network. In Huawei uBro solution, the Eudemon 8080E or Eudemon 1000E serves as the SeGW.

In Huawei uBro solution (triple-cabinet), the Eudemon 8080E serves as the SeGW. In Huawei uBro solution (single-cabinet), the Eudemon 1000E serves as the SeGW.

The SeGW performs the following functions:

Providing the standard firewall to protect the NEs in the uBro core network. Providing the IP Security Protocol Virtual Private Network (IPsec VPN) function.

By establishing the IPsec VPN tunnel between the AP and the SeGW, the SeGW provides security protection for the communication between the AP and the uBro core network NE.

2.3.7 M2000 The M2000 is located in the uBro core network. The M2000 is unified wireless network management platform of Huawei. Through the platform, you can manage the AG, Clock Server, AHR, AP Manager, SeGW in a unified way. Huawei M2000 is referred to as the iManager M2000.

2.3.8 AAA The authorization, authentication and accounting (AAA) server is in the uBro core network and performs (U) SIM authentication. Huawei infoX-AAA serves as the AAA server in the uBro solution.

2.4 Technical Features As a new network, Huawei uBro solution possesses the following new technical features.

2.4.1 Automatic Network Planning And Optimizing The uBro system supports the following features about automatic network design:




Issue 02 (2009-08-14)

Automatic configuration of the frequency point in the cell. Through frequency detection, the AP selects the frequency with minimum interference as the frequency of a cell. The frequency detection range is defined in the cell frequency list of the AP.

Automatic configuration of scrambles in the cell. The AP detects scrambles to select the scramble with the minimum interference as the AP scramble.

Automatic configuration of AP neighboring cells. The AP detects the neighboring macro cells with or without the same frequency and completes the AP neighboring cell configuration automatically.

Pilot frequency power automatic adjustment When the UE calls a call number, the pilot frequency power is adjusted automatically.

2.4.2 Interference Detection After the AP cell is established, the AP can automatically detect the quality of upstream signals, indicate the quality of signals in the current location through an LED in the front panel, allowing the user to adjust the location of the AP. The uBro system supports the following interference detection attributes:

The AP supports detecting the interferences in the upstream Rx channels. The AP provides an LED to indicate the interference detection result. Through the signal

LED in the front panel, the AP can indicate the quality of signals in the current location. The AP supports configuring, modifying, and querying the interference thresholds.

2.4.3 Location Detection (Optional)

Location detection is an optional feature.

To prevent unauthorized use of the AP, the carrier needs to control the location of the AP.

The uBro system detects the location of the AP and judges whether the location of the AP is legitimate. If the location is legitimate, the uBro system allows the AP to be connected to the AG; if not, the uBro system automatically prohibits the utilization of the AP. Location detection can be implemented based on:

The neighboring cell list of the macro cell neighboring an AP Binding the location of the AP with the neighboring cell list of the macro cells neighboring the AP .When the AP is under the coverage of the macro cell, the uBro system binds the location of the AP with the neighboring cell list of the macro cells neighboring the AP. If the contents of the neighboring cell list change, it means that the location of the AP also changes.

Dynamic IP addresses If the connectivity session location and repository function (CLF) is available, you can query the port number on the CLF. Locating an AP through the CLF is used in preference.

The location detection feature is applicable to the services related to locations and emergency calls.



2-11

2.4.4 Location Indication When a UE enters the AP cell and resides there successfully, the uBro system needs to notify the UE of the Information about the current network.

The uBro system provides three modes to indicate the locations:

Through a short message − The AP can send a short message. When the UE enters the AP cell, the AP sends a

short message to the UE, notifying the user that he or she has entered the AP cell. The contents of the message can be configured and customized in the AP.

− The AP can send a flash short message to the UE for notifying the location. After the message is read, it can be deleted automatically.

− When the UE enters and exits the AP cell frequently within a short period, the AP does not send message to the UE to avoid interferences on the user.

Through a PLMN identifier The AP cell and macro cell use different public land mobile network (PLMN). When a UE resides in the AP cell, the roaming flag appears on the UE. The user of the UE knows that he has already resided in the AP. After the user leaves from the AP cell to the macro cell, the roaming mark disappears.

Through audio tone insertion (ATI)(Optional) In a CS call between UEs, the AP indicates the location by playing an announcement.

The location indication through an announcement is suitable for both the caller and the callee. Such a location indication mode, however, cannot be implemented during a handover. The location indication through an announcement is applicable to voice services only.

2.4.5 Clock Synchronization To satisfy the requirements of clock synchronization, the uBro solution supports three synchronization modes:

Synchronization through air interfaces When the AP is under the coverage of macro cells of the UMTS, the AP supports synchronizing clock through an air interface.

Synchronization through IP networks (Huawei private protocol) The AP receives IP clock packets from the clock server in the IP network for clock synchronization.

Synchronization through IEEE 1588 Version 2 (1588v2) IEEE 1588v2 is an auto-sensing network time synchronization protocol, in which the clock layering and reconstruction of the entire network can be automatically achieved through the algorithm used for selecting the source.IEEE 1588 supports both clock synchronization and frequency synchronization.The current AP only employs the frequency synchronization mode. To prevent the resources in the clock server which are obtained illegitimately, the control flow is separate from the service flow in the clock. The control flow is transmitted through the IPSec tunnel.

2.4.6 Access Control Supporting access control, the uBro system can implement access control over the UE.




Issue 02 (2009-08-14)

The uBro system supports the following access control attributes:

The access control policy is in open mode In open mode, the AP does no restrict the access of any UE.

The access control policy is in close mode In close mode, the AP only accepts the access request of an authorized UE, and rejects the access requests of unauthorized UEs (except emergency calls). The uBro system supports configuring the access control list of the AP based on the MISISDN numbers of the UEs.

The access control policy is in group mode The group mode is applicable to the SME. UEs in the access control list of the ePico not only can enjoy the services of the ePico, but also can enjoy services of other ePicos in the group. In group mode, the uBro system configures a unified access control list for the group. The unified access control list is effective to all ePicos in the group.

The access control in group mode is only for ePicos.

2.4.7 Cell Reselection The uBro system supports the following features about cell reselection:

When a UE is in standby mode, the UE can made bi-directional selection between the AP cell and macro cell, and between the AP cell and AP cell.

The AP supports the configuration of the hierarchical cell structure (HCS) parameter. It allows the UE to first reside in the AP cell by surveying the valid HCS parameter.

2.4.8 Cell Handover The uBro system supports the following cell handover attributes:

At homes and in SOHOs Supports the unidirectional hard handover from the AP cell to the neighboring macro cell.

In SMEs − Supports the bi-directional hard handover between neighboring ePico cells and the

automatic configuration of ePico wireless parameters. − Supports the unidirectional hard handover from the ePico cell to the neighboring

macro cell. − Supports the unidirectional hard handover from the macro cell to the neighboring

ePico cell.

In SMEs, the bi-directional hard handover between ePico cells, and the unidirectional hard handover from the macro cell to the neighboring ePico cell are only for ePicos.

2.4.9 HSPA The uBro system supports the following HSPA attributes:

The HSDPA service allows the maximum of downlink data rate to be 7.2 Mbit/s. The HSUPA service allows the maximum of uplink data rate to be 1.44 Mbit/s.



2-13

2.4.10 Security Authentication To prevent illegitimate access of the AP to the AG, the uBro core network needs to authenticate the AP.

The uBro core network authenticates the AP based on Internet Key Exchange version 2 (IKEv2). IKEv2 supports two authentication protocols:

Extensible Authentication Protocol - subscriber identity module (EAP-SIM). The EAP-SIM is a GSM based authentication and key negotiation mechanism.

Extensible Authentication Protocol -Authentication and Key Agreement (EAP-AKA)

2.4.11 Differential Charging (Optional) The uBro network and UMTS are the same in the logical architecture of the core network and billing system which is in compliance with 3GPP TS32.200 (R5) and TS32.240 (R6).

The differential charging is implemented based on SAI and LAC:

The SAI configuration policy refers to classifying SAIs based on UE identity. UEs with different identities correspond to different service area identifications (SAIs). Differential charging is achieved through the mapping between SAIs and charging rates in the call detail record (CDR).

The differential charging in the PS domain is implemented based on the location area code (LAC).A macro network is differentiated from an AP network by LAC. The CDRs of PS services include LACs, so the use of LACs on both the UMTS and uBro network facilitates the differential charging in the PS domain.

Users are charged in the following two ways based on their identities:

Users of the UEs with the owner, admin member, or member identity enjoy the pricing standard of HomeZone.

Users of the UEs with the guest or roaming identity enjoy the pricing standard of the macro network which the UEs cross.

2.4.12 Performance Management of the AP (Optional) The AP manager can subscribe to the performance data of APs. After the subscription, involved APs upload performance files at the end of each statistics period. The AP manager combines the performance files generated within the same period into one file and then sends it to the performance report system (PRS) for parsing and summarizing. Meanwhile, the AP manager exports the configuration data of the APs involved in the feature description and provides the data for the PRS.

As a specialized performance tool, the PRS summarizes performance data, analyzes performance statistics, exports reports, sort performance data, and analyzes interference and call drop.

The performance management of the AP consists of the following functions:

Subscribing to performance statistics, which are not reported by default Uploading performance statistics periodically to the PRS




Issue 02 (2009-08-14)

2.4.13 Double-IPSec (Optional)

The double-IPSec feature is an optional feature.

The information exchanged between the AP and the AG traverses the IP network which has security threats because of the unqualified QoS. Therefore, it is necessary to distinguish between voice streams and data streams by differentiated services code point (DSCP).

The double-IPSec feature ensures that two IPSec tunnels are set up between the AP and the SeGW.

The AP initiates two EAP authentication requests to obtain two private network addresses.

The AP labels the streams with different DSCPs based on their destination addresses. The HGW routes IP packets based on the public network address and private network

address mapped from the DSCP onto the operator network.

2.4.14 Emergency Call Service The route from the UMTS core network to the emergency call center is identified by service area identity (SAI):

The SAI which is the same as that of the macro network where the AP is located is used for routing emergency calls, thus reusing the emergency call-related resources on the current macro network as many as possible.

Or, the SAI is only used for routing emergency calls.

2.4.15 Selection of the Optimal Core Network The proximate access of the AP, namely, the AP and the surrounding macro network can be connected to the same pool or the same NE. This not only effectively reduces the cost of constructing the core network but also decreases the signaling between exchanges and switchover delay. In addition, QoS and customer satisfaction rate are improved.

To solve the problem of proximate access of the AP, the multi-CN function is introduced to the SGSN9810 V800R009C02. That is, a AG can connect to multiple CN nodes at the same time.

The AG can connect to multiple MSCs or SGSNs on the core network to ensure that:

The AP and its home macro network access the same core network. Network planning is rational.

2.4.16 AG Supporting Iu-Flex The AG can connect to multiple nodes on the core network through Iu-Flex technology. The nodes form a pool and work in redundancy mode or load sharing mode. In a pool, any node can serve the AP. If the nodes on the core network do not form a pool, only the ones saving the RNC ID can provide services for the AP.



2-15

2.4.17 End-to-End Security Solution Between the AP and the AP Manager (Optional)

End-to-end security solution between the AP and the AP Manager is ensured in the following ways:

Security of the transmission of File Transfer Protocol (FTP) is adopted to ensure the security of the files transmitted between the AP and the AP manager.

TR069 over Secure Sockets Layer (SSL) is adopted to ensure the security of the management signaling between the AP and the AP manager. − SSL and the Transport Layer Security (TLS) are adopted to ensure the security of the

data transmitted between the AP and the AP manager. − The AP manager can be configured as the Secure HTTP (HTTPS) server and the AP

the HTTPS client. If HTTPS is configured as the access mode on the universal resource locator (URL) of the AP manager, the AP must support HTTPS connections.

− The AP manager is configured with the auto-signature public key certificate and private key to support TLS Rivest, Shamir, Adleman (RSA) series algorithms.

2.4.18 Flow Control of the IMSI Query Requests The AHR supports the flow control of international mobile subscriber identity (IMSI) query requests.

If the flow of IMSI query requests reaches a threshold, the AHR discards the requests from the AP configured with the access control policy in close mode.

If the flow of IMSI query requests reaches a threshold, the AHR discards the requests from the AP configured with the access control policy in group mode.

2.4.19 Dynamic Jitter Prevention Typically, the transmission quality at the air interface cannot be ensured because comparatively serious jitter occurs in the transmission of data packets. Quality of the end-to-end data transmission in CS services must be protected from packet loss, delay, and jitter. The AP provides the following measures to prevent jitters dynamically:

The AP caches the received data packets and determines the synchronization between the time stamp in the packets and the time at the air interface, and then sends data based on the synchronization.

Clock synchronization is determined based on the first data packet. The cached data packets are sent through the air interface after a fixed interval.

If no packets are lost within a time period and the data packets are cached in the AP for a long time, the interval before sending out the cached data packets through the air interface can be reduced.

If data packets are discarded because they reach the AP late, the interval before sending out the cached data packets through the air interface can be extended.

2.4.20 Compensation for Packet Loss in Voice Services If the bearer network cannot guarantee the QoS of the voice services of the AP, it determines whether to start Realtime Transport Protocol (RTP) redundancy compensation based on the loss condition of the packets in uplink and downlink directions dynamically detected by the AP and AG.




Issue 02 (2009-08-14)

Redundancy compensation helps to improve the condition of packet loss in data services when the network status is not good.

2.4.21 Alarm for the Disconnection of AP (Optional) In the enterprise scenario, if the AP is disconnected from the AG because of the failure of power or the bearer network, the network side detects the disconnection and raises an alarm, and then reports the alarm to the M2000 through the AG.

In view of the large number of APs, the network side can only detect certain APs. On the AP manager, users can set which APs need to be detected by the AG for the report of disconnection alarms.

2.4.22 Daylight Saving Time The absolute time synchronously obtained by the AP from the NTP server does not contain the time zone and daylight saving time (DST) rule. The time zone and daylight saving time rule of the AP can be configured on the AP manager. Considering the huge number of APs, the time zone and DST rule are configured as area parameters.

2.4.23 Allocation of Cell IDs Cell IDs can be configured on the AP manager automatically or manually and can be configured as SACs. The range of the cell IDs configured under each RNC ID can also be set on the AP manager.

2.4.24 AP Type APs are classified into two types, home AP and ePico. Users can view the type of an AP on the AP manager. The user manages APs differentially based on their types.

2.4.25 AP Name An AP is assigned AP name, also called node ID. The name information is contained in the alarm sent through the northbound interface.

Being regarded as a user attribute, an AP name is bound to the appropriate AP user and corresponds to the SIM card in the AP. If a user only changes the AP but does not change the SIM card, the AP name does not change.

2.4.26 Separation of OM and Service (Optional) The AP sets up two IPSec tunnels, one for the OM service and the other for the other services. The AP manager supports two virtual local area networks (VLANs), one for the communication with the AP and the other for the communication with the AHR.

The single-cabinet solution does not support the separation of OM and service feature.



2-17

2.5 System Interface 2.5.1 Overview of Interfaces

Figure 2-6 shows the interfaces in Huawei uBro solution.

Figure 2-6 Interfaces in the uBro solution

Public Network

Clock Server

UE

Ho

Ae

AP Manager

SeGW eIu/Ab

Ac

Uu AP

AHR

AG

Hb/Hg

AAA

BOSS

(U)SIM

Iu CN

D’

RADIUSDiameter

HLR

AP access point AG access gateway UE user equipment HLR home location register SeGW security gateway AHR AP home register AAA authorization, authentication and accounting server CN core network BOSS business and operation support system

2.5.2 eIu Interface The eIu interface is defined by Huawei and adopted between the AP and AG. The eIu interface exchanges the control plane signaling and user plane data between the AP and AG.

Figure 2-7 shows the structure of the protocol stack of the eIu interface.

Figure 2-7 Protocol stack of the eIu interface

RANAP APM

Control plane

Data

PS user plane

GTP-U

UDP

IP

IuUP

CS user plane

RTP

IP

SPUA

SCTP

IP

UDP

RANAP Radio Access Network Application Part




Issue 02 (2009-08-14)

APM AP Management Private Protocol SPUA SCTP Private User Adaptation Layer SCTP Stream Control Transmission Protocol IuUP Iu user plane RTP Real Time Protocol UDP User Datagram Protocol IP Internet Protocol GTP-U GPRS Tunneling Protocol for User Plane

Protocols on the Control Plane The protocols adopted by the control plane are shown as follows:

RANAP The Radio Access Network Application Part (RANAP) implements the signaling exchange between the CN and the RNC for the Iu-CS interface.

APM The AP Management Private Protocol (APM) is a private protocol defined by Huawei. It aims to provide AP management function such as link management and AP authentication.

SPUA The SCTP Private User Adaptation Layer (SPUA) is between the SCTP and RANAP: to replace the functions of MTP3 User Adaptation layer (M3UA) and of Signaling Connection Control Part (SCCP).

SCTP The Stream Control Transmission Protocol (SCTP) is a reliable transmission protocol oriented to connection and based on packets. It is used to transport the Signaling System Number 7 (SS7) over the IP network.

Protocols on the CS User Plane The protocols on the CS user plane are shown as follows:

UDP The User Datagram Protocol (UDP) is a connectionless transmission layer protocol. It provides connectionless transmission function for the upper layer protocol.

RTP The Real Time Protocol (RTP) provides E2E real-time transmission for media stream such as voice and video.

IuUP The Iu User Plane (IuUP) is a wireless network user plane protocol of the Iu interface, and is intended to transmit user plane data related to the Radio Access Bearers (RAB). The IuUP is borne over the RTP layer to ensure real-time transmission of voice.

Protocols on the PS User Plane The GPRS Tunneling Protocol for User Plane (GTP-U) transmits PS domain data packet directly. The GTP-U protocol uses the GTP tunnel ID to identify the user services.



2-19

2.5.3 Ab Interface The Ab interface is between the AP and the AG. When the AP is powered on for the first time and initiates the BOOT flow, the AP communicates with the AG through the Ab interface, and acquires the AP initialization configuration data, including wireless network parameters and the IP address list of uBro core network.

Figure 2-8 shows the protocol stack at the Ab interface.

Figure 2-8 Protocol stack at the Ab interface

Application

IP

UDP

The Ae interface supports the following protocols:

UDP IP

2.5.4 Ae Interface The Ae interface is between the AP and the AP manager. The AP manager manages the APs through the Ae interface. The Ae interface complies with the TR069 protocol.

AP Manager V100R002C02 and later versions support the TR069 over Security Socket Layer (TR069 over SSL) protocol stack to ensure the security of management signaling between the AP and the AP manager. In the TR069 over SSL protocol stack, the Secure HTTP (HTTPS) protocol is used.

Figure 2-9 shows the protocol stack at the Ae interface.

Figure 2-9 Protocol stack at the Ae interface

SOAP

IP

TCP

RPC Mothods

Application

HTTP

The Ae interface supports the following protocols:




Issue 02 (2009-08-14)

Remote Procedure Call (RPC) Methods Simple Object Access Protocol (SOAP) Hyper Text Transport Protocol (HTTP) Transport Control Protocol (TCP) IP

2.5.5 Hb Interface The Hb interface is between the AG and the AHR. When the AP is powered on and initiates the BOOT flow, the AG communicates with the AHR through the Hb interface, and acquires the AP initialization configuration data.

Figure 2-10 shows the protocol stack at the Hb interface.

Figure 2-10 Protocol stack at the Hb interface

Application

IP

UDP

The Hb interface supports the following protocols:

UDP IP

2.5.6 Hg Interface The Hg interface is between the AG and the AHR.

The Hg interface performs the following functions:

When the AP is registered in the AHR or the AP user modifies the user's service information through the AHR, the AHR sends service attribute parameters to the AG through the Hg interface.

The AHR provides the AP location detection function for the AG through the Hg interface.

Figure 2-11 shows the protocol stack at the Hg interface.

Figure 2-11 Protocol stack at the Hg interface

Application

IP

UDP

The Hg interface supports the following protocols:



2-21

UDP IP

2.5.7 Ho Interface The Ho interface is between the AHR and the AP manager.

When adding, modifying, or deleting the Information about the group of the AP, the AHR sends the changed group information to the AP manager through the Ho interface to guarantee the group information consistency between the AHR and the AP manager.

Figure 2-12 shows the protocol stack at the Ho interface.

Figure 2-12 Protocol stack at the Ho interface

SOAP

IP

TCP

Application

HTTP

The Ho interface supports the following protocols:

SOAP HTTP TCP IP

2.5.8 Ac Interface The Ac interface is between the AP and the clock server. The AP communicates with the clock server through the Ac interface to synchronize the clock.

Figure 2-13 shows the protocol stack at the Ac interface.

Figure 2-13 Protocol stack at the Ac interface

Application

IP

UDP

The Ac interface supports the following protocols:




Issue 02 (2009-08-14)

UDP IP

2.5.9 RADIUS Interface The Remote Authentication Dial In User Service (RADIUS) interface is between the SeGW and the AAA. RADIUS adopts UDP as the transmission protocol.

2.5.10 D' Interface D' interface complies with the 3GPP TS29.078 Standards, and adopts the Mobile Application Part (MAP) protocol.

D' interface is an optional interface of Huawei uBro solution. If the carrier's HLR supports D' interface, Huawei uBro solution supports D' interface between the AAA and the carrier's HLR.

When the AP initiates a (U) SIM card based authentication request to the AAA, the AAA acquires the authentication data of the (U) SIM card from the HLR through D' interface.

2.5.11 Diameter Interface The Diameter protocols comply with standards of the next-generation AAA protocol. The Diameter protocols include the basic protocol, Network Access Server (NAS) protocol, Extensible Authentication Protocol (EAP), Mobile IP (MIP) protocol, and Code Message Syntax (CMS) protocol.

The Diameter protocol is the optional interface of Huawei uBro solution. When the carrier's HLR does not support the D' interface, Huawei uBro solution supports the Diameter interface between the AAA and the AHR.

When the AP initiates a (U) SIM card based authentication request to the AAA, the AAA acquires the authentication data of the (U) SIM card from the AHR through Diameter interface.

A network can select either the D' interface or the Diameter interface. But the two interfaces cannot coexist in a network simultaneously.

2.5.12 Uu Interface The standard Uu interface is between the UE and AP. The Uu interface complies with the standards of 3GPP Release 6, and supports terminals of standards R99, R4, R5 and R6.

2.5.13 Iu Interface The Iu interface is between the AG and the UMTS core network. The Iu interface complies with standards of 3GPP Release 6 and supports bearing over ATM. An increasing number of core network devices are based on IP addresses and the Iu interface is also over IP.

The Iu interfaces of SGSN9810 V800R009C02 and later versions are over IP. Iu over IP is an optional feature. The single-cabinet solution does not support the Iu over IP feature.

uBro Solution Description 3 Networking Solution


3-1

3 Networking Solution

About Thi

T he contents o

s Chapter

he following table lists t f this chapter.

Section Describes

3.1 Service Networking The service networking solutions of Huawei uBro solution.

3.2 Access Networking AP access networking of Huawei uBro solution.

3.3 Clock Server Deployment Scheme

Deployment of the clock server in the uBro solution.

3 Networking Solution uBro



Issue 02 (2009-08-14)

3.1 Service Networking

Networking Architecture Figure 3-1 shows the AG networking architecture.

Figure 3-1 AG networking architecture

AP

GGSN

AG

Gn

eIuCSIu-CS

Iu-PS

SGSN

In this solution, the AG provides the following functions:

Provides the eIu interface to connect with the AP, thus controlling and managing the AP. Provides the standard Iu interface to connect with the UMTS core network, thus

converging and forwarding the service data and control data of the AP.

Networking Principles In the UMTS, the CN is divided into the CS domain and PS domain. The uBro network services are therefore divided into the CS domain services and PS domain services.

The traditional CS domain service, such as voice services, complies with the following principles:

The AP encapsulates service data into IuUP packets and sends the packets to the AG through the eIu interface in IP bearer mode.

The AG does not process the data, sends the service data to the CS domain of the CN through the standard Iu-CS interface.

For the PS domain services, the realization principles are the same as those in the traditional UMTS.

Networking Features The networking scheme can be implemented easily, without too many changes to the network equipment in the UMTS network. The AG adopts the standard Lu interface for connecting with the UMTS core network. The interoperability test for other interfaces is not required.



3-3

3.2 Access Networking Access networking refers to the networking mode adopted by the AP for accessing the uBro core network.

3.2.1 xDSL Access Networking In the Home and SOHO application scenarios, the x Digital Subscriber Line (xDSL) broadband access is adopted extensively. The access networking scheme of Huawei uBro solution supports the xDSL access.

Figure 3-2 shows the xDSL access networking architecture.

Figure 3-2 xDSL access networking architecture

AP

IPsec tunnel

xDSL

AHR

AG

uBro core network

RouterBRASDSLAM

Public IP network

SeGW

AAA

BRAS broadband access server xDSL x digital subscriber line DSLAM digital subscriber line access multiplexer

Networking Principles In the Home and SOHO application scenarios, the AP connects to the public IP network through multi-channel xDSL. The Digital Subscriber Line Access Multiplexer (DSLAM) converges and distributes data, and isolates other AP users through the dedicated VLAN. The AP service is transmitted to the broadband access server (BRAS) through the point to point protocol over Ethernet (PPPoE) or dynamic host configuration protocol (DHCP) to complete the access authentication and charging of the public IP network.

After passing the BRAS authentication, the AP service is sent to the SeGW (ingress equipment) of the uBro core network through the public network. The SeGW processes the data and forwards the data to the AG and AAA, thus finishing the authentication of the mobile service.

Networking Features The xDSL access networking solution possesses the following features:

Uses rich home broadband resources. The AP, as an online user of the xDSL, does not require a private transmission network.

Allocates PVCs to the AP services to isolate them from other services and ensure the QoS of the AP services.

Adopts the IPsec transmission scheme to ensure transmission security.




Issue 02 (2009-08-14)

Because the AP service data must pass the public IP network with security loophole, the IPsec transmission scheme establishes IPsec security channels between the AP and the SeGW to ensure the secure communication between the AP and the NE in the uBro core network.

The IPsec ensures the security of data transmission by adding new fields to the headers of the IP data packets. In tunneling mode, the whole IP packet is used to calculate the ESP header. The whole IP packet is encrypted and encapsulated in a new IP packet with the ESP header. When data is transmitted over the Internet, the real original address and destination address are hidden.

3.2.2 Ethernet Access Networking In the Small and Medium Enterprise (SME) application scenario, the enterprise LAN is used for connecting to the public IP network. Huawei uBro solution supports the Ethernet access network.

Figure 3-3 shows the Ethernet access networking architecture.

Figure 3-3 Ethernet access networking architecture

ePico SeGWSwitch

Public IP Network

AHR

AG

uBro Core Network

Router Router

AAA

VPN

VPN virtual private network

Networking Principles In the Ethernet access networking solution, the ePico is connected to the public IP network through the enterprise LAN and is separated from other users through a private VLAN. The ePico services are transmitted over the public IP network to the ingress equipment SeGW of the uBro core network. The SeGW processes the data, forwards the data to the AG and the AAA, and authenticates mobile services.

Networking Features The Ethernet access networking solution possesses the following features:

The Ethernet access networking solution allocates private VLAN and MPLS DiffServ/TE mode to the ePico service to ensure the QoS of the uBro services.

The Ethernet access networking solution uses E2E to ensure transmission security.



3-5

3.3 Clock Server Deployment Scheme In Huawei uBro solution, the clock server adopts multicast to implement AP clock synchronization. The clock server can be deployed in any of the following locations of the uBro network:

uBro core network Access network Backbone network

Generally, the clock server can be deployed in uBro core network.

3.3.1 Networking with the Clock Server Deployed in the uBro Core Network

Figure 3-4 shows the networking architecture with the clock server deployed in the uBro core network.

Figure 3-4 Networking architecture with the clock server deployed in the uBro core network

User Network

AP HGW

ePico

ePico

uBro Core NetworkBearer Network

LANSeGW

AG

AHR

AP Manager

M2000

Clock Server

AAA

DSLAM

Access Network Backbone Network

Switch Router Router

BRASIP NetworkIP Network

Router Router

The requirements of this networking on the bearer network are as follows:

The backbone network and the access network support the multicast function. The backbone network supports the QoS of the differential service model, such as

802.1P and Multi-Protocol Label Switch (MPLS) The access network must support VLAN isolation.

The networking scheme is characterized by centralized deployment of the clock server, easy maintenance and management, and larger multicast delay and jittering.

3.3.2 Networking with the Clock Server Deployed in the Backbone Network

Figure 3-5 shows the networking architecture with the clock server deployed in the backbone network.




Issue 02 (2009-08-14)

Figure 3-5 Networking architecture with the clock server deployed in the backbone network

User Network

AP HGW

ePico

ePico


LANSeGW

AG

AHR

AP Manager

M2000

AAA

DSLAM



BRASIP Network

Clock ServerClock Server

IP NetworkRouter Router

The clock server is connected to the convergence layer router or the core layer router in the backbone network.

The networking scheme requires that the access network supports multicast function.

The networking scheme is characterized by centralized deployment of the clock server and easy maintenance and management.

3.3.3 Networking with the Clock Server Deployed in the Access Network

Figure 3-6 shows the networking architecture with the clock server deployed in the access network.

Figure 3-6 Networking architecture with the clock server deployed in the access network

User Network

AP HGW

ePico

ePico


LAN

SeGW

AG

AHR

AP Manager

M2000

AAA

DSLAM



BRAS

IP Network



IP Network

Router Router



3-7

Clock Server Connecting to the BRAS or Router There are too many users connecting to the BRAS and the router, the clock server can be connected to the BRAS or the router. The networking scheme is unsuitable to the scenario where only few users are connected to the BRAS and the router.

The networking scheme requires that the BRAS and the router support the multicast function.

The networking scheme is characterized by spare distribution of many clock servers, and inconvenience in centralized maintenance and management.

Clock Server Connecting to the DSLAM When there are too many access users under the DSLAM and the capacity of the DSLAM is very large, the clock server can be connected to the DSLAM. The networking scheme is unsuitable to the scenario where only few users are connected to the BRAS and the router, or the capacity of the DSLAM is very small.

The networking scheme requires that the DSLAM supports the multicast function.

The networking scheme is characterized by spare distribution of many clock servers, and inconvenience in centralized maintenance and management.

uBro Solution Description 4 Security Solution


4-1

4 Security Solution

About Thi

T tents

s Chapter

he following table lists the con of this chapter.

Section Describes

4.1 Overview of the Security icies and their classification of the uBro Solution

Security polsolution.

4.2 Network Equipment Security icies for the AP and core NEs in the uBro Security polsolution.

4.3 Network Security Security policies and technologies of the uBro solution.

4.4 O&M Security OM security policies of the uBro solution.

4 Security Solution uBro



Issue 02 (2009-08-14)

4.1 Overview of the Security Solution The following describes the security policies of Huawei uBro solution:

Robust security protection Multiple security protection lines have been established for the key equipment in the uBro network. When one security defense line collapses, the left ones can still protect the security of the uBro network.

Minimum authorization The AP user, O&M engineer or the NE service/process are only entitled to the minimum rights, bandwidth, and network resources necessary to the implementation of normal functions. Unnecessary network services are prohibited to reduce security risks.

Active defense The uBro solution incorporates security design. You do not have to take remedies after occurrence of accidents.

Fuse mechanism The fuse mechanism should be adopted at the locations of the network that are vulnerable to attacks. Before the attacks can damage the security of network and the user, the system automatically disconnects the malicious user from the network, or reduces the bandwidth and QoS of the connection so that the damages can be minimized.

The security problems of Huawei uBro solution involve:

Network equipment security Network security Operation and maintenance security

4.2 Network Equipment Security Network equipment security refers to the following security measures provided by NEs:

AP equipment security − In local and remote maintenance of the AP, the AP supports password based access

authentication. − The AP supports the access control list to control the access of UEs and prevent

unauthorized access. CN equipment security

− Password based access authentication in remote maintenance − Reinforcement of the operating system − Patch management − Abnormality detection − Virus prevention − Sensitive data encryption



4-3

4.3 Network Security The uBro solution extends the UMTS network to the house of the user through the public IP network. How to ensure the network security, especially security of the mobile core network, is the most critical problem facing the uBro solution.

4.3.1 Security Domain Partition To ensure the network security, the uBro solution divides a network into the following security domains:

Non-trusted domain − Home network domain and enterprise LAN domain − Public network domain

Trusted domain − uBro CN domain − UMTS mobile CN domain

4.3.2 Border Protection The firewall is deployed between various security domains, especially the border between the uBro core network and the public IP network.

The security prevention policies of the firewall are shown as follows:

Attack prevention policy ACL policy and data packet filtering policy Network Address Translation (NAT) Dual gateway policy

4.3.3 Network Anti-Attack Through the deployment of firewalls and proper security configuration, the uBro core network can prevent the following network attacks:

Anti-DoS attack Anti-scan network attack Anti-malformation message attack

4.3.4 Network Access Authentication Network access authentication refers to identifying the equipment that accesses the network to achieve the following aims:

Preventing the access of the unauthorized AP Preventing the attackers pretending as the legitimate users from accessing the network

In the uBro network, there are two types of access authentication:

Broadband access authentication The AP accesses the broadband network through an ADSL device, and receives the authentication of the public IP network. The access authentication supports DHCP and PPPoE authentication protocols.

4 Security Solution uBro



Issue 02 (2009-08-14)

uBro core network access authentication After passing the broadband access authentication, the AP receives the authentication of the uBro core network through IPsec or DHCP protocol. In authentication mode, the AAA adopts IKEV2 (EAP-SIM and EAP-AKA) for authenticating the AP.

4.3.5 Transmission Security In a bearer network, transmission security is to prevent the signaling in control plane and data in user plane from being thieved, forged, or destructed during the transmission process.

The uBro solution provides the following features about transmission security:

Supporting E2E VLAN or Multi-Protocol Label Switching VPN (MPLS VPN) to implement isolation between AP users and isolating AP services from non-AP services by allocating PVCs and VLANs in the access network.

Supporting the access control list to define the protected data flow. Packets defined in the access control list are protected; and pickets rejected by the access control list are not protected.

Supporting IPsec The uBro solution establishes IPsec security tunnels between the AP and the SeGW to protect the specified data streams. In this way, the solution ensures the transmission safety of the bearer network. The IPsec tunnel provides the following security attributes: − Data confidentiality. − Data integrity − Anti-replay

Supporting the Internet Key Exchange protocol (IKE). − The IKE provides safety bidirectional authentication. − The IKE supports the NAT detection and NAT traversal.

Supporting the Encapsulating Security Payload (ESP) protocol. − The ESP can encrypt the IP packets. − ESP authenticates the integrity of IP packets to judge whether the packets are

corrupted during transmission. − The ESP supports NAT traversal.

4.4 O&M Security The O&M security refers to the security of network management, and its security policies are shown as follows:

Integrated NE management − The AP manager manages APs in the network. − The M2000 manages the NEs in the uBro core network.

Centralized account and rights management The following measures are taken to protect the security of OM accounts: − All accounts of NE administrators are created and managed by the NM system (NMS)

in a centralized manner.



4-5

− All account information is stored in the network management (NM) system. Integrated log management

− The NMS can collect and filter log information of every NE. − The NMS supports viewing logs, collecting statistics, and analyzing data. − The NMS stores and backs up logs in a centralized manner.

uBro Solution Description 5 QoS Policies


5-1

5 QoS Policies

About Thi

T conte

s Chapter

he following table lists the nts of this chapter.

Section Describes

5.1 General QoS Policies The general QoS policies of the uBro solution.

5.2 QoS Policies of the AP nterface for ensuring the Air Interface

Algorithm adopted by the AP air iQoS of the network.

5.3 Transmission QoS Scheme

adopted by the transmission network for ensuring the QoS of the network. Algorithm

5.4 AG QoS Scheme Algorithm adopted by the AG for ensuring the QoS of the network.

5 QoS Policies uBro



Issue 02 (2009-08-14)

5.1 General QoS Policies Huawei uBro solution supports the following general QoS policies:

The AP user has precedence over non-AP user in using AP resources. The mobile service has precedence over fixed network service in using transmission

resources. The real-time service and voice service have precedence over non-real-time service and

data service in using AP resources. The Best-Effort (BE) service is available to the non-real-time service.

5.2 QoS Policies of the AP Air Interface Many users and services compete for the AP air interfaces. In the uBro solution, the following factors affect the air interface resources allocated to user services:

Channel elements (CE) resources restriction Code resources restriction User resources restriction

To achieve the optimum QoS effect for user services, the AP air interface QoS policies solve the resources restriction problem through the following algorithms:

QoS assurance algorithm at resources congestion QoS assurance algorithm for the service quality and link quality

5.2.1 QoS Assurance Algorithm at Resources Congestion This QoS algorithm is used to increase the number of access users and ensure the QoS of the access users in the case of congestion of the CE resources, code resources, and transmission resources.

Priority Management Algorithm The main purpose of the priority management algorithm is to increase the access users for the AP and ensure the QoS of these access users in the case of limited resources.

Two types of priority are described as follows:

Priority of the UEs The user priority can be graded into two levels: priority of AP users and priority of non-AP users. The priority of AP users is the highest priority; the priority of non-AP users is the lower priority.

Priority of a service The priority of the service can be divided into Traffic Class (TC) priority and Allocation Retention Priority (ARP). The carrier can configure the related parameters in the AP to define the priority of a service.



5-3

Intelligent Access Algorithm The purpose of intelligent access algorithm is to reduce rejected access requests so that more UEs can access the network of the AP.

The intelligent access algorithm involves the following two functions:

Resource preemption When the CE resources are limited, a UE is allowed to preempt a part of CE resources of other UEs with lower priority. The UEs of lower priority can release the CE resources by downspeeding the PS services.

Preemption function of emergent call service When the CE resources and the user resources are limited, the emergent call services are allowed to preempt resources of services with lower priority. The AP releases resources of the services with lower priority.

Payload Reforming Algorithm Some preemption algorithm may lead to the increase in the access delay of CS service users and affect the service experience of the UEs. The payload reforming algorithm can reduce the access delay of the CS service users by reserving CE resources.

When the CE resources of the AP are preempted by the UEs, the AP reduces the speed of the PS service of the UEs through the payload reforming algorithm. In this way, the AP can reserve resources.

5.2.2 QoS Assurance Algorithm of Traffic Volume and Link Quality

The QoS assurance algorithm of the traffic volume and link quality is intended to keep the services uninterrupted and intact when the wireless links deteriorate.

In the AP, the wireless link QoS assurance algorithm mainly includes the following two algorithms:

The traffic volume based dynamic channel configuration control (DCCC) algorithm Link quality based DCCC algorithm

The DCCC algorithm involves:

Upward adjusting the speed of the upstream link Downward adjusting the speed of the upstream link Upward adjusting the speed of the downstream link Downward adjusting the speed of the downstream link

Traffic Volume Based DCCC Algorithm When the UE intends to send a service of a large quantity, the AP increases the bandwidth allocated to the UE to ensure that the UE can enjoy high-speed service.

If the bandwidth allocated to the UE is very high but the actual service volume of the UE is very small or zero, the AP releases the resources occupied by the UE by reducing the bandwidth allocated to the UE, and ensure that other UEs have enough resources, thus guaranteeing the QoS of other users.

5 QoS Policies uBro



Issue 02 (2009-08-14)

Link Quality Based DCCC Algorithm Provided that the UE intends to send services, if the link quality is very poor, the AP can adjust the bandwidth of the UE to avoid interruption of the service of the UE.

5.3 Transmission QoS Scheme In the uBro network, the services between the AP and the AG are transmitted over xDSL line and Ethernet. The AP shares the transmission bandwidth with other NEs. The AP services compete with non-AP services for bandwidth; the Real Time (RT) services compete with Non-Real Time services for bandwidth.

The transmission QoS scheme satisfies the QoS requirements of the UE through the following algorithms:

Congestion detection algorithm Multiplexing and header compression of the transmission packets Transmission resources based access control algorithm Blind handover

5.3.1 Congestion Detection Algorithm The congestion detection algorithm is based on the mechanism of detecting packet loss and time delay, and requires that every data packet contains a serial number and time stamp.

In the current uBro network, the Iu-CS adopts the RTP protocol, and the data packet contains serial number and time stamp. The Iu-PS adopts the GTP-U protocol, and the data packet contains the serial number but does not provide time stamp information. Therefore, the congestion detection based on delay cannot be implemented. Only the CS service can implement the time delay based congestion detection.

The CS service congestion detection involves:

Upstream detection The congestion detection is implemented in the AG. The AG first detects the delay in the upstream. If the delay is higher than the threshold, it indicates that congestion occurs in the network. The AG first transmits data packets of services with higher priority, and discards data packets of services with lower priority.

Downstream detection The congestion detection is implemented in the AP. The AP first detects the delay in the downstream. If the delay is higher than the threshold, it indicates that congestion occurs in the network. The AP first transmits data packets of services with higher priority, and discards data packets of services with lower priority.

5.3.2 Transmission Packet Multiplexing and Header Compression To implement the transmission packet multiplexing and header compression, the AP and the AG must support User Datagram Protocol (UDP) port multiplexing and Real-time Transfer Protocol (RTP) header compression. Through the UDP port multiplexing and RTP header compression, the AP and the AG can improve the data transmission efficiency and alleviate congestion in the transmission channel.



5-5

5.3.3 Transmission Resources Based Access Algorithm When detecting transmission congestion, the AP first uses the partial preemption algorithm to ensure the AP transmission QoS.

In the implementation of the partial preemption algorithm, the AP allows a UE sustaining access failure to preempt partial resources of other UEs with lower priority. The UEs with lower priorities release the occupied resources by reducing the speed of the PS service.

5.3.4 Blind Handover If the congestion detection algorithm, the transmission packet multiplexing and header compression, and the transmission resources based access algorithm fail to solve the transmission congestion problem, the system can switch the PS user who is in conversion and has lower priority to a macro cell, and release the transmission resources of the PS user so that a user with higher priority can access the CS service.

There are two types of blind handover:

NRT service blink handover Provided that the NRT service of an online UE has already occupied all transmission resources; a new UE intends to access the RT service, but the partial preemption algorithm and packet multiplexing algorithm fail to satisfy the resource requirement of the RT service access. At the moment, the AP switches the online NRT service to the macro cell to release the transmission resources for the RT service and ensure the QoS of the RT service.

BE service blind handover When the BE services of the UE has occupied a large quantity of transmission resources, the RT service of the online UE suffers from larger delay and packet loss. According to the service priority policy, the AP switches the BE service to a macro cell to release the transmission resources for the RT service and ensure the QoS of the RT service.

5.4 AG QoS Scheme 5.4.1 AG Access Control

When the UE activates the Packet Data Protocol (PDP) context, the AG needs to negotiate with the UE in respect to the service QoS.

In the case of resources (session count, bandwidth, CPU occupancy, and bearer link count) congestion, the AG rejects the access of new users.

5.4.2 QoS Queue Management The AG allocates data packets of UEs to the QoS queues based on the QoS type. The AG adopts Class-based WFQ (CBWFQ) algorithm for queue scheduling and determines the sequence of transmitting the data packets.

When congestion occurs in a queue, the AG uses the Weighted Random Early Detection (WRED) algorithm to specify the rule of discarding the data packets and ensure the reliable transmission of data with higher priority.

5 QoS Policies uBro



Issue 02 (2009-08-14)

5.4.3 DiffServ Function The AG supports the Differential Service (DiffServ) function. The DiffServ is a QoS model that is suitable to a backbone network and can satisfy various service requirements. In the implementation of the DiffServ, a network node can specify the Per-Hop Behavior (PHB) according to the differentiated services code point (DSCP) in the packet header.

The AG supports the following PHBs:

Network control (NC) Expedited forwarding (EF) Assured forwarding (AF) Best-effort (BE)

Besides, the AG supports 3 discarding priorities of the AF.

5.4.4 QoS Mapping Function The AG supports the following QoS mappings:

Mapping between 3GPP QoS and DSCP Mapping between DSCP and ATM QoS Mapping between R97/98 and R99 QoS

5.4.5 Traffic Regulating If the traffic of a UE exceeds that defined in the actually-applied QoS, the AG regulates the data packets through the following measures:

Discarding extra data packets Degrading the QoS of the data packets

5.4.6 Prevention of Time Delay and Jittering In the case of CS voice service, the AG alleviates time delay and jittering through the following measures:

Buffering the initial data packets Buffering data packets of a certain period

uBro Solution Description 6 Operation and Maintenance


6-1

6 Operation and Maintenance

About Thi

T lists the conten

s Chapter

he following table ts of this chapter.

Section Describes

6.1 O&M System he O&M system and operation and Architecture of tmaintenance schemes.

6.2 O&M System of the AP Maintenance tools of the O&M system of the AP and their functions.

6.3 O&M System of Central Office Equipment

O&M System of Central Office Equipment and their functions.

6 Operation and Maintenance uBro



Issue 02 (2009-08-14)

6.1 O&M System This section describes the O&M system of Huawei uBro solution.

Figure 6-1shows the architecture of the O&M system of the uBro solution.

Figure 6-1 Architecture of the O&M system

AP ManagerGUI&Toolkit

Terminal management

Central office equipment management

AP ManagerServer

SeGW

AP

AHR

M2000 GUI

M2000 Server

AHR AG ClockServer SeGW LMT/

Toolkit AP

WebUI AAA

BOSS/AHR Client

In Figure 6-1 the O&M system of the uBro solution is divided into two parts:

Terminal equipment management Central office equipment management

6.1.1 Solution to Terminal Equipment Management In the uBro solution, the terminal is AP. The following describes the maintenance mode of the AP:

Remote maintenance The carrier locates and removes faults for the AP through the AP manager to reduce and omit onsite supports.

Passive maintenance The AP user first reports the faults to the carrier and the carrier then solves the problems. The maintenance engineers of the carrier do not collect maintenance data from the AP.

6.1.2 Solution to Central Office Equipment Management The central office equipments are managed by the M2000 remotely and managed by the LMT/Toolkit locally. For detailed Information about maintenance function, see 6.3 O&M System of Central Office Equipment.



6-3

6.2 O&M System of the AP The OMS of the AP consists of two parts:

AP manager AP WebUI

6.2.1 AP Manager The AP manager, as the centralized NMS of the AP, is a Web-based maintenance system.

The AP manager has considered the requirements of the carriers for AP operation and AP maintenance. It provides the following powerful AP operation & maintenance functions:

Configuration management Software management Task management Fault management

Configuration Management The AP Manger supports the following AP configuration & management function:

The AP Manger supports configuring the AP individually or in batches. When a parameter is applicable to a single AP, configure the parameter for the AP individually. When a parameter is applicable to many APs, configure the parameter for these APs in batches.

The AP manager supports configuring local parameters. After a local parameter is configured, the value of the parameter is applicable to all APs of the local area.

The AP manager supports configuring AP parameters automatically. At power-on, the AP is allowed to download configuration data from the AP manager automatically. If the AP is not powered on when the AP manager configures AP parameters, you can create a configuration task in the AP manager. Once the AP is powered on, the configuration task can be executed automatically. When the configuration parameters of the AP change, the AP automatically reports the changes to the AP manager.

Software Management The AP manager supports the following AP software management functions:

The AP manager supports uploading the AP software to the AP Manger for centralized storage and management of AP software of several versions.

The AP manager supports upgrading AP software individually or in batches. − The AP manager supports upgrading AP software manually or through a task. − The AP manager supports upgrading AP software by area and version in batches.




Issue 02 (2009-08-14)

− If the AP is not powered on when the AP manager upgrades AP parameters, you can create a upgrade task in the AP manager. Once the AP is powered on, the configuration task can be executed automatically.

The AP manager supports browsing AP software version information. The AP manager supports deleting the AP software.

Task Management The AP manager supports configuring and upgrading the AP on task basis so that the carrier can arrange the task execution time flexibly.

You can create, modify, delete, copy, implement, suspend and resume a task.

The AP manager supports the following AP task management functions:

When creating a configuration task, you can specify the triggering conditions and target AP cluster.

When creating an upgrade task, you can specify the triggering conditions, target AP cluster, and target version.

You can view the detailed information of a task, including the task name, task status, task type, and task creator.

You can execute a task manually or specify a time for automatic execution.

Fault Management The AP manager supports the following AP fault management functions:

The AP Manger supports querying the status of the AP. The status of the AP includes normal, warning, minor, critical, and emergency.

The AP Manger supports querying the AP status in batches. The AP Manger supports collecting statistics on APs by area, software version, or status, and displaying the statistics in table, histogram, and pie chart.

The AP Manger supports locating faults in an AP in abnormal status. The fault locating means include tracing an interface, and tracing signaling.

6.2.2 AP WebUI The onsite maintenance personnel can manage the AP through the AP WebUI.

The AP WebUI allows users to perform the following operations:

Viewing AP status Viewing and changing AP configuration parameters Uploading the logs generated on the AP Loading software Uploading the configuration files

The functions of modifying parameters, uploading logs and configuration files, and loading software are for the maintenance engineers only, and are not recommended for the AP users.



6-5

6.3 O&M System of Central Office Equipment 6.3.1 AG Maintenance System

The AG is maintained through the M2000 and the LMT. The AG OMS performs the following functions:

Configuration management Device management Performance management Alarm management Software management Tracing management Security management

Configuration Management With the AG configuration management, you can add, delete, modify, and query the system data. The AG supports dynamic data configuration, and static data configuration.

Dynamic data configuration refers to changing data without stopping the system operation.

Static data configuration refers to a process during which administrators edit MML.txt offline first and load it, and then restart the system to validate the changed data.

Device Management With the device management function of the AG, you can monitor, control and test the hardware and links of the system.

The AG provides the following device management functions:

Status query function The AG allows you to query the status of a board, optical port, Message Transfer Part Level 3 (MTP3) link, destination signaling point, and sub-system.

Status control function − Resetting and switching a board − Blocking/Unblocking an optical port, MTP3 link and GTP path − Enabling/Disabling a destination signaling point, and a sub-system

Test function The test function provides important means for locating faults and detecting problems. The AG supports SAAL link self-loop test and GTP path test.

Performance Management Performance management is to collect the data that reflects network operation from the AG and the network around it.

The performance management system actively reports the measurement results of every measurement period to the M2000 server.




Issue 02 (2009-08-14)

The M2000 client supports querying, classifying and displaying (in diagram) the performance measurement results.

Alarm Management The alarm management function of the AG is intended to monitor the AGs and facilitate daily maintenance.

The alarms generated in an AG are reported to the M2000 and the LMT in real-time through the MML interface. The AG supports connecting to an external alarm box for reminding the maintenance engineer of the occurrence of an alarm through sound and light.

The alarms reported by the AG are classified into fault alarms and event alarms. Based on alarm severity, fault alarms are classified into critical alarms, major alarms, minor alarms, and warning alarms.

The maintenance engineer handles alarms through the alarm console and the maintenance console. The alarm operations include alarm browsing, alarm log query, alarm configuration, alarm maintenance, and alarm filtering.

Software Management Software management includes version file management and patch file management. The version file and patch file can be downloaded through the FTP protocol from the version server to a local AG, where the software and patches are loaded and activated.

The AG allows installing patches to eliminate faults online without stopping services.

Tracing Management The tracing management function of the AG can greatly facilitate the device maintenance.

The AG supports tracing messages of the Iu interface. The AG also supports tracing messages of a layer, including Signaling Connection Control Part (SCCP), Signaling ATM Adaptation Layer (SAAL), and Stream Control Transmission Protocol (SCTP).

Maintenance personnel can save tracing results based on requirements and query the results through the tracing reviewing tool when necessary.

Security Management The security management of the AG involves:

Operation right management The rights of operators are managed on the basis of command groups. A command group refers to a group of commands. The commands are first allocated to various command groups, and are then allocated to operators with various operation rights. In this way, the rights of the operators are managed.

Log management − Operation log

An operation log records the Information about the operations performed by an operator, including the user name, user ID, login IP address, command executed, execution time, and execution result.

− Security log



6-7

A security log records the Information about all login events, authentication events, right control events, and security mechanism modification.

6.3.2 AHR O&M System Physically, the AHR is a server, and is maintained in the M2000 and the AHR Client. The AHR O&M system supports the following functions:

AP data management AP area management AHR system management AHR log management

AP Data Management The AHR provides the AP data management functions:

Registering/Deregistering an AP The AHR supports registering/deregistering APs individually or in batches.

Querying and modifying the Information about an AP You can query an AP by the user name or user ID, and then modify the information of the AP.

Managing the access control list of an AP The AHR supports controlling the access control list of every AP in the AHR system and number of UEs under all AP.

AP Area Management An AP area is the area specified by the carrier for an AP in reference to the geographic area for the convenience of business operation and AP management & maintenance. The Information about an AP area includes AG, SeGW, clock server, AP manager, IP addresses of NEs, and location.

The AP area management includes adding, modifying, and deleting an AP area.

The AHR provides the following AP area management functions:

AP migration management − The AHR supports shifting an AP within an AP manager or between two AP

managers. − The AHR supports shifting one AP or multiple APs. − The AHR supports shifting an AP between AP areas.

Binding an AP area with the IP address list of the AG, SeGW, clock server, and AP manager.

An AP area may contain multiple or a single SeGW, clock server, and AP manager. An SeGW, Clock server, and AP manager may belong to one or multiple AP areas.

AHR System Management The AHR provides the following system management functions:




Issue 02 (2009-08-14)

Data backup and recovery The AHR supports backing up its own data and data of the AP periodically. When the system is abnormal, the user can recover the system by using the backup data.

Right management The right management is to control the operators and rights of the operators. Every user belongs to a user type. The user types include administrator, common operator, and guest. An administrator has all operation rights; a common operator has service operation rights; a guest has the query right.

Alarm management When the AHR system is abnormal, the AHR reports the following alarms through the SNMP interface: − When a process of the AHR is abnormal, the AHR reports service abnormality event

alarm. − When the total number of UEs accessing the AP reaches the upper threshold, the

AHR reports the UE access license insufficiency alarm. The alarm threshold of accessed UEs under an AP can be configured.

AHR Log Management The AHR supports operation log query. The operation log records the operations performed by all operators in the AHR.

6.3.3 Clock Server O&M System The operation and maintenance for the clock server are made in the M2000 and the LMT.

The O&M of the clock server meets the requirement of users for operation and maintenance and provides the following O&M functions:

Security management Configuration management Software management Alarm management Log management

Security Management The clock server protects the operator's information. If an operator has not operated an NE for a long time, the OM interface is locked automatically.

Configuration Management Configuration management is mainly applied in NE maintenance and data configuration. Configuration management supports the consistency check for configured data. Data can be configured dynamically or statically.

Dynamic data configuration mode: The modified data can be validated immediately. Static data configuration mode: The modified data cannot be validated until the

equipment is reset.



6-9

Software Management The software management function supports software version management and software upgrading.

Alarm Management The alarm management system of the clock server detects and reports the faults of NEs in real time. It also displays alarms and the suggestions for clearing the alarms on the M2000 or LMT.

Log Management The log management function supports recording system operation information in real-time, and saving the records in a log. The log can help to locate and solve system problems.

6.3.4 SeGW Maintenance System The operation and maintenance for the SeGW are performed on the M2000 and the User-interface. The maintenance system of the SeGWs supports alarm functions. Data configuration and software upgrading are implemented through the Telnet function of the SeGW.

uBro Solution Description 7 Service Operation


7-1

7 Service Operation

About Thi

T e contents o

s Chapter

he following table lists th f this chapter.

Section Describes

7.1 Service Provisioning visioning, AP registration, AP user ID, service proAP deregistration, AP migration, and AP access control list maintenance.

7.2 AP Installation Installation of the AP.

7.3 Interference Processing Ways of making the AP free from interference.

7.4 Upgrading of the AP Upgrade of the AP.

7.5 Maintenance of the AP Maintenance of the AP.

7 Service Operation uBro



Issue 02 (2009-08-14)

7.1 Service Provisioning The uBro solution provides (U) SIM card based service provisioning scheme. As a result, the AP supports plug & play, satisfying the carrier's requirements.

7.1.1 AP User Identifying Scheme The registration information of an AP user must carry the AP user ID. The uBro solution supports four AP user identification schemes:

Adopt the APEI of an AP for uniquely identifying an AP user and bind APEI with the IMSI of the (U) SIM card. In this scheme, if a user intends to change the AP, the user must start the deregistration flow and then the registration flow. If the user intends to replace the (U) SIM card, the carrier must modify the registration data.

Adopt the APEI of the AP for identifying an AP user, but the APEI is not bound with the IMSI of the (U) SIM card. In this scheme, if a user intends to change the AP, the user must start the deregistration flow and then the registration flow. The user can replace the (U) SIM card without modifying any registration data.

Adopt the IMSI of the (U) SIM card for identifying an AP user uniquely, and bind the IMSI with the APEI of the AP. In this scheme, if a user intends to replace the (U) SIM card, the user must start the deregistration flow and then the registration flow. If the user intends to replace the AP, the carrier must modify the registration data.

Adopt the IMSI of the (U) SIM card for identifying an AP user uniquely, but the IMSI is not bound with the APEI of the AP. In this scheme, if a user intends to replace the (U) SIM card, the user must start the deregistration flow and then the registration flow. The user can replace the AP without modifying any registration data.

7.1.2 Service Provisioning Mode

Service Sales Mode There are two service sale modes:

Independent service sale mode The carrier sells the AP and the (U) SIM card separately. The user can purchase the AP and the (U) SIM card separately. The user can insert the (U) SIM card into the AP in reference of the user manual.

Bundle sales The carrier sells the AP and the (U) SIM card by binding them together. Before selling the AP to the user, the carrier has already inserted the (U) SIM card into the AP. But the (U) SIM card is invisible to the user who has purchased the AP.

Service Sale Flow There are two service sale flows:



7-3

Business hall of the carrier If a user intends to apply for services, the user goes to the carrier's business hall, fills in the service application form, and submits the user information.

Subscription through the network The user logs in to the web site of the carrier, fills in the service application form, and submits the user information. The user pays the service through electronic account transfer, remittance, or a credit card.

7.1.3 AP Registration

Registration Information During AP registration, the carrier's BOSS generates the following AP registration information:

Basic information of the AP user, including the user name, user ID, telephone number, mobile phone number, post code, dwelling place, email, and AP name.

Information about the AP user's residential area, house: administration region, area, floor, structure, latitude and longitude of the house.

Identification information of the AP user, including APEI of the AP, and IMSI of the (U) SIM card.

Service information of the AP user, including the home group of the AP, maximum user number of the AP, access control list of the AP, location service selection, and location indication mode.

Registration Flow During AP registration, the information is exchanged among the user, BOSS of the carrier, AHR, and AP manager. The following describes the AP registration flow:

1. The user submits AP registration application to the carrier and provides the Information about the AP user.

2. The carrier inputs the user information of the AP into its BOSS system and generates the AP registration information. The carrier's BOSS system sends the AP registration information to the AHR through the SOAP interface.

3. The AHR checks the validity of the AP registration information. If invalid, the AHR rejects the registration; if valid, the AHR saves the registration information. Meanwhile, the AHR determines the home group of the AP according to the registration information, and allocates an AP index to the AP user.

4. The AHR synchronizes the information of the AP home group and the AP Index to the AP manager. In the initial power-on, the AP manager configures network parameters for the AP.

7.1.4 AP Deregistration AP deregistration is to deregister the AP user and interrupt the AP service. The following describes the deregistration flow:

1. The AP user submits an AP deregistration application to the carrier's BOSS system. 2. The carrier's BOSS system sends the AP deregistration request to the AHR.




Issue 02 (2009-08-14)

3. The AHR receives the messages from the BOSS system, and then deletes the information of the AP user from the databases. Meanwhile, the AHR notifies the AP manager and the AG to delete the information of the AP user and terminates the service.

7.1.5 AP Migration AP migration is to shift an AP from one home group to another. During the migration process, the information of the AP home group is reallocated.

In the uBro solution, the AP migration involves two scenarios:

Shifting an AP between home groups under an AP manager. In the AP migration process, the AHR only needs to modify the area information, home group information, and save the information.

Shifting an AP between different home groups under two AP managers. That is, shift an AP from one AP manager to another AP manager. During the AP migration process, the AHR deregisters the original AP and then register the AP. For the AP manager from which the AP, the information of the home group must be deleted; for the AP manager to which the AP is shifted, the information of the home group must be added.

The uBro solution provides the following AP migration application scenarios:

Migration of an AP Migration of multiple APs Migration of an AP home group

7.1.6 Maintenance of the Access Control List of the AP Maintenance of the access control list of the AP is to query and modify the access control list of the AP through the BOSS of the carrier.

Flow of Querying the Access Control List of the AP The following describes the flow of querying the access control list of the AP:

1. The user logs in to the Website of carrier or goes to the business hall of the carrier and queries the access control list of the AP through the BOSS. The BOSS system of the carrier checks the ID of the AP user. If the user is an illegitimate user, the BOSS rejects the query; if the user is legitimate, the BOSS system permits the query.

2. If the query request of the legitimate user is approved, the BOSS system sends the AP user ID and query request to the AHR.

3. The AHR queries the access control list of the AP according to the AP user ID, and returns the access control list of the AP to the BOSS.

4. The BOSS replaces the IMSI numbers in the access control list of the AP with MSISDN, and displays it for the user.

Flow of Modifying the Access Control List of the AP The following describes the flow of modifying the access control list of the AP:

The modification involves adding entries to the access control list and deleting entries from the access control list. The following describes the flow of modifying the access control list of the AP:



7-5

1. The user logs in to the Website of carrier or goes to the business hall of the carrier and applies for modifying the access control list of the AP through the BOSS. The BOSS system of the carrier checks the ID of the AP user. If the user is an illegitimate user, the BOSS rejects the modification request; if the user is legitimate, the BOSS system permits the modification request.

2. If the modification request of the legitimate user is approved, the BOSS converts the MSISDN provided by the user into IMSI number. Meanwhile, the BOSS sends the AP user ID and modification request of the user to the AHR.

3. The AHR modifies the access control list of the AP, saves the modifications, and returns the modified access control list to the BOSS. The BOSS displays the modified access control list to the AP user.

4. The AHR sends the modified access control list to the AG, and the AG then sends the modified access control list to the AP.

7.2 AP Installation The AP is small in size, and can be mounted on the desk or wall at home, in SOHOs, and in SMEs. The carrier adopts different installation methods for different installation environment.

Home and SOHO The AP user can install the AP in line with the UAP2105 User Guide delivered with the AP independently.

SME The ePico user can install the ePico in line with the ePico3801 User Guide delivered with the ePico independently. In the SME environment, the quantity of ePicos to be installed is very large. The engineers of the carrier should send engineers to provide onsite installation guide.

7.3 Interference Processing During the utilization process, the AP may be subject to external interferences. By viewing the interference LED, the AP user can get to know the seriousness of the interference, and take actions according to the seriousness of the interference.

There are two types of interference against the AP:

Temporary interference If there is temporary interference in the AP, the AP can recover through power control.

Permanent interference When the interference source against the AP exists on long term basis and the AP cannot counter the interference through power control, the AP user needs to shift the AP until the interference LED turns to green/blue. If the AP user cannot remove the interference by shifting the AP, the AP user needs to dial the hotline of the carrier to report the fault. After receiving the report from the AP user, the carrier's maintenance engineer can adjust the wireless parameters of the AP through the AP manager to reduce the interference until the interference LED turns to green/blue.




Issue 02 (2009-08-14)

If the carrier's maintenance engineer cannot reduce the interference by adjusting the wireless parameters of the AP through the AP manager, the carrier should send engineers to remove the interference on site.

7.4 Upgrading of the AP When providing new services or solving software faults, the carrier must upgrade the software of the AP. The software of the AP can be upgraded automatically between the AP and the AP manager. The software of the AP is usually upgraded once every one or two years, provided that the normal use of the AP is not affected.

The software of the AP is usually upgraded for the following purposes:

Solving some special problems Removing serious bugs in the software Providing new functions

7.5 Maintenance of the AP When the AP becomes faulty, the AP user can remove the faults according to the UAP2105 User Guide, and ePico3801 User Guide. If the fault still exits, the AP user can remove the fault through the following means:

Remote fault handling The user can make a customer service call to report the fault. The engineer analyzes the fault identification data of the AP online, and eliminates the fault by changing configured data or upgrading the software

Onsite fault handling If the fault cannot be removed through remote fault maintenance, the carrier sends maintenance engineers to handle the fault onsite. If the AP cannot be restored onsite, the maintenance engineer brings the faulty AP back to the service department of the telecom carrier. During the maintenance period, the telecom carrier can lend a temporary AP to the user.

uBro Solution Description 8 Reference Information


8-1

8 Reference Information

About Thi

T e contents o

s Chapter

he following table lists th f this chapter.

Section Describes

8.1 System Performance ce parameters of major NEs in the uBro solution. Performan

8.2 Reference Standards and Protocols

Reference standards and protocols of the uBro solution.

8 Reference Information uBro



Issue 02 (2009-08-14)

8.1 System Performance 8.1.1 AP

Table 8-1 lists the system performance parameters of the AP.

Table 8-1 System performance parameters of the AP

Parameter ePico3801 UAP2105

Frequency band UL: 1920 MHz to 1980 MHz DL: 2110 MHz to 2170 MHz

UL: 1920 MHz to 1980 MHz DL: 2110 MHz to 2170 MHz

Maximum TX power 20 dBm (100 mW) 13 dBm (20 mW)

Number of carriers One carrier per cell One carrier per cell

CE (Channel Elements) number

32 20

TX/RX diversity No TX or RX diversity No TX or RX diversity

Receiver sensitivity -110 dBm -110 dBm

Clock precision ±0.1 ppm ±0.1 ppm

8.1.2 AG Table 8-2 lists the system performance parameters of the AG.

Table 8-2 System performance parameters of the AG

Parameter Value

Data forwarding capability in the PS domain 3 Gbit/s

Voice forwarding capability in the CS domain 18,000 Erl

Number of managed APs 75,000

8.1.3 AP Manager Table 8-3 lists the system performance parameters of the AP manager.

Table 8-3 System performance parameters of the AP manager

Item Parameter

Number of managed APs 250,000



8-3

Item Parameter

Number of concurrent upgraded APs 70

Number of concurrent handled alarms 40

8.1.4 AHR The performance specifications of the AHR vary according to its hardware configurations and are described in terms of the home network and office network.

For the performance specifications of the ATAE server configured with one disk array (with six disks used), see Table 8-4.

For the performance specifications of the ATAE server configured with two disk arrays (with 12 disks used), see Table 8-5.

Table 8-4 Performance specifications of the AHR (Basic configuration)

Name Value of Home Networks

Value of Office Networks

Number of managed APs 150,000 50,000 (15,000 in group mode)

Number of managed UEs (IMSIs in ACL) 4,800,000 1,600,000 (not including group ACL)

Number of managed UEs (Max User, Concurrent)

600,000 800,000

Number of APs managed in a group 10,000 1024

Number of IMSIs managed in a group 1024 1024

Number of UE managed in an AP 32 32

Max number of concurrent users in an AP 4 16

Table 8-5 Performance specifications of the AHR (Medium configuration)



Number of managed APs 500,000 160,000 (50,000 in group mode)

Number of managed UEs (IMSIs in ACL) 16,000,000 4,800,000 (not including group ACL)

Number of managed UEs (Max User, Concurrent)

2,000,000 (4 UEs per AP)

2,400,000 (16 UEs per AP)

Number of APs managed in a group 10,000 1024

8 Reference Information uBro



Issue 02 (2009-08-14)



Number of IMSIs managed in a group 1024 1024

Number of UE managed in an AP 32 32

Max number of concurrent users in an AP 4 16

The bandwidth between the AHR server and the client is required to be 256 kbit/s. One AHR server can connect to a maximum of 20 clients at the same time.

The bandwidth between the AHR server and any of the AAA, AG, and AP manager is required to be 10 Mbit/s.

8.1.5 Clock Server Table 8-6 lists the system performance parameters of the clock server.

Table 8-6 System performance parameters of the clock server

Item Parameter

Maximum number of supported clients

10,240 APs

Maximum packet-transmitting rate 128pps (packet per second) (in the case of IEEE1588V2) 50pps (packet per second) (in the case of Huawei private protocol)

Maximum occupied bandwidth of each channel of signals

Normal value: 20kbit/s, Maximum value: 40kbit/s (in the case of IEEE1588V2) Normal value: 30kbit/s, Maximum value: 50kbit/s (in the case of Huawei private protocol)

Output clock precision When the server is directly connected to the client: 10 ppb (parts per billion) When the server is not directly connected to the client: 50 ppb (parts per billion)

Clock holding time 7 days

8.1.6 SeGW Table 8-7 lists the system performance parameters of the SeGW.



8-5

Table 8-7 System performance parameters of the SeGW

Item Performance of the Eudemon 8080E

Performance of the Eudemon 1000E

Number of IPSec tunnels 80,000 (2*ESPU) 15,000

Data processing capability of IPSec

16Gbit/s (2*ESPU) 5.6Gbit/s

8.1.7 M2000 Table 8-8 lists the system performance parameters of the M2000.

Table 8-8 System performance parameters of M2000

Item Parameter

Maximum M2000 system capacity (M2000 based on ATAE platform)

18 equivalent NEs (25 equivalent NEs if disk arrays are used)

8.1.8 AAA Table 8-9 lists the system performance parameters of the AAA.

Table 8-9 System performance parameters of AAA

Item Parameter

The max amount of AP 500,000

The max active AP 500k*25.2%=126,000

RADIUS authentication message processing rate 126K/3600=35 pieces per second

RADIUS transaction processing rate 35 pieces per second

SS7 processing rate 35 pieces per second

8.2 Reference Standards and Protocols This solution complies with the following standards and protocols:

3GPP 3GPP R6 2006-03, 3GPP R99/R4/R5 (mainly including Uu/Iu interface protocols)

IETF standards IP, TCP, UDP, SCTP, RTP, and PPP

uBro Solution Description A Glossary

A Glossary

Numberics

PP representative international standard organization consisting of telecom standard rganizations of many countries and regions. It is founded in 1998.

A

Authorization, and Accounting protocol. Authentication refers to dentities before the users use network resources. Authorization

uditing.

AP BOOT process h as the e. The

he NEs based on the IP addresses sent by the AHR.

munity f multiple home APs. It facilitates the sharing of AP

P

AP zone A zone allocated to the AP by the operator from the aspect of service operation. It

3G Ao

AAA The Authentication,authenticating user irefers to authorizing users to use network resources. Accounting refers to collecting and recording the use of network resources for charging or a

ACL Access control list. A traffic filter configured on a router and used to identify the packets of a certain type based on an attribute of the packets, such as the IP address.

The process during which the AP obtains the IP addresses of related NEs sucAG, SeGW, AP manager, and IP clock after being powered on for the first timAP sends a Boot request to the AHR through the provisioning AG. Then the AHR sends the AP a Boot reply carrying the configuration information of the AP. After that, the AP reconnects t

AP com An AP group consisting oresources. AP users in the same community can enjoy the services provided by all the APs in the community.

APEI AP equipment identity. A serial number allocated to an AP by the manufacturer. It uniquely identifies an Awhen you remotely maintain APs through the AP manager.

facilitates the management and maintenance of the AP. Generally, AP zones are allocated based on geographical areas. The zone information includes the IP addresses and locations of the AP manager, AG, SeGW, and clock server.

A Glossary uBro Solution

Description

uthorization user

he function of managing authorized users. The AP is a UMTS access device used in e SOHO, in the SME, or at home. AP users can modify the parameter values about P access control on the Web site provided by the carrier or telephone the carrier and

l

the AHR updates the stored parameters bout AP access control and sends the parameters to the appropriate AP for nchronization.

B

blind handover oad control module)

AC nection admission control. series of actions taken by the network during the call setup phase to determine hether a connection request should be accepted or rejected.

r

cell reselection uring which the MS moves from the residential cell to a cell with

P group p consisting of multiple enterprise APs. It facilitates the sharing of AP

rvice

sh SMS short message automatically displayed on the receiving mobile phone. If not saved, a message is deleted automatically.

sm

nnection bandwidth and QoS are decreased.

amanagement

TthArequest the carrier to reset such parameters. The parameters about AP access controare the access mode (such as open, close, and group) and ACL. These parameters aresent to the AHR through the BOSS. Then asy

The handover triggered by an algorithm module (such as the lrather than UE measurement.

C

C ConAw

cell handove The process during which the UE is moved from one cell to another to implement service access or retain the ongoing call in the wireless communications system.

The process dstronger signals if certain conditions are met.

E

EA An AP grouresources. AP users in the same group can enjoy the services provided by all the APs in the group.

emergency call se A service during which a user makes an emergency call and the system identifies the call, processes the call, and then routes the call to the emergency center.

F

fla Asuch

fuse mechani A mechanism set up at the places nearest to attack resources to eliminate or decrease harmfulness. Before the network and valid users suffer from the attack, the connections between malicious terminals and the network are disconnected automatically, or the co


IKE

ubscriber identity. niquely

and

itial power-on scenario caused by the start of the AP. In this scenario, the AP requests account ation from the AHR, and then the AHR sends the information to the AP. The

ccount information of the AP consists of the APIE, maximum number of connected address, local SCTP port number, location indication mode,

.

ure the confidentiality, integrity, and genuineness of the packets

I ocation area identity. n

AC ocation area code. code used to uniquely identify a location area within a PLMN. It ranges from 0 to 535.

M

blind handover triggered by an algorithm module (such as the load control module)

I

Internet Key Exchange Protocol. A protocol constructed on the framework defined by the ISAKMP. It provides IPSecwith an automatic negotiation shared key to set up SAs, thus facilitating the use and management of IPSec.

IMSI International mobile sA number with not more than 15 digits and used to identify a mobile user uand globally. It is stored in the HLR, VLR, and (U) SIM and transmitted through the radio interface and MAP interface. It consists of the MCC, MNC, and MSINadopts decimal coding.

in Ainformausers, ACL, internal IP location personalization display, longitude, and latitude, as well as the IP addresses of the uBro core NEs, namely the AP manager, AG, SeGW, and clock server.

IPsec IP Security ProtocolA generic term used to describe a set of open protocols. It allows specific communication parties to perform encryption and data source authentication on the IP layer to enstransmitted over the Internet.

L

LA LA code consisting of the MCC, MNC, and LAC and used to identify a PLMN locatioarea globally and uniquely.

L LA65

location identification The process during which the system confirms the new location of the UE after the UE is moved.

The handover rather than UE measurement.

A Glossary uBro Solution

Description

NAT traversal

ynamically based on a protocol. Therefore, the call signaling process cannot be set tly.

g cell cellular mobile telephone system, a neighboring cell refers to the cell shared by rea.

terference interference in the AP and caused by the wireless environment.

P context acket Data Protocol context. nt on both the SGSN and the GGSN which contains the

er is currently visiting and the GGSN serving the subscriber access point.

d

RX sensitivity receiver can receive strong signals.

ry terference

udden and temporary interference in the AP in a moment.

/RX diversity technology used to originate or receive signals through an antenna array at the ng end. The diversity technology is an effective way to

N

A solution to the identification and change of various signaling messages as well as the pre-allocation of media UDP ports. The NAT device and firewall convert only the IP, TCP, and UDP headers of general packets. In H.323, SIP, MGCP, and H.248, however, the IP address is private and the private IP addresses in user signaling messages cannot be changed, and the IP addresses in media flows are negotiated dup correc

neighborin In the the coverage area and the current service a

P

permanent in

Long-term

PD PA data structure presesubscriber's session information when the subscriber is in an active session. When a mobile subscriber wants to use GPRS, the user must first attach and then activate a PDP context. In this way, a PDP context data structure is allocated to the SGSN that the subscrib

R

RANAP Radio Access Network Application Part. The wireless network protocol used on the Iu interface of a UMTS system. It is useto create wireless network bearer between the core network and the AP.

The range within which the

S

SA Security association. A mechanism used for implementing the security services provided by IPSec for data flows. It includes the protocol, algorithm, and key and determines how to process IPpackets.

T

temporain

The s

TX Aoriginating end or receiviprevent multi-path fading.


uBro network

y the

UE e ME and SIM/USIM.

N irtual private network. ate network. It encompasses encapsulated, encrypted, and shared or public networks. Private networks can connect to

VRRP

IP address and the hosts in the network communicate with other networks with this IP address. If the master router in the backup group fails, a backup router in the backup group becomes the new master router and continues to provide routing services for the hosts in the network. In this way, hosts in the network can continue to communicate with external networks. This protocol is designed for the LAN that has multicast or broadcast capabilities, for example, the Ethernet.

X

xDSL x digital subscriber line. A modulation/demodulation technology used to provide broadband high-speed Internet services by adopting traditional telephone lines and the digital compression mode with a frequency higher than 4 kHz. This technology allows you to log in to the Internet and make calls at the same time because it uses a frequency spectrum higher than that of ordinary speech signals. The current technologies related to xDSL include ADSL, RADSL, SDSL, and VDSL.

U

UMTS broadband network. A network providing a low-cost and easy-deployed solution to the coverage of signals in the SOHO, in the SME, and at home. It helps to expand the area covered bUMTS network, increase network capacity, and improve the quality of indoor signals,thus improving the user experience in the SOHO, in the SME, and at home.

User equipment. A combination of th

V

VP VThe extension of the privauthenticated links acrossthe Internet remotely through the VPN.

Virtual Router Redundancy Protocol. A protocol through which a group of routers in a LAN including one master router and several backup routers are combined to form a virtual router, namely, the backup group. The virtual router has its own

uBro Solution Description B Acronyms and Abbreviations

B Acronyms and Abbreviations

Numberics

PP rd Generation Partnership Project

orization and Accounting

L ital Subscriber Line

2+ ubscriber Line 2 PLUS

ay

ol

P Manager P Management System

M synchronous Transfer Mode

AS roadband Access Server

U entral Processing Unit

3G 3

A

AAA Authentication, Auth

AAL2 ATM Adaptation Layer 2

ACL Access Control List

ADS Asymmetrical Dig

ADSL Asymmetrical Digital S

AG Access Gatew

AHR AP Home Register

AP Access Point

APEI AP Equipment Identity

APM AP Management Private Protoc

A A

AT A

B

BR B

C

CN Core Network

CP C

CS Circuit Switched domain

B Acronyms and Abbreviations uBro Solution

Description

on Protocol

erv ice

oS enial of Service

LAM igital Subscriber Line Access Multiplexer

Iu nhanced Iu Interface

P ncapsulating Security Payload

E ast Ethernet

P ile Transfer Protocol

nt

TP-U PRS Tunneling Protocol for User Plane

I raphical User Interface

e

ss

SPA igh Speed Packet Access

UPA igh Speed Uplink Packet Access

D

DHCP Dynamic Host Configurati

DiffS Differentiated Serv

DNS Domain Name Server

D D

DS D

E

e E

ES E

F

F F

FT F

G

GGSN Gateway GPRS Support Node

GMM GPRS Mobility Manageme

GPRS General Packet Radio Service

GTP GPRS Tunneling Protocol

G G

GU G

H

HCS Hierarchical Cell Structur

HGW Home Gateway

HLR Home Location Register

HSDPA High Speed Downlink Packet Acce

H H

HS H

I

ID Identity


ange protocol

criber Identity

ddress ocol

tocol

u Interface

P User Plane

ntity

CS ocation Service

T ocal Maintenance Terminal

tation layer

M

SISDN obile Station International ISDN Number

P3 essage Transfer Part Level 3

Server

ranslation

AT-T AT Traversal

etwork Element

IKE Internet Key Exch

IMSI International Mobile Subs

IP a Internet Prot

IPsec IP Security Pro

I Iu

IuU Iu

L

LAC Location Area Code

LAI Location Area Ide

LAN Local Area Network

L L

LM L

M

M3UA MTP3 User Adap

MAC Media Access Control

MGW Media Gateway

MM Mobility Management

MML Man Machine Language

MODE Modulator-DEModulator

MPLS Multi-protocol Label Switch

MSC Mobile Switching Center

M M

MT M

N

NAS Network Access

NAT Network Address T

N N

NE N

B Acronyms and Abbreviations uBro Solution

Description

C peration & Maintenance Center

tem

E thernet

S acket Switched Domain

N ublic Switched Telephone Network

nnel

E uality of Experience

P ation Part

NC adio Network Controller

C adio Resource Control

otocol

ty

Part

Protocol

NMP imple Network Management Protocol

O

OM O

OSS Operating Support Sys

P

PDP Packet Data Protocol

PLMN Public Land Mobile Network

PPPO Point to point protocol over E

P P

PST P

PVC Permanent Virtual Cha

Q

Qo Q

QoS Quality of Service

R

RAC Routing Area Code

RAI Routing Area Identity

RANA Radio Access Network Applic

R R

RR R

RTP Real-time Transport Pr

S

SAI Service Area Identi

SCCP Signaling Connection Control

SCTP Stream Control Transmission

SeGW Security Gateway

SGSN Serving GPRS Support Node

SIM Subscriber Identity Module

SME Small and Medium Enterprise

S S


HO mall Office and Home Office

ayer

Protocol

Protocol

E ser Equipment

TS niversal Mobile Telecommunications System

AN irtual Local Area Network

X

xDSL x Digital Subscriber Line

SO S

SPUA SCTP Private User Adaptation L

T

TCP Transmission Control

U

uBro UMTS Broadband

UDP User Datagram

U U

UM U

Uu Uu Interface

V

VL V

VPN Virtual Private Network

ubro solution description(v200r001_02,03).pdf

Documents